mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-07 12:11:43 +00:00
Optionally associate master instance with AWS Elastic IP
When MASTER_RESERVED_IP is set to elastic IP from AWS, then aws/util.sh will associate it with master instance and assign it to KUBE_MASTER_IP. If no MASTER_RESERVED_IP is set, new elastic ip will be requested from amazon. This allows cluster certificates to be generated for an IP that doesn't change between stopping & starting cluster instances. The requested elastic ip is not released when kube-down.sh is run. I think it is good because user could have created DNS records and it would be bad if the IP was removed. He can reuse it next time through MASTER_RESERVED_IP when setting up cluster again.
This commit is contained in:
@@ -43,7 +43,9 @@ MINION_SCOPES=""
|
||||
POLL_SLEEP_INTERVAL=3
|
||||
PORTAL_NET="10.0.0.0/16"
|
||||
MASTER_IP_RANGE="${MASTER_IP_RANGE:-10.246.0.0/24}"
|
||||
|
||||
# If set to Elastic IP, master instance will be associated with this IP.
|
||||
# Otherwise new Elastic IP will be aquired
|
||||
MASTER_RESERVED_IP="${MASTER_RESERVED_IP:-}"
|
||||
|
||||
# When set to true, Docker Cache is enabled by default as part of the cluster bring up.
|
||||
ENABLE_DOCKER_REGISTRY_CACHE=true
|
||||
|
Reference in New Issue
Block a user