From a167a90f8075b8f0fe8d33657902b56c68a90b1c Mon Sep 17 00:00:00 2001 From: Zach Loafman Date: Mon, 29 Aug 2016 19:12:16 -0700 Subject: [PATCH] AWS: Fix unbound SSH_CIDR Another e2e bug, this one injected by https://github.com/kubernetes/kubernetes/pull/27061 --- cluster/aws/config-test.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cluster/aws/config-test.sh b/cluster/aws/config-test.sh index 5e7b746cc5c..107264e0a21 100755 --- a/cluster/aws/config-test.sh +++ b/cluster/aws/config-test.sh @@ -78,6 +78,8 @@ NON_MASQUERADE_CIDR="${NON_MASQUERADE_CIDR:-10.0.0.0/8}" # Traffic to IPs outsid SERVICE_CLUSTER_IP_RANGE="${SERVICE_CLUSTER_IP_RANGE:-10.0.0.0/16}" # formerly PORTAL_NET CLUSTER_IP_RANGE="${CLUSTER_IP_RANGE:-10.245.0.0/16}" MASTER_IP_RANGE="${MASTER_IP_RANGE:-10.246.0.0/24}" +SSH_CIDR="${SSH_CIDR:-0.0.0.0/0}" # IP to restrict ssh access to nodes/master +HTTP_API_CIDR="${HTTP_API_CIDR:-0.0.0.0/0}" # IP to restrict HTTP API access # If set to an Elastic IP address, the master instance will be associated with this IP. # Otherwise a new Elastic IP will be acquired # (We used to accept 'auto' to mean 'allocate elastic ip', but that is now the default)