We first need to determine the name of these namespaces, for both the staging and production releases.
For reference, Superset is deployed in the superset-next and superset namespaces, whereas Spark-History is deployed into spark-history and spark-history-test.
Usually, we try to make sure these namespaces match the wikimedia.org subdomain, so e.g. something like mpic and mpic-test/mpic-next, etc.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| mpic: provision staging and production namespaces | operations/deployment-charts | master | +2 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T361335 Deploy the MP Instrumentation Configuration application to the DSE k8s cluster | |||
| Resolved | brouberol | T361337 Create MPIC Kubernetes namespaces |
Change #1016932 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/deployment-charts@master] mpic: provision staging and production namespaces
Change #1016932 merged by Brouberol:
[operations/deployment-charts@master] mpic: provision staging and production namespaces
root@deploy2002:~# kube_env admin dse-k8s-eqiad root@deploy2002:~# kubectl get namespaces | grep mpic mpic Active 78m mpic-next Active 78m