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

OCPBUGS-3990: Add HyperShift specific priorityClass #167

Merged

Conversation

jsafrane
Copy link
Contributor

HyperShift needs guest cluster control plane components with priority "hypershift-control-plane", https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/

@openshift/storage

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Nov 29, 2022
@openshift-ci-robot
Copy link
Contributor

@jsafrane: This pull request references Jira Issue OCPBUGS-3990, 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.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ropatil010

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

In response to this:

HyperShift needs guest cluster control plane components with priority "hypershift-control-plane", https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/

@openshift/storage

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 29, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 29, 2022
return nil
}

}
Copy link
Member

Choose a reason for hiding this comment

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

IMO the withHypershiftDeploymentHook function would be a better place for this, what do you think?

Copy link
Contributor Author

@jsafrane jsafrane Nov 30, 2022

Choose a reason for hiding this comment

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

Agreed.

Initialy, I saw a separate withHypershiftReplicasHook, so it looks like the idea was to have fine-grained hooks. But it looks weird to have them that fine grained.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed & pushed

@@ -169,6 +171,7 @@ func RunOperator(ctx context.Context, controllerConfig *controllercmd.Controller
controlPlaneInformersForEvents,
withHypershiftDeploymentHook(isHypershift, os.Getenv(hypershiftImageEnvName)),
withHypershiftReplicasHook(isHypershift, guestNodeInformer.Lister()),
withHypershiftPriorityClass(isHypershift),
Copy link
Member

Choose a reason for hiding this comment

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

You forgot to remove this line

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oops, fixed

HyperShift needs guest cluster control plane components with priority
"hypershift-control-plane", https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/
Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 1, 2022
@openshift-merge-robot openshift-merge-robot merged commit e2f4558 into openshift:master Dec 1, 2022
@openshift-ci-robot
Copy link
Contributor

@jsafrane: All pull requests linked via external trackers have merged:

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

In response to this:

HyperShift needs guest cluster control plane components with priority "hypershift-control-plane", https://hypershift-docs.netlify.app/how-to/distribute-hosted-cluster-workloads/

@openshift/storage

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.

@jsafrane
Copy link
Contributor Author

jsafrane commented Dec 6, 2022

/cherry-pick release-4.12

@openshift-cherrypick-robot

@jsafrane: new pull request created: #170

In response to this:

/cherry-pick release-4.12

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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

5 participants