-
Notifications
You must be signed in to change notification settings - Fork 225
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: Set default values on the APIVersion
and Kind
on the nodeClassRef
#1093
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: engedaam The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e2cc36c
to
c12bdf4
Compare
Pull Request Test Coverage Report for Build 8472762287Details
💛 - Coveralls |
4e6aa07
to
06665e6
Compare
06665e6
to
6bc40db
Compare
/hold We need to make sure that this PR is merged in after drift hash versioning have been released. Issue: #957 |
/test all |
@engedaam: No jobs can be run with
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
6bc40db
to
4462c2f
Compare
99852cd
to
067b22d
Compare
APIVersion
and Kind
on the nodeClassRefAPIVersion
and Kind
on the nodeClassRef (DO NOT MERGE)
067b22d
to
5dcddba
Compare
APIVersion
and Kind
on the nodeClassRef (DO NOT MERGE)APIVersion
and Kind
on the nodeClassRef
/remove-hold |
5dcddba
to
21039c6
Compare
21039c6
to
0ee2838
Compare
// To avoid a breaking change on the NodePool API, we will be setting a default APIVersion and Kind | ||
// defined by the cloudprovider to each nodeClassRef on every NodePool. This will be removed once | ||
// the NodePool API requires APIVersion and Kind to be set at NodePool creation. | ||
// TODO: remove at v1 when APIVersion and Kind are required fields on NodePool |
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 was thinking here, should we make it required, or should we make it optional and just require that cloud providers add the defaulting logic to include the GVK into NodePools? If we require it, we can't default it. Is there a point in allowing users to be wrong here?
0ee2838
to
8a5ff14
Compare
8a5ff14
to
51a4027
Compare
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@engedaam Given that we are punting on setting the default GVK and we have already merged in the CloudProvider changes to allow for shorter reconciles, do we need to keep this PR open? I think if we were to make this change down-the-line, it would most likely take the form of something in our conversion webhooks |
Closing for now. We plan on handling defaults for the APIVersion and Kind as part of the conversion webhooks at v1. |
Fixes #N/A
Description
GetNodeClassGVK
to the cloudprovider interfaceAPIVersion
andKind
of the NodeClass that is supported by the provider. Karpenter will default all NodePools to theAPIVersion
andKind
, given by the provider, inside of eachnodeClassRef
.APIVersion
andKind
at runtime.nodeClassRef
required at v1, which will allow us to drop the defaulting behavior.apiVersion
andkind
innodeClassRef
#909How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.