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

docs: document some advanced scheduling techniques #2183

Merged
merged 1 commit into from
Jul 25, 2022

Conversation

tzneal
Copy link
Contributor

@tzneal tzneal commented Jul 25, 2022

Description

Documents the usage of Exists in provisioners and a method for a spot to on-demand split for a workload.

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: #
  • No

Release Note


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@tzneal tzneal marked this pull request as ready for review July 25, 2022 18:51
@tzneal tzneal requested a review from a team as a code owner July 25, 2022 18:51
@tzneal tzneal requested a review from bwagner5 July 25, 2022 18:51
@netlify
Copy link

netlify bot commented Jul 25, 2022

Deploy Preview for karpenter-docs-prod ready!

Name Link
🔨 Latest commit 53a1566
🔍 Latest deploy log https://app.netlify.com/sites/karpenter-docs-prod/deploys/62deea6096b5920009f0a0ae
😎 Deploy Preview https://deploy-preview-2183--karpenter-docs-prod.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@tzneal tzneal force-pushed the add-advanced-scheduling-doc branch from 12b2393 to 53a1566 Compare July 25, 2022 19:09
Copy link
Contributor

@ellistarn ellistarn left a comment

Choose a reason for hiding this comment

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

Nice!

@ellistarn ellistarn merged commit c25e50b into aws:main Jul 25, 2022
@tzneal tzneal deleted the add-advanced-scheduling-doc branch July 25, 2022 22:50
@FernandoMiguel
Copy link
Contributor

@tzneal can these "virtual domains" be used for kubernetes.io/arch too ?

@FernandoMiguel
Copy link
Contributor

ref: #2024

@tzneal
Copy link
Contributor Author

tzneal commented Jul 28, 2022

@FernandoMiguel Yes, they would work for any label. It doesn't do quite the same thing as weighting provisioners, it instead gives ratio'd topology spreads.

@FernandoMiguel
Copy link
Contributor

I believe I gave it a try a few days ago, and it didn't really work as expected.
All instances were of the same arch

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.

None yet

3 participants