Karol Szwaj comments

Results 108 comments of


                                            Karol Szwaj

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

I will take a look

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Seems like the same issue like here: https://github.com/envoyproxy/gateway/issues/2964 I will have some time now to debug this

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

I have tested it against the gateway with multiple listeners ```bash apiVersion: gateway.networking.k8s.io/v1beta1 kind: Gateway metadata: name: infra-gateway spec: gatewayClassName: eg-internal listeners: - name: company-https hostname: '*.company.com' protocol: HTTPS port:...

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

hey, I concluded my debugging here https://github.com/envoyproxy/gateway/issues/1861#issuecomment-2032093712 I couldn't reproduce this issue, even with the same protocol and port but a different hostname, I could match proper backend service. The...

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

hey @arkodg, I tried both of them, like I said the traffic passed in my case properly to the correct backend. But it might be that other folks want to...

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Oh, I did not see these in my example :)

Karol Szwaj

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

Listener is not created when there are multiple multiple listeners having same protocols and ports but different hostname

chore: use list instead of map for Provider Resources

OOM killed

KubeVirt GenerateRandMAC

Application Installation values modification fails