Error if secret created and owned by keycloakclient is deleted before it #62
Assignees
Labels
bug
Something isn't working
Comments
|
Hi @mostoja. Thank you for your feedback. |
zmotso
added a commit
that referenced
this issue
Jun 25, 2024
Moved the deletion process of the KeycloakClient before any logic that requires client secrets. This will help avoid errors if the KeycloakClient secret is removed before it and the deletion process gets stuck.
10 tasks
NikolayMarusenko
pushed a commit
that referenced
this issue
Jun 25, 2024
Moved the deletion process of the KeycloakClient before any logic that requires client secrets. This will help avoid errors if the KeycloakClient secret is removed before it and the deletion process gets stuck.
|
lovely! can we expect new release and helm chart soon? |
|
I am also experiencing this issue. When can we expect a new release? |
|
This component will be released soon. You can track its progress here: #76. |
|
@mostoja @FWest98 keycloak-operator version 1.22 has been released with the latest fixes and improvements: https://github.com/epam/edp-keycloak-operator/releases/tag/v1.22.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If during deletion of keycloakclient's namespace secret owned by resource is deleted before resource I get an
unable to serve keycloak clienterror and resource is never deletedTo Reproduce
What did you do?
Tried deleting keycloakclient's namespace
What did you expect to see?
Namespace deleted
What did you see instead? Under which circumstances?
Deletion hanging becuase keycloakclient's finalizer is not removed
Kubernetes cluster type:
AKS
$ operator-sdk version$ go version$ kubectl versionScreenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: