brentmjohnson

not sure if the operator eventually reconciles resources and overwrites this, but you can also patch the cronjob as a workaround like the following: ```` kubectl patch CronJob/jaeger-spark-dependencies -n observability...

Use of **ws** server-side seems to work fine as-is with a native chromium WebSocket API client. HTTP/1 requests hit the "upgrade" event and HTTP/2 requests hit the "connect" event. Only...

@ackava, i believe most browsers should respect the server's ALPN negotiation, but yeah if your server reports http2 and support for extended connect (re: RFC 8441) i would expect chrome...

@connor4312 thanks so much for the work on this! I kind of expected this to be released to vscode-insiders but maybe not yet? rustwasm/walrus dependency upgrades are now in the...

Confirmed spec.calicoNetwork.linuxDataplane = iptables works as expected (SNAT + MASQ) with above config. If anyone has any ideas related to potential incorrect tigera operator generated manifests / config would be...

> Could you share `ip6tables-save -c` output from the node where your ping pod runs? What is `k8s-lb` IP? Sure! k8s-lb ip addr show eth0: ``` 2: eth0: mtu 1500...

Thanks for confirming. In cluster DNS seemed to proxy as expected. I will validate for TCP / UDP. Let me know if you expect any other protocols may need specific...

I did identify one other issue / behavior in the current implementation in response forwarding of SNAT'ed requests. I observed some fragmentation of response packets from the external service. They...

Thanks all, I will re-test once a dev image is available. Any feedback on expected level of support for forwarding of fragmented payloads?

confirmed SNAT / MASQ of ICMP6 from pod network CIDR to external services in the node network CIDR works as expected now in `calico/node:v3.27.3-3-g547edf833d4c`