-
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
✨ Implement MachinePool Machines in CAPI, CAPD, and clusterctl #7938
Conversation
/hold |
test/infrastructure/docker/exp/internal/controllers/dockermachinepool_controller.go
Outdated
Show resolved
Hide resolved
d7623eb
to
7ea8b9f
Compare
920bcd2
to
29f27a9
Compare
/retest |
test/infrastructure/docker/exp/internal/controllers/dockermachinepool_controller.go
Outdated
Show resolved
Hide resolved
/retest |
b4cd27f
to
eb4eaeb
Compare
/retest |
/retest |
553215f
to
06a2eb1
Compare
I'll try to review this week |
@sbueringer Could you take a look at this when you have some time. Thanks! |
Yup will do. Got side tracked unfortunately, but now I hopefully have some time. |
Sounds good, thanks! |
"must match metadata.namespace", | ||
), | ||
) | ||
// InfraRef can be empty for MachinePool Machines so skip the check in that 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.
How are we getting around the OpenAPI validation run by the kube-apiserver? infrastructureRef is a required field on the Machine and its corresponding OpenAPI schema.
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.
Since it's not a pointer we just leave the infraRef uninitialized when we create it for MPMs. Is that what you're asking?
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'm surprised that it works as in the schema in the CRD infraRef is required. So the apiserver should block
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.
So for this to work I would expect that we have to change the Machine CRD to make infraRef optional (eg like config ref)
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.
But maybe there's a reason why it works anyway
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 think we can have uninitialized structs even if it's not optional. Should be the same reason a blank label selector works in CAAPH.
/retest |
a5813fb
to
c469b38
Compare
/retest |
c469b38
to
e9225c1
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.
/area machinepool
@fabriziopandini @sbueringer Do you think we're about good to merge this? |
@Jont828 As far as I remember we still have some racy conditions to sort out, but most of this is on me getting busy on many fronts and not keeping up on latest updates I was chatting with @CecileRobertMichon about having a meeting to help in getting this moving forward, I will try to get this moving soon |
e9225c1
to
e4c9c9f
Compare
@Jont828: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
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. |
What this PR does / why we need it: Add implementation for MachinePool Machines based off of this proposal.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4063