Jonathan Innis
Jonathan Innis
Looking over this issue: I'm realizing that what this issue really is is a discussion issue around a bunch of things, providing a common space for any cloud providers that...
> We can get this converted to a GitHub Discussion @sftim My one reservation about converting this to a discussion is routing. Do we have a good feeling which issues...
@mikkeloscar Thats interesting. I wouldn't expect to see the behavior that you're describing. I could definitely see this race occurring when there is a pod that is just coming up...
> Please share a link if its open source +1 to what @Bryce-Soghigian said. We should link out to these CloudProviders in our README so that users have a pointer...
@dewstyh Do you have an update here? It's tough for us to make progress on the bug without getting more information.
> ### Taint specified with wildcard value, but toleration isn't specified at all (no key, no value) I'm not convinced the generated case is the behavior we want. In my...
@VishDev12 > Another point of note is that if we have this separation, we can use a single provisioner to support generated taints with different keys. Workloads can "choose" which...
/kind documentation
I'm wondering if a semantic like `optionalTaints` is more appropriate here. I'm concerned with the `*` semantic in the existing `taints` field since there is an understanding at this point...