Skip to content
New issue

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

Cloud Provider choice does not install cloud provider onto cluster #12

Open
bcdurden opened this issue Aug 3, 2022 · 3 comments
Open

Comments

@bcdurden
Copy link

bcdurden commented Aug 3, 2022

Problem

Working with Harvester templates specifically I noticed that despite choosing harvester in the cloudprovider field, that the cloud provider itself was not provisioned in the cluster.

Expected Behavior

When choosing 'harvester' as the cloudprovider, the corresponding cloud provider configuration is dropped into the resulting Cluster manifest.

What Happens

The cluster is provisioned with Harvester as a node driver but does not include the needed inline kubeconfig file entry under `spec.rkeConfig.machineSelectorConfig[]'.

Desired Fix

I suspect this is difficult to fix as it sits in that acquiring the kubeconfig requires a reference to an existing secret before injecting the contents into a yaml file. Since I can't use kubectl explain to trapse the internal Cluster object docs (they are empty), I am uncertain if there is a secretRef option as opposed to an inline definition.

The other option is keeping the kubeconfig in the values.yaml file, but that presents problems with unencrypted secrets and could not be stored in a code repo without aid of something like SOPs or external secrets, etc.

However, instructions on how to manually inject this would be useful or at least highlighting it as a need.

@shrapk2
Copy link

shrapk2 commented Sep 6, 2023

Did you find a solve for this? I'm having a similar issue with the Harvester CSI driver. Works via the UI, but not through the Helm template...

@staedter
Copy link

staedter commented Feb 1, 2024

I have found a workaround for that bug. I also opened an issue for in the harvester repo, but one developer said my workaround was already pretty good and they are not planning on fixing this and that not using Helm instead of the GUI with Cluster-Templates is an advanced use case that is not officially supported e.g. you are on your own trying to make it work.

You can see my workaround in the issue I mentioned here harvester/harvester#4568

@bcdurden
Copy link
Author

bcdurden commented Feb 2, 2024

I feel this repo is pretty dead. We've pulled it in over at RGS and have been curating it here: https://github.com/rancherfederal/rancher-cluster-templates

Most of it has been rewritten but substantial fixes have already been implemented, Harvester CSI driver works great (although you have to include/generate a kubeconfig for it to work).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants