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

Controller unreachable after cert-manager certificates expire #701

Open
kmorning opened this issue Aug 27, 2024 · 1 comment
Open

Controller unreachable after cert-manager certificates expire #701

kmorning opened this issue Aug 27, 2024 · 1 comment
Labels
enhancement New feature or request v2 This affects only Operator v2

Comments

@kmorning
Copy link

Environment details

  • Kubernetes v1.29.4
  • pireaeus-operator 2.5.1
  • cert-manager v1.14.5

Description
I've setup both the internal and api TLS using certmanager as described in how-to docs. It seems that the certificates are valid for 3 month upon issue. Certmanager renews the certificates automatically 1 month before expiry, but the deployed linstor pods still use the old certificates. When the original certificates expire, cluster communications are broken. I had to manually delete the controller, satellite and csi pods so that they spin up again using the renewed certs.

Desired behavior
Controller, satellite and csi pods should reload certs or restart after renewal.

@WanzenBug
Copy link
Member

I guess non of our components implement watching and reloading of the certificates.

@WanzenBug WanzenBug added enhancement New feature or request v2 This affects only Operator v2 labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v2 This affects only Operator v2
Projects
None yet
Development

No branches or pull requests

2 participants