@white-xylophone-9961 has left the channel

Has anyone seen issues with Ubuntu 22.04 nodes in rancher vsphere clusters? I’m running into ssh errors when I try to deploy 22.04 nodes, but it works fine for 20.04.

We ran into issues with 22.04 but they were not ssh related. Our problem appears to be related to https://github.com/rancher/rancher/issues/38816 We have had to stay on 20.04 ubuntu for our clusters

Yeah, we never got that far. The nodes never deploy at all due to ssh failures.

@victorious-fountain-25696 has left the channel

Hi, I have couple clusters with cloud-provider vsphere and now there's a need for change the nodeport range from the default 30000-32767 to e.g. 30000-39999. Is it possible to change? I cannot find the place the nodeport configuration is set. In a custom cluster the nodeport range is changeable even from "edit config -> networking" but in vsphere deployed cluster the whole networking sections is gone. Any advices?

hi all, can we think of provisioning rke2 cluster with vsphere vcenter integration without ssh, provision entirely like using cloud-init ? If a customer has multiple networks, there will be a network dependency to open ssh connection from rancher to downstream clusters.

Installing rancher-desktop 1.8.1 I get this error. Any way to get out of this? I've tried reinstalling twice now 2023-04-14T174209.468Z: WSL: executing: /bin/sh -c [ -e /etc/os-release ] && . /etc/os-release ; echo ${VERSION_ID 0.1} Error: wsl.exe exited with code 4294967295

Has anyone tried to deploy a RKE2 cluster into a SDDC? Trying to deploy a fresh cluster into a new SDDC but it can't even get to the point where it starts the VM. I haven't found anything in the logs yet that seem useful but it says failed to create VM and it attempts to recreate however it doesn't delete the previous attempt and it will just go in circles until you tell it to stop

Hi there, we have some trouble to get a vSphere based k8s cluster with version v1.25.9+rke2r1 provisioned by a Rancher v2.7.3 instance. Rancher itself is a fresh deployment on AKS and its trying to bring up a cluster on our on-premise vSphere infrastructure. Rancher installation went without any issues and it imported its "local" cluster just fine. For vSphere we are using the vSphere cloud provider and configured cpi/csi under the "Add-On Config" tab. At first everything seems to work fine. It creates VMs in the defined pools and the "Provisioning Log" tab shows messages as expected:

[INFO ] waiting for viable init node
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for agent to check in and apply initial plan
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for probes: etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for probes: etcd, kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for probes: kube-apiserver, kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for probes: kube-controller-manager, kube-scheduler
[INFO ] configuring bootstrap node(s) rancher-test-pool1-5fd745d759-p6wvj: waiting for cluster agent to connect
[INFO ] non-ready bootstrap machine(s) rancher-test-pool1-5fd745d759-p6wvj and join url to be available on bootstrap node

But here is gets stuck forever. The "Explore" button has turned blue and can be clicked and I can see the node details and a few other entities in the cluster. But it won't complete that last step and the node has the label

<http://plan.upgrade.cattle.io/system-agent-upgrader=7dbfe3bc7aa1f9e217597840afda8c191bdef89403968ed04de99eec|plan.upgrade.cattle.io/system-agent-upgrader=7dbfe3bc7aa1f9e217597840afda8c191bdef89403968ed04de99eec>

and the other nodes don't do anything either. Right now we selected the cilium network plugin but we ran into the same issue using calico. We also don't see any obvious error messages anywhere that would point us into the right direction. Any ideas or pointer what might be causing this? Thanks

Hey we have just upgraded to rancher 2.6.11 from 2.6.8 and when building an rke2 vsphere cluster and selecting cloud provider as vsphere it does not show the options in the add on config. Is this a bug?

Good morning folks, I'm hoping someone can help me with a cluster whoopsie I made. My controlplane node is in a deleting mode, but the node-controller finalizer is preventing the deletion. This is good because I can still talk to the cluster. Once the node is in this state, is there any way to tell rancher NOT to delete the node?

Maybe by editing the

<http://nodes.management.cattle.io|nodes.management.cattle.io>

object directly?

Dear community members,

