Skip to content

Drop the empty externalTrafficPolicy of the gateway Service - #34

Merged
vramperez merged 2 commits into
masterfrom
drop-external-traffic-policy
Nov 13, 2026
Merged

vramperez merged 2 commits into
masterfrom
drop-external-traffic-policy

Conversation

@vramperez

Copy link
Copy Markdown
Collaborator

apisix.service.externalTrafficPolicy was set to an empty value because apisix chart versions before 2.18 wrote the field for every Service type, and the API server rejects it on a ClusterIP Service. The chart now uses apisix 2.18.2, which only writes it for NodePort and LoadBalancer Services, with Cluster, the Kubernetes default.

Nothing changes in what is deployed: a ClusterIP gateway gets no field, and a NodePort or LoadBalancer one gets Cluster, the policy Kubernetes applied when the value was empty.

Tests

  • Render of the gateway Service as ClusterIP, NodePort and LoadBalancer

It was set to an empty value because apisix chart versions before 2.18 wrote
the field for every Service type, and the API server rejects it on a ClusterIP
Service. The chart now uses apisix 2.18.2, which only writes it for NodePort and
LoadBalancer Services, with `Cluster`, the Kubernetes default. A ClusterIP
gateway gets no field and a NodePort or LoadBalancer one gets the same policy as
before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vramperez
vramperez merged commit c88d2ac into master Nov 13, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants