Our integration test runs our k8s controller outsides of our k8s cluster. It will spin up lots of jobs/pods in a k8s namespace X.
Right now, X = buildkite, it happens to be where our CI is running. It becomes a problem now if we saw a pod in buildkite namespace, we don't know if the pod is from CI workload or integration tests.
This change makes sure when we run our CI, workload generated by integration will run on its own namespace, reducing confusion and hopefully easier to manage on the long run.
Our integration test runs our k8s controller outsides of our k8s cluster. It will spin up lots of jobs/pods in a k8s namespace X.
Right now, X =
buildkite, it happens to be where our CI is running. It becomes a problem now if we saw a pod inbuildkitenamespace, we don't know if the pod is from CI workload or integration tests.This change makes sure when we run our CI, workload generated by integration will run on its own namespace, reducing confusion and hopefully easier to manage on the long run.