gitlab-runner merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests2017-01-18T05:58:57Zhttps://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/389Kubernetes Namespace Overwrite2017-01-18T05:58:57Zusername-removed-764633Kubernetes Namespace Overwrite## What does this MR do?
This MR gives more flexibility for CI pipelines based on Kubernetes Runner. It adds a environment variable to overwrite the target Kubernetes namespace. Therefore, you can for instance, use `Helm`/`Landscaper`...## What does this MR do?
This MR gives more flexibility for CI pipelines based on Kubernetes Runner. It adds a environment variable to overwrite the target Kubernetes namespace. Therefore, you can for instance, use `Helm`/`Landscaper` to install Charts and create the set of services/pods that are required to execute the CI pipeline step, and also the ability to clean-up by deleting an namespace completely.
The namespace can only be overwritten if matches a configured regular expression (added to the runner configuration), to guarantee only designed namespace names can be employed. When this configuration is empty, this whole overwrite behavior is disabled.
## Why was this MR needed?
To create more flexible CI runs, to include `Helm` packages in a brand new namespace which will be deleted altogether afterwards. Using an overwrite mechanism avoid an extra steps to achieve the same goal.
## Does this MR meet the acceptance criteria?
- [x] Documentation created/updated;
- Tests
- [x] Added for this feature/bug;
- [x] All builds are passing;
- [x] Branch has no merge conflicts with `master`;
## What are the relevant issue numbers?
No issues related to this change.
v1.10Tomasz Maczukintomasz@gitlab.comTomasz Maczukintomasz@gitlab.com