►
From YouTube: Kubernetes v1.27 Release
Description
Don't miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from 18 - 21 April, 2023. 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.
A
A
Thanks
everyone
for
joining
us
today
welcome
to
a
special
edition
of
cncf's
live
webinar,
kubernetes
version,
1.27
release,
I'm
Libby,
Schultz
and
I'll,
be
moderating
today's
webinar
I'm
going
to
read
our
code
of
conduct
and
then
hand
over
to
Xander
dravinsky
and
Mark
Rossetti,
both
from
the
kubernetes
version.
1.27
released
a
few
housekeeping
items
before
we
get
started
during
the
webinar
you're,
not
able
to
speak
as
an
attendee,
but
you
can
definitely
pop
questions
and
comments
into
the
chat
feel
free
to
do
so
and
we'll
get
to
as
many
as
we
can
at
the
end.
A
This
is
an
official
webinar
of
the
CNC
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct
and
please
be
respectful
of
all
of
your
fellow
participants
and
presenters.
Please
also
note
that
the
recording
and
slides
will
be
posted
later
today
for
the
cncf
online
programs,
page
at
community.cncf.io
under
online
programs.
They're
also
available
via
your
registration
link,
used
to
join
today
and
will
be
on
our
online
programs.
C
Want
to
start
Xander
yeah
yeah,
so
thank
you
for
joining
us.
Everyone.
We
are
gonna.
Do
a
just
a
little
bit
of
an
overview
of
some
of
the
top
level
features
that
are
part
of
the
kubernetes
1.27
release
release
day
was
Tuesday
the
11th.
So
it's
been
out
there
a
few
days
now,
I
want
to
go
to
the
next
slide.
C
Yeah
quick,
intro,
I'm,
I'm,
Xander
I,
am
the
1.27
release.
Lead
I
have
been
on
the
release.
Team
120
was
my
first
version
and
I've
been
on
every
every
version.
Since
then
I've
LED,
enhancements
and
and
worked
on
the
comms
team
as
well
yeah.
It's
been
been
about
three
years
on
the
team
yeah.
B
And
I'm
Mark
Rossetti
I've
been
contributing
to
kubernetes
since
early
2019
and
I've
been
at
part
of
the
release
team.
Since
the
125
release,
where
I
was
enhancement,
Shadow
twice
and
then
a
handsome
sleep,
this
last
release.
C
All
right,
I'm
gonna
do
this,
like
you
know
one
of
the
the
old
movies
where
they
do
the
credits
first
and
and
just
throw
out
a
big
thank
you
to
the
entire
release
team.
You
know
it's
just
two
of
us
here
right
now,
but
you
can
see
that,
like
the
the
whole
team
is
actually
a
huge
group
of
people
that
all
contribute
a
lot
of
work
to
making
this
happen
and
got
it
broken
down
by
roll
here.
C
You
know:
we've
got
folks
across
enhancements,
CI
signal
release,
notes,
Communications,
bug,
triage
and
docs,
and
on
this
slide,
I
have
the
the
names
of
the
the
leads
bolded
yeah,
really
just
to
kind
of
illustrate
that
it.
It
really
is
a
huge
group
effort
to
make
this
happen.
So
big,
big,
thank
you
to
everyone
that
participated.
C
And
then
I
want
to
talk
a
little
bit
about
the
theme
to
some
of
you.
If
you
read
the
release,
blog
may
have
seen
this.
Every
release
has
a
theme.
This
one
is
Chill
Vibes
and
got
our
our
sloth
logo
here,
created
by
Brittany,
labrick,
and
and
thank
you
so
much
to
her
for
for
doing
that.
For
us,
it's
I
really
love
it.
C
C
That
features
need
to
meet,
and
this
was
the
first
time
that,
like
at
least
for
the
first
Milestone,
which
is
enhancements,
freeze
every
single
feature
we
didn't
have
to
deal
with
any
exception
requests
and
the
the
release,
as
it
continued
like
really
just
stayed
pretty
calm
and
and
chill
throughout
the
whole
time,
which
is
just
an
unusual
thing
compared
to
previous
releases,
and
it
really
ended
up
being
because
there's
been
a
ton
of
work
going
on
behind
the
scenes
to
kind
of
tighten
the
process
and
and
make
things
more
smooth
and
so
I
think
this
was
probably
the
first
release
that
we
really
got
to
feel
the
benefit
of
all
the
work.
B
Oh
sure,
yeah
I
can
speak
to
this
So
for
anybody
who's
not
really
familiar
with
how
the
enhancements
process
work
in
kubernetes.
B
Most
major
changes,
especially
user-facing
changes
in
kubernetes,
are
required
to
go
through
an
enhancement
process
and
as
part
of
the
enhancement
process,
there's
a
kubernetes
enhancement
proposal
that
gets
written
up
and
reviewed
by
stakeholders
and
that
kind
of
outlines
the
work
and
how
it's
going
to
be
tested
for
stability
and
production,
Readiness
and
all
of
that
sorts.
B
So
this
release
in
the
127
release
there
were
60
enhancements
that
graduated
or
moved
from
one
phase
to
a
next,
which
is
kind
of
a
very
large
amount,
which
is
even
more
surprising
that
it
was
such
a
chill
of
release
for
reference.
The
last
release:
126
there
was
only
39
enhancements
that
progressed
or
graduated.
B
So
here's
a
little
bit
of
a
breakdown,
there's
18
new
enhancements
that
went
to
Alpha
29
new
enhancements
I
went
to
Beta
And
beta
is
a
big
milestone
because
that's
when
enhancements
are
the
functionality
behind
those
enhancements
is
usually
on
by
default
and
is
available
for
a
lot
of
users
to
use
and
then
there's
another
13
that
went
to
stable,
there's.
Also
a
number
of
deprecations
and
removals
I'm
not
really
going
to
go
over
those
they're
all
outlined
in
a
blog
link.
That's
linked
below
do.
C
B
C
All
right
so
this
time
around
we're
gonna,
do
things
just
a
little
bit
differently
than
this.
Webinar
has
been
done
in
the
past.
You
know,
usually
when
we've
done
the
the
release,
webinar
kind
of
gone
through
every
enhancement
that
made
it
into
the
release
and
and
done
just
like
a
little
one
sentence.
Blurb
as
Mark
mentioned,
this
is
a
huge
release
with
a
lot
of
enhancements
that
made
it
in
so
we've
kind
of
pivoted.
C
The
format
of
this
to
just
focus
on
the
major
themes
of
the
release
that
are
outlined
in
the
release,
blog
and
yeah
I.
Think
for
that
kind
of
full
breakdown.
You
can
see
the
the
release
notes
yep,
so
we're
gonna
start
with
mentioning.
Yet
again
the
registry
change
I
know:
we've
been
talking
a
lot
about
this
throughout
the
whole
release
cycle
and
I'm.
Sure
some
folks
are
tired
of
hearing
about
it,
but
it
really
Bears
mentioning
again
the
image.
C
It's
really
about
balancing
the
Ingress
egress
load
for
these
images
across
providers,
and
it's
it's
going
to
provide
just
a
better
experience
for
everybody,
so
the
127
images
are
not
going
to
be
published
to
the
old
registry
right
now.
Request
of
the
old
registry
will
redirect
to
the
new
one,
but
if
you're
behind
like
a
proxy
or
something
there
is
some
some
work
that
may
need
to
be
done
to
make
things
function
as
expected.
C
So
this
is
mentioned
in
detail
in
the
deprecations
blog,
which
you
can
find
on
the
kubernetes
blog
but
yeah.
We
wanted
to
start
with
this
one,
because
it
is
an
important
thing
that
that
may
require
some
changes
depending
on
your
environment,
yep.
B
All
right,
so,
the
next
enhancement
that
we
wanted
to
highlight
was
the
SEC
comp
defaults
have
graduated
to
stable.
This
is
so,
if
you're
one
once
this
is
enabled
it
basically
defers
the
second
profiles
to
your
the
container
runtime,
and
so
that
just
allows
more
flexibility
and
configuration
in
order
to
enable
this.
B
That
does
require
a
cubelet
flag
to
be
passed
and
just
Please
be
aware
that
you
know
the
set
comp
profiles
for
your
container
runtime
will
differ
depending
on
your
container
runtime
and
also
can
vary
depending
on
releases
of
that,
and
infrastructure
providers
can
also
modify
those
too.
C
All
right
and
the
next
one
we
have
a
mutable
scheduling
directives
for
jobs,
so
this
is
going
to
stable
and
really
the
the
gist
of
this
is
kind
of
that
bottom
section
there.
So
the
those
fields
like
node,
Affinity,
node,
selectors,
Toleration,
scheduling,
Gates
annotations
and
labels
can
now
be
updated
before
a
job
becomes
unsuspended.
B
And
here's
another
one
that's
graduating
to
stable.
This
is
a
downward
API
support
for
huge
Pages.
So
now,
if
you're,
you
can
kind
of
let
the
workloads
know
how
much
what
the
limits
and
requests
are
for
the
huge
pages
of
the
different
sizes
and
quantities.
B
C
All
right
and
then
we've
got
pod
scheduling,
Readiness
graduating
to
Beta.
This
is
a
pretty
cool
one
actually
being
able
to
add
the
Readiness
gates
to
to
pods
before
they
scheduled.
So
if
you've
got
you
know,
labels
or
annotations
or
any
kind
of
mutations
that
need
to
be
applied
to
a
pod.
C
You
can
set
a
gate
on
the
Pod
to
do
that,
work
before
scheduling
so
that
you
don't
have
to
deal
with
the
churn
of
the
scheduler
and
and
have
those
pods
in
in
their
fully
mutated
State
before
they
make
it
to
that
stage.
I
think
yeah
I
think
this
one
will
be
useful
to
a
lot
of
people.
Yeah.
B
B
This
node
log
access
through
kubernetes
apis.
So
previously
you
could
stream
some
files
from
the
the
cubelet
under
like
the
log
files
to
the
keyboard,
but
this
enhancement
kind
of
adds
apis
to
do
more
deep
introspection
of
your
system,
kind
of
in
a
kubernetes
native
way,
so
on
on
Linux
you'll,
be
able
to
query
Journal
D
and
see
like
system
events
and
everything
through
this
and
on
Windows
you'll
be
able
to
query
events
into
the
Windows
application.
B
Logs
to
this
too,
this
is
just
going
in
Alpha,
so
it
will
need
to
be
enabled
and
there's
a
little
bit
of
information
on
how
to
enable
that,
for
anybody,
who's
interested
in
taking
advantage
of
that
here.
C
All
right
and
then
we've
got
the
read,
write
once
pod
persistent
volume
access
mode
going
to
Beta.
C
B
All
right,
here's
some
improvements
to
how
pod
topology
spread
is
calculated,
After,
Rolling
updates,
so
new
in
I
think
going
to
yeah
new
going
to
Beta.
There's
this
new
field
called
match
label
keys
where
you
can
specify
labels.
B
The
names
of
labels
in
this
match
labels
keys
and
then
the
the
scheduler,
when
it's
going
through
rolling
updates
of
deployments,
will
look
at
the
values
in
those
scheduling
keys
in
addition
to
the
label
selectors
that
you've
selected
and
make
decisions
with
this,
and
this
is
to
help
like
one
of
the
big
use.
B
Cases
is
highlighted
here,
and
this
is
that
you
can
use
this
pod
template
hash,
which
will
help
the
scheduler
distinguish
between
revisions
within
the
deployments
of
your
workloads
and
help
them
get
kind
of
spread
across
whatever
your
Pi
typology
spread
defines.
C
All
right,
faster,
SC,
Linux
volume,
re-labeling
I,
can't
really
pretend
to
know
much
about
SE
Linux,
but
it
does
speed
up
container
startup
time
by
mounting
volumes
with
the
correct
label
yeah
and
then
the
SE
Linux
Mount
field
being
added
to
the
CSI
driver
objects
too.
B
B
These
amounts
of
volume
it
does
so
without
setting
the
SC
Label
permissions
or
contexts
on
the
drive.
So
then
something
will
go
and
recursively
kind
of
update
permissions
on
all
the
files,
and
this
is
mechanisms
to
skip
all
of
that.
So
let's
discuss
and
better
performance.
B
Of
in
a
similar
vein,
this
robust
volume
manager
reconstruction
feature
has
graduated
to
Beta.
So
now
the
this
is
the
volume
management
code
within
the
cubelet
has
kind
of
been
refactored
to
keep
retain
more
State
about
what
volumes
are
already
mounted
on
the
Node.
So
just
this
will
help
make
the
node
resets
and
everything
more
stable
and
reliable,
and
also
just
better
stability
with
respect
to
volume
mounts.
C
C
So
before
a
pod
is
scheduled,
you'd
be
able
to
mutate
the
the
direct
install,
giving
the
ability
for
external
resource
controllers
to
influence
that
placement,
while
still
kind
of
offloading
the
scheduling
work
to
the
scheduler
itself.
So
it
kind
of
allows
building
lighter
touch,
scheduler
directions
without
having
to
implement
a
full
scheduler
plug-in
foreign.
B
And
this
one
is
one
that
I
think
a
lot
of
people
have
been
waiting
for.
B
The
list
this
one's
been
in
the
works
for
quite
a
while.
This
is
the
In-Place
update
of
pod
resources.
So,
with
this
functionality
containers
you
can
add
and
subtract
resources
to
containers
that
are
running
without
needing
to
restart
them.
So
this
is
I.
Think
of
this
is
in
place
vertical
pod
Auto
scaling,
whereas
the
normal
vertical
pod,
Auto
scaler,
would
reschedule
pods
with
different
resource
requests
here,
we'll
just
update
them
in
place,
so
this
will
definitely
help
a
lot
of
workloads
scale
faster
and
with
fewer
interruptions
between
and
yeah
I.
C
Know
people
are
really
excited
button,
so
yeah
make
sure
to
enable
that
flag
and
and
and
give
it
a
shot.
B
And
I
think
also
read
the
docs
for
this.
This
does
require
specific
versions
of
a
lot
of
container
runtimes
in
conjunction
with
this
function,
this
feature
being
enabled
in
the
cubelete.
C
All
right
we're
going
to
talk
a
little
bit
too.
It's
an
opportunity
to
participate
in
the
release,
team
and
and
get
involved
in
the
kubernetes
project.
C
So
there's
a
little
bit
of
a
breakdown
here
of
of
how
this
works.
I
mentioned
this
before,
but
there
are
various
sub
teams
that
are
part
of
the
release
team
and
as
part
of
each
release
cycle.
Each
of
these
teams
takes
like
roughly
four
Shadows
that
participate
as
part
of
the
team
and
and
learn
from
the
lead
on
on
how
kubernetes
is
released.
C
I,
don't
believe
we
have
the
dates
lined
up
for
the
next
release
cycle
yet,
but
the
application
is
currently
open
for
for
those
that
would
like
to
Shadow
and
participate
in
128,
and
you
can
see
the
the
link
right
down
at
the
bottom
there
and
if
you
go
to
the
Sig
release
repo
on
GitHub,
there
are
handbooks
and
and
breakdowns
of
each
of
the
roles
and
what
the
shadow
program
looks
like
overall.
B
And
a
little
bit
more
information
and
that's
just
available,
even
if
you're
not
subscribed
to
look
at
so
highly
recommend
if
you're
interested
to
try
and
get
involved.
C
And
then
we
also
wanted
to
mention
kubecon
next
week.
I
think
a
lot
of
folks
are
probably
aware
of
that.
Yeah
myself
and
Mark
will
both
be
there
as
well
as
some
other
members
of
the
release,
team
and
I
think
we're
all
probably
happy
to
chat
about
the
release
or
the
release
team.
The
shadow
program,
any
of
these
things,
yeah
should
be,
should
be
a
really
exciting
event
and
yeah.
You
can
see
more
details
for
that
and
other
upcoming
events
on
the
cncf
event,
page.
C
And
that's
that's
what
we
have
I
know
this
one
was
a
little
shorter
than
than
previous
webinars,
but,
like
I
said,
we
wanted
to
kind
of
focus
on
the
top
level.
Major
themes
so
really
appreciate
everyone
dropping
in
to
listen
and
yeah
I
hope
you
get
the
chance
to
try
out
127
and
enjoy
some
of
the
new
features.
C
We're
also
if
it
comes
up
always
happy
to
field
questions
in
kubernetes
slack
through
the
the
Sig
release
channel,
would
be
a
good
place
to
to
post
questions.
A
Thanks
for
sharing
this,
this
is
exciting,
stuff
and
I
hope
we
see
most
of
you
live
and
in
person
at
kubecon
next
week
we
will
be
taking
a
pause
from
online
programs
next
week
for
kubecon
and
then
also
the
week
after,
for
everyone
to
recover
and
we'll
be
back
the
first
week
of
May
so
stay
tuned,
and
this
will
be
online
in
just
a
little
bit
this
afternoon
and
thank
you,
Xander
and
Mark,
both
of
you
for
your
time
today
and
thanks
everyone
for
joining
us.