Any idea when 2.7.0 will be in https://releases.rancher.com/server-charts/stable ?

I installed Rancher Desktop a few days ago and it was working until this morning when things broke down. when I run

kubectl version

I’m getting this error:

invalid configuration: no configuration has been provided
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:36:36Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.7
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Something in the configuration seems to have become corrupted somehow. How can I reset the ~/.kube/config or re-establish a new configuration?

having trouble importing EKS into new rancher version 2.7. As far as i know we have followed procedure. 1. cloud credentials 2. aws

aws-auth

config map entry for the MapUsers where can we check logs regarding importing?

When I install sysbox on RKE2 I run into this issue: https://github.com/nestybox/sysbox/issues/567 I can fix it by using the patch for CRI-O that is show on the second to last comment but I'd like to switch kubelet back onto systemd instead. Does anyone know where the kubelet arguments are stored on the host machines (or elsewhere) so that I can manually repair the

--cgroup-driver

flag?

Hello Rancher Team, I’m new to rancher and trying to setup v2.6 over single node with docker. I am having following errors. Appreciate If anyone can help. Here is how my setup is. single node docker image running behind nginx as reverse proxy (it is docker-compose.yml having both containers). That single node is behind AWS classic load balancer. following are the errors being logged by rancher node (docker-compose logs -f).

rancher-server_1  | 2022/12/01 04:54:09 [ERROR] Failed to handle tunnel request from remote address 172.19.0.2:49716 (X-Forwarded-For: 44.230.106.196, 172.31.30.132): response 400: websocket: the client is not using the websocket protocol: 'websocket' token not found in 'Upgrade' header
rancher-server_1  | 2022/12/01 04:54:09 [ERROR] Failed to handle tunnel request from remote address 172.19.0.2:49716 (X-Forwarded-For: 44.230.106.196, 172.31.30.132): response 400: Error during upgrade for host [c-sxlgx]: websocket: the client is not using the websocket protocol: 'websocket' token not found in 'Upgrade' header

I have another AWS EKS cluster. I am trying to import in above rancher instance. It is showing

waiting

status.

what component in rancher syncs the helm repos for Apps section? all my repos are in "In Progress" status for hours and I see no charts

apologies if this has been asked before. What jetstack chart for cert-manager is compatible with the weird cattle helm install process in rancher 2.6.9?

Hi Rancher team. It has been a great experience using this app on mac with M1 chip. But I get into some problem when I run docker images (mysql). Can anyone help ?? Below is the docker-compose I’ve used

version: "3"
services:
  db:
    container_name: spring-db
    image: mysql
    platform: linux/amd64
    environment:
      MYSQL_DATABASE: todos
      MYSQL_USER: root
      MYSQL_PASSWORD: root
      MYSQL_ROOT_PASSWORD: root
    volumes:
      - ./db/data:/var/lib/mysql:rw
    ports:
      - "3307:3307"
    restart: always

Below is the error I see

Can anyone recommend a clean method of deploying Rancher on a Harvester cluster for the express purpose of managing Harvester and deploying additional Rancher clusters?

Hello. Is anyone here who know what's the logic behind alertmanager-rancher-monitoring-alertmanager-generated vs alertmanager-rancher-monitoring-alertmanager secrets? I deploy my rancher-monitoring by helm manually where I added own routes and receivers but after installing the chart alertmanager-rancher-monitoring-alertmanager-generated seams to contains my changes for a short period of tiem and then are ovveritend and contains some default values, so the config alertmanager-rancher-monitoring-alertmanager-0 is not the one that I deploy with helm chart.

Hi Rancher Team! Could you kindly advice how to disable PodSecurityPolicy admission controller in Rancher, if is it possible of course. We are using Rancher 2.6.8 at the moment.

Hello there! I'm using Rancher 2.7.0 integrated with vSphere I noticed that the form to create a new cluster in vSphere with rke2/K3s is very different from RKE1 With RKE1, I'm able to use templates to create the VMs On RKE2/K3s I must paste my Cloud Config YAML every time Are there any plans to implement templates on RKE2/K3s? Am I missing something? Thanks in advance

