Skip to content

Commit

Permalink
Fix resources in cinder csi deployment template
Browse files Browse the repository at this point in the history
This should fix the "Managed cluster should ensure control plane pods do
not run in best-effort QoS" CI test that is currently failing with:

    5 pods found in best-effort QoS:
    openshift-cluster-csi-drivers/openstack-cinder-csi-driver-controller-5bfc8fdf46-k9h6f is running in best-effort QoS
    openshift-cluster-csi-drivers/openstack-cinder-csi-driver-node-gqmzg is running in best-effort QoS
    openshift-cluster-csi-drivers/openstack-cinder-csi-driver-node-hn5pp is running in best-effort QoS
    openshift-cluster-csi-drivers/openstack-cinder-csi-driver-node-nsffx is running in best-effort QoS
    openshift-cluster-csi-drivers/openstack-cinder-csi-driver-operator-7f968db7f-hkvmj is running in best-effort QoS

https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-4.7/1334497702402068480

Also bump the memory requirements to 50Mi to align with aws-ebs.
  • Loading branch information
mandre committed Dec 3, 2020
1 parent bc8d42c commit c2031b2
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 4 additions & 4 deletions assets/csidriveroperators/openstack-cinder/07_deployment.yaml
Expand Up @@ -39,6 +39,10 @@ spec:
image: ${OPERATOR_IMAGE}
imagePullPolicy: IfNotPresent
name: openstack-cinder-csi-driver-operator
resources:
requests:
cpu: 10m
memory: 50Mi
priorityClassName: system-cluster-critical
serviceAccountName: openstack-cinder-csi-driver-operator
nodeSelector:
Expand All @@ -49,7 +53,3 @@ spec:
- key: node-role.kubernetes.io/master
operator: Exists
effect: "NoSchedule"
resources:
requests:
cpu: 10m
memory: 20Mi
8 changes: 4 additions & 4 deletions pkg/generated/bindata.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit c2031b2

Please sign in to comment.