Deploying on IPv6 only clusters fail with defaults

[frederictobiasc]

What happened:

I tried to deploy the chart on a k3s cluster with IP Family = IPv6.

The following error occured:

Error: INSTALLATION FAILED: 1 error occurred:
	* Service "ingress-nginx-controller" is invalid: spec.ipFamilies[0]: Invalid value: "IPv4": not configured on this cluster

What you expected to happen:

I expected the chart to be deployed successfully in standard configuration with only IPv6 IP Family enabled.

The documentation states, that the field controller.service.ipFamilies is assigned automatically.

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.):

Kubernetes version (use kubectl version):

Environment:

• Cloud provider or hardware configuration: QEMU x86 VM
• OS (e.g. from /etc/os-release): NixOS 23.11 (Tapir)
• Kernel (e.g. uname -a): Linux 6.1.37 NixOS SMP PREEMPT_DYNAMIC Sat Jul 1 11:16:27 UTC 2023 x86_64 GNU/Linux
• Install tools: klipper-helm
• Basic cluster related info:

Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.4+k3s1", GitCommit:"8d0255af07e95b841952563253d27b0d10bd72f0", GitTreeState:"clean", BuildDate:"1970-01-01T01:01:01Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.4+k3s1", GitCommit:"8d0255af07e95b841952563253d27b0d10bd72f0", GitTreeState:"clean", BuildDate:"1970-01-01T01:01:01Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/amd64"}

• kubectl get nodes -o wide

• Others:

How to reproduce this issue:

Create a basic k3s cluster with IpFamily = IPv6.

Anything else we need to know:

This has been reported before, but no fix so far:
Related issue: #8175

Workaround (from issue above)

# Modify the defaults:
controller.service.ipFamilyPolicy=null
controller.service.ipFamilies=null

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/remove-kind bug

I don't think there is a CI test for SingleStack+ipv6.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

[longwuyuan]

There are values file key:value pairs that you can play with a see if its possible to install on ipv6 only cluster.
That is line 518 of the values file of the helm chart.

if you dont use helm then manual set the ipfamilies spec.

/close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

There are values file key:value pairs that you can play with a see if its possible to install on ipv6 only cluster.
That is line 518 of the values file of the helm chart.

if you dont use helm then manual set the ipfamilies spec.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.