Updated 10. Setting the solution up in AKS (Azure Kubernetes Service) (markdown)

Cesar De la Torre 2018-05-19 16:01:52 -07:00
parent e28285ddad
commit 4169f284d4

@ -148,18 +148,6 @@ So when you use `kubectl`, it'll be managing that particular cluster:
![image](https://user-images.githubusercontent.com/1712635/40208942-49195356-59f1-11e8-968d-8450b1b67739.png) ![image](https://user-images.githubusercontent.com/1712635/40208942-49195356-59f1-11e8-968d-8450b1b67739.png)
Now, you can also manually run the Kubernetes proxy with:
>```
>kubectl proxy
>```
So when you open the Kubernetes dashboard it'll be targeting the right cluster, too, when typeing the following URL into the browser:
>```
>URL: http://localhost:8001/#!/cluster
>```
![image](https://user-images.githubusercontent.com/1712635/40209200-cc1390e0-59f2-11e8-816d-eec1d01359ca.png)
## Important: Store your credentials/secrets for Kubernetes and ACR in a safe place! ## Important: Store your credentials/secrets for Kubernetes and ACR in a safe place!