Skip to content
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

Merged

Conversation

andreykont
Copy link
Contributor

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.

Copy link

netlify bot commented Mar 7, 2024

Deploy Preview for kamaji-documentation ready!

Name Link
🔨 Latest commit a1dd6fe
🔍 Latest deploy log https://app.netlify.com/sites/kamaji-documentation/deploys/660c071672a8b30008c961b3
😎 Deploy Preview https://deploy-preview-427--kamaji-documentation.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@andreykont andreykont marked this pull request as draft March 21, 2024 06:02
@andreykont andreykont marked this pull request as ready for review March 23, 2024 12:01
@hrak
Copy link

hrak commented Mar 28, 2024

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:

  • front proxy CA
  • SA certificate

Copy link
Member

@prometherion prometherion left a 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?

@andreykont
Copy link
Contributor Author

Of course, I will do

@andreykont andreykont marked this pull request as draft March 29, 2024 07:29
@andreykont
Copy link
Contributor Author

Hello @hrak. I fixed other secret's owner references.
Also I have tested owner reference restore process for all 13 secrets on my local environment.
Please look at PR again.

Copy link
Member

@prometherion prometherion left a 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.

@prometherion prometherion marked this pull request as ready for review April 2, 2024 15:25
@prometherion prometherion added this to the v0.4.3 milestone Apr 2, 2024
@prometherion prometherion added the bug Something isn't working label Apr 2, 2024
@hrak
Copy link

hrak commented Apr 3, 2024

LGTM, let's wait for @hrak's review too.

LGTM!

@prometherion prometherion merged commit dc3d506 into clastix:master Apr 3, 2024
10 checks passed
@prometherion prometherion modified the milestones: v0.4.3, v0.5.0 Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants