Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3501

Is it possible to configure kubeApiQps and kubeApiBurst for the vertical-pod-autoscaler (VPA)?

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected
    • Hide

      IHAC has a query related to who is using the vertical-pod-autoscaler-opertaor & trying to configure QPS or Burst but since the OLM-operator reverts all my changes on the VPA-operator.
      Is it possible to configure QPS or Burst for VPA in a proper way that is persisted, without turning off the OLM-operator?
      Supporting document which is referred by the customer:
      VPA support setting kube API QPS and kube API Burst, ref.
      https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/admission-controller/main.go#L61 And the VPA-operator can pass these arguments to the VPA via `VERTICAL_POD_AUTOSCALER_EXTRA_ARGS`, ref.

      https://github.com/openshift/vertical-pod-autoscaler-operator/blob/cefe7fbe971fe30aa6bf9a3058a6c4b35570ef01/pkg/operator/config.go#L58

       

      Show
      IHAC has a query related to who is using the vertical-pod-autoscaler-opertaor & trying to configure QPS or Burst but since the OLM-operator reverts all my changes on the VPA-operator. Is it possible to configure QPS or Burst for VPA in a proper way that is persisted, without turning off the OLM-operator? Supporting document which is referred by the customer: VPA support setting kube API QPS and kube API Burst, ref. https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/admission-controller/main.go#L61 And the VPA-operator can pass these arguments to the VPA via `VERTICAL_POD_AUTOSCALER_EXTRA_ARGS`, ref. https://github.com/openshift/vertical-pod-autoscaler-operator/blob/cefe7fbe971fe30aa6bf9a3058a6c4b35570ef01/pkg/operator/config.go#L58  

      Is it possible to configure QPS or Burst for VPA in a proper way that is persisted, without turning of the OLM-operator?
       
      As of now If the customer is making any changes the OLM reverts all the changes because of the vertical-pod-autoscaler-operator.  
       
      Supporting document which is referred by the customer:
      VPA support setting kube API QPS and kube API Burst, ref.
      https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/admission-controller/main.go#L61 And the VPA-operator can pass these arguments to the VPA via `VERTICAL_POD_AUTOSCALER_EXTRA_ARGS`, ref.

      https://github.com/openshift/vertical-pod-autoscaler-operator/blob/cefe7fbe971fe30aa6bf9a3058a6c4b35570ef01/pkg/operator/config.go#L58
      .
       

       

       

            gausingh@redhat.com Gaurav Singh
            rhn-support-vsolanki Vimal Solanki
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: