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

Make it possible to remove cpu limit from che-gateway container

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Specifying workspaces gateway and project-clone containers

      With this update of the `CheCluster` Custom Resource, a `gatewayContainer` and `projectCloneContainer` sections are added under `.spec.devEnvironments`. This enhancement allows the administrators to specify the details of the container that will host the workspace reverse proxy (gateway) and the container that clones the remote Git repositories:

      [source, yaml, subs="+quotes"]
      ----
      spec:
        devEnvironments:
          gatewayContainer:
              __<container_settings>__
          projectCloneContainer:
              __<container_settings>__
      ----

      [TIP]
      ====
      You can use this enhancement to remove the CPU limits for the containers:

      [source, yaml]
      ----
      spec:
        devEnvironments:
          gatewayContainer:
            resources:
              limits:
                cpu: "0"
      ----
      ====
      Show
      = Specifying workspaces gateway and project-clone containers With this update of the `CheCluster` Custom Resource, a `gatewayContainer` and `projectCloneContainer` sections are added under `.spec.devEnvironments`. This enhancement allows the administrators to specify the details of the container that will host the workspace reverse proxy (gateway) and the container that clones the remote Git repositories: [source, yaml, subs="+quotes"] ---- spec:   devEnvironments:     gatewayContainer:         __<container_settings>__     projectCloneContainer:         __<container_settings>__ ---- [TIP] ==== You can use this enhancement to remove the CPU limits for the containers: [source, yaml] ---- spec:   devEnvironments:     gatewayContainer:       resources:         limits:           cpu: "0" ---- ====
    • Enhancement
    • Done

      Description of problem:

       

      Each Workspace pod comes with che-gateway container attached. It has cpu limit set to 500m. CPU Limits are generally considered as harmful. This CPU Limit is set unreasonably high - we've never seen this container have more than few millicores consumption and moreover it breaks the openshift scheduler due to increased likelihood of overcommitted nodes.

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Create Workspace pod - there is che-gateway container with CPU Limit set.

      Actual results:

      Che-gateway container of Workspace pod has CPU Limit set to 500m

      Expected results:

      Che-gateway container of Workspace pod has no CPU Limit set

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

            mloriedo Mario Loriedo
            rhn-support-agiertli Anton Giertli
            Maksym Musienko Maksym Musienko
            Jana Vrbkova Jana Vrbkova
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: