►
From YouTube: Kubernetes SIG CLI 20180620
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
evening,
good
afternoon,
depending
on
where
you
are
it's
June
20th,
and
this
is
sick,
CLI
I'm,
your
host
I'm
at
a
we
have
the
agenda
pretty
packed
for
today.
There
are
two
main
topics
that
we
want
to
discuss,
which
is
the
retrospective
and
planning
for
112.
So
let's
get
this
thing
going
as
soon
as
possible,
quick
announcements,
the
master
for
112
has
been
opened
two
days
ago
in
at
least
my
afternoon,
5:00
p.m.
A
111
is
slowly
closing
if
you
got
pinked
for
a
for
a
buck
for
an
issue.
Please
reply
promptly
to
any
queries
or
issues.
If
you
find
about
that,
it
is
what
do
you
think
that
is
critical
and
should
be
in
111?
Then
please,
reach
out
to
the
sig
release
and
you'll
probably
have
to
open
a
PR
against
111
future
branch
and
have
a
fix
and
master
as
well.
That's
all
for
announcements.
The
test
grid
antwuan,
won't
be
able
to
make
it.
He
was
the
he
was
the
Deon
Cole
for
testing
for
the
past
two
weeks.
A
A
A
Okay,
so
I
don't
see
pirates
in
here,
so
I'll
just
take
over
the
responsibility
for
running
the
retro,
so
I've
copied
over.
This
is
the
110
and
this
will
be
111.
Retro
I'll
share
the
link
in
the
agenda
so
that
you
can
all
also
have
a
look
at
it.
But
so
the
first
item
is
a
quick
reminder.
This
is
a
non
bland,
full
type
of
a
communication.
We
are
not
trying
to
blame
or
shame
anything
or
anyone
we're
trying
to
improve
our
processes.
However,
things
was
done
in
111.
A
A
We
were
basing,
mostly
on
the
summer
emails
that
were
sent
out
to
the
entire
community
kubernetes
community.
Since
then,
we
set
up
the
uncle
row.
I
think
that
several
people
already
got
a
chance
to
to
play
the
role
during
our
last
call.
I
was
talking
with
Sean
about
doing
a
introduction,
video
for
the
on
call.
A
If
everything
goes
well,
we
will
do
one
during
our
next
meeting
so
that
the
the
PlayBook
that
that
was
created
by
Shawn
as
one
of
the
links
it
will
contain
that
particular
recording
of
our
meeting,
so
that
the
people
that
are
filling
in
the
role
for
the
first
time
will
know
how
to
use
the
tools,
what
to
look
and
where
to
look
these,
how
to
be
a
how
to
perform
the
uncle
role
properly.
The
other.
The
other
item
was
to
review
the
tests.
A
This
is
the
one
area
that
I've
discussed
several
times
during
cube
con
with
Phil
and
with
other
folks.
I've
talked
with
the
sig
testing
as
well.
During
kill
con.
They
sent
out
a
proposal
yesterday
with
the
testing
framework
with
documents.
They
are
currently
gathering
feedback.
I
haven't
read
through
it,
but
I'm,
hoping
that
we
will
be
slowly
able
to
improve
the
test
coverage.
Currently,
that
is
mostly
due
to
their
factorings
that
happen
in
111
and
will
continue
to
happen,
and
then
the
next
releases.
Okay.
B
A
Room
was
awesome,
yeah.
That's
awesome,
big
huge,
thank
you
to
every
single
person
that
fill
in
the
role
that's
already
signed
out
for
the
next
week's.
That
is.
That
is
amazing,
that
that
really
I
haven't
seen
our
sake
being
called
out
or
when
we
were
called
out.
It
was
always
already
taken
care
of.
That
is
just
amazing.
So
thank
you
to
every
single
person
doing
this
this
this
this
job.
It's
not
an
easy
one,
but
it's
definitely
worth
it.
B
On
that
same
note,
I'd
go
ahead
and
say:
we've
also
done
a
fairly
good
job.
With
regards
to
pretty
much
consolidating
all
of
the
CLI
pieces.
So
I
know,
we'd
have
several
goals
with
that,
one
of
them
being
to
split
them
out,
eventually,
but
I'd
say
in
general
I
the
CLI
has
been.
It
has
gone
through
major
cleanup,
I'd,
say.
A
Now
that
to
that
that
that
would
not
be
even
possible
with
some
significant
improvements
on
the
API
missionary
side
as
well.
A
lot
of
the
functionality
that
we
have
on
the
client
code
relies
on
the
API
machinery,
and
a
lot
has
been
improved
in
that
area
as
well.
So
that's
definitely
a
worth
worthwhile
improvement
on
their
side.
A
A
C
There's
there's
two
I
guess
interpretations
of
this
question.
The
first
is
like
what
are
issues
I,
guess
and
then
the
second
is
just
like:
how
can
we
like?
What
would
we
like
to
do
to
be
more
effective,
I
I,
don't
know,
there's
anything
I
mean
I,
don't
I,
don't
think
anything.
I
think
1.11
went
pretty
well
from
from
my
perspective,
but
maybe
there's
there's
some
ways.
We
can
get
more
creative
about
other
stuff.
A
Yeah
I
think
that
maybe
we
could
could
just
jump
to
the
next
question,
which
is
what
we
will
do
differently
for
112
and
Beyond
and
I
will
be
the
visibility,
and
this
will
be
the
discussion
for
112
items.
I
would
like
to
see
a
a
spreadsheet
that
will
be
linked
in
our
agenda
so
that
everyone
can
clearly
see
what
are
the
main
features.
I've
looked
for
the
features
that
were
extractors
from
their
futures,
repo
for
112
I've,
seen
there
one
was
around
server-side
printing
and
the
other
one
was.
A
Gypsy
do
this,
but
none
of
the
items
that
we
will
be
talking
about
in
a
moment
are
there,
so
that's
definitely
something
that
we
just
need
to
ensure
that
it
is
put
there.
Most
importantly,
we
have
a
spreadsheet
that
we
will
be
able
to
look
at
towards
the
end
of
112
release
and
say
how
good
we
are
with
our
plans
against
the
actual
execution.
B
C
C
C
One
thing
that
we
did
for
customize
was
build.
The
whole
thing
outside
of
coop
control.
I
was
like
kubernetes
Kedavra
Menace,
which
allowed
one
us
to
build
it
without
having
to
coordinate
with
the
main,
like
totally
decouple,
we're
doing
this
piece
of
work
from
whether
it
will
be
released
in
110
or
112
or
111
or
whatever.
C
It
is
in
get
customer
feedback
and
launch
it
and
have
folks
download
it
indefinitely
and
make
the
test
story
a
little
bit
simpler,
because
it's
not
tied
into
this
massive
test
suite,
but
instead
to
have
like
focused
unit
tests
on
it.
So
from
a
development
perspective
that
worked
pretty
well
in
in
112,
I
think
what
might
be
worth
exploring
is
taking
some
of
the
encapsulated
work,
such
as
the
dynamic
crate
and
dynamics
set
and
to
first
build
those
as
their
own
commands
in
their
own
repo.
B
C
They
just
notice
the
retro
is
the
retrospective
linked
in
the
notes.
It
is
not
I
haven't
shared
with
okay.
Anyone,
no
problem
I
just
want
any
advice
missing,
something
let's
say:
CLA,
oh
I'll,.
A
A
Okay,
I
think
we're
we're
pretty
good,
are
the
retro
so
thanks
anyone
I
think
we'll
we'll
just
continue
with
the
other
part
of
the
meeting.
That
is
probably
more
interesting
to
a
lot
of
us,
which
is
planning
I've
noticed
that
fail
you've
added
the
first
four
items,
so
you
want
to
walk
us
through
them
shortly.
C
C
So
the
first
two
items
are
really
about
continuing
the
trend
up:
moving
hard-coded
per
API
logic
out
of
the
client
towards
a
mechanism
that
will
work
with
version,
skewed
clients
and
also
work
with
extensions
such
as
CDs
or
or
our
unit.
Api's
machi
and
I
talked
a
bit
about
strategies
and
techniques
for
this
at
KU
Connie.
You-
and
this
is
also
been
discussed
quite
a
bit
in
the
past,
but
I
could
kind
of
you
kind
of
where
we
both
the
approach.
C
We
both
felt
pretty
good
about,
was
a
I
sort
of
pseudo
template
based
approach,
but
data-driven,
so
you
can
attach
data
to
CR
DS,
for
instance,
and
then
use
that
to
drive
the
creation
insect
commands.
Rather,
we
talked
about
crate
to
start
there
and
then
committing
on
out
how
that
goes.
Explore
if
set
would
also
be
possibility.
C
C
And
then,
lastly,
getting
customized
available
as
an
app
command
in
control,
we're
getting
having
a
number
of
folks
using
this
surprisingly.
Actually,
a
lot
of
folks
are
using
it
as
library
too,
but
this
is
will
resolve
a
number
of
coop
control
issues,
and
so
the
next
logical
step
would
be
to
put
it
as
an
alpha
command
and
get
make
it
available
to
users
that
way,
and
that
will
also
doing
so
will
also
kind
of
flesh
out
that
first
end
end
process
for
can
we
take
a
feature,
develop
it
outside
the
core
prototype?
A
A
So
we
will
definitely
continue
to
those
refactoring,
because
the
end
goal
of
all
of
those
refactoring
is
to
be
able
to
extract
cubes
ETL
to
its
own
repo,
so
that
this
can
move
a
lot
faster
than
the
kubernetes
itself,
as
a
continuation
of
that
word
will
be
a
common
library,
the
printing
methods
and
a
couple.
Others
we've
managed
to
encapsulate
those
in
a
single
package.
A
So
far,
we
would
like
to
start
the
process
of
extracting
these
common
functionalities
to
a
library
we
will
start
as
a
staging
repo
inside
of
kubernetes
and
at
some
point
in
time
we
will
be
publishing
that
as
a
separate
repository,
so
that
people
who
are
writing
their
own
plugins,
your
own
cube
CTL
like
CL
eyes.
So
all
of
them
can
easily
consume
those
bits
using
that
particle
library
and
provide
the
same
functionality
in
a
similar
manner.
That
of
cubes
ETL
does
and
then
continuing
on
the
topic.
A
The
plugins
we've
had
numerous
discussion
during
the
cube
con
we've
been
bringing
the
topic
of
plugins
and
cube
CTO
during
our
previous
meeting
several
times,
we're
trying
to
gather
all
those
expectations
and
the
feedback
that
we
got
hurt
and
hopefully
in
112,
we'll
be
able
to
put
together
a
proper
plugin
solution.
And
finally,
as
you
probably
all
know,
we
were
able
to
implement
the
server-side
printing
so
that
the
printing
functionality
is
currently
driven
by
the
server.
A
So
in
111,
we've
enabled
the
server-side
print
by
default
in
gypsy
deal,
but
there
are
still
some
deficiencies
in
this
mechanism
like,
for
example,
sorting
we've
been
discussing
the
sorting
on
one
of
our
previous
meetings.
If
you
scroll
through
the
notes,
you'll
be
able
to
easily
find
that
the
notes
from
that
discussion.
So
there
are
some
steps
required
to
finish
a
proper
server-side
panning
in
the
cube,
CDL
wiring,
and
that's
that's
basically
it
both
one
and
I
will
be
working
on
four
of
those
interchangeably.
So
I
think
that's
that's.
B
So
really
quickly,
something
I'd
go
ahead
and
say
as
well
as
well.
The
plan
right
now
is
to
basically
tie
in
the
common
library
containing
Kineret
CLI
options
with
plugins
in
the
future.
It'd
be
nice
to
we'll
think
of
a
way
to
entice
people,
entice,
plug-in
authors
in
the
future
to
use
this
library.
So,
while
the
plan
is,
you
know,
we'll
use
it
ourselves
put
it,
it
would
also
be
nice
if
we
could
highly
entice
people
that
write
plugins
to
also
make
use
of
it.
B
A
A
D
D
D
The
I
had
heard
that
the
community
meeting
or
the
meetings
that
happen
in
previous
cute
cons
may
not
happen
this
time
through
hallway
conversation
here.
So
so,
if
we
want
even
more
face-to-face
time
as
a
cig,
let's
consider
showing
up
a
day
early
I
think
most
people
show
up
a
day
early
anyway
and
get
together
for
a
few
hours
to
do
some
deep
planning.
A
I'm
not
sure
how
they
are
planning
with
it
with
this
cube
Cod.
But
what
proved
very
well
in
in
in
Europe
over
a
month
ago
was
that
the
first
day
before
Cuba
itself
began
was
there
was
a
core
developers
meet
up.
I
can
remember
was
what
was
the
name
of
that
meeting
and
only
the
core
developers
for
the
majority
of
the
bits
for
cube
where
prisoner
and
Phil
and
I,
we
spent
a
decent
amount
of
time
talking
with
each
other
about
cubes.
Etl
I've
also
been
quite
amount
of
that
quite
significant
amount
of
time.
A
Talking
with
the
sig
apps
over
there
I
think
yeah,
definitely
the
day
before
I
think
they
will
be
planning
to
something
some
some
kind
of
a
engagement
for
the
Chordettes,
so
I'm,
hoping
that
this
will
be
the
exact
time
where,
where
each
of
us
will
be
able
to
spend
some
face
time
together
and
discuss,
all
of
that
is
required.
That.
A
Yeah
totally
totally
totally
support
that
one
I
had
one
more
thing
that
I
want
to
bring
up
for
1:12
planning.
Please
ensure
that
every
single
of
these
items
that
we
have
in
here
has
a
future
issue
opened.
If
there
is
one
already,
please
link
it.
If
there's
none,
please
open
any
one
and
put
a
link
in
here,
so
that
we
have
a
place
where
to
go
and
so
that
they
learn
properly
in
the
overall
kubernetes
future
planning
spreadsheets
that
there
is,
that
is
generated.
Okay
Sean.
Would
you
be
willing
to.
C
A
D
A
Well,
thanks
I
know
I
July
4th
I.
If
I
remember
correctly,
that's
a
holiday
in
the
u.s..
Yes
I
think
that's
that's
reasonable
to
just
skip
that
meeting
in
that
case,
because
in
that
case,
I
would
be
just
me
I'm,
not
sure
whether
we're
fan
is
being
based,
but
is
easy.
All
of
you
will
be
yeah,
so
so
yeah.
That
will
be
just
me
in
that
case.
D
C
I
think
we
need
to
this
is
kind
of
something
we're
experimenting
with
and
I.
Don't
I'm
not
aware
of
anyone
else
doing
this
sort
of
approach.
I
think
we
probably
want
to
approach
it
as
if
we
are
developing
them
as
kubernetes
features.
Okay,
you
know
efficiency
benefits
of
development,
but
our
intention
I
think,
is
to
get
these
features
into
one
twelve
coop
control
as
as
ups
then
either
then
during
the
code
or
coming
up
with
some
other
mechanism
to
be
determined
got
it.
A
Yeah
well
sang
Sean
with
regards,
because
if
you,
if
you're
gonna
be
out,
then
then
we
just
need
to
figure
out
how
to
ensure
within
the
next
two
weeks,
so
that
this
is
linked
to
the
proper
issues.
I'll
be
gone
after
for
for
two
weeks
as
well,
so
cool
I,
don't
think
we
have
any
stand-ups
because
of
the
code.
Freeze,
I,
don't
think
that
too
much
has
been
happening
mostly
mostly
I.
Think
a
lot
has
happened
around
stabilizing
111
so
that
it
is
open
unless
I'm,
wrong
and
I
feel
free
to
to
prove
me
wrong.
A
D
D
A
Think
we
filled
in
our
time
slots
pretty
good,
pretty
good.
Does
anyone
have
does
they
want
to
else,
have
anything
else
to
add
with
regards
to
either
retro
or
planning
or
QTL
itself,
or
our
meetings
overall
I.
C
A
Yeah
actually
Thea
the
versions
queue
is
something
that
we
should
probably
improve,
and
I
will
make
a
very
nice
action
item
in
our
retro
I'm
gonna.
Add
it
over
there
right
after
this
meeting
that
we
should
improve
the
versions,
keep
that's,
maybe
a
little
bit
yeah
I
waited
small
steps.
That's
I
think
that's
something
reasonable
to
have,
especially
when,
at
some
point
of
time
we
will
have
our
own
keep
CTL
repo,
and
then
it
will
be
super
crucial
that
we
don't.
A
A
Okay,
I'll
send
one
another
email,
reminding
that
we
cancelled
the
meeting
in
two
weeks
because
of
the
u.s.
holidays,
and,
if
that's
all,
thank
you
very
much.
That
was
a
very
fruitful
meeting
for
myself
and
I
hope
for
how,
for
all
of
you
as
well,
I'll
ensure
to
put
up
the
recording
and
I'll
synch
with
you
Sean
about
the
linking
the
features
thanks
very
much
folks
and
see
you
soon.
In
that
case,
bye.