Deploy into azimuth management cluster #66
Conversation
This file contains hidden or 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
…imuth-cloud/azimuth-apps-operator into feat/azimuth-cluster-installs
|
Ran out of time to finish this before the end of my internship, this project is being passed to @wtripp180901 |
wtripp180901
force-pushed
the
feat/azimuth-cluster-installs
branch
from
0431e32 to
d94d88e
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.
A patch that allows Helmreleases to be deployed directly into the management cluster, typically used to deploy other FluxCD resources targetting a remote cluster. Motivated by our Slinky app requiring multiple Flux managed helm installs due to CRD dependencies which prevent it from being packaged under a single umbrella Helm chart.
Adds
managementInstallto the AppTemplate spec. If true, the targetted Helm chart must implementkubeconfigandtargetNamespacefields.