this is after I deleted most nodes in order to roll out a new VM template

question about namespace roles: How comes a project owner in Rancher can create services in the manager cluster, but not endpoints?

Is there any way to recover a cluster in an error state? I’m unable to join new nodes to this cluster because of the error state.

Is it possible to deploy an EKS cluster with version 1.24?

With rancher?

nerdctl

does anyone know if there's a way to get harvester-csi to use a specific storage class instead of the "harvester" default?

if there's not, is there a way to add a disk selector to harvester default?

also, seems like if i delete it, harvester (or something) just recreates it.

I am trying to install Rancher-desktop 1.7 on windows. I am getting error starting Kubernetes. Can someone help with this issue?

#rancher-desktop I am trying to install Rancher-desktop 1.7 on windows. I am getting error starting Kubernetes. Can someone help with this issue?

Hi! Thats my case: https://github.com/rancher/rke2/issues/3710 I would like to know, where exactly should I add this:

kube-proxy-arg:
  - proxy-mode=ipvs
  - ipvs-strict-arp=true

in

cluster.yaml

. I mean in which section of yaml

Hey, when i try to setup Rancher with docker, rancher doesn't come up and exited with an error Code.

2023/02/25 13:58:10 [FATAL] k3s exited with: exit status 2
INFO: Running k3s server --cluster-init --cluster-reset
2023/02/25 13:58:32 [INFO] Rancher version v2.7.1 (bb1c35fc4) is starting
2023/02/25 13:58:32 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/02/25 13:58:32 [INFO] Listening on /tmp/log.sock
2023/02/25 13:58:32 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:34 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:36 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:38 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:40 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:42 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:44 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:58:52 [FATAL] k3s exited with: exit status 2
INFO: Running k3s server --cluster-init --cluster-reset
2023/02/25 13:59:16 [INFO] Rancher version v2.7.1 (bb1c35fc4) is starting
2023/02/25 13:59:16 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/02/25 13:59:16 [INFO] Listening on /tmp/log.sock
2023/02/25 13:59:16 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:18 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:20 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:22 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:24 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:26 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:29 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2023/02/25 13:59:36 [FATAL] k3s exited with: exit status 2

I use this howto here: https://www.rancher.com/quick-start

I am successfully using rancher manager on GCP but I want to build my own home k8s lab with harvester and rancher. Specifically rancher manager 2.7.1 on bare-metal Ubuntu 22.04.2 LTS installed on k3s v1.24.7+k3s1, integrated with harvester 1.1.1 When trying to provision a new cluster on harvester and trying to set options for the machine pool, the UI tries to retrieve k8s/clusters/v1/harvesterhci.io.virtualmachineimages and receives a 404:

{
  "Code": {
    "Code": "NotFound",
    "Status": 404
  },
  "Message": "<http://clusters.management.cattle.io|clusters.management.cattle.io> \"v1\" not found",
  "Cause": null,
  "FieldName": ""
}

and the UI shows: clusters.management.cattle.io "v1" not found on my harvester master node a hv01:/home/rancher # kubectl api-resources | grep clusters.management.cattle.io/v1 does not produce any output and a curl https://harvester.xxx.com/healthz produces curl: (60) SSL certificate problem: self-signed certificate in certificate chain which is to be expected as cert management, especially an automated process with let's encrypt is not available. Would anyone in the community have any ideas of where to look or next steps to begin to troubleshoot?

Hello and excited to join the Rancher workspace. I am a complete newbie to Rancher. Any good video tutorials that someone can point to thanks in advance?

Hi, I deployed rancher as a docker inside a VM. Set it up successfully. When I deploy workloads however, I can't access the workload even though I'm adding a port mapping. Configuration: VM IP (where rancher is running side a docker): 192.168.0.164 Port configuration: ports: - containerPort: 32400 hostIP: 192.168.0.164 hostPort: 32400 name: plex protocol: TCP What am I missing?

hello folks , could you please guide me how to implement DSCP QOS on network interfaces in suse rancher setup ?

Asking again before i open a bug.. This issue is reproduced 😞 I’m trying to restore my cluster from snapshot. I’ve done it many times with

v1.19.6

but now it doesn’t work for me with

v1.22.6

After running:

/usr/local/bin/k3s server --cluster-init --cluster-reset --cluster-reset-restore-path=/root/k3s-dr-recovery-master1-1674728519

I get the following error:

Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg=" doesn't exist. continuing..."
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg=" doesn't exist. continuing..."
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=info msg="Cluster reset: backing up certificates directory to /var/lib/rancher/k3s/server/tls-1674730228"
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg="updating bootstrap data on disk from datastore"
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=fatal msg="failed to write to : open : no such file or directory"
Jan 26 10:50:29 master1 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Jan 26 10:50:29 master1 systemd[1]: Failed to start Lightweight Kubernetes.

That empty path seems not right.. Any suggestions? Thanks

Hello All, • My Cluster is stuck in "Waiting" state (showing on Rancher dashboard) • Info message is "Waiting for API to be available" • Rancher version: 2.7.0 • Kubernetes version: 1.22.9 • RKE: 1.x All pods/containers are running (no restarts) What can be the issue? Please help.

Hi! Does anyone have experience with the above versions? Thanks! Balazs

I am trying to setup a backup for my Rancher v2.6.2, I am using custom endpoint for S3, I explicitly turn off TLS checking but still geting this error. Can anyone help me figure out how to bypass this problem?

I am trying to import EKS cluster in Rancher (2.7). I first tried and went ahead to create a Cloud Credential for AWS. I get "Authentication test failed, please check your credentials" on the UI. This info on the UI is bit vague. Where can I get more details to troubleshoot further?

Hi, I have to big images in my cluster (>10 GB) and rancher can't pull them due to timeout issue, where I can configure timeout for images to pull?

I need to create a back up of my clusters (including VPC's) - Does rancher do that?

Is it possible to make rancher create a new cluster via kubectl (on the cluster that rancher is storing its config in)?

wrong channel ...

Hello all, I am experiencing some weird behaviours trying to run Rancher. This is the situation: • 1.24.9 RKE2 Cluster (1 Master + 2 Nodes) • Context is Airgap (no internet access) • Cert-manager installed through Helm Chart • Rancher 2.7.1 installing though Helm Chart When launching the install of Rancher, it seems to fail looking for the following file /home/aks-operator/.kube/config and failing to list and watch *v1.AKSClusterConfig (get aksclusterconfigs.meta.k8s.io). The issue is, I am not using AKS… Is there a Chart var or Env var with which I could specify that it is running on an RKE2 cluster ? Thanks

Hi there, I am getting "*ErrImagePull: rpc error: code = Unknown desc = context deadline exceeded*" when pulling big images to my Rancher 2.7.0 cluster with RKE, does anybody know how to increase timeout to fix that issues?

What might cause a node to be NotReady after coming up again? e.g. if we take a snapshot of a k3s node and restore it; we see the node go into a healthy running state, but then immediately go into NotReady state for quite a while and then only after many minutes come back. Is there any way to debug why that might be aside from inspecting

describe

output?

hi , kubernetees in not working in rancher desktop, checking k3's image for long time