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

add service.loadBalancerIP #61

Open
2 tasks done
kingsmill opened this issue Oct 15, 2021 · 2 comments
Open
2 tasks done

add service.loadBalancerIP #61

kingsmill opened this issue Oct 15, 2021 · 2 comments

Comments

@kingsmill
Copy link

Preflight Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

This helm chart supports setting "service.type" but if you define the service.type to LoadBalancer the helm chart does not have the option to set "service.loadBalancerIP" which is required to define a dex service external IP for direct remote access.

Proposed Solution

This would be a simple change. The following three lines would be required in templates/service.yaml.

spec:
  type: {{ .Values.service.type }}
  {{- with .Values.service.clusterIP }}
  clusterIP: {{ . }}
  {{- end }}
  {{- with .Values.service.loadBalancerIP }}    <--
  loadBalancerIP: {{ . }}                       <--
  {{- end }}                                    <--
  ports:

Alternatives Considered

Modify helm chart or use another helm chart. By way of comparison, some other dex helm charts do support loadBalancerIP.

Additional Information

No response

@sagikazarmark sagikazarmark transferred this issue from dexidp/dex Oct 16, 2021
@sagikazarmark
Copy link
Member

@kingsmill thanks for opening this issue.

Yeah, adding loadBalancerIP make sense. Feel free to submit a PR if you are in the mood for it.

Thanks!

@DonaldKellett
Copy link

I second this, would be great if we could specify a static load balancer IP address

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

3 participants