►
From YouTube: Kubernetes SIG Node 20201116
Description
Meeting Agenda:
https://docs.google.com/document/d/1j3vrG6BgE0hUDs2e-1ZUegKN4W4Adb1B6oJ6j-4kyPU
A
Good
morning
it's
monday
november
16th,
it's
a
ci
group
of
signaled.
Are
we
talking
about
test
failures
and
helping
each
other
fix
this
test
so
yeah
the
this
week
is
kubecon
week.
I
think
many
people
will
be
out
and
about
watching
some
presentations.
I
also
know
that
like
right
now
there
is
a
quote
freeze,
so
there
is
no
like
regular
code
authoring.
A
We
just
need
to
fix
as
many
release
blocking
tests
as
possible,
so
I
want
to
like
there
is
a
non-release
blocking
tab
called
serial
on
couplet
and
it's
all
red.
So
I
want
to
start
with
that
and
ask
if
anybody
already
looked
at
it
and
if
not,
who
who
wants
to
take.
A
A
Well,
thank
you
yeah.
This
will
be
great.
I
noticed
last
week
it
was
like
friday
when
I
was
thinking
about.
What's
going
on,
I
saw
no
test
run
at
all,
and
today
at
least
we
have
some
tests
run.
So
I
think
it's
some
infrastructure
place
infrastructure
issue.
D
E
D
I
mean,
I
think
it's
been
failing
for
a
long
time.
I
I
I
vaguely,
like
I
said
I
wrote
in
the
issue.
I
vaguely
have
memories
of
it,
leaving
like
a
couple
of
things
failing,
but
now
it
just
seems
it
fails
all
the
time
so
and
if
you
look
at
the
the
flake
meter
json
or
whatever
it's
called
it's,
you
know
it
says
failing
for
965
days
or
whatever,
so
there
you
go
1045
days.
So
you
know
it's.
A
A
It
because
I
remember
I
was
looking
at
limiting
tests,
we've
been
ga
and
limiting
feature
and
signal,
and
I
was
looking
specifically
on
p
limiting
it
was
working.
I
don't
know.
A
Okay,
so
our
term
don't
expect
to
fix
everything.
So
I
think
if
there
is
an
infrastructure.
E
A
Should
spread
across
everything,
but
then
fixing
this
issue
may
still
keep
up
with
a
few
flavors.
B
A
Thank
you
very
much.
Next.
F
F
Yes,
that's
me
it's
it's
very,
very
simple
question.
I
thought
it
was
a
good
idea
to
ask
in
this
forum
who's
the
contact
point
for
the
kubernetes.
Is
this
gc
device
plugin
gpu
lane?
I
mean
you
just
need
to
get
in
touch
and
understand
why
it
fails,
because
it
feels
like
setting
up
the
environment
trying
to
set
up
the
cluster
timeout
fails
and
just
wanted
to
learn
more
and
see.
What's
going
on.
C
Yeah
hi
this
is
raven.
I
was
looking
into
this
failure
and
I
just
put
this
issue
here
so
basically,
the
test
currently
is
failing,
because
in
this
new
version
of
kubernetes
we
are
checking
the
topology
info
from
the
devices
returned
from
us
plugin.
However,
in
our
current
version
of
device
plugin,
we
don't
have
this
topology
info,
which
means
topology,
is
not
there.
C
So
that's
why
we're
seeing
a
lot
of
fun
mpe
in
the
test-
and,
I
think
sorry
forgot
his
name,
but
there
is
a
fix
already
there
on,
but
I
think
the
fix
well,
the
test
is
still
filling
on
the
fix.
I
have
a
look
into
this
new
failures,
but
yeah
I'll
be
looking
into
it.
C
A
Yeah,
we
also
still
have
critical
test
failures.
I
looking
at
one
in
release
blocking,
I
think
who
was
with
another
mate.
You
was
looking
and
another
one.
E
Yeah,
I
I
don't
think
I
had
was
working
on
any
other
test
failures.
I
just
needed
to
figure
out
why
the
output
on
the
conformance
tests
isn't
quite
right.
E
Yeah,
I
haven't
had
ted
time
to
figure
out
how
a
specific
variable
was
set
yet,
but
hopefully
I'll
have
time
this
week,
cool.
A
Okay,
it's
a
very
short
agenda
and
we
we
have
a
lot
of
work.
If
anybody
wants
some
work
and
doesn't
know
what
to
do,
we
can
probably
like
mention
some
pr's
like
assign
some
issues.
F
A
Okay,
I
will,
I
will
take
a
look
and
pin
you,
but
anybody
else.
If
you
see
something
and
like
feel
free
to
mention
francesca
right,
am
I
saying
right
francesca.