Dear community members, We are new to Rancher and to RKE2. We want to setup a RKE2 cluster in our airgapped VMware vSphere environment without the use of Rancher (used for bootstrapping). This works, but after the installation of the rke2 kubernetes cluster, I want to automatically install the vsphere cloud provider. According to the documentation this should be possible using this configuration: Contents of /etc/rancher/rke2/config.yaml: token: SECRET tls-san: - kubernetes.my.domain.local write-kubeconfig-mode: "0644" cloud-provider-name: rancher-vsphere cloud-provider-config: /etc/rancher/rke2/vsphere.conf Contents of /etc/rancher/rke2/vsphere.conf: [Global] datacenters = "tkgi" insecure-flag = "1" user = "ADuser@my.domain.local" password = "PASSWORD" server = "vcenter.my.domain.local" port = "443" cluster-id = "testclusterid0001" [VirtualCenter "vcenter.my.domain.local"] user = "ADuser@my.domain.local" port = "443" password = "PASSWORD" datacenters = "rke2" I get the following errors after systemctl start rke2-server.service and waiting a while. We use rke2 version 1.24.13+rke2r1. kubectl logs pod/rancher-vsphere-cpi-cloud-controller-manager-bgqd7 -n kube-system ... E0523 142529.727585 1 config_yaml.go:136] vsphere.conf does not have the VirtualCenter IP address specified E0523 142529.727593 1 config_yaml.go:214] validateConfig failed: vsphere.conf does not have the VirtualCenter IP address specified W0523 142529.727598 1 config.go:69] ReadCPIConfigYAML failed: vsphere.conf does not have the VirtualCenter IP address specified E0523 142529.727615 1 config.go:73] ReadConfigINI failed: 31 expected section header F0523 142529.727625 1 main.go:265] Cloud provider could not be initialized: could not init cloud provider "vsphere": 31 expected section header ... This is caused by a ConfigMap that doesn't have the correct contents: kubectl describe ConfigMap/vsphere-cloud-config -n kube-system Name: vsphere-cloud-config Namespace: kube-system Labels: app.kubernetes.io/managed-by=Helm component=rancher-vsphere-cpi-cloud-controller-manager vsphere-cpi-infra=config Annotations: meta.helm.sh/release-name: rancher-vsphere-cpi meta.helm.sh/release-namespace: kube-system Data ==== vsphere.yaml: ---- # Global properties in this section will be used for all specified vCenters unless overriden in VirtualCenter section. global: secretName: "vsphere-cpi-creds" secretNamespace: "kube-system" port: 443 insecureFlag: true # vcenter section vcenter: "": server: "" datacenters: - "" Also the vsphere-cpi-creds secret is not correct. kubectl get all -n kube-system ... NAME READY STATUS RESTARTS AGE pod/etcd-rancher04-01 1/1 Running 0 14m pod/helm-install-rancher-vsphere-cpi-tj8sl 0/1 Completed 0 14m pod/helm-install-rancher-vsphere-csi-h9j9m 0/1 CrashLoopBackOff 7 (4m3s ago) 14m pod/helm-install-rke2-canal-zhf4w 0/1 Completed 0 14m pod/helm-install-rke2-coredns-mvcbj 0/1 Completed 0 14m pod/helm-install-rke2-ingress-nginx-tlsdk 0/1 Pending 0 14m pod/helm-install-rke2-metrics-server-r7dx8 0/1 Pending 0 14m pod/kube-apiserver-rancher04-01 1/1 Running 0 14m pod/kube-controller-manager-rancher04-01 1/1 Running 0 14m pod/kube-proxy-rancher04-01 1/1 Running 0 14m pod/kube-scheduler-rancher04-01 1/1 Running 0 14m pod/rancher-vsphere-cpi-cloud-controller-manager-5g946 0/1 ImagePullBackOff 0 14m pod/rke2-canal-pfhx7 2/2 Running 0 14m pod/rke2-coredns-rke2-coredns-7f75564ff4-fnxlw 0/1 Pending 0 14m pod/rke2-coredns-rke2-coredns-autoscaler-84d67b7c48-72dtj 0/1 Pending 0 14m ... My question is how to get this working. I think the /etc/rancher/rke2/vsphere.conf file should be used by the rke2 service to generate a Helm chart with the correct values, but this fails somehow.

Can someone help me figure out why my nodes are not building properly? I have a rancher cluster that is live and working. I need to add a new worker node and discovered my template in vsphere was missing so i am attempting to build a new one. The issue I am having is that when rancher builds the node it dies saying timeout waiting for ssh. I tested connectivity to the device from mine and was able to connect to it using the keys I got from the cluster manager screen. as far as i can tell the VM is live and well, but i'm not sure where to look to figure out why rancher isn't able to connect to it.

Hi there! I`ve same issue https://github.com/rancher/rancher/issues/36986 And I can`t understand how to install cloudbase-init correctly. Help me please

Seeing an issue with Rancher and RKE2 clusters running on VMware. The issue is around deployments initial bursting. I have VMs with 6CPUs but VMware is showing them as over allocated and should be right sized to 4CPUs. However, if I do that and then need to conduct some deployments I am not having enough resources to deploy unless I increase CPUs back to 6. Anyone experiencing this issue with on-prem K8s running on VMware and if so how are you overcoming this obstacle.

Hi, got a setup where we are deploying a downstream cluster across 2 vsphere clusters, with each cluster having its own vsan datastore and this cannot be shared between vsphere clusters. When we create a pvc it’s in a pending state with the error ‘failed to get a shared data store in kubernetes cluster, Error no shared data store found for nodevm.’ Issue here https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/2377 Any ideas is there a workaround to this we can use?

Hi, we have built various custom clusters and want to convert them as vSphere clusters in the future. Is the only way to build the new vSphere clusters and then manually move everything or is there a way to connect the custom cluster to a vSphere cluster? Then you could just delete the custom cluster nodes and be migrated.

Hi, I have installed Rancher v2.7.4 on a K3S cluster, and I am looking for ways to perform a cluster backup. Please share your suggestions on what's the best way to perform a Rancher Backup and Restore.

I am getting following in

rancher-vsphere-cpi-cloud-controller-manager

RKE2 v1.25 and also in v1.26

E0713 17:24:46.617584       1 node_controller.go:229] error syncing 'node1': failed to get provider ID for node node1 at cloudprovider: failed to get instance ID from cloud provider: VM Guest hostname is empty, requeuing

Is this a permissions issue in vsphere?

Hi, I just get managed to deploy a vSphere Cluster with VM-Templates, cloud-init, vApp-Options and so on with the standard cluster->create->vSphere - wizard. Becaus there are many parameters to enter, I like to create a cluster-template. For RKE2 there is the new helm-concept: https://github.com/rancher/cluster-template-examples/tree/main. Do I have to register this templates under Repositories for the local-cluster? This seams to work with the example github-repo. Or can I deploy a template direct with helm from a local helm-chart? I did not get this to work. I like to avoid the deploiment with a repo. Rancher: 2.7 on a k3s cluster.

Hi All, I am having a bit of an issue with getting something working, I've spun up an Ubuntu VM and installed rancher with docker (using the quick start command).

I can then go to the cluster management page and 'create' a cluster on vsphere, I put in the right creds, then in the options I choose RKE2 as the provider, mostly leave the options unchanged apart from selecting a network and a VM template to use (Ubuntu, spins up with dynamic IP)

a VM spins up in vpshere named after the node pool name I entered, but it gets stuck on 'configuring bootstrap nodes <stuff> waiting for agent to check in and apply initial plan

Have tried opening ports with UFW (a few rancher ports I read about, plus 443, on both the vm hosting the dockerised rancher and the node pool it spins up, no luck)

The thought occurs it could be some host.docker.internal stuff maybe? (pls feel free to recommend troubleshooting steps if you agree?) or that the node it spins up just isn't doing anything rancher-y at all (for example, I cant see any containers on that machine with dockerps, and don't see any mention of rancher or RKE in the syslog/auth log etc)

hi all, i am going through the process of upgrading my clusters from 1.24 to 1.25.11