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

K8s: Tutor should not assume sole control on k8s namespace #1018

Open
waza-ari opened this issue Mar 17, 2024 · 1 comment
Open

K8s: Tutor should not assume sole control on k8s namespace #1018

waza-ari opened this issue Mar 17, 2024 · 1 comment

Comments

@waza-ari
Copy link
Contributor

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.

@regisb
Copy link
Contributor

regisb commented Mar 26, 2024

What command specifically is causing an issue? What are the logs?

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

No branches or pull requests

2 participants