Skip to content

Forward priority to k8s #6012

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

Closed
wants to merge 9 commits into from
Closed

Forward priority to k8s #6012

wants to merge 9 commits into from

Conversation

SeungjinYang
Copy link
Collaborator

Tested (run the relevant ones):

  • Code formatting: install pre-commit (auto-check on commit) or bash format.sh
  • Any manual or new tests for this PR (please specify below)
  • All smoke tests: /smoke-test (CI) or pytest tests/test_smoke.py (local)
  • Relevant individual tests: /smoke-test -k test_name (CI) or pytest tests/test_smoke.py::test_name (local)
  • Backward compatibility: /quicktest-core (CI) or pytest tests/smoke_tests/test_backward_compat.py (local)

Base automatically changed from resources-priority to master June 16, 2025 17:47
@SeungjinYang SeungjinYang force-pushed the k8s-priority branch 3 times, most recently from 650a619 to ce0b266 Compare June 16, 2025 19:30
@SeungjinYang
Copy link
Collaborator Author

/quicktest-core

@SeungjinYang SeungjinYang requested a review from cg505 June 17, 2025 22:26
Copy link
Collaborator

@cg505 cg505 left a comment

Choose a reason for hiding this comment

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

looks sick

Comment on lines +509 to +510
logger.info('_configure_priority_class: '
f'{updating_existing_msg(priority_class_field, name)}')
Copy link
Collaborator

Choose a reason for hiding this comment

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

info level?

Comment on lines +191 to +193
- apiGroups: [ "scheduling.k8s.io" ]
resources: [ "priorityclasses" ]
verbs: [ "list", "create", "patch" ]
Copy link
Collaborator

Choose a reason for hiding this comment

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

will this get updated correctly? Do we need to update any permissions docs or whatever? (Helm chart??)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants