Using Plandev to debug Blueapi opens a VSCode remote server within the container. If the developer's local instance of VSCode is closed without using File > close remote connection, the remote server is not immediately terminated. (It looks like it is eventually, but potentially upwards of 7-24 hours later.)
If a subsequent connection is made, a new instance of the VSCode remote server is started. Initial testing on P46 suggests that this can be upwards of 300Mb memory use per instance. Long-running pods with multiple connections per day can quickly stack up enough VSCode remote instances to become unstable.
VSCode processes can be seen by exec'ing into the Blueapi container, running ps -ef and observing the number of commands starting with /home/ubuntu/.vscode-server/.... Memory usage can be seen in the Kubernetes / Compute Resources / Pod Grafana dashboard.
Acceptance Criteria
- Normal usage of Plandev does not cause instability
Using Plandev to debug Blueapi opens a VSCode remote server within the container. If the developer's local instance of VSCode is closed without using
File>close remote connection, the remote server is not immediately terminated. (It looks like it is eventually, but potentially upwards of 7-24 hours later.)If a subsequent connection is made, a new instance of the VSCode remote server is started. Initial testing on P46 suggests that this can be upwards of 300Mb memory use per instance. Long-running pods with multiple connections per day can quickly stack up enough VSCode remote instances to become unstable.
VSCode processes can be seen by exec'ing into the Blueapi container, running
ps -efand observing the number of commands starting with/home/ubuntu/.vscode-server/.... Memory usage can be seen in theKubernetes / Compute Resources / PodGrafana dashboard.Acceptance Criteria