-
Notifications
You must be signed in to change notification settings - Fork 996
Closed
Labels
s2Broken use cases or features (with a workaround). Only humans may set this.Broken use cases or features (with a workaround). Only humans may set this.
Description
Version: v0.26.1+a0fedeb
The use case is I have EKS deployment and created a wsproxy in GKE.
I can successfully curl the wsproxy and pull up the dashboard message in a browser that redirects me to the EKS deployment's access url.
However in the wsproxies dashboard, it continued to show:
UNHEALTHY
Not available
Errors
unexpected status code 400
Which was expected when I first installed the wsproxy and had not yet created DNS entries.
I had to scale the EKS deployment from 2 to 0 replicas and scaled up to 2, and then the wsproxy showed healthy.
Metadata
Metadata
Assignees
Labels
s2Broken use cases or features (with a workaround). Only humans may set this.Broken use cases or features (with a workaround). Only humans may set this.