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
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
Once #704 is finished we need to start flushing out what prevents us from having multiple Team CR instances in a cluster.
As a start we should try to create a single Team CR instance in a namespace that is not named kabanero and make sure everything still works.
Then we should try to create a second Team CR instance in another namespace that is not named kabanero and make sure it also works (and that the first continues to work).
By work, I mean that the correct pipelines are created in the correct namespaces and that a webhook can be used to deploy an application. The Team CRs should point to different targetNamespaces and should not be able to deploy to the target namespace of the other CR instance. There is an existing issue in the tekton-pipelines namespace that the pipelines need to have unique names, so the two Team CR instances will either need to have a disjoint set of stacks, or will need to have completely different pipelines implementations.
The text was updated successfully, but these errors were encountered:
Once #704 is finished we need to start flushing out what prevents us from having multiple Team CR instances in a cluster.
As a start we should try to create a single Team CR instance in a namespace that is not named
kabanero
and make sure everything still works.Then we should try to create a second Team CR instance in another namespace that is not named
kabanero
and make sure it also works (and that the first continues to work).By work, I mean that the correct pipelines are created in the correct namespaces and that a webhook can be used to deploy an application. The Team CRs should point to different
targetNamespaces
and should not be able to deploy to the target namespace of the other CR instance. There is an existing issue in thetekton-pipelines
namespace that the pipelines need to have unique names, so the two Team CR instances will either need to have a disjoint set of stacks, or will need to have completely different pipelines implementations.The text was updated successfully, but these errors were encountered: