We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github: rancher/vsphere-charts#83
Hi team, When it comes to set up the Out-of-three provider Vsphere, the instrucstion are detailed here: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/configure-out-of-tree-vsphere.- However, based on this comment, rancher/vsphere-charts#83 (comment) "It is not supported to install the vsphere CPI or CSI into RKE2 via the app catalog..If provisioning RKE2 via Rancher, you should select the vsphere cloud provider when provisioning the cluster. This will automatically install the vsphere cpi and csi charts into the downstream cluster, as part of cluster provisioning.
Should we include this? Regards
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Related Issues
Github: rancher/vsphere-charts#83
Summary
Hi team,
When it comes to set up the Out-of-three provider Vsphere, the instrucstion are detailed here: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/configure-out-of-tree-vsphere.- However, based on this comment, rancher/vsphere-charts#83 (comment)
"It is not supported to install the vsphere CPI or CSI into RKE2 via the app catalog..If provisioning RKE2 via Rancher, you should select the vsphere cloud provider when provisioning the cluster. This will automatically install the vsphere cpi and csi charts into the downstream cluster, as part of cluster provisioning.
Should we include this?
Regards
The text was updated successfully, but these errors were encountered: