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

Don't set externalTrafficPolicy when externalService is ClusterIP #266

Open
baby-gnu opened this issue Jun 9, 2023 · 6 comments · May be fixed by #374
Open

Don't set externalTrafficPolicy when externalService is ClusterIP #266

baby-gnu opened this issue Jun 9, 2023 · 6 comments · May be fixed by #374
Labels
bug Something isn't working

Comments

@baby-gnu
Copy link

baby-gnu commented Jun 9, 2023

Describe the bug

I can't deploy the helm with the following values.yaml:

front:
  hostPort:
    enabled: false

  externalService:
    enabled: true
    type: ClusterIP

I get the following error:

Error: Service "mailu-front-ext" is invalid: spec.externalTrafficPolicy: Invalid value: "Local": may only be set when `type` is 'NodePort' or 'LoadBalancer'

Environment

  • Kubernetes Platform Scaleway

Additional context

I have an existing nginx ingress as LoadBalancer with correct TCP service forwarding.

@baby-gnu baby-gnu added the bug Something isn't working label Jun 9, 2023
@emouawad
Copy link

+1 same here

@jlxq0
Copy link

jlxq0 commented Oct 6, 2024

Same. Did anyone figure this out?

@WebSpider
Copy link
Contributor

I'll see if i can provide a PR for this

@jlxq0
Copy link

jlxq0 commented Oct 17, 2024

What's the workaround, @WebSpider?

@WebSpider
Copy link
Contributor

Sorry, real life happend. Thanks for tagging me, ill PR tonight.

Its a matter of putting an extra 'if' in the template that creates the service.

@jlxq0
Copy link

jlxq0 commented Oct 24, 2024

How do we get this merged now? 😇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants