Description
Description
The Web Terminal Tooling plugin handles /exec/init
calls by attempting to inject kubeconfig into the first container in the pod. If this fails, the whole call fails, so the plugin only works when the tooling container is first in the list.
However, the devfile/api functions for merging plugin components into a devworkspace merge components in the order 1. Parent, 2. Plugins, 3. Main content, resulting in the tooling container being last in the list. This causes web terminal to fail with changes from #240
Short-term solution
The web terminal should resolve the first compatible container (i.e. if it can't resolve an exec in the first container, it should try the second, etc.)
Long-term solution
We need a way of specifying where web terminal should inject kubeconfig.
Metadata
Metadata
Assignees
Labels
No labels