Vishnu Deva

Okay, that makes a lot of sense, I can see how not having the provisioner at least define the labels/taints will collapse that boundary. It was definitely a stretch in...

If we have an undefined value in the taint, how would the coexistence of isolated and non-isolated workloads work in this scenario? Looking at a few cases: ## Taint specified...

I agree with your concerns about empty taint values. That's its own valid case, and shouldn't be conflated with this new feature. > You can create another Provisioner that doesn't...

Of course @jonathan-innis, here's an example of what I was planning to use it for. # Example ## Facts * There are 5 different teams. * Each team has at...

That's awesome! Thank you both!

Thank you for the explanation, but please allow me to take a bit more of your time. I understand this concern: > We see this as a concern since behaviors...

That's definitely a workable solution and is what I'm using right now to separate workloads in a dedicated provisioner. The main issue is just that the premise of this issue...

It's a bit hard to put a number to it, because it varies based on the availability of dynamic taints. ### Case I: Available Even at the initial stages of...