[wip] start pulling kubernetes logic out of environmentd's kubernetes orchestrator into orchestratord #30900
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
having two separate systems managing our kubernetes resources has been a pain. also, this is one prerequisite to moving to an environmentd-less world (since we probably don't want the balancers doing our kubernetes operations), and should also allow us to have better separation of permissions (since we will eventually be able to remove ~all kubernetes access from environmentd itself).
Tips for reviewer
this is very much a work in progress and not ready to merge - i've sketched out the shape of the implementation, but haven't tried using it yet. opening this now to get feedback on the overall direction - if this looks reasonable, if there are other things i should consider, etc.
Checklist
$T ⇔ Proto$T
mapping (possibly in a backwards-incompatible way), then it is tagged with aT-proto
label.