►
From YouTube: Kubernetes SIG Testing 2018-02-20
A
Okay,
hello,
everyone:
this
is
the
suggesting
weekly
meeting
on
February
20th,
2017,
it's
being
recorded
and
will
be
put
on
YouTube
as
soon
as
we
get
done
with
this
pretty
quick
agenda
today.
If
you
have
anything
that
you
wanted
to
add
just
go
ahead
and
put
that
in
the
talk
and
we
can
get
to
it.
I
guess
the
first
thing
I
wanted
to
hook
up
to
it
on
the
Ponte
hoodies
that
I'm
trying
to
work
on.
A
I
open
that
a
PR
yesterday
for
like
a
generic,
just
GCS,
upload
utility,
it's
gonna
help
us
push
stuff
into
the
storage
and
then
following
that,
I
had
two
more
PRS
that
are
ready
to
open
after
that
ones
emerged:
I'm
currently
refactoring
the
Origin
PR
flows
to
use
the
binaries
and
images
just
as
pieces,
so
they're
not
gonna,
be
using
it
in
the
context
of
proud
but
we'll
be
getting
battle
tested
on
each
of
the
components.
So
I'm
feeling
pretty
good
about
that.
A
One
thing
I
wanted
to
bring
attention
to.
Ben
is
not
here
to
take
the
credit
for
it,
but
he
started
to
work
on
making
the
pre
submits
faster,
and
one
of
the
things
was
caching
for
the
basil
basil
job.
So
there's
a
link
to
a
image
there,
where
the
pre
submit
for
test
effort
has
gotten
more
than
twice
as
fast
after
his
changes.
So
he's
probably
gonna
have
a
couple
more
of
those.
It's
exciting
also
doesn't
look
like.
A
B
A
A
Okay,
well,
it's
been
a
lot
of
and
it
looks
really
good.
So
there's
a
command
health
page,
which
kind
of
explains
the
different
commands
that
are
available
and
actually
at
the
top
of
it,
you're
able
to
select
your
own.
You
know
whatever
repo
you're
working
on
and
it'll,
tell
you
on
that
repo
specifically,
which
commands
are
enabled
how
to
use
them.
A
A
Cool
the
last
thing
our
last
thing
I
had
for
today
was
there
was
any
sure
you
opened
this
morning
from
some
of
the
maintainer
to
the
helm,
repo
I
don't
know
if
we
have
sort
of
come
to
a
unified
opinion.
There's
a
couple
issues
with
the
stale
issue
closure
where
I
think
has
been
designed
in
a
way.
That's
super
useful
for
the
core,
kubernetes
repo
and
some
of
the
other
repos,
but
potentially
for
the
hollom
repo,
it's
not
as
applicable,
and
it's
been
kind
of
frustrating
for
them.
A
D
A
D
A
D
Is
a
very
hot
topic
right
now,
contributor
experience
will
actually
be
talking
about
that
tomorrow
we
talked
about
it
for
the
last
several
weeks,
I
think
it's
being
socialized
as
to
kind
of
what
is
our
main
motto.
If
you
will
meaning
consistency
is
key,
we
keep
hearing
reoccurring,
themes
across
major.
D
Z'
and
steering
committee
members
that
we
should
make
it
as
consistent
as
possible,
but
that
leaves
a
lot
of
gray
areas
with
consistent
as
possible
means,
so
I
think
we
need
to
find
a
make.
A
final
judgment
call
on
what
exactly
that
means
and
we're
going
to
discuss
that
tomorrow.
At
the
contributor
experience
meeting,
okay.
A
D
D
D
So
so
far
it
sounds
like
we
are
erring
on
the
side
of
the
entire
project
versus
helm.
In
this
case,
so
I
guess
from
a
testing
in
for
a
perspective,
it
would
be
nice
to
have
some
kind
of
not
best
practice.
That's
the
wrong
word
I'm!
Looking
for
I,
don't
know
why
I'm
thinking
that,
but
some
kind
of
like
what
can
we
do
in
this
case
of
this
one
thing
isn't
working
for
this
group
anymore
like
is
there?
Is
there
another
like?
D
Is
there
a
customization
that
we
could
do
for
this
crew
or
is
for
an
additional
bot
command?
That
would
reopen
it
if,
like
there's
certain
conditions
that
are
met,
I
guess
that's
what
I
would
just
want
to
hear
from
from
the
testing
and
Fred
crew
like
what
other
solutions,
if
we
decide
that
the
consensus
is,
consistency
is
key,
and
what
could
we
do
in
these
cases
where?
How
comes
our
or
other
projects
come
along
and
we
do
need
to
make.
D
A
A
good
question
I
think
so
right
now
there
is
a
mechanism
to
say
hey,
you
know
this
is
an
issue
we
really
care
about,
ignore
it.
Please
I
think
it
is
a
little
bit
more
onerous
to
then.
You
know
if
40
percent
of
their
issues
have
this
problem
that
can
get
kind
of
annoying
as
well
as
I
have
to
comment
that
on
all
40
percent
of
the
issues,
but
I
did
yeah.
That's
definitely
a
good
question.
Yeah.
A
D
A
F
G
G
Nobody
else
has
seen
anything
I've
missed
with
touch
going
to
the
AWS
quota
and
then
I
know.
We
had
talked
about
additional
quota
that
we
need
for
scalability
or
T
twos
I
didn't
know
if
there's
any
other
quota
types
that
we
think
we
might
need
going
forward
for
additional.
You
know
types
of
testing
or
stuff
like
that
that
anybody
had
any
visibility
into
and
I
can
try
and
get
that
moving
sooner
rather
than
later.
C
G
E
I've
been
looking
in
some
CI
test
failures.
There
are,
there
are
a
bunch
of
Kubb
admin,
related
CI,
test
jobs
that
have
been
already
for
a
while
at
least
a
month
and
and
I
think
I
think
we
have
a
fix
it.
We
want
to
try
and
it
at
least
we'll
work
around
temporary
work
around
so
Basel
we
go
get
a
Basel
build
fix
in,
but
we
have
a
commit
in
merged
in
kubernetes
anywhere.
Now
we
just
need
to
bump
up
the
rev
that
it's
pointed
to
in
the
in
the
qu,
Badman,
Runner
and
I.