https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
b
I assume you already tried the same way
Copy code
k scale deploy rancher -n cattle-system --replicas=1
a
What kind of cluster is Rancher installed on? You could log onto one of the nodes, run kubectl locally (I assume the kubeconfig you're current using is pointing to the rancher auth proxy) and then scale up the deployment
e
@agreeable-oil-87482 Cluster is setup using the cluster.yaml file and imported into the cluster...
a
so you ran 
rke up
?
e
It was not me, but yes...
a
Running that will generate a kubeconfig that will auth to the apiserver of that cluster directly. Use that to increase the deployment replica count
e
how do I do that exactly?
rke config
you mean?
a
Do you have the kubeconfig that was generated by 
rke up
?
e
Yes, I do see the kubeconfig file inside that directory...
a
point kubectl to that file - can you get a list of Pods?
e
Thank you so much, you saved my day... 8-)
❤️
a
No worries 👍
e
I ran the scale command but it didn't fix the problem, it needs some time maybe?
a
It'll take some time for the Rancher pod to spin up
k get po -n cattle-system
- what does it list?
e
Yeah, it needed some time, the web UI is back...
Thank you very much one more time... ❤️
a
Pods will have spun up but wouldn't have passed the readiness probe yet.
You're welcome
e
@agreeable-oil-87482 The reason why I ran the command is because I have a node in 
Removing
state...
Can you help with that too?..
a
In a downstream cluster?
e
Yes, the cluster is a 
custom
type cluster....
The rancher version is v2.6.2
And the node says "Removing, resources scheduled for deletion"...
But it has been more 4 hours now...
a
Which method did you use to delete the node? Ie from the rancher UI?
e
Yes, from the rancher UI...
When it got stuck I went to the kubectl and removed the node from there...
a
Is anything running on the node?
e
Now the cluster doesn't see the node but it's listed in the UI...
No, it was a clean system...
actually the cluster itself is a clean cluster, I just installed longhorn today and that's it...
But that node didn't join the longhorn installation...
a
How many nodes in the cluster and which role(s) does that node have? And in 
kubectl get no
it's not listed anymore?
e
yes, 
k get no
doesn't list the node, it was a regular worker node...
The cluster has 3 masters and 5 workers, this node was called 
kub-dev-worker01
...
a
Rancher > Cluster > Nodes > Edit YAML for the node that's supposed to be removed and delete any 
finalizers
e
I am getting 404 page not found when trying to save the file...
a
ctrl+f5 the page - is it still there?
e
I tried refreshing, it's still there, yes...
a
<https://<your-rancher-url>/dashboard/c/local/explorer/management.cattle.io.node> - is it listed here?
e
Yes, it's there...
a
Try deleting it from there using the three dots. If that fails, edit its yaml and delete the finalizers from there.
e
I tried deleting from there, no luck...
I tried editing the yaml but it's not an option...Only the View option is available...
a
Ah ok. In your rancher management cluster:
Copy code
kubectl get <http://node.management.cattle.io|node.management.cattle.io> -A
Then edit one, ie:
Copy code
kubectl edit <http://node.management.cattle.io|node.management.cattle.io> machine-fncw4 -n c-m-9q4wfk4z
And remove the finalizers
e
Awesome, it got disappeared now... 8-)
You are great, I can't explain how thankful I am...
❤️
a
No problem at all 👍
2 Views
Open in Slack
PreviousNext
Powered by