What would you like to be added:
Gateway API desperately needs following enhancements to be fully declarative and production-ready solution:
1)Gateway API should have an ability to determine additional service spec, i.e. externalTrafficPolicy: local
2)Gateway API should have an ability to configure GW nodeselector/affinity/toleration fields
Why this is needed:
1)regarding feature 1: in secured topologies where you have special gateway nodes to control ingress/egress traffic deployed service with load balancer IP should have that externalTrafficPolicy: local to preserver real client IP address. without that every time after deploying GW we need to manually create service/or override created service. That does not looks reasonable since K8S should be configured as a code.
2)affinities/tolerations/nodeselector fields also should exists to allow to schedule gateway pods ONLY to specific nodes
What would you like to be added:
Gateway API desperately needs following enhancements to be fully declarative and production-ready solution:
1)Gateway API should have an ability to determine additional service spec, i.e. externalTrafficPolicy: local
2)Gateway API should have an ability to configure GW nodeselector/affinity/toleration fields
Why this is needed:
1)regarding feature 1: in secured topologies where you have special gateway nodes to control ingress/egress traffic deployed service with load balancer IP should have that externalTrafficPolicy: local to preserver real client IP address. without that every time after deploying GW we need to manually create service/or override created service. That does not looks reasonable since K8S should be configured as a code.
2)affinities/tolerations/nodeselector fields also should exists to allow to schedule gateway pods ONLY to specific nodes