[DM-49745] Refactor Sasquatch sub charts #4474
Merged
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
afausti
force-pushed
the
tickets/DM-49745
branch
from
bda12af to
cd63803
Compare
afausti
force-pushed
the
tickets/DM-49745
branch
from
cd63803 to
d7e7712
Compare
- Also disable kafka-connect-manager in usdf-int since it is not being used there. Fix up user references
- The replicator password must be same in both source and target clusters
afausti
force-pushed
the
tickets/DM-49745
branch
from
feec717 to
32b0ed8
Compare
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.
In this PR we propose a better organization of the Sasquatch sub charts to make it more explicit which Phalanx applications depend on Sasquatch by creating a sub chart for each application.
Centralize application specific configuration in their sub charts.
Also add a new sub chart for the event-driven tap implementation.