-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
✨ CABPK: Add support for kubeadm skipPhases field #5993
✨ CABPK: Add support for kubeadm skipPhases field #5993
Conversation
Welcome @dntosas! |
Hi @dntosas. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test (will take a closer look later) |
/retitle ✨ CABPK: Add support for kubeadm skipPhases field |
@dntosas Change looks good so far. The next step is implementing conversion. Please take a look, but feel absolutely free to ask if there are any questions! P.S. There are a few more videos about CAPI in general here: https://cluster-api.sigs.k8s.io/developer/guide.html?highlight=video#videos-explaining-capi-architecture-and-code-walkthroughs |
@dntosas let me know if I can help somehow to get this moving |
Hey @fabriziopandini, was kinda busy last weeks. Will take a look today and reach out to you if needed so to move forwards with this :) |
9b857d5
to
6d8ddaa
Compare
@sbueringer @fabriziopandini i think we are better now :) fixed failing tests |
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.
Thanks for the update!
/lgtm
@@ -96,6 +96,10 @@ func kubeadmInitConfigurationFuzzer(obj *bootstrapv1.InitConfiguration, c fuzz.C | |||
// InitConfiguration.Patches does not exist in kubeadm v1beta1 API, so setting it to nil in order to avoid | |||
// v1beta1 --> upstream v1beta1 -> v1beta1 round trip errors. | |||
obj.Patches = nil | |||
|
|||
// Initonfiguration.SkipPhases does not exist in kubeadm v1beta1 API, so setting it to nil in order to avoid |
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.
"Initonfiguration"?
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.
will push a fix in next hour(s) ☝️
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.
pushed ^^ thnx :)
Thanks looks good +/- the last nit above |
In this commit, we enable users to exclude specific phases of their choice during init/join command execution. This can be helpful in cases like provisioning a cluster without kube-proxy deployed. Note: This option takes effect only only on Kubernetes >=1.22.0. Signed-off-by: dntosas <ntosas@gmail.com>
6d8ddaa
to
541d94d
Compare
Thank you very much! /lgtm |
this is a great first contribution @dntosas, thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
/hold |
/hold cancel |
This patch does not show depending on the kubernetes version. And should the actual value used in skipPhases have the prefix such as
which one is right? |
I found reference at here.
in
is right thanks. |
What this PR does / why we need it:
In this PR, we enable users to exclude specific phases of their
choice during init/join command execution. This can be helpful in
cases like provisioning a cluster without kube-proxy deployed.
Note: This option takes effect only only on Kubernetes >=1.22.0.
Which issue(s) this PR fixes
Fixes #5357