Skip to content

Commit b699826

Browse files
author
Matthew
committed
docs(installing-deis): add helm target usage
1 parent 74b3c7a commit b699826

1 file changed

Lines changed: 11 additions & 2 deletions

File tree

docs/src/installing-deis/installing-the-deis-platform.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,17 @@ First check that you have `helm` installed and the version is correct.
1010

1111
Ensure your kubectl client is installed and ensure it can connect to your kubernetes cluster. This
1212
is where `helm` will attempt to communicate with the cluster. You can test that it is working
13-
properly by running `kubectl get nodes`. If you see a list of available nodes, kubectl is
14-
communicating with the kubernetes master.
13+
properly by running
14+
15+
$ helm target
16+
Kubernetes master is running at https://10.245.1.2
17+
Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster
18+
KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns
19+
KubeUI is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-ui
20+
Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
21+
InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
22+
23+
If you see a list of targets like the one above, helm can communicate with the kubernetes master.
1524

1625
Once finished, run this command to provision the Deis platform:
1726

0 commit comments

Comments
 (0)