Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AWS kube-up bug: PROJECT unbound variable #21141

Closed
justinsb opened this issue Feb 12, 2016 · 0 comments · Fixed by #21144
Closed

AWS kube-up bug: PROJECT unbound variable #21141

justinsb opened this issue Feb 12, 2016 · 0 comments · Fixed by #21144
Assignees
@justinsb
Milestone
v1.2

Comments

@justinsb
Copy link
Member 

cluster/../cluster/../cluster/aws/util.sh: line 1158: PROJECT: unbound variable
@justinsb justinsb added this to the v1.2 milestone Feb 12, 2016
@justinsb justinsb self-assigned this Feb 12, 2016
justinsb added a commit to justinsb/kubernetes that referenced this issue Feb 12, 2016
@justinsb
AWS: Fix kube-up generation of kubeconfig
1852fab 
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 kubernetes#21141
@justinsb justinsb mentioned this issue Feb 12, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinsb justinsb

Labels
None yet
Projects
None yet
Milestone
v1.2
Development

Successfully merging a pull request may close this issue.

AWS: Fix kube-up generation of kubeconfig justinsb/kubernetes
2 participants
@justinsb @mikedanese