►
From YouTube: Kubernetes 1.28 Release
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everyone,
thanks
for
joining
us
today,
welcome
to
today's
cncf
live
webinar,
kubernetes
1.28,
release,
I'm
Libby,
Schultz
and
I'll
be
moderating
the
webinar
today
I'm
going
to
read
our
code
of
conduct
and
then
hand
over
to
Grace
Wen
release
team
lead
and
atarva
shinde
enhancements
team
lead
from
the
kubernetes
1.28
release
team.
A
A
few
housekeeping
items
before
we
get
started
during
the
webinar
you're,
not
able
to
speak
as
an
attendee,
but
we
welcome
and
encourage
you
to
drop
all
your
questions
into
the
chat
box
on
the
right
hand,
side
of
your
screen
and
we
will
get
to
as
many
as
we
can
at
the
end.
This
is
an
official
webinar
of
the
cncf
and,
as
such
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.
A
Please
be
respectful
of
all
your
fellow
participants
and
presenters.
Please
also
note
that
the
recording
and
slides
will
be
posted
later
today
to
the
cncf
online
programs,
page
at
Kim
community.cncf.io
under
online
programs.
They
will
be
available
via
your
registration
link.
You
use
to
join
today
and
the
recording
will
be
on
our
online
programs.
Youtube
playlist.
B
Thank
you,
Libby
hi,
everyone,
my
name
is
Grace
and
I.
Was
the
release
team
lead
for
the
1.28
release
and
if
a
turtle
would
say,
go
to
the
next
slice
and
introduce
himself.
C
Hello,
my
name
is
I'm
from
India
I'm,
the
version
1.28
announcements
lead
and
the
there's
one
another
folk
with
her
who
is
not
able
to
join
us
today,
but
he
is
Brad
who
was
the
kubernetes
1.26
coms
lead
for
the
release
team,
1.28
complete
for
the
release
team
so
yeah.
This
was
the
basic
introduction
about
us
Grace
over
to
you.
B
Yeah,
so
this
release
is
made
up
of
a
lot
of
folks,
so
these
are
the
people
that
contributed
to
the
1.28
release,
many
of
whom
has
now
gone
on
to
work
on
the
1.29
release,
which
started
on
Monday,
so
a
huge
shout
out
to
them
and
all
the
work
that
they
put
into
this,
so
that
we
can
have
a
new
release.
B
The
theme
for
this
release
is
plantronettes
because
it
is
summer
here
where
I
am
in
the
Northern,
Hemisphere
and
I
thought.
A
garden
was
a
really
good
symbol
for
our
open
source
ecosystem.
The
fact
that
we
all
have
a
very
unique
backgrounds
and
roles,
but
each
of
us
is
really
critical
to
the
ecosystem.
C
C
I'll
talk
about
the
kubernetes
kubernetes,
so
kubernetes
has
a
process
for
those
that
for
the
features
that
may
be
maybe
major
themes
or
that
may
be
user
facing.
So
these
these
enhancements
go
through
a
process,
a
release
tracking
process
and
they
go.
C
For
the
announcement
they
are
planning
to
propose
around
five
evaluated
to
version
1.28,
among
which
these
announcements
that
have
started
with
Stage
Alpha
nines
announcements
that
moved
to
Stage
beta
are
14
and
around
12
announcements
have
graduated
to
Stage
table.
C
B
Yeah
now
yeah,
especially,
we
won't
be
able
to
go
through
each
of
the
enhancements,
because
that
will
take
a
bit
of
time
but
to
Tara
and
I
will
go
through
some
major
themes
that
we
think
you
should
know
about.
So
first
off
we
have
changes
to
supported
skew
between
control,
plane
and
note
version.
So
upgrading
to
new
version
is
a
pain
Point
amongst
folks
in
the
community,
and
hopefully
this
will
make
it
easier.
B
They
can
be
three
apart
instead
of
two
a
partner,
and
this
will
hopefully
support
for
you
to
upgrade
your
control
plane
and
then
your
node
easier.
This
enhancement
is
now
unstable
and
you
can
go
to
the
link
here
to
read
more
about
it
and
it's
also
on
our
blogs.
B
Next
up,
we
have
a
recovery
from
non-graceful,
no
shutdown.
So
this
is
the
in
the
event
of
a
broken
Os
or
broken
heart
wears
situation
where
the
shutdown
is
unexpected
and
hard
to
detect
by
the
cubelet.
This
enhancement
will
support
the
stateful
set
spots
to
be
recovered,
so
I,
think
of
it.
As
you
know,
the
pots
that
are
stuck
in
the
node
that
is
being
shut
down
will
get
air
lifted
yeah,
and
then
we
have.
This
feature
is
currently
in
beta
improvements
to
custom
resource
definition.
B
Validation
rules,
that's
a
mouthful,
but
this
is
one
of
the
enhancements
that
incorporate
the
common
expression
language,
which
is
one
of
the
ways
that
you
can
declare
rules
for
your
custom
resource
definitions
now
and
to
use
that
you
have
two
optional
field:
reason
and
field
path
for
you
to
specify.
B
Next
up
another
one
that
is
also
related
to
the
cell
or
common
expression.
Language
is
now
you
can
use
cell
to
enforce
customizable
policies
within
your
yaml,
and
in
order
to
do
this,
you
need
to
enable
the
two
things
that
we
outline
there.
This
feature
is
also
in
beta.
C
So
the
amazing
thing
about
version
1.28
among
the
very
other
new
announcement
is
we
we
officially
now
have
sidecar
containers
available.
C
So
the
way
you
can
use
the
sidecar
contest,
the
init
containers
are
used
as
a
side
card
container,
and
you
can
enable
this
sidecar
container
by
mentioning
the
restart
policy
field
in
your
init
container
specification.
And
if
you,
if
you
omit
the
restart
policy
specification
field
from
the
in
from
your
init
container
specification.
That
means
you
just
want
your
pure
container
to
try
this
feature.
Will
this
container
circuit
available
waiting
on
to
another
new
announcements
that
we've
got
the
status
of
the
the
mix
proxy
version?
C
So
let's
say
you
have
a
multiple
containers
in
your
clusters
and
you're
trying
to
access
a
resource
of
often
a
from
an
API
server
which
isn't
supported
by
your
API
server,
because
there
are
a
lot
of
lot
of
API
version
API
service
with
multiple
versions.
So
how
to
deal
with
this?
So
there's
a
there's,
an
announcements
called
mixed
virgin
proxy.
C
So
through
this
you,
the
announcement
is
to
one
of
the
abras
inside
your
clusters,
which
can
satisfy
request
that
you
are
trying
to
access
the
resource
to
so
you
can
enable
this
announcement
with
the
unknown
version.
Interoperability
proxy
feature
get
the
next
announcement
we
have
is
support
for
the
and
support
for
enabling
swaps
this
on
Linux,
so
announcement
was
introduced
in
1.22,
but
it
it
has
graduated
to
in
1.28,
so
it
this
one,
the
swap
support
was
actually
not
labeled
in
kubernetes,
but
from
1.2
to
1.22
it
was.
C
It
was
made
available,
but
stay
for
one
point
to
it
as
it
has
graduated
to
Stage
beta.
It
is
now
become
more
reliable
and
it
is
now
more
controllable
on
how
you
can
swap
how
you
can
enable
the
swap
support
on
your
assisting.
So
now
you
now
it
is
possible
to
also
monitor
what
what
what's
happening
inside
this
swap
inside
your
swap
usage.
C
This
effort
is
being
made
to
enable
the
end
users
or
the
kubernetes
API
users
to
get
all
the
necessary
functions
into
one
staging
repository,
and
it's
it's
it's
it's
now
paying
a
turn
in
a
more
gradual
kind
of
way.
It
is
not.
The
summary
of
this
announcement
is
that
the
initiative
has
now
stopped.
C
The
another
feature
that
we
have
for
1.28
books.
This
is
now
adjected
to
Stage
Beta
Support.
This
announcement
is
it
lets
you
Define
conditions
for
your
web
hooks
for
when
the
kubernetes
should
make
the
HTTP
call
for
admission
for
while
the
admission
process,
so
this
at
this
match
condition
should
be
totally
satisfied
in
order
to
make
the
call
to
the
web.
C
You
want
to
request
to
and
currently
the
match
conditions
match,
conditions
are
in
the
form
of
common
Express,
common
expressive
language
and
you,
you
can
have
up
to
64
match
conditions
for
a
single
web
hook,
and
it
is,
as
it
has
graduated
to
Beta
match
conditions
field
is
now
enabled
by
default.
B
Yeah,
thank
you.
Another
stable
features
that
we
shipped
is
automatic
retroactive
assignment
of
default
storage
class.
So
in
the
past
you
need
to
create
a
default
storage
cost
first
and
then
assign
a
PVC
to
the
class.
B
Now
the
control
planes
will
set
a
storage
class
for
any
existing
PVC
that
doesn't
have
the
storage
class
name
defined.
So
that
way
the
PVC
is
no
longer
stuck
in
an
Unbound
stage.
B
B
So
what
this
means
is
we
are
offering
an
additional
and
more
flexible
pot
replacement
policy
for
jobs
that
allows
the
part
to
be
started
only
when
it's
fully
terminated.
That's
an
optional
Behavior,
instead
of
when
the
termination
process
start-
and
this
is
specifically
applicable
for
folks
who
are
running
machine
learning,
workloads
asked
this
will
prevent
clashing
between
the
pause
and
also
help.
B
You
manage
the
resources
within
your
notes
and
then
last
but
not
least,
this
is
not
a
major
theme,
but
it's
part
of
the
release,
and
rather
a
large
one.
B
B
B
This
will
only
affect
user
who
directly
install
uptrend
versions
of
kubernetes.
If
you
use
fully
managed
kubernetes
through
a
cloud
providers,
you
likely
won't
be
effective.
B
This
might
affect
you
also
if
you
run
Linux
on
your
own
PC
and
installed
cubectl
using
the
Legacy
package
Repository.
The
latest
blog
on
kubernetes.io
block
is
about
this.
So
if
you're
curious,
if
you're
affected
or
not,
you
can
explore
more
there,
but
that
is
it
for
our
major
theme.
C
I,
just
information
for
all
the
folks
around
here
to
get
a
more
detailed
view
on
each
and
every
announcement
you
can
follow
the
kubernetes
1.28
block
that
has
been
posted
on
the
kubernetes.io
website,
so
yeah
go,
give
it
a
give
it
a
rate.
So
it's
amazing
yeah.
B
I
will
drop
it
in
the
chat
there.
We
go.
Yeah
I
wanted
to
talk
a
little
bit
about
our
release,
Team
Shadow
program-
that
is
how
Brad
and
I
and
atarba
begin
our
journey
on
the
release
team.
B
B
Each
release
is
about
four
months
and
we're
very
beginner
friendly.
No
experience
required
when
I
got
started.
I
was
in
first
year
university
and
didn't
have
any
open
source
experience
and
it's
been
an
amazing
journey.
So
far,.
C
I
just
want
to
Echo
this
that
there's
no
technical
requirement
as
such
a
lot
of
folks
start
to
ask
that
what
skills
do
you
need
what
technical
skills
are
asked
in
order
to
apply
for
these
shadow
rules?
There's
no
such
technical
requirement
that
is
needed.
You
just
have
to
you.
Just
have
to
be
good
at
communications
and
be
a
team
player.
That's
all
and
you're
just
good
to
go
so
yeah
don't
apply
for
the
version.
1.30
kubernetes
release
and
yeah.
B
Someone
in
the
chat
asked
they
missed
how
to
join
the
shadow
role
as
their
in
the
URL
for
signing
up.
Unfortunately,
it
was
due
last
Friday
and
the
application
is
closed
already,
but
the
next
cycle
application
will
open
in
December.
So
keep
your
eyes
out.
Then.
If
you
want
to
sign
up
for
updates,
you
can
sign
up
for
sick
release,
mailing
list
or
join
the
Sig
release
channel
on
Slack.
B
And
upcoming
events,
we
have
kubecon
n
a
in
November
in
Chicago
if
you're
a
contributor,
there's
also
the
contributor
Summit
that
I
love
to
attend
and
you
will
get
to
see
sick
release
folks
there
if
you
have
any
other
questions
but
beside
that.
That
is
the
end
of
our
webinar.
B
A
B
A
Us
have
if
anyone
has
any
questions
or
wants
to
follow
up,
will
Grace
and
atarba
put
your
Handles
in
the
chat
and
that
way
anybody
can
follow
up
with
y'all
just
in
case,
and
otherwise
we
will
have
this
recording
up
in
probably
the
next
hour
or
so
fantastic
awesome.
A
Attending
and
thank
you
everybody
for
joining
us
and
we
will
see
you
next
time
thanks,
Grayson
natarva,
bye.