Proposal for Implementing Multiple Broker Deployment Strategies in Akri #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Kate Goldenring <kate.goldenring@gmail.com>
Signed-off-by: Kate Goldenring <kate.goldenring@gmail.com>
|
This document should be broken down into several separate proposals:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This document discusses how to add support for multiple broker deployment strategies in Akri. It ultimately
proposes a phased approach with 5 phases of building up the Configuration CRD, Instance CRD, Agent,
and Controller to support all strategies. It assumes the support of terminating Pods via Jobs.
References #17 for background on implementing Job Brokers.