feat(rancher): AWS - Variable to adjust security group ingress cidr #246
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Default for backwards compatibility 0.0.0.0/0, but recommended to lock down public access to a single ip address or a limited range. Additional change in K3s installation: Advertise kube apiserver on internal ip (advertise-address), allow access in addition through public ip (tls-san).
wombelix
changed the title
|
Requires one more adjustment: The workload cluster tries to reach Rancher through the public fqdn, working on it. |
…e on private ip inside vpc Rancher URL is set to a public reachable FQDN based on sslip.io. The workload cluster tries to reach and join Rancher through that public IP. In cases were the ingress CIDR is not 0.0.0.0/0 (recommended), downstream cluster need a way to reach Rancher through the private IP. This is achieved with a split-horizon DNS setup that maps the Rancher FQDN to a private ip inside the VPC.
|
Problem addressed with 289682f and successfully tested. |
wombelix
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Default for backwards compatibility 0.0.0.0/0, but recommended to lock down public access to a single ip address or a limited range.
Additional change in K3s installation: Advertise kube apiserver on internal ip (advertise-address), allow access in addition through public ip (tls-san).
This PR improves security by advertising kube apiserver on the internal ip and allowing narrowed down ingress rules. Result is a security group that allows self access and from the CIDR defined in variable
security_group_ingress_cidr.