I'm looking to do the same and it seems that this playbook is totally broken as it makes ipv4-only assumptions.

For example, this preinstall check fails even though there is an ipv6 address available on the host.

fatal: [node1]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}
fatal: [node2]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}
fatal: [node3]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}

I'm looking to do the same and it seems that this playbook is totally broken as it makes ipv4-only assumptions.

For example, this preinstall check fails even though there is an ipv6 address available on the host.

fatal: [node1]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}
fatal: [node2]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}
fatal: [node3]: FAILED! => {
    "assertion": false,
    "changed": false,
    "evaluated_to": false,
    "msg": "Do not schedule more pods on a node than inet addresses are available."
}

Right! I also think so. I tried creating an IPv6 only cluster on Fedora Coreos and met an error about etcd. Error is same with which mentioned here

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Kubernetes is dual stack now; kubespray should also support IPv6-only or dual stack deployments. I'll be trying to work on this a bit as we can't go into production without dual stack support.

Kubernetes is dual stack now; kubespray should also support IPv6-only or dual stack deployments. I'll be trying to work on this a bit as we can't go into production without dual stack support.

I have also started working on that; adding support for IPv6 only and dual stack. Do you want to coordinate efforts?

I am currently running single-stack IPv6 kubernetes with kubeadm and would be interested in working on this with you so that I can deploy with kubespray instead.

Me too, I'm interested to run use kubespray with IPv6 only. Is any progress in this?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

My current workaround is to define a wireguard interface on all IPv6-only-hosts with an wg0-ipv4-address. Of course - this should not be the correct solution for this issue. It would be much better to have a "native" IPv6-only support via kubespray.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

@k8s-triage-robot: Closing this issue.

/reopen

@starcraft66: You can't reopen an issue/PR unless you authored it or you are a collaborator.

/remove-lifecycle rotten

can this be reopened? or is there a new issue for this / has it been fixed?