Open emreberber opened 4 months ago
not sure I fully understand this .. you had a application ID in CSI then it expired and you replace the new application ID but it doesn't work?
Yes, that's right
did you try kill the pod then reload it o ensure at least in this way it works? I think it's in cloud-config which should reload when pod restart?
It will be fixed after pod restart, but can't it dynamically get the current secret without doing that?
that will need recreate the openstack client
which I think it's not currently supported, folks can comment if my understanding is correct
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When I delete or rotate the Openstack application credential, I updated the cinder-csi-cloud-config secret but it does not receive the new credentials.
What you expected to happen:
I was expecting it to continue dynamically with new credentials without restarting any pods
How to reproduce it:
I installed the Cinder CSI Plugin, then deleted the applicaiton credential, then created a new credential and updated the secret
Anything else we need to know?:
Environment: