2017-04-20 263 views

回答

1

該插件管理器部署爲普通的pod或部署,使用簡單kubectl apply -f

YAML的看起來是這樣的,看你需要特定版本:

apiVersion: v1 kind: Pod metadata: name: kube-addon-manager namespace: kube-system labels: component: kube-addon-manager spec: hostNetwork: true containers: - name: kube-addon-manager # When updating version also bump it in: # - cluster/images/hyperkube/static-pods/addon-manager-singlenode.json # - cluster/images/hyperkube/static-pods/addon-manager-multinode.json # - test/kubemark/resources/manifests/kube-addon-manager.yaml image: gcr.io/google-containers/kube-addon-manager:v6.4-beta.1 command: - /bin/bash - -c - /opt/kube-addons.sh 1>>/var/log/kube-addon-manager.log 2>&1 resources: requests: cpu: 5m memory: 50Mi volumeMounts: - mountPath: /etc/kubernetes/ name: addons readOnly: true - mountPath: /var/log name: varlog readOnly: false volumes: - hostPath: path: /etc/kubernetes/ name: addons - hostPath: path: /var/log name: varlog

的附加組件管理器觀察/etc/kubernetes/addons/根據具體YAML文件,把你喜歡這裏安裝任何插件。

+0

謝謝!與直接安裝插件相比,插件管理器帶來哪些好處? – aknuds1

+0

插件是集羣的一部分,並將文件部署到主機中可簡化與任何配置管理器的集成。但更有趣的是,它確保了文件的狀態與羣集中的狀態。因此,在RBAC之前,如果用戶修改了dns等,插件管理器將基於本地文件系統恢復描述。 – Pegerto