https://rancher.com/ logo
Join the conversationJoin Slack
Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Powered by Linen
general
  • t

    tall-doctor-28108

    08/22/2022, 9:12 AM
    Good to see that Rancher 2.6.7 is out. Thanks for all the amazing work! I have one question though: Am I reading the newly formatted support matrix right? Are all 1.24.x patches officially supported? For example: https://www.suse.com/suse-rke1/support-matrix/all-supported-versions/rke1-v1-24/
    t
    • 2
    • 1
  • f

    future-account-50371

    08/22/2022, 11:02 AM
    getting error on cattle-cluster-agent-67b6c8f46-2rfj2 connecting to rancher\": x509: certificate signed by unknown authority"
    b
    • 2
    • 3
  • m

    most-sunset-36476

    08/22/2022, 11:15 AM
    Hi all, could anyone can take a look at the issue I opened in the GitHub Terraform Rancher2 provider, in case someone has already faced this issue and can help, I would greatly appreciate it! I've tried to get help here and on Reddit with no luck and I'm stuck! Thank you very much in advance!
  • i

    important-umbrella-22006

    08/22/2022, 12:34 PM
    Hello, I have RKE2 cluster I want to enable an alpha feature using feature-gate option
    TTLAfterFinished=true
    But when i change kube-controller-manager and kube-apiserver pods configuration, these gets restarted and revise configuration file to original. Does it control by fleet? can someone help me with the process of how to modify kube-controller-manager and kube-apiserver pods configuration?
    l
    • 2
    • 1
  • h

    handsome-mouse-36138

    08/22/2022, 1:35 PM
    Hi all,
  • l

    loud-belgium-84462

    08/22/2022, 2:33 PM
    Has any one integrated k8s-bigip-ctlr big ip controller with rancher kubernetes
    l
    • 2
    • 25
  • r

    rough-teacher-88372

    08/22/2022, 4:15 PM
    due to unfortunate circumstance, we have to fix a rancher system running on rke with kubernetes v1.23.8. the rancher installation on the system is version 2.6.3. A recent upgrade of the underlaying kubernetes version upgraded the ingress that shipped with the rancher installations' helm chart from networking.k8s.io/v1beta1 to networking.k8s.io/v1. Subsequent attempts to use helm upgrade to upgrade the rancher installation are failing because helm can no longer find networking.k8s.io/v1beta1 (even though neither the new version of rancher nor the current ingress resource use that version). I'm assuming that helm is using the old release manifest and is attempting to compare that while upgrading but I am not entirely sure why it is trying to use the old ingress version. The exact error message is
    Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "rancher" namespace: "" from "": no matches for kind "Ingress" in version "<http://networking.k8s.io/v1beta1|networking.k8s.io/v1beta1>"
    ensure CRDs are installed first
    I'd absolutely love any help on this
    b
    t
    • 3
    • 7
  • b

    bland-dress-30943

    08/22/2022, 8:09 PM
    is rke2 faster than rke? is it easy to deploy rke2 in production for high availability?
    l
    • 2
    • 1
  • b

    brash-monitor-41966

    08/22/2022, 8:21 PM
    i did a rke up but I dont see a load balancer or ingress getting deployed in namespace ingress-nginx. AME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default-http-backend ClusterIP 10.43.137.41 <none> 80/TCP 31h
  • b

    brash-monitor-41966

    08/22/2022, 8:22 PM
    do I need a separate loadbalancer/ingress deployment with rke?
    t
    • 2
    • 3
  • s

    some-oil-32535

    08/22/2022, 9:58 PM
    Does the Worker Node / Control Plan Node need IPv6 ? or is it safe to disable it?
    c
    • 2
    • 3
  • c

    cuddly-restaurant-47972

    08/22/2022, 10:49 PM
    Is there consensus on the most mature way to deploy rancher managed clusters (not the rancher management cluster) using automation? Terraform, Ansible, CLI, etc? Definitely would want to deploy k3s and rke2 clusters.
    s
    • 2
    • 8
  • m

    many-church-13850

    08/23/2022, 4:16 AM
    Hi Guys, any documentation on how to deploy k3 cluster using terraform?
  • f

    freezing-wolf-83208

    08/23/2022, 5:50 AM
    trying to upgrade kubernetes on my local cluster v2.6.6 - I first downloaded rke 1.3.12, we were using 1.2.2 before and running on k8s 1.19.3. and then on running the rke up command I run into WARN[0196] [etcd] host [161.211.xx.xx] failed to check etcd health: failed to get /health for host [161.211.xx.xx]: Get "https://161.211.xx.xx:2379/health": remote error: tls: bad certificate FATA[0196] [etcd] Failed to bring up Etcd Plane: etcd cluster is unhealthy: hosts [161.211.xx.xx] failed to report healthy. Check etcd container logs on each host for more information The etcd logs show that its not able to trust the CA - kube-ca is being used. tried to rotate the cert, ran into a diff issue - "FATA[0000] Failed to rotate certificates: can't find old certificates" any ideas would be greatly appreciated.
  • m

    most-sunset-36476

    08/23/2022, 6:41 AM
    Hi, all on RKE downstream cluster creation with Rancher Launched Kubernetes in an Infrastructure provider, using multiple worker pools and a Load Balancer, I get the following logs from the rancher agent on one of the stuck worker node pool (3 worker node pools, 1 worker per node pool):
    time="2022-08-19T07:04:25Z" level=warning msg="Error while getting agent config: Get \"<https://rancher.gandalf.mordor.net/v3/connect/config>\": dial tcp 20.42.142.242:443: i/o timeout"
    time="2022-08-19T07:04:28Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
    time="2022-08-19T07:04:28Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
    time="2022-08-19T07:04:38Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
    time="2022-08-19T07:04:38Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
    time="2022-08-19T07:04:48Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 20.42.142.242:443: i/o timeout"
    time="2022-08-19T07:04:48Z" level=error msg="Remotedialer proxy error" error="dial tcp 20.42.142.242:443: i/o timeout"
    time="2022-08-19T07:04:58Z" level=info msg="Connecting to <wss://rancher.gandalf.mordor.net/v3/connect> with token starting with 4sfxz9dk54w2hp9xv729k8tbgnf"
    time="2022-08-19T07:04:58Z" level=info msg="Connecting to proxy" url="<wss://rancher.gandalf.mordor.net/v3/connect>"
    time="2022-08-19T07:05:00Z" level=warning msg="Error while getting agent config: Get \"<https://rancher.gandalf.mordor.net/v3/connect/config>\": dial tcp 20.42.142.242:443: i/o timeout"
  • m

    most-sunset-36476

    08/23/2022, 6:42 AM
    Any idea ? The other worker nodes from other worker pools registers successfully, but that one get stuck in registering forever.
  • m

    most-sunset-36476

    08/23/2022, 6:47 AM
    Sometimes it happens on 2 worker nodes from two worker pools, sometimes only 1. It's totally random. When not using an external ingress load balancer, it works perfectly and all nodes are registered. I try to get help here but no one is answering any of my posts. I would really appreciate help!
  • m

    most-sunset-36476

    08/23/2022, 6:48 AM
    On the rancher cluster controller i can see the following logs about the stuck nodes:
    2022/08/22 14:45:36 [TRACE] dialerFactory: Skipping node [system1] for tunneling the cluster connection because nodeConditions are not as expected
    2022/08/22 14:45:36 [TRACE] dialerFactory: Skipping node [general1] for tunneling the cluster connection because nodeConditions are not as expected
  • m

    most-sunset-36476

    08/23/2022, 6:57 AM
    2022/08/22 13:13:03 [ERROR] failed to sync schemas: Post "<https://10.0.0.1:443/apis/authorization.k8s.io/v1/selfsubjectaccessreviews?timeout=15m0s>": unexpected EOF
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:01:59 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:00 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:02 [ERROR] error syncing 'c-fzndh/u-3svhcofub3-admin': handler cluster-crtb-sync: couldn't ensure service account impersonator: failed to get secret for service account: cattle-impersonation-system/cattle-impersonation-u-3svhcofub3, error: timed out waiting for the condition, requeuing
    2022/08/22 14:02:03 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:03 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:05 [ERROR] error syncing 'p-9w5l9/creator-project-owner': handler cluster-prtb-sync: couldn't ensure service account impersonator: failed to get secret for service account: cattle-impersonation-system/cattle-impersonation-user-ff9gr, error: timed out waiting for the condition, requeuing
    2022/08/22 14:02:07 [ERROR] error syncing 'p-29gg6/creator-project-owner': handler cluster-prtb-sync: couldn't ensure service account impersonator: failed to get secret for service account: cattle-impersonation-system/cattle-impersonation-user-ff9gr, error: timed out waiting for the condition, requeuing
    2022/08/22 14:02:08 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:08 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:18 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:18 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:02:39 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:02:39 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:03:09 [ERROR] error syncing 'c-fzndh/m-7whc7': handler rke-worker-upgrader: getNodePlan error for node [m-7whc7]: failed to find plan for 10.100.0.5, requeuing
    2022/08/22 14:03:09 [ERROR] error syncing 'c-fzndh/m-2r949': handler rke-worker-upgrader: getNodePlan error for node [m-2r949]: failed to find plan for 10.100.0.4, requeuing
    2022/08/22 14:08:51 [ERROR] Failed to handling tunnel request from remote address 10.244.0.10:55478 (X-Forwarded-For: 10.1.0.4): response 401: failed authentication
  • m

    most-sunset-36476

    08/23/2022, 7:36 AM
    BTW the [m-7whc7] and [m-2r949] are the stuck nodes.
  • c

    colossal-policeman-83714

    08/23/2022, 7:38 AM
    hi all i try upgrade rancher/rancher docker single install v2.5.x to 2.6.3 but i reviceve log:
    2022/08/23 07:40:14 [INFO] Done waiting for CRD <http://projectmonitorgraphs.management.cattle.io|projectmonitorgraphs.management.cattle.io> to become available
    2022/08/23 07:40:14 [INFO] Waiting for CRD <http://cisbenchmarkversions.management.cattle.io|cisbenchmarkversions.management.cattle.io> to become available
    2022/08/23 07:40:15 [INFO] Done waiting for CRD <http://cisbenchmarkversions.management.cattle.io|cisbenchmarkversions.management.cattle.io> to become available
    2022/08/23 07:40:15 [INFO] Waiting for CRD <http://templates.management.cattle.io|templates.management.cattle.io> to become available
    2022/08/23 07:40:15 [INFO] Done waiting for CRD <http://templates.management.cattle.io|templates.management.cattle.io> to become available
    2022/08/23 07:40:15 [INFO] Waiting for CRD <http://monitormetrics.management.cattle.io|monitormetrics.management.cattle.io> to become available
    2022/08/23 07:40:16 [INFO] Done waiting for CRD <http://monitormetrics.management.cattle.io|monitormetrics.management.cattle.io> to become available
    2022/08/23 07:40:17 [FATAL] k3s exited with: exit status 255
  • c

    colossal-policeman-83714

    08/23/2022, 7:39 AM
    when i run it with debug=true
    2022/08/23 07:41:52 [DEBUG] Loglevel set to [debug]
    2022/08/23 07:41:52 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
    2022/08/23 07:41:52 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:true Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
    2022/08/23 07:41:52 [INFO] Listening on /tmp/log.sock
    2022/08/23 07:41:52 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:41:54 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:41:56 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:41:58 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:42:00 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:42:02 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
    2022/08/23 07:42:04 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
    2022/08/23 07:42:06 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
    2022/08/23 07:42:08 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
    2022/08/23 07:42:14 [FATAL] k3s exited with: exit status 255
  • c

    colossal-policeman-83714

    08/23/2022, 7:43 AM
    I need help because the system is running. Please..
  • r

    rough-pager-2467

    08/23/2022, 9:05 AM
    Hi every one, I have an issue now, as I try to install kubernestes luster using RKE and Helm rancher, but after installation, all the services, I attached on my server via nginx auto redirecting to rancher sites what is the actual problem here. what can I do to fixed the stuff, I'm new to rancher anyway, so hope that I can have your help
  • a

    adventurous-addition-59971

    08/23/2022, 10:21 AM
    👋 Hi everyone!
  • c

    careful-optician-75900

    08/23/2022, 10:35 AM
    Hello !. Please help me. Its very urgent I really need help for that. Cos, can see logs from rancher UI. But the thing is that container logs window always disconnected again and again. So, i check the logs and then i found web socket issues. Also with that rancher failed/disconnected and then we have production web-socket endpoint, once that rancher web-socket failed and then our production web-socket also disconnected on production dashboard.
    2022/08/12 19:27:36 [ERROR] Error during subscribe write tcp 192.68.102.197:80->192.68.101.253:53682: write: broken pipe
    2022/08/12 19:27:36 [ERROR] Error during subscribe write tcp 192.68.102.197:80->192.68.101.253:53714: write: broken pipe
    2022/08/12 19:27:36 [ERROR] Error during subscribe write tcp 192.68.102.197:80->192.68.101.253:53698: write: broken pipe
    2022/08/12 19:27:49 [ERROR] Error during subscribe write tcp 192.68.102.197:80->192.68.101.253:44424: write: broken pipe
    2022/08/12 19:28:06 [ERROR] Failed to handling tunnel request from remote address 192.68.101.98:37902: response 400: cluster not found
    2022/08/12 19:28:06 [INFO] Active TLS secret serving-cert (ver=570139701) (count 12): map[<http://listener.cattle.io/cn-127.0.0.1:127.0.0.1|listener.cattle.io/cn-127.0.0.1:127.0.0.1> <http://listener.cattle.io/cn-192.68.101.118:192.68.101.118|listener.cattle.io/cn-192.68.101.118:192.68.101.118> <http://listener.cattle.io/cn-192.68.101.218:192.68.101.218|listener.cattle.io/cn-192.68.101.218:192.68.101.218> <http://listener.cattle.io/cn-192.68.101.223:192.68.101.223|listener.cattle.io/cn-192.68.101.223:192.68.101.223> <http://listener.cattle.io/cn-192.68.101.98:192.68.101.98|listener.cattle.io/cn-192.68.101.98:192.68.101.98> <http://listener.cattle.io/cn-192.68.102.146:192.68.102.146|listener.cattle.io/cn-192.68.102.146:192.68.102.146> <http://listener.cattle.io/cn-192.68.102.160:192.68.102.160|listener.cattle.io/cn-192.68.102.160:192.68.102.160> <http://listener.cattle.io/cn-192.68.102.197:192.68.102.197|listener.cattle.io/cn-192.68.102.197:192.68.102.197> <http://listener.cattle.io/cn-192.68.102.232:192.68.102.232|listener.cattle.io/cn-192.68.102.232:192.68.102.232> <http://listener.cattle.io/cn-localhost:localhost|listener.cattle.io/cn-localhost:localhost> <http://listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system|listener.cattle.io/cn-rancher.cattle-system:rancher.cattle-system> <http://listener.cattle.io/cn-listener.cattle.io/fingerprint:SHA1=|listener.cattle.io/cn-listener.cattle.io/fingerprint:SHA1=>
    2022/08/12 19:28:06 [INFO] Active TLS secret tls-rancher-internal (ver=570139702) (count 1): map[<http://listener.cattle.io/cn-10.100.249.233:10.100.249.233|listener.cattle.io/cn-10.100.249.233:10.100.249.233> <http://listener.cattle.io/fingerprint:SHA1=86080A37DFA63E45479DCAA425785F79B5AAF953|listener.cattle.io/fingerprint:SHA1=86080A37DFA63E45479DCAA425785F79B5AAF953>]
    2022/08/12 19:28:11 [ERROR] Failed to serve peer connection 192.68.101.118: websocket: close 1006 (abnormal closure): unexpected EOF
    2022/08/12 19:28:11 [INFO] error in remotedialer server [400]: read tcp 192.68.102.197:443->192.68.102.160:43614: use of closed network connection
    2022/08/12 19:28:11 [ERROR] Failed to serve peer connection 192.68.102.160: websocket: close 1006 (abnormal closure): unexpected EOF
    2022/08/12 19:28:11 [INFO] error in remotedialer server [400]: read tcp 192.68.102.197:443->192.68.101.118:50186: use of closed network connection
    2022/08/12 19:28:16 [INFO] Handling backend connection request [192.68.102.160]
    2022/08/12 19:28:16 [INFO] Handling backend connection request [192.68.101.118]
    2022/08/12 19:28:16 [ERROR] Failed to handling tunnel request from remote address 192.68.101.98:37962: response 400: cluster not found
    2022/08/12 19:28:16 [ERROR] Failed to handling tunnel request fr
  • b

    brash-monitor-41966

    08/23/2022, 12:56 PM
    I create a rke cluster on gcp. I built it using gcp ubuntu instances from a gcp bastion host and 3 other nodes all with worker, etcd, control plane roles. Now when i tried to deploy rancehr with helm, The nginx load balancer EXTernal IP shows as pending. any idea? I didnt see this whhen I deployed the load balancer for GKE
  • a

    abundant-printer-55142

    08/23/2022, 1:22 PM
    👋 Hi everyone! Just joined this channel. Have a problem setting up rancher desktop. For some reason the dashboard is not working.
    a
    • 2
    • 1
  • a

    acoustic-photographer-83125

    08/23/2022, 1:37 PM
    Hello All trying to setup k8s cluster with rke using custom system images. i am not able to override the rke-tools image can i get some help how i can override rke-tools image ?
    • 1
    • 1
  • l

    little-smartphone-40189

    08/23/2022, 2:10 PM
    So, I was running a rancher 2.5.5 cluster in an air-gapped environment (no internet) using a private AWS cloud provider. Clusters could be created using the cloud provider and properly use cluster autoscaler. After upgrading to Rancher 2.6.6, no cluster with a cloud provider can be created. It always seems to error out saying it "can't find X node" and just quits. Clusters without the cloud provider work fine. Converting a cluster to one that uses a cloud provider results in the same result (broken) and nothing else has changed on the back-end other than rancher/RKE. logs just repeat over and over that it can't find X node, and that the CNI driver can't be initialized. Any help would be appreciated
Powered by Linen
Title
l

little-smartphone-40189

08/23/2022, 2:10 PM
So, I was running a rancher 2.5.5 cluster in an air-gapped environment (no internet) using a private AWS cloud provider. Clusters could be created using the cloud provider and properly use cluster autoscaler. After upgrading to Rancher 2.6.6, no cluster with a cloud provider can be created. It always seems to error out saying it "can't find X node" and just quits. Clusters without the cloud provider work fine. Converting a cluster to one that uses a cloud provider results in the same result (broken) and nothing else has changed on the back-end other than rancher/RKE. logs just repeat over and over that it can't find X node, and that the CNI driver can't be initialized. Any help would be appreciated
View count: 16