minikube: add ip-family flags and core IPv6 config plumbing #22061

kartikjoshi21 · 2025-12-08T08:05:21Z

This PR introduces the core configuration and CLI plumbing for IPv6 and dual-stack clusters in minikube. It does not change kubeadm/CNI templates or control-plane bindings yet; those come in follow-up PRs.

Concretely, it:

Adds an --ip-family flag to minikube start:
- ipv4 (default, current behaviour)
- ipv6
- dual
Wires IPv6-aware CIDRs and addresses into ClusterConfig / KubernetesConfig:
- --service-cluster-ip-range-v6 → KubernetesConfig.ServiceCIDRv6
- --pod-cidr → KubernetesConfig.PodCIDR (IPv4)
- --pod-cidr-v6 → KubernetesConfig.PodCIDRv6 (IPv6)
- --subnet-v6 → ClusterConfig.Subnetv6 (KIC Docker/Podman network)
- --host-only-cidr-v6 → ClusterConfig.HostOnlyCIDRv6 (VirtualBox)
- --static-ipv6 → ClusterConfig.StaticIPv6
Extends Node with an IPv6 field so later PRs can populate node IPs.
Adds defaults for IPv6 CIDRs:
- DefaultServiceCIDRv6 = "fd00::/108"
- DefaultPodCIDRv6 = "fd01::/64"
Introduces normalizeAndValidateIPFamily() which:
- Normalises IP family to ipv4 / ipv6 / dual (defaulting to ipv4),
- Sets IPv6 defaults when an IPv6-capable family is selected,
- Keeps the existing IPv4 PodCIDR default (cni.DefaultPodCIDR) for ipv4/dual,
- Validates CIDRs/addresses for --subnet-v6, --service-cluster-ip-range-v6, --pod-cidr, --pod-cidr-v6, and --static-ipv6.
Adds guardrails for IPv6/dual on the Docker driver:
- IPv6-only clusters require a Linux Docker daemon (not Docker Desktop),
- Dual-stack on Docker Desktop prints a warning,
- Prints a tip about enabling IPv6 in daemon.json if the daemon/network blocks IPv6 bridge networks.

For --ip-family=ipv4 with no IPv6 flags, minikube behaves exactly as today (IPv4-only cluster, existing Service/Pod CIDR defaults, no CNI or kubeadm behaviour change).

Fixes: #8535

Refer to #22061 (comment) comment for testing steps.
Tested and verified on:

PS C:\Users\kartikjoshi> wsl --version
WSL version: 2.6.2.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.71
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.7093

k8s-ci-robot · 2025-12-08T08:05:27Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kartikjoshi21
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot · 2025-12-08T08:05:31Z

Hi @kartikjoshi21. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

minikube-bot · 2025-12-08T08:06:05Z

Can one of the admins verify this patch?

kartikjoshi21 · 2025-12-08T08:06:31Z

Logs with basic flags plumbing and current behavior validation

kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ ./out/minikube delete --all --purge
🔥  Deleting "minikube" in docker ...
🔥  Removing /home/kartikjoshi/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.
🔥  Successfully deleted all profiles
💀  Successfully purged minikube directory located at - [/home/kartikjoshi/.minikube]
📌  Kicbase images have not been deleted. To delete images run:
    ▪ docker rmi gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1763789673-21948 gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1760939008-21773 gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1759745255-21703 gcr.io/k8s-minikube/kicbase-builds:v0.0.47-1756116447-21413
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ ./out/minikube start \
  --driver=docker \
  --cni=bridge \
  --ip-family=ipv4

kubectl get nodes -o wide
kubectl get pods -A -o wide
😄  minikube v1.37.0 on Ubuntu 24.04 (kvm/amd64)
✨  Using the docker driver based on user configuration
📌  Using Docker driver with root privileges
👍  Starting "minikube" primary control-plane node in "minikube" cluster
🚜  Pulling base image v0.0.48-1763789673-21948 ...
💾  Downloading Kubernetes v1.34.1 preload ...
    > preloaded-images-k8s-v18-v1...:  337.01 MiB / 337.01 MiB  100.00% 3.73 Mi
