For rancher (using harvester), if i provision a few machine pools is there a way I can add an external/generic node manually outside of the pools?

#general Does suse provide license support for k3s ?

Hey guys, why am I getting 404 not found on Rancher Dashboard? Do I need to like Factory Reset my Rancher Desktop?

is there a good way to run monte carlo simulations on K3S?

Good morning. When attempting to connect to a v2.5.8 Rancher cluster using Rancher CLI, like this:

rancher login https://<fqdn> --token <token>

I am getting this message:

FATA[0000] Bad response statusCode [401]. Status [401 Unauthorized]. Body: [message=Unauthorized 401: must authenticate] from [https://<FQDN>/v3]

Is there something different I need to be doing? Or, is there a way to use a KUBECONFIG file to authenticate (like we do when using kubectl or helm)?

I think I figured it out. Rancher CLI wants to authenticate the local Rancher cluster, not the Kubernetes cluster.

In the Rancher helm chart, is there a way to include custom dashboard-ui instead of using the one that comes with rancher? I went through the rancher helm chart but couldn’t find from where the UI image is being pulled.

👋 Hi everyone!

I'm hoping I can get some help standing up a k3s cluster on bare metal

I'm using k3sup, and I've setup 3 servers and 3 workers, they all show as ready.

flannel-backend=host-gw

All nodes are reachable between each other and from workers, I see the cni0 interface and I can ping pods from the host. On server I cannot ping pods form the host, and there is no cni0 interface

servers have a

--node-taint='k3s-controlplane=true:NoSchedule'

taint, which I assumed meant that non system workloads aren't scheduled, but looks like no workloads are scheduled on workers at all, including coredns, etc. I ran out of places to look for a cause, does anyone have any insight? Thanks in advance

Hello, the documentation says that ARM64 is supported only with Flannel CNI. Rancher uses Canal by default. Would that work (because of Flannel being also under the hood), or it requires CNI to be just Flannel?

Follow up question on the ARM64 support above. How experimental is it? I just need a node to compile some Raspberry Pi code once in a while. The only thing I would need that may be missing based on the doc is the monitoring/logging capability. Anybody has experience with ARM64 already on rancher 2.6?

Hi, Im using rancher v2.6.6 and trying to create a new cluster with the GKE driver. The creation fails, and this what I see :

$ k describe googlemachines   -n fleet-default
...
error setting machine configuration from flags provided: no Google Cloud Project name specified (--google-project)

but on the create cluster dialog I don't see any input where I clould set the projectId (or zone, or instance type) what do I miss?

Hey! I'm trying to automatically run a wsl-vpnkit command when rancher desktop starts up, I tried to create a file in the %AppData%\rancher-desktop\provisioning directory called initvpn.start File content:

#!/bin/sh
/mnt/c/Windows/system32/wsl.exe -d wsl-vpnkit service wsl-vpnkit start

Made sur that the line endings are LF. If I run the same command through wsl in the rancher-desktop distribution it works, but not with the script. I couldn't find any logs about the command run either, is it even logged somewhere? Thanks

Hello, I m creating my cluster with k8s version 1.22, AMI Version 1.22.12-20220914, but i can't install all deployment easily. Cos, most of the API Version are deprecated etc. I am also installed rancher-2.6.8 and can't use. So, which rancher version should i need to use ? Or do i need to downgrade eks version ?

34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 22:23:16.209414      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
2022/09/26 22:25:17 [INFO] Loaded configuration from <https://releases.rancher.com/kontainer-driver-metadata/release-v2.6/data.json> in [0x74ac4e8]
2022/09/26 22:25:17 [INFO] Loaded configuration from <https://releases.rancher.com/kontainer-driver-metadata/release-v2.6/data.json> in [0x74ac4e8]
W0926 22:33:04.212632      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 22:39:54.214550      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 22:48:37.218047      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 22:58:17.222378      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:06:07.226246      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:13:56.228652      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:22:07.231982      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:29:26.234908      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:38:10.236563      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:45:14.240648      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:51:19.243966      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0926 23:58:18.246772      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:04:27.259409      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:13:25.254800      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:21:47.258678      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
E0927 00:25:17.996714      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
E0927 00:25:18.058935      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
E0927 00:25:18.107718      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
E0927 00:25:18.176601      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
E0927 00:25:18.448782      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
2022/09/27 00:25:18 [ERROR] Failed to read API for groups map[<http://metrics.k8s.io/v1beta1:an|metrics.k8s.io/v1beta1:an> error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding]
E0927 00:25:18.618230      34 gvks.go:69] failed to sync schemas: unable to retrieve the complete list of server APIs: <http://metrics.k8s.io/v1beta1|metrics.k8s.io/v1beta1>: an error on the server ("Internal Server Error: \"/apis/metrics.k8s.io/v1beta1?timeout=15m0s\": the server could not find the requested resource") has prevented the request from succeeding
W0927 00:25:19.365353      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
2022/09/27 00:25:21 [INFO] Updating TLS secret for cattle-system/tls-rancher-internal (count: 2): map[<http://field.cattle.io/projectId:local:p-v5fsk|field.cattle.io/projectId:local:p-v5fsk> <http://listener.cattle.io/cn-10.100.212.117:10.100.212.117|listener.cattle.io/cn-10.100.212.117:10.100.212.117> <http://listener.cattle.io/fingerprint:SHA1=F66FDBCDF677741CEEA4BDFFEBBFF42EF448B7E6|listener.cattle.io/fingerprint:SHA1=F66FDBCDF677741CEEA4BDFFEBBFF42EF448B7E6>]
2022/09/27 00:25:21 [INFO] Updating TLS secret for cattle-system/serving-cert (count: 7): map[<http://field.cattle.io/projectId:local:p-v5fsk|field.cattle.io/projectId:local:p-v5fsk> <http://listener.cattle.io/cn-127.0.0.1:127.0.0.1|listener.cattle.io/cn-127.0.0.1:127.0.0.1> <http://listener.cattle.io/cn-192.68.102.115:192.68.102.115|listener.cattle.io/cn-192.68.102.115:192.68.102.115> <http://listener.cattle.io/cn-192.68.102.208:192.68.102.208|listener.cattle.io/cn-192.68.102.208:192.68.102.208> <http://listener.cattle.io/cn-192.68.102.22:192.68.102.22|listener.cattle.io/cn-192.68.102.22:192.68.102.22> <http://listener.cattle.io/cn-localhost:localhost|listener.cattle.io/cn-localhost:localhost> <http://listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system|listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system> <http://listener.cattle.io/fingerprint:SHA1=229A4E9BA347B7D28CE3DA11785A787FB24DE0A1]|listener.cattle.io/fingerprint:SHA1=229A4E9BA347B7D28CE3DA11785A787FB24DE0A1]>
W0927 00:27:04.262048      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:32:57.264854      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:41:52.270559      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:49:04.272743      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0927 00:57:10.275272      34 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+

I have created a Racher cluster with 2 master servers. spec: RKE 1.3.14 version started a K8s version: v1.24.4 Using Helm installed 2 Racher masters with version 2.6.8 OS: CentOS 7.9 Running VMs in Scaleway. while creating a custom K8s cluster with one master node. I am getting the following error.

Ready	False	55 mins ago 	[Disconnected] Cluster agent is not connected

On the Workloads > Pods view, what determines which container image is displayed? There are 3 containers in the pod, but we only see the istio proxy listed.

Hello

👋 Hi everyone! Can the api workload rancher be used for bulk input? so I can make multiple workloads in one post request

Hi all, ... I need to configure fleet imageScan when using image name into helm chart values.yaml instead of raw kubernetes manifests. Someone could give me some example ? Thanks ;)

Hi all. Can anyone suggest that multi cluster environment can be handled by rancher or not??

Hi, does anyone know if there is a way to "propagate labels and annotations defined at Rancher Project to underlying namespaces" ?

Anyone having problems with S3 etcd backup in 2.6.6? I get

failed to set s3 server: failed to check s3 bucket:etcd-backup, err:Access Denied

I already tried to change the IAM Policy, I'm trying with

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:*"
      ],
      "Resource": [
        "arn:aws:s3:::*",
        "arn:aws:s3:::*/*"
      ]
    }
  ]
}

And it still fails

Rancher already generates a kubeconfig file invoking the Rancher CLI when setting

kubeconfig-generate-token

to

false

. Now that Rancher supports time limited tokens - would it be possible to add AAD integration to Rancher CLI? Similar post was raised on the forum some time ago.

hi all

You're out of memory

Hi everyone! I'm getting stucked when try register a cluster on my RKE HA Rancher. A continuous message "Waiting for node to register. Either cluster is not ready for registering, cluster is currently provisioning, or etcd, controlplane and worker node have to be registered" is present when I apply the command on the vm to be provisioned. I'm using this proxy configuration on my Rancher HA instance: https://docs.ranchermanager.rancher.io/how-to-guides/new-user-guides/infrastructure-setup/nginx-load-balancer Seems like it's a proxy problem, because if I change my DNS to the RKE node where Rancher is deployed, ignoring the Load Balancer, the cluster is deployed normally. I'm using RKE v1.3.10 (v1.22.9) and Rancher 2.6.8. Anyone could help me? Thanks very much!