-
Bug
-
Resolution: Done
-
Critical
-
DWO 0.14.0, 3.0.0.GA
-
False
-
None
-
False
-
-
Documented as Known Issue
-
Workaround Exists
-
- Log in to cluster
- Apply config map into user's workspace
- Try to start a devfile
Related upstream issues:
- Automount envFrom fields can appear in random order
- Order of volumeMounts, etc. is not consistent in deployment, resulting in repeated changes
After the configmap is applied, the workspace starts rapidly creating and terminating workspace pods
kind: ConfigMap apiVersion: v1 metadata: name: disconnected-env annotations: controller.devfile.io/mount-as: env labels: controller.devfile.io/mount-to-devworkspace: 'true' controller.devfile.io/watch-configmap: 'true' data: MAVEN_OPTS: >- -Duser.home=/home/user -Djavax.net.ssl.trustStore=/home/user/.m2/truststore.jks -Djavax.net.ssl.trustStorePassword=changeit
This environment variable is necessary for a correct build of a maven based project https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.15/html/end-user_guide/using-artifact-repositories-in-a-restricted-environment_crw#using-self-signed-certificates-in-maven-projects_crw
Workaround:
Add an env variable directly into a devfile in the dashboard
- is related to
-
RHDEVDOCS-4120 Add Using artifact repositories in a restricted environment examples in the Mounting Secrets procedure
- Closed