►
From YouTube: Kubernetes SIG CLI 20180411
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).
B
Everyone
I
feel
it
feels
like
yesterday
that
I
was
just
here
doing
a
contributor
experience,
update,
I'm,
actually
including
it
being
linked
to
the
retrospective
document,
both
in
the
saiga
gender,
as
well
as
the
zoom
chat.
This
is
going
to
be
a
much
a
much
shorter
version
of
our
1.10
community
release.
This
is
just
some
things
that
like
to
do
retros
on
their
own
features
and
work,
and
things
like
that.
So
it's
really
good.
Oh
actually,
let
me
turn
my
notifications
off
here
too.
So
you
don't
hear
those.
B
B
Obviously,
if
there's
not
many
other
folks
speaking
just
speak
up,
but
if
there
are
quite
a
few
folks
speaking
just
on
the
retrospective
document
go
in
there
and
make
make
a
note
under
a
bullet
that
you
have
a
talk
topic
and
your
name
so
that
we
can
call
on
you
if
you
have
something
to
say
but
do
not
want
to
either
pose
as
publicly
or
but
rather
have
me
say
it
on
your
behalf.
Anonymously
feel
free
to
reach
out
to
me
and
zoom
chat.
This
should
not
be
us
putting
blame
on
any
one
individual.
B
B
All
right
so,
first
things,
first
typically
in
a
normal
retro,
we
would
go
back
to
the
action
items
that
we've
collected
from
the
last
retro,
since
this
is
my
first
retro
with
you
all
I'm,
not
sure
if
you
had
one
for
1.9,
so
we're
actually
gonna
go
ahead
and
skip
that
part.
If
you
feel
like
there
was
discussions
about
1.9
either
we
did
do
or
you
where
we
did
not
hit
just
go
ahead
and
populate
this,
and
this
document
will
also
be
circulated
at
some
point
this
week.
B
A
Think
the
implementation
of
the
service
are
printing
went
very
well,
so
I
would
like
to
call
out
Clayton
and
Huan
for
driving
the
majority
of
the
work
for
for
that
feature,
we
didn't
have
any
problems,
major
problems
with
the
feature
it
went
pretty
smoothly.
So
I
think
that'll
be
my
point
for
our
well
well
in
1.10.
B
B
A
B
How
do
you
think
that,
so
just
to
follow
up
with
this,
like
as
an
action?
What
do
you
feel
like?
Oh
not
what
do
you
really?
What
what
do
you
feel?
How
do
you
feel
like
this
could
be
worked
on
for
improvement?
Is
there
something
that
you
can
work
on
with
the
release
team
to
be
better
as
there
an
internal
process
that
we
can
build,
it
might
make
things
a
little
bit
easier
on
flakes.
A
So
definitely
the
emails
that
are
being
sent
out,
I,
think
weekly
or
every
other
week
for
flakes
and
the
six
which
are
owning
them.
This
is
definitely
something
that
is
very
valuable
for
me
as
a
cig
lead.
It's
easy
for
me
to
figure
out.
Are
there
any
flakes
because
I'm
personally
not
actively
monitoring
all
the
flakes
and
such
a
summary?
A
But
I
can
remember
sorry
the
name
of
the
person
that
is
sending
out
those
emails,
but
she's
monitoring
those
very
frequently
and
ensuring
that
the
flakes,
if
they
do
pop
up
appropriate
six,
are
being
called
out
and
the
quantities
that
male
English.
So
that's
definitely
something
that
helps
to
improve
and
limit
the
number
of
lakes
and
ensure
that
the
the
six,
including
six
Eli,
is
capable
of
responding
to
the
place.
C
A
From
the
multiple
reviews
that
I've
been
doing
over
the
several
past
weeks
and
months,
I've
noticed
that
there
are,
there
are
significant
amount
of
tests
that
are
not
good
enough
for
testing
the
functionality
behind
them.
So
all
of
us
should
be
more
careful
about
improving
the
quality
of
the
tests,
whichever
better
functionality
we're
touching
within
the
the
scope
of
our
cig.
B
B
That's
good,
that's
really
good,
to
hear
all
right
last
call
for
what
could
have
gone
better
and
again.
We
don't
necessarily
need
to
add
these
now
that
you
can
take
some
time
this
week
and
add
these
they'll
be
attached
to
your
agenda.
I
know
for
the
community
of
release
retrospective.
We
definitely
had
folks
at
in
for
the
fact-
and
folks
are
actually
still
reviewing
that
document
and
it's
going
to
be
under
review
and
saying
release.
So
these
documents
are
getting
digested
so
definitely
feel
free
to
use.
You
know
Dad
value
titties
for
the
project.
B
Okay,
let's
go
ahead
and
move
on
then
to
the
last
item.
What
can
we
do
differently
for
1.10
and
beyond?
This
is
really
our
actions
here
and,
and
so
far
what
I've
collected
is
paying
attention
to
the
the
ke
dev
emails,
the
summaries
and
then
also
possibly
set
up
a
rotation
for
triage
to
improve
flake
the
flake
situation
and
also
review
tests
and
look
for
areas
of
improvement.
B
B
A
You
very
much
Paris
I,
think
that
that
we
will
be
able
to
earning
from
this
release
to
ensure
that
we
are
doing
the
retrospective
on
every
single
after
every
single
release,
and
then
we
can
be
able
to
improve
the
quality
of
the
sick,
CLI,
stuff,
yeah.
A
A
Okay,
with
the
retrospective
done,
we
can
now
focus
on
the
other
two
bits.
I've
noted
two
stuff,
but
I'll
probably
go
ahead
and
add
one
another.
The
Mende
proposed
is
the
flag
rotation
topic,
so
we
will
definitely
I
would
like
to
discuss
this
topic
with
the
rest
of
the
group.
So
first
maybe
ng
you've
added
to
you
the
topic
of
creating
communities,
six
client
lips,
reporters
last
time.
Yes,
can
you
walk
us
through?
Oh.
C
C
A
I
totally
support
this
idea,
but
before
we
will
be
able
to
do
that,
there
are
several
problems
that
we
have
the
first
and
the
biggest
problem
is,
and
I'd
actually
pointed
it
out
and
as
one
of
the
future
topics
that
I
wanted
to
burn
up.
Is
the
kubernetes
/
cube
CTL
repo
that
we
have
that
repo
was
meant
to
be
just
the
thing
that
you're
talking
about
a
common
set
of
functionality?
That
will
be
first
and
most
importantly,
you've
entered
in
kubernetes
and
used
inside
of
kubernetes
for
building
the
cube,
CTL
command.
A
The
printers
is
going
in
exactly
that
direction,
to
be
able
to
extract
some
common
functionality
in
a
library
that
will
be
then
usable
by
other
way,
other
way,
other
community
members
and
and
actually
the
the
part
about
publishing
the
repo
is
I.
Think
the
the
smallest
problems
that
we
have,
because
I
can
talk
to
Stefan
and
that's
as
simple
as
just
adding
additional
configuration
options
for
further
communities
for
keeps
ETL
related
bids
that
we
want
to
have
in
the
staging
grade
book.
A
This
basically
goes
all
the
way
to
discussion
that
we
had
for
good
couple
months
before
when
we
try
to
extract
the
entire
cube
CTL
outside
of
communities.
Repo,
this
basically
goes
all
the
way
to
that.
There's
a
lot
of
work
needed
to
to
be
performed
upfront
before
we
will
be
able
to
extract
that
bit
out.
Does
that
make
sense
to.
C
You
yes
make
sense,
so
you
know
that
extracting
to
extract
all
the
community,
all
the
cue
cuddle
code
out
it's
hard
made
or
caught
her
to
do
that,
and
so
before
that
happen
we,
so
we
cannot
have
some
code
that
it's
not
under
the
staging,
because
there,
if
there's
some
code
that
is
not
under
staging
we,
this
can
be
important
group.
Yes,
oh
I,.
A
Think
David
mentioned
David
each
mentioned
that
several
meetings
ago
and
that
we
can
slowly
start
fighting
this
split
by
adding
stuff
to
the
staging
group
Oh
as
soon
as
they
are
in
a
reasonable
way
to
be
separated
out
of
the
cube
CDL.
So
with
slow
steps
we
will
be
building
our
staging
repo
and
once
we
are
happy
with
the
shape
of
the
actual
web
libraries
in
that
staging
repo,
we
will
be
then
able
to
publish
those
for
consumption
by
other
users.
I
think
that
there
could
be
the
the
simplest
approach
for
for
this.
C
A
C
Yeah
bad
another
comments
related
to
this
is
so
that
ripple,
which
is
mirror
from
the
staging
I
think
it
should
be
completely
managed
by
the
publishing,
but
in
other
words,
humor
should
not
directly
contribute
to
that.
So
I
don't
want
to
see
a
ripple
that
it's
a
half
managed
by
about
half
managed
by
the
human.
That's
it's
not
the
state.
No.
A
No,
what
I
meant
is
by
staging
I
mean
that
we
will
be
moving
the
bits
into
the
staging
under
kubernetes
repo
just
to
ensure
that
whatever
we
move
to
the
staging
under
staging
directory
in
kubernetes
repo,
that
these
bits
are
not
being
used
in
in
in
any
other
bits
of
kubernetes,
so
that
we
have
problems
when
using
so
and
once
we
are
happy
with
the
contents
of
that
staging
directory.
Only
then
we
will
be
able
to
turn
on
the
publishing,
but
the
publishing
bit
will
always
be
fully
automatic.
There
is
no
human
involved
in
it.
A
That's
what
I
meant
with
the
the
staging,
the
staging
as
the
directory
being
the
entry
point
for
the
actual
publication
of
the
libraries
for
the
cube
CTL
stuff
this.
Actually,
this
will
be
also
important
and
I
would
even
say
crucial
for
the
plug-in
authors,
because
once
we
have
the
framework
for
building
the
plugins,
we
would
like
them
to
reuse
as
much
of
the
function
that
we
already
have
and
keep
CTL
in
their
own
plugins.
A
A
Then
a
any
comment
author
will
be
responsible
for
just
using
this
structure
as
one
of
the
options
elements
in
this
truck
for
every
command
and
then
just
invoke
printer
method,
which
will
return
an
appropriate
printer
that
the
user
requested.
This
is
to
simplify
and
unify
the
user
experience
for
printing
the
objects
with
cube,
CDL
commands,
and
additionally,
on
top
of
that,
we
would
like
to
be
able
to
do
exactly
the
same
thing
with
flags.
A
D
D
They
basically
instruct
and
not
a
story
about
which
flags
go
with
particular
functionality.
So
I
guess
I
would
encapsulate
all
of
this
as
we
plan
on
taking
common
functionality
across
the
codebase
and
for
each
for
each
set
of
set
of
flights
that
provide
one
common
functionality.
Those
are
groups
on
your
trip.
A
A
Well
aside
from
that,
the
fact
that
we
need
to
improve
and
I'll
be
actually
but
I'll
leave
it
for
the
next
time
in
two
weeks,
the
testing
guide
for
for
the
cube
CTL,
but
that's
probably
a
bigger
topic
that
I
would
like
to
cover
the
next
time,
but
we
can
start
with
trying
to
figure
out
how
the
yong-chol
rotation
would
look
like
and
maybe
we'll
create
the
initial
list
for
for
dealing
with
those
Wendy.
Do
you
have
any
ideas
how
we
could
start
implementing
those?
A
The
current
the
current
approach
that
I'm
taking
is
that
whenever
there
is
the
cube
that
email
about
snakes,
I'm
looking
for
6e
ally
and
either
I'm
reaching
out
last
time,
I
was
talking
with
you,
because
I've
noticed
that
you
were
pink
on
the
issues
and
I
was
also
talking
to
I.
I
can't
remember
her
name,
she
was
dealing
with
those
snakes
and
eventually,
as
a
continuation,
also
picked
up
some
further
fixes
to
the
sorry
to
the
issue
so
that
we
can
able
to.
A
C
A
If
you
find,
if
you
find
the
link,
it
would
be
nice
to
include
it
into
it
into
the
agenda,
the
other.
The
other
idea
that
I
have
is.
It
would
be
good
to
sync,
with
the
other
six,
that
price
mentioned
that
are
either
discussing,
or
maybe
they
already
implemented
the
idea
of
having
the
the
uncle
rotation
for
the
tests
and
and
see
how
they
approach
the
topic,
and
maybe
you
know,
cooperate
with
them
because
maybe
they
already
have
those
the
software
for
them
implemented.
A
A
And
she
mentioned
cig
apps,
but
unfortunately,
Matt
Farina,
who
was
present
earlier,
left
some
some
time
mid,
true
somewhere
in
there
in
the
in
the
middle
of
the
meeting.
So
I
can
personally
try
to
pink
Matt
and
she
and
try
to
figure
out
what
what
they
are
using,
how
they
are
using
it
or
what
are
the
the
progress
that
they
are
making
on
this
topic
and
will
well,
hopefully
will
slowly
try
to
divide
the
problem.
A
A
D
We're
basically
starting
to
work
with
printers
by
first
merging
all
the
older
flags,
with
all
the
flights
trucks
that
we
plan
on
having.
So
those
include
a
sync
single
structure
for
each
printer
type,
that
they've
identified
so
one
for
human
readable,
one
for
name
and
success:
printing,
another
for
Jason
and
llamó,
another
for
template,
printing
and
the
last
one
for
custom
columns.
So
now
that
we
have
those
five
structures
merged,
what
we're
working
on
now
is
basically
wiring
those
structures
at
the
command
level.
D
So
the
ongoing
work
basically
aims
to
no
longer
use
this
flow,
but
rather
have
each
command
instantiate
a
flag,
its
structure
and
essentially
use
the
flag
structure
to
bind
all
the
flags
and
then
obtain
a
printer
from
that
as
well.
So
right
now,
we've
tackled
all
the
such
commands.
All
the
sections
are
currently
using
this
this
pattern.
D
D
So
a
side
goal
of
this
work
would
be
to
define
what
kind
of
output
we
should
and
should
not
expect
from
commands.
So
the
ideal
situation
would
be
to
isolate
human
readable
output
to
the
gate
command.
You
know
potentially
looking
to
having
maybe
template
output,
a
sort
of
create
and
set
commands
so
right
now
they
only
support.
D
You
know
success
printing
and
KCMO
printing,
as
you
expect,
but
in
some
tests
some
tests
actually
made
use
template
printings
of
your
looking
into
it
as
well,
so
that
the
main
goal
is
to
once
we
have
the
printers
wired
basically
have
groups
of
these
structures,
depending
on
which
commands
are
using
them.
So
if
we
are
dealing
with
the
gate
command,
the
gate
command
would
have
a
struct
that
composes
only
the
structures
containing
the
flights
that
get
needs,
such
as
the
human
readable
bits,
the
jason
yellow
bids,
the
temporary
cousin
home
bits
and
then
procreate.
D
D
A
Okay,
hearing
none
I
think
we
covered
all
the
topics
that
we
had
for
today
and
I.
Think
I'm
gonna
give
you
back
the
ten
minutes
of
the
original
time,
especially
that
the
last
time
we
we
were
over
time
by
at
least
10
or
15
minutes.
So
thank
you
very
much
everyone
for
joining
the
call
and
see
you
all
in
two
weeks.