Downstream clusters flapping between available and unavailable state
This document (000020416) is provided subject to the disclaimer at the end of this document.
Management cluster K8S version: 1.21.5
Rancher Pod logs show errors like the below;
Failed to connect to peer wss://x.x.x.x/v3/connect [local ID=y.y.y.y]: websocket: bad handshake
A workaround until Rancher upgarde is to reduce the Rancher deployment replicas to one.
As of Kubernetes version v1.21, service account tokens are pod-specific, and are invalidated when the pod is deleted, which is why Rancher is unable to use it and thus unable to reach other Rancher replica instances via web-socket.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020416
- Creation Date: 25-Oct-2021
- Modified Date:27-Oct-2021
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com