-
Notifications
You must be signed in to change notification settings - Fork 2
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
Flexible subnet configuration #196
Conversation
Signed-off-by: Marcus Noble <[email protected]>
Skipping CI for Draft Pull Request. |
Signed-off-by: Marcus Noble <[email protected]>
2673fb1
to
f479ac0
Compare
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
helm/cluster-aws/values.yaml
Outdated
availabilityZone: c | ||
isPublic: true | ||
tags: | ||
subnet.giantswarm.io/role: bastion |
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.
having 3 subnets for 1 bastion might be overkill tho :p
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, until an AZ is having issues :p
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.
still, its a lot of IP wasted, we should put bastions on the smallest possible subnet size which is /28 if I remember correctly
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, the default split still needs some work, there's a LOT of wasted IPs in this but for now it's just an example to get things working.
could you post here some AWSCluster part where the subnets are generated from the config? Should we also put a comment on that section that it should not by changed unless someone knows exactly what they are doing? I can see customer breaking it |
@calvix Here's an example of an public AWSCluster created using these default values:
The tags you see are the final set of tags after CAPA has added it's own default tags to the user provided tags. |
ac30c7b
to
14eb753
Compare
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
14eb753
to
cf45657
Compare
…cluster-aws into flexible_subnets_alternative
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
4d7a52f
to
575c6c9
Compare
/test create |
ToDo on Monday
|
Notes on private cluster upgrades to this versionWhen upgrading a private cluster, following the migration steps, the upgrade works as expected providing no changes are made to the CIDR blocks. |
|
Signed-off-by: Marcus Noble <[email protected]>
Signed-off-by: Marcus Noble <[email protected]>
/rest create |
/test create |
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.
changes LGTM, but I feel we need some kind of documentation for this, could we have an example of how to dot the complex subnets in the Readme or some docs/separate-subnets.MC
?
Adds the ability to have more complex subnet layouts and the ability to target which subnets to use for different groups of resources.
Note: This is a breaking change for existing private clusters and will require a change to the provided values. An entry in the changelog and readme have been added with the required details.
Checklist