Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kubernetes ingress manifest created for workspace is not compatible with nginx-ingress >= 0.22.0 #13094

Closed
ddelbondio opened this issue Apr 8, 2019 · 1 comment
Closed

Kubernetes ingress manifest created for workspace is not compatible with nginx-ingress >= 0.22.0 #13094

ddelbondio opened this issue Apr 8, 2019 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@ddelbondio
Copy link

Description

The nginx ingress has a backwards incompatible change in 0.22.0, which causes the ingress created for the workspace to redirect all requests to / instead of /[PATH] on ws-agent of the workspace pod.
See kubernetes/ingress-nginx#3174 (comment) for more details on how to fix it in a backwards compatible way.

Reproduction Steps

Starting a workspace with nginx ingress 0.22.0 or later will produce:

2019-04-08 18:23:40,220[aceSharedPool-1]  [WARN ] [.i.k.KubernetesInternalRuntime 242]  - Failed to start Kubernetes runtime of workspace workspacezo2ddqelvg0eaakc. Cause: Server 'wsagent/http' in machine 'dev-machine' not available.

Using any previous version works (tested using nginx ingress 0.21.0).

OS and version:
Linux, Kubernetes (v1.10.11), che 7.0.0-beta-2.0
@ddelbondio ddelbondio changed the title Kubernetes ingress manifest created work workspace is not compatible with nginx-ingress >= 0.22.0 Kubernetes ingress manifest created for workspace is not compatible with nginx-ingress >= 0.22.0 Apr 9, 2019
@che-bot
Copy link
Contributor

che-bot commented Oct 9, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2019
@che-bot che-bot closed this as completed Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ddelbondio @che-bot