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

IPV6 Documentation #53824

Closed
mmueen opened this Issue Oct 12, 2017 · 7 comments

Comments

Projects
None yet
6 participants
@mmueen

mmueen commented Oct 12, 2017

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature
/sig network
/area ipv6

What happened:
There is not consolidated documentation / guide available for deployment of Kubernetes with IPV6. The information is sparse and not at a single location, so it would be really helpful if all the documentation is compiled in wiki and act as a single stop for anyone trying to deploy kubernetes with IPV6.

What you expected to happen:
Complete guide of deploying Kubernetes with IPV6.
List of issues / components which lack IPV6 support right now.

Environment:

  • Kubernetes version (use kubectl version): Latest
  • Cloud provider or hardware configuration**: VirtualBox cluster, Ubuntu 16.04.1 host, CentOS 7 guests
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@feiskyer

This comment has been minimized.

Show comment
Hide comment
@feiskyer
Member

feiskyer commented Oct 17, 2017

@cmluciano

This comment has been minimized.

Show comment
Hide comment
@cmluciano
Member

cmluciano commented Oct 17, 2017

@mmueen

This comment has been minimized.

Show comment
Hide comment
@mmueen

mmueen commented Oct 18, 2017

/assign @mmueen

@valentin2105

This comment has been minimized.

Show comment
Hide comment

valentin2105 commented Nov 14, 2017

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Feb 12, 2018

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

fejta-bot commented Feb 12, 2018

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

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Mar 14, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

fejta-bot commented Mar 14, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Apr 13, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

fejta-bot commented Apr 13, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment