Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to set environment variables into Eclipse Che core components using CheCluster #21605

Closed
tolusha opened this issue Aug 3, 2022 · 1 comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@tolusha
Copy link
Contributor

tolusha commented Aug 3, 2022

Is your task related to a problem? Please describe

There a couple of requests [1] and [2] to set environment variables into Eclipse Che containers. Currently we have a way to do so [3] by creating a ConfigMap or Secret. But it does not work for Gateway containers and it is harder than setting them via CheCluster CR.

[1] #21260
[2] #21530
[3] https://www.eclipse.org/che/docs/stable/administration-guide/mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container/#mounting-a-secret-or-a-configmap-as-an-environment-variable-into-a-container_che

Describe the solution you'd like

Allow to set environment variables into Eclipse Che containers by configuring CheCluster CR.
For instance, setting environment variables for containers will look like:

spec:
  components:
    dashboard:
      deployment:
        containers:
          -  env:
              - name: <NAME>
                value: <VALUE>
    che-server:
      deployment:
        containers:
          -  env:
              - name: <NAME>
                value: <VALUE>
  networking:
    auth:
      gateway:
        deployment:
          containers:
            - name: oauth-proxy
              env:
                - name: <NAME>
                  value: <VALUE>

Release Notes Text

An admin can now specify arbitrary environment variables that will be applied to the containers of the core components of Eclipse Che. Those environment variables can be specified in the CheCluster Custom Resource.

@tolusha tolusha added kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/next area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Aug 3, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 3, 2022
@azatsarynnyy azatsarynnyy added severity/P1 Has a major impact to usage or development of the system. sprint/next and removed sprint/next status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 3, 2022
@tolusha tolusha added this to the 7.52 milestone Aug 6, 2022
@tolusha tolusha closed this as completed Aug 6, 2022
@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Aug 18, 2022
@l0rd l0rd changed the title Allow to set environment variables into Eclipse Che containers Allow to set environment variables into Eclipse Che core components using CheCluster Aug 18, 2022
@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
@devstudio-release
Copy link

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-3271

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants