Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config: centrally configured k8s namespace #192

Merged

Conversation

diegodelemos
Copy link
Member

@diegodelemos diegodelemos commented Jun 9, 2020

@diegodelemos diegodelemos marked this pull request as ready for review June 9, 2020 13:24
reana_commons/config.py Outdated Show resolved Hide resolved
@diegodelemos diegodelemos force-pushed the r/274-configurable-namespace branch 2 times, most recently from 37e7c59 to b0dfda6 Compare June 11, 2020 14:08
* In order to be able to deploy REANA in different Kubernetes
  namespaces we centralise the namespace configuration in
  `REANA_INFRASTRUCTURE_KUBERNETES_NAMESPACE` so every REANA component
  can rely on it when managing REANA related Kubernetes objects.
  This configuration happends at deployment time
  (closes reanahub/reana#274).
@diegodelemos diegodelemos force-pushed the r/274-configurable-namespace branch 2 times, most recently from 8c2347e to d358ecc Compare June 11, 2020 14:22
CHANGES.rst Outdated Show resolved Hide resolved
reana_commons/config.py Outdated Show resolved Hide resolved
Diego Rodriguez added 2 commits June 19, 2020 10:36
* Creates a new configuration variable to hold the namespace used
  to run runtime pods in REANA (closes reanahub/reana#268).

* Creates a central configuration variable for fully qualified
  infrastructure component names so any component can contact them
  from a different namespace.
@diegodelemos diegodelemos merged commit a1ca63e into reanahub:master Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants