I’m trying to determine if I’ve found a bug in 2.6.6 with Cloud Credentials. I’m trying to add credentials for an

AzureUSGovernmentCloud

environment. I get a

400 Subscription ID does not exist

, and I see nothing in the request that identifies the request as the

AzureUSGovernmentCloud

environment. This is all I see in the body:

{
  "clientId": "my client id",
  "clientSecret": "my client secret",
  "subscriptionId": "my subscription id"
}

My suspicion is that the request is being sent to Azure Public Cloud, which is why the subscription doesn’t exist. Does anyone know what I might be missing? I have ran through the creation/registration on Azure Public Cloud several times using the exact same method and it works fine every time, so it seems like an issue specific to non-public Azure clouds.

So the documentation shows how to do setup Rancher on Nutanix AHV, but not seeing what I need according to the documentation.

The Rancher agent is deployed on a downstream Kubernetes cluster. It calls the Rancher server to communicate with Rancher. It looks like it cannot communicate with Rancher because the server URL is localhost

Hi, is there a way to log user activities on Rancher, like who logged in and from which IP and what they looked at and changed ?

This is under rancher UI. Local cattle cluster can't communicate to rancher server. How can i add rancher-server-url for local cattle-cluster ? Cos, it's provisioning and getting this

Hello, how can i clean the whole rancher from cluster?

Has anyone been able to update the max-pods setting when using EKS? After following the steps outlined in the AWS docs: https://docs.aws.amazon.com/eks/latest/userguide/cni-increase-ip-addresses.html I now can't get the change applied due to the Rancher managed Launch Templates. I can update the launch template to set the max-pods limit in the bootstrap script, but I can't apply this to the Autoscale Group created by Rancher as EKS complains about it being out of sync. Anyone got this working?

Who knows about this error?

2022-08-10T12:11:24.268Z: Kubernetes was unable to start: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
    at ChildProcess.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:142946|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:142946>)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  stdout: '',
  stderr: " * rc-service: service `k3s' does not exist\n",
  code: 1,
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    'shell',
    '--workdir=.',
    '0',
    'sudo',
    '/sbin/rc-service',
    '--ifstarted',
    'k3s',
    'stop'
  ]
}
2022-08-10T12:24:35.069Z: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1

❯ curl -sfL <https://get.k3s.io> | sh -
[ERROR]  Can not find systemd or openrc to use as a process supervisor for k3s

❯ uname -a
Darwin KR-LPGQ21XYVW 21.4.0 Darwin Kernel Version 21.4.0: Mon Feb 21 20:35:58 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T6000 arm64

is there anywhere I can educate myself on the inner workings related to persistent volumes in rke clusters provisioned by rancher on top of harvester, using the harvester-ci/longhorn based storage system?

scaling up and down we’ve ended up with some missing volumes, and we’re struggling to restore them from backup in longhorn, then have the downstream cluster workloads mount/recognize them

Hi. Is there a dedicated channel for https://github.com/rancher/rancher in this slack?

Is there a way to determine the Rancher user that deployed an “application”, i.e. chart? adding a label to annotation or some indication of the user might be valuable.

Hello Team, seeing the following error trying to deploy a RKE2 cluster from rancher on my harvester cluster:

Error with pre-create check: "the server could not find the requested resource (get <http://settings.harvesterhci.io|settings.harvesterhci.io> server-version)"

I’m unable to find any reference to this error in any of the system logs, its only present on the UI while the cluster is trying to get deployed.

finally got a ceph rbd storageclass working cleanly in rancher, whew that was a wild ride of tshooting

Hi, I have a few rancher clusters deployed on EC2 (RKE1) and now I'm working towards implementing a VPN in my company (Pritunl) and I was looking to restrict access to rancher nodes from outside, looking into the

rancher-nodes

security group, I see a few rules that give access to

0.0.0.0/0

TCP 30000 - 32767 TCP 80 TCP 443 TCP 6443 TCP 2376 Are those rule safe to modify with my VPN server IP ? or are there more steps to it? thanks

harvesterHCI 1.0.3 is available, but it dont see a upgrade button in the right corner. is the upgrade not yet available via the dashboard?

What would be some tips to speed up Rancher running on GKE ? I have 3 replicas.

data.rancher2_cluster.cluster: Still reading... [20s elapsed]
data.rancher2_cluster.cluster: Still reading... [30s elapsed]
data.rancher2_cluster.cluster: Still reading... [40s elapsed]
data.rancher2_cluster.cluster: Still reading... [50s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m0s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m10s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m20s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m30s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m40s elapsed]
data.rancher2_cluster.cluster: Still reading... [1m50s elapsed]
data.rancher2_cluster.cluster: Still reading... [2m0s elapsed]
data.rancher2_cluster.cluster: Still reading... [2m10s elapsed]
data.rancher2_cluster.cluster: Read complete after 3m10s [id=c-xxxx]

