Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix resources in deployment template #12

Merged
merged 1 commit into from Dec 4, 2020

Conversation

mandre
Copy link
Member

@mandre mandre commented Dec 3, 2020

Because of this error the containers were running in best-effort QoS.

resources:
requests:
cpu: 10m
memory: 20Mi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to fix the manifests in ./assets instead. Those are the resources that the operator deploys in the cluster.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: check the EBS operator here: https://github.com/openshift/aws-ebs-csi-driver-operator

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review @bertinatto.

I've fixed the manifests in openshift/cluster-storage-operator#108 and fixed them here too while I was at it.

I'm not sure I understand your comment about ./assets - could you clarify what needs to be fixed in the assets directory?

Copy link
Member

@bertinatto bertinatto Dec 3, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I meant to say we should also update the files in this directory:

https://github.com/openshift/openstack-cinder-csi-driver-operator/tree/master/assets

This will fix the QoS for the controller and the node shown in this message:

openshift/cluster-storage-operator#108 (comment)

We can keep the changes in this file (manifests/07_deployment.yaml), but you should also update the file in CSO (as you're correctly doing in PR https://github.com/openshift/cluster-storage-operator/pull/108/files). This particular file is here just for reference as it's not used by anything.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha! I'll update accordingly.

@openshift-merge-robot
Copy link
Contributor

@mandre: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-openstack e24b6fb link /test e2e-openstack

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Because of this error the containers were running in best-effort QoS.

Also add resource constraints to the assets and align with aws-ebs's
constraints values.
@bertinatto
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2020
@bertinatto
Copy link
Member

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, mandre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2020
@openshift-merge-robot openshift-merge-robot merged commit b6d390e into openshift:master Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants