feat: Allow configuring the Service IP Family policy to make it dual-stack #252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
This PR allows users to configure the
ipFamilyPolicy
andipFamilies
of the Kubernetes Service.By default, Kubernetes Services are created to work only on the IPv4 stack.
People on a dual-stack network should be able to specify the policy they want.
See https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services for reference.
Existing or Associated Issue(s)
—
Additional Information
—
Checklist
Chart.yaml
according to semver.values.yaml
and added to the README.md. The helm-docs utility can be used to generate the necessary content. Usehelm-docs --dry-run
to preview the content.ct lint
command.