🔥  Creating docker container (CPUs=2, Memory=3072MB) ...
🐳  Preparing Kubernetes v1.34.1 on Docker 29.0.2 ...
🔗  Configuring bridge CNI (Container Networking Interface) ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
NAME       STATUS   ROLES           AGE   VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION                     CONTAINER-RUNTIME
minikube   Ready    control-plane   5s    v1.34.1   192.168.49.2   <none>        Debian GNU/Linux 12 (bookworm)   6.6.87.2-microsoft-standard-WSL2   docker://29.0.2
NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE   IP             NODE       NOMINATED NODE   READINESS GATES
kube-system   etcd-minikube                      0/1     Running   0          4s    192.168.49.2   minikube   <none>           <none>
kube-system   kube-apiserver-minikube            0/1     Running   0          4s    192.168.49.2   minikube   <none>           <none>
kube-system   kube-controller-manager-minikube   0/1     Running   0          3s    192.168.49.2   minikube   <none>           <none>
kube-system   kube-scheduler-minikube            0/1     Running   0          3s    192.168.49.2   minikube   <none>           <none>
kube-system   storage-provisioner                0/1     Pending   0          1s    <none>         <none>     <none>           <none>
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ kubectl get pods -A -o wide
NAMESPACE     NAME                               READY   STATUS    RESTARTS       AGE     IP             NODE       NOMINATED NODE   READINESS GATES
kube-system   coredns-66bc5c9577-qcbk6           1/1     Running   0              2m5s    10.244.0.2     minikube   <none>           <none>
kube-system   etcd-minikube                      1/1     Running   0              2m11s   192.168.49.2   minikube   <none>           <none>
kube-system   kube-apiserver-minikube            1/1     Running   0              2m11s   192.168.49.2   minikube   <none>           <none>
kube-system   kube-controller-manager-minikube   1/1     Running   0              2m10s   192.168.49.2   minikube   <none>           <none>
kube-system   kube-proxy-jcvhm                   1/1     Running   0              2m5s    192.168.49.2   minikube   <none>           <none>
kube-system   kube-scheduler-minikube            1/1     Running   0              2m10s   192.168.49.2   minikube   <none>           <none>
kube-system   storage-provisioner                1/1     Running   1 (2m3s ago)   2m8s    192.168.49.2   minikube   <none>           <none>
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ docker network inspect minikube
[
    {
        "Name": "minikube",
        "Id": "c1162b89eeb5fc041f022fcffbe8f9a44c3778146abf90a3d1c4f0c4e21138ad",
        "Created": "2025-11-27T05:16:25.564927403Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "192.168.49.0/24",
                    "Gateway": "192.168.49.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "20f782bd5029fc4a3e291e6180d993ae3ed62bb70eac66c4f1d44dbc088cdb42": {
                "Name": "minikube",
                "EndpointID": "a12e850a99129399eabb8b14cd4ccdeef571109be83f76d76e40537f98c68736",
                "MacAddress": "6e:19:61:a9:95:10",
                "IPv4Address": "192.168.49.2/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "--icc": "",
            "--ip-masq": "",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {
            "created_by.minikube.sigs.k8s.io": "true",
            "name.minikube.sigs.k8s.io": "minikube"
        }
    }
]

kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ ./out/minikube delete --all --purge
./out/minikube start \
  --driver=docker \
  --cni=bridge \
  --ip-family=ipv6 \
  --service-cluster-ip-range-v6=fd00::/108 \
  --pod-cidr-v6=fd01::/64
🔥  Deleting "minikube" in docker ...
🔥  Removing /home/kartikjoshi/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.
🔥  Successfully deleted all profiles
💀  Successfully purged minikube directory located at - [/home/kartikjoshi/.minikube]
📌  Kicbase images have not been deleted. To delete images run:
    ▪ docker rmi gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1763789673-21948 gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1760939008-21773 gcr.io/k8s-minikube/kicbase-builds:v0.0.48-1759745255-21703 gcr.io/k8s-minikube/kicbase-builds:v0.0.47-1756116447-21413
😄  minikube v1.37.0 on Ubuntu 24.04 (kvm/amd64)
✨  Using the docker driver based on user configuration
📌  Using Docker driver with root privileges
💡  If Docker daemon IPv6 is disabled, enable it in /etc/docker/daemon.json and restart:
  {"ipv6": true, "fixed-cidr-v6": "fd00:55:66::/64"}
👍  Starting "minikube" primary control-plane node in "minikube" cluster
🚜  Pulling base image v0.0.48-1763789673-21948 ...
💾  Downloading Kubernetes v1.34.1 preload ...
    > preloaded-images-k8s-v18-v1...:  337.01 MiB / 337.01 MiB  100.00% 1.83 Mi
