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

Pipeline controller should not use the same namespace as tekton pipeline controller. #1176

Open
ScrapCodes opened this issue Mar 2, 2023 · 1 comment
Labels

Comments

@ScrapCodes
Copy link
Contributor

/kind bug

What steps did you take and what happened:
When I execute

kubectl delete -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.45.0/release.yaml

It ends up deleting the pipeline loop controller as well.

What did you expect to happen:
If the two controller are on different namespaces, it might be easier to upgrade them.

Additional information:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Python Version (use python --version):
  • SDK Version:
  • Tekton Version (use tkn version):
  • Kubernetes Version (use kubectl version):
  • OS (e.g. from /etc/os-release):
@Tomcli
Copy link
Member

Tomcli commented Mar 2, 2023

Personally I don't like to have too many namespaces. I think the right way is maybe expose namespace in the pipelineloop kustomize config so that users can configure them when they want to. And for the default namespace in the pipelineloop manifests, we can set the namespace to kubeflow if running it in tekton-pipelines is conflicting with the Tekton docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants