►
From YouTube: Kubernetes SIG Node 20221018
Description
SIG Node weekly meeting. Agenda and notes: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#heading=h.adoto8roitwq
GMT20221018-170414_Recording_1472x1120
A
Hello,
hello,
it's
I,
think
not
weekly
meeting
it's
October,
18
2022.
welcome
everybody.
Today
we
have
this
will
be
a
short
agenda.
Let's
get
started,
we
will
kick
off
with
the
regular
PR
analysis.
We
have
more
PR's
now
213.,
it's
plus
eight
from
last
week
from
a
merged,
mostly
Cherry,
picks
and
small
PRS,
but
we
immersed
external
credential
provider
goes
to
GA.
A
So
if
you
are
using
built-in
credential
provider
Beware,
it
will
be
gone
soon
and
close
box,
mostly
minor
trivial,
edits
nothing
to
fish
out
of
the
closed,
nothing
rotten.
So
at
least
we
don't
let
good
code
rolled
yeah,
that's
a
status!
Please
put
your
effort
into
reviewing.
Prs
I
know
that
cubecon
is
coming
and
some
of
you
may
be
traveling,
so
maybe
it
wouldn't
be
that
active.
A
But
let's
try
and
with
that
I
wanted
to
discuss
next
item
is
next
week
is
kubecon
as
far
as
I
understand,
I
think
that's
right
and
I
suggest
we
cancel
the
meeting
just
in
case
people
traveling,
and
there
may
be
less
participants
on
the
meeting.
Any
objections.
B
That
looks
amazing,
I
can
simulation
objects,
I
can.
A
Thank
you,
I
think
we'll
do
the
same
for
CI
meeting
as
well,
so
talking
about
CI
meet
income
myself
and
Swati
prepares
short
report
on
CI
group
status.
I
think
this
this
report
may
be
something
that
we
need
to
do
regularly,
because
interest
group
May,
get
lost
and
I
wanted
to
make
sure
that
we
track
what's
going
on
and
we
highlight
the
status
so.
D
A
Like
we,
please
give
us
feedback
on
the
report
format
or
any
other
information.
You
may
be
interested
in
I.
A
I
know
what
we're
missing
is
some
kind
of
big
button
saying:
is
it
green,
overall
or
red
overall
I
think
right
now
status
is
green.
Overall,
we
are,
we
are
not
degraded
much
and
we
are
reasonably
good
shape,
but
nevertheless
we'll
walk
through
the
status.
A
So
we
have
a
lot
of
permafailers.
We
have
some
infrastructure
problems
like
this
one,
and
for
this
one
we
even
have
a
PR
that
supposedly
fixing
just
PR
as
in
a
review
for
a
while.
We
have
some
eviction
tests
that
was
failing
for
a
very
long
time
and
many
people
attempted
to
fix
it,
but
still
no
progress,
I
think
it
was
failing
for
almost
a
year
now
we
know
that
functionality
works.
A
We
just
know
that
something
is
not
very
good
with
infrastructure
and
we
don't
have
enough
time
to
get
to
eviction.
Even
if
we
try
to
write
to
the
Discovery
fast
and
some
also
eviction
test
fails
on
cry
about
this
different
eviction.
So
different
tests
different
run
times
have
different
test.
A
Failing
performance
tests
like
something
that
we
want
to
invest
into
going
forward,
we
are
currently
working
on
fixing
it,
but
it's
a
long
process,
try
and
kind
of
like
we
fix
a
bug,
see
how
it
goes
and
some
new
bug
Rises.
So
that's
kind
of
failure.
So
we
experience-
and
we
have
some
very
strangely
failing
tests,
we're
working
on
a
clean
up
this
test.
A
Some
of
them
are
not
needed,
some
of
them
just
needed,
but
we
didn't
pay
attention
for
a
while,
like
sock
test,
for
instance,
soak
me
and
we
run
cubot
over
and
over
again
for
a
very
long
time
and
this
test.
We
made
a
couple
attempts
to
fix
this
test,
but
it
goes
back
to
Red
over
and
over
again
so
yeah,
sometimes
that
we
need
to
pay
attention
to
yeah
and
some
other
tests,
and
we
have
some
flaky
tests
as
well.
Flakiness
is
not
something
we
concentrated
concentrated
too
much.
A
We
did
it
for
release
122
I,
believe
we
fixed
a
lot
of
flakiness
because
we
get
to
Green
all
over
the
board.
So
we've
paid
a
lot
of
attention
of
flakiness
right
now
we
have
Reds,
so
we
pay
more
attention
to
that,
but
you
can
read
and
see
what
kind
of
tests
are
failing
right
now
and
with
that
I
do
you
want
to
take
over.
D
Sure
so
we
have
this
project
board.
This
is
a
CI
project
board,
where
we
keep
track
of
the
tasks
that
have
been
assigned
that
haven't
been
assigned
how
the
progress
is
going
on.
So,
as
you
can
see,
there
are,
there
are
issues
where
we
don't
have
assignees
for
about
a
month
and
sometimes
more
than
a
month.
So
this
is
an
opportunity
for
people
to
pick
up
tasks
and
maybe
join
us
in
the
same
note,
see
I'm
meeting
again
similar
to
that
we
have
the
bug
triage.
D
We
have
a
project
board
very,
very
capture,
all
the
bugs
that
have
been
triaged
to
identify
bugs
that
are
high
priority
bugs
we.
We
made
some
good
progress
in
the
last
month
or
so,
and
we
caught
upon
a
lot
of
bug,
triages
and
we've
again
identified
a
lot
of
bugs
that
don't
have
a
signees
just
to
capture
some
of
the
stats
there.
D
With
regard
to
kind
of
the
progress
made
in
the
last
month,
or
so
we
have
a
sorry
Sergey,
can
you
scroll
up
a
bit
yeah,
so
we
have
eight
bugs
that
were
created
and
13
bugs
that
were
closed
in
terms
of
the
recent
progress
in
the
past
month
we
have
had
four
meetings
and
on
an
average
we
have
seven
attendees,
but
we
have
had
13,
unique
participants
and
just
a
shout
out
to
all
the
attendees
that
have
been
attending
the
meeting
regularly
and
helping
out
in
this
area
moving
down
to
the
pr
stats.
D
D
Absolutely
yeah,
so
we've
captured
some
stats
here
for
the
PR's
made
to
KK
PR's
made
2K
in
test
area
and
test
infrastructure,
and
all
of
these
links
and
pointers
be
it.
Links
to
test
grid
are
essentially
opportunities
and
work
waiting
to
be
grabbed.
So
if
people
are
interested
feel
free
to
assign
themselves
to
that,
I
think
that
completes
our
reports.
A
Again,
overall,
we
are
in
Green
State.
We
accumulate
in
depth
right
now,
so
we
I
think
we
removed
a
lot
of
that
on
bug
triage
front.
We
don't
like
didn't,
know
about
critical
bugs
and
we
don't
have
anything
that
we,
like
any
unknowns
are
eliminated,
but
there
are
some
critical
bugs
that
are
not
looked
at
so
same
with
tests.
We
know
that
everything
works
pretty
stable,
but
we
have
long-standing
issues
that
blocks
us
from
being
completely
green
and
having
like
good
signal.
Overall,
any
questions.
A
Okay,
if
you
have
any
questions
you
want
to
reach
out
offline,
please
do
if
you
know
somebody
interested
in
contribution.
Please
send
them
away.
A
Next
item
is
sidecar
working
group
I
set
a
doodle
for,
but
for
to
pick
a
time
it's
European
kind
of
aligned
it's
morning
in
Pacific
time,
I
mean
morning
ish.
A
B
So
there
is,
as
far
as
the
code
is
concerned,
there
isn't
any
significant
anything
to
update
except
I
made
a
few
fixes
to
address
Ronald's
comments,
the
unit
tests
that
we're
missing
and
added
a
type
of
fix,
but
really
I
think
we're
waiting
for
the
container
D
release
to
happen.
I
tested
this
out
privately
with
the
latest
container
d169,
the
master
Branch
container
D
and
the
full
e2e
tests
work.
Fine
with
that,
and
also
try
to
talk
with
the
cryo.
It
works
fine,
but
I
think
for
release.
B
We
want
this
to
be
that
we
want
the
container
need
to
be
available
so
that
it
can
run
the
full
ETV
tests
every
time
a
code
is
a
chicken
is
made.
So
that's
what
we're
waiting
on
I
don't
know.
Mike
do
you
know
when
I
saw
Reuben's
comment
last
week
that
you're
planning
to
get
this
feature
in
1.7
and
not
169.?
B
So
when
do
we
think
we
will
have
that
officially
out
169.
E
Yeah
I
I
don't
have
a
timeline
because
containerdy
doesn't
release
based
on
well
the
time
it's
actually
features
driven.
There's
enough
feature.
It
is
going
to
be
a
new
release.
E
Samuel,
who
is
also
on
the
call
I
believe
yesterday,
he
said,
hey
we're
gonna.
He
said
he
was
gonna.
Take
a
look
at
the
release
of
169.
When
he's
got
some
time.
B
C
Usually
we
do
it
on
on
cve
requirements,
but
we've
talked
about
doing
it
this
week
or
or
you
know
just
priority.
Coupon,
okay,.
B
That's
great
so
if
it's
there,
then
we
can
I'm
taking
vacations
in
December.
It's
going
to
be
around
the
time
when
this
release
is
going
to
come
out
so
I'm
hoping
to
wrap
this
up.
Hopefully
we
can
get
this
in
early
so
that
if
there
are
any
issues
I'm
available
to
look
into
it,
so
that
that
was
the
only
thing
I
wanted
to
give
a
heads
up
on.
B
So
yeah
that
so
Ronaldo,
if
you
have
any
concerns
with
the
c
group,
please
let
me
know-
hopefully
the
next
week
is
coupon.
So
after
that
there
should
be
a
little
bit
of
quiet
time
to
fix
any
issues
that
are
there
or
any
code
review
issues
to
look
at
to
get
this
ready
to
go
in
as
soon
as
the
CIA
is
ready
for
it.
B
B
Glory
stories
but
yeah
I
think
next
next
week
we're
all
going
to
be
pretty
busy
right
so
Mike
and
Peter
and
Menaul.
If
you
can
take
a
look
at
the
I,
have
the
coupon
slides
for
next
week,
11
to
16
are
pertaining
to
our
to
the
In-Place
recess
feature.
If
you
have
the
chance
have
some
time,
please
flip
through
them,
and
let
me
know
if
something
is
off
especially
slide
16,
which
is
I.
B
Think
a
lot
of
feedback
from
Mike
has
gone
into
that
I
want
to
try
and
emphasize
what
we
need
from
the
runtimes
and
capture
that
I
hope.
This
bullet
points
captured
well
sounds
good.
Thank
you.
That
was
all
from
me
any
questions.
B
Yeah
I
think
next,
our
our
talk
is
on
Wednesday
next
26
I
think,
hopefully,
I'll
see
a
whole
whole
bunch
of
you.
There
in
person.
A
Yeah
and
if
you're
going
to
click
on,
please
register
for
contributor
Summit
in
a
month
on
Monday
I,
think
yeah.
B
I
already
did
that
so
I'll
be
coming
in
I'll,
be
flying
in
late,
Sunday
night
and
I'll,
be
there
Monday
for
that
and
switching
between
some
sessions
with
the
application
networking
the
HTO.
There
is
some
interesting
sessions
there
and
of
course,
then
there's
this
on
Wednesday.
A
Okay,
as
I
said,
he's
very
short
on
agenda
today.
If
you
have
extra
time,
you
can
spend
it
on
reviewing
PRS.
Thank
you.
Everybody
have
a
good
recipe.