►
From YouTube: Webinar: What’s New in Kubernetes 1.18
Description
The release team will cover the new features in Kubernetes 1.18
Presenters: Jeremy Rickard, Enhancements Lead, Jorge Alacron, Release Lead, and Karen Chu, Communications Lead
A
Get
started
I'd
like
to
thank
everyone
who
is
joining
us
today.
Welcome
to
today's
ciencia
webinar,
what's
new
in
kubernetes,
1.18,
I'm,
Karen,
Chiu,
community
program
manager
at
Microsoft
and
CNC,
an
ambassador
and
I
will
be
moderating.
Today's
webinar
we
like
to
welcome
our
presenters.
Today
we
have
Jeremy
Rickard
enhancements,
lead,
George,
alicorn,
release,
lead
and
myself
the
comms
lead
from
1.18,
and
just
before
we
start
a
few
housekeeping
items
during
the
webinar.
You
are
not
able
to
talk
as
an
attendee.
There
is
a
Q&A
box
at
the
bottom
of
your
screen.
A
Please
feel
free
to
drop
in
your
questions
there
and
we'll
get
through
as
many
as
we
can.
At
the
end.
This
is
an
official
webinar
of
the
CNCs
and,
as
such
is
subject
to
the
CN
CF
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
just
be
respectful
of
all
your
fellow
participants
and
presenters.
A
B
Much
Karen
so
we'll
start
off
today,
just
by
giving
a
little
brief
overview
about
the
the
logo
for
the
118
release,
every
release
has
has
its
own
personality
and
its
own
kind
of
representation.
If
you
remember
the
116
release,
there
was
a
great
logo
based
around
breadsticks
Maki,
who
is
the
release,
lead,
that's
a
big
fan
of
breadsticks
and
the
Olive
Garden,
so
that
kind
of
featured
into
the
through
the
release.
So
let's
start
off
this
webinar
by
having
a
little
bit
of
background
on
how
this
came
to
be
yeah.
C
C
Have
the
privilege
of
design
designing
the
logo
for
the
a
for
the
a
for
the
given
release
a
slave
for
one
eating
I
took
the
opportunity
and
run
with
it
in
the
logo
for
one
ending
a
one,
then
it's
inspired
by
the
LHC
it
a
Large,
Hadron
Collider,
which
is
a
annex
and
physics
experiment
meant
to
explore
the
three
fundamental
questions
of
a
really
fundamental
questions
of
physics
at
least
part
of
this
product.
A
part
of
the
motivation
is
because
before
I
say,
actually
started
working
as
a
software.
C
A
software
engineer,
I
was
a
physicist
and
I
keep
the
physics
around
still,
even
even
to
this
point
every
now
and
then,
and
one
a
wanted
to
take
the
opportunity
to
take
the
opportunity
to
talk
about
a
little
bit
about
physics
and
the
other
one
is
that
the
LHC
is
like
the
Cabrini,
like
the
kubernetes
communities,
have
really
large
clay,
a
really
large
collaboration.
They
have
thousands
of
people
from
a
from
all
around
the
globe.
C
Constantly
working
towards
trying
to
gain
a
better
understanding
of
the
underline,
underline,
loss
of
physics
and
like
the
Cabernet
like
the
kubernetes
community,
like
the
kubernetes
community,
they
are
very
inclusive
and
they
are
doing
a.
They
are
doing
a
lot,
a
lot
of
really
meaningful
and
super
in
a
super
interesting.
B
B
Thanks,
so
today,
the
agenda
for
this
webinar
is
gonna.
Allow
us
to
give
you
a
little
bit
of
an
overview
of
118,
we'll
give
you
a
couple
of
quick
highlights
of
things
that
we
think
are
super
important
to
bring
forward.
We'll
also
give
you
a
really
quick
update
on
the
119
release
with
things
that
are
going
on
and
then.
B
A
little
bit
of
an
overview
of
each
one
of
the
enhancements
that
came
into
the
release
will
also
have
a
period
of
Q&A
at
the
end.
So,
first
up,
let's
talk
about
the
119
release
because
that's
kicking
off
right
now,
so
we're
here
to
talk
about
118,
but
one
my
team
is
pretty
relevant,
I.
Think
as
well
as
consumers
of
kubernetes.
You
might
be
interested
to
know
when
the
119
release
will
happen.
B
Originally,
that
was
supposed
to
be
June
30th,
but
because
of
everything
that's
happening
in
the
world,
it's
been
extended
a
little
bit,
so
the
new
target
date
is
August
4th.
There's
a
lot
of
changes
that
are
going
into
this
with
with
regard
to
the
the
timelines
and
the
dates
within
the
release.
But
we
wanted
to
make
you
aware
of
just
when
the
the
target
of
the
the
119
really
should
be.
So
you
can
kind
of
do
some
better
planning
about
when
you
might
adopt
that
release.
B
If
you're
interested
in
reading
more,
the
slides
will
be
available
at
the
end,
but
I've
included
a
link
here
to
discussion
forum
and
the
Cabrini's
dev
mailing
list,
where
a
lot
of
these
things
have
been
spelled
out.
So
you
can
see
some
very
specific
things
like
what's
gonna
happen
if
120
afterwards,
what
are
some
of
the
changes
we're
trying
to
implement
within.
C
C
Way,
one
quick
thing,
but
also,
but
a
with
the
changes
in
the
way,
119
a
release,
and
this
way
this
will
possibly
also
be
very
similar
to
the
way
for
the
120
release.
So
there
is
so
they
wanted
a
usually
we
have
formally
a
four
releases
per
year
this
year,
we're
only
gonna
have
one
in
a
118,
118
and
120
120,
that's
a
grim
plan
and
one
additional
change.
That's
going
to
a
one
additional
change.
That's
going
to
happen
is
that
a
the
release
team
is
going
to
start
publishing
a
lot
more
release
candidates.
C
So
all
the
things
that
we're
going
to
be
talking
about
right
here,
a
one
good
place
to
test
them
out,
was
with
the
kubernetes
release
candidate,
which
was
released
before
the
official
one.
A
one
18.0
release
and
1:18
is
gonna
have
a
lot
more
of
those
say
so,
okay,
so
all
the
new
enhancements
are
being
worked
on.
You
can
actually
you
can
actually
try
them
out
and
kick
the
air
kick
the
tires
with
them.
Yeah.
B
B
What
that
means
that
they've
graduated
to
being
fully
released
and
supported
you
can
expect
them
to
live
forever
with
some
level
of
confidence
within
kubernetes
and
not
change
too
much
11
of
those
things
graduated
to
beta,
which
means
that
they
think
that
the
people
working
on
those
features
think
that
the
API
is
reaching
the
point
of
stability.
Changes
could
happen
going
forward,
but
you
can
expect
them
to
probably
live
and
have
a
certain
set
of
stability
and
testing
going
into
them.
B
Those
things
are
usually
enabled
by
default
as
well,
and
then
twelve
things
were
introduced
as
alpha
features.
Those
are
brand
new
things
that
are
being
added
to
committees,
they're
gonna,
be
behind
feature
gates,
so
it's
to
use
them
you'll
have
to
enable
them
to
take
advantage
of
those
features.
But
you
can
see
it's
a
pretty
good
spread
almost
equally
divided
between
the
categories,
giving
us
a
good
mix
of
brand
new
things
and
some
promotions
of
things
that
have
been
around
for
a
little
while
so
I'll
turn
it
over
to
Jorge.
C
We
also
have
a
nickel,
a
an
equal
proportion
of
features
that
are
going
to
be
stable
in
a
way
we
believe,
but
they
are
completely
ready
for
brother
for
products
use
a
and
with
that,
let's
come
to
the
next
slide
to
see
some
a
some
a
some
of
the
changes
that
we
want
to
highlight
out
a
out
of
the
bag.
One
day
one
of
them
is
actually
flying,
go
one
of
the
a
lot
of
a
lot
of
people
use
kubernetes
to
host
their
applications
and
put
one
another.
C
Besides,
taking
a
taking
a
context
and
some
information
about
the
kubernetes
object
that
you
want
to
handle
a
you
know,
for
example,
a
config
map
or
a
pod
they're,
also
going
to
take
some
options,
kind
of
a
options,
kind
of
argument
which
a
where
you
can
specify
some
additional
made
a
metadata
for
a
for
a
furniture
operation
and
one
project.
In
that
a
that
is
being
developed
within
the
game
within
the
coronaries
organization.
A
you
can
actually
find
the
incorporated
sake
in
github.com
cover
96
client
go
fix.
This
one
is
going
to
help.
C
B
I
mean
I
think
the
tool
is
really
useful.
Manually
upgrading
to
clang
go
118
obviously
introduces
these
changes.
The
context
1
is
pretty
big,
but
the
the
other
ones
too
like
when
you
have
a
delete
operation.
Previously
it
accepted
things
by
reference,
and
now
it's
my
value.
So
there's
just
a
lot
of
changes
that
you
have
to
go
through.
I
had
changes
across
like
54
files
in
this
project
that
I
was
updating
yesterday
and
clang.
Go
fix
is
pretty
nice.
C
On
to
a
stability,
a
completely
couple
of
enhancements
that
one
inform
a
form
180
in
are
to
improve
this
double
a
the
improve.
The
stability
of
the
project
in
really
cool
ways
are
a
pain
base.
Evictions,
a
cubicle,
Dave,
API
server
child
run,
CI,
a
CSI
block,
storage,
support
and
windows
improvements
improvements
over
a
overall.
You
can
see
that
people
a
that
people
have
been
working
in
almost
all
areas
of
kubernetes.
Equally
it
you
have
eight,
you
have
some
tools
and
put
it
improve.
C
B
C
And
as
far
as
new
things
go,
we
all
say
we
a.
We
have
also
seen
some
enhancements
a
try
to
tackle
a
try
to
tackle
some
a
some
case.
Some
complex
issues
that
a
that
a
that
people
a
that
people
have
come
across
a
lot
of
organization.
A
lot
of
organizations
are
using
kubernetes
and-
and
you
know,
for
a
for
the
most
part-
and
you
have
your
standard
clusters
with
some
things
for
hundreds
of
notes.
C
But
a
lot
of
a
lot
of
people
are
really
pushing
the
boundaries
with
the
kind
of
things
that
you
can
do
with
kubernetes,
and
we
have
seen
a
lot
of
issues
when
you
are
running
thousand
thousands
of
parts
of
thousand
eight
thousands
of
nodes
and
one
a
one
of
the
really
cool
enhancements.
I
came
into.
One
important
is
priority
and
furnace
for
API
server
requests
it
this
more
or
less,
and
it
enables
us
to
we
have
a
more
reliable,
install
the
installation
of
kubernetes
or
we
able
we
can
actually
separate
separate.
C
The
requests
are
a
landing
into
the
API
server
and
we
can
travel
some
of
them
to
a
to
allow
for
they
turn
up.
For
the
most
important,
a
told
that
for
other
important,
a
request
to
go
in
and
and
allow
a
allowed
people
a
a
lot
of
people
to
have
a
more
consistent
user,
a
user
experience
where
a
when
interacting
with
that
will
a
really
low
a
low
red
cluster
it
the
other
a
another
cold.
C
One
is
a
cube
color
of
the
ball
game,
like
all
the
other
enhancements
that
I'm
mentioning
a
we're
going
to
talk
about
a
more
about
this
one
later
on.
But
if
you
have
her
about
it,
a
just
know
that
this
is
a
that
this
is
on
the
works
and
that
so
a
and
is
a
close,
a
and
each
day's
closer
and
closer
to
be
a
to
be
an
GA.
It
will
keep
a
keep
color
on
the
Bob.
It's
definitely
going
to
be
definitely
going
to
be
a
game-changer
configure.
C
A
configurable
HP,
a
scalpel,
OCD,
I,
HPA
I
saw
a
HPA
at
this
point
in
time
is
something
so
sorry
Curtis
so
having
more
ways
to
tune
it.
It's
gonna,
it's
gonna,
be
amazing
and
immutable
secrets
and
config
maps
also
help
a
the
developers
interact.
We
interact
with
the
kubernetes
cluster
in
a
more
secure,
a
secure
manner
to
prevent
any
accidental
mistakes
or
applies.
B
Right
thanks
for
giving
us
those
quick
overviews,
so
next
we're
gonna
go
through
updates
for
each
one
of
the
six.
So
when
things
are
worked
on
in
kubernetes,
they
generally
fall
underneath
of
the
purview
of
a
cig,
so
that
could
be
something
like
authentication
or
API
machinery
or
storage.
So
each
one
of
the
updates
that
comes
into
the
release
is
is
kind
of
shepherded
by
the
SIG's
and
they
have
responsibility
for
getting
it
across
the
line.
B
So
we've
organized
things
by
sig,
so
you
can
give
you
a
better
understanding
of
how
things
have
changed
in
the
release.
It'll
start
out
with
API
machinery
so,
like
we
previously
mentioned
priority
and
fairness
for
API
server
requests
is
one
that
came
in
and
for
each
one
of
these
items,
when
you
get
the
slides
later
on,
you
can
actually
click
through
to
the
tracking
issue
and
the
enhancement
proposal
or
cap
to
see
what's
been
proposed,
what's
been
implemented
so
far,
and
what
the
plans
are
for
each
one
of
these
things
going
forward
in
the
notes.
B
We've
also
included
blogs,
so
in
some
of
these
features
had
dedicated
blogs
written
for
them.
Some
of
them
didn't
this
one
did
so
in
speaker.
Notes
for
this
you'll
be
able
to
find
a
nice
overview
of
this
feature
so,
but
at
a
high
level,
this
is
a
brand
new
one
coming
into
the
into
the
release
into
kubernetes,
and
we
mentioned
previously
that
things
kind
of
broke
down
between
the
lines
of
alpha
beta
and
stable.
B
This
was
one
that's
brand
new,
so
it
is
an
alpha
issue
and
and
really
in
addition
to
what
we've
mentioned
for
this
one
already.
This
really
helps
us
prevent
you
know:
clobbering,
the
API
server
under
heavy
load,
keeping
things
going,
keeping
people
from
stepping
on
each
other
when
they're,
making
API
server
requests.
B
Next
one
is
AP
I--
server
network
proxy
kept
proxy
to
beta.
Some
of
the
titles
here
are
not
some
because
everybody
seen
it:
okay,
okay,
these
are
the
the
titles
from
the
issues
in
the
repository,
so
they
need
probably
a
little
bit
of
massaging,
but
here
you
know
we're
moving
the
API
server
Network
proxy
to
beta.
So
this
is
something
that's
existed.
Land
almost
landed
in
117
didn't
quite
make
it,
so
it's
made
it
into
118.
It
allows
you
to
separate
user
and
user
initiated
network
traffic
from
API
server,
initiated
traffic.
C
Okay,
I
didn't
today
adding
to
this
enhancement
a
every
one
way.
One
quick
note
is
that
if
the
usefulness
of
this
of
this
fail,
this
one
of
the
one
of
the
things
that
you
can
really
tackle
with
this
one
is
that
if
you
can
differentiate
with
a
if
your
traffic
is
coming
from
users
or
from
a
or
from
actual
applications,
you
can
be
more
restrict
when
it
comes
to
a
security,
security
and
compliance
to
only
allow
sort
of
a
certain
a
certain
entities
to
do
certain
types
of
operations.
So
there's
this
innate.
C
This
enhancement
is
something
that's
been
mentioned,
a
lot
by
cloud
providers
who
want
to
enable
eight
users
to
have
a
more
secure
experience
when
working
with
manage
govern
a
kubernetes
or
a
offerings.
But
you
know
same
way
same
in
hey
this
enhancement
can
really
be.
It
can
really
be
used
in
a
INE
one
in
the
a
in
that
kind
of
manner.
So
if
anyone,
if
anyone
has
uses
word
UK,
but
you
will
actually
want
to
know
whether
it
user
is
doing
something
or
manage
application,
is,
is
doing
something
else.
B
B
When
something
is
in
alpha
by
default,
it's
not
going
to
be
turned
on
you'll
have
to
go
and
enable
that
in
the
feature
flag,
when
things
go
to
beta
they're
on
by
default,
so
you
can
turn
them
off.
If
you
don't
want
to
use
them,
but
by
default
they
will
be
on
and
then,
when
things
move
to
stable,
the
feature
flag
is
dropped,
so
the
feature
just
becomes
part
of
all
installations
of
Cabrini's.
B
C
Tell
you
whether
something
happen
or
not,
but
at
least
with
the
API
server
tried
around
actually
a
7s
and
then
the
request
all
the
way
to
the
API
server
passing
through
any
admission
web
hooks
or
anything.
So
you
have
configure
along
the
weight
of
my
time.
I
ate
I
might
change
the
way
the
your
manifest
is
going
to
be
handle
and
created
on
the
cluster
it.
This
is
going
to
be
a.
C
This
is
going
to
give
you
all
that
information,
all
that
information
that
you
need
and
if
you
use
cube
Caudill
a
cube,
coral
apply
dry
run
it's
going
to
do
the
client
a
diff
by
default
a
so.
If
you
just
dry
run,
that's
a
that's!
What's
going
to
happen,
if
you
want
a,
if
you
actually
want
the
API
server
to
it,
you
have
to
specify
a
dry
barnacle
server.
Yeah.
B
That's
a
great
point,
thank
you
so
much!
Okay!
So
back
to
our
client
go
issue.
We
talked
about
before
we're
giving
you
a
little
bit
of
an
example
here.
But
again
this
is
a
change
to
client
go.
You
can
see
that
the
structure
of
calls
change
so
when
we
want
to
get
pods
using
client
go.
It
looks
a
little
something
like
this.
You
asked
for
the
core
v1
API
group
and
then
you
would
ask
for
pods
in
a
certain
namespace
and
then
you
do
the
operation
of
get
before
you
used
clang
go
from
118.
B
B
Don't
have
that
so
you'd
still
have
to
change
imports
and
and
whatnot,
but
you
can
keep
the
signatures
around
for
a
little
bit
longer,
but
that
will
be
removed
in
121,
so
you'll
eventually
have
to
make
this
transition
anyway.
In
the
speaker
notes
here
again,
we've
linked
to
the
client
go
fix
tool
thanks
to
Jordan
Leggett.
For
that
it's
it's
really
useful,
all
right
now
on
to
sig
architecture,.
C
Subway,
so
one
of
the
first
enhancements
from
cigarette
textured
that
we
are
going
to
talk
about
is
enabled
warning
conformance
test
with
our
beta
rest.
Api
is
or
features,
and
so
is
so
at
least
some
context
that
is
really
useful
when
today,
when
talking
about
a
conformance,
is
that
this
tests
are
supposed.
These
are
end-to-end
tests
are
a
managed
and
maintained
by
kubernetes
contributors.
Entities
live
with
the
rest
of
the
ladies
code.
C
To
that
end,
a
conformance
test
tend
to
on
the
test
a
product
production,
a
production,
ready,
a
production,
ready
features
because
anything
that
anything
that
is
in
alpha
it
might
partially
work
you
may
have
so
it
may
have
some
changes
with
a
we
don't
really
know,
and
hence
it's
been
kept
in
alpha
things
are
in
beta
are
a
little
bit
more
say
a
little
bit
more
stable,
but
we
don't
really
have
any
sense
that
they
are
okay,
you
know
they
they
might
stay,
they
may
still
change
so
I'm
a
so.
How
many
have
you
know?
C
I
have
in
the
set
of
conformance
test
only
test
out
a
GAAP
I
serve
a
GAAP
ice
and
features.
It's
really
helpful
for
people
who
manage
their
own
kubernetes
clusters
to
ensure
that
your
installation,
your
installation
processes,
work
in
sa
a
as
expected
and
an
equal
to
useful
for
any
way
for
anyone
who
manage
a
who
manages
kubernetes
cluster
for
other
organizations
or
other
or
other
users.
B
Oh,
I
DC
discovery
endpoints
in
the
api
server
to
be
used
outside
of
the
api
server,
and
this
is
cool
because
it
enables
you
to
do
things
like
use,
authentication
tokens
from
kubernetes
to
use
as
a
general
authentication
mechanism,
so
you
could
use
it
for
services
outside
the
cluster
as
well
and
federate
things
to
other
clusters.
It's
kind
of
neat
next
is
some
changes
to
the
certificate
signing
request
API.
C
And
one
of
the
enhancements
I
already
mentioned
a
from
gigolo
scaling
is
second
feast
a
capacity
they
have
already
to
configure
the
scale
below
silly
of
horizonte
HPA,
which
stands
for
horizontal
boy,
or
example
on
our
scalars,
so
in
the
air.
So
in
this
case
you,
whenever
a
whenever
you
have
a
employment,
stay
filter
or
something
something
of
the
sort.
Normally
you
have
the
capacity.
Normally
you
have
take
capacity
to
specify
what
threshold
of
CPU
or
memory
utilization
please.
C
These
resources
should
be
using
and
how
how
to
scale
up
whether
you
have
a
minimum
from
a
number
of
replicas
from
maximum
number
of
replicas
and
then
HPA
handle
how
many
replicas
to
took
it
to
create
based
on
the
based
on
the
utilization
and
the
target
is
utilization,
one
new,
a
one-day
one
new
way.
The
articles,
a
auto
scaling
is
a
enabling
us
to
country
to
fight
through
this
process
is
by
allowing
a
allowing
us
to
tell
HP
HP
a
resources
how
how
fast
to
scale
and,
for
example,
in
the
slice
you
can
it.
C
You
can
see
how
that's
going
to
look
so,
whenever
you've
defined
in
your
HP
a
may
manifest
in
GMO
you
can
have.
You
can
have
something
like
behavior
scale
of
your
policies,
and
now
you
can
end
now.
You
can
actually
say
I
want
to
scale
up
by
these
by
this
percentage
and
then
in
that
way,
in
that
we
just
I
that
come
over
a
accommodate
the
behavior
of
the
closer
to
your
particular
a
to
your
particular
application.
B
All
right,
let's
move
on
to
six
CLI
now
and
the
first
one
that
we'll
talk
about
is
that
debug
command
that
we
mentioned
earlier.
This
one
actually
builds
on
top
of
the
ephemeral
containers.
Alpha
feature
that
was
introduced
a
little
while
ago,
and
what
this
allows
you
to
do
is
to
add
pot,
so
the
femoral
containers
enhancement
allows
you
to
add
new
pods
or
containers
to
a
pod.
So
maybe
you
deploy
your
your
workloads
normally
and
you.
B
You
follow
good
practices,
and
you
don't
include
things
like
a
shell,
or
you
know
the
ability
to
like
to
run
bash
inside
of
that
container.
You
want
to
lower
the
the
attack
vectors
right,
but
it
also
makes
it
a
little
bit
tricky
to
debug,
sometimes
so
ephemeral
containers
allow
you
to
spin
up
a
new
container
inside
of
that
pod
that
might
be
able
to.
B
You
know,
share
a
volume
or
do
some
other
things
to
help
you
take
advantage
of,
or
do
some
debugging
to
do
that,
though
there
wasn't
really
anything
exposed
in
coop
CTL
to
help
you
do
that.
So
that
is
what
this
debug
command
is
doing.
This
is
allowing
you
to
to
take
a
pod,
that's
already
running
and
add
an
ephemeral
debug
container
to
it.
You
can
find
some
more
information
in
the
enhanced
proposal
to
see
what
they
plan
on
adding.
C
C
The
best
thing
that
you
could
do
is
to
compile
that
web
server
way,
so
that
you
end
up
only
with
a
binary,
then
de
binary
copied
into
a
container
using
at
least
relays,
contain
a
container
image
that
this
release
container
image
is
only
going
to
have
enough
resources
for
you,
a
binary
to
be
executed
and
run
is,
but
it's
not
going
to
have
any
bash
is
not
going
to
have
any
other
utilities.
There
is
no
way
for
you
to
install
anything.
C
So
if
you
actually
do
something
like
you
cut
off
the
book,
you
can
create
a
new
container
and
run
it
within
the
same
set
of
a
Linux
namespaces,
so
build
a
so
that
you
can
actually
interact
with
your
update.
You
can
actually
interact
with
a
with
your
application,
so
something
that
you
could
do
in
a
production,
for
example,
is
to
have
your
web
server
up
and
running,
and
then
you
run
your
additional
container
in
that
one.
You
installed
something
like
curled
and
then
you
create
your
girl
from
localhost.
B
Yeah
I
think
it's
a
it's
a
perfect
use
case
to
show
how
to
use
that,
so
the
next
one
is
coops
detailed.
If
so,
this
allows
you
to
compare
an
object
on
your
file
system.
So
if
you
have
a
Yama
file
defines
maybe
a
deployment
or
some
other
resource,
and
you
want
to
compare
that
against
what's
actually
running
in
the
cluster,
so
you
can
kind
of
compare
that
state
that
you
think
it
might
be
with
what
it
actually
is.
Then
this
commands
very
useful
for
that
again.
This
is
a
stable
one.
B
It's
been
around
for
a
little
while
and
it's
ready
to
use
in
production
this
one's
not
really
a
super
user
facing
one,
but
it's
interesting
to
track,
especially
if
you're
building
anything
that
depends
on
the
code.
The
coupe's
detail
package
itself
has
moved
to
a
new
repo,
so
you
can
find
some
more
information
about
this
in
the
enhancement
proposal
as
well.
C
C
One
of
the
areas
where
we
have
been
trying
to
improve
it
in
the
past
is
to
move
the
cloud
provider
from
inside
of
kubernetes
it's
a
to
it,
so
it
with
some
place
so
that
they
can
be
developed
in
my
a
maintain
a
separate
separately
from
the
coronaries
see
a
similarly
similar
to
the
previous
enhancement
that
we
just
mentioned
where
people
wanted
to
move
in
all
the
code
for
cube
kernel
outside
and
in
in
this
case,
a
piece
fear
is
gone.
It's
one
of
the
first
club,
a
club
provider.
C
B
Lifecycle,
so
the
first
one
here
is
support
for
Windows
and
Kuby
DM,
so
you've
actually
been
able
to
use
qbm
a
little
bit
with
Windows,
but
the
this
gives
you
the
ability
to
add
notes
to
a
COO
BDM
windows
cluster,
which
is
pretty
cool
before
you
couldn't
easily
do
that.
Kuba
DM
is
a
way
of
provisioning
clusters.
It's
tons
of
ways
you
can
get
a
cluster
of
a
kudiye
kuba
VM
is
a
really
useful
way.
It
allows
you
to
do
a
lot
of
things.
Rotate
certs,
add
nodes
to
clusters.
B
C
The
first
announcement
from
circular
working
that
a
signet
work
that
we
want
to
discuss
is
adding
a
protocol
to
services
and
endpoints.
This
one
is
alpha
K,
alpha
gated,
so
the
only
way
that
you
can
actually
a
give
it
a
try
is
to
any
enable
the
feature
away
from
this
one,
and
this
enhancement
essentially
allows
us
to
expand
to
specify
whether
a
service
or
an
endpoint
is
going
to
be
using
this
TCP
UDP
CTP
or
something
always
something
on
the
sort.
And
this
this
is
related
to
a
previous
enhancement.
From
day.
C
One
7117
early
cycle
were
endpoint
slice
when
a
1
into
beta
and
endpoints
endpoint
slices
actually
actually
introduce
a
concept
of
a
protocol
which
would
allow
a
way
for
people
to
specify
a
to
specify
that
a
given
port,
it's
actually
dedicated
for
us
for
a
specific
type
of
way
for
a
specific
type
of
protocol,
and
they,
this
enhancement,
is
going
to
it's
proposing
to
us
a
to
allow
the
same
set
of
functionality.
Away
from
a
introduced
by
air
from
introduced
by
the
endpoint
slices
cap
into
is
a
normal
services
and
endpoints.
C
Then
next
one
is:
is
a
ipv6
port,
one
huge
area
of
the
below
many
kubernetes
from
the
line
for
the
couple
years.
As
we
know,
IPA
has
been
known
ipv6
and
now,
with
this
enhancement,
Koine
going
into
beta
for
the
food
again
means
up,
for
the
most
part
must
pay.
A
lot
of
people
are
going
to
be
getting
this
by
getting
this
by
default
and
you
can
actually
age.
You
can
actually
give
it
a
hey,
give
it
a
try
with
your
a
kubernetes
clusters.
This
enhancement
a
means,
an
ipv6.
Only
clusters
are
going
to.
C
C
And
they,
author,
create
the
other
couple.
Things
that
come
to
mind
is
with
pay
back
in
backing.
Companies
want
a
want
and
a
one
13:8
default.
Dns
server
server
also
change
a
core,
a
core
DNS
to
have
full
IP
ipv6
support.
So,
as
we
can
speak
on
the
yes,
we
continue
wrong
a
rolling
on
a
rolling
in,
but
this
one
it's
gonna
be
possible
to
have
all
your
kubernetes
components,
John's
a
use
IPA
just
using
56
and
the
next
enhancement,
which
is
a
new
and
put
a
new
endpoint
API.
C
This
one
is
again
in
a
Bay
innovator
status,
and
this
is
a
meant
to
replace
a
horrible
one
endpoint
and
to
mitigate
some
performance
at
scale,
a
some
performance
in
Scoville,
a
scalability
issues,
and
this
one
job
already
already
mention
it
by
another
name,
but
to
provide
the
full
story.
This
is
probably
by
the
end
points
lie,
say
a
API.
The
long-term
plan
is
to
have
this
way
to
have
this
one
AP.
C
They
decorate
like
the
tech
or
API
when
a
to
introduce
one
doing
a
when
doing
anything
with
anything
and
with
networking
they
currently
take.
The
current
service
API
has
some,
as
we
mentioned
some
press
on,
perform
a
some
performance
issues
that
were
discovered
with
scalability
test
work.
We
ramp
up
the
number
of
notes
off
to
5020
and
try
to
see
how
things
behave
and
also
a
and
did
this
enhancement
is
going
to
essentially,
instead
of
free
computing,
the
entire
list
of
endpoints.
The
service
is
using
this
and
then
notifying
all
day,
all
the
watchers.
C
All
the
entities
are
actually
watching
for
changes
to
these
same
points.
A
this
and
a
this
enhancement
is
going
to
allow
this
loop
to
be
eight
to
be
broken
down
a
to
be
broken
down
into
different
groups,
and
only
the
group
has
they
that
that
is
using
a
certain
endpoint
has
to
be
has
to
be
recomputed
to
a
computer
and
updated.
C
C
The
next
day,
the
next
one
increase
changes.
This
one
is
embed
a
this
one
is
in
beta
state,
and
this
will
this
dis
enhancement
for
118
adds
a
wallet,
are
a
support
for
Walter
host
names,
a
better
better
path
matching
and
the
Declaration
of
a
ingress
classes.
So
it's
pretty
interesting
I
think
because
it's.
B
Duplicate
slide
there
all
right,
let's
move
on
just
sick
node
now
so
the
first
one
here
is
changes
to
pod
overhead.
So
when
you
are
running
things,
there's
a
little
bit
of
non-negligible
overhead
associated
with
keeping
track
of
the
pod
quota
management,
things
that
go,
and
you
know
they're
necessary
to
run
the
workloads-
and
this
is
accounting
for
those
when
it's
making
for
the
pot
sandbox,
not
just
as
Pacific
containers,
there's
a
sandbox
that
goes
along
with
each
one
of
your
pots
and
that
wasn't
really
taken
into
consideration
when
scheduling
decisions
and
things
were
happening.
B
B
Next
one
up
is
the
topology
manager
so
giving
you
the
ability
to
run
pieces
of
kubernetes
in
and
workloads
in
in
different
hardware
topologies.
It's
basically
like,
if
you
have
some
some
GPU
nodes
or
other
things
that
you
want
to
run
low
latency
workloads
in
this
is
a
lot
of
needs
to
do
that,
and
this
was
introduced
as
an
alpha
in
116
and
it's
going
in
beta
in
118.
So
you
can
see
that
in
a
fairly
short
amount
of
time
this
is
turned
around.
B
You
can
expect
this
to
be
around
as
a
stable
thing
somewhere
down
the
road.
This
one
also
has
a
dedicated
blog
post
associated
with
it.
So
you
can
go,
read
a
lot
of
information
about
this
and
on
the
kubernetes
blog
and
again
in
the
future
notes
or
starting.
The
speaker
notes
here:
we've
included
a
link
to
that
blog.
B
Next
up
is
adding
startup
liveness
probe
hold
offs,
so
sometimes
you
have
pods
that
are
really
slow
to
start,
and
maybe
the
health
checks
or
the
liveness
probes
start
fail
and
then
the
pod
gets
killed.
This
allows
you
to
set
an
initialization
failure
threshold
so
that
you
can
back
things
off
and
not
necessarily
start
handling
the
failures,
I'm
really
slow
to
start
containers,
this
one's
beta
as
well.
B
It's
been
around
for
a
little
bit
since
116,
but
now
it's
beta
so
you'll
be
able
to
use
this
without
turning
feature
flags
on
this
one
is
actually
a
change
to
a
feature.
That's
been
stable
for
a
little
while
huge
pages
is
a
feature
that
I
haven't
really
used,
but
for
using
clusters
that
have
the
region
a
lot
of
data.
This
one
allows
you
to
make
some
changes
to
use
the
feature
a
little
bit
more
efficiently.
Again,
you
can
find
more
information
in
the
tracking
issue
and.
C
C
This
way
this
one
is
in
beta,
so
for
a
lot
of
people,
this
is
gonna,
be
turned
on
by
default
and
what
everyone
other
things
are
often
it
often
comes
up,
is
that
people
are
a
if
you,
if
you
have
a
coaster
in
a
given
region,
interviewer
has
a
multiple
available
area
availability
zones.
If
you
have
multiple,
if
you
have
multiple
replicas
to
allow
for
a
high
availability
configuration
to
a
they
optimize,
the
optimal
configuration
that
you
would
want
is
to
have
at
least
one
replica
of
your
application
running
in
each
availability
zone.
C
That
way,
if
there
is
some
issue
with
the
infrastructure
and
there's
always
going
to
be
something
open
about
a
open
available,
and
this
enhancement
essentially
improves
on
that
by
a
play
by
playing
around
with
there
and
they
it
is,
it
essentially
allows
for,
like
a
for
that,
configuration
to
happen
even
when
a
when
a
when
using
anti
affinity,
it
will
sort
in
a
or
other
in
their
path.
A
configurations.
B
C
And
like
that,
one
thing,
bass
eviction,
this
one
was
actually.
It
was
also
mentioned,
be
a
we
also
mentioned
at
the
beginning
of
this
talk
webinar
this
one
with
automatic.
If
this
may,
this
one
is
in
stable
in
this
means
an
automatically
any
tainted
notes.
We
know
a
with
no
executes,
it
will
become
already
and
returnable
a
so
in
a
nut
bolts.
Nothing
will
get
scheduled.
A
Mulligan
schedule
on
day
of
this
ones,
and
this
enhancement
has
been
beta
since
Y
is,
is
1:13
and.
A
C
The
next
thing
has
been:
is
it's
a
adding
a
configurable
default
event
both
spread?
It
will
this
again
going
up
a
talk
talking
about
highly
available
configurations
this.
This
had
so
defaults
Pentonville
to
the
post,
set
on
a
top
of
the
five
one
and
allow
operators
to
define
it
so
and
again,
another
another
tool
to
ensure
that
your
applications
are
a
highly
available
and
a
tolerant
of
any
infrastructure
failures
mm
the
next
enhancement,
a
running,
multiple
scheduling
profiles-
and
this
is
a
this-
is
particularly
a
particularly
interesting
for
the
most
part,
a
lot
of
people.
C
A
lot
of
people
can
can
get
by
with
the
with
default
behavior
and
it
would.
There
are
a
lot
of
people
that
are
using
hybrid,
are
using
and
building
hybrid,
a
hybrid
clusters.
You
know,
for
example,
a
for
example.
If
you
have
a
bunch
of
notes
to
run
a
web
servers
egg
some
way,
some
other
notes
to
run
your
end,
to
run
your
databases,
but
then
you
actually
start
doing
a
lot
of
a
machine
learning
and
like,
and
you
start
bringing
in
a
really
specialized
a
simply
really
specialized
CPUs
or
GPUs
attack.
C
Kinda
thing:
if
you
start
trading
all
your
worker
nodes,
a
like
they
are
the
same,
you
might
probably
be
missing
out
on
a
lot
of
a
lot
of
optimization
and
this
enhancement
that
just
way
and
I
just
want
stable
money
is
actually
going
to
enable
users
to
specify
the
neuron
is
scheduled
in
profile
to
tell
a
scheduler
or
multiple,
a
or
multiple
schedulers,
how
to
run
it.
Okay,
how
do
I
have
to
run
this
a
couple
different
workloads?
This
is
okay.
This
is
also
going
to
help.
This
is
also
going
to
help
for
people.
B
Was
a
lot
of
crazy
things
coming
out
of
that
sig
and
a
lot
of
them
are
staple.
The
interesting
thing,
I
think,
is
that
a
lot
of
work
goes
into
making
that
happen,
and
we
see
the
same
thing
in
sig
storage.
So
the
first
one
we'll
talk
about
is
the
ability
to
use
raw
block
devices
as
persisted
volume
sources.
This
one's
been
around
since
1/9
as
an
alpha
feature:
I
graduated,
its
beta
in
113,
and
now
it's
available
just
as
a
by
default
feature.
A
B
B
Six
storage
has
really
taken
on
the
mantle
of
pushing
things
towards
being
stable
and
then
a
pretty
interesting
one
that
it's
brand-new
is
the
ability
for
specifying
secrets
and
config
maps
as
immutable.
So
right
now,
when
you
make
a
config
map
and
you
load
it
into
a
pod,
there's
actually
a
sync
loop
that
happens.
So
if
you
make
a
change
to
that,
config
map
it'll
be
mounted
as
a
filesystem
volume
in
the
pod,
it'll
actually
reflected
in
the
pod
at
some
period
later.
B
So
what
this
allows
you
like
a
better
practice,
is
to
actually
make
a
new
config
map
and
then
do
like
a
rolling
upgrade
where
you
reference
the
new
config
map.
That's
what
really?
This
isn't
foreseen,
so
you're
able
to
specify
that
secrets
and
convicted
maps
are
immutable
and
it'll
prevent
edits
to
those
things
from
happening
and
it'll
also
disable
the
watch
loop.
So
you
won't
actually
spend
time.
You
know.
B
How
a
server
looking
at
those
things
and
then
another
new
alpha
peach
feature
is
generic
data
populate
errs?
You
can
go.
Take
a
look
at
the
enhancement
proposal
for
some
more
information
here,
but
in
112
the
data
source
field
was
added
to
the
persistent
volume
claim
spec,
and
this
is
just
enhancing
that
a
little
bit
more
and
another
stable.
So
we've
seen
whole
bunch
of
stables,
and
this
is
the
last
one
in
six
storage.
This
one
is
enabling
the
PVC
excuse
me
to
use
the
data
source
parameter
for
creating
a
new
one.
C
Now,
first,
more
control
over
how
containers
are
managed,
and
this
can
be
discovered,
move
some
limitations
and
you
prove
some
a
kubernetes
api
compatibilities.
However,
the
current
docker,
a
lot
of
people,
are
using
a
dedicated,
ocher
enterprise
tools.
So,
for
example,
the
docker
a
enterprise
18:09
release,
has
not
been
actually
updated
to
work
with
the
windows,
a
host
container
service
on
the
only
container
that
has
been
my
aim
I
created.
So
this
is
a
this
enhancement
is
actually
about
aka.
C
Can
you
knock
the
power
and
get
a
getting
a
lot
more,
a
to
wholesome
runtime
something
available
for
with
a
for
Windows
work?
Your
notes
with
these
users
will
be
able
to
take
full
advantage
of
the
LA
of
the
latest
features
and
improvements.
I
have
eight
I
have
been
shipped
with
10
Windows,
Server,
2000,
9
and
18
a
and
1809
the
next
one
implementing
front
rank
on
some
windows.
C
This
one
can
be
a
can
be
used
to
make
it
easier
to
schedule
pots
on
into
appropriate
notes
based
on
a
they
always
a
version
of
they
always
NCP.
A
CPU
are
a
separate,
a
CPU
architecture
and
any
other
information
that
you
have
you
have
around
with
hyper-v
available
windows
can
run
containers
or
a
control
containers
may
on
multiple
windows
or
a
multiple
windows,
operating
system
versions
and
Linux
containers
might
be
a
my
might
be
able
to
do
this
in
the
future
as
well.
C
C
C
This
is
somewhat
similar
to
a
plain
old
container
running
a
runaway
on
linux,
where
you
can
specify.
I
want
this
process
to
run
a
with
some
knots
and
also
the
user
and
this.
Finally,
this
finally
became
stable
on
a
118
and
it's
ready
for
production
use
and
with
that
we
actually,
we
actually
just
cover
all
the
enhancements
that
went
into
118
and
if,
with
that,
let's
take
a
let's
take
it
away.
B
B
And
then
you
can
you
come
on
to
the
release
team
and
you
help
out
and
learn
the
responsibilities
of
that
that's
specific
and
that
that
role
enhancements.
For
example,
the
team
and
I
split
up
all
of
the
enhancements
that
are
tracked
in
the
coup
Brandis
enhancements
repo.
We
would
ping
each
one
to
figure
out
what
was
gonna
happen
in
that
release
and
kind
of
Shepherd
it
through
the
process.
Generally,
the
releases
are
around
three
months,
but
that's
changing
a
little
bit
right
now.
B
The
workload
varies
depending
on
which
team,
which
part
of
the
release
you're
in
so
enhancements,
is
kind
of
front-loaded.
Release,
notes,
Doc's
are
kind
of
back
loaded,
so
you
can
kind
of
gauge.
You
know
where
your
interest
is
and
what's
time
commitment
might
look
like,
but
we
definitely
recommend
that
you,
if
you're
interested
in
this
at
all,
apply
to
be
a
shadow
for
the
next
release,
which
would
be
120.
We've
already
formed
the
119
team,
but
you
know
at
the
end
of
each
release.
B
C
If
you're
interested
about
a
on
learning
more
about
the
way
it
the
release,
team
or
the
kubernetes
community
in
general,
if
the
release
team,
like
any
other
sub
project
or
sick,
a
within
the
kubernetes
community,
has
all
the
meetings
a
completely
open.
So
if
you
can,
you
can
change,
you
can
join
in.
You
can
ask
questions
and
like
and
with
that
I
guess.
We
now
open
the
ground
for
actual
questions
about
the
webinar
and
one
eighth
inning
yeah.
A
C
This
is
this
is
for
distro
list
containers
come
a
come
into
play.
If
you
google,
destroy
these
containers,
you
will
probably
come
across
a
repository
owned
by
Google.
I
will
I
will
leave,
and
that
is
the
district's
containers.
Essentially
just
give
you
enough
of
an
operating
system
and,
for
example,
they
they
give
you
the
basic
CA
certificates
and
enough
tools
to
just
be
able
to
run
by
a
binary.
They
don't
they
don't
have
a
they
don't
have
a
shell,
they
don't
they
don't
provide
the
opportunity
it.
C
C
You
cannot
to
apt-get
install
blah
blah
blah
and,
if
you're,
using
a
if
you're,
reducing
those
destroy
race
images,
you
are
morally
secure
in
your
application,
because
now
you
can
do
have
an
additional
a
barrier
that
is
going
to
ensure
that
only
your
application
is
running
and
that
no
one
can
exit
into
the
container
and
install
something
else
and
no
way
that
no
one
can
inject
and
he
can
any
kind
of
traffic
into
that
and
that
that
is
there.
That
is
a
good
practice
to
follow.
C
If
you
worry,
if
you
actually
want
to
debug
your
application,
while
using
a
distro,
that's
container
Drupal
I
have
to
go
back
to
your
to
your
container
image,
a
docker
file,
for
example,
you
will
have
to
change
from
GCR,
destroy
this
to
from
:
1:13.
That
will
actually
give
you
a
a
devil
like
operating
system.
Then
you
have
to
build
your
image
again.
You
have
to
push
in.
You
have
to
wait.
You
have
to
wait
for
things
to
redeploy.
C
A
cube
code
of
the
book
is
essentially
a
shortcut
to
do
all
that
work
and
we
keep
color
of
the
bombs.
You
can
just
say,
cube.
Kernel
I
had
this
pot
I
want
to
run
debian
container
inside
of
it
and
as
soon
as
I
get
back
containing
the
same
in
the
same
milk
network,
hostname
namespaces
then
I
can
actually
then
I
can
now
is
a
install
of
a
and
it's
also
them
wanting.
I
essentially
have
your
kubernetes
cluster
serve
as
a
local
machine,
and
it's.
B
A
B
B
Have
a
lot
of
the
detailed
information
at
hand?
I
would
have
to
go,
read
the
caps
themselves.
It's
try
to
you
know
to
answer
any
specific
question
for
you.
How
do
those
things,
but
again
the
caps
are
like
the
source
of
truth.
So
anytime,
a
change
is
gonna
be
made
to
kubernetes.
It
has
to
go
through
this
enhancement
process
and
that's
called
the
kubernetes
enhancement
process
and
all
of
those
things
live
in
karate,
slash
enhancements
on
github,
so
github.com
slash,
kubernetes,
slash
enhancements.
B
You
can
find
all
the
things
that
have
been
previously
implemented,
things
that
are
proposed
and
are
being
iterated
on,
like
sidecar
containers.
As
an
example,
you
can
find
all
the
things
that
have
gone
into
previous
releases
there
as
well.
When
those
things
are
merged
and
approved,
they
end
up
in
a
caps
directory,
so
in
github
you
can
find
in
the
enhancements
repo.
You
can
find
all
of
the
caps
that
have
been
merged
previously
and
we'll
give
you
more
info.
B
A
Okay,
thank
you
and
Jeremy
and
George
thanks
for
a
great
presentation.
That's
all
the
time
we
have
questions
for
today.
Thank
thank
you.
Everyone
for
joining
us,
the
webinar,
recording
and
slides,
will
be
online
later
today
and
we
look
forward
to
seeing
everyone
at
a
future.
Cn
CF
webinar
have
a
great
day.
Thank.