5:08 the most important thing in this tutorial. Thanks for such a great content..

Very authentic and helpful video! Thanks!

IMPORTANT: A new review of Rancher is now available at kzfaq.info/get/bejne/gKxxf8eZ2ajcgmw.html

I love rancher :)

Very interesting, thanks for the video!

I think you have explained very nicely thanks u so much from India...

Excellent video.

5:11 Loved it how you switched to Dark mode

Rancher has not only RKE as a Kubernetes distribution but also K3s and RKE2, which both are NOT based on Dockershim, but on containerd. Second thing is: Kubernetes is deprecating Dockershim as part of the Kubernetes project, but Dockershim will continue to exist as a plugin, like some other CRI plugins. It will be maintained by Docker Inc, Mirantis and Rancher. So, the comment about Rancher not being up-to-date is irrelevant.

Really interesting video and also on time for me. I've been working with Rancher a few years back (on prem) and will go back to working with it towards the end of the year. The setting with docker and the fact that it uses post-provisioning installs on node pools made me wince a bit. I hope they will fix it soon. Personally I prefer CLIs over UIs, so the dashboard view is not a killer feature for me. Still I prefer provisioning with terraform and am also exploring Crossplane and cluster API. Could you make a video about fully automated provisioning lifecycle including Day2 OPs? There are plenty of videos about how to start, but rarely good ones that dive into Day2 specific challenges. Thanks for great vid as always :)

You might want to mention that it also offers a single point of access into multiple clusters via the rancher proxy for kubectl. This is great for centralized access control that can even be per namespace etc. without deploying anything special onto the clusters itself.

I finally get why people love your videos. You do point out those terrible features/bugs. I really love this kind of hands on experiences rather than those apopathetic tutorials

For on prem rancher also has rbac with AD which is super nice , also another rancher project worth looking at is LongHorn distributed storage which again is amazing if your on prem storage isn’t anything super special

Most important thing that everyone should do: change it to dark mode! YES!

thanks for the video

One thing to be careful about that I struggled to figure out is that it installs on a docker IP (in example: 172.16.0.5)and not on the localhost 127.0.0.1, therefore if you try to access it via the localhost or 127.0.0.1 it might not work. Had to spend many hours to see this is how it worked, since the rancher academy or other tutorials stated otherwise.

K9S gang rise up

I don't use rancher for cluster management or creation. Like you say, it feels unnecessary when using managed clusters on DO, Google, AWS etc. However I always attach rancher post creation to manage RBAC, ingress, and get a basic UI overview of what is going on. If there was one thing I still feel like rancher does best it is RBAC management (linking to github, AD, etc). Also for getting some quick templates up for basic apps and visualizing where things are located, editing configs and secrets and so on, it is very handy. On the other hand that kind of works against git-ops, so :D. back to pros and cons..

would also be interested in showing us how best to utilize and implement tailscale/taildrop in your preferred cluster setup and config..tnx

Great content! What do you think about Gardener? Do you think it is a good choice for running a KaaS on top of OpenStack? Thanks

I'm still not able to retire Docker Engine for some nodes. While containerd is used for k8s pods, there are a few labeled nodes that have Docker Engine as well bind mounted named pipe to it for build agents. Kanako didn't work for multistage Dockerfiles when I tried it (a few months ago). Do we have a non-Docker Engine way to build container images, yet, that works for multistage Docker files?

Hi, Just to answer some of the CONS part 1. Rancher has k3s and rke2 which uses containerd by default and I think they are moving away from rke (the first version) anytime soon. 2. For ingress controller nginx was already enabled just go to the default namespace>load balancing For the storage you have a lot of options in their apps section but rancher recommends longhorn. 3. Again just use k3s and rke2.

Brother, clearly you have to know , only the coding and cluster junkies like me love rancher :) Well done video

Thank you so much for your video but there are more advanced options for K8's cluster lifecycle mangers like CAPI or Hive that have MachineSet/MachineDeployment/MachineConfig and cluster auto-scaler options..

About immutable images, are there any pre-built, up-to-date kubernetes vm images ready for use ?

Thank you for you video. I like to much. You are very updated. Could you create a video comparing OS distro to run Kubernetes on-premise? Which is the best one?

Nice video viktor! What are alternatives to Rancher in order to monitor multiple Kubernetes clusters in cloud using a single UI. I prefere using IaC to manages multiples clusters (terraform, argocd) , but what about monitoring and visualizations of all clusters? Grafana, and service mesh UI give us this kind of details for a dedicated cluster, but it would be useful to have a unified UI to check health of all clusters, manage alerts... Did you already explore this kind of tool?

What's your idea about Running Rancher 2.x on a three node on-premise cluster? VM specification (4CPU, 16GB)

i had issues with it, on a local lab machine (32gb ram, i7, 480ssd): some services refuse to start up, the kubectl "web gui" gives error 1006 and does not show anything... looking for alternatives, what do you suggest to create a local test lab? I put proxmox on this machine, and created 6 vms using ubuntu 20.04, 3 master and 3 workers, having the host (proxmox is based on debian 10) sharing its own disk space as nfs share... but i'd like to move away from rancher, so, suggestions? :)

Is there any reference architecture for an active active between on prime and cloud rancher cluster?

hey Viktor - could you make a video on k8s security applications such as stackrox & twistlock? How necessary they are, are they replaceable with other measures, effect on cluster performance etc.?

Would be interested to know what you think of VMware Tanzu? 😀

Is it possible to add Raspberry PI (ARM64) as a node in the RKE cluster? I get stuck in the node provisioning stage when I try to add a Raspberry PI as a node in the RKE cluster. Much appreciated.

My lab has no internet connections. Does this work for this kind of environment? I see the nodes need to download images from internet.

Hello Admin, I install rancher on my local K8s cluster (1master node + 2 worker node). I build this cluster from scratch with 3 ubuntu VM on VMware workstation. Each VM have 2 NIC (1public + 1private) I run follow command from your script: # If NOT EKS export INGRESS_HOST=$(kubectl \ --namespace ingress-nginx \ get svc ingress-nginx-controller \ --output jsonpath="{.status.loadBalancer.ingress[0].ip}") #then echo $INGRESS_HOST >> however the result still blank. Can you suggest me on how to solve it? Thank you very much!

Mirantis-k30s would improve Rancher k3s limitation by providing Cri-O as the runtime alternative, in addition providing integration with multiple csi storages

If the main "pro" for rancher are on-prem installations, how does it compare to OKD ? as that should be free OpenShift without RedHat support right? Would OKD be a better option for on-prem ? you would get Storage management, mutable provisioning, non-docker setup in addition to all the stuff rancher provides

5:29 0.6/5.8 cores? 05.8? Am I missing something here? What is 0.8 cores exactly?

In varibale RANCHER_ADDR what you given?

can u pls make a vid on how to upgrade helm charts using cicd or how to automate the deployment of helm charts.

how to fix below error: Error: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.25.3+k3s1

is Rancher the best tool for creating and managing multiple clusters, or is there a better option?

Can you do an Openshift video(s)?

KOPS? What do you think?

is this rancher giving up, or suse pausing development after acquisition? what is the better free cross-provider ui management alternative (including on-prem and cloud clusters)?

By all the comments about the glory of cloud managed k8s, many many user can and will not running on public cloud, at least not our customers, non of them are allowed to run there. I would rather prefer you are fair and focus on the rancher use case, Which is mostly on prem. And then compare with other on prem alternatives

I think, I can sense Suse influence already :D The new interface v2 is terrible, anyway I really like Rancher in some kind..

docker: whywhywhywhy? lol

Weird how people think Kubernetes is something you should buy from a public cloud provider. Easy, yes. But so expensive.

docker

I hate rancher and all it does, it's way too intrusive in the communication between the control plane and the nodes. We got left out with no management working on production clusters for a while until we decided to redeploy everything from scratch without Rancher. If you don't pay for support, it's a ticking bomb

DO NOT use Rancher. Sad it sold. It took yrs of my life in frustration and stress. Team sucks. Arrogant and not helpful. Left it and never looking back!!!

Rancher deploys ingress. You just "using it wrong" :-D In the video, you are enabling ingress but not the default backend. Therefore, you can not see a service. Because thats the only service you would see for ingress: $ kubectl get service -A | grep ingress ingress-nginx default-http-backend ClusterIP 10.43.160.19 80/TCP 288d However, even without the default backen, you should have ingress. Please check this: $ kubectl get pods -A | grep ingress ingress-nginx default-http-backend-6977475d9b-4km5v 1/1 Running 0 24d ingress-nginx nginx-ingress-controller-mjblv 1/1 Running 0 24d ingress-nginx nginx-ingress-controller-sld26 1/1 Running 0 24d ingress-nginx nginx-ingress-controller-thbcc 1/1 Running 0 24d kube-system rke-ingress-controller-deploy-job-4c4hq 0/1 Completed 0 24d You should have the ingress-controller and should be able to create ingresses. But you do not have the "default backen" service. Regarding docker: I agree mostly. However, two notes on this: I) dockershim will be supported by 3rd Parties for a longer period. II) While RKE depends on Docker they already have K3S and RKE2 which are not. Therefore, one should consider RKE as a "soon to be replaced" product. The pitty is, RKE2 and K3S are supported by Rancher for beeing imported and managed (and upgraded), but they do not support creating clusters with them out of Rancher. Hopefully this may come sooner than later. Especially K3S and K3OS are really awesome, did a lot with them recently. PSP will not go, it will be reimplemented differently. But as of now, its still here and therefore should be supported by Rancher. I fully agree on Kubernetes Versions of cloud providers. It's even worse: In Azure, if you create a AKS cluster out of Rancher, everything is fine. It knows it's AKS and it automatically grays out stuff like etcd and controller, because those are "hidden" in AKS. If you create it in Azure and import it, you have big red failures right on your dashboard (that one with the gauges) because it does not detect ist AKS.