►
From YouTube: To IPv6 - The Dual-stack Adoption Advisory Panel
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
To IPv6 - The Dual-stack Adoption Advisory Panel - Bridget Kromhout, Microsoft; Tim Hockin, Google; Dinesh Majrekar, Civo; Lachie Evenson, Microsoft; Rags Srinivas, InfoQ
We all know we’re running out of IPv4 addresses. Kubernetes introduced the current implementation of dual-stack networking (supporting both IPv4 and IPv6 at the same time) in v1.20, and the dual-stack feature graduated to stable in v1.23. While the world has been slow to adopt IPv6, it is happening. It’s time to learn about using dual-stack to start your own move away from IPv4, supported by changes in Kubernetes components such as pods and services. Join for the discussion as SIG Network members and Kubernetes contributors dive into the technical details underlying the move to dual-stack networking, and leave with recommendations to shape your IPv4/IPv6 rollout strategy.
A
All
right
all
right,
can
everyone
hear
me
perfect?
So
those
of
you
in
the
back
there
is
a
lot
of
room
in
the
front.
You
know
if
you
want
to
come
front.
You
know
you
don't
like
a
particular
answer
by
one
of
the
panelists.
You
can
even
accost
them.
You
know
I'm
just
kidding,
but
thank
you
for
coming.
You
know
it's
always
a
pleasure
to
be
in
person.
A
I
did
a
lot
of
kubecon
talks
virtual
right.
We
got
a
what
three
o'clock
in
the
morning
for
one
of
these,
but
but
you
know
it's
it's
great
to
be
in
person.
It's
four
o'clock:
it's
a
reasonable
time.
People
are
here,
but
this
is
your
panel.
You
know
so
be
ready
with
the
questions.
I'm
just
going
to
do
a
quick
round
of
introductions
and
after
that,
it's
all
yours,
okay,
so
feel
free
to
ask
some
of
the
tough
questions
make
this
panelist
squirm.
A
A
How
many
of
you
are
already
on
the
ipv6
bandwagon
when
it
comes
to
kubernetes,
whoa?
Okay,
that's
very
cool
last
question:
on
a
scale
of
1
to
10
a
networking.
Geek
right
is
10
and
really
know
nothing
about.
You
know
kind
of
the
different
levels
or
whatever
right,
that's
one
and
I'm
somewhere
like
a
level
two
level,
three.
Something
like
that.
How
many
are
you
above
a
level
six,
a
level
seven,
a
few.
C
A
No,
but
but
thanks
again
for
coming,
this
is
your
panel,
so
I
have
a
great
august
panel
in
may,
so
it's
pretty
cool
I'll.
Let
them
introduce
themselves
so
be
ready
to
ask
some
questions.
I'm
gonna
run
around
with
a
handheld
mic.
Please
wait:
okay,
don't
yell
yell
out,
because
you
know
there
are
virtual
audience
who
are
listening
as
we
speak,
so
I
don't
want
to
ignore
any
of
them.
A
D
E
B
Wonderful,
hello,
everybody
how's,
everybody
doing
good.
Thank
you.
Thank
you.
I
need
the
energy.
I
need
the
energy.
My
name
is
lachlan
evenson.
I
work
at
microsoft.
I
actually
worked
in
sig
network
on
the
dual
stack
feature
in
kubernetes,
so
really
excited
to
hear
from
you
all.
We
want
to
make
it
better.
So
please
ask
questions
either
today
or
you
can
find
me
online.
I'd
really
love
to
just
hear
about
how
it's
being
used
so
all
these
hands.
B
C
All
right,
thank
you
lockheed.
I
will
say
that
if
kubernetes
having
ipv6
is
one
really
good
thing
that
happens
this
year,
I
guess
it
was
technically
right
at
the
end
of
last
year.
But
if
everybody
implements
it
this
year,
then
you
may
possibly
single-handedly
fix
2022.
So
please
go
back
and
do
that
and
I'm
bridget.
C
I
work
on
lockheed's
team
and
if
you
would
like
to
register
a
complaint
about
or
perhaps
a
pull
request
to,
the
docs
for
ipv6
or
the
code,
examples
that
I
worked
on
with
lockheed
or
the
blog
post
or
you
know,
oh
come
and
bike
shed
the
production
readiness
review,
I
feel
like
we
could
have
done
a
little
bit
more
with
that.
Why
not
so
but
yeah
happy
to
chat
about
it.
A
Perfect,
so
anybody
have
any
question,
but
you
know,
while
you're
warming
up.
I
think
that
was
a
good
segue
into
the
question
that
I
was
gonna
ask,
which
is
I'm
a
developer?
I'm
an
app
developer
right
and
you
know
kubernetes
networking
was
great
because
it
was
kind
of
like
an
extended
vm
right.
You
know
it
got
its
own
ip
address
and
all
that
I
needed
to
do
was
kind
of
wire
up
the
ip
address
or
something
like
that.
But
as
a
developer,
do
I
really
care
about
ipv6?
A
Should
I
really
care
about
ipv6
and
if
I
do,
what
are
my
resources
to
get
started?
You
know
there
are
not
a
whole
lot
out
there.
You
know
I
mean
I
tried
looking
for
them.
So
can
you
can
you
point
developers
in
the
right
direction,
give
some
ideas?
How
many?
How
many
of
you
think
that
this
is
a
problem?
You
know
that
yeah
yeah.
I
see
a
lot
of
things
going
up.
So
so,
let's,
let's
look
at
this
from
a
developer
perspective
and
especially
from
an
app
developer
perspective.
C
Yeah
that
that's
a
that's
a
great
question
and
I
I
hope
the
answer
is
your
cluster
administrators
can
set
it
up
correctly.
So
it's
not
a
terrible
burden,
but
I'm
looking
at
tim
blinking
behind
his
mask
and
I
think
maybe
he
thinks
well
how
much
of
a
terrible
burden
do.
We
expect
this
to
be
for
people.
D
My
feeling
here
is,
if
you
don't
know
you
care,
you,
don't
care.
This
is
a
space
where
you
shouldn't
most
people
should
not
have
to
care
98
of
of
applications
and
users.
This
should
be
transparent
to
them
and
for
those
people
who
do
care,
that's
where
the
apis
that
we've
added
are
but
they're
all
optional,
and
we
were
like
super
rigorous
about
making
sure
that
nobody
breaks
nobody
changes
automatically
and
for
most
users,
nothing
changes,
behaviorally.
E
I
think
I
don't
agree
with
that,
really.
So
for
end
users,
what
we've
kind
of
had
with
kubernetes
and
v4
is
that
our
pods
are
almost
hidden
by
default
right.
They
don't
they're,
not
addressable
on
the
internet
and
going
down
the
v6
and
the
dual
stack
route.
All
of
your
pods
suddenly
become
addressable
and
routable
and
reachable
from
the
public
internet,
which
is
a
really
really
dangerous
thing
exactly
for
the
uneducated.
E
B
It
doesn't
mean
that
you
can
connect
to
them
all,
but
if
you
don't
set
things
up
right,
that
could
be
a
hassle
and
in
the
ipv4
internet
the
world
we
live
today,
we've
relied
on
this
system
called
nat
to
keep
everybody
safe
out
of
the
box
exactly
and
that
kind
of
goes
away
which
nat
actually
breaks
the
internet
most
of
the
time.
So
I'm
hopeful
that
in
the
ipv6
internet
we
can
actually
have
better
connectivity,
but
I
you
know
back
to
your
original
question.
B
It
should
be
as
simple
as
setting
a
field
to
say.
I
want
dual
stat
networking
so
from
a
developer
perspective,
what
we
hear
from
the
community
and
from
customers
is,
I
need
to
present
my
application
on
both
the
ipv4
internet
and
the
ipv6
internet,
and
why
they're
asking
this
is
typically
driven
today
by
regulation.
We
have
some
regulation
by
a
country
that
we
operate
in
to
have
to
present
services
that
are
part
of
a
government
or
any
kind
of
other
international
organization.
A
Yeah,
that's
that's
great
and
and-
and
I
think
it's
partly
cultural
too
right-
you
know,
for
example,
like
you
said
you
know
it.
The
perception
that
each
of
these
ips
might
be
routable
might
itself
be
a
you
know,
kind
of
a
red
flag,
so
to
say
right.
So
so
can
you
address
some
of
those
issues
of
actually,
you
know
moving
from
ipv4
to
ipv6,
not
necessarily
from
a
kubernetes
perspective,
but
from
a
general
perspective
and
and
and
kind
of
talk
about
some
of
the
challenges
there.
And
how
do
you
mitigate
them?
A
C
E
Yeah
I'd
agree
with
that.
So
I've
been
working
on
implementing
this
stuff
over
the
past
few
weeks
because
you
know
like
nothing
like
last
minute
homework
and
it
is
pretty
simple
to
get
v6
onto
a
cluster
now
in
in
the
latest
version.
So
the
improvements
are
really
good.
It's
just
that.
You
know
obviously
found
that
danger
out
the
box,
which
is
really
key.
B
B
B
And
a
lot
of
the
pathways
even
in
different
application
codes.
Those
implementations
on
different
networking
stacks
are
a
little
less
mature.
So
it's
a
really
good
way.
Hey
I
presented
on
both
and
I
start
to
get
a
feel
for
ipv6
and
how
it
operates,
and
I
start
to
get
comfortable
with
you
know:
operating
different
service
discovery.
B
All
these
different
mechanisms
and
you've
got
v4
there
to
serve
the
production
workload,
so
you've
got
a
great
way
to
start
getting
a
feel
for
how
v6
functions,
and
I
really
think
it's
key,
because
we
do
get
a
lot
of
well.
I
just
want
to
go
to
ipv6
and
I
said
well,
go
and
see
what
works
and
see
what
breaks
and
sadly,
most
customers
end
up
coming
back
and
end
up
saying.
C
And-
and
I
think
that's
related
to
the
when
we're
talking
and
all
of
us,
you
know
in
some
capacity
talk
to
production,
user
customers.
They
aren't
necessarily
in
a
green
field,
so
they
might
have
some
backing
data
store
that
uses
legacy
whatever
or
they
might
have
some
hybrid
situation
where
they
can't
put
v6
on
everything.
So
setting
up
a
hey,
we
have
an
ideal
v6
v6
scenario.
It's
great.
You
can
do
that
in
a
test
lab,
but
you
can't
necessarily
do
that
in
production
and
that's
fine,
that's
where
everyone
is
it's
not
just
you.
A
F
Hi
so
you're
saying
that
ipv6
may
not
be
for
everyone,
and
people
need
ipv4
too.
I
agree
on
some
part,
but
why
is
not
nat
64
a
solution
because
to
me
seems
that
getting
dual
stack
kind
of
brings
more
problems
than
it
solves.
You
get
the
problems
from
both
ipv4
and
ipv6,
so
preference
would
be
ipv6
cluster
with
the
net
64.
A
B
B
You
won't
wanna,
that's
fine!
That's
fine!
Okay,
okay!
So
your
application,
software
makes
no
changes
and
therefore,
even
on
the
back
end,
you're
never
actually,
testing
the
application
software
and
having
done
this
for
a
service
provider
in
the
past,
actually
getting
ipv6
end
to
end
is
actually
a
better
state
overall.
B
For
many
different
reasons,
transport
reasons,
overhead
reasons,
routing
reasons,
but
if
you
never
actually
turn
it
on
right
to
you
and
plug
it
right
into
your
application
software,
you
don't
actually
know
the
challenges
that
you're
going
to
face
in
service
discovery
and
a
whole
bunch
of
other
things.
So
I
think
getting
that
end
to
end
connectivity,
because
we
come
from
the
ipv4
world
and
we
all
grew
up
under
it.
B
I
think
you
know
that
is
that's
been
one
way
to
actually
do
this,
but
I
think
what
we
want
to
get
out
of
is
is
being
hinged
to
netting
forever
and
keeping
ipv4.
Now,
on
the
back
end
too,
large
clusters
is
becoming
a
thing.
Now
we
can't
go
to
a
customer
and
say
give
us
a
slash
8,
because
you
want
to
run
70
000
pods.
B
D
I
I
hope,
I'm
hopeful
that
dual
stack
is
a
is
a
transitory
thing
right
and
as
people
get
more
familiar
with
v6
and
the
v6
internet,
you
know
becomes
a
complete
thing
that
people
will
start
to
drain
off
their
needs
for
v4
right
and
we'll
be
able
to
see
those
things
end
of
life.
Over
time
I
mean
that's
the
goal
for
the
last
20
years,
but
this
time
we're
for
real.
E
And
having
implemented
v6
recently
as
well,
it
wasn't
just
for
clusters,
v4
nat
versus
v6,
rootable,
everywhere.
V6
rootable
is
absolutely
a
joy
to
use
when
you
get
it
set
up
and
you
understand
it
and
you
put
a
really
simple
addressing
structure
into
your
whole
network.
Everything
just
falls
into
place.
D
Kubernetes
was
designed
on
an
assumption
that
all
pods
were
reachable
and
that
they
were
on
the
larger
network
right,
and
that
was
great
at
sort
of
small
scale.
It
doesn't
work
everywhere,
especially
in
big
places
where
you
know
there
isn't
a
slash,
eight
or
slash
16,
to
give
you,
and
so
we
we
find
a
lot
of
customers
users
doing
what
we
call
island
mode
right.
D
I've
written
some
talks
on
this
and
they
put
their
clusters
in
an
island,
and
then
they
only
poke
holes
or
build
bridges
off
the
island
for
specific
services
and
that
works.
But
it's
not
what
kubernetes
was
really
designed
to
do
and
so
we're
seeing
now
with
dual
stack
people
who
do
island,
v4
and
flat
v6,
and
we
think
that's
a
really
nice
intermediate
step.
Yeah.
A
So
I
don't,
I
don't
want
to
forget
the
virtual
audience
I'll
come
to
you
in
a
second,
but
here's
a
question.
I
don't
want
you
guys
to
turn
back,
but
I'll
read
it
out.
My
organization
would
like
to
use
ipv6
ula
addresses
in
both
on-prem
and
public
cloud
hosted
communities,
but
this
still
seems
to
be
on
the
roadmap
correct.
What's
the
underlying
issue
for
this
coming
later.
B
Here
yeah,
so
there
are
many
different
address
types
in
ipv6,
ula
is
one,
so
it's
just
different
levels
of
addressing.
I
think
what
we
wanted
to
do
so
to
throw
the
the
answer
back
is
we'd
love
to
hear
about
your
use
case
and
actually
understand
how
we
want
to
do
addressing
and
which
addressing
so,
which
link
local,
addressing
ulas.
We
want
to
understand
how
you
want
this
to
operate.
B
I've
heard
this
feedback,
so
if,
if
you're
the
one
asking
the
question,
please
come
talk
to
sig
network
and
give
us
the
feedback,
because
if
you
want
to
do
different
addressing
schemes,
we
basically
came
up
with
one
that
worked
to
serve
a
function
to
get
the
feature
on
the
ground
and
start
getting
feedback.
So
I
have
heard
this
more
than
once
and
I
would
love
either
an
issue
in
sig
network,
so
we
can
start
to
discuss
but
bring
your
use
case.
We
really
want
to
understand
how
you
want
to
carve
up
the
addresses.
C
D
B
G
Over
there
yeah,
so
I
have
a
question
around
the
security
or
default
security
with
not
for
v4,
so
we
had
that
default
security.
Is
there
a
way,
or
are
you
currently
working
on
a
solution
for
v6
that
you
can
have
a
network
policy
as
a
default
for
the
whole
cluster,
so
that
developers
are
not
accidentally
exposing
services
and.
A
I
think
I
think
this
is
a
you
know.
There's
a
ramification
in
general
right
I
mean
kubernetes
ipv6,
the
dual
stack
pretty
much
hit
every
component
in
kubernetes
right.
You
know
not
just
security
right,
so
maybe
security
is
one
manifestation
of
that,
but
but
maybe
you
can
address
it
generally
as
well.
D
B
I
I
can
jump
in
there
too,
unless
jumping
anybody
else
wants
to
jump
in.
So
what
we
needed
to
do
because
we
kept
rags,
can
I
can
you
move
to
that
way?
So
I
can
at
least
address
the
person
asking
questions.
Sorry,
what
we
needed
to
do,
because
we
kept
getting
stuck,
was
none
of
the
upper
level.
Abstractions
could
consume
dual
stack
or
even
ipv6,
because
nobody
was
using
it
right,
so
we
needed
to
create
all
the
core
apis
and
componentry.
B
So
if
that's
you
again,
please
come
and
talk
to
us
and
talk
to
your
you
know
cloud
network
provider
or
whoever
you're
using
to
get
your
ip
addresses,
because
if
it's
you
sorry
I'm
putting
that
back
on
you,
but
we
need
to
start
showing
examples
and
getting
it
throughout
the
documentation.
But
this
we
couldn't
put
the
horse
before
the
cart.
You
know
what
what
I
mean.
We
couldn't
start
writing
about
upper
level,
things
that
needed
to
come
into
play
like
all
the
cni
providers
and
how
that
works.
B
We
needed
to
get
the
core
apis
in
and
that's
what
we've
done
so
now
that
people
can
play
with
this,
we
can
actually
rationalize.
Well,
how
do
we
model
default
network
policies
at
an
ipv6
level,
because
we
were
everything
was
stuck
on?
Well,
I
don't
have
it
and
nobody
was
using
ipv6
on
its
own
or
very
little
people.
So
I'm
hoping
that
you
know
this
kind
of
gets
the
conversation
around.
How
do
we
model
those
things?
In
addition
to
what
tim
was
saying,
yeah.
Thank
you.
C
B
I
think
making
it
very
easy
to
get
a
cluster,
that's
configured
correctly
out
of
the
box,
and
I
think
we're
seeing
that
I'm
seeing
more
and
more
more
of
the
tools.
I
think
there
was
a
talk
from
the
folks
that
work
on
cops
that
they
have
ipv6
and
how
they
implemented
that
so
more
tools,
implementation.
So
they
can
see
it
and
then
just
for
managed
service
providers
make
it's
very
easy
to
get
a
cluster.
B
That's
either
ipv6
only
which
I'm
seeing
a
lot
of
or
dual
stack
out
of
the
box,
so
I
think
making
it
really
simple
to
deploy
so
that
people
can
start
using
it
and
giving
us
more
feedback
on
these
specific
features.
That
would
be
my
goal
is
making
it
really
simple
and
across
all
the
tooling.
I
think
the
talk
was
on
cops.
B
D
D
B
I
E
I
mean
that
they're
still
gonna
play
a
part
right
because
they're
not
doing
just.
Do
you
mind,
do
you
mind
repeating
the
question?
If
you
don't
mind,
yeah
question
was
load
balancers,
whether
they
still
play
a
part
in
either
a
v6
or
a
dual
stack
world
and
they're
going
to
play
a
part
because
they're
doing
things
more
things
than
just
nat,
which
is
what
traditionally,
we
kind
of
use
load
balancers
for
so
the
load
balancing
things
like
a
b
workflow
and
deployments.
E
D
B
D
A
B
Short
answer
is
yes,
the
the
long
answer
is
the
great
thing
is
now
it
can
be
transparent
to
the
actual
user,
so
the
provider
can
actually
do
that
hand
off
and
you,
as
the
user
could
have
end-to-end
encryption
on
your
network
without
having
any
special
software
required
or
third-party
software
to
do
the
negotiation
of
that
ipsec
tunnel.
So
I
think
it's
it's
a
very
interesting
place
and
that's
one
of
the
benefits
of
ipv6,
and
I
think
you
know
again,
a
lot
of
the
community
was
stuck
on.
B
You
know,
let's,
let's
be
clear:
we
we
took
v6
only
clusters
and
brought
them
along
for
the
ride.
They
had
been
stuck
in
alpha
and
when
we
picked
up
dual
stack,
we
said:
we've
got
to
take
everything
across
the
line
here,
having
all
this
core
componentry
in
kubernetes
itself,
I
think
now
we
can
experiment
with
the
bits
and
pieces,
because
the
conversation
before
was
well.
Kubernetes
doesn't
support
it.
B
So
therefore,
I
can't
do
anything
with
it,
and
so
I
think
yes,
you
could
bake
that
in
should
be
transparent
to
the
kubernetes
user,
but
we
could
get
pretty
crafty
in
ipv6
land
where
the
you
know,
south
of
the
cni,
where
you
set
up
point-to-point
encryption
out
of
the
box
and
not
have
to
deal
with
that
at
mtls
layout.
That's
just
something
you
could
do.
C
A
B
K
A
A
C
We
have
an
ipv6
panel
next
year.
I
would
really
love
it
to
be
folks
from
the
community
who
are
implementing
it,
because
we
have
one
here,
and
I
want
to
hear
a
little
bit
more
about
what
you're
implementing
now,
but
keep
in
mind
that
these
conversations
are
not
a
broadcast
of
us
to
youth.
These
are
the
conversations
where
you're
telling
your
stories
amongst
each
other
over
time
and
we're
building
together
what
you
want
it
to
be.
C
B
Yeah,
I
think
you
know
my
goal
here
today-
was
just
to
educate
and
get
the
word
out
that
this
exists
and
that
I
would
really
love
to
see
end
users
up
here
talking
about
their
experi
experience,
and
you
know
sig
network
we're
listening
as
well.
We
want
to
hear
if
this
works
and
meets
the
needs
of
the
people
that
are
trying
to
utilize
it.
So
I
think
it's
six
months.
I
think
if
it's
across
all
providers
and
there's
one
click,
give
me
a
kubernetes
cluster
with
dual
stack
or
v6.
E
I'd
love
to
see
more
v6
only
clusters
really
because
there's
a
huge
amount
of
the
internet.
You
know
like,
like
github,
that
you
just
don't
know,
hasn't
configured
it
so
getting
more
people
using
it,
testing
it
and
feeding
back
to
the
entire
internet
community
about
what
works
and
doesn't
work,
we're
just
going
to
keep
pushing
that
v4
to
v6
transition
down
the
line.