Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gateway svc with externalTrafficPolicy fails when set to ClusterIP #755

Open
ramki88 opened this issue May 13, 2024 · 2 comments
Open

Gateway svc with externalTrafficPolicy fails when set to ClusterIP #755

ramki88 opened this issue May 13, 2024 · 2 comments

Comments

@ramki88
Copy link

ramki88 commented May 13, 2024

With reference to #88, adding externalTrafficPolicy when the type is ClusterIP would fail. ClusterIP can be used when exposing the gateway using the ingress controller.

http://ingress/-> apisix-dashboard
http://ingress/api/* -> apisix-gateway

@meektechie
Copy link

I am also facing the same issue. It supports only NodePort & LoadBalancer. We need ClusterIP support also

  • Service "apisix-gateway" is invalid: spec.externalTrafficPolicy: Invalid value: "Cluster": may only be set for externally-accessible services

@ramki88
Copy link
Author

ramki88 commented Sep 9, 2024

@meektechie, for workaround as of now, leaving the externalTrafficPolicy blank in values.yaml deploys the chart.

apisix:
  service:
    type: ClusterIP
    externalTrafficPolicy:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants