Closed as not planned
Closed as not planned
Description
Before reporting an issue
- I have searched existing issues
- I have reproduced the issue with the latest nightly release
Area
dependencies
Describe the bug
If a Keycloak instance with spec.http.tlsSecret points to a Secret that does not exist yet, the Keycloak instance doesn't recover from the error below even after the Secret it created, I had to bounced the Keycloak operator pod to get past the issue below
Version
22.0.1
Expected behavior
When the Secret becomes available, the Operator should continue reconciling the Keycloak instance and proceed past the previous error
Actual behavior
The Keycloak instance becomes stuck in Error state as the Operator stops reconciling it
How to Reproduce?
- Install and setup database (We use Postgres)
- Install Keycloak Operator
- Create Keycloak instance with the TLS Secret pointing to:
spec:
http:
tlsSecret: certificate-secret
- Keycloak Instance should error with the screenshot earlier above
- Setup TLS config (We use Cert Manager), this should eventually lead to the creation of Secret "certificate-secret"
- Keycloak Instance stays in error
Anything else?
We noted this previous issue which was marked resolved, however we're looking for a more permanent solution
#22170