Skip to content

Conversation

JPinkney
Copy link
Contributor

@JPinkney JPinkney commented Jul 22, 2021

What does this PR do?

This PR cherry-picks all the relevant commits I could find from upstream che-machine-exec into main.

  1. Adapt Che Machine Exec to devworkspace workspace engine eclipse-che/che-machine-exec#130
  2. removing env.Name check to adapt to che sidecar env var removal eclipse-che/che-machine-exec#142
  3. Adapt to DWO change where new label is devworkspace_id eclipse-che/che-machine-exec#138
  4. Fix issue where /exec/init calls put kubeconfig in first container eclipse-che/che-machine-exec#129

Currently trying Web Terminal 1.3 leads to a crash loop backoff with unable to get current workspace id. Configure custom pod selector or che workspace id without these changes

What issues does this PR fix or reference?

Is it tested? How?

Release Configuration Management and others added 30 commits June 11, 2020 00:18
* Fix devworkspace api group to fix idling

Signed-off-by: Josh Pinkney <[email protected]>

* Move from 1.0 version format to 1.0.0

Signed-off-by: Josh Pinkney <[email protected]>

* Add in go modules for automatic security validation

Signed-off-by: Josh Pinkney <[email protected]>
* Add initial version of Jenkinsfile source sync

Signed-off-by: Josh Pinkney <[email protected]>
Signed-off-by: Josh Pinkney <[email protected]>
(cherry picked from commit 66b64be296efbec51558aa07d5b11c023af8c0a3)
Signed-off-by: Josh Pinkney <[email protected]>
Signed-off-by: Josh Pinkney <[email protected]>
(cherry picked from commit ccc183e)
Signed-off-by: Josh Pinkney <[email protected]>
Add stopped-by annotation and fix vulnerabilities
Signed-off-by: Josh Pinkney <[email protected]>
Remove dockerfile from root so that we can use CPaaS templating
Update web-terminal-exec version to 1.3
Add github action for creating next dockerimage
Change dockerfile base image and login to quay securely
amisevsk added 3 commits July 22, 2021 10:49
When /exec/init is called (e.g. in the web terminal operator), it
resolves the first container that supports a shell, but does not use
this container for injecting kubeconfig. When no container name is
provided, the kubeconfig is injected into the first container, which
causes kubeconfig injection to fail when the first container in the pod
does not support a shell.

Signed-off-by: Angel Misevski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants