You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
/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
):tkn version
):kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: