►
From YouTube: Kubernetes SIG Testing - 2019-05-07
Description
A
A
A
B
Your
kindness
could
we
edit
the
zoom
blink,
the
zoom
link
in
the
calendar.
Invite
seems
broken,
maybe
it's
just
me,
but
it
thinks
it's
a
Maps
link
and
it's
also
the
wrong
zoom
ID.
Even
if
you'd
like.
If
you
go
to
the
agenda,
then
yes,
it's
the
correct
assume,
but
every
time
I
try
to
it.
I
go
I,
go
to
the
wrong
zoom,
meaning
do.
B
A
A
A
It
is
now
what
if
I
Pam
so
go
ahead
and
get
started
so
hi.
Everybody
today
is
Tuesday.
May
7th
I
am
Erin
of
severe.
You
are
at
the
kubernetes
SiC
testing
weekly
meeting.
You
are
all
adhering
to
the
kubernetes
code
of
conduct
by
not
being
jerks,
and
you
can
go
watch
yourselves
do
so
later,
because
this
meeting
is
being.
A
Recorded
and
will
be
posted
to
YouTube
so
first
up
on
the
agenda
when
I
guess
and
talk
to
us
offline
in
email
about
testing
at
any
rate,
limiting
system
for
github
API
stuff,
I
I
wanted
to
close
the
loop
on
that
and
see.
If
we
had
any
questions
comments,
concerns
here
and
what
we
needed
to
do
to
move
things
forward.
If
Timothy
st.
A
B
B
Users
use
it
like
specific
users
to
test
that
out
on
and
because
of
the
sheer
volume
that
the
community
CI
robot
handles.
It
would
be
a
super
great
candidate
and
basically,
what
they
would
do
is
turn
on
a
flag
that
sends
parallel
data
to
Splunk
right
now.
That
is
all
it
would
do
there
wouldn't
be
actually
any
new
rate-limiting
enabled
it's
really
just
for
research
purposes.
At
this
point
there
is
a
documented
rollback
process
and
I
do
believe.
The
doc
I
tried
to
link
I
thought
I
linked
in
the
notes.
B
Maybe
I
didn't,
let
me
know
to
fix
that
has
a
contact
email.
These
are.
This
is
Nick
Van,
Wiggins
team
and
he's
been
helping
out
with
a
lot
of
github
API
stuff.
Wednesday,
testing
and
prowl
has
seen
issues
in
the
past.
We
shouldn't
see
any
changes
from
the
kubernetes
side
there
shouldn't
be.
It
should
really
not
make
a
difference.
B
A
A
Opened
an
issue
to
signify:
if
something
goes
wrong,
we
got
something
we
can
link
back
to.
Let's
move
forward
so
I,
don't
know
what
has
to
happen
on
your
end
to
make
that
happen,
ICC
great
individuals
that
were
mentioned
in
the
gist
I've
assigned
Eric
and
Nicole
who
have
joined
this
call
as
contacts
on
our
end.
If
there's
anything,
we
need
to
do,
we
listed
Katie
ireba,
as
one
thing
I
think.
Also
maybe
there's
another
thing
we
could
identify
so
I
want
us
to
funnel
the
discussion
to
that
or
the
issue.
Okay,.
B
A
C
Gonna
make
it
short
sweet
we're
doing.
There
are
a
couple
of
umbrella
issues,
we're
tracking
a
lot
of
teasing
a
part
of
the
test,
suite
primarily
for
dependency
problems.
I,
don't
know
if
you
actually
do
a
def
graph
of
the
antenna
testing
favor,
but
it's
amazing.
You
find
that
one
thing
is
connected
everything
else,
so
we're
teasing
apart
that
primarily
for
the
ability
for
people
to
Thunder
the
framework.
This
is
part
of
like
the
long-standing
work
items
we've
had
forever.
C
I
wrote
more
specifically
about
getting
certain
things
out
of
tree
and
enabling
test
apparatus
for
those
facilities
than
the
mana
tree,
namely
calm
providers
is
the
most
pressing
upon
so
theta.
If
you
have
comments
with
reviews
that
you
seem
to
get
assigned
to
randomly
feel
free
to
focus
on
the
testing
combos
channel,
there's
reasons
why
we're
doing
everything
I'm.
A
Trying
to
take
a
look
at
reviews
as
well
and
I,
feel
like
I've,
seen
one
umbrella
issue.
That's
like
we
want
to
break
it
apart
when
it's
unclear
to
me
exactly
what
things
are
being
broken
apart
and
why
so
like
it
was
done
whether
or
not
the
messaging
was
like
just
freaking
up,
and
somebody
was
breaking
things
up
into
a
package
that
didn't
seem
to
be
listed
in
the
issue
that
talked
about
breaking
things
up.
The.
C
A
Okay,
I
will
take
my
questions
over
to
the
testing
Commons
channel
if
it
seems
like
things
are
being
broken
up
like
to
granularly
or
it's
unclear
to
me
like,
where
they're
being
shoveled,
because
I
love
the
impression
you
have
a
directory
structure.
You
intend
to
make
so
it's
about
populating
that,
rather
than
like
exploding
everything
into
100
pieces
and
then
it's
broken.
C
C
C
A
A
Okay,
so
next
up
I
have
something
on
the
agenda
where
I
feel
like
I've,
been
carrying
around
this
agenda
item
for
a
couple
weeks
now
and
still
haven't,
had
the
time
to
go
through
and
dig
into
what
is
it
that
we
are
doing
with
prowl
and
what
are
our
long-term
plants
or
roadmap
for
it?
So
I
don't
know
if
we
wanted
to
go
through
that
doc
today
and
speak
to
that
a
little
more
I
can
also
walk
us
through
what
is
currently
in
our
115
milestone.
A
So
we
can
talk
about
what
we
are
planning
and
working
on
before
those
two
things.
I
wanted
to
chat
specifically
about
the
concept
of
coding,
release
blocking
jobs,
it's
going
to
place
a
link
in
chat
and
yeah
sure
why
not
I
guess
I
can
share
my
screen
here.
So
conceptually
right
now,
I
feel
like
the
release
team
has
felt
this
pain
where,
like
release
blocking
jobs,
it's
kind
of
unclear
who
owns
what
so,
if
I
go,
take
a
look
at
the
repo
called
cig
release
where
all
of
the
release
related
processes
are
defined.
A
A
So,
in
order
to
help
us
measure,
the
responsive
part
could
be
helpful
to
know
like
when
alerts
are
being
sent
out
and
like
when
they
are
being
reacted
to
in
some
form
or
another.
So
it
seems
like
a
good
way
to
represent
that
would
be
by
using
test
grants.
Functionality
where
test
grade
can
actually
send.
A
I
haven't
up
an
issue
about
finding
owners
for
all
of
the
release.
Blocking
jobs
on
cig
testing
I
believe
should
be
the
owner
for
some
of
these
jobs.
I
plan
to
enforce
this
by
right
now
we
have
tests
that
much
the
test
grade
configuration
and
make
sure
that,
like
everything
that
has
a
proud
job,
also
has
an
entry
somewhere
in
test
grid.
I'd
like
us
to
enforce
that
everything
that
is
in
released
blocking
has
an
email
address
that
it
can
send
alerts
to
so
I.
Don't
know
if
I
have
anything.
That's.
A
Visible
here
sorry
I'm
doing
this
live,
but
conceptually
I
go
to
sig,
releasing
best
signal,
ease,
master
blocking
I
think
there
are
a
lot
of
jobs
here
where
test
cases
belong
to
a
lot
of
different
people.
So,
for
example,
this
tests
GC
cause
master
default
and
separating
test
cake
most
of
the
end-to-end
tests
that
are
slow
or
flaky
or
really
to
a
special
feature.
A
They
all
have
names
like
sink
storage,
seeing
network
whatever
scene
it
belongs
to,
but
ultimately
like
a
single
entity
should
be
responsible
for
making
sure
that
this
job
is
healthy
and
that
the
individual
test
cases
are
being
entrusted
by
the
appropriate
six
jobs
like
this.
It
seems
really
clear,
like
that's
already
the
responsibility
of
the
CI
signal
role
on
the
release
team
and
so.
A
Release
team
home
most
of
these
jobs.
That
said,
there
are
many
jobs
that
I
think
fall
more
within
the
domain
of
state
testing,
like
the
verified
job,
which
has
a
ton
of
these
like
scripts
that
are
supposed
to
kind
of
lint
and
verify
and
check
things
and
I'd
like
for
us
to
take
at
least
the
initial
ownership
of
the
job
and
then
figure
out
ways
to
shard
off
to
other
entities.
A
If
they
own
things
like
the
conformance
requirements,
verify
job
should
probably
be
owned
by
state
architecture
because
of
the
conformance
definition
working
group
I
would
probably
want
the
API
machinery
folks
to
own
a
number
of
things
that
relate
to
generation
for
API
machinery.
I
also
feel
like
we
should
own
any
job
that
has
the
word
basil
in
it,
so
on
and
so
forth.
A
Google
group
and
I
feel
like
for
now
the
folks
who
go
through
our
open-source
on-call
rotation
can
subscribe
to
this
and
as
we
move
to
a
world
where
prowl
runs
in
community
and
infrastructure,
other
people
can
also
subscribe
to
these
alerts
and
make
sure
they
are
kept
up
to
date
on
when
things
break.
And
why
so.
Any
of
this
seem
wildly
controversial.
A
A
That's
really
all
I
had
to
say
about
that.
Specifically,
if
you
want
with
our
remaining
ten
minutes,
I
can
walk
us
through.
What's
in
the
115
milestone,
I
can
also
give
us
ten
minutes
I.
Could
anybody
else
has
anything
they
want
to
talk
about
with
the
ten
minutes
or
we
could
just
get
ten
minutes
back.
A
Okay,
well
with
that
resounding
set
of
opinions,
I
will
be
closing
out
the
114
milestone
today.
Anything
that
gets
kicked
over
into
115,
hi
or
somebody
else
I
know,
may
be
working
on
it
if
it's
not
in
a
milestone,
we're
not
working
on
it
and
if
you
care
deeply
about
that,
please
come
reach
out
to
us
on
state
testing.