What is the correct way to install add-ons using Kubernetes 1.1?

What is the correct way to install addons using Kubernetes 1.1? docs are not as clear as we would like on this topic; they seem to imply that you need to copy the yaml addon files to / etc / kubernetes / addon on the main nodes, but I tried this and nothing happens.

In addition, to add confusion to the documents, it is understood that add-ons are related to Kubernetes:

Thus, the only permanent way to make changes to add-ons is to update the manifest on the main server. Nevertheless, users are not recommended to do this on their own - they should rather wait for the new version of Kubernetes, which will also contain new versions of add-ons.

So, how should I really install add-ons, f.ex. cluster-loadbalancing , with Kubernetes 1.1?

+5
source share
1 answer

... they seem to imply that you need to copy the yaml addons files to / etc / kubernetes / addon on the main nodes, but I tried this and nothing happens.

This is true only if you use one of the salt-based installation mechanisms.

So, how should I really install add-ons, f.ex. cluster-loadbalancing, with Kubernetes 1.1?

Most add-ins can be installed by simply running kubectl create -f against the replication controller and utility files for the add-in. First you need to create a kube-system namespace if you haven’t already done so, and some of the add-ons (like dns ) require you to fill in a few values ​​in the jinja template, which would otherwise be processed by salt.

+3
source

Source: https://habr.com/ru/post/1245328/


All Articles