here at TMX we have rancher desktop install on our centos machine every time I start it it seems to start 2 copies. the second copy find a port in use and complain. Is that normal with desktop rancher ?

Hi, I'm using Rancher 2.6.8 and was wondering how to provision clusters using the

<http://clusters.provisioning.cattle.io/v1|clusters.provisioning.cattle.io/v1>

API using a

kubernetesVersion

that is built/supplied by someone else. Currently this only seems to work with the rke2 or k3s kubernetes versions bundled with Rancher.

Hello. I am having an issue where the Ubuntu machines in a Rancher only cluster were updated we can no longer access rancher. The ingress pods and rancher pods are all running. But port 443 and 80 are not open on the nodes. I have a daily rancher backup on S3 is there a way to fix this or restore it on a new cluster. And if restoring it is the way to go please guide me to the right direction. This was an RKE1 cluster running HA rancher with many clusters on them.

Hello Everyone, this has never happened to me after working with Rancher for over a year. I did a test cluster with our Rancher server and once I finished the test deleted. The cluster is on updating stage and there is only 1 worker node left, the cluster is on updating stage and it has this message

Waiting for cp-zema-uat1 to finish provisioning

has anyone had this problem before and how can I delete it? thanks in advance

could anyone please assist me I am having a very hard time figuring this out.

Hey all, pretty new to rancher, can someone point me to some tutorials about setting up rancher. I mean from the start, I have ubuntu server and docker what's next? What else I need to install?

hey all, me again, all good overall, REK1 working prefect but when I switch to RKE2/K3s I'm greeting strange issues. anyone have any idea?

Hi — I have a Rancher/FreeIPA integration issue — we have been running rancher 2.5.8 on RHEL 7 & RKE2 on an isolated network for over a year, and suddenly lost the ability to login to the Rancher GUI using FreeIPA credentials. Error from GUI looks like “unknown error, see your system administrator” Local logins work fine but my users depend on the FreeIPA flavor login. Rebooted all masters recently which did not help. Internal error from API looks like LDAP error 49, but the FreeIPA authorization setup looks fine and appears to work; I know the read-only FreeIPA user’s credentials work, but still no luck logging in to Rancher GUI. Any ideas on what to check? Thanks for any help you can provide..

hi, anyone here still using Rancher 1.6?

Hi I'm just trigger a upgrade for the APP Rancher-Backup.. And I'm wondering why i can't use an exsisting Volume-Claim? Is there a plausible explanation why?

Try to run Rancher Desktop on my corporate notebook. Installation world but Kubernetes cannot be started. To me it looks like proxy issues. Where can I set proxy settings for Rancher Desktop?

Does anyone know exactly the “apps” under Apps-> Charts are filtered ? for example there are many more available charts at https://github.com/rancher/charts/tree/release-v2.6.8/charts than listed on my installation. specifically I’m looking for the rancher-vsphere-csi app

👋 Hi everyone! which version of rancher is supported for elastic kuberneties version V 1.22 currently using v2.5.7

Hi,I am installed Rancher with RKE2 on SLE Micro using the RPM package. I did this two times before, and it always worked great, installing the package,

systemctl start rke2-server

, and waiting for it to come up. This time, the service will not come up - in the kubelet.log file I find several entries of this:

E1205 13:53:15.683661    2726 remote_runtime.go:209] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to create containerd task: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument: unknown"
E1205 13:53:15.683713    2726 kuberuntime_sandbox.go:70] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to create containerd task: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument: unknown" pod="kube-system/etcd-rancher-har-nue-01"
E1205 13:53:15.683746    2726 kuberuntime_manager.go:833] "CreatePodSandbox for pod failed" err="rpc error: code = Unknown desc = failed to create containerd task: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument: unknown" pod="kube-system/etcd-rancher-har-nue-01"
E1205 13:53:15.683802    2726 pod_workers.go:951] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"etcd-rancher-har-nue-01_kube-system(e18aa5e5b83a5a3c56d78e4054612394)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"etcd-rancher-har-nue-01_kube-system(e18aa5e5b83a5a3c56d78e4054612394)\\\": rpc error: code = Unknown desc = failed to create containerd task: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: error during container init: write /proc/self/attr/keycreate: invalid argument: unknown\"" pod="kube-system/etcd-rancher-har-nue-01" podUID=e18aa5e5b83a5a3c56d78e4054612394
E1205 13:53:15.723238    2726 kubelet.go:2466] "Error getting node" err="node \"rancher-har-nue-01\" not found"

Am I right in thinking that this is my issue? If yes, any ideas what is happening here and where that "invalid argument: unknown" could come from?

Hi! We are running

rke version v1.3.12

, and while attempting to monitor with prometheus+grafana k8s services (without success) noticed they didn’t get and endpoint IP:

kube-system      kube-prometheus-coredns                   ClusterIP      None            <none>            9153/TCP                                                       127m
kube-system      kube-prometheus-kube-controller-manager   ClusterIP      None            <none>            10257/TCP                                                      127m
kube-system      kube-prometheus-kube-etcd                 ClusterIP      None            <none>            2381/TCP                                                       127m
kube-system      kube-prometheus-kube-proxy                ClusterIP      None            <none>            10249/TCP                                                      127m
kube-system      kube-prometheus-kube-scheduler            ClusterIP      None            <none>            10259/TCP                                                      127m
kube-system      kube-prometheus-kubelet                   ClusterIP      None            <none>            10250/TCP,10255/TCP,4194/TCP                                   127m

Because of that, we are unable to monitor those metrics; this is an example configuration for one of our clusters:

---
nodes:
- address: node1.localdomain
  hostname_override: node01
  user: rke
  role:
  - controlplane
  - worker
  - etcd
  labels:
    role: storage-node
- address: node02.localdomain
  hostname_override: node02
  user: rke
  role:
  - controlplane
  - worker
  - etcd
  labels:
    role: storage-node
- address: node03.localdomain
  hostname_override: node03
  user: rke
  role:
  - controlplane
  - worker
  - etcd
  labels:
    role: storage-node
- address: node04.localdomain
  hostname_override: node04
  user: rke
  role:
  - worker
  labels:
    role: storage-node
- address: node05.localdomain
  hostname_override: node05
  user: rke
  role:
  - worker
  labels:
    role: storage-node
services:
  etcd:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    external_urls: []
    ca_cert: ""
    cert: ""
    key: ""
    path: ""
    uid: 0
    gid: 0
    snapshot: null
    retention: ""
    creation: ""
    backup_config: null
  kube-api:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    service_cluster_ip_range: 10.43.0.0/16
    service_node_port_range: ""
    pod_security_policy: false
    always_pull_images: false
    secrets_encryption_config: null
    audit_log: null
    admission_configuration: null
    event_rate_limit: null
  kube-controller:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    cluster_cidr: 10.42.0.0/16
    service_cluster_ip_range: 10.43.0.0/16
  scheduler:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
  kubelet:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
    cluster_domain: cluster.local
    infra_container_image: ""
    cluster_dns_server: 10.43.0.10
    fail_swap_on: false
    generate_serving_certificate: false
  kubeproxy:
    image: ""
    extra_args: {}
    extra_binds: []
    extra_env: []
network:
  plugin: canal
  options: {}
  mtu: 0
  node_selector: {}
authentication:
  strategy: x509
  sans: []
  webhook: null
addons: ""
addons_include: []
ssh_key_path: ~/.ssh/id_rsa
ssh_cert_path: ""
ssh_agent_auth: false
authorization:
  mode: rbac
  options: {}
ignore_docker_version: false
kubernetes_version: "v1.23.7-rancher1-1"
..........

Is there anything I have to do to enable those metrics?

Are there any examples of cluster drivers using CAPI? Wasn't turning up anything on my own, and wondering if anyone has implemented this before using rancher cluster drivers. The existing cluster driver example looks like it predates CAPI