Hello there. I have a strange issue: When I want to upgrade my cluster to a newer Kubernetes Version only 2 of my 4 worker nodes get upgraded. Master-Node and ETCD-Node get upgraded without issues. Rancher means after upgrading 2 out of 4 the update is done and gives no error. In Rancher UI and with "kubectl get nodes" all my worker nodes seem healthy. I checked the clusterSpec in Rancher API UI, there the 2 nodes are also missing Anyone has an idea? Would be very appreciated Rancher Verison: 2.5.16 Kubernets Version: 1.18.12

When we need to use these annotation ? I have some issues with web-sockets. When i check proxy server logs, i got "*Error* getting SSL certificate "default/*-tls": local SSL certificate default/*-tls was not found. Using default certificate" and it keeps updating ingress to classic load balancer and got disconnected every 1mins after upgrading rancher version.

annotations:
    <http://field.cattle.io/projectId|field.cattle.io/projectId>: ""

Updating local copy of SSL certificate to classic load balancer every 1 mins. How to troubleshoot these issues ? Nginx-ingress logs: 8 controller.go:177] Configuration changes detected, backend reload required. 8 backend_ssl.go:189] Updating local copy of SSL certificate "cattle-system/tls-rancher-ingress" with missing intermediate CA certs I0830 050732.859819 8 controller.go:195] Backend successfully reloaded.A Any ideas for SSL Uploading every 1 mins ? Many thanks

Hello All, When running a helm upgrade command on my rancher cluster, I am getting the following

Error: UPGRADE FAILED: create: failed to create: the server responded with the status code 413 but did not return more information (post secrets

) ....Has anyone seen this error before and any ideas on how can I troubleshoot it further will be helpful

I'm trying to point a banzai logging operator

Output

to a custom S3 endpoint. Has anyone managed to do this? Running into issues

apiVersion: <http://logging.banzaicloud.io/v1beta1|logging.banzaicloud.io/v1beta1>
kind: Output
metadata:
  annotations:
    <http://field.cattle.io/description|field.cattle.io/description>: OVH Object Storage PoC
  name: ovh-banzai-objectstorage-output
spec:
  s3:
    aws_key_id:
      valueFrom:
        secretKeyRef:
          key: accessKeyId
          name: logging-ovh-s3
    aws_sec_key:
      valueFrom:
        secretKeyRef:
          key: secretAccesKey
          name: logging-ovh-s3
    s3_bucket: mybucket
    s3_endpoint: <https://storage.gra.cloud.ovh.net/>
    s3_region: gra
status:
  active: true

OVH's Object Storage definitely works with the

aws s3

CLI, so it stands to reason Banzai operator "should" be compatible with it too. The S3 API is the S3 API. Disappointingly, this config doesn't seem to work. If you see what's wrong with my config would appreciate it 🙂

Hello, 👋 I would like to drop a label on my metrics despite my configuration the label id is still present

- job_name: test-drop
        honor_timestamps: true
        scrape_interval: 10s
        metric_relabel_configs:
          - action: labeldrop 
            regex: id

container_memory_usage_bytes{container="alertmanager", endpoint="https-metrics", id="/kubepods/burstable/pod6088fe00-1184-4dd7-99de-31ea8ac2faa6/00b165c3291d6e004f5ce9bdac7c470cba18266ba128ba1c8b4bc19ccff1af21", image="<http://quay.io/prometheus/alertmanager:v0.24.0|quay.io/prometheus/alertmanager:v0.24.0>", instance="10.240.0.18:10250", job="kubelet", metrics_path="/metrics/cadvisor", name="00b165c3291d6e004f5ce9bdac7c470cba18266ba128ba1c8b4bc19ccff1af21", namespace="monitoring", node="aks-main-84901719-vmss000002", pod="alertmanager-prom-operator-alertmanager-0", service="prom-operator-kubelet"}

Hi I am trying to install rancher getting below error any suggestions WARN[0028] Can't pull Docker image [rancher/rke-tools:v0.1.87] on host [10.130.156.101]: Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 10.130.156.10158820 >3.215.51.67443: read: connection reset by peer docker is not able to pull the images ..?

any one faced this issue ?

Hey eveyone is there any way i can pass rancher username at the time of installation. I am using helm chart for install rancher. Command:

helm upgrade --install rancher rancher-latest/rancher   --namespace cattle-system   --set hostname=url   --set ingress.tls.source="letsEncrypt" --set bootstrapPassword=abcdxyz  --set letsEncrypt.email="email"   --set letsEncrypt.environment="production"

Hi. I see these CRDs in my clusters:

[I] ➜ k get crd |grep coreos
<http://alertmanagers.monitoring.coreos.com|alertmanagers.monitoring.coreos.com>                             2021-11-04T11:05:32Z
<http://podmonitors.monitoring.coreos.com|podmonitors.monitoring.coreos.com>                               2022-09-13T14:46:07Z
<http://probes.monitoring.coreos.com|probes.monitoring.coreos.com>                                    2022-09-13T14:46:08Z
<http://prometheuses.monitoring.coreos.com|prometheuses.monitoring.coreos.com>                              2021-11-04T11:05:32Z
<http://prometheusrules.monitoring.coreos.com|prometheusrules.monitoring.coreos.com>                           2021-11-04T11:05:32Z
<http://servicemonitors.monitoring.coreos.com|servicemonitors.monitoring.coreos.com>                           2021-11-04T11:05:32Z

are they there by default? How can I disable them? (interfering with grafana-agent)

Only if you installed either our monitoring stack or the upstream prometheus operator

I've got a physical cluster with etcd/controlplane roles on some of the physical machines. I'd like to move these roles off to some VMs. What would be the proper steps to do this? Do I need to add the new VMs first, then remove the physical node(s)? Or the other way around?

Hi , pls share terraform code to deploy rancher using ingress-nginx on EKS . I want to use self-signed cert

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

Anyone using KEDA with the HTTP add on for auto scaling of web deployments? I've implemented it and it works but I am not sure of how to Determine the best value for the pending requests threshold. Any suggestions?

Hey, what it takes to call sonarqube apis from inside the aks. Right now, I am passing client id and secret and api key in the headers but it is giving me 401. Any help will be really appreciate! Note: I am having cloud flared as a firewall in between aks and sonarqube...

Hi , I have a issue which is I make deployment to rancher, code base is laravel. my application run for 6 hrs or 5 hrs and its stop working on rancher. when i redeploy application its start working again what should be the error. i have one pod running against application. Please help Thanks

How to set pod level proxy details in rancher environment. We have already tried throough env variable but still no luck . Please let me know is there any other way to add proxy details.

Hey everyone Why does my Rancher deployment creating a certificate chain with two certificates where in the past it created only one?

Hi, just realized that my Rancher UI lacks all Rancher Repositories I use to have there (Rancher v2.6.8). I<m trying to find out the repo infos to recreate them, but cannot find any infos on these...

Hi All, I have a kubeadm created cluster on 1.24.2 (The current supported kubernetes version for 2.6.8), and Rancher installed and is currently running. When I click on the individual nodes, each of them report "n/a" under cpu and ram, and when I look at the dashboard, it reports total ram I have, but not the total used ram. Did I install rancher incorrectly?

@here Im using rancher desktop and trying to pull image, but I can see pull image taking too long and share steps how to login with user.

Hi, I'm running Rancher 2.6.5 and I have a cluster provisioned to AKS. I did upgrade this cluster from Kubernetes 1.20.9 to 1.22.15. Unfortunately the update on Azure has been blocked due to a Network-Policy. After removing the network-Policy the update finished on AKS, but the cluster state on Rancher is still stuck on 'This cluster is currently Updating'. Everything works fine, but I have no clue how to tell Rancher that this cluster has succesfully been updated. Anybody has an idea? Many thanks! Hans-Peter

Hey all, Some time ago, we at Komodor, started working on a new OSS project called Helm-Dashboard. Now, it’s finally ready for users, and I’m excited to share with the world. You can see its GitHub repo here: https://github.com/komodorio/helm-dashboard So Helm-Dashboard is basically a GUI for Helm, and it’s designed to solve some of the more acute painpoints 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. I invite everyone who is using Helm to give it a try and share your feedback. Feel free to open GitHub issues, send PRs, ask questions in a dedicated #helm-dashboard channel on our Slack Kommunity: https://join.slack.com/t/komodorkommunity/shared_invite/zt-1dm3cnkue-ov1Yh~_95teA35QNx5yuMg Give it a ⭐ if you liked it :) Or consider upvoting on HackerNews: https://news.ycombinator.com/show

How do i replace existing Rancher certificates? the whole chain the documentation is unclear

Can rancher ui implemented on eks?

Does anyone have any examples of creating resource requests of gpu memory? I am able to schedule on gpu nodes and run computation on the gpu, but currently I can get cuda oom with my current resource limit definitions as pods can be schedule on nodes no matter how much gpu memory I have available:

resources:
  limits:
    <http://nvidia.com/gpu|nvidia.com/gpu>: 1

I would like to request/limit to a certain amount of gb, instead of a whole device.

Need to forward stderr and stdout Rancher 2.6 UI Console Logs to a fluentd pod running in the same namespace, tried with the Banzai login marketplace app, but looks not working, any thoughts?

Hi guys, I have Rancher 2.4.5 running on my server. Currently I am trying to import my AKS cluster in. my rancher is running under custom port 8000. when I execute the rancher cluster agent to AKS, the agent failed to connect to rancher (CATTLE_SERVER). After deeper check, the agent attempt to connect to the domain name without the port being included. No wonder the connection is failing. Any idea how to make the agent connect to the complte address we provide as the CATTLE_SERVER, with the port number?