Add application credential finalizer management#466
Conversation
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2149808219c047b3bdc2a60b7057ee80 ❌ openstack-k8s-operators-content-provider FAILURE in 9m 35s |
dcc0ee2 to
c589f2f
Compare
c589f2f to
6dcb651
Compare
6dcb651 to
6746f66
Compare
6746f66 to
a97bce4
Compare
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 4m 02s |
|
recheck |
Signed-off-by: Veronika Fisarova <vfisarov@redhat.com>
a97bce4 to
76eb56d
Compare
|
Following the discussion in watcher-operator the AC finalizer management is now split into two phases:
This prevents a race condition where rapid AC rotations could revoke credentials still in use by running pods. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Deydra71, fmount The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The patch is in line with what we did in the other storage operators. |
08378e9
into
openstack-k8s-operators:main
Jira: OSPRH-27509
Application Credential dev-doc: https://github.com/openstack-k8s-operators/dev-docs/blob/main/application_credentials.md
Status.ApplicationCredentialSecretopenstack.org/swift-ac-consumerfinalizer to the AC secret after service config is renderedThis ensures that the keystone-operator cannot revoke a rotated AC secret while Swift is still consuming it.
Depends-On: openstack-k8s-operators/keystone-operator#685
Assisted-by: Claude Opus 4.6 noreply@anthropic.com