@crooked-cat-21365 use the compare? https://github.com/rancher/rke/compare/v1.3.17...v1.4.1

Hi guys, I followed the guide https://docs.rancherdesktop.io/how-to-guides/setup-NGINX-Ingress-Controller/ and tried to change port 8080 to 80 so that http://demo.localdev.me/ is accessible, however that does not work, any idea what needs to be done additionally?

@shy-musician-14644 Hi you should ask in #rancher-desktop

Weird question: what container runtime is default for hosted kubernetes?

Has anyone run into issues with Vault Kubernetes auth and Rancher clusters? I have a few old clusters (Kube 1.20, 1.21) that work fine with Vault Kubernetes auth, but the new Rancher environment I’m spinning on k8s 1.23 Vault Kubernetes auth just doesn’t work despite being setup and configured in the exact same way

Trying to restore my broken etcd of a cluster managed in Rancher the GUI gives me an error message "Cluster must have at least one etcd plane host: failed to connect to the following etcd host(s) ...". How is this supposed to work? AFAICS the documentation of Rancher 2.6 doesn't describe this special case (nor does it give any other example for a successful restore).

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 again folks! 👋 A few months ago, we at Komodor released a new open-source project called Helm-Dashboard, which got a lot of positive feedback and attention from the community. I’m happy to share that now Helm-Dashboard can be installed both locally AND on a cluster. It’s basically a GUI for Helm, designed to solve some of the more acute pain points of Helm users by visualizing changes in Helm charts. The goal is to help beginner Helm users to get started with Helm, and for more experienced users to speed up operations. The new cluster installation capability would enable users to collaborate better and share the same view of their charts. Check it out on GitHub: https://github.com/komodorio/helm-dashboard Feel free to join our Slack Kommunity: https://join.slack.com/t/komodorkommunity/shared_invite/zt-1dm3cnkue-ov1Yh~_95teA35QNx5yuMg Give it a ⭐ if you liked it :)

I am not able to access Kubernetes on my rancher desktop. Anyone? (edited) image.png

Hello - I have an interesting problem for you all... When I add a specific node (node A) to a k3s cluster, that machine gets filtered from port 443 of another node (node B) in my cluster. This causes issues because on node A I have a pod which makes a request that hits port 443 of node B, but cannot. I can provide more information if needed but I was wondering if anyone has seen this sort of behavior before when adding machines to a cluster. TIA for any helpful advice.

--> #rancher-desktop

Hello All, I have a Rancher Manager (deployed over K3S in Azure) which I am trying to integrate with my LDAP also deployed over K3S. But I am getting following issue . https://github.com/rancher/rancher/issues/40012. Could anyone please help me with this.

Hi Everyone, I am new to rancher and need to evaluate RBAC on rancher. How does RBAC works on rancher, does it uses native kubernetes RBAC for managing user access. Any link to documentation or blog will be highly appreciated. Thanks in advance.

@tall-school-18125 Now that 2.7.0 is out, did any UI performance enhancements make it into the release? https://rancher-users.slack.com/archives/C3ASABBD1/p1657819590698229

hey all, dunno if this is the right channel to ask, but i am trying to stand up a brand-new rancher environment on brand-new Fedora CoreOS instances (VMs). I created a cluster with three machines and it’s been sitting on “Waiting for API to be available”. I found https://github.com/rancher/rancher/issues/38222 but it’s closed as fixed

Rancher 2.7 and K8 1.24.8

Hi, Do we have any mechanism to create rancher roles during helm installation?

Hello, I installed a cluster using rancher. then i installed metallb from ui then i also installed these crds: --- apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: creationTimestamp: null name: my-ip-space namespace: metallb-system spec: addresses: - 10.8.4.0/24 status: {} --- apiVersion: metallb.io/v1beta1 kind: BGPAdvertisement metadata: creationTimestamp: null name: bgpadvertisement1 namespace: metallb-system spec: aggregationLength: 32 communities: - 64512:1234 ipAddressPools: - my-ip-space localPref: 100 status: {} I didn't see an option to enable this setting. ipvs: strictARP: true I don't know if it's because of this parameter that it doesn't work. metallb provisions ip loadbalancers well. A fortigate firewall is placed in front of the ips load balancers (metallb). Thank you for your help.

This is the RKE1

Hi All. I've an installation of rancher with a couple of managed cluster (1.24.4rke2). I've an error with default service account of a namespace: "Message":"clusters.management.cattle.io \"c-m-7l9g7r75\" is forbidden: User \"systemserviceaccount[namespace]:default\" cannot get resource \"clusters\" in API group \"management.cattle.io\" at the cluster scope","Cause":null,"FieldName":""} (post selfsubjectaccessreviews.authorization.k8s.io)

I created both role and rolebinding without success. I've to configure permission on the rancher console?

Hi. Has anyone successfully gotten RKE to use OIDC (Keycloak) as an authentication provider? This is separate from the Rancher front-end, just the cluster itself. I have this config set in the kube-api extra_args section:

oidc-client-id: <http://myclient.example.org|myclient.example.org>
          oidc-groups-claim: groups
          oidc-issuer-url: <https://keycloak.example.org/realms/test>
          oidc-username-claim: preferred_username

When I get a token and try to use it to authenticate (just did a kubectl --token=XXXXXXXXXX get nodes, I get a message: error: You must be logged in to the server (the server has asked for the client to provide credentials) and the kube-api server just logs this:

time="2023-01-26T18:31:29Z" level=info msg="Processing v1Authenticate request..."
time="2023-01-26T18:31:29Z" level=error msg="found 1 parts of token"

has anyone done this?

Hey gang! 🤟 Komodor’s latest open-source project, Helm-Dashboard is generally available with the release of V.1.0.0 Coincidently at the same time the project crossed 3K stars on GitHub (and hundreds of daily active users), only three months since it was released! Some of the cool new features you can expect to see in the new version: • Auto-update repositories when installed into cluster • The ability to reconfigure charts without access to their source • Specifying multiple working namespaces • Self-sufficient binary, no helm/kubectl requirement • REST API documented • As always, we welcome everyone to provide feedback and suggestions on the project’s roadmap on our social channels, GitHub, or the Slack Kommunity. We’ve even created a user survey form to make it easier on you 🙂

Does anyone know if I can use traefik 2.x as my ingress controller to access Rancher UI ? If yes how should I configure it ?

Hi y'all I am having a very hard time debugging an issue with rke-cli. I am trying to add more nodes, I am following the exact same steps as I did the first time I added them, and many times after. Except something is wrong now cuz when I run the command: rke up --update-only it does not add the new nodes

it actually complains that "Node not found" on the new nodes i have attempted to add

There are no other error logs

The cluster is functioning okay, afaik since everything else is running ( this is also in production )

I have managed to see the node for like 1-2 seconds on the node list and then it went away. The new node's kubelet complains that the node is not found as well when attempting to run kubelet

the k8s version is 1.24.4