►
From YouTube: Kubernetes SIG Testing 2018-09-18
Description
A
Everyone
today
is
September
18th.
This
is
the
sixth
testing
weekly
meeting
I've
got
meeting
notes
in
the
chat
and
we're
recording
this
we'll
put
it
on
YouTube
as
soon
as
we
can
so
in
the
minutes
are
the
first
thing
we've
got.
Is
a
presentation
about
this
multi
ball
cutter
view
tool
so
offer
it's
yours
I.
D
D
Okay,
now
you
can
see
it
yep,
okay,
so
so
I
am
going
to
show
you
a
code
review
tool.
I
have
been
working
on,
so
it's
called
reviewer,
not
very
interesting
name
and
what's
interesting
about
it.
Is
it's
a
multi
repo,
so
it
can
handle
multiple
repos
in
the
same
review
now,
so
it's
multi
repo,
it's
hosting
and
nastic,
so
it
can
work
with
any
hosting
github
gitlab
on-prem
bitbucket,
whatever
you
need
and
the
reason
it
can
do.
That
is
because
it's
actually
using
your
local
git
repositories.
So
it's
not
actually
going
to
get
habit.
D
Good,
laugh
and
all
that
it's
privacy-preserving,
so
you
can't
see
people's
other
private
code
and
source
code
never
actually
leaves
your
own
machine.
So
it's
really
secure.
You
can
view
local
changes
in
the
tool.
So,
as
your
coding,
you
want
to
see
it,
you
don't
have
to
push
to
see
the
diff
and
there's
a
multi
repos
CLI
tool
and
it
works
with
multiple
off
providers.
Github,
google,
because
it's
based
on
firebase
and
fibers
just
gives
that
for
free,
so
next
slide
skipped
one
yeah.
So
this
is
like
the
architecture
you
can
see
here.
D
This
is
fire
store
where
it's
storing
just
a
made
of
data
and
the
files
and
the
dish,
the
code
and
the
diff
are
actually
coming
from
a
local
server.
That's
getting
them
from
your
local
gift,
and
this
is
what
you
see
in
the
web
app
and
over
here.
There's
the
CLI
tool,
that's
also
interacting
with
fire
store
and.
B
D
Your
gate
and
with
your
file
system
and
there's
a
cloud
service
to
do
some
other
things
that
I
can
mention
later
now.
This
is
what
it
looks
like.
So
you
can
see.
This
is
like
the
main
panel
you
have
whatever
you
need
to
do.
This
is
like
your
to-do
list,
things
that
are
either
waiting
for
you
to
review
or
to
fix.
B
D
D
D
You
can
ask
me
questions
if
you
want
I
guess
so
the
user
flows
are
working
on
a
feature:
how
to
do
how
to
private
workers
work
and
joining
me
this
after
submission.
So
it's
kind
of
like
an
unusual
tool
because
of
the
architecture,
and
it
allows
these
different
and
special
flows
in
addition
to
the
usual
one,
but
we'll
start
with
the
usual
one.
D
D
That's
why
it's
privacy-preserving,
because
if
one
of
the
repos
here
was
actually
private
and
the
reviewer
won't
see
them,
and
so
they
get
approval
only
for
the
files
they
saw
once
everything
is
approved,
then
you
can
submit.
As
the
author
and
the
cloud
service
cloud
service,
merges
the
changes
for
the
repos.
It
can.
B
D
D
Private,
repos
CI
checks
the
diff.
If
the
diff
is
not
breaking
the
private
repo
see,
I
can
actually
tell
the
system
this
diff
is
approved
and
if
it
breaks
then,
as
a
private
rego
owner
I
can
join
this
make
the
fixes
participate
in
the
discussion,
contribute
changes
to
the
public
code
and
once
and
everything
is
served
locally,
so
nothing
is
really
shared.
That
is
private.
I.
Think
I
already
said
that,
like
three
times,
okay,
now
you
can
actually
join
it
if,
after
it's
been
submitted,
so
you
can
have
you
can
be
like
a
light
repo.
D
D
D
D
D
D
D
And
then
I
can
see
it's
here
immediately,
yeah
the
to
block.
Also,
this
part,
sorry
about
that.
That's
the
basic
idea,
yeah
I,
think
yeah.
So
do
you
think
I
wanted
to
say
about
this
yeah?
So
that's
the
demo,
thank
you,
and
if
this
is
interesting
for
you
and
you
think
this
might
be
useful,
please
let
me
know
I'd
be
happy
to
help.
You
understand
how
to
use
this
and
how
it
can
fit
your
workflow.
C
D
A
D
B
So
I
was
looking
at
this
as
potentially
a
you
know,
interesting
way
to
use
this
potentially
instead
of
the
PR
dashboard
I.
Don't
know
you
know.
If
long-term
you
want
to
keep
the
PR
dashboard,
it
doesn't
seem
like.
That
is
something
we
invest
in
very
heavily,
and
this
seems
like
it
has
a
bunch
of
interesting
features.
I'd
be
interested
to
sort
of
see,
you
know
how
and
whether
we
could
integrate
this
with
prowl.
B
Like
one
thing,
that's
pretty
challenging
right
now
is
on
people
being
able
to
launch
you
know
PRS
or
whatever
launch
tests
without
creating
a
PR.
This
potentially
might
help
with
that.
Where
you
know,
maybe
there
was
some
off
song-and-dance.
We
could
recognize
that
I
am
a
member
of
the
org
and
I
could
sort
of
say:
hey
here's,
my
you
know,
I
want
you
to
run
a
proud
job.
That
does
the
test
that
I
want,
but
doesn't
you
know
actually
create
a
pull
request.
D
B
If
there
is
a
way
where
a
bunch
of
people,
you
know
maybe
like
the
gka
team,
doesn't
want
to
have
everybody
install
this
app?
Would
there
be
a
way
for
you
know,
either
the
community
to
host
something
for
the
community,
or
maybe
various
companies
in
the
community
to
sort
of
have
a
hosted
version,
or
is
that
sort
of
architectural
II
impossible
or
well.
B
D
B
E
D
Like
it
could
it
could
serve,
you
could
have
like
two
two
options
to
like
avoid
having
it
run
locally,
one
is
to
have
it
run
on
a
server
and
like
bring
in
the
files
from
a
server.
Just
as
it's
running
on
my
machine,
it
could
equally
run
on
any
server
right
and
have
the
local
repositories
just
there
on
the
server
on
the
machine.
That's
just
fine
and
another
option
is
to
upload
the
files
to
firebase
and
then
they're
available
there,
and
it
doesn't
need
any
get
reporting
like
once.
You
push
your
like
changes
to
review.
D
B
D
B
A
D
B
It's
really
important,
so
another
set
of
you
know
interesting
people
to
bring
this
to
and
potentially
find
champions
for.
The
project
would
be
contributor
experience
they
meet
slightly
earlier
than
this
on
Wednesday,
but
so
that
I
think
you
know
if
you're
up
for
doing
another
demo
I
think
that'd
be
a
good
set
of
people
to
demo
this,
oh
yeah
and
I'm.
So
I,
don't
know
a
question
I
had
you
know
like?
B
Does
anybody
else
have
a
feeling
for
the
you
know,
multi
repo,
like
the
multi
repo
aspect
of
this,
seems
pretty
unique,
and
you
know
if
they're
like
do
you
guys
see
that
this
would
be
their
domain
like
there's
demand
for
this
on
with
the
people
that
you
work
with
I.
C
Know
that
we've
had
they
use
several
scenarios
for
work
submitting
to
three
or
more
repos
within
the
kubernetes
community
in
order
to
get
a
particular
feature
across
the
line,
I
think
that
that
will
continue.
It
would
be
really
nice
to
have
a
place
where
this
is
this
concise
set
and
all
of
the
test
has
passed
and
all
of
the
repos
and
here's.
The
joint
discussion
around
that
I
see
immediate
use
for
me
and
I.
Think
Oh.
E
Offer
you
might
try
reaching
out
to
a
gentleman
named
Sam
Boyer
he's
prominent
in
the
NGO
community.
He
worked
on
a
tool
called
death,
forgo
dependency
management.
I
can
introduce
the
two
of
you
but
DEP
and
then
Matt
names
escaping
me
but
glide
before
they.
They
both
work
with
multiple
CM
providers
and
basically
cash
code
across
multiple
SCM
types
and
repositories,
and
it
may
be
a
way
to
provide
the
local
a
different
way
to
provide
the
the
local
viewport
and
to
the
data
in
a
way
that
also
could
work
remotely.
D
E
E
A
Look
I
guess,
jumping
back
to
one
point:
do
we
as
I
understood
it
like
at
some
point
all
the
staging
repos
like
they're,
obviously,
basically
a
mono
repo
right
now
with
the
ways
that
they're
synced
out
of
kaykai,
but
in
the
future
the
thought
was
the
fewer
head-to-head
dependencies
that
exists
between
repos
the
better
right,
whereas
this
tool
is
more
championing
the
mono
repo
approach
and
trying
to
help
developers
that
have
those
dependencies
does
that
work
with
the
future
direction?
There.
A
But,
as
my
understanding
was
like,
that's
not
the
goal
with
the
kubernetes
repos
and
like,
even
though
the
staging
repos
today
are
basically
a
mono
repo,
because
they're
synced
out
of
kaykai
the
future
would
like
that
not
to
be
the
case,
and
so
this
tool,
I
don't
know
it
seems
like
there's
a
push
to
have
more
separation
and
not
have
repost.
It
depends
on
each
other
right.
B
Yeah
I
mean
yeah,
I
mean
I,
think
that's
definitely
a
I,
don't
know
that
everybody
I
mean
that's.
Certainly
in
my
opinion
that
you
know
I
think
it's
better
to.
If
you
have
dependency,
you
know
if
a
projects
like
thing
a
and
B
has
dependencies
to
either
put
them
in
the
same
repo,
or
else
you
know
have
some
sort
of
way
of
upgrading
both
of
them
asynchronously
such
that
like
they
don't
need
to
merge
together.
B
A
B
Mean
I
I
would
suspect
we
would
try
and
figure
out.
You
know
a
way
to
avoid
that,
just
because
it
would
make
prowl
way
more
complicated
right.
You
know
it
sort
of
depends
on.
If
you
know
this
is
I
mean
it
still
could
be
helpful
right
like
if
I
have
a
and
B
and
they
are
in
separate
repos
and
I.
Am
you
know
making
a
PR
that
still
backwards-compatible?
B
It
still
might
be
useful
to
review
them
together,
even
if
they
are
merged
independently,
but
yeah
I
mean
you,
don't
I,
don't
think
that
you
know
this
I
mean
this
tool
would
be
the
only
thing
you
know
necessary
to
convince
us
that
making
prowl
you
know,
merge,
10,
repo,
uber
PR
would
be
a
good
thing
right.
A
Yeah
yeah,
reviewing
in
tandem,
seems
to
seem
super
useful
I,
just
wondering
getting
tests,
I
think
I
think
maybe
it
was
a
hippie
thing
like
it
would
be
nice
for
for
them
when
they're
landing
changes
across
PRS
to
have
that
test.
That
says
everything
works
together
and
I'm.
Just
not
sure
we
have
any
of
the
influenza
for
that
right
now,
but.