Is there a channel for jobs?

Hi, is there a way to stop and start containers in Rancher2, like we used to have in 1.6?

I am trying to add new master node in the highly available k3s setup (I am using postgres as database to store the state of k3s) and here is the command curl -sfL https://get.k3s.io | sh -s - server --datastore-endpoint='postgres://k3s:ypassword@192.168.11.5:5432/k3s' I m using to add new master node but it is giving me following error so can you someone look into it and help ??

systemd[1]: k3s.service: Service hold-off time over, scheduling restart. systemd[1]: k3s.service: Scheduled restart job, restart counter is at 97783. systemd[1]: Stopped Lightweight Kubernetes. systemd[1]: Starting Lightweight Kubernetes... sh[23500]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service sh[23500]: /bin/sh: 1: /usr/bin/systemctl: not found k3s[23512]: time="2022-08-11T071900Z" level=info msg="Starting k3s v1.24.3+k3s1 (990ba0e8)" k3s[23512]: time="2022-08-11T071900Z" level=info msg="Configuring postgres database connection pooling: maxIdleConns=2, maxOpenConns= k3s[23512]: time="2022-08-11T071900Z" level=info msg="Configuring database table schema and indexes, this may take a moment..." k3s[23512]: time="2022-08-11T071900Z" level=info msg="Database tables and indexes are up to date" k3s[23512]: time="2022-08-11T071900Z" level=info msg="Kine available at unix://kine.sock" k3s[23512]: time="2022-08-11T071900Z" level=fatal msg="starting kubernetes: preparing server: bootstrap data already found and encryp " systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: k3s.service: Failed with result 'exit-code'.

systemd[1]: Failed to start Lightweight Kubernetes.

Hello everyone! 🙂 Just have a couple of quick (and probably silly newb) questions around the Rancher Cluster agent on Rancher 2.6 when running against a generic imported k3s cluster. 1. How do the agents authenticate themselves with the Rancher server during setup and then once they are running please? It’s not completely clear from the docs here: https://rancher.com/docs/rancher/v2.6/en/overview/architecture/#2-cluster-controllers-and-cluster-agents 2. Also, does Rancher handle upgrades of cluster and fleet agents on each downstream cluster itself or is that something we need to handle as part of regular operations? Thanks in advance!

Hey, is there a way to upgrade RKE clusters to a new k8s version from the `cluster-explorer-`ui like it was possible in

cluster-manager

? I cannot find anything. We're on 2.5.15. Any help appreciated.

Hello everyone, is it possible to change/replace with different hosts all RKE and Rancher downstream cluster master hosts gradually one after other?

Hello 🙂 Which version of K3s contains the most updated versions of the following packages please?

<http://docker.io/rancher/klipper-helm|docker.io/rancher/klipper-helm>
<http://docker.io/rancher/klipper-lb|docker.io/rancher/klipper-lb> 	
<http://docker.io/rancher/local-path-provisioner|docker.io/rancher/local-path-provisioner> 	
<http://docker.io/rancher/mirrored-coredns-coredns|docker.io/rancher/mirrored-coredns-coredns> 	
<http://docker.io/rancher/mirrored-library-busybox|docker.io/rancher/mirrored-library-busybox> 		
<http://docker.io/rancher/mirrored-library-traefik|docker.io/rancher/mirrored-library-traefik> 	
<http://docker.io/rancher/mirrored-metrics-server|docker.io/rancher/mirrored-metrics-server>	
<http://docker.io/rancher/mirrored-pause|docker.io/rancher/mirrored-pause>

With NavLinks you can add links to the navigation list on the left of the web UI. The config allows you to set the target for the link, i.e. _self, _parent, etc. is there a way to replace the main div as opposed to use a new window or replace the existing?

Hey everyone, Just updated rancher to v2.5.7, I usually dump the yaml from Helm template and do my own kubectl apply after adding ALB ingress changes. (I didn’t add cert manager) and getting for

helm-operation

pods.

Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Waiting for Kubernetes API to be available
Timeout waiting for kubernetes

Appreciate any help on how can I fix this.

Do you have a namespace filter set? (top of page)

Good afternoon channel, we've got a brand new AWS EKS cluster that we attempted to import into Rancher, and getting this error: Cluster must have at least one managed nodegroup. Googling the error produced some opened/closed issues, but nothing on how to really get it fixed/import successfully. Rancher version is v2.6.4 EKS is also integrated with SpotInst, so no plans on creating NodeGroups via console/rancher per se Any suggestions ?