Arko Dasgupta

Results 937 comments of Arko Dasgupta

thanks for your contribution @evol262, adding the interfaces for the iptble layer will make it simpler to extend the codebase and the nftable implementation will improve the speed of programming...

Hoping to help out with this issue. **Existing Projects** * [Here's](https://istio.io/latest/docs/tasks/traffic-management/ingress/secure-ingress/#configure-a-mutual-tls-ingress-gateway) an example of how mTLS is described to the user in Istio and how the user can configure their...

> For your use case, I prefer using the [EnvoyProxy API](https://github.com/envoyproxy/gateway/blob/main/api/config/v1alpha1/envoyproxy_types.go) instead of labeling the Gateway. The driving factor for this recommendation is to avoid Gateway annotation sprawl. Thoughts @arkodg...

fixed with https://github.com/envoyproxy/gateway/pull/404

attaching some test logs done with 2 gateways 2 Gateway resources ``` $ kubectl get gateway/eg -o yaml apiVersion: gateway.networking.k8s.io/v1beta1 kind: Gateway metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"gateway.networking.k8s.io/v1alpha2","kind":"Gateway","metadata":{"annotations":{},"name":"eg","namespace":"default"},"spec":{"gatewayClassName":"eg","listeners":[{"name":"http","port":8080,"protocol":"HTTP"}]}} creationTimestamp: "2022-09-23T02:00:18Z" generation:...

reviewers please note that this PR doesnt handle delete of Gateway resources, will raise an issue to track it once this PR is in, and will fix be fixed in...

@danehans I cherry-picked https://github.com/envoyproxy/gateway/pull/435 on top of this PR and CI now passes

@danehans imho EG should propose a sane default such as ^ and any mod should be addressed via https://github.com/envoyproxy/gateway/issues/31 / https://github.com/envoyproxy/gateway/issues/24

imho `make run-kube-local` should pick a new bootstrap file (which would be supported once https://github.com/envoyproxy/gateway/issues/31 is in) which would contain the updated xDS address `host.docker.internal` (for non linux systems) it...

I dont see an easy of doing this w/o adding a new API or supporting Envoy resource configs directly. suggesting moving this in `backlog` and tackling this later once https://github.com/envoyproxy/gateway/issues/31...