►
From YouTube: Kubernetes SIG Node CI 20230510
Description
SIG Node CI weekly meeting. Agenda and notes: https://docs.google.com/document/d/1fb-ugvgdSVIkkuJ388_nhp2pBTy_4HEVg5848Xy7n5U/edit#heading=h.2v8vzknys4nk
GMT20230510-170403_Recording_2160x1340.mp4
A
A
A
It's
a
signaled
CI
meeting
welcome
everybody.
We
have
for
an
agenda
item
today,
Swati.
What
do
you
want
to
talk
about.
B
This
created
on
kubernetes,
test
infra
and
I'm,
not
the
most
proficient
with
test
Central
jobs.
I
was
hoping
that
someone
can
kind
of
proofread
what
I'm
doing
there
I
see.
There's
a
unit
test
failure
still
there
so
I
I
would
really
appreciate.
You
know
some
help
there.
What
I'm,
trying
to
enable
is
on
release
branches,
125,
126
and
127,
that
we
can
run
node
feature
related
tests,
and
this
is
linked
to
the
back
porting
that
we
are
attempting
to
do
which
I
spoke
about
yesterday
in
the
signal
meeting.
B
It
is
failing
initially,
it
was
complaining
about
improper
test
grid
names
or
test
groups,
or
something
like
that.
I
added
that,
but
it's
still
complaining
and
I'm,
not
100
sure
what
I
can
do
to
prevent
it.
B
Let
me
take
a
look.
Sorry
I
can't
actually
see
it.
B
B
Yeah,
so
it
exists
in
pre-submit
like
kubernetes
master
pre-submit,
so
should
I
be
using
a
different
name.
It's
a
it's
essentially
complaining
that
I'm
using
the
same
name
as
it.
A
A
Yeah
and
from
just
review
perspective,
anybody
wants
to
willing
to
help.
D
You
can
help
me
after
your
thank.
A
You
yeah,
it
will
be
sick
release.
We
will
need
somebody
from
Securities
because
it's
do
we
need
to
to
be
in
securities.
A
D
Couple
of
release
branches
for
for
for
not
really,
but
just
like
some
jobs
for
release
branches
are
really
let
me
maybe
you
can
put
them
together.
A
And
you
put
them
in
under
six
node
right
so.
B
B
A
Mike,
once
you're
done
with,
did
you
ping
me
I
will
approve.
D
A
Okay,
any
more
agent
items
today.
If
not,
then
we
can
go
to
triage
I,
also
reviewed
the
performance.
It
still
looks
good,
so
no
need
to
open
it
here.
A
Okay,
Francesca.
E
Yes,
so
very
fresh,
simple
enough,
so,
instead
of
having
the
sample
device
plugin
image
as
an
exception
here-
just
add
it
to
the
you
know:
image
list
managed
by
the
test
framework.
E
E
Yes,
we
should
this
is
why
I'm
running
all
the
serial
tests
to
make
sure
the
flow
is
exercised,
but
yeah
should
be
simply
ever.
Okay
yeah.
It's.
C
E
C
A
I,
don't
think
it's
test
related.
F
F
A
F
Yeah
I
put
this
on
the
signal
agenda
for
next
week.
To
basically,
the
debate
is
whether
it
needs
to
be
configurable
or
could
be
the
new
default
or
no
configuration.
A
Okay,
I,
don't
think
it's
a
test
related.
It's
looks
like
a
coatulated.
A
D
It's
not
really
an
issue,
I
think
it
was
somebody
flagged
it
as
a
potential
potential
issue,
but.
C
A
A
A
D
A
Well,
of
course,
I
anyway,
let
me
close
it.
A
A
A
B
A
Anybody's
interested
to
look
at
it,
the
stock
job
is
basically
something
that
never
shut
off
the
node.
The
node
keeps
running.
A
Okay,
so
there
is
like
another
cleanup
on
the
nearly
I
think
about
it
in
the
slack
last
week,
so
maybe
she'll
come
back.
A
A
Oops
yeah:
what
does
it
say.
A
A
C
C
A
It
has
a
flake
with
boiler
mounts.
A
A
Yeah,
okay,
I
think
we're
done
with
this
to-do
list.
Well,
you
can
pick
Daniela.
A
Yeah
I,
don't
think
this
is
being
repeated.
B
A
Perhaps
you
can
Target
swap
cap.
C
A
Okay,
so
this
is
related
to
In-Place,
update
and
Vina
is
assigned
so
likely
it's
okay
and
it's
okay!
Okay,
thank
you,
everybody
for
reviewing
it
with
me.
We
now
will
go
to
box
any
other
agenda
for
that's
really
the
stuff.
A
C
A
Time
out
seconds
period,
so
you
yeah
it
shouldn't
start
any
new
job.
Before
timeout
like
before
previous
execution,
succeeded.
A
Is
it
yeah
just
think
again.
F
A
A
Is
the
issue
that
we
are
missing
weight
here.
F
The
the
error
message
doesn't
have
the
Pod
name.
It
has
the
container
ID
instead
I
see,
and
that
was
the
and
this
person
submitted
a
PR
it
to
fix
it,
but
their
fix
involve
threading
the
Pod
name
through
the
CRI
I.
Think
a
few
of
us
commented
back
that
probably
wasn't
going
to
work
to
update
the
CRI
interface
just
to
fix
this
log.
A
A
A
A
A
Yeah,
if
basically
it's
resolved.
A
A
C
A
A
So
David
yesterday
said
that
they're
looking
at
termination
improvements
and
Dixie
you're,
also
working
on
pod
life
cycle
right
tests.
B
A
A
A
A
A
Okay,
then,
have
a
good
rest
of
the
day.
Bye
thanks.