OCPBUGS-33742: setting higher priority class for external-dns pods

[mukrishn]

What this PR does / why we need it:
Hypershift operator pods are created with higher PriorityClass but external-dns, to create a successful HCP we need both of them to up and available. Due to default priority class on external-dns, this pod gets evicted by the scheduler to fit higher priorityClass pods when there is no available space on suitable nodes.

Now setting the same priorityClassName used by the operator pod for external-dns pod as well.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # OCPBUGS-33742

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[openshift-ci-robot]

@mukrishn: This pull request references Jira Issue OCPBUGS-33742, which is invalid:

• expected the bug to target the "4.17.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

What this PR does / why we need it:
Hypershift operator pods are created with higher PriorityClass but external-dns, to create a successful HCP we need both of them to up and available. Due to default priority class on external-dns, this pod gets evicted by the scheduler to fit higher priorityClass pods when there is no available space on suitable nodes.

Now setting the same priorityClassName used by the operator pod for external-dns pod as well.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # OCPBUGS-33742

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

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 openshift-eng/jira-lifecycle-plugin repository.

[csrwng]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, mukrishn

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:

• OWNERS [csrwng]

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

[csrwng]

/jira refresh

[openshift-ci-robot]

@csrwng: This pull request references Jira Issue OCPBUGS-33742, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.0) matches configured target version for branch (4.17.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request.

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[mukrishn]

/retest

[enxebre]

/retest
/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c698d1d and 2 for PR HEAD 2a737f1 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c5401ca and 1 for PR HEAD 2a737f1 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f91af53 and 0 for PR HEAD 2a737f1 in total

[openshift-ci]

@mukrishn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure	2a737f1	link	false	/test e2e-azure

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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

/hold

Revision 2a737f1 was retested 3 times: holding

[csrwng]

/hold cancel
/retest-required

[openshift-ci-robot]

@mukrishn: Jira Issue OCPBUGS-33742: All pull requests linked via external trackers have merged:

• openshift/hypershift#4050

Jira Issue OCPBUGS-33742 has been moved to the MODIFIED state.

In response to this:

What this PR does / why we need it:
Hypershift operator pods are created with higher PriorityClass but external-dns, to create a successful HCP we need both of them to up and available. Due to default priority class on external-dns, this pod gets evicted by the scheduler to fit higher priorityClass pods when there is no available space on suitable nodes.

Now setting the same priorityClassName used by the operator pod for external-dns pod as well.

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # OCPBUGS-33742

Checklist

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

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 openshift-eng/jira-lifecycle-plugin repository.