With this setup, the dnsPolicy is set to ClusterFirst, which I understand

[4:05 PM] I followed the instructions in https://github.com/kurokobo/awx-on-k3s to setup AWX in a k3s cluster. With this setup, the dnsPolicy is set to ClusterFirst, which I understand to mean that if the fqdn cannot be resolved in the cluster, try and resolve it via the internet. The problem I have is that we have a large number of nodes in a domain that is not resolvable from the internet. At the moment I’m having to use IP addresses, which works but is not ideal. My understanding is that if the dnsPolicy is set to Default, the cluster will use the DNS settings in the host. Unfortunately I know next to nothing about Kubernetes (but I’m learning). How do I override or change the dnsPolicy?

Where would I find info about admission controllers in k3s? I understand these for vanilla k8s, but the k3s docs talk about “admission control plugins”. I haven’t found where these are documented yet. Could someone point me in the right direction?

issues with Deploying RKE2 with Metallb Issue - IP gets assigned to the loadbalancer but no ARP entries are showing up under the interfaces, ARP ping and curl fails to the deployed loadbalancer IP + port IP Pool and L2Advertisement config

apiVersion: <http://metallb.io/v1beta1|metallb.io/v1beta1>
kind: IPAddressPool
metadata:
  name: core-net-192.168.92.140-159
  namespace: metallb-system
spec:
  addresses:
  - 192.168.94.140-192.168.94.159
---
apiVersion: <http://metallb.io/v1beta1|metallb.io/v1beta1>
kind: L2Advertisement
metadata:
  name: metallb-pool
  namespace: metallb-system
spec:
  ipAddressPools:
  - core-net-192.168.99.140-159

How can we enable kubeproxy ipvs on the management cluster? (at the moment i only have one cluster with workernodes added to the management cluster)

kubeproxy:
      extra_args:
        ipvs-scheduler: lc
        proxy-mode: ipvs

do i need to deploy a separate cluster with workernodes for this?

I am getting following error when importing a cluster to rancher

2.6.6

:

level=error msg="Failed to connect to proxy. Response status: 400 - 400 Bad Request. Response body: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' headerError during upgrade for host [c-m-w9nnqvqq]: websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header" error="websocket: bad handshake"

Any idea what this could be related to ?

I try to use a custom image of hyperkube (based on kubernetes release v1.23.15 and rancher_hyperkube release v1.23.15-rancher1) to override kubernetes version "v1.23.15-rancher1-1". However, when I run "rke up --update-only", I see following error:

FATA[0011] Failed to reconcile etcd plane: getDefaultKubernetesServicesOptions: No ServiceOptions found for cluster version [v1.23.15-rancher1-1] or cluster major version [hyperkube-v1.23]

Please share the insight and how to fix it.

Hi Team, Rancher (version: 2.7.1) went down. It was working fine with an EKS cluster. All I see in the rancher logs is the below. Could you please provide some pointers here? 2023-03-13T161351.423780681Z stdout F 2023/03/13 161351 [ERROR] error syncing 'c-jftcc': handler cluster-deploy: Get "https://5DD450D2C5E6834B8501244FF80BC0A0.gr7.us-east-1.eks.amazonaws.com/apis/apps/v1/namespaces/cat tle-system/daemonsets/cattle-node-agent": dial tcp: lookup 5DD450D2C5E6834B8501244FF80BC0A0.gr7.us-east-1.eks.amazonaws.com on 10.43.0.1053 no such host, requeuing 2023-03-13T161351.473835741Z stdout F 2023/03/13 161351 [ERROR] error syncing 'c-jftcc': handler eks-operator-controller: [Syncing error: syncing failed] RequestError: send request failed Not sure where <5DD450D2C5E6834B8501244FF80BC0A0.gr7.us-east-1.eks.amazonaws.com> is coming from.

Is there a way to update the management cluster yaml file? I get stuck on "Waiting for API" when trying to import an existing K3s cluster. I cannot create a new management cluster because of a "POST method not supported" error. It looks like the management cluster is using an incorrect IP address

