2017-04-20 284 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