Open tedim52 opened 11 months ago
@Tedi it seems that the k8s service resource is not removed when you remove the enclave's service, I don't remember well but I think it was left there for a reason, or probably it's a bug. You could double-check my assumption. @mieubrisse Do you remember why the k8s service is not removed in this circumstance?
Yep, I have some context here but maybe not the solution - when we were developing k8s, waiting for k8s to actually remove things took a veryyyyyy long time. We instead implemented "tombstoning", where Kurtosis would say "hey k8s, clean this up" and k8s would do it on its own sweet time while Kurtosis proceeded. That said, my understanding is that service cleanup should still happen immediately (even if Pod descheduling didn't).
So my two thoughts are either:
What's your CLI version?
0.85.36
Description & steps to reproduce
kurtosis service add test-enclave test2 httpd --ports http=80
kurtosis service rm test-enclave test2
kurtosis service add test-enclave test2 httpd --ports http=80
returns:Desired behavior
The service with the same name should be able to be added, in accord with functionality over Docker cluster.
What is the severity of this bug?
Painful; this is causing significant friction in my workflow.
What area of the product does this pertain to?
CLI: the Command Line Interface