Hi, I have installed “Rancher Desktop” in my Macbook. I’m getting the below exception, Any suggestion,

Error Starting Kubernetes
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
Last command run:
/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> start --tty=false /Users/jayachandran.nachimu/Library/Application Support/rancher-desktop/lima/_config/0.yaml

Context:
Starting virtual machine

Some recent logfile lines:
   'time="2023-03-13T15:54:42-04:00" level=fatal msg="instance name \\"0\\" too long: \\"/Users/jayachandran.nachimu/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456\\" must be less than UNIX_PATH_MAX=104 characters, but is 104"\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>',
    'start',
    '--tty=false',
    '/Users/jayachandran.nachimu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ]
}

Deployed RKE1 via vmware/rancher integration. Any idea how i can re deploy RKE to a node? It's a control node and it still has all the data, just something happened to where the certs don't match the config for the set ip of the node.

Hi All, We are planning to upgrade our EKS cluster from 1.23 to 1.25 but when I checked Rancher official document it says Rancher 2.7.1 only supports 1.23 . So, wanted to check if thats correct?

Hello, I've successfully setup rancher backups to a custom S3 endpoint, it is working perfectly fine but when I try to create a restore job from one of the backups it fails, throwing an error:

Failed to download s3 backup: no backup files found with prefix [/rancher-backup-9ca2915d-3a70-48be-828c-6b8a85e7319a-2023-03-14T08-19-08Z.tar.gz] in bucket [backups]

Can anyone help me figure out what is the problem?...

I double checked and the filename is correct, it's stored in the backups target with that exact name.

Hi folks, Could any help me with resources where I can look into, to understand the features and pricing of Rancher. I don't want to go via sales talk, document would really help.

Hi guys

I wonder if anyone here can help please. We have an existing cluster deployed with rke running cluster_cidr 10.12.0.0/16 and service_cluster_ip_range 10.13.0.0/16, and we would like to change both cluster_cidr and service_cluster_ip_range to new subnets (10.14.0.0/16 and 10.15.0.0/16). Is there a way for us to do that without tearing the cluster down and re-deploy with new settings?

Hey everyone ! I'm having an issue with Rancher and cluster management with node that stays stuck in "Deleting" state, underlaying VM is removed but nodes stays in "Deleting" state in the machine pool. More informations in the thread

does anyone know when Rancher 2.7.2 will be released?

Hi, does anybody know how to test helm charts in Rancher 2.7.0? Can I apply them in UI?

i was wondering if its possible to use traefik as an ingress controller with metallb with RKE2 ? I cant seem to find any guides or docs about changing those things.

The Rancher doc says in the automatic upgrades section:

Danger

If the K3s cluster was imported into Rancher, Rancher will manage the system-upgrade-controller deployment and plans. Do not follow the steps on this page.

I imported my k3s cluster and it appears in Rancher, but the system-upgrade controller is not running in k3s. And there is no option to upgrade k3s in the Rancher cluster management dashboard. Any idea why this would happen?

Can I change the ingress hostname by simply editing the yaml file where it is defined and then running

kubectl apply -f <filename>

?

Morning

To add, we deployed kubernetes 1.24.4 using rke 1.3.15, and then all our applications. We need to change the current cluster_cidr and service_cluster_ip_range to new subnets, but would like to avoid tearing down the cluster and re-deploying our applications and their components. Does any one know how best to do this, if it is possible. Or point me to any documentations that might help us. Thanks in advance.

👋 Hi everyone!

I am new to Rancher …I need to setup multi node k8s cluster with rke command line ..now which is the best rke or rke2 …if I don’t opt for separate load balancer

I think with RKE only one master can add into kubeconfig ..now if i need to add another master how can i do

Greetings.

Anyone else has problems installing Cert Manager from Apps in Rancher 2.7.1 on GKE? Install fails but I can't see any errors