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

[release-4.6] Pao run master nodes #374

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #373

/assign fromanirh

marcel-apf and others added 3 commits September 25, 2020 07:48
PAO is meant to run on "control plane".
Use podAffinity to schedule PAO only on master nodes.
(https://docs.openshift.com/container-platform/4.5/nodes/scheduling/nodes-scheduler-pod-affinity.html)
Use taints tolerations to allow PAO scheduling on the master nodes.
(https://docs.openshift.com/container-platform/4.5/nodes/scheduling/nodes-scheduler-taints-tolerations.html)

Update the manifests according to the above.

Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
Straight forward test that checks the node PAO is running on
is a master node.

Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
The performance-operator node placement test needs
to run after the operator pod was created, hence
we move it from the 0_config suite to a later suite.

Signed-off-by: Francesco Romani <fromani@redhat.com>
@coveralls
Copy link

Pull Request Test Coverage Report for Build 541

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 70.939%

Totals Coverage Status
Change from base Build 538: 0.0%
Covered Lines: 869
Relevant Lines: 1225

💛 - Coveralls

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MarSik, openshift-cherrypick-robot

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 lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 25, 2020
@ffromani
Copy link
Member

/retest

@ffromani
Copy link
Member

please don't retest without noticing me before, we're hitting CI issues.

@ffromani
Copy link
Member

/retest

@openshift-merge-robot openshift-merge-robot merged commit db8ccff into openshift-kni:release-4.6 Sep 25, 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

7 participants