►
From YouTube: Kubernetes SIG Node 20220201
Description
Meeting Agenda:
https://docs.google.com/document/d/1j3vrG6BgE0hUDs2e-1ZUegKN4W4Adb1B6oJ6j-4kyPU
A
Hello,
hello,
it's
first
of
february,
2022.
time
flies.
We
already
passed
one
month
of
2022
and
a
lot
of
things
happening.
I
want
to
start
with
formal
buster.
If
you
missed
something,
you
didn't
miss
a
lot.
We
didn't
create
too
many
pr's,
but
we
grow
in
appearance
numbers
because
I
think
most
of
our
effort
right
now
is
on
caps,
which
leads
me
to
the
next
announcement
that
carefree
says
on
thursday.
A
If
you
have,
if
you
want
to
approve
your
cap
for
this
release,
you
need
to
rush
in
today.
I
think
today
is
already
kind
of
late.
I
mean
if
you
didn't
make
a
announcement
long
time
ago.
So
yeah,
please
be
mindful
of
the
timeline.
B
Yes,
sir,
I
would
say
anything:
that's
not
already
on
the
spreadsheet
and
under
consideration
like
we're
not
going
to
look
at
last
minute
caps
at
this
point,
because
it's
beyond
the
soft
deadline
for
prr-
and
I
know
the
prr
team-
is
having
some
staffing
issues
due
to
illness
and
we've
got
lots
of
stuff
left.
So
thanks
to
everybody
who
got
all
of
that
stuff
done
on
time-
and
I
know
I've
got
a
list
that
I'm
still
working
through,
but
hopefully
everybody's
kept
will
get
looked
at
before
the
deadline.
A
Thank
you,
lana
renee.
Do
you
want
us
to
talk
about
status
of
in-place,
both
vertical
scanning.
C
Oh
yeah
hi,
so
there
is
no
nothing
further
to
update.
I
I'm
still
waiting
for
direct
to
finish
his
review.
He
mentioned
last
week
that
he
is
halfway
through
and
I
don't
think
he's
got
the
chance
to
finish
it
up.
C
So
after
that
review
I'll,
look
at
fixing
any
major
issues
that
he
has
and
get
it
to
a
state
where
it's
good
enough
and
we'll
I'll
be
creating.
I
think,
at
the
end
of
february
I
should
be
done
with
my
day.
Job
work
release
as
well,
so
I'll
get
some
more
time
after
that,
but
I'll
create
issues
and
then
seek
help
for
them.
I
know
a
couple
of
folks
have
already
offered
to
help.
C
The
goal
is
to
try
and
fix
most
of
the
issues
that
are
outstanding
from
the
courtroom.
I
think
there
were
nine
or
ten
want
to
fix
as
many
of
them
as
possible
in
this
release,
and
then
the
rest
can
come
in
during
the
beta.
C
That's
all
great.
Thank
you
for
update
one
more
thing.
Last
week
I
was
in
the
scheduler
scheduling
site.
I
don't
think
api
has
changed
that
much
at
all,
except
for
some
of
the
unit
test.
Fixes
that
came
came
through
to
the
review.
Scheduler
looks
good.
They
there
is
one
issue
for
performance
there.
I
think
they've
offered
to
help
on
that.
So
from
scheduling
and
api
perspective,
we
should
be
good
to
check
this
in.
A
Thank
you,
jeep.
Don't
talk.
D
Hello
yeah,
so
this
is
the
gap
around
new
conditions
for
pod
sandbox
creation,
thanks
alana
for
taking
the
first
look.
There
were
some
comments
around
how
this
might
work
with
with
the
new
cap
around
tracing,
so
I've
addressed
and
clarified
some
of
the
usage
scenarios
where
you
know
having
this
might
be
helpful
and
might
provide
some
more
contextual
data,
but
tracing,
and
this
can
definitely
be
complementary,
yeah
other
than
that.
D
Just
pretty
much
waiting
for
like
overall
node
review
to
take
place
and
really
hoping
to
get
this
in
for
1.24,
if
possible,.
A
Okay,
I
just
opened
this
cap
for
everybody
to
be
to
have
a
chance
to
read
a
summary
if
you're
interested
to
take
a
look,
please
do
thanks.
That's.
D
D
E
A
A
So
yeah
for
everybody
on
the
call
not
familiar.
This
is
a
a
checkpoint
ability
on
the
couplet,
so
we
will
be
able
to
take
checkpoints
of
our
containers.
A
Okay,
yeah:
I
wanted
to
bring
up
this
cry
versioning
again
I
shared
document
last
week
and
sasha
commented.
I
think
I
addressed
all
the
comments
now
after
this
document,
like
after
creation
of
this
document,
I
think
my
next
steps
will
be
to
convert
this
document
into
specific
requirements.
What
you
want
to
get
for
sierra
api-
and
I
wanted
to
just
highlight
this-
a
couple
of
things
that
may
be
interesting.
A
First,
is
this
cri
tools,
pr
that
was
merged
recently?
This
is
like
switched
criteros
to
v1
api
and
it's
not
gonna
work
for
container
g
1.5.
It
only
works
for
category
1.6,
so
we
need
to
declare
what
cri
tools
backward
compatibility
is
supposed
to
be
and
how
many
versions
back
should
the
support
of
various
runtimes,
and
this,
let
me
think
enough,
like
how
did
we
announce
this
switch
to
v1
api,
because
we
did
a
good
job
announcing
like
there
are
things
like
this
stargaze
snapshotter
that
implements
a
proxy
on
sierra
api?
A
That
also
relies
on
the
v1
alpha
2
right
now,
and
it
didn't,
I
I'm
not
sure
whether
they
even
know
about
they
need
to
switch
to
v1.
At
some
point,
so
we
may
need
to
based
on
this
document
to
declare
what
the
backward
principality
story
will
be
and
how
long
will
support
different
versions
of
sierra
api,
so
yeah.
If
you
have
a
want
to
comment
on
that,
please
do,
and
I
will
keep
working
on
that
to
make
sure
that
you
move
into
the.
A
A
It's
extremely
short
signal
meeting
today.
Thank
you,
everybody
for
attention.
Let's
get
back
to
our
prs
and
caps,
so
we
have
extra
15
minutes
to
do
that.
Thank
you.
Bye
thanks.