-
Notifications
You must be signed in to change notification settings - Fork 661
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
Error updating status of newly created SealedSecrets resources #1354
Comments
Hi, Same here, recent sealedsecrets get stuck in fluxcd reconciliation InProgress in 0.24.2 |
hi everyone, we are investigating this bug. We will come back as soon as possible with fix/information about it. Sorry for the inconveniences Álvaro |
Hi Alvaro, Check out #1355, I explained what is happening and what I think is missing for everything to work :) Regards, Sebastien |
Unfortunately, I am still observing the same behavior :(
|
hi @tewfik-ghariani, let me check it. Thanks for notifying it |
It is fixed with v0.24.4 release, thanks a lot! |
Which component:
controller v0.24.2
Describe the bug
Hi, we have recently noticed that the operator complains about updating the status of newly created SealedSecrets resources, even though the unsealing operation is successful:
As a result, the corresponding secret resource is created but the SealedSecret resource doesn't have any status entry and the SYNCED field is not set to true
To Reproduce
Steps to reproduce the behavior:
kubeseal
status
field in the SealedSecret resourceExpected behavior
It is expected that the status field is shown as in v0.24.0 and no warnings are emitted in the logs
Version of Kubernetes:
Additional context
I confirm that this bug did not exist in v0.24.0 after testing it, and I have doubts that it might be due to this change: #1295 that was introduced in v0.24.2 as per the release notes
The text was updated successfully, but these errors were encountered: