-
Notifications
You must be signed in to change notification settings - Fork 979
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
move default provisioner to helm post-install hook #810
Conversation
✔️ Deploy Preview for karpenter-docs-prod ready! 🔨 Explore the source changes: 9f4188f 🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/61944aa6fb7d3800086616b3 😎 Browse the preview: https://deploy-preview-810--karpenter-docs-prod.netlify.app |
@@ -3,6 +3,9 @@ apiVersion: karpenter.sh/v1alpha5 | |||
kind: Provisioner | |||
metadata: | |||
name: default | |||
annotations: | |||
"helm.sh/hook": post-install | |||
"helm.sh/resource-policy": keep |
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.
What do these do?
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.
this tells helm that it's a post-install hook and to keep the resource rather than deleting it right after applying.
@@ -50,7 +50,10 @@ func (m *GenericControllerManager) RegisterControllers(ctx context.Context, cont | |||
} | |||
} | |||
if err := m.AddHealthzCheck("healthz", healthz.Ping); err != nil { |
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.
Can you call this livez (liveness)
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.
I can't tell if this is a joke. If it's not, the convention is healthz for liveness check
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.
hoooraaay
1. Issue, if available:
N/A
2. Description of changes:
post-install-hook
resource. Helm resources applied in a post-install-hook are applied after the regular release resources are applied and are technically not part of the release. If you specify the--wait
flag when helm installing, the post-install-hook will wait until release resources are in a Ready state. So, I have added readiness probes to both the controller and webhook deployments so that helm is signaled properly to begin the post-install-hook.3. Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.