@@lele-tz1uz op is asking if this is a comparable tool to lens or the other dashes. its not. you wouldn't deploy a full rancher to manage a non-rancher cluster. you can say the same for EKS, there are ways to add non-EKS clusters, but there's really no point if all you want is a UI.
Used K8S for quite some time even in my homelab, but it was always a PITA. No matter how well you are prepared, how much knowledge you have, how many assisting tools you are using, it's always PITA. That tool better deserves its original name - BORG. It really feels like you're within a BORG spaceship kube. It automates things, but it actually FAILS miserably pretty often with various operations, i.e migrating pods onto the server that failed, but came back online quickly, etc. There are just so many issues with it. Granted, you can easily extend functionality of K8S, but that adds a whole bunch of even more complexity. I went to SWARM, but now I just just single node docker instances. I respect my time and I don't want to waste it on just managing infra all the time.
I think kubectl is essential to know. I really like that rancher gives insight to crds and can assist in deploying clusters. I use k3s in my lab. I like portainer but it doesn't feel fully features and the kunernetes dashboard app is a pain. Lens is probably the best I've used. But for deployments Argocd is nice with the dashboard it gives but it's only for the deployments resources.
Been using k9s for over a year. Having a free tool is paramount for a home lab. I have recently noticed that some types do not show up in k9s and I had to resort to kubectl to see them. I haven't tried to investigate why this is happening, but it is a down side for sure.
Would Rancher fit this llist?
u kinda need to install the cluster with rancher to make the dash work, so prob not. it depends on ingress, etc.
@@_vindicator_ that's not true, you can also manage clusters that were not created using rancher (I did it, not by hearsay :) )
@@lele-tz1uz op is asking if this is a comparable tool to lens or the other dashes. its not. you wouldn't deploy a full rancher to manage a non-rancher cluster. you can say the same for EKS, there are ways to add non-EKS clusters, but there's really no point if all you want is a UI.
Used K8S for quite some time even in my homelab, but it was always a PITA. No matter how well you are prepared, how much knowledge you have, how many assisting tools you are using, it's always PITA. That tool better deserves its original name - BORG. It really feels like you're within a BORG spaceship kube. It automates things, but it actually FAILS miserably pretty often with various operations, i.e migrating pods onto the server that failed, but came back online quickly, etc. There are just so many issues with it. Granted, you can easily extend functionality of K8S, but that adds a whole bunch of even more complexity. I went to SWARM, but now I just just single node docker instances. I respect my time and I don't want to waste it on just managing infra all the time.
Thank you Brandon!
K9s is superb. But provisioning a cluster with Rancher is way more peaceful.
I think kubectl is essential to know. I really like that rancher gives insight to crds and can assist in deploying clusters. I use k3s in my lab.
I like portainer but it doesn't feel fully features and the kunernetes dashboard app is a pain. Lens is probably the best I've used. But for deployments Argocd is nice with the dashboard it gives but it's only for the deployments resources.
Thanks.
Been using k9s for over a year. Having a free tool is paramount for a home lab. I have recently noticed that some types do not show up in k9s and I had to resort to kubectl to see them. I haven't tried to investigate why this is happening, but it is a down side for sure.
Devtron is good too