mirror of https://github.com/docker/docs.git
Add install Helm on Docker EE section
Signed-off-by: Traci Morrison <traci.morrison@docker.com>
This commit is contained in:
parent
0e8bcfc90b
commit
5ea0367863
|
|
@ -4,7 +4,7 @@ description: Learn how to install kubectl, the Kubernetes command-line tool, on
|
|||
keywords: ucp, cli, administration, kubectl, Kubernetes
|
||||
---
|
||||
|
||||
Docker EE 2.0 and higher deploys Kubernetes as part of a UCP installation.
|
||||
Docker Enterprise 2.0 and higher deploys Kubernetes as part of a UCP installation.
|
||||
Deploy, manage, and monitor Kubernetes workloads from the UCP dashboard. Users can
|
||||
also interact with the Kubernetes deployment through the Kubernetes
|
||||
command-line tool named kubectl.
|
||||
|
|
@ -29,9 +29,9 @@ To use kubectl, install the binary on a workstation which has access to your UCP
|
|||
{: .important}
|
||||
|
||||
First, find which version of Kubernetes is running in your cluster. This can be found
|
||||
within the Universal Control Plane dashboard or at the UCP API endpoint [version](/reference/ucp/3.2/api/).
|
||||
within the Universal Control Plane dashboard or at the UCP API endpoint [version](/reference/ucp/3.2/api/). You can also find the Kubernetes version using the Docker CLI. You need to source a client bundle and type the `docker version` command.
|
||||
|
||||
From the UCP dashboard, click on **About Docker EE** within the **Admin** menu in the top left corner
|
||||
From the UCP dashboard, click **About** within the **Admin** menu in the top left corner
|
||||
of the dashboard. Then navigate to **Kubernetes**.
|
||||
|
||||
{: .with-border}
|
||||
|
|
@ -91,14 +91,31 @@ curl https://storage.googleapis.com/kubernetes-release/release/$env:k8sversion/b
|
|||
</div>
|
||||
</div>
|
||||
|
||||
## Using kubectl with a Docker EE cluster
|
||||
## Using kubectl with a Docker Enterprise cluster
|
||||
|
||||
Docker Enterprise Edition provides users unique certificates and keys to authenticate against
|
||||
Docker Enterprise provides users unique certificates and keys to authenticate against
|
||||
the Docker and Kubernetes APIs. Instructions on how to download these certificates and how to
|
||||
configure kubectl to use them can be found in [CLI-based access.](cli.md#download-client-certificates)
|
||||
|
||||
## Install Helm on Docker Enterprise
|
||||
|
||||
Helm is the package manager for Kubernetes. Tiller is the Helm server. Before installing Helm on Docker Enterprise, you must meet the following requirements:
|
||||
|
||||
* You must be running a Docker Enterprise 2.1 or higher cluster.
|
||||
* You must have kubectl configured to communicate with the cluster (usually this is done via a client bundle).
|
||||
|
||||
To use Helm and Tiller with UCP, you must grant the default service account within the kube-system namespace the necessary roles. Enter the following kubectl commands in this order:
|
||||
|
||||
```bash
|
||||
kubectl create rolebinding default-view --clusterrole=view --serviceaccount=kube-system:default --namespace=kube-system
|
||||
|
||||
kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
|
||||
```
|
||||
It is recommended that you specify a Role and RoleBinding to limit Tiller’s scope to a particular namespace, as described in [Helm’s documentation](https://helm.sh/docs/using_helm/#example-deploy-tiller-in-a-namespace-restricted-to-deploying-resources-only-in-that-namespace).
|
||||
|
||||
See [initialize Helm and install Tiller](https://helm.sh/docs/using_helm/#initialize-helm-and-install-tiller) for more information.
|
||||
|
||||
## Where to go next
|
||||
|
||||
- [Deploy a workload to a Kubernetes cluster](../kubernetes.md)
|
||||
- [Deploy to Kubernetes on Docker Desktop for Mac](/docker-for-mac/kubernetes.md)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue