Genome Nexus Changes #38
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
- Create separate namespace for genome nexus. It is possible there have been some problems with having two mongo helm charts running (session-service and genome-nexus). Maybe having these in separate namespaces will help. - gn-vep seemed to restart a lot so increase timeouts - since genome nexus is in a new namespace the ingress had to be updated as well
zhx828
approved these changes
Nov 12, 2019
|
@zhx828 from what I understand the ingress has to be in the same namespace as the service it's pointing to: kubernetes/kubernetes#17088 |
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.
been some problems with having two mongo helm charts running
(session-service and genome-nexus). Maybe having these in separate
namespaces will help.
as well