SHIP-0039: Blog post build scheduler options features and guidelines

[adambkaplan]

Feature

As the code changes related to shipwright-io/community#213 merge, we should prepare a blog post showing how developers can use the specific features. In particular:

1. Steer builds to specific nodes, such when using Shipwright with multi-arch worker nodes
2. Allow builds to tolerate a node taint
3. Allow builds to be scheduled with a custom scheduler, optimized for CI/CD, batch, or other workloads.

[ayushrakesh]

@adambkaplan I want to work on this issue, do we need to create a blogpost for this?

[adambkaplan]

@ayushrakesh eventually yes, we should have a blog post for this feature. However, it needs to be implemented first! At present the community isn't ready to commit this feature to a specific, upcoming release.

[adambkaplan]

@ayushrakesh are you still interested in working on this? The node selector feature is now available with Builds v0.14.0.

Maybe @dorzel too?

[dorzel]

@adambkaplan I could certainly work on this. Are we thinking that it should be a single blog post encompassing all of the features (along with the accompanying shp CLI changes) or more piece-by-piece as they get incorporated into shipwright releases?

[adambkaplan]

Are we thinking that it should be a single blog post encompassing all of the features (along with the accompanying shp CLI changes) or more piece-by-piece as they get incorporated into shipwright releases?

I'm open to either. I don't think the node selector flag made it to the CLI in v0.14.0 - that would be really nice to showcase if it lands in v0.15.0

[dorzel]

Ok - maybe I can do one for each feature/CLI feature pair, as I'm planning on doing the CLI PRs after the current Tolerations and Custom Scheduler PRs merge.

[adambkaplan]

Moving this to the backlog - this would be a great addition to our content if folks in the community have time to write it up. That said, it isn't a hard requirement for releasing.

[dorzel]

Starting to scope this out and create a draft. Obviously the CLI changes aren't quite in yet, but starting on this early.