Closed khteh closed 1 year ago
@khteh, for websockets support :
- ensure ingress has rule for the initial request path to the websocket
- host: myapp.com http: paths:
- backend: service: name: svc-myapp port: number: 443 pathType: Prefix path: /*
- configure larger idle timeout (default is 60 seconds), or setup heartbeat from the application layer Done.
Why does it change to wss://
scheme? Is that the root cause?
@khteh, based on your ingress snippet, your pathType
is Prefix
, but the path is /*
. This is not a valid configuration, you can't specify *
with Prefix
path type in ingress. Could you verify the ingress got reconciled successfully?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Describe the bug Running a ASP.Net Core 7 web application behind ALB in EKS cluster bumps into the following error seen in chrome debugger:
Running the same application on my local development host does not have this error at all.
The ALB ingress has the following annotation:
and the following kubernetes
Service
:Steps to reproduce
Expected outcome A concise description of what you expected to happen.
Environment
eksctl 0.120.0
Additional Context: