Updated 10. Setting the solution up in AKS (Azure Kubernetes Service) (markdown)
parent
e28285ddad
commit
4169f284d4
@ -148,18 +148,6 @@ So when you use `kubectl`, it'll be managing that particular cluster:
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
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
|
|
||||||
>```
|
|
||||||

|
|
||||||
|
|
||||||
|
|
||||||
## 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!
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user