►
From YouTube: Kubernetes SIG CLI Meeting (07/17/2019)
Description
Kubernetes SIG CLI bi-weekly meeting on 07/17/2019, hosted by SIG CLI co-chair Sean Sullivan.
A
Cloud:
okay,
so
there's
there's
just
one
announcement
that
I
that
I
put
into
the
notes,
which
is
we
plan
on
having
a
sig
CLI
face
to
face.
This
is
one
of
the
few
times
per
year,
which
the
six
CLI
actually
is
able
to
get
together,
and
this
is
going
to
be
at
coop
con
North
America.
It's
it's
all
the
way
in
November
November
18th
through
the
21st
in
San
Diego.
We
just
want
to
mention
this
us
in
case
people
need
to
plan
very
far
in
advance.
A
C
Yeah
so
I'm
Cornelius
said
I'm
active
on
the
crew
project.
Right
now
also
contributed
to
scaffold
a
little
and
yeah
so
my
biggest
achievements.
So
far,
our
integration
tests
for
crew
and
yeah,
the
big
things
on
the
horizon
now
is
getting
moti
index
mode
index,
feature
and
crew,
so
that
there's
some
only
the
centralized
index
but
several
indices.
D
A
A
A
A
B
I'm
still
here
so
as
I
said
I
here,
basically,
what
I'm
seeking
to
get
out
of
this
is
to,
if
you
can,
you
know,
go
to
Google
today
and
search
IQ
CTL
plugins,
you're
gonna,
learn
to
terrains,
that
I
have
a
communication
and
what
I
believe
to
is
add
a
document
section
in
there.
Please,
if
you're,
considering
to
write
a
plugin,
please
consider
packaging
for
crew,
because
it
gives
you
these.
You
know
it
benefits
over
packaging
it
with
like
apps
or
hombre,
or
something
like
that.
B
So
these
are
the
main
reasons
that
I'm
trying
to
do
that.
The
reason
I'm
asking
for
permission
is
because
the
project
is,
you
know
just
a
little
bit
early.
It's
not
super
stable
they're
moving
a
lot
of
things
here
and
there
like
we're,
trying
not
to
break
users,
involve
us
as
much,
but
we
are
doing
that.
Sometimes
still
so,
it's
like
still
0.2,
so
I
wasn't
exactly
sure
whether
it's
okay,
I
haven't
seen
a
lot
of
examples
of
like
some
projects
you
know
being
mentioned
in
the
actual
documentation.
So
what.
D
A
F
Think
it
makes
sense
to
tell
people
make
people
aware
of
the
benefits
of
packaging
with
crew.
We
should
probably
we
can
cover
this
in
their.
You
know
review,
but
we
should
probably
just
make
sure
that
we
accurately
represent
the
maturity
of
crew
and
like
whatever,
if
there's
any
reason
they
wouldn't
use
crew.
Just
make
sure
we
include
that
as
well,
so
folks
know
rather
make
sure.
Maybe
it
makes
sense
to
say
that
this
is
our
preferred
approach.
We
recommend,
but
also
let
people
know
like
how
to
determine
what
the
right
solution
is
for
them.
B
B
Think
there's
a
pair
out
there,
fixing
it
right
now
like
instead
of
using
execs
installs
that
are
planning
to
you
like
pork,
so,
like
the
plug-in
will
run
it's
a
sub
process
and
sort
of
replacing
personnel.
I
think
that
PR
was
merged.
I
I
haven't
been
following:
I
think
it
was
merged,
but
I'm
not
sure
if
it
made
it
totally
said.
Okay.
F
F
We
watch
and
I
discussed
also
having
like
a
sexy.
Oh
I,
authored,
plug-in
group
that
maybe
we
want
to
a
functionality
that
we
would
consider
shipping
with
coop
control,
but
you
know
haven't
packaged
them
together.
Yet
because
of
you
know
the
maturity
level
or
other
reasons
so
that
that
I
don't
know
if
that's
related
to
this,
but.
B
I
guess
sort
of
there
are
other
sub
projects
like,
for
example,
nginx
ingress.
Another
Korean
sub
project
was
using
actually
crew
today,
so
like
they're,
relying
on
it
as
a
primary
installation
method,
so
I
would
say
like
there's
a
bit
of
acceptance
out
there,
but
we're
not
quite
where
we
want
to
be
I
mean
plays
our
genes,
so
I
don't
know.
We
want
to
treat
it
despite.
F
Okay,
that
makes
sense
yeah.
That's
interesting,
though,
about
the
nginx
thing.
Maybe
a
follow-up
thing
then
would
to
be
to
make
like
a
hub
for
the
project
own
plugins
for
various
days,
so
each
sake
can
publish
there.
We
have
a
list
of
the
repos
or
plugins
for
each
of
the
legs
and
and
have
them
distributed
through
crew.
Yeah.
B
I
feel
like
we
should
probably
like
the
project.
We
should
come,
give
more
stand-ups
because
there's
been
some
developments
going
on
and
like
some
new
plugins
coming
in
that
are
some
one
significant.
There
is
interest
within
Google
to
actually
like
and
finally
interested
in
Google
to
also
distribute
through
CTL
plugins
for
various
projects
that
are
not
really
yet
so
I'll
loop,
some
of
the
Gruber's
in
there
as
well
I,
feel
like
the
plugins
will
be
like
adopt
a
more
and
more
so
you
can
go
to
Mission,
Tom
and
I
think
we
should
come
yeah.
F
B
A
C
So
what
we
were
trying
to
achieve
was
to
get
some
criteria
that
will
help
us
to
make
an
objective
and
not
such
a
subjective
decision
to
as
to
whether
those
plugins
should
go
into
the
centralized
index
or
not,
and
this
these
criteria
are
right
now
sitting
in
pull
requests
of
the
clinics
and
and
it's
there
waiting
for
review
and
input
from
other
people.
So
and
if
you
have
time
to
have
a
look
at
these
criteria
and
think
of
why
they
would
could
work
or
could
not
work.
That
would
be
really
great.
A
E
B
Just
to
just
saw
that,
like
hump
of
the
project
doesn't
stay
at
Google,
so
primarily
right
now.
This
is
the
only
white
crew
where
it's
like,
without
that
we
actually
can't
handle
like
me,
dominant,
had
support
for
multiply,
indexes
and
I
think
maybe
like.
We
should
probably
like
schedule
some
time
to
us
about
like
benefits
like
advantages
and
disadvantages
of
centralized
plugging
in
X,
and
so
last
time
this
topic
came
up.
B
We
basically
said
that
I
think
here's
the
there
was
a
meeting
that
much
he
was
leading
here
we
discussed
and
said
you
know
it's
basically
like
we're
not
trying
to
be
the
packagers
of
plugins,
like
you
know,
you
should
think
of
canonical
or
redhead,
for
example,
the
way
they
package
Linux
packages
and
they
look
at
the
source
code.
They
provide
patches
and
you
know
they
make
releases.
We
said
we're
not
gonna
go
that
route.
B
Take
a
look
at
your
code
and
where
you
should
make
it
clearly
clear
that
users
are
installing
plugins
that
are
not
necessarily
and
the
outcome
of
that
which
we
haven't
done
yet
was,
let's
add
a
warning
like
every
time
you
run
crew
install,
they
should
see
a
warning
saying
you're
about
to
install
random
binaries,
which
are
executable
to
your
machine.
Are
you
sure
something
like
that?
That
was
the
outcome
breach?
But
you
know
I'm
happy
to
discuss
that
as
well.
Okay,.
F
F
F
B
I'm
trying
to
like
find
ways
to
automate
it
like
I
mean
you
know
if,
like
potentially
Auto
merging,
like
release
bumps
you're
writing
a
tool
that
automatically
goes
and
bumps
the
releases
but
again
I
think
we're
actually
spending
a
lot
of
time
on
litigating.
The
plug-in
names
because
there
are
like
people
are,
writing
really
weird
plug-in
names
and
we
don't
want
them
to
exist,
necessarily
like
they're
making
to
us
for
they're
under
companies,
actually
changing
their
plug-in
names.
B
F
It
the
I
guess
my
biggest
concern
is
we
we
may
want
to
use
crew
to
in,
like
for
project
plugins
right,
like
you're
saying,
like
maybe
seek
networking
plug-in
they
want
right,
so
they
added
the
crew
and
then
in
our
documentation.
You
say:
crew,
install
that
plug-in
and
then
we're
kind
of
teaching
users
to
just
like
install
things
with
crew,
which
I
think
it's
fine,
but
it
might
not
be
we're
teaching
them
to
ignore
that
warning.
F
B
B
That's
all
like,
and
that's
why
I
think
like
we
make
the
index
just
like
ethical.
Like
you
say,
okay
I
want
to
accept
the
responsibilities
of
downloading
plugins
from
this
particular
index,
meaning
I
trust
this
index.
Then
there
will
be
no.
There
wouldn't
be
a
warning
as
such
and
then
centralized.
It
makes
possibly
could
be
like
that
as
well.
Yeah.
F
B
F
B
Something
like
that
would
work,
yeah,
okay,
cool,
hey,
listen
speaking,
I
think
we're
like
so
three
months
away.
Anything
like
that,
but
I
think
you
don't
get
it
some
functionality
supporting
multiple
indexes.
That's
it
yeah
like
having
more
discussions
around
centralizing,
makes
it
probably
a
few
moments.
Okay,.
A
G
I'm
happy
to
give
some
update
on
customized.
So
in
a
past
few
weeks
we
released
a
new
version
of
customized,
which
is
3.0.2,
so
this
version
include
a
fix
of
some
web
poker,
related
name
reference
which
blocked
the
QP
other
users.
So
we
fixed
that
issue
and
released
a
version
for
that
and
besides
that,
I'm
working
on
the
extended
patch
that
I
had
present
in
the
last
six
CRI
meeting.
G
So
the
patch
is
going
to
work
for
both
strategic
March
and
Jason
patch,
so
based
on
accountant
of
the
patch
we
can
determine
which
type
it
is
and
based
on
the
selector
that
specified
in
a
customization
file.
This
patch
can
be
applied
to
multiple
targets
and
so
right
now
the
implementation
is
mostly
down.
We
added
the
transformer,
we
added
a
lot
of
tests
and
the
next
step
is
going
to
add
documentation
and
example
for
this.
So
once
that
is
complete
completed,
we
will
release
a
new
version
of
customize
and
then
another
update
is
about.
G
Recently
we
received
many
PRS
from
our
community
contributors.
One
of
them
is
Jeremy
Bratt,
the
other
is
Eugene
Jung,
so
they
both
work
on
some
bug.
Fixing
sandbags
and
responds
to
the
issues
are
problems
that
you
the
reported,
and
they
are
very
helpful
on
fixing
those
and
improve
our
documentation
and
test
coverage
so
very
precious
to
their
help.
That's.
A
But
it's
still
very
exciting
that
we've
begun
to
move
it
and
if
you
have
any
any
time
to
help
out
to
pitch
in
to
this
effort,
it'll
be
very
appreciated
and
we
it's
it's.
Actually.
You
know
there's
some
difficulty
in
coordinating
these
PRS
just
because,
just
because
of
the
dependencies-
and
you
know
we
have
to
you-
know
some
of
the
these.
Some
of
the
moves
are
kind
of
difficult
to
need
to
coordinated
amongst
several
people,
because
your
PR
might
end
up
conflicting
was
somebody
else's
PR
move
anyway.
A
A
Does
anybody
have
any
questions
about
our
coupe
cuddle
and
independence
and
moving
the
coop
cuddle
package
coupe
cuddle
code
into
staging
once
so
for
those
who
aren't
as
familiar
with
the
effort?
Once
we
move
this
code
into
staging,
then?
Basically
the
code
will
be
reusable
and
it
will
be
available
from
the
coop
cuddle
repo,
instead
of
being
stuck
in
the
coop
cuddle
main
repo
or
the
coop
cuddle.
E
A
A
A
Okay,
so
so
we
don't,
we
don't
have
any
other
topics
to
cover
today,
but
number
one.
If
you
could
add
your
name
if
you
attend
and
since
we
do
have
extra
time-
and
we
do
have
some
contributors
which
who
I
haven't
had
a
chance
to
meet
and
and
I
think
some
of
the
rest
of
us
haven't
had
a
chance
to
meet.
If
you
want
to
introduce
yourself
now
would
be
the
time
I'll
start
off.
I'm
Sean,
Sullivan
and
co-chair
of
6cl
I
work
at
Google
and
I'll
cede.