User reports:

• When using Dev Spaces 3.2, VSCode will fail to pull plugins
• OpenShift cluster proxy has a custom CA
• we can connect to plugin download URL endpoint from main workspace container runtime and download it via command line <<<<<<<<<------------

Please find attached an encrypted file with screenshots, a log file.

User verbatims:

"We upgraded our OpenShift Dev Spaces operator to version 3.2.0 on Tuesday of this week. Afterwards, when we spun up a workspace using VSCode IDE, we are now no longer able to install plugins through the IDE. This includes all of the plugins available in the Extensions Marketplace in VSCode, including the PHP-Debug (felixfbecker.php-debug) plugin we were using."

"With the previous version of Dev Spaces (3.1.0), we were able to install plugins successfully. So it is unclear why the same process is failing with Dev Spaces 3.2.0."