kops create cluster \
--cloud "aws" \
--zones "us-west-2a" \
--networking "kopeio-vxlan" \
--vpc "vpc-dd775bba" \
--node-security-groups "sg-36822b4d" \
--ssh-public-key=./ssh/olalonde.pub \
--name "staging.mydomain.com" \
2> /dev/null || true
Previewing changes that will be made:
*********************************************************************************
A new kubernetes version is available: 1.5.4
Upgrading is recommended (try kops upgrade cluster)
More information: https://github.com/kubernetes/kops/blob/master/permalinks/upgrade_k8s.md#1.5.4
*********************************************************************************
...
$ kops version
Version 1.5.3 (git-46364f6)
I can replicate this.
@olalonde could you re-run your command with -v=10 to get debug information and post the result?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Most helpful comment
I can replicate this.