Hi, Is Rancher supported on Redhat Linux

Redhat 7.x and 8.x

I don't know about support, but it does run quite well on RHEL 8. If you turn on fapolicyd, you may need to make some changes to policy, but it'll do just fine.

Hi All, I am getting the problem when trying to fix expired cert of k3s cluster using system-upgrade . I set the back date and follow the instruction given here (https://docs.k3s.io/upgrades/automated) but pods (system-upgrade-controller-8677c8fb4-4mg6h) is in pending state

I’m trying to figure out why a feature isn’t working and I’m not really sure what it’s called. In Rancher Cluster Manager, you can go into “Service Discovery” > “Services” and for a Cluster IP service, you can click on the name and it exposes the service via the web interface. For example, I have an app that exposes a web-service that you normally get to via

kubectl port-forward

and if I click on it, it opens a new tab with the url to ‘clusters/c-m-sssss/api/v1/namespaces/my-app/services/httpapp ui80/proxy’. What is this feature called?

Hi! does anyone know what this warning is ?

pod 231% ?

i do

describe

on that

node

and it says `Non-terminated Pods`:

40

in total

@astonishing-kilobyte-96371 Hi, sounds like some pods have crashed...

kubectl get pods

should provide info, then need to look at each one to see what is what..

@astonishing-kilobyte-96371 and in describe, all the other output looks ok?

hey all, i just updated to rancher server

2.6.9

and I have this message

Node pools must have unique name prefixes

when I want to upgrade kubernetes version. This is something new added to rancher kubernetes support? I use multiple node pool with the same prefix and different templates but never had issue prior this version.

Did someone get Rancher to work in a HA RKE setup with an external loadbalancer?

Hi everyone, has anyone here tested node autoscaler on Rancher ( backend nodes are on VMware Esxi and Azure) as far as document goes it says that it supports EC2 autoscalling on Amazon, would like to know if anyone has been able to get it working on Vmware and Azure

Hey all, We would like to add a custom tolerations in cattle-cluster-agent deployment for a user added taint in node, so we are exactly hitting this issue - https://github.com/rancher/rancher/issues/16050 Saw the work around :

An empty key with operator Exists matches all keys, values and effects which means this will tolerate everything.
tolerations:
- operator: "Exists"

and

kubectl -n cattle-system patch ds/cattle-node-agent -p '{"spec":{"template":{"spec":{"tolerations":[{"operator":"Exists"}]}}}}'

do you think that the first code snippet can be added to the cattle-cluster-agent deployment manifest or it will work only with kubectl patch? We would like to make this persist with code. Please let us know if we really can add a toleration to cattle-cluster-agent deployment manifest, thank you 🙇

Has anyone successfully consolidate logs from

ns:cattle-logging-system deploy:rancher-logging

and monitoring from

ns:cattle-monitoring-system deploy:rancher-monitoring-*

into the single grafana instance in

ns:cattle-monitoring-system

?? I'm hoping to reduce overall resource utilization by consolidating and I'd like to add Loki to the mix, but I'm unsure as to where to put it. Any thoughts, or pointers to docs specific to Rancher would be greatly appreciated.

Hello, I can’t find csi helm chart in Rancher 2.6.9 . I see cpi but i don’t see csi

for vsphere btw

My book “Edge Computing with Kubernetes” available in Amazon: https://amazon.com/dp/B0B2PSZ1BK is a good book to learn and build #edgecomputing systems using #K3s a lightweight #Kubernetes, sensors and hardware devices. Here is a video explaining the content of each chapter:

Hi folks, I am trying to run etcd on M1 mac but I get

"msg":"failed to open database"

However on switching to a different Mac user on the same machine etcd runs fine. I had colima installed previously which I have tried to eliminate completely

~/.rd/bin/docker run -it --rm --env <http://gcr.io/etcd-development/etcd:v3.6.0-alpha.0-amd64|gcr.io/etcd-development/etcd:v3.6.0-alpha.0-amd64>

Any ideas what might be leading to this?

Hi, I'm new to cluster driver and had a question about local cluster access. From the cluster driver implementation, is it possible to access the local cluster with Rancher's service account token? Experimenting using the in-cluster config failed (from within the cluster driver), and I was wondering how else a cluster drive to read/write to the local cluster

-

Hi Folks, for people learning Kubernetes this might be interesting. I had a sit down chat with Kodekloud founder Mumshad Mannambeth over on the Veeam Community Hub Kubernetes Korner and the recording is now online here:

My #EdgeComputing Systems with Kubernetes book, is available for $5 in Packt site in this link https://packt.link/YUQYK Learn kubernetes and run it at the #edge using Raspberry Pi devices and have some fun this Christmas. A preview video in .

Hi everyone, so I’m trying to create a kubernetes cluster that can allow be add servers from different provider(aws, azure, DO) as worker nodes, has anyone tried creating a kubernetes cluster using a custom provider and then tried to add an AWS EC2 node as a worker node using the “sudo docker …” command? I tried it but it’s not working, Digital ocean was added successfully and works but not AWS EC2

Hi everyone, I use rke to create the K8s cluster, and I use network provider calico to archive pod communication within the cluster but I have an issue with it: The calico-node pod in some nodes restarted frequently My cluster.yaml

network:
  plugin: calico
addons: |-
  ---
  apiVersion: v1
  data:
    calico_backend: bird
    cni_network_config: |-
      {
        "name": "k8s-pod-network",
        "cniVersion": "0.3.1",
        "plugins": [
          {
            "type": "calico",
            "log_level": "WARNING",
            "log_file_path": "/var/log/calico/cni/cni.log",
            "datastore_type": "kubernetes",
            "nodename": "__KUBERNETES_NODE_NAME__",
            "mtu": __CNI_MTU__,
            "ipam": {
                "type": "calico-ipam"
            },
            "policy": {
                "type": "k8s"
            },
            "kubernetes": {
                "kubeconfig": "__KUBECONFIG_FILEPATH__"
            }
          },
          {
            "type": "portmap",
            "snat": true,
            "capabilities": {"portMappings": true}
          },
          {
            "type": "bandwidth",
            "capabilities": {"bandwidth": true}
          }
        ]
      }
    typha_service_name: none
    veth_mtu: "1430"
  kind: ConfigMap
  metadata:
    name: calico-config
    namespace: kube-system

Hi all, one of our db pod is getting stuck in Container creation state with error rpc error: code = Aborted desc = an operation with the given Volume ID 0001-0009-rook-ceph-0000000000000001-be0dbc43-a6c0-11ec-b935-22173251b500 already exists. We are using rook-ceph as storage manager. We restarted csi, rbd plugins and provisioner pods .but still no luck. Any clues on this?