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
Feat: Nodes are now owned by Provisioners, and will cascade on delete by default #1934
Conversation
✅ Deploy Preview for karpenter-docs-prod canceled.
|
c11e277
to
0019cec
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.
lgtm! We should add a --cascade=orphan
example to docs once the issue with it is figured out.
@@ -169,6 +169,7 @@ func (p *Provisioner) getPods(ctx context.Context) ([]*v1.Pod, error) { | |||
return pods, nil | |||
} | |||
|
|||
// nolint: gocyclo |
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.
😮
- apiGroups: [""] | ||
resources: ["pods/binding", "pods/eviction"] |
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.
nice tidying!
Fixes: #1268 #1738
Description
Previously, when a provisioner was deleted, the nodes would be leaked and require manual cleanup. With this change, deletion of a provisioner will result in deletion of the nodes it launched. This aligns with the GitOps mental model.
Since this is a breaking change, this will trigger a minor version bump.
How was this change tested?
make test
--cascade=orphan
. See: https://kubernetes.slack.com/archives/CAR30FCJZ/p1655243575953659. Ownerreferences may still be removed via API if node orphaning is necessary.Does this change impact docs?
Release Note
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.