Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cinder-csi-plugin] Cannot rotate secret dynamically #2629

Open
emreberber opened this issue Jul 23, 2024 · 6 comments
Open

[cinder-csi-plugin] Cannot rotate secret dynamically #2629

emreberber opened this issue Jul 23, 2024 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@emreberber
Copy link

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

/kind feature

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:

  • cinder-csi-plugin version: 2.30.0
  • OpenStack version: 6.6.0
  • Others:
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 23, 2024
@jichenjc
Copy link
Contributor

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?

@emreberber
Copy link
Author

Yes, that's right

@jichenjc
Copy link
Contributor

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?

@emreberber
Copy link
Author

It will be fixed after pod restart, but can't it dynamically get the current secret without doing that?

@jichenjc
Copy link
Contributor

that will need recreate the openstack client which I think it's not currently supported, folks can comment if my understanding is correct

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants