-
Notifications
You must be signed in to change notification settings - Fork 13
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
Disable lakom via annotation from seed #106
Disable lakom via annotation from seed #106
Conversation
b864ba7
to
9049aa8
Compare
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.
Thanks!
I have some change requests in the in-code comments
charts/gardener-extension-shoot-lakom-service/templates/configmap-extension-config.yaml
Outdated
Show resolved
Hide resolved
…etion code Co-authored-by: Vladimir Nachev <[email protected]>
…on in configmap The annotation is a gardener implementation detail that does not need to be exposed via the values.yaml interface. This it's removed. Annotation is renamed to better reflect its function and official annotation naming conventions are used from https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#label-selector-and-annotation-conventions
73405a1
to
2081ec4
Compare
Hi @vpnachev, could you verify that this approach with |
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
What this PR does / why we need it:
ManagedSeed clusters do not need a lakom deployment since they can already be verified by the seed that's managing them. This feature allows us to configure this using an annotation on the seed resources of the managedseed.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: