Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1505

Builds in SNO should have configurable resource constraints

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • None
    • None
    • MCO Sprint 268, MCO Sprint 269, MCO Sprint 270, MCO Sprint 272
    • 0

      In a single-node OpenShift (SNO) deployment, cluster admins prefer to have tight control over the resources for the various workloads running within that deployment due to the limited available resources. Currently, we have no way of allowing a cluster admin to set resource requests or limits on the image build process. We could potentially expose this by embedding the corev1.ResourceRequirements struct (or a subset thereof) into the MachineOSConfig object.

       

      Done When:

      • We've embedded the aforementioned struct (or an equivalent) into the MachineOSConfig object.
      • Or, we've determined that a different approach is better.
      • Or, we've determined that this is not actually necessary.

              zzlotnik@redhat.com Zack Zlotnik
              zzlotnik@redhat.com Zack Zlotnik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: