Hi everyone... I already worked with rancher to provide a k8s cluster into a VMWare, and was a great work. I moved for other job and here we have a IKS (IBM Kubernetes Service) working, and we are installing the Rancher UI to operate this Cluster. Anybody know if Rancher may managing two different cluster like IKS and EKS (aws) in the same interface?

Hello, I have a question related to the rancher k8s upgrades master class hosted by @happy-wire-88980 https://github.com/mattmattox/Kubernetes-Master-Class/tree/main/rancher-k8s-upgrades The update of every component was covered except for the OS upgrade. How do you managed them? The easiest way to do it would be to upgrade one node at a time: cordon/drain -> updates -> reboot -> uncordon, this is a long and tidy process. For the admin cluster, I'm wondering if replacing not up to date nodes with new ones based on an up to date template is a good idea. For the downstream cluster, creating a new cluster with up to date nodes and moving the workload from on cluster to another. This offer a way to move back everything to the previous cluster is something goes wrong. Any though about this or some pointers on how to handle the OS updates for rancher and k8s nodes?

Is there a schedule of MasterClass's being scheduled in first part of 2023? (Not on pinned website)