Charly Molter
Charly Molter
Yes that's the idea behind the new selectors
This will be part: https://github.com/kumahq/kuma/issues/4739 implemetn with #5211
Might be a good time to do now. This has been around for over a year no?
@lobkovilya can you add more info and switch this back to `triage/pending` ?
Yes I was thing metav1/corev1/appv1 something like this.
Just a matter at adding some entries there: https://github.com/kumahq/kuma/blob/master/.golangci.yml#L25-L42 Looking at it we're not talking about a LOT of them: ``` ➜ kuma git:(fix5005) git grep k8s.io/api | grep '\.go'...
> I agree that we don't want to downgrade to TCP. I'm not sure what the protocol tag is supposed to mean in these cases. If the application can't handle...
Here's the use-case where this causes problem: 1. set 2 dps with `kuma.io/protocol: http` and tracing. This works well! 2. change one of these dps to use `kuma.io/protocol: http2`. This...
Yes I think so. I'm also unclear why `this protocol inference should not be used on the inbound side at all.` @jakubdyszkiewicz could you explain?
Question for triage: Feels like we have a path forward now right?