I'm trying to install rancher manager on my k3s cluster running on WSL-2 but am getting

helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=<http://k3s-rancher.homelab.int|k3s-rancher.homelab.int>

Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.25.6+k3s1

What am I doing wrong? I had previously run:

kubectl create namespace cattle-system

namespace/cattle-system created

kubectl create namespace cert-manager

namespace/cert-manager created

kubectl apply --validate=false -f <https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.crds.yaml>

<http://customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/certificaterequests.cert-manager.io> created

<http://customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/certificates.cert-manager.io> created

<http://customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/challenges.acme.cert-manager.io> created

<http://customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/clusterissuers.cert-manager.io> created

<http://customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/issuers.cert-manager.io> created

<http://customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io|customresourcedefinition.apiextensions.k8s.io/orders.acme.cert-manager.io> created

helm repo add rancher-latest <https://releases.rancher.com/server-charts/latest>

"rancher-latest" already exists with the same configuration, skipping

helm repo add jetstack <https://charts.jetstack.io>

"jetstack" has been added to your repositories

helm repo update

Hang tight while we grab the latest from your chart repositories...

...Successfully got an update from the "jetstack" chart repository

...Successfully got an update from the "rancher-latest" chart repository

Update Complete. ⎈Happy Helming!⎈

helm install cert-manager jetstack/cert-manager --namespace cert-manager --version v1.0.4

NAME: cert-manager

LAST DEPLOYED: Sat Mar 4 09:55:31 2023

NAMESPACE: cert-manager

STATUS: deployed

REVISION: 1

TEST SUITE: None

NOTES:

cert-manager has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer

or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them

can be found in our documentation:

<https://cert-manager.io/docs/configuration/>

For information on how to configure cert-manager to automatically provision

`Certificates for Ingress resources, take a look at the `ingress-shim``

documentation:

<https://cert-manager.io/docs/usage/ingress/>

Does k3s API server handle garbage collection? I have two resources, one primary and one secondary. Secondary resource has a reference to primary, but after deleting primary, the secondary is not deleted automatically. Any thoughts?

looks like rancher cant install on the latest ver of k3s?

➜  helm install rancher rancher-latest/rancher --namespace cattle-system --set hostname=rancher.whatever
Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.25.6+k3s1

What is the usage scenario of the egress-selector-mode parameter, I don’t quite understand

Hi everyone. Just making the move to port an existing application to K3S (already have a couple of other single-node applications running with it, and really happy with the experience). On this specific case though, HA is important, so I wonder if anyone could share experiences of the setup/integration with EC2 Autoscalling Groups. I’m planning on have 3 masters (all of them master/worker at the same time). I saw a project that would use bash scripts at Cloud Init, and that’s fine, but I was curious whether there was a more “obvious” way of handling this scenario. Any experience anyone could share on this sort of setup? Appreciate it!

Hi, i'm looking for some advice on how to restart k3s service from a container running inside. In a air gapped environment solution i provide a way for the user to change machine's network settings and whenever the IP changes the k3s cluster requires a restart to fully function. I've tried running a job with "systemctl restart k3s" but i get a

dbus

error (

no data available

iirc) Is there a way for me to do this? Thanks!

didn't realize this channel was available. Thank you @hundreds-evening-84071 Cross posting from #general. Apologies. is there a specific support channel for k3s? Navigating all the compatibility matrices. I have determined the following: Harvester 1.1.1 requires rancher 2.6.9 Rancher 2.6.9 requires k3s 1.20 to 1.24 K3s is certified on ubuntu 20.04 and 22.04 Since the latest stable of k3s in 1.22.3 I am installing it on Ubuntu 20.04 and it can't seem to download the hash. curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.22.3 sh - [INFO] Using v1.22.3 as release [INFO] Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.22.3/sha256sum-amd64.txt curl -k https://github.com/k3s-io/k3s/releases/download/v1.22.3/sha256sum-amd64.txt Not Found Why is it so hard to get a Rancher Manager installed to manage kubernetes nodes on a harvester cluster? This has been mind boggingly difficult.

Since the latest stable of k3s in 1.22.3

I’m not sure what you mean by that

s/in/is

1.22 is end of life. the most recent version of 1.22 is v1.22.17+k3s1, not 1.22.3

aha! ty.

Where did you see that 1.22.3 was the latest stable?

Also, you’re missing bits from the end of the version in your install command. It would be something like

INSTALL_K3S_VERSION=v1.22.17+k3s1

not

INSTALL_K3S_VERSION=v1.22.17

to be honest.... out of date information that has trained OpenAI. I turned to the bot as I didn't want to keep spamming all you fine folk.

Why anyone uses chatbots instead of looking at documentation or project repos I’ll never understand

it pointed me to all the different compatibility matrices.. so it did it's job there.

anyways.... back at it. Thanks again for your help @creamy-pencil-82913!

1.23 is end of life as well, I would probably use the latest 1.24 release. you can get that from INSTALL_K3S_CHANNEL=v1.24

with k3s cluster running on 1.22 is it okay to run this to go to latest version available in stable channel?

curl -sfL <https://get.k3s.io> | INSTALL_K3S_CHANNEL=stable sh -

or should it be done in steps? 1.22 to 1.23 to 1.24 and so on?

looking at this doc: https://docs.k3s.io/upgrades/manual

See the Kubernetes version skew policy link on that page

Running k3s on wsl-2 I'm getting:

W0311 11:54:32.405026    2510 sysinfo.go:203] Nodes topology is not available, providing CPU topology

Anyone know why?

Does anyone now if

Topology Aware Hints

works on k3s? I can’t seem to get this working. All my nodes have a different

<http://topology.kubernetes.io/zone|topology.kubernetes.io/zone>

label. Adding the annotation

<http://service.kubernetes.io/topology-aware-hints|service.kubernetes.io/topology-aware-hints>: auto

to my service should better route the traffic, but it doesn’t seem to have an effect.

ASK SW INFO: -3x Alpine vm run on VMware Workstation 17 ? 1. can I deploy k3s into those 3 vms from Rancher instead of install k3s on those 3 vms first then install Rancher. if yes any doc on that 2. I install Rancher on docker, but it takes 2.5GB RAM. The Rancher is idle Why so big

@creamy-pencil-82913 does this mean the image binary installs the crd now when launched? https://github.com/k3s-io/helm-controller/commit/09dedbf504bdaa722b99d9e7ea8bd67fba787bd2

I haven't seen this reported before...running k3s 1.25.4+k3s1 on Fedora 36 I get an error:

2023/03/03 00:09:28 Starting NATS Server Reloader v0.7.4
Error: too many open files
Stream closed EOF for testkube/testkube-nats-0 (reloader)

which prevents one of my pods (testkube/testkube-nats-0) from starting. and I'm not sure if that is specific to k3s or upstream Kubernetes. Is this a known issue or should I investigate more deeply?

quick question; Is Rancher 2.7.1 compatible with Kubernetes 1.25? I tried searching github repo readme and everything but I can’t see clear statement up to what version is compatible. I’m in the need to use cluster autoscaler function and it says it only from version Kubernetes 1.25 but it’s confusing now if I can use AS function with Rancher 2.71 and K3s... Anybody who can shine a light here please? Thanks!

Hi, When it comes to private registries, the user's credentials are stored in registries.yaml which is found in

/etc/rancher/k3s/

. But say the dev machine running k3s is shared by users with different credentials, each with access to the registries.yaml file and

/etc/rancher/k3s/

directory. How would I prevent user x from accessing/viewing user y's credentials stored in registries.yaml while at the same time using user's x credentials to pull and push to the private registry? Thanks in advance.

Greetings

I have some networking issues with a k3s setup. Is there a specific way to ask a question here?