🔥  Creating docker container (CPUs=2, Memory=3072MB) ...
🐳  Preparing Kubernetes v1.34.1 on Docker 29.0.2 ...
🔗  Configuring bridge CNI (Container Networking Interface) ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ docker network inspect
docker: 'docker network inspect' requires at least 1 argument

Usage:  docker network inspect [OPTIONS] NETWORK [NETWORK...]

See 'docker network inspect --help' for more information
kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ docker network inspect minikube
[
    {
        "Name": "minikube",
        "Id": "b84287d9edfc3b6e15a154b9ae611ea0664dca10fd3a85908784064dcefaf089",
        "Created": "2025-11-26T11:34:27.616639443Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "192.168.49.0/24",
                    "Gateway": "192.168.49.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "2bf3628d6001aa223242e4cef1b0b098eb59ac7749acf4fde7615ac54495d354": {
                "Name": "minikube",
                "EndpointID": "aa21a413ae7660ea35e6bcfe7fb19fdc628dda5c77bc319822d212517c782bb3",
                "MacAddress": "76:c8:b1:14:67:6c",
                "IPv4Address": "192.168.49.2/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "--icc": "",
            "--ip-masq": "",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {
            "created_by.minikube.sigs.k8s.io": "true",
            "name.minikube.sigs.k8s.io": "minikube"
        }
    }
]

kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ ./out/minikube start -p ipfam-bad \
  --driver=docker \
  --cni=bridge \
  --ip-family=foo
😄  [ipfam-bad] minikube v1.37.0 on Ubuntu 24.04 (kvm/amd64)
✨  Using the docker driver based on user configuration
📌  Using Docker driver with root privileges

❌  Exiting due to MK_USAGE: Invalid --ip-family foo. Must be one of: ipv4, ipv6, dual.

kartikjoshi@kartikjoshiwindows:~/minikube-ipv6-support/minikube$ ./out/minikube start -p bad-svc-v6 \
  --driver=docker \
  --ip-family=dual \
  --service-cluster-ip-range-v6=not-a-cidr
😄  [bad-svc-v6] minikube v1.37.0 on Ubuntu 24.04 (kvm/amd64)
✨  Using the docker driver based on user configuration
📌  Using Docker driver with root privileges

❌  Exiting due to MK_USAGE: --service-cluster-ip-range-v6 must be a valid IPv6 CIDR: invalid CIDR address: not-a-cidr

kartikjoshi21 · 2025-12-09T07:52:03Z

Testing

All tests were done with a locally built out/minikube.

1. Default IPv4 cluster (no new flags)

