►
From YouTube: Kubernetes SIG Testing 2019-09-10
Description
A
Sorry
to
be
a
bit
late,
we
have
the
agenda
for
today's
tea
in
the
invite
and,
yes,
she
is
start
by
introducing
any
new
participants
to
the
call
for
those
who
don't
know
me:
I
am
amiko
Aragon
I
work
for
Aaron
who's,
co-founder
and
chair
for
seek
testing
and
very
happy
to
be
here.
They
see
Alvaro
on
the
call
and
Catherine
feel
like
I
know
a
lot
of
people
on
the
call,
except
for
Cynthia
and
my
yak,
you
like
to
introduce
yourselves.
B
B
B
C
Hi,
my
name
is
Santa
and
I
work
for
our
mesosphere.
We
just
currently
now
tallest
did
like
you,
I
user
of
copernicus
and
I
am
the
Takeda
atmosphere
for
the
developer
productivity
department
and
I
kind
of
like
use
data,
central
repo
and
and
set
up
the
prowl
instance
and
the
set
of
the
kubernetes
workflow
for
our
projects
internally
and
I
handled
it.
The
kubernetes
slack,
sometimes
asking
questions
and
then
I
think
I
must
have
had
some
Piazza
against
it
too.
A
A
A
D
No
dates
on
testing
comments.
We
actually
have
a
we
actually
haven't
met
or
a
for
a
couple
of
weeks,
a
one
because
I'll
be
enrolled
and
then
because
of
a
holiday,
a
holiday
in
the
US
and
right
now,
the
big
party
they
made
a
big
bearable,
work
refactoring,
they
tested
the
test
framework,
a
it's
on
hold
a
until
daybreak
until
the
master
branch
of
communities.
It's
open
so
really
nothing
to
update.
A
A
A
E
I
didn't
realize
this
was
on
the
agenda,
so
we've
released
0.5
and
then
0.5
point
one
which
was
a
small
patch
fixing
windows
and
we've
done
a
lot
of
work
on
error,
reporting
and
debug
logging
to
make
it
easier
to
figure
out
why
it's
not
working
in
strange
environments
and
we're
hopefully
going
to
be
shipping
a
number
of
those
improvements
in
the
next
release
which
is
pending
and
about
a
week
or
so.
But
we
might
push
it
back
to
shore
them
up
a
little
bit
more.
A
F
It's
just
some
some
notes
that
I'll
turn
into
a
design
dog
it's
halfway
to
design
doc
already
though,
but
it's
just
about
adding
some
tips,
some
generalized
tooling,
that
we
can
use
between
all
the
different
parameters
for
updating
and
deploying
prowl
itself
right
now,
there's
a
lot
of
bespoke
stuff.
That's
out
there
and
it'd
be
nice
to
provide
that
bundled
with
pro.
F
It's
the
idea
is
to
kind
of
get
a
lot
of
the
experience
that
we
have
for
the
main
kubernetes
Pro
instance
available
for
other
instances,
there's
some
things
that
the
kubernetes
Pro
instance
will
need
to
do
that.
Other
instances
won't
such
as
like,
actually
publishing
images
and
stuff
like
that.
So
this
tooling
is
more
meant
for
other,
proud
senses.
F
For
that
will
actually
deploy
whenever
those
employment
files
are
changed,
so
that's
an
easy
way
to
define
the
state
of
your
cluster
and
get
and
had
all
of
that
control
the
Kitab
so
I
assume
a
lot
of
people
are
already
following
this,
but
they're
probably
running
a
you
know
letting
tied,
merge
their
merge,
their
changes
and
then
running
a
make
file.
Data
ploy,
or
something
like
that.
This
makes
it
all
possible
to
do
through
github.
F
There's
a
couple
questions
that
it
can
be
hard
about
this,
though,
which
is
in
particular,
which
version
do
we
update
to
like?
How
do
we
pick
a
version
tag
you'd
think
we
just
want
to
pick
the
latest,
like
version
that's
available,
but
unfortunately
that's
not
necessarily
a
stable
version
like
we
haven't
necessarily
tested
that
version.
Of
course
past
you
know
all
the
code
past
pre
submits,
but
we
haven't.
We
haven't
necessarily
had
a
real
pro
instance
use
it.
F
So
it's
better
to
bump
to
versions
that
we
have
run
the
the
kubernetes
prowess
and
so
on
and
validated
a
little
bit
right
now,
there's
not
really
an
easy
way
to
determine
what
that
is,
though,
digging
through
the
git
history,
so
I
think
at
the
bottom
of
this
document.
There's
also
a
discussion
about
taking
staple
versions.
F
That
would
make
it
so
that
it's
always
safe
for
their
to
bump
to
any
image
version
in
that
repo
and
I
think
that
I've
got
some
ideas
about
some
tooling
that
we
can
do
to
automate
that
so
similar
to
the
auto
bump
job.
We
would
just
have
to
approve
a
PR
if,
if
the
the
previous
version
was
stable
and
if
it
is,
then
it
would
automatically
get
tagged
so
no
scripts
that
anybody
has
to
run.
A
A
F
Just
notes
right
now:
I'm
really
turned
into
a
full
design
doc.
Yet
but
I'd
like
I'm,
just
getting
people's
opinions
and
then
then
I'll,
maybe
a
improve
it
a
little
bit
and
or
at
least
add
my
my
actual
proposal.
There
I've
done
a
little
initial
work.
I
think
this
is
gonna,
be
pretty
straightforward
and
like
the
right
approach,
but
I
just
wanted.
If
anybody's
got
any
better
ideas,
some
ways
to
do
things.
That
would
certainly
be
great
to
hear
about
now.