Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-685

Update CRI-O to use one conmon per pod

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Major Major
    • openshift-4.10
    • None
    • None
    • None
    • 8
    • False
    • False
    • undefined

      In the ongoing effort to reduce the memory footprint of system level tools (CRI-O/conmon), there is the desire to change the architecture of how conmon is run. currently, there is a conmon process per container, as well as per container exec process. While this is simple, it has needless overhead (especially because of how go processes hold onto memory that they use).

       

      As a openshift user, i'd like the infrastructure keeping containers running to have as small a footprint as possible. Moving to one conmon per pod will help with this

              pehunt@redhat.com Peter Hunt
              pehunt@redhat.com Peter Hunt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: