This message was deleted.
# general
a
This message was deleted.
c
you need to put a manifest to deploy the digital ocean cloud provider in the additional manifests section. the “cloud provider config” section is only for if you’re using a built-in cloud provider.
if you don’t want to deploy it as an additional manifest, you’ll need to log in to one of the server nodes and deploy the cloud provider manually
a
Thanks for your reply! I almost gave up 😬 .. I just found a post here on slack of someone else posting a similar solution, but it doesn’t seem to have an effect. I would like to try and apply it manually to see if that works, but I don’t know how to apply that. There is no
kubectl
c
there is, you just need to put it in your path
💯 1
export
PATH=$PATH:/var/lib/rancher/rke2/bin/ KUBECONFIG=/etc/rancher/rke2/rke2.yaml
If you have a manifest that you can apply with kubectl, its probably easier to just paste that in to the rancher UI though, and let the installer handle it for you
a
That’s what I did. No success 😕
c
where in the UI did you put it
a
In the
Add-on Config
section
c
Down at the bottom, under Additional Manifest?
a
Yes
c
That should be the correct place for it.
Did you put it there when you originally created the cluster, or did you add it after the fact?
a
Before. Fresh cluster
c
Hmm. You might check the logs on the server nodes to see if there were any errors deploying the manifest
or if it did get deployed, see if there are errors in the pod logs
a
I just tried
kubectl get nodes
on one of the nodes but getting
The connection to the server localhost:8080 was refused - did you specify the right host or port?
c
sounds like you didn’t export the kubeconfig path as I suggested up above
a
you’re right 😅
Ah it seems to have applied the config
Thanks for the help @creamy-pencil-82913. This will help me on my way. #LifeSaver
c
CreateContainerConfigError looks wrong though
suggests something in your manifest is invalid
a
Yeah I checked the logs. I’m missing a secret 🤓
c
👍