-
Notifications
You must be signed in to change notification settings - Fork 112
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
Owner reference should be re-reconciled if it is lost for CA secret object #427
Owner reference should be re-reconciled if it is lost for CA secret object #427
Conversation
✅ Deploy Preview for kamaji-documentation ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This appears to be the case for more resources than just the CA. Other resources that don't set controller ref when the checksum is valid:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As pointed out by @hrak, may I ask you to ensure the controller references to all the secrets, please?
Of course, I will do |
Hello @hrak. I fixed other secret's owner references. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's wait for @hrak's review too.
LGTM! |
When you restore Kamaji tcp from backup, such tool as Velero deletes ownerReference on objects.
This may lead to bug if third-party controller take control under restored objects.
In my case I lost ca.crt and ca.key files in CA secret object.
The problem is described in detail here
According to CAPI specification about owner references:
Kamaji always has to restore owner reference for it's objects.