►
From YouTube: Kubernetes SIG Node 20210224
Description
Meeting Agenda:
https://docs.google.com/document/d/1j3vrG6BgE0hUDs2e-1ZUegKN4W4Adb1B6oJ6j-4kyPU
A
Good
morning
it's
february
24th
2021,
it's
a
signal,
ci
subgroup
meeting
and
we
have
very
short
agenda
again,
let's
jump
right
in
it.
First,
we
wanted
triage
issues
as
usual.
Let's
go
to
oh,
I
don't
see
my
screen.
B
A
Thank
you,
sorry
for
my
voice.
I
I'm
taking
second
day
off
second
half
of
the
day
off
anyway,
so
I
tried
most
of
it.
There
are
a
few
like
triaged
out
mostly
and
some
they
were
approved.
They
just
moved
to
approval
column.
A
A
Yeah
and
it's
jobs,
so
it's
it's
not
related
to
our
group,
okay
and
then
I
will
need
to
go
through
archived
items
and
add
them
to
main
signal
dashboard
like
project
board.
A
So
this
seems
to
be
something
that
you
may
take.
A
So
this
one
is
somebody
improving
assertions.
So
if
some
fake
runtime
fails
with
the
calls
we
need
to
assert
and
fail
the
test
and
then
parameter
dependencies
for
n
into
the
node,
I
think
it's
related
to
us.
I
haven't
looked
at
this
yet.
B
A
A
A
D
A
A
A
Okay,
so
this
is
so
if
host
swap.
A
A
I
have
a
feeling
he's:
not
he
won't
be
able
to
take
it
anytime
soon.
I.
B
See
yeah
you
can
you
can
either
cc
or
assign
both
of
us,
and
I
will
see
if
I
can
get
to
it.
I
also
have
20
million
other
things.
I
bet.
A
A
Contention
job,
oh
it's
I
mean
it's
yours.
I.
B
B
B
A
Okay,
it's
already
direct
here,
but
yeah
yeah.
A
Wait
is
it
second
one?
I
I
think
you
already
merged
one
of
them
right.
F
A
Okay,
thank
you
and
we
are
out
of
items
to
review
so
yeah.
Let's
see
how
big
of
a
process
we
make
by
next
amazing,
it's
a
good
idea.
You
wanted
to
assign
people.
B
Okay,
yeah,
that's
what
we
do
in
sig
instrumentation,
which
I
just
got
out
of
this
morning,
but
I
have
not
yet
done
that
for
the
bigger
node
board.
So
maybe
now
is
a
great
time
to
start.
Oh,
I
had
a
action
from
last
last
week
or
I
guess
it
was
just
last
week,
morgan
as
approver.
I
pinged
him
again
because
he
needs
to
submit
a
pr
for
that.
B
Yeah,
I
think
it's
the
the
like
test,
no
or
test
e
to
e
slash,
node
and
test
e
underscore,
I
think
yeah.
A
Okay,
let's
discuss
this
continuity
plan,
I
mean,
do
you
wanna
talk
about
it,
you
you
brought
it
up.
D
Yeah
sure
so
for
the
sequence,
I
think
this
is
the
worst
one
doorstep
that
says
failures,
so
it
makes
sense
to
start
tackling
them
looks
like
these
can
start
to
bring
some
plan
and
already
did
some
triage
on
this.
D
Maybe
you
can
bring
these
as
tasks
and
start
to
tackle
as
part
of
the
subgroup.
You
just
need
to
make
make
sure
that
they
make
sense.
Somehow.
A
I
remember
we
discussed
it
and
we
said
that
we
will
come
up
with
I.
We
want
to
do
split
tests
that
actually
taking
container
d,
so
we
have
to
have
a
build
container
d
and
there's
a
run
test
on
container
d.
So
these
are
two
different
categories.
We
didn't
want
to
mix
them
up
and
I
remember
we'd
been
discussing
that
somebody
need
to
write
a
specific
like
proposal
which
versions
of
continuity
we
test
against
which
version
of
kubernetes.
A
Do
you
know
if
this
happened?
A
B
Yeah,
the
time
is
not
great
for
her.
It's
very
late,
because
she's
in
india.
A
A
I
mean:
do
you
want
to
take
action
item
and
describe
which
versions
we
want
to
test
and
based
on
idc
comments,
or
we
just
want
to
ping
and
ask
her
to
do
that.
Yeah,
maybe
paying
for
it.
F
D
F
D
D
A
Okay,
so
we
also
need
to
understand
where
to
put
this
test,
so
we
need
to
have
continuity,
tab
that
is
purely
testing
continuity,
but
then,
on
release
blocking
we
probably
need
to
test
it.
We
need
to
test
regular
tests,
like
all
the
tests
on
continuity
on
some
of
the
version
of
containers.
E
Yeah,
I
put
it
here.
I
just
yeah
good,
quick
kind
of
question
feedback
would
be
nice
for
from
you
all,
so
I'm
working
on
a
glacial
shutdown
feature
and
we're
adding
et
test
for
it.
So
the
feature
is
in
alpha
right
now
and
it's
also
a
serial
test.
So
right
now
just
for
background,
we
put
the
serial
like
tag
and
the
alpha
tag,
but
there's
no
test
grid
job.
Basically,
that
runs
those
combination
of
tests.
E
So
the
proposal
here
is
just
to
create
a
new
job,
basically
new
job,
a
new
like
tab
on
test
grid
that'll
just
run
this
test,
so
I
just
wanted
to
kind
of
check
that
that's
that's
kind
of
you
know
cool
and
that's
like
the
normal
kind
of
flow,
because,
like
for
example,
we
have
a
lot
of
the
other
serial
tests.
Right
now
I
linked
on
the
on
the
dock.
The
node
kublet
serial
test,
there's
quite
a
few
tests
there,
but
the
whole
tab
is
kind
of
pretty
red.
E
I
I've
looked
at
it
briefly.
It
seems
like
some
type
of
infra
issues
where
one
of
the
test
runs
like
kills
all
the
other
ones.
So
I
just
so,
I
guess
two
questions.
One
question
is
it:
do
you
think
it's
reasonable
approach
for
like
sub
features
to
have
sub
sub
jobs
and
subtest,
and
then
the
second
bigger
question,
I
guess,
is
around
the
kublet
serial
tab.
If
there's
some
plants,
I
don't
know,
maybe
to
maybe
refactor
it
and
put
some.
E
C
E
C
Yeah
like
in
general,
if
I
understand
correctly
like
like,
I
also
created
the
one
like
key
pages
or
stuff
like
this.
The
main
reason
was
because
I
wanted
to
use
bigger
instances
of
gce,
so
I
needed
to
provide
the
configuration
like
different
configurations
and,
like
all
other
serial
tests
are
using
like
again
from
my
perspective,
I
don't
see
a
problem
to
create
like
additional
dub.
But
okay,
let's
see
what
sergey
and
germany
will
say.
A
Yeah
we're
trying
to
right
we're
trying
to
run
tests
together,
so
we
don't
spend
too
much
resources
on
just
standing
up
environment
and
tearing
it
down,
but
in
this
case
yeah
I
think
graceful
termination
is
very
disruptive
test.
I
think
it
may
influence
other
tests
by
like
go
into
this
termination
state
and
then
goes
back
so
I
just.
F
F
E
I
didn't
try
yeah,
I
only
tried
to
kind
of
locally
just
for
that
test.
Like
ete,
I
didn't
try
running
it
with
other
tests,
but
that's
kind
of
why
I
asked
because
it
seems
like
the
node
kublet
serial
tests
right
now
are
failing
due
to
one
of
the
tests
kind
of
killing.
All
the
rest.
That's
what
it
looked
like.
I
wasn't
able
to
narrow
that
which
one
but
looks
like
there's
some
more
colored
on
going
there.
E
A
I
think,
maybe
as
a
good
practice,
we
can
write
a
description
of
this
test
and
like
in
this
pr
provide
a
little
more
information.
While
it's
separate
tab.
E
Okay
sounds
good,
and-
and
do
you
think
maybe
we
should
yeah?
Do
you
think
we
should
extend
that?
I
mean
just
thinking
like
longer
term
like,
for
example,
the
serial
tab
right
now
has
like
a
it's.
Quite
there's,
not
it's
like
random
serial
test
based,
I
don't
see,
like
you
know,
one
category.
A
tests
like,
for
example,
there's
resource
management
tests
like
docker
shim
tests,
all
types
of
different
testing-
I
don't
know-
maybe
it
makes
sense
to
split
those
out
longer
term
too.
That's
kind
of
separate
discussion,
but
I
don't
know.
C
E
B
Oh
yeah,
I
snuck
that
in
there
I
just
wanted
to
make
sure
for
the
folks
who
are
in
this
meeting,
because
I
didn't
actually
bring
this
up
in
sig
node
yesterday
I
sent
an
email
to
sig
architecture
and
cc
sig
node.
We
discussed
not
this
week
but
the
week
prior
about
the
node
and
-2
version
sku
tests
and
basically
they
don't
exist,
so
I'm
bringing
it
to
sig
arch
asking
like
we
say
this
is
supported,
but
we
don't
actually
verify
this
anywhere.
B
B
Yeah,
the
decision
from
node
was
to
make
a
problem
of
sig
architecture,
and
so
now
it
is
becoming
because
I
think
initially
those
tests
were
supposed
to
be
owned,
not
by
sig
node,
but
by
sig
cluster
life
cycle.
So
yeah
we
can't
go
and
just
tell
them
hey
cluster
life
cycle.
This
is
your
problem,
so
yeah
going
to
say,
architecture
tomorrow.
B
That's
clever,
okay,
do
we
have
anything
else
for
ci
stuff
or
do
we
want
to
jump
into
the
wider
project
board.
A
My
new
presenter:
do
you
want
to
show
your
screen.
A
Yeah
anybody
who
are
not
interested
in
creation
product
issues
can,
like
I
mean
know
her
feelings.
You
just
go
otherwise
just
bear
with
us
with
the
product.
Yes,.
B
And
this
is
actually
the
test
board,
because
I
I
pinned
in
slack
the
links
to
both
of
the
boards
as
well
as
the
triage
guide.
So
that
way
we
can
refer
to
those
and
they're
like
in
the
channel
in
an
easily
findable
way
so
yeah
I
haven't.
Actually
I
wasn't
able
to
make
this
meeting
last
week
because
I
had
a
conflicting
meeting,
but
this
week
I
am
here.
A
Much
faster
but
yeah,
you
have
a
lot
of
experience
to
use
it.
B
So
yeah,
one
of
the
things
I
think
we
want
to
cover
today
is
feature
prs
missing
from
board
that
happen
to
have
sig
testing
label.
I
think
maybe
what
we
should
do
for
this
board
so
right
now
I
am
excluding
everything
with
the
label
sig
testing,
but
maybe
we
should
change
it,
so
we're
only
excluding
things
that
have
label
like
test
flake
and
failing
tests
and
then
we'll
miss
less
stuff
that
we
actually
need
here.
B
C
B
B
I
guess
we
can
just
manually
archive
them
when
they
don't
apply
because
yeah
otherwise
we'll
like
miss
things
like
that,
which
probably
should
be
going
on
this
board.
Oh
there's,
so
many
more
there's
so
many
more
well.
We
can
go
through
this
today
and
archive
all
the
ones
that
don't
make
sense.
I
guess
so.
Let's
do
it.
B
Oh!
That's
me,
hello.
Me.
That's
work
in
progress,
so
this,
I
don't
think,
makes
sense
to
put
on
this
board.
So
I
guess
I
can
just
put
this
on
here
and
archive
it
oops.
What
is
my
mouse
doing
now.
F
B
And
please
speak
up
if
you
think
that
I
am
wrong
in
pulling
something
off
of
this
board
or
archiving
something
that
I
think
shouldn't
be
here.
It's
rebase.
B
B
B
This
seems
like
a
reasonable
thing
to
put
on
this
board,
and
that
looks
like
everything
is
ready
for
it.
Work
in
progress,
not
ready
for.
A
B
Yeah
but
then
I
guess
it
doesn't
like
the
board
is
helpful
for
sort
of
showing
people
what
the
state
of
yeah
our
triage
is.
B
Sorry,
we've
brought
this
upon
ourselves
because
we're-
I
guess,
we're
almost
through
this
list
now
that
we're
pulling
in
all
of
this
prs
that
previously
weren't
looking
at
goodness
this
one
has
like
a
million
people
commenting
on
it.
Well,
I
guess
we'll
put
this
into
needs
reviewer
and
see
what
happens
with
it.
B
I
don't
know
if
my
mouse
keeps
getting
stuck.
This
one
looks
like
end
to
end
test
specific,
so
I
will
archive.
B
That,
I
guess
we're
also
picking
up
like
a
lot
of
things
that
were
rotten
too
so.
B
B
Okay,
so
we've
got
a
new,
exciting
query
and
I
guess
a
bunch
of
stuff
to
triage
and
a
bunch
of
stuff
in
needs.
Reviewer,
maybe
let's
go
through
the
so
I
know
for
needs
approver.
Essentially
anybody
on
the
approver
list
can
pick
them
up,
so
I
don't
necessarily
want
to
assign
those,
but
maybe
we
can
go
through
and
see
if
there's
no
assignee
for
the
needs,
reviewer
ones.
Let
me
just
double
check
what
that
github
query
is.
I
know
we
have
a
link
for
it
in
sig,
instrumentation.
B
Okay,
so
you've
got
like
12
of
these,
so
I've
got
a
bunch
of
folks
on
the
call
who
wants
to
get
a
sign
to
review
some
stuff.
B
C
B
You
already
reviewed
this
one.
I
see
yes,
oh,
are
you
not
an
org
member?
Yet,
oh
you
probably
are
now
so
now
you
should
be
able
to
lgtm
this.
B
I
guess
we'll
find
out
when
my
query
gets
updated.
It
looks
like
it
worked:
yay,
okay,
who
wants
to
review,
move
csi
drivers,
cash
sync
to
go
routine.
B
B
Yeah
people.
B
B
A
sig
storage
thing,
but
it's
gonna,
require,
I
guess,
approvers
from
both
sigs.
B
Is
why
this
has
been
kind
of
sitting
like
somebody
from
signo
has
triaged
this,
but
we
still
need
to
get
somebody
from
storage
to
look
at
it.
So
I'll
maybe
skip
the
sig
storage
ones.
B
B
I
think
this
is
a
change
to
the
sync
loop,
which
I
guess
also
has
storage
changes
since
it
uses
it
does
things
for
volume
manager
is
sick
storage
on
here,
not
really.
A
B
Great,
I
think
this
one
is
basically
good
to
go.
You
were
just
waiting
for
something
to
merge
in
front
of
it
so
that
one
still
hasn't
been
merged.
I'm
just
gonna
put
an
lgtm
on
this
one
and
see
what
happens
because
I've
already
reviewed
this
one.
It's
just
been
kind
of
sitting.
B
B
There
we
go,
I
will
now
be
assigned
it,
but
it
needs
to
be
updated
there
we
go
there's
another
one
gone.
Is
anybody
here
excited
about
windows
ones?
I
did
ping
sing
windows
about
these
and
the
windows
ones
are
supposedly
on
their
board.
So,
oh
sergey,
this
is
probably
one
that
you'd
be
interested
in.
This
is
the
revert
of
the
revert.
B
Problem
panda
amanda
what
a
great
username
this
needs
priority,
but
it
was
triage
accepted.
It's
probably
backlog.
B
This
looks
like
a
pretty
small
change
for
like
a
first
review.
It's
just
some
updates
for
cli
flags.
Does
anybody
want
to
take
this
one.
E
B
E
B
Now
assigned
cool
cool,
so
I
guess
what
else
do
we
have
in
here?
We've
got
a
sig
storage,
one,
that's
really
just
sig
storage,
the
sig
windows
one
and
the
sig
network,
one.
So,
okay,
there's
one
left,
which
is
this
one.
B
Oh
you're
you're,
not
an
org
member,
no
sounds
like
it's
time
for
you
to
become
an
org
member.
B
I
just
said
this
on
my
meeting
earlier,
but
I'm
happy
to
say
it
again.
If
you
are
not
currently
an
org
member
but
you're
regularly
attending
these
meetings,
I
will
absolutely
sponsor
you
to
become
an
org
member.
The
bar
for
becoming
an
org
member
is
like
is
not
going
to
use
ci
for
crypto
mining
and
has
done
useful
things
for
kubernetes.
You've
certainly
met
both
of
those
bars,
so
I
would
be
happy
to
sponsor.
You
will
need
a
non-red
hat
sponsor
since
I
work
at
red
hat.
A
A
C
Okay,
that
that's
very
cool
and
let's
just
follow
up
on
slack.
B
Fabulous,
I
love
adding
new
new
people.
This
always
makes
me
so
happy.
We
have,
I
guess,
16
minutes
and
there's
like
seven
things
here
to
triage.
So
let's
just
get
through
these
two.
I
guess,
while
we're
all
here
for
what
it's
worth
instrumentation
does
not
record
these
sessions
because
there's
not
really
anything
exciting.
I
think
to
go
back
to
look
at
on
the
recordings,
but
I
know
the
first
half
of
this
meeting
is
recorded,
so
perhaps
in
the
future.
We
cannot
record
this
half
because
there's
not
really
much
point.
B
B
This
is
from
december
10th
2019.,
I'm
like
where's
the
triage
label.
It
doesn't
have
one
because
it's
very
old,
so
this
one's
on
the
test
board
as
well
sergey,
do
you
have
an
opinion
about
what
we
should
do
with
this
one?
The
bug
rotted
out.
A
B
I
will
put
this
as
I
guess
priority
important
long
term.
I
will
triage
accept
this
and
yeah.
I
don't
know
this
has
been.
B
B
And
then
I
guess
we
can
do
you
want
me
to
remove
this
from
the
test
board?
I
don't
know
if
I
can
do
that
here.
B
But
yeah
that
probably
will
require
a
node
reviewer
so
and
yeah
also
archived
on
that
one
here.
So
the
icon
is
confusing.
It's
got
the
little
box,
but
they
both
look
the
same
to
me
so
cubelet
and
cube
proxy
ignore
cis
cuddle
errors.
I
don't
like
ignoring
this
cuddle
errors.
Maybe
that's
why
it's
got
a
hold
on
it.
If
this
has
a
hold
on
it,.
B
Oh
yeah
and
the
cap
hasn't
gone
anywhere.
Oh
yes,
I
think
this
is
related
to
that
rootless
cap.