From 1852fab029f3e46295776d1a7e08d9f8ca0a1b83 Mon Sep 17 00:00:00 2001 From: Justin Santa Barbara Date: Fri, 12 Feb 2016 09:27:39 -0500 Subject: [PATCH] AWS: Fix kube-up generation of kubeconfig We were assuming the PROJECT env var was set, which the e2e tests do. But PROJECT is normally not set on AWS (it is set on GCE); this broke as part of the harmonization. Revert to the pre-existing behaviour here, where we use "aws_" as the prefix. Fix #21141 --- cluster/aws/util.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster/aws/util.sh b/cluster/aws/util.sh index 3a18e744a2f..049b3a48dec 100755 --- a/cluster/aws/util.sh +++ b/cluster/aws/util.sh @@ -1155,7 +1155,7 @@ function build-config() { export KUBE_CERT="${CERT_DIR}/pki/issued/kubecfg.crt" export KUBE_KEY="${CERT_DIR}/pki/private/kubecfg.key" export CA_CERT="${CERT_DIR}/pki/ca.crt" - export CONTEXT="${PROJECT}_${INSTANCE_PREFIX}" + export CONTEXT="aws_${INSTANCE_PREFIX}" ( umask 077 create-kubeconfig