-
Notifications
You must be signed in to change notification settings - Fork 41
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 control plane template #88
Implement control plane template #88
Conversation
As you mention this change really needs to be done as part of a API version bump to v1beta2 as the change is API breaking. |
@zawachte - i'll start work on a PR to bump the API version so that we can start work on v1beta1 (will also create the 0.1 release branch) |
PR is ready for review. I bumped the Also note that I tweaked the generated manifests. For example when generating the bootstrap manifests, we now only include the bootstrap subfolder: I also tested this patch locally by:
|
Thanks @anmazzotti . I will start reviewing. |
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 this @anmazzotti . A few minor comments, nothing major. Let me know if i need to clarify anything.
It would have been easier for reviewers if the introduction of the v1beta2 api version was in a separate PR to the introduction of the control plane template.
Also, before we merge will you be able to squash your commits so they tell a store. Perhaps into 2 commits: 1 for the API version bump and 1 for the control plane template.
@@ -0,0 +1,71 @@ | |||
/* | |||
Copyright 2020 The Kubernetes Authors. |
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.
nit: as its a new file maybe 2024 would be better?
|
||
// KThreesConfigTemplateSpec defines the desired state of KThreesConfigTemplate. | ||
type KThreesConfigTemplateSpec struct { | ||
// INSERT ADDITIONAL SPEC FIELDS - desired state of cluster |
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.
We can probably remove this autogenerated comment
g.Expect(AddToScheme(scheme)).To(Succeed()) | ||
g.Expect(cabp3v1.AddToScheme(scheme)).To(Succeed()) | ||
|
||
t.Run("for KThreesConfig", utilconversion.FuzzTestFunc(utilconversion.FuzzTestFuncInput{ |
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.
nit:
t.Run("for KThreesConfig", utilconversion.FuzzTestFunc(utilconversion.FuzzTestFuncInput{ | |
t.Run("for KThreesControlPlane", utilconversion.FuzzTestFunc(utilconversion.FuzzTestFuncInput{ |
@@ -0,0 +1,130 @@ | |||
/* | |||
Copyright 2020 The Kubernetes Authors. |
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.
Copyright 2020 The Kubernetes Authors. | |
Copyright 2024 The Kubernetes Authors. |
I did not see this PR coming, sorry for that and thank you for the review. |
@anmazzotti what is the status here? Are you waiting for my review? |
Affirmative. |
Also please do not release after this is merged. I have a follow up PR to remove the |
29d8ae4
to
9badbb7
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.
This is looking good @anmazzotti. Great work.
Just a couple of things:
- Could you confirm what manual testing you have done with the new control plane template?
- Could you squash the commits so they tell a story?
Thank you. I'll squash two commits to highlight the new version being added and the KThreesControlPlaneTemplate addition too. I think those two are the most important features for this PR, rest is scaffolding. |
Sounds good to me 👍 |
9badbb7
to
4fe6c8a
Compare
I see there are thousands of new files in vendor folder, do we need check in this folder? |
4fe6c8a
to
b2841f1
Compare
b74ef2d
to
5b87294
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
@anmazzotti would you please resolve conflicts? |
5b87294
to
979c577
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.
@anmazzotti - would you be able to squash the commits so they tell a story?
Apart from squashing the commits i think this is good to go from my side.
Signed-off-by: Andrea Mazzotti <[email protected]>
1db1973
to
1e126bb
Compare
@anmazzotti would you mind adding a e2e test case to cover clusterclass? |
This should be part of #62
The main focus of this PR is to enable Cluster Classes.
The KThreesControlPlaneTemplateSpec was introduced for this very reason.
Changes to the existing KThreesControlPlaneMachineTemplate are also required for the correct reconciliation of the Cluster topology.
Still in draft as I'm testing if everything still works.
I am not sure whether this will introduce backward compatibility, probably yes since the API changed, however I am not sure how else this could be implemented differently.