Make Namespace configurable or infer it from Kubernetes confguration
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Benedikt Wetzel added Master Project 20/21 Theodolite Kotlin To Do labels
added Master Project 20/21 Theodolite Kotlin To Do labels
- Benedikt Wetzel mentioned in merge request !85 (merged)
mentioned in merge request !85 (merged)
- Owner
Best solution would be to infer it from the Kubernetes config/the used ServiceAccout. If that's not possible, we could pass it to Theodolite via an environment variable, which could also be automatically set, as shown here: https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/
env: - name: MY_POD_NAMESPACE valueFrom: fieldRef: fieldPath: metadata.namespace
- Lorenz Boguhn mentioned in merge request !91 (merged)
mentioned in merge request !91 (merged)
- Benedikt Wetzel added In Progress label and removed To Do label
added In Progress label and removed To Do label
- Benedikt Wetzel closed
closed
- Benedikt Wetzel removed In Progress label
removed In Progress label
- Sören Henning added modul/theodolite label
added modul/theodolite label
- Sören Henning changed milestone to %0.5.0
changed milestone to %0.5.0
- Owner
Have you checked if the namespace can derived from the "execution context", e.g. from the Kubernetes Client library?
- Developer
Yes, i didn`t found any way to directly derive it. Therefore I decided to use the DownwardAPI as suggestet at https://stackoverflow.com/questions/31557932/how-to-get-the-namespace-from-inside-a-pod-in-openshift.
- Owner
Ok, thanks