►
From YouTube: Kubernetes SIG CLI 20180606
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
good
morning,
good
afternoon,
good
evening,
it's
June
6,
and
this
is
our
bi-weekly
60
line
meeting.
My
name
is
machi
and
I'm.
The
organizer
of
today's
meeting
our
agenda
for
today
is
very
small,
honestly
there's
multiple
announcements
that
I
have
mostly
and
then
we
will
go
through
the
test
grid
and
I'll
recap.
The
discussion
that
I
had
before
with
with
Sean
with
regards
to
the
test
playbook,
so
the
most
important
part
is.
Let
me
share
my
screen.
First
of
all,.
A
Okay,
so
first
of
all,
code-free
started
yesterday,
which
means
there's
nothing
landing
in
cube
111
other
than
super
important
critical
bug
fixes.
So
if
you
are
pink
to
fix
it
back
or
you're
assigned
a
critical
bug
for
111,
please
make
sure
to
respond
as
soon
as
possible
and
help
the
sick
release
team
to
deliver
cube
111
by
the
end
of
by
the
end
of
June.
A
Additionally,
during
the
next
meeting
in
two
weeks,
which
will
be
June,
20
I
would
like
to
hold
two
items.
One
will
be
the
retrospective
for
111
and
the
other
one
will
be
planning
for
112.
The
reason
for
doing
the
planning
is
that
June
20,
if
I
remember
correctly,
is
also
the
date
when
the
bra
the
master
will
be
reopened
for
112.
So
if
you
have
anything
that
you
are
planning
to
work
on
for
112,
please
show
up
on
the
next
meeting.
I
would
like
to
create
a
small
document
so
that
we
have
the
information.
A
A
The
other
two
announcement
is
that
cube
con
china
call
for
proposals
closes
today.
So
if
you
are
planning
to
attend
the
China
Meetup,
it
will
be
sometime
in
August
feel
free.
You
don't
have
that
much
time,
but
you
still
have
a
chance
and
additionally
keep
Cuba
and
North
America
CFP
opened
and
it
is
a
and
you
have
time
till
August
12th
and
it
will
be
how
held
in
the
first
half
of
December.
A
Okay,
that's
basically
all
for
the
for
the
announcements.
Now,
let's
get
to
the
test
grid
out
for
the
past
two
weeks,
I
was
responsible
for
for
monitoring
the
test
grid.
There
were
three
major
events
during
that
time.
The
biggest
one
was
when
Ron
and
I
merged
folk.
Basically,
that
was
my
merge
when
we
merged
dropping
the
Reapers
that
was
last
Monday
and
that
cost
that
caused
significant
failures
and
the
cubes
ETL
tests,
which
I
fixed
along
the
way
it
looked
like
after
the
fixes,
which
landed
in
both
master
and
110
as
well.
A
The
Keuka
back
to
normal
there's
one
temporary
problem
with
skew
testers
that
who
unopened
last
week
while
I
was
out,
but
I
haven't
seen
this
thing
we
have
hearing.
So
maybe
that
was
connected
with
some
other
issues
and
currently
I've
noticed
that
gke
tests
are
failing.
That
includes
regular
Jiki,
Jiki
stereo
and
skew
tests
running
on
two
key
I've
open
an
issue
earlier
today,
and
it
looks
like
the
problem
is
with
G
key
itself,
because
the
system
cannot
set
up
the
instances.
A
So
that's
basically
it
shortly
earth
today,
I've
also
created
I've,
updated
the
unit
test
coverage
sheet
that
we
are
keeping
up-to-date.
It
looks
like
we
have
some
new
packages.
The
majority
of
packages
that
I've
noticed
did
not
change
significantly
I
think
there's
one
or
two
new
packs
of
packages
that
were
not
monitored
before
some
disappeared,
but
the
overall
status
is
basically
the
same.
A
A
The
majority
of
the
refactorings
landed
we've
created,
something
that
is
called
generic
CLI
options,
which
provides,
which
provides
a
tolling
for
for
commands
that
every
single
commands
can
now
use
in
a
unified
way.
That
includes
printing.
That
includes
creating
clients
from
configuration
options
as
well
as
helpers
for
record
we've
also
added
a
wait
command
that
is
probably
a
new
command
that
was,
that
has
been
awaited
for
quite
a
while.
A
We've
used
it
currently
for
as
a
replacement,
mostly
end
delete
command.
Since
we
get
rid
of
got
rid
of
the
Reapers
entirely
and
we
are
relying
on
the
server-side
deletion.
That
means
we
had.
We
need
to
wait
for
the
resource
to
be
removed,
to
maintain
the
backwards-compatibility
functionality
that
that
delete
command
had.
So
that's
definitely
something
worth
looking
at
aside
from
waiting
for
resource
to
be
deleted.
There
are
some
simple
conditions
that
you
can
use
to
wait
for
something
to
happen.
B
B
We
will
be
making
some
relatively
small
changes
to
coop
cuddle
itself
in
the
apply
to
add
a
server
side
apply
flag,
but
that
even
that
will
only
be
in
the
in
our
feature
branch.
So
it
you
won't
even
see
it
in
the
master
branch.
Most
of
the
work
is
being
done
in
a
feature:
branch
and
they're,
basically,
where
we
believe
we're
relatively
close
to
a
an
alpha,
a
very
simple
end-to-end,
where
the
coop
cuddle
will
be
able
to
talk
to
this
new
endpoint
and
do
a
basic,
merge.
A
Okay,
hearing
none
I
think,
like
I
said
we
can
close
the
meeting
with
this
thanks
very
much
that
was
very
helpful
and
short
I'll
send
out
a
an
email
to
the
6ui
mailing
list,
telling
people
that
the
next
meeting
in
two
weeks
on
June
20th,
we
will
be
holding
both
the
retro
and
planning
so
that
the
a
greater
amount
of
fuel
can
come
and
help
us
shape
the
cube
CTO
in
the
right
direction.
Thanks
very
much,
everyone
have
a
good
day
and
I'm,
giving
you
back
about
half
an
hour.
I'm
sorry.