-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
[Hydra Maester] Creation no longer working from a CR #433
Comments
If there's been a recently update, do the RBAC resources for My feeling is that it's not able to patch to add the finaliser once you apply Just to note, we're running the same version and don't experience this issue. |
The maester has not been changed in a long while, I would rather look for the source in the k8s version used. But this is alarming as it may suggest that the current maester controller won't work properly on newer k8s versions 😞 |
@Demonsthere I think we can close this issue, because at GameVerse we use the latest k8s security update in our k8s clusters and there is no problem to create OAuth2Client using CR. And nobody has commented for 2 years so.... |
Closing as stale |
Preflight checklist
Describe the bug
I'm using since a long time this kind of CR to create my clients:
And I never got into trouble. But maybe after the last update (either Kubernetes or Hydra Maester) now when applying a new oauth2client I get this error:
It's quite hard to find information on internet but it could come from the type wrongly initiated... I tried multiple things according to my old other CR that worked a long time ago, that have other properties generated after creation. I tried to patch one by one and the only thing making it passes was to add the finalizer explicitly.
So if I'm using:
The Hydra Maester won't complain and will create immediately my client into Hydra.
It's so strange... any thought on this issue?
Thank you,
Reproducing the bug
Relevant log output
Relevant configuration
Version
Hydra Maester v0.0.26
On which operating system are you observing this issue?
No response
In which environment are you deploying?
No response
Additional Context
The text was updated successfully, but these errors were encountered: