From 32689a0dfc5b40814bcb7eba99c57d78881b70cb Mon Sep 17 00:00:00 2001 From: wangxy518 <40482095+wangxy518@users.noreply.github.com> Date: Tue, 15 Dec 2020 18:15:34 +0800 Subject: [PATCH] Update kubernetes-on-vsphere-with-helm.md --- docs/book/tutorials/kubernetes-on-vsphere-with-helm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/book/tutorials/kubernetes-on-vsphere-with-helm.md b/docs/book/tutorials/kubernetes-on-vsphere-with-helm.md index adb18e549..2987bbbf9 100644 --- a/docs/book/tutorials/kubernetes-on-vsphere-with-helm.md +++ b/docs/book/tutorials/kubernetes-on-vsphere-with-helm.md @@ -152,7 +152,7 @@ The CPI supports storing vCenter credentials either in: In the example `vsphere.conf` above, there are two configured [Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets). The vCenter at `10.0.0.1` contains credentials in the secret named `cpi-engineering-secret` in the namespace `kube-system` and the vCenter at `1.1.1.1` and `192.168.0.1` contains credentials in the secret named `cpi-global-secret` in the namespace `kube-system` defined in the `[Global]` section. -An example [Secrets YAML](https://github.com/kubernetes/cloud-provider-vsphere/raw/master/manifests/controller-manager/vccm-secret.yaml) can be used for reference when creating your own `secrets`. If the example secret YAML is used, update the secret name to use a ``, the vCenter IP address in the keys of `stringData`, and the `username` and `password` for each key. +An example [Secrets YAML](https://raw.githubusercontent.com/kubernetes/cloud-provider-vsphere/master/manifests/controller-manager/vccm-secret.yaml) can be used for reference when creating your own `secrets`. If the example secret YAML is used, update the secret name to use a ``, the vCenter IP address in the keys of `stringData`, and the `username` and `password` for each key. The secret for the vCenter at `1.1.1.1` might look like the following: