AKS Downstream Cluster not Available with Websockets failing
This document (000020767) is provided subject to the disclaimer at the end of this document.
Environment
AKS 1.22+
Situation
Testing the Websocket using these instructions will show the following error:
Bad Request {"baseType":"error","code":"ServerError","message":"websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header","status":400,"type":"error"}
Resolution
helm upgrade --install \ ingress-nginx ingress-nginx/ingress-nginx \ --namespace ingress-nginx \ --set controller.service.type=LoadBalancer \ --version 4.0.18 \ --create-namespace \ --set controller.watchIngressWithoutClass=trueAlternatively, on Rancher 2.6.7 onward, you can add the class name on the helm install/upgrade steps :
--set ingress.ingressClassName=nginx
Cause
Kubernetes version 1.22 deprecated versions of the Ingress APIs in favor of the stable networking.k8s.io/v1
API. That leads to this scenario, where we update the controller.watchIngressWithoutClass tag.
Disclaimer
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:000020767
- Creation Date: 16-Sep-2022
- Modified Date:19-Mar-2024
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com