Hello Everyone can someone help me to Integrate rancher with onelogin

Rancher shows me a terminating namespace "cert-manager-test" in Not in a Project, that actually does not terminate. kubectl doesn't show me the namespace at all. If I try to edit the yaml file via the burger menu in Rancher's Cluster Explorer, then it just says "Loading...". If I select "Config" and then the Edit as YAML button at the bottom, then it shows me a yaml file to edit:

apiVersion: v1
kind: Namespace
metadata:
  name: cert-manager-test
  annotations:
    <http://cattle.io/status|cattle.io/status>: >-
      {"Conditions":[{"Type":"ResourceQuotaInit","Status":"True","Message":"","LastUpdateTime":"2022-09-20T11:12:04Z"},{"Type":"InitialRolesPopulated","Status":"True","Message":"","LastUpdateTime":"2022-09-20T11:12:04Z"}]}
    <http://kubectl.kubernetes.io/last-applied-configuration|kubectl.kubernetes.io/last-applied-configuration>: >
      {"apiVersion":"v1","kind":"Namespace","metadata":{"annotations":{},"name":"cert-manager-test"}}
    <http://lifecycle.cattle.io/create.namespace-auth|lifecycle.cattle.io/create.namespace-auth>: 'true'
    <http://field.cattle.io/containerDefaultResourceLimit|field.cattle.io/containerDefaultResourceLimit>: '{}'
#    key: string
  creationTimestamp: '2022-09-20T11:12:03Z'
  deletionTimestamp: '2022-09-20T11:13:07Z'
  labels:
    <http://kubernetes.io/metadata.name|kubernetes.io/metadata.name>: cert-manager-test
#    key: string
  resourceVersion: '116945107'
  uid: 9918aab8-1f1c-48fe-b8b0-9d64a98a5084
  fields:
    - cert-manager-test
    - Terminating
    - 25h
spec:
  finalizers:
    - kubernetes
#    - string
__clone: true

If I try to remove the finalizer and save, then I get an error popup in red

Operation cannot be fulfilled on namespaces "cert-manager-test": StorageError: invalid object, Code: 4, Key: /registry/namespaces/cert-manager-test, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 9918aab8-1f1c-48fe-b8b0-9d64a98a5084, UID in object meta:

Every helpful hint is highly appreciated

Does anyone have running clusters on docker with cgroups v2 (systemd driver)? I am wondering which is the best approach to fix the docker configuration until it is supported by rancher and the agent is passing the correct parameters for v2 I have described the issue here: here . So basically how do we configure the daemon? 1. Leave it as it is by default and modify individual containers - cons - until rancher is passing the correct parameters it would be very unrealiable 2. Change the

default-cgroupns-mode

to

host

- cons - all containers will be running with

CgroupnsMode: host

3. Change the docker driver to cgroupfs v1 ?

Hi, I'm getting the following error "Node k8s-worker-2 status is now: NodeHasDiskPressure", worker disk looks fine, any idea what can be this issue?

Try posting in #rancher-desktop

Hi, pls share cleanup process for imported cluster. I have deregistered it from Rancher console, but still see cattle-fleet-system/cattle-impersonation-system/cattle-system on detached cluster. EKS with rancher 2.6.0 is my env

Hello folks. We setup a k3s single server in the lab using the online instructions and now trying to access its API from a remote windows machine using postman. Can someone please point us to the right direction. We are getting 403 forbidden errors when we try.

What would be the correct way of doing this in a prod environment

Hi Guys,

#rancher-desktop I am facing an issue in opening Rancher Desktop. Below is the error. Appreciate the help in resolving this. Error: EPERM: Operation not permitted, open 'c:\users\.... \wsl-helper.podman-machine-default.log' OS: Windows 10 PS: On installation, the Rancher Desktop GUI opens as expected. However, reopening it after a couple of hours gave the issue. I already tried installing and re-install but facing the same behavior. Thanks,

Hi guyes! I have a question regarding the rancher monitoring chart that i hope someone here know more about. I am trying to get the cluster role monitoring-ui-view into my setup which came with monitoring v2 14.5.100+. I however only have other versions avaliable to me in rancher, 100.1.3+up19.0.3 is the latest one i can install. How can i get 14.5.100? I am currently running rancher 2.6.2.

(rancher-desktop broke my moby-engine service on Fedora 36 BTW, needed to reinstall the entire package)

Has anyone successfully setup Harbor within Rancher and RKE2? I thought I had everything figured out but I randomly get the error

x509: certificate signed by unknown authority

It doesn’t happen on every endpoint that I try to login to but it does happen… just very randomly.

Hi all. Are there any solutions/patterns for automating and provisioning cluster with on premise physical machines (e.g no hypervisor). Projects like tinker ell look interesting wondered if anyone had done anything similar?

Hi, I have two weird issues. One is that the Rancher monitoring chart is nog showing data for pods anymore. Just "no data". It shows some other up to date metrics, but no CPU usage per pod for example. The other one is that Helm upgrades run fine, but the

kubectl proxy

container is not stopping so it hangs infinitely. Any insights/tips would be very much appreciated!

Anyone have ideas on why I don't see a kube-apisever audit event when I open a secret in the Rancher GUI, but I do if I kubectl get the secret? I thought maybe something cache wise, but the behavior is the same even after redeploying the Rancher Deployment

Anyone using rancher 2.6.8, k8s 1.24 & rancher-monitoring? I think the rancher-monitoring bugs. It doesn't collect usage data

Hi folks! I’m have a pretty basic setup (single machine running k3s, nothing fancy), my cluster runs fine and everything is good. But if I create an AMI/snapshot of the entire machine, and then restore it to another, DNS/networking on all pods is broken and doesn’t recover automatically. As soon as I restart k3s (

systemctl restart k3s

or reboot the machine) it all comes back, networking is fine again. It’s quite annoying to have to restart k3s manually after snapshot+restore of a machine, though - any idea why this would happen or how I can debug further?

Hey Guys, I just launched a rancher management instance running on k3s cluster. Now I wanted to spinup rke2 down stream cluster. After I've created the cluster Element the joining URL only shows

--etcd --controlplane --worker

in the registration command. Any idea how this can happen?

Try posting in #rancher-desktop

Hi Everyone, I've got a question about cert-manager compatibility. I run a microk8s cluster with Kubernetes 1.24 and i want to install rancher 2.6.8 to it. But i was wondering. Do i have to install Cert-manager 1.7.3 (like mentioned in the docs) or can i install the newest stable version: cert-manager 1.9.1? Thanks in advance!

Hi Everyone, Recently I installed Rancher 2.6.8, then I was trying to install kubernetes cluster using RKE2 or K3S methods but with no luck. Each time I get : Read: [Disconnected] Cluster agent is not connected Im running cluster behind NAT just for testing purposem Rancher is avaiable for rest nodes either public address or private IP. I use Debian 11 to install Rancher and klaster.

Hey folks, in Rancher 2.6.6... have setup ADFS auth. Setting up a role that I can assign to admin-users... Access to what resource is needed to get list of AD users?

k3s weekly report is up! https://github.com/k3s-io/k3s/discussions/6173

I'm stuck with an annoying issue. One Rancher managed cluster is constantly in error state with message

secrets "cattle-system/c-c-xrj24" not found

I can still access the cluster and everything is running correctly, but I cant e.g. update kubernetes version. I've tried to figure out what that secret should contain, but all my attempts end with "handler cluster-provisioner-controller: unexpected end of JSON input". E: Does anyone have an idea how to fix this, e.g. recreate that secret? What that secret should even consist of?

Hi everyone, where might someone go to ask a beginner question?

trying to install rancher but getting this error: chart requires kubeversion: <1.25.0-0 which is incompatible with kubernetes v1.25.0

any idea