```bash
./out/minikube start --driver=docker --alsologtostderr -v=1
kubectl get nodes -o wide
Expectations:

Cluster starts and behaves as before.

2. --ip-family validation
bash
Copy code
./out/minikube start --driver=docker --ip-family=foobar
Expectations:

Fails with a usage error:

Invalid --ip-family foobar. Must be one of: ipv4, ipv6, dual.

No cluster is created.

3. CIDR validation / type checking
3.1 --pod-cidr must be IPv4
./out/minikube start \
  --driver=docker \
  --ip-family=dual \
  --pod-cidr=fd01::/64
Expectations:

Fails with a usage error mentioning --pod-cidr must be a valid IPv4 CIDR.

3.2 --pod-cidr-v6 must be IPv6

./out/minikube start \
  --driver=docker \
  --ip-family=dual \
  --pod-cidr-v6=10.244.0.0/16
Expectations:

Fails with a usage error mentioning --pod-cidr-v6 must be a valid IPv6 CIDR.

3.3 --service-cluster-ip-range-v6 must be IPv6
./out/minikube start \
  --driver=docker \
  --ip-family=dual \
  --service-cluster-ip-range-v6=10.96.0.0/12
Expectations:

Fails with a usage error mentioning --service-cluster-ip-range-v6 must be a valid IPv6 CIDR.

3.4 --subnet-v6 must be IPv6
./out/minikube start \
  --driver=docker \
  --subnet-v6=10.0.0.0/24
Expectations:

Fails with a usage error mentioning --subnet-v6 must be a valid IPv6 CIDR.

4. --static-ipv6 validation
./out/minikube start \
  --driver=docker \
  --ip-family=dual \
  --static-ipv6=192.168.49.2
Expectations:

Fails with a usage error:

--static-ipv6 must be a valid IPv6 address.

medyagh · 2025-12-10T22:00:55Z

/ok-to-test

illume · 2025-12-16T20:46:34Z

I ran through your tests manually on Windows 11 Enterprise with docker desktop... but with cmd and not gitbash.

All good.

wsl --version
WSL version: 2.6.1.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.7392

In git bash:

gh pr checkout 22061
make

Then in windows cmd:

1. Default IPv4 cluster (no new flags)

out\minikube start --driver=docker --alsologtostderr -v=1
...
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

3. CIDR validation / type checking

3.1 --pod-cidr must be IPv4

out\minikube start   --driver=docker  --ip-family=dual  --pod-cidr=fd01::/64
😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: --pod-cidr must be a valid IPv4 CIDR: <no value>

3.2 --pod-cidr-v6 must be IPv6

out\minikube start --driver=docker --ip-family=foobar
😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: Invalid --ip-family foobar. Must be one of: ipv4, ipv6, dual.

3.2 --pod-cidr-v6 must be IPv6

out\minikube start   --driver=docker   --ip-family=dual   --pod-cidr-v6=10.244.0.0/16
😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: --pod-cidr-v6 must be a valid IPv6 CIDR: <no value>

3.3 --service-cluster-ip-range-v6 must be IPv6

out\minikube start   --driver=docker  --ip-family=dual   --service-cluster-ip-range-v6=10.96.0.0/12
😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: --service-cluster-ip-range-v6 must be a valid IPv6 CIDR: <no value>

3.4 --subnet-v6 must be IPv6

out\minikube start --driver=docker --subnet-v6=10.0.0.0/24
😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: --subnet-v6 must be a valid IPv6 CIDR: <no value>

4. --static-ipv6 validation

😄  minikube v1.37.0 on Microsoft Windows 11 Enterprise 10.0.26200.7392 Build 26200.7392
✨  Using the docker driver based on existing profile

❌  Exiting due to MK_USAGE: --static-ipv6 must be a valid IPv6 address

illume · 2025-12-16T20:54:13Z

This should error IMHO, but runs. (note ipv4 with ipv6 flags)

out\minikube start --driver=docker --ip-family=ipv4 --pod-cidr-v6=fd01::/64

illume

Hey hey. I left a few notes.

cmd/minikube/cmd/start_flags.go

minikube-pr-bot · 2025-12-18T11:31:06Z

kvm2 driver with docker runtime
error downloading artifacts: artifact download start: exit status 14docker driver with docker runtime
error downloading artifacts: artifact download start: exit status 14docker driver with containerd runtime
error downloading artifacts: artifact download start: exit status 14

minikube-pr-bot · 2025-12-18T15:24:58Z

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.28.0/json-events(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.28.0/preload-exists(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.34.3/json-events(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.34.3/preload-exists(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.35.0-rc.1/json-events(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnly/v1.35.0-rc.1/preload-exists(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestDownloadOnlyKic(gopogh)	Unknown
Docker_Linux_containerd_arm64 (10 failed)	TestBinaryMirror(gopogh)	0.00% (chart)
Docker_Linux_containerd_arm64 (10 failed)	TestAddons/Setup(gopogh)	0.00% (chart)
Docker_Linux_containerd_arm64 (10 failed)	TestDockerEnvContainerd(gopogh)	0.00% (chart)
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.28.0/json-events(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.28.0/preload-exists(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.34.3/json-events(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.34.3/preload-exists(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.35.0-rc.1/json-events(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnly/v1.35.0-rc.1/preload-exists(gopogh)	Unknown
Docker_Linux_containerd (10 failed)	TestDownloadOnlyKic(gopogh)	0.00% (chart)
Docker_Linux_containerd (10 failed)	TestBinaryMirror(gopogh)	0.00% (chart)
Docker_Linux_containerd (10 failed)	TestAddons/Setup(gopogh)	0.00% (chart)
Docker_Linux_containerd (10 failed)	TestDockerEnvContainerd(gopogh)	0.00% (chart)

Besides the following environments also have failed tests:

Docker_Linux: 24 failed (gopogh)
none_Linux: 17 failed (gopogh)
Docker_Linux_crio: 24 failed (gopogh)
KVM_Linux_containerd: 23 failed (gopogh)
Docker_Linux_crio_arm64: 24 failed (gopogh)
Docker_Linux_docker_arm64: 24 failed (gopogh)
KVM_Linux: 23 failed (gopogh)
KVM_Linux_crio: 23 failed (gopogh)

To see the flake rates of all tests by environment, click here.

k8s-ci-robot · 2025-12-18T21:29:13Z

@kartikjoshi21: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
integration-vfkit-docker-macos-arm64	`09823ff`	link	false	`/test integration-vfkit-docker-macos-arm64`
pull-minikube-build	`09823ff`	link	true	`/test pull-minikube-build`
integration-docker-docker-linux-arm64	`09823ff`	link	true	`/test integration-docker-docker-linux-arm64`
integration-docker-crio-linux-x86-64	`09823ff`	link	true	`/test integration-docker-crio-linux-x86-64`
integration-docker-containerd-linux-x86-64	`09823ff`	link	true	`/test integration-docker-containerd-linux-x86-64`
integration-kvm-crio-linux-x86-64	`09823ff`	link	true	`/test integration-kvm-crio-linux-x86-64`
integration-docker-docker-linux-x86	`09823ff`	link	true	`/test integration-docker-docker-linux-x86`
integration-kvm-crio-linux-x86	`09823ff`	link	true	`/test integration-kvm-crio-linux-x86`
integration-none-docker-linux-x86	`09823ff`	link	true	`/test integration-none-docker-linux-x86`
integration-docker-containerd-linux-x86	`09823ff`	link	true	`/test integration-docker-containerd-linux-x86`
integration-kvm-docker-linux-x86	`09823ff`	link	true	`/test integration-kvm-docker-linux-x86`
integration-docker-crio-linux-x86	`09823ff`	link	true	`/test integration-docker-crio-linux-x86`
integration-kvm-containerd-linux-x86	`09823ff`	link	true	`/test integration-kvm-containerd-linux-x86`
integration-docker-docker-linux-arm	`09823ff`	link	true	`/test integration-docker-docker-linux-arm`

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

k8s-ci-robot requested review from medyagh and prezha December 8, 2025 08:05

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 8, 2025

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 8, 2025

kartikjoshi21 mentioned this pull request Dec 8, 2025

minikube: Add ipv6 and dual stack support for docker/Podman #21630

Open

kartikjoshi21 force-pushed the pr1-ipfamily-core branch from 40967e8 to 1c88f6d Compare December 9, 2025 07:48

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 10, 2025

This comment has been minimized.

Sign in to view

illume reviewed Dec 16, 2025

View reviewed changes

cmd/minikube/cmd/start_flags.go Outdated Show resolved Hide resolved

cmd/minikube/cmd/start_flags.go Show resolved Hide resolved

cmd/minikube/cmd/start_flags.go Outdated Show resolved Hide resolved

cmd/minikube/cmd/start_flags.go Outdated Show resolved Hide resolved

illume reviewed Dec 16, 2025

View reviewed changes

cmd/minikube/cmd/start_flags.go Show resolved Hide resolved

minikube: add ip-family flags and core IPv6 config plumbing

09823ff

kartikjoshi21 force-pushed the pr1-ipfamily-core branch from 1c88f6d to 09823ff Compare December 18, 2025 11:07

minikube: add ip-family flags and core IPv6 config plumbing #22061

Are you sure you want to change the base?

minikube: add ip-family flags and core IPv6 config plumbing #22061

Conversation

kartikjoshi21 commented Dec 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-ci-robot commented Dec 8, 2025

Uh oh!

k8s-ci-robot commented Dec 8, 2025

Uh oh!

minikube-bot commented Dec 8, 2025

Uh oh!

kartikjoshi21 commented Dec 8, 2025

Uh oh!

kartikjoshi21 commented Dec 9, 2025

Testing

Uh oh!

medyagh commented Dec 10, 2025

Uh oh!

This comment has been minimized.

This comment has been minimized.

illume commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

1. Default IPv4 cluster (no new flags)

3. CIDR validation / type checking

3.1 --pod-cidr must be IPv4

3.2 --pod-cidr-v6 must be IPv6

3.2 --pod-cidr-v6 must be IPv6

3.3 --service-cluster-ip-range-v6 must be IPv6

3.4 --subnet-v6 must be IPv6

4. --static-ipv6 validation

Uh oh!

illume commented Dec 16, 2025

Uh oh!

illume left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

minikube-pr-bot commented Dec 18, 2025

Uh oh!

minikube-pr-bot commented Dec 18, 2025

Uh oh!

k8s-ci-robot commented Dec 18, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

kartikjoshi21 commented Dec 8, 2025 •

edited

Loading

illume commented Dec 16, 2025 •

edited

Loading