-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Files ending in .yaml seem to now end in .manifest #126
Comments
Hi @micah, which tool you're using to install Kubernetes? That might affect what the files are called and where they are installed to. You can simply modify the config files yourself to suit your system, but I'm interested to know what installer you're using in case it's something we should consider providing an option for. |
Hi @micah, which tool you're using to install Kubernetes? That might
affect what the files are called and where they are installed to.
I used kubespray. I was unsure why they were called this, and thought
perhaps it was a 1.9 change.
You can simply modify the config files yourself to suit your system,
but I'm interested to know what installer you're using in case it's
something we should consider providing an option for.
I'm guessing it might be something worth considering, since kubespray is
an incubator project, and a fairly popular mechanism for installing!
…--
micah
|
Same thing in kops - e.g. https://github.com/kubernetes/kops/blob/master/nodeup/pkg/model/kube_apiserver.go#L88 |
Closing as the .manifest files are now included in the config file. Please re-open if you still see a problem |
In 1.9, I'm told things like this:
1.1.1 Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the below parameter.
but it seems like the files all end with .manifest instead of .yaml, perhaps this is a 1.9 change?
The text was updated successfully, but these errors were encountered: