config: centrally configured k8s namespace #192
Merged
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.
namespaces we centralise the namespace configuration in
REANA_INFRASTRUCTURE_KUBERNETES_NAMESPACE
so every REANA componentcan rely on it when managing REANA related Kubernetes objects.
This configuration happends at deployment time
(closes devops: deploy reana infrastructure in different namespace reana#274).
to run runtime pods in REANA (closes devops: split nodes by responsibilities (infrastructure VS runtime) reana#268).
infrastructure component names so any component can contact them
from a different namespace.