Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54737

Bump socks5-proxy, konnectivity-proxy, http-proxy, client-token-minter memory requests

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.18.0
    • 4.18.z
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      Memory requests for several containers (socks5 proxy, konnectivity proxy, http proxy, token minter, etc.) have been updated to 30Mi to match their steady-state utilization. This change results in a total persistent memory increase of approximately 200Mi per HyperShift Control Plane (HCP).
      Show
      Memory requests for several containers (socks5 proxy, konnectivity proxy, http proxy, token minter, etc.) have been updated to 30Mi to match their steady-state utilization. This change results in a total persistent memory increase of approximately 200Mi per HyperShift Control Plane (HCP).
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-54225. The following is the description of the original issue:

      Description of problem:

          The memory requests associated with socks5-proxy, konnectivity-proxy, http-proxy, and client-token-minter containers are too low based on memory utilization of these containers in steady-state.
      
      

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          Every time.

      Steps to Reproduce:

          1. Create ROKS v4.18 HyperShift cluster.
          2. Collect control plane pod metrics.
          

      Actual results:

          Memory requests are set to 15Mi for socks5-proxy containers, 10Mi for konnectivity-proxy, http-proxy, and client-token-minter containers.

      Expected results:

          Memory requests should reflect actual memory utilization in stead-state i.e. 30Mi across socks5-proxy, konnectivity-proxy, http-proxy, and client-token-minter containers.

      Additional info:

          

              evan.reilly Evan Reilly
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Evan Reilly Evan Reilly
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: