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

Support dual stack services #108

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

withinboredom
Copy link

This keeps ipFamily in the component chart and translates it to ipFamilyPolicy to allow dual stack deployments.

Closes #107

@@ -37,7 +37,7 @@ spec:
healthCheckNodePort: {{ $.Values.service.healthCheckNodePort }}
{{- end }}
{{- if $.Values.service.ipFamily }}
ipFamily: {{ $.Values.service.ipFamily }}
ipFamilyPolicy: {{ $.Values.service.ipFamily }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it make sense to also rename the field in the values.yaml file?
The following would also remain downward compatibility:

Suggested change
ipFamilyPolicy: {{ $.Values.service.ipFamily }}
ipFamilyPolicy: {{ or $.Values.service.ipFamilyPolicy $.Values.service.ipFamily }}

@ThomasK33
Copy link

Thanks for the PR @withinboredom, mostly LGTM. It would probably make sense also to rename the field name in the values.yaml file to avoid confusion in the future.

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

Successfully merging this pull request may close these issues.

ipFamily isn't a thing
2 participants