Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2711

Support for namespace-level configuration of pod tolerations and node selector

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 3.0.0.GA
    • 3.0.0.GA
    • docs
    • False
    • False
    • Hide
      = Enabling admins to specify pod tolerations and node selector

      With this update, {prod-short} admins can specify `podTolerations` and `podNodeSelector` for workspaces by setting a `CustomCheProperty` in the `CheCluster` custom resource. This is a global configuration and cannot be specified for a workspace or user.
      Show
      = Enabling admins to specify pod tolerations and node selector With this update, {prod-short} admins can specify `podTolerations` and `podNodeSelector` for workspaces by setting a `CustomCheProperty` in the `CheCluster` custom resource. This is a global configuration and cannot be specified for a workspace or user.
    • Documented as Feature Request

    Description

      Synced from Eclipse Che issue

      https://github.com/eclipse/che/issues/20884

      Is your task related to a problem? Please describe

      As a Eclipse Che admin, I want to be able to set up the configuration of pod tolerations and node selector. Devworkspace operator expected them as k8s namespace annotations:

          metadata: 
            annotations: 
              controller.devfile.io/node-selector: |
                {
                  "test-node-selector": "test"
                }
              controller.devfile.io/pod-tolerations: |
                [
                  {
                    "key": "key1",
                    "operator": "Equal",
                    "value": "value1",
                    "effect": "NoSchedule"
                  }
                ]
      

      see more https://github.com/devfile/devworkspace-operator/pull/696

      Describe the solution you'd like

      Che-operator should grab existing configuration from che-server's env var configuration CHE_WORKSPACE_POD_NODE__SELECTOR and CHE_WORKSPACE_POD_TOLERATIONS__JSON and put them in a format expected by devworkspace operator.

      Describe alternatives you've considered

      n/a

      Release Notes Text

      It is now possible to specify pod tolerations and node selector for workspaces of a Che instance setting a CustomCheProperty in CheCluster CR. It's not possible to specify that for just one workspace or for one user: it's a global config.

      Attachments

        Activity

          People

            rhn-support-mleonov Max Leonov
            jiralint.codeready Bot Codeready
            Max Leonov Max Leonov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: