Anatolii Bazko

Let's keep this issue open until we add a section to the Eclipse Che documentation about proxy configuration. Currently we mention proxy only here [1] [1] https://eclipse.dev/che/docs/stable/administration-guide/checluster-custom-resource-fields-reference/#checluster-custom-resource-components-cheServer-proxy-settings

@LMantovan There is no way to configure image registry for DevWorkspace operator image. But it is possible to achieve in the following steps; 1. Download DWO templates `https://github.com/devfile/devworkspace-operator/blob/main/deploy/deployment/kubernetes/combined.yaml` 2. Replace...

Hello, @vinay-keshava What was your command to start a minikube cluster? Did `chectl server:deploy` command completed successfully? Could you run `chectl server:logs` and attach obtained logs?

+1

@AObuchow Can we close the issue?

@bbsclient Thank you for reporting.

For [1] and [2], all critical and high level vulnerabilities comes from base image [3]. [1] https://trivy.dev/results/?image=quay.io/eclipse/che-operator:7.59.0 [2] https://trivy.dev/results/?image=quay.io/devfile/devworkspace-controller:v0.18.1 [3] registry.access.redhat.com/ubi8-minimal:8.7-1049

For [1], simply building a fresh image will reduce the number for critical vulnerabilities to 1, like for base image [2] [1] https://trivy.dev/results/?image=quay.io/che-incubator/configbump:0.1.4 [2] https://trivy.dev/results/?image=alpine:3.12

It is not possible to reproduce on 7.83.0

Hello, @debkantap This is the correct link `https://artifacthub.io/packages/helm/eclipse-che/eclipse-che`