-
Notifications
You must be signed in to change notification settings - Fork 539
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
Make subnet spec id field required for SSA to work with CC #3748
Changes from all commits
14109e7
1bc6ce8
55a78fa
342dd42
39f088b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
- op: add | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So... (and this is probably my lack of knowledge in this area, but please bear with me) The way these different from currently configurable networking, like just plain adding your VPC ID into the cluster config, is that these values will now be managed fields and used in SSA. So the user doesn't have to change things in a config file but rather apply new patch values? Did I get that right? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, this particular scenario tests BYO VPC and subnets which was not working before SSA and id field being compulsory. |
||
path: /spec/topology/variables/- | ||
value: | ||
name: byoInfra | ||
value: "true" | ||
- op: add | ||
path: /spec/topology/variables/- | ||
value: | ||
name: vpcID | ||
value: "${BYO_VPC_ID}" | ||
- op: add | ||
path: /spec/topology/variables/- | ||
value: | ||
name: publicSubnetID | ||
value: "${BYO_PUBLIC_SUBNET_ID}" | ||
- op: add | ||
path: /spec/topology/variables/- | ||
value: | ||
name: privateSubnetID | ||
value: "${BYO_PRIVATE_SUBNET_ID}" | ||
- op: add | ||
path: /spec/topology/variables/- | ||
value: | ||
name: fdForBYOSubnets | ||
value: "us-west-2a" | ||
- op: replace | ||
path: /spec/topology/workers/machineDeployments/0/failureDomain | ||
value: "us-west-2a" |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
bases: | ||
- ../topology/cluster-template.yaml | ||
|
||
patches: | ||
- path: ./byo-infra-variables.yaml | ||
target: | ||
group: cluster.x-k8s.io | ||
version: v1beta1 | ||
kind: Cluster | ||
- path: ./limited-az-variable.yaml | ||
target: | ||
group: cluster.x-k8s.io | ||
version: v1beta1 | ||
kind: Cluster | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
- op: add | ||
path: /spec/topology/variables/- | ||
value: | ||
name: vpcAZUsageLimit | ||
value: "1" |
This file was deleted.
This file was deleted.
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, what happens in case of existing clusters is that their ID will be set to a default empty string, right?
Does that affect the cluster at all?
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 means if a subnet spec is defined, it should have the id field.
Making id a unique identifier solves SSA coauthoring issue. More info in the CAPI issue.
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.
kubernetes-sigs/cluster-api#6320
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.
Yeah, I saw this one. Just was wondering about existing configs since now it will not just omit the value but update it to an empty string.
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.
For existing configs (by this I mean existing clusters), even though initially id field was empty, after the creation, ids are filled by CAPA controllers, so no existing cluster should have their id fields empty during upgrading to v1beta2.
If you are asking about using an existing template, they will no longer work for creating new clusters.
This is a breaking change for existing templates that use the unsupported use cases and the reason why we needed a new API version is because of this. We will need to document this properly with the v1beta2 release.