►
From YouTube: Kubernetes SIG Node CI 20230531
Description
SIG Node CI weekly meeting. Agenda and notes: https://docs.google.com/document/d/1fb-ugvgdSVIkkuJ388_nhp2pBTy_4HEVg5848Xy7n5U/edit#heading=h.2v8vzknys4nk
GMT20230531-170533_Recording_2086x1340.mp4
A
A
A
A
A
Like
last
released,
we
had
two
caps
that
broke
Standalone
mode.
Now
we
should
be
able
to
catch
it
very
quickly,
yeah,
okay,
next
one
is
arm64
I'm
64
quote
for
that
was
merged.
Test
grid
definition
was
merged.
Now
the
problem
still
persist
after
the
first
verse.
There
was
a
second
verse,
some
adjustments
made,
but
we
still
have
it
failing
you
see.
Zero
can
start.
B
B
A
A
When
we
have
mtpr
that
just
test
every
job
but
yeah,
maybe
I
keep
it
in
sync:
periodics
and
CI.
Jobs
is
not
sometimes
say
going
away
from
each
other
and
like
Ci,
job
is
not
fully
covering
with
our
periodics
running
or
other
ways
around,
and
it
makes
it
harder
to
understand
how
to
test
the
pr
and
what
kind
of
tests
are
available.
C
B
No
I
was
kind
of
thinking
about
this,
but,
like
my
understanding
was
that
we
have
periodics
and
then
we
have
pre-submits
and
the
purpose
is
kind
of
different
from
each
other.
In
the
sense
that
you
know
you
submit
your
pre-submit,
you
can
enable
a
job
at
a
time
of
a
PR
for
a
very
specific
case,
and
and
that's
why
we
have
them
as
optional,
so
enabling
them
as
part
of
periodics
might
be
just
because
of
resource
constraints.
I
believe
I
kind
of
want
to
have
that
separation.
And
but
that's
just
my
understanding,.
A
Yeah
so
yeah,
the
problem
is
that
approaches,
please
submits,
are
degrading
over
time
and
police
admits
also
diverging
from
periodic's
definition.
So
if
there
are
some
Alpha
feature
flag
or
like
some
feature
flags
that
was
defined
on
periodics,
it's
not
on,
please
submits
any
longer,
and
please
admits
wouldn't
run
that's
kind
of
issues
happening
all
the
time
right.
That's
that's.
Probably
the
reason.