Updates to install galaxy-deps separately #89
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
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.
Update the configs and documentation so that the Galaxy dependencies are installed separately from GKM. The deps should be installed cluster-wide, as Operators are supposed to be. The Galaxy chart will rely on those to instantiate necessary resources. Among following best practices, this now allows multiple instances of GKM/Galaxy to be installed on the same cluster, each in separate nodepool/namespace.
One outstanding issue is the the Postgres Cluster pod does not respectFixed in 7d455bf.nodeSelectorso it is not getting scheduled on the same node as the rest of the Galaxy deployment.