►
From YouTube: Kubernetes SIG Testing - 2021-06-01
Description
A
Let
me
just
do
the
quick
intro
welcome
everyone
to
the
sick
testing
week
meeting
today
is
tuesday
june
1st
2021.
remember
to
follow
the
code
of
contact
while
right
here,
yeah
rihanna,
take
it
away.
B
All
right,
you
would
see
that
we
created
a
an
issue
to
make
a
new
label.
Basically,
we
need
to
get
the
guide,
keep
and
ensure
that
all
conformance
prs
that
come
in
for
for
promoting
performance
tests
actually
should
be
circling
according
to
their
rules
for
two
weeks,
flag,
free
and
the
label
that
we're
proposing
is.
It
should
be
added
automatically
whenever
you
touch
the
conformance
yaml
file
and
then
be
removed
manually
by
whoever
is
allowed
to
merge
it.
B
So
the
idea
at
this
stage
is
to
stop
merging
with
a
manual
remove
so
we'd,
like
some
feedback
on
that
and
community
ideas
on
that
conformance
is
well
down
down
the
road
for
covering
all
the
technical
debt,
but
all
new
endpoints
coming
and
also
need
their
two
weeks
flag
free.
So
it
would
be
a
long-term
thing,
even.
C
B
A
So
I
think
adding
it
when
it's
changed
should
be
possible
today,
with
the
owner's
label
configuration
I'm
wondering
if
you
expect
the
users
who
are
removing
the
label
to
remove
it
today,
you'd
need
like
right
access
to
the
repo
and
that's
pretty
locked
down.
A
B
B
Can
approve
conformance
brs?
I
think
those
people
should
be
the
ones
that
that
remove
it,
because
they
are
the
the
stewards
making
sure
that
that
we
do
not
merge,
and
I
they
normally
would
not
allow
it
in
before
the
two
weeks.
But
it
also
is
a
bit
of
a
reminder
for
everybody
keep
in
mind.
We
need
to
do
weeks
and
manually
it
could.
I
know
two
or
three
releases
ago.
There
was
a
case
where
they
let
it
in.
B
I
think
after
a
week
because
of
test
freeze
and
code
freeze,
so
it
should
be.
I
think
it
needs
to
be
automated.
It
could
be
when
that
approver
actually
get
it
to
the
approved.
They
can
just
remove
that
label.
B
B
A
We
could
open
it
up
to
the
test
info
like
generally,
but
I
I
think
it's
probably
got
the
fastest
way
forward.
If
it's
something
you
could
pick
up,
I
can
leave
a
comment
and
again,
I'm
speaking
just
as
me.
I'm
not
sure
aaron
would
probably
have
a
different
opinion
here.
I'll
leave
a
comment
in
the
in
the
pr,
but
I
I
think
what
you're
proposing
sounds
like
a
pretty
reasonable
thing
to
do,
and
certainly
adding
that
label
automatically
is
something
we
can
do
today.
C
B
No,
the
idea
is
whenever
you
create
a
creative
etv,
and
the
e2e
test
must
run
for
two
weeks
before
you
can
do
the
promotion
vr
so
you'll
the
owner
would
auto
also
create
the
e2e
test.
Get
the
test
grid
link
create
the
pr
for
the
promotion.
The
moment.
B
Conformance
after
the
other
conformance
yaml,
it
would
actually
block
it
with
a
label
saying
you
need
two
weeks
from
your
issue
before
your
e
to
e
test
and
then
whoever
improves
it
would
then
require
they
show
me
your
link
show
me
that
you've
done
your
two
weeks,
flake,
free
and
then
based
on
this,
it's
more
of
a
reminder
for
for
the
people,
that's
already
looking
after
conformance
and
also
an
information
label
for
people,
because
not
everybody
is
acutely
aware.
C
C
C
Fail
that
the
the
windows
dashboards
we
already
have
in
place
and
since
we
are
trying
to
get
them
informing,
they
would
kind
of
block
us
in
that
regard.
Is
there
any.
C
Procedure
to
make
sure
that
it
works
for
windows
as
well,
first
or
at
the
very
least,
add
a
linux.
Only
tag
or
something.
B
The
conformance
requirement
at
the
moment
is
for
all
non-vendor-specific
endpoints.
So
if
an
endpoint
is
specific
for
a
specific
vendor,
it
does
not
qualify
for
conformance,
but
whether
the
non-vendor-specific
items
actually
work
on
windows.
I
don't
think,
there's
a
specific
that
I
think
that's
more
a
question
of
for
the
conformance
meeting.
I'm
not
100
sure.
B
What
we
have
started
doing
from
our
side,
because
we're
doing
the
bulk
of
the
promotions
for
conformance
we
actually
the
moment
we
have
the
e2e
test
in
and
it's
on
the
test
grid.
We
create
the
promotion
vr
to
be
in
the
queue,
so
people
can
already
say:
oh
there's,
a
promotion
coming
and
we
copy
the
link
to
the
test
grid.
So
anybody
can
click
on
the
link,
follow
and
go
to
the
test
grid.
So
we're
trying
to
keep
it
as
low
friction
as
possible
for
anybody
wanting
to
review
and
be
sure
where
we
are.
D
A
Sweet,
we
don't
have
anything
else
on
the
agenda.
Does
anyone
that's
in
the
meeting
right
now?
I
want
to
bring
anything
up.
A
Cool
thanks
everyone
for
joining
we'll
get
the
rest
of
the
hour
back
thanks.