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

orchestratord support alternative schedulers #30961

Conversation

alex-hunt-materialize
Copy link
Contributor

@alex-hunt-materialize alex-hunt-materialize commented Jan 7, 2025

Add support to the helm chart for alternative kubernetes schedulers.

Motivation

Part of the migration to using orchestratord in SaaS. We use a custom scheduler there.

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@@ -224,6 +224,9 @@ rbac:
# -- Whether to create necessary RBAC roles and bindings
create: true

# use a non-default kubernetes scheduler
Copy link
Contributor

Choose a reason for hiding this comment

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

let's use the -- notation to pull this into our generated docs, and can call out it's only needed when using a custom scheduler

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@alex-hunt-materialize alex-hunt-materialize force-pushed the support_alternative_schedulers branch 3 times, most recently from 557d6a1 to bcc5c5f Compare January 7, 2025 17:11
@alex-hunt-materialize alex-hunt-materialize marked this pull request as ready for review January 7, 2025 17:11
@alex-hunt-materialize alex-hunt-materialize merged commit 596c2cb into MaterializeInc:main Jan 13, 2025
10 checks passed
@alex-hunt-materialize alex-hunt-materialize deleted the support_alternative_schedulers branch January 13, 2025 09:58
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