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
When creating a new environment, tutor will create the namespace automatically. More crucially, when deleting an environment, it will attempt to delete the namespace as well.
This is an issue if the namespace is externally created (in our case, basically the entire cluster except tutor is GitOps managed using ArgoCD), which is also creating the namespace including a few basic services (HashiCorp vault connection for secret store and so on). When tutor attempts to delete the NS, it conflicts with ArgoCD.
Again it might make sense to introduce an additional parameter to control the behaviour.
The text was updated successfully, but these errors were encountered:
Bug description
When creating a new environment, tutor will create the namespace automatically. More crucially, when deleting an environment, it will attempt to delete the namespace as well.
This is an issue if the namespace is externally created (in our case, basically the entire cluster except tutor is GitOps managed using ArgoCD), which is also creating the namespace including a few basic services (HashiCorp vault connection for secret store and so on). When tutor attempts to delete the NS, it conflicts with ArgoCD.
Again it might make sense to introduce an additional parameter to control the behaviour.
The text was updated successfully, but these errors were encountered: