-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
✨ Enable Kubernetes upgrades in CAPIM #8938
✨ Enable Kubernetes upgrades in CAPIM #8938
Conversation
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.
/area provider/infrastructure-in-memory
71c506c
to
a32cbda
Compare
72941e7
to
41841e7
Compare
/retitle ✨ Enable Kubernetes upgrades in CAPIM |
This should be ready for review now. This PR doesn't add an e2e test upgrade flow - I'm not sure of the best way to do that i.e. inline in our current test or as a new scaling test case. |
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.
great work!
just a couple of nits
test/infrastructure/inmemory/internal/controllers/inmemorymachine_controller.go
Outdated
Show resolved
Hide resolved
test/infrastructure/inmemory/internal/cloud/api/v1alpha1/etcdcluster_annotations.go
Outdated
Show resolved
Hide resolved
@@ -117,6 +119,15 @@ func (c *cache) List(resourceGroup string, list client.ObjectList, opts ...clien | |||
} | |||
} | |||
|
|||
// TODO: This only matches the nodeName field for pods. No other fieldSelectors are implemented. |
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.
WDYT about returning an error when we notice another field selector?
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.
// TODO: This only matches the nodeName field for pods. No other fieldSelectors are implemented. | ||
if pod, ok := obj.(*corev1.Pod); ok { | ||
if listOpts.FieldSelector != nil && !listOpts.FieldSelector.Empty() { | ||
if !listOpts.FieldSelector.Matches(fields.Set{"spec.nodeName": pod.Spec.NodeName}) { |
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.
Is there any way to check that the "incoming" field selector is the one we think it is?
(maybe I'm misreading this entire statement)
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'd like to take this as a follow-up for now. I'm not sure what else this might break currently.
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.
Sounds good
Looks like I basically added the same comment twice 😂
Signed-off-by: killianmuldoon <[email protected]>
41841e7
to
bd52d47
Compare
/lgtm |
LGTM label has been added. Git tree hash: a3d6d7a020e340c6290020a704d35d52a2a24fb5
|
Thx! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Enable upgrading of Kubernetes clusters using in-memory infrastructure with CAPIM.