Yaml plugin should not need to be run inside its own side car container
See original GitHub issueDescription
At the moment the yaml plugin is using eclipse/che-theia-endpoint-runtime:next
but don’t really need additional dependencies from the side car container. So it make sense to move that into the Theia-ide container.
https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/redhat/vscode-yaml/0.4.0/meta.yaml#L15
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Kubernetes Sidecar Container | Best Practices and Examples
Sidecar containers are containers that are needed to run alongside the main container. The two containers share resources like pod storage and network ......
Read more >Cannot deploy Theia plugin on Che with sidecar container
I am trying to deploy a custom Theia plugin on a Che workspace. The plugin is intended to execute a task on the...
Read more >Config Management Plugins - Argo CD - Read the Docs
Make sure that sidecar container is running as user 999. Make sure that plugin configuration file is present at /home/argocd/cmp-server/config/plugin. yaml .
Read more >ECS-V4: Observability with Sidecars in Kubernetes - YouTube
We've seen observability with logging, monitoring and tracing. They all have a common requirement - your containers needs certain behaviour, ...
Read more >Kubernetes Multi-Container Pods: Sidecar, Ambassador ...
If you need to run a single container in Kubernetes, then you have to ... do not forget to join us on our...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@amisevsk although this is correct YAML LS works on a single file so it is relatively nimble. Alternately you can consider running it inside the browser just like it is done for Openshift console.
I guess this is still relevant, since vscode-yaml is using the node sidecar these days.