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

Sample cloud-config master.yaml has wrong kube-apiserver options #10467

Closed
chiefy opened this issue Jun 28, 2015 · 6 comments
Closed

Sample cloud-config master.yaml has wrong kube-apiserver options #10467

chiefy opened this issue Jun 28, 2015 · 6 comments
Labels
area/os/coreos priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@chiefy
Copy link
Contributor

chiefy commented Jun 28, 2015

the --service-cluster-ip-range option results in this:

$ ./kube-apiserver --insecure-bind-address=0.0.0.0 --service-cluster-ip-range=10.100.0.0/16 --etcd-servers=http://localhost:2379
unknown flag: --service-cluster-ip-range
Usage of ./kube-apiserver:
...
$ ./kube-apiserver --version 
Kubernetes v0.17.0
@roberthbailey
Copy link
Contributor

This flag used to be called --portal_net. See #8740.

@roberthbailey roberthbailey added kind/support Categorizes issue or PR as a support question. team/cluster labels Jun 29, 2015
@roberthbailey
Copy link
Contributor

It was changed with release 0.18.0 (see the release notes).

@roberthbailey roberthbailey self-assigned this Jun 29, 2015
@chiefy
Copy link
Contributor Author

chiefy commented Jun 29, 2015

Ok, still seems like an issue since the master.yaml is pulling down version 0.17.0 binaries and using 0.18.0 options?

@roberthbailey
Copy link
Contributor

Yes, that seems like a bug. Are you interested in updating the configs to use a more recent release?

@roberthbailey roberthbailey added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. area/os/coreos area/platform/aws priority/backlog Higher priority than priority/awaiting-more-evidence. and removed team/cluster kind/support Categorizes issue or PR as a support question. labels Jun 30, 2015
@roberthbailey roberthbailey removed their assignment Jun 30, 2015
@chiefy
Copy link
Contributor Author

chiefy commented Jun 30, 2015

@roberthbailey yeah, I actually got them working with my terraform based project. I will fork + PR.

@roberthbailey
Copy link
Contributor

Thanks! I'd much rather see the configs catch up to a newer kubernetes version that keep old flags around.

@chiefy chiefy mentioned this issue Jun 30, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/os/coreos priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chiefy @roberthbailey