►
From YouTube: Kubernetes SIG CLI 20200115
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
the
way
you
are
today
is
January
15th
and
we're
having
our
another
bi-weekly
6e
align
meeting.
My
name
is
Masha
I'll
be
your
host.
Today,
our
agenda
is
packed
I
linked
it
in
the
chat.
So
please
add
your
name
to
that
in
these
part,
if
you're
not
there,
yet
let
me
kick
off
with
quick
announcements.
So,
first
of
all
the
coronaries
contributor
experience
survey
is
still
open.
A
If
you
haven't
got
a
chance
to
to
respond
to
that
survey,
there's
a
link
in
the
agenda
to
the
email
that
was
set
out
earlier
to
the
community
staff
mailing
list
make
sure
to
respond.
This
basically
shapes
how
the
developer
tooling
is,
is
being
built
around
the
coronaries
project.
So
you
have
an
influence
on
what
you
like
what
you
don't
like
about
the
entire
work
flows.
A
A
A
That
basically
means
that
we
will
open
the
floor
for
people
to
bring
up
questions
discussions
ideas,
since
that
is
recorded.
We
can
old
and
looking
through
those,
but
at
the
same
time
gives
us
the
ability
to
meet
you
to
one
another
and
answer
the
questions
that
people
might
have
around
60
Li
overall
or
the
past
decision
is
future
directions.
A
Finally,
we
had
a
configuration
brainstorming
session
earlier
this
week
if
you've
seen
announcements
from
Phil
from
last
week,
I
linked
both
the
message
that
was
sent
out
to
the
governor
at
6:00
Eli,
as
well
as
the
agenda
and
meeting
notes
from
that
meeting.
If
you're
interested
in
participating,
please
sync
with
Phil.
If
I
remember
correctly,
he
was
thinking
about
setting
up
another
event
like
that
one
in
the
near
future.
Basically,
it
was
entirely
devoted
to
discussing
how
we
can
configure
and
work
with
with
the
cube
resources.
A
C
D
The
whole
issue
was
might
hey.
This
is
wolf.
The
whole
issue
is
documented
in
2052.
You
can
link
to
that
from
the
notes.
The
issue
20:52
yeah,
that's
about
bars
and
about
the
situations
where
it
works
and
doesn't
work,
and
we
suggested
in
that
issue
they
pile
their
own,
removing
bars
on
post
Amar's.
If
you
want
stick
it
on,
require
writing
and
some
sort
of
shortcut
there
document
subscribe
thanks.
E
So
I,
don't
think
Jenny's
here,
so
I'm
gonna
make
it
it's
gonna
be
brief.
We
just
want
to
say
that
everything's
moving
along
for
dry
run,
we
have
a
bully
request.
That
does
what
we
talked
about
during
the
meeting
and
in
the
cap.
It's
mostly
reviewed.
We
have
a
failing
test
right
now,
but
everything
should
be
good.
Very
soon.
We
have
another
person
helping
us
with
the
documentation
from
Dave
and
Reverend,
because
we
need
to
change
all
the
documentations
for
driver.
E
E
A
F
So
I
just
missed
a
couple
of
meetings
and
wanted
to
check
in
I
reviewed
the
video
but
we'll
check
in
about
coop
cuddle,
debug
planning
on
doing
the
implementation
for
alpha
and
118
I
wanted
to
see.
If
there's
any
additional
feedback
before
marking
kepis
is
implementable,
I
saw
there
was
a
little
discussion
about
whether
this
should
be
in
control
or
customized,
but
I.
Don't
I,
don't
think
it
was
addressed.
I,
don't
think
a
decision
was
made.
Is
that
right,
I
think.
A
A
So
I
like
I
personally,
the
fact
that
I
want
to
have
it
as
a
regular
command
I
would
still
go
with
with
kubernetes
and
start
bringing
awareness
to
the
users
that
this
is
the
command.
That
will
be
there
eventually
newer
versions.
We
can
think
of
how
to
provide
users
with
newer
versions,
but
oh
yeah,.
F
A
Is
also
agreeing
that
Caudill
would
make
sense,
I
mean
he
had
planned
on.
Oh
I'm,
sorry
I
mean
I,
look
through
your
cap
earlier
today,
and
basically,
unless
there's
some
hard
objections
that
anyone
wants
to
make
with
regards
to
keep
cuddle.
Debug
own
emerged
the
cap
right
after
this
meeting
or
a
little
bit
of
later,
but
basically
today
and
I'm
not
saying
it's
like
completely
a
hundred
percent
of
how
many
percent
dawn
cap,
as
is
but
I,
think
since
we're
introducing
in
alpha
command,
it
doesn't
have
to
be
fully
hundred
percent
sure.
A
The
way
we
envision
this
being
in
the
long
run,
I'm
pretty
sure
that
we
will
iterate
over
the
command,
how
it
works,
gather
feedback
from
users
and
improve
as
we
go
before
we
do
a
final
GA
of
those
commands,
so
I
think
the
current
the
current
cap
nicely
covers
the
basic
use
cases,
several
workflows
that
both
Lee
and
myself
thought
of
and
other
people
that
were
also
reviewing
the
cap.
So
unless
I'm
going
to
hear
a
strong
objections,
the
cap
is
is
going
to
be
merged
within
the
next
few
hours.
A
F
F
My
other
question
is
that
someone
drove
by
and
said
we
needed,
I
needed
to
go
ahead
and
fill
out
the
testing
plan
I'm,
not
sure
exactly
what
that
would
look
like
for
for
CLI
changes,
but
I
thought
it
would
be
reasonable
just
to
write
basically
what
you
just
said
that
we
will
put
this
under
and
hopeful
subcommands,
and
it's
very
clear
that
it's
in
testing
and
doing
real
word
world
testing
and
then
just
a
personal
note
for
me.
I
expect
this
feature
to
take
several
releases
before
we
would
even
consider
a
beta
yeah.
A
That's
pretty
much
my
take
and
on
it
as
well.
So,
even
though
we
will
be
creating
some
tests
covering
the
functionality,
putting
hard
requirements
with
regards
to
how
this
should
be
tested
doesn't
seem
right
because
we
might-
and
we
most
probably
will
change
the
functionality
over
the
curse.
If
we
find
that
whatever
you
thought
at
this
point
in
time
is
just
ridiculous
or
requires
a
great
amount
of
user
input
by
anyone,
introversion
whatever
we
will
try
to
simplify
the
use
cases
and
it
improves
a
user
experience.
A
B
Just
wanted
to
let
you
guys
know
that
the
papyri
factor
merged
and
again
it
didn't
change
any
functionality.
It
was
just
our
our
first
pass
at
trying
to
clean
stuff
up.
It
probably
did
too
much
to
be
honest,
I.
You
know
now
that
I
I
got
the
feedback
that
I
got
as
well
as
my
own.
You
know,
looking
back
on
what
I
did
I
probably
did
too
much
in
in
that
one
and
and
in
the
future,
would
probably
try
to
a
smaller
scope
just
for
safety's
sake,
but
it
it
hopefully
it
it
has
reorganized.
G
Okay,
so
yeah
I'll,
chime
in
so
one
thing
which
crew
is
always
driving
is
that
we
don't
know
how,
like
an
adoption,
is
and
how
many
people
are
actually
using
plugins,
and
for
that
we
built
a
little
tool
which
basically
helps
us
track.
How
many,
how
many
plugins
there
are
so
for
that
I
wanted
to
share
my
screen,
but
I
don't
know
which
window
it
is.
A
G
G
Perfect,
okay,
great
so,
and
so
what
we
started
to
do
is
we
have
a
basically
a
cron
job
which
runs
on
cloud
run
and
it
scrapes
all
the
github
download
statistics
from
all
the
plugins.
We
have
another
coup
index
by
the
way
the
number
has
increased
to
75
plugins.
So
ever-growing
yesterday
it
was
two
more
plugins
submitted,
so
there
is
more,
more
plugins
are
being
submitted
and
alright.
So
you
know
this
this
tools,
great
the
download
statistics
from
github.
G
We
need
to
do
that
because
guitar
doesn't
only
provides
the
total
number
of
downloads
and
we
won't
really
want
to
have
the
downloads
over
time.
So,
for
example,
here
you
see
the
downloads
of
crew
for
different
versions
and
also
with
a
nicer
graph.
So,
for
example,
sir,
this
shows
that
our
latest
version
in
three
points
we
can
draw
now
really
has
taken
off
and
the
others
are
basically
not
downloaded
and
much
anymore.
G
There
are
a
few
downloads,
but
we
don't
know
why,
and
so
this
is
the
most
important
thing
for
us
because,
but
basically
we're
working
on
crew,
but
they
are
also
plug-in
statistics
for
individual
plugins,
so
one
overview
for
all
the
plugins
which
you
can
look
into
and,
of
course,
or
individual
against,
like
for
crew
for
the
crew
plugin
yeah,
and
so
we
won't
release
this
at
some
point.
It's
not
completely
ready.
Yet
there
are
a
few
issues
I'm,
but
I
think
this
will
be
a
great
tool
to
try
and
plug-in
success
as
well.
A
A
H
So
the
the
way
we
tackled
bug
stuff
last
time
we
did
it,
it
just
doesn't
seem
like
a
way
that
we'll
be
able
to
get
through
130
open
issues.
I
still
want
to
propose
the
idea
of
having
a,
maybe
even
a
one-off,
like
heads
down.
We
all
focus
on
get
up
issues
go
through
and
triage
and
close
all
the
ones
we
can.
H
H
Yeah
I
think
that's
that
I
think
even
just
one
meeting
is
great
I.
Think
honestly,
if
we
can
tackle
the
brunt
of
these,
most
of
these
have
been
open
for
a
while
and
if
we
can
like
bust
down
the
numbers
and
like
one
or
two
meetings,
like
probably
you
know,
won't
have
to
do
it
as
often
or
reoccurring
whatever,
but
like
yeah
there's
just
like
there's
120,
he
opened
right
now
and,
like
I'm
sure,
a
good
chunk
of
these
are
just
like
you
know,
quick
triage
and
close
or
something.
H
Yeah
I
think
that's
so
how
I've
done
open
source
bug
scrubs
in
the
past
is
someone
literally
just
shares
their
screen
and
we
go
issue
by
issue
just
talking
through
it.
You
spend
probably
like
30
to
60
seconds
per
issue,
and
then
you
know
someone
can
volunteer
to
take
it.
If
it's
one,
we
think,
needs
some
like
actual
attention.
Otherwise,
like
like
I,
said
a
lot
of
these
I
really
just
think.
Are
you
know
a
little
education
could
get
it
closed
on
the
user's
behalf.
A
Okay,
so
let's
propose
this:
let's
have
one
box
crap
next
Wednesday
can
I
ask
you
to
send
out
an
invite
to
all
of
260
li
the
same
time
as
we
are
having
six
Eli
next
Wednesday.
We
would
have
the
meeting
that
will
be
entirely
focused
on
scrubbing
the
box
and
can
I
throw
at
you
the
the
preparation
for
that
yeah.
A
If
that's
the
case
and
nobody
objects,
they'll
be
pretty
awesome
and
I
would
like
to
see
folks
that
want
to
have-
and
you
know
show
up
during
the
next
next
week's
meeting
and
let's
see
how
this
will
go,
how
frequently
we
would
want
to
go
with
this,
how
how
our
velocity
will
be
with
about
with
tackling
those
cool
yeah.
Definitely,
let's
do
it
next
week
and
let's
get
this
ball
rolling.