https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
w
p
Yes but this part I don't fully understand
Copy code
# depend on kubectl to operate the Harvester cluster
./deploy/generate_addon.sh <serviceaccount name> <namespace>
Where is someone supposed to run that
w
Yes it could be clearer - I think wherever you have kubectl command and Harvester kubeconfig file. One of comments in issue 1812 (about halfway down) includes "6. Download the Generate addon configuration for cloud provider 7. Download Harvester kubeconfig and add into your local ~/.kube/config file 8. Generate K3s kubeconfig by running generate addon script 
./deploy/generate_addon.sh <k3s cluster name> <namespace>
e.g 
./generate_addon.sh k3s-focal-cloud-provider default
9. Copy the kubeconfig content 10. ssh to K3s VM 11. Add kubeconfig content to 
/etc/kubernetes/cloud-config
file, remember to align the yaml layout"
p
Wait how would that work when the cluster doesn't allow external
Copy code
certificate is not valid for any names, but wanted to match <http://my.harvester.domain.com|my.harvester.domain.com>
Oh grab the kubeconfig from rancher and not harvester
@witty-jelly-95845 Now how do I provide our internal SSL certs to the helm chart
I think it might be because we have rancher behind an ingress maybe?
Ok I figured it out. Have to run it from the harvester node and give it the port forwarded connection
🙌 1
And now I'm getting x509 unknown authority issues
w
Sorry I've not tried this - perhaps log an issue referencing 1812?
31 Views
Open in Slack
PreviousNext
Powered by