The currently-used machine-exec component is left-over from an earlier iteration of the Web Terminal Operator, where it was expected that the Operator itself would provide the terminal UI (i.e. the CloudShell UI)

As OpenShift requirements limit the implementation to using OpenShift Console terminal functionality for connecting to Web Terminals, much of the functionality in the exec component is unused. This makes the component both more complex and harder to maintain that it needs to be.

The exec component should be rewritten to provide the minimal functionality required for establishing a Web Terminal session. Criteria: the exec component should

• Expose the existing /exec/init endpoint for proxying a user's OpenShift token
• Expose the existing /activity/tick endpoint for tracking terminal inactivity
• Shut down the terminal workspace if the inactivity timeout is reached
• Support detecting the tooling container in the workspace, and provision user configuration to allow the user's login to be propagated to the terminal session
• Support readiness/health endpoints to confirm availablity