Issue
Issue
- Pods return to the Initializing status even though containers in the pod are running
- Overlay connectivity broken after a node reboot until flannel is restarted
- I have the alert 'Node Disk is Running Full in 24 hours', what does this mean?
- Bind on Port 80 Fails Due to Permissions in NGINX Ingress
- Controlplane/Etcd nodes are stuck at provisioning for a new cluster
- kube-apiserver "socket: too many open files" error messages
- How to prevent NetworkManager from interfering with Kubernetes cluster networking interfaces
- Missing container metrics in Rancher monitoring for AKS clusters in Rancher v2.2 - v2.4
- `Get secret: secrets "webhook-receiver" not found` errors observed in Rancher v2.4 and v2.5 server logs
- Rancher v2.x provisioned vSphere cluster nodes stuck in provisioning, with "Waiting for SSH to be available", as a result of pre-existing cloud-init configuration in VM Template
- Rancher v2.5 provisioned Kubernetes clusters, without a worker role node, display "Cluster health check failed: cluster agent is not ready" error
- Rancher log forwarding to an Elasticsearch endpoint stops functioning as a result of connection reload behaviour in Rancher v2.3, prior to v2.3.8, and v2.4, prior to v2.4.4
- How To Fix Hairpin Connectivity with IPVS enabled
- Resolving "Conflict. The container name is already in use" errors when updating a Rancher Kubernetes Engine (RKE) CLI or Rancher v2.x provisioned Kubernetes cluster
- 401 Unauthorized error using the Rancher2 Terraform Provider v1.4.0 with `access_key` and `secret_key` authentication
- nginx-ingress-controller pods failing to load configuration with "client intended to send too large body" error in nginx-ingress-controller < nginx-0.32.0-rancher1
- Logs not forwarded by Rancher Logging in Rancher v2.x when Docker daemon logging driver is not set to json-file
- "ERROR: XFS filesystem at /var has ftype=0, cannot use overlay backend" error messages logged by the Docker daemon upon daemon startup
- Troubleshooting - Nodes wont join cluster or show unavailable
- Loading the new Rancher Dashboard in an airgapped environment redirects to /fail-whale
- Slow etcd performance (performance testing and optimization)
- Filesystem actions in containers fail with `Too many levels of symbolic links`
- Kernel crash after "unregister_netdevice: waiting for lo to become free. Usage count"
- Experimental Dashboard feature causes memory leak in rancher server and cattle-cluster-agent processes in Rancher v2.4.0 - v2.4.2
- Logging integration doesn't work if Docker Root is not default /var/lib/docker
- Error in driver during machine creation: Error launching instance: InvalidParameterValue: Invalid value 'r5.12xlarge ' for InstanceType.
- Istio fails to deploy with restricted PodSecurityPolicy in Rancher v2.3 and v2.4
- Resolving conntrack table full error messages: 'nf_conntrack: table full, dropping packets'
- Pod network connectivity non-functional as a result of sysctl net.ipv4.ip_forward=0
- Rancher pre v1.6.22 "Hosts stuck Reconnecting" Rancher server logs show 'Cursor returned more than one result'