Uploaded image for project: 'OpenShift Autoscaling'
  1. OpenShift Autoscaling
  2. AUTOSCALE-433

Enable component e2e suites for VPA

XMLWordPrintable

    • AUTOSCALE - Sprint 279

      The current VPA suite we run in our CI is only the full-vpa suite.

      There are individual suites that test component-specific functionlity for each component: https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/e2e/v1

      This card documents what we need to do in order to run these downstream.

      1. Allow the VPA Operator e2e hack script to be able to run other suites: https://github.com/openshift/vertical-pod-autoscaler-operator/blob/07793e4051b7227f16a0f86e505d1de824b15a1c/hack/e2e.sh
      2. Fix/Disable some tests downstream that fail/do not work in our downstream kubernetes-autoscaler repo.
      3. Create prow jobs for each component suite for VPA-operator in the openshift/release repo. 

       

      This card doesn't document running VPA tests in our kubernetes/autoscaler fork. Perhaps that's something to think about, but for now it is not trivial to do because we have to figure out how to properly deploy VPA from that repo, since it does not contain references to our operator.

              rh-ee-macao Max Cao
              rh-ee-macao Max Cao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: