►
From YouTube: Kubernetes SIG CLI 20201021
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
Good
morning,
good
evening,
good
afternoon,
depending
on
where
you
are
today
is
october
21st-
and
this
is
another
of
our
six
year-
life
weekly
meetings.
My
name
is
mate
and
I'll
be
your
host.
Today,
I
don't
have
any
particular
announcements
for
today,
so
we
can
right
away
jump
over
to
the
topics
I
see.
Eddie
is
on
the
call
eddie
want
to
talk
about
the
first
issue
that
we
covered
last
week
during
the
blocker
box-
scrub
yeah.
Sorry,
I'm
just
getting
caught
up
here
during
the
headlight
movement.
B
No,
I'm
good
cool,
so
this
one
came
up
in
our
bug
scrub,
and
this
has
come
up
in
a
bunch
of
different
places
and
ways
and
we've
closed
issues
as
duplicates.
The
tldr
is
xdg
is
the
kind
of
like
the
base
linux
philosophy
for
config
files.
It's
the
idea
that
configs
should
go
inside
of
like
a
dot
config
folder
in
your
home
directory,
as
opposed
to
being
scattered
around
and
kind
of
just
have
a
centralized
place.
B
Most
operating
systems
have
like
a
built
in
to
default
to
this.
If
you
just
rely
on
like
the
xddg
environment
variables,
and
so
it's
kind
of
been
open
for
a
while
and
we've
kind
of
put
a
hold
on
it,
so
I
think
doug
volunteered
to
take
a
stab
at
this,
we'll
probably
need
a
kept
for
this,
based
on
it
being
a
big
change
and
a
bunch
of
tooling
will
need
to
be
adopted
at
some
point.
C
Yeah,
I'm
I'm
aware
of
it,
and
I
don't
know
if
you
guys
agree,
but
I
was
wondering
if
you
can
use
like
a
backwards
like
a
if
user
have
the
kubiconfig
file
there
and
don't
have
the
dot
config
cup
city
out
there.
So
we
still
use
that
at
least
for
two
or
three
months
or
something
like
that
after
we
change
the
the
default
config
value.
B
I'd
assume
we'd
probably
have
to
keep
using
dot
cube
config
until
we
cut
a
major
version
change
because
that's
a
pretty
breaking
change,
but
I
I'd
agree.
I
think
we
could
default
to
that
new
xdg
stuff.
A
Let
it
sit
for
one
release,
gather
some
feedback,
get
her
back
box
fix
any
box.
If
there
will
be
some
in
the
next
release,
we
would
switch
the
flip
and
make
it
opt
out
so
that
it
will
be
the
default.
A
But
those
people
that
I
want
to
go
back
to
the
previous
behavior
would
have
it
and
then
in
the
third
release
we
would
entitle
sure
we
would
remove
the
option
of
going
back
to
the
cube
to
the
old
cube
file,
but
for
the
backwards
compatibility
we
would
keep
the
reading
the
old
location
for
longer
than
those
three
releases
it
would
just.
It
would
not
be
possible
to
go
back
to
the
old
one
by
default,
but
we
would
still
read
that
one
and
eventually
put
a
warning
somewhere
there.
D
C
D
D
I
was
just
going
to
say
that,
like
you,
it's
it's,
I
think
it's
possible
that
we
would
want
to
just
support
dot,
coop,
slash,
config
forever
or
like
three
years
or
you
know,
might
as
well
be
for
because,
like
the
chances
of
breaking,
people
are
high
and
the
what's
to
be
gained
from
not
falling
back
on.
That
is
pretty
low.
C
A
From
the
issue
yeah
I'll
write
it
down
in
in
that
issue:
that's
basically
what
we
are
doing
with
every
api
and
I
would
treat
our
configuration
as
as
a
sort
of
api.
That's
why
I
would
go
this
route.
This
allows
people
interested
in
the
new
feature
trying
it
out
eventually
report
the
box.
You
know,
and
yes,
we
need
a
cap,
and
the
cap
has
to
explicitly
call
out
this
approach.
A
Even
though
we
we
probably
don't
say
that
configuration
is
our
api,
but
it's
a
a
a
pretty
important
thing
for
people,
especially
that
we
will
be
dividing
the
the
config.
Currently,
everything
goes
under
home.cube.
A
That
includes
both
the
config
and
the
cache
with
xdg
directory
specification.
We
will
be
splitting
to
cache
landing
in
dot
cash,
cube
and
config.
A
Sorry
in
config,
landing
in
dot,
config
cube,
so
it'll
be
a
big
breaking
change
and
we
need
to
make
sure
that
cap
is
there
and
that
we,
we
are
very
allowed
about
doing
that.
Change.
That
includes
sending
announcements
to
sexyli
and
kubernetes
death,
probably
a
kubernetes
block
and
that's
doable
and
yeah,
and
cap
is
the
starting
point.
So
if
you're
douglas
open
to
working
on
it,
I'm
more
more
than
happy
to
to
welcome
that
kind
of
a
change.
C
Yeah
definitely
I
I'm
just
picking
up
some
issues
that
I
see
they
are,
while
dull
mode
so
just
try
to
move
forward
with
those
and
also
be
familiar
with
the
process.
The
code
so
be
nice.
E
Yeah,
I
was
just
gonna
amplify
what
mache
said.
We
need
to
communicate
with
the
rest
of
the
community
and
that
might
include
showing
up
at
the
kubernetes
next
community
meeting
and
as
much.
I
said
we
need
to
get
this
out
so
that
nobody's
surprised
by
this,
and
actually
it
might
even
be
worthwhile
to
not
do
anything
but
just
submit
ask
for
feedback
for
a
little
bit
before.
We
actually
start
working
on
this,
just
to
make
sure
that
we
know
that
people
are
gonna,
be
on
board.
A
So
we
can
definitely
put
a
cap
together
already
and
and
then
we
can
send
out
the
infos
out.
A
A
There's
there's
another
issue
that
I
that
I
linked
to
this
one.
Also
there
was
an
ask
for
multiple
configs
available
within
the
cube
home
directory.
I
haven't.
I
purposely
put
it
together
with
the
other
one,
because
since
we
will
be
touching
on
the
configuration
area,
can
you
dac
also
see?
Maybe
the
xdg
specs
also
touches
on
the
topic
of
having
multiple
conflicts.
A
A
That
can
you
also
put
include
that
one,
oh
I'll
write
it
down
in
the
I'll
write
it
down
in
the
in
the
other
issue,
and
we
can
pick
up
the
cap
discussion
from
there.
B
Yeah
plus
one
to
that
doug,
if
you
want
any
pairing
or
help
with
any
of
the
the
camper,
the
bureaucracy
stuff
feel
free
to
tag
me
in
I've,
been
wanting
to
dig
into
that
a
little
bit
more.
Oh
great,.
B
You
later,
then,
thank
the
other
thing
I
want
to
bring
up.
This
is
so.
This
is
something
that's
been
in.
The
back
of
my
mind
for
a
bit
is,
I
don't
think
the
cubeconfig
file
schema
has
any
concept
of
configurations
that
are
user
configurable
at
the
cubeconfig
level
to
avoid
having
to
pass
flags
or
something
all
the
time
kind
of
you
know
like
same
defaults
that
users
can
configure
on
their
end.
A
A
Can
you
edit
write
your
thoughts
into
the
issue
so
that
it
doesn't
disappear?
Yeah
I'll
capture
that.
F
Cool
and
one
more
thing
to
add
on
that,
too,
is
one
of
the
things
I
noticed
about.
The
config
file.
That
I
think
is
an
obstacle
to
to
multiple
configs
is
that
the
config
file,
essentially
stores
serves
two
purposes:
one
is
to
define
the
clusters
and
and
what
you
can
select,
and
then
it
also
has
the
concept
of
current
context.
F
If,
if
you
think
about
like,
I
want
to
have
a
bunch
of
different
config
files
that
define
my
clusters
but
then
which
one
of
those
is
the
one
that
controls
which
one
you
have
currently
selected
so
anyway,
I
I
can
write
that
a
note
on
that
in
the
issue
as
well,
but
I
think
that
maybe
it's
a
good
time
to
address
that
potentially
yeah.
Just
a
quick
point.
E
We
we
already
have
code,
which
merges
a
config
file.
That
code
already
exists
and
is
already
part
of
how
we
parse
config
files
now
just
to
keep
that.
B
In
mind,
yeah,
that's
a
good
point.
I
just
wanted
to
throw
out
there
that
I'll
bring
this
up
to
justin
garrison,
who
demoed
his
thing
last
time,
because
I
feel
like
this
is
right
up
justin's
alley
in
terms
of
what
he
was
looking
for
so
I'll.
Let
him
know
about
this.
One.
A
I
was
about
to
say
the
exact
same
thing
that
it
literally
it
fits
into
what
jason
was
doing
last
time
with
regards
to
multiple
conflicts,
so
yeah.
A
Okay,
cool:
does
anyone
have
any
questions,
thoughts,
suggestions
with
regards
to
this
topic
since
we're
exploring
this
area.
A
Okay,
I'm
hearing
none,
let's
jump
off
to
the
next
topic,
eddie
another
of
our
blocker
bug
issues
is
the
describe
pattern
matching.
B
So
yes,
okay,
so
right
so
I
see
antoine
just
commented
is
antoine
on
the
call
I
haven't
seen
him.
Okay,
the
tldr
for
this
one
is
describe,
does
pattern
matching?
So
if
you
type
cube,
ctl
describe
secret
default
and
there's
a
secret
name
default
token
stuff.
It
will
pattern
match
on
the
beginning
of
that
search.
B
This
behavior
is
not
replicated
through
anything
else,
including
get
and
other
features,
and
this
kind
of
just
zhao
brought
this
up
about
just
finding
consistency.
So
I
think
we
can
make
a
decision
if
we
want
to
implement
this
elsewhere,
deprecate
this
behavior
inside
of
describe.
A
D
A
A
I
mean
personally,
I
rarely
invoke
this
tribe
on
on
a
set
of
resources.
My
described
invocation
is
usually
done
after
I
do
cuddle
get
whatever
resource.
Let's
say
I
do
I'm
going
to
do
cubecardo
get
secrets,
I'm
gonna
see
a
list,
and
if
I
want
to
dive
into
one
particular,
I
will
do
describe
secret
and
I'll
get
the
name,
because
I
already
did
get
beforehand.
A
A
Okay,
going
to
reply
to.
A
A
A
Eddie
you
want
to
go
since
you're
in
on
the
roll
you
want
to
go
next,
especially
that
I
have.
I
have
an
upgrade
for
you
with
regards
to
update
cobra.
B
Yeah,
so
this
is
a
quick
and
easy
one.
Hopefully
you
can
read
through
that
pr.
If
you're
interested,
I
opened
a
pr
to
bump
cobra,
so
we
can
get
some
new
functionality
that
brian
and
knight
need
to
work
on
completion
and
because
brian
is
the
lord
and
savior
of
completion
and
the
there
was
a
bunch
of
there's
a
transitive
shaking
his
head.
B
There's
a
transitive
dependency
change
for
cobra
that
depended
on
a
newer
version
of
go
yaml
and
goyammal
new
version
broke
or
changed
the
default
line,
wrapping
behavior
from
being
infinite
line,
wrapping
to
80
characters,
and
so
this
is
obviously
a
breaking
change,
and
so
this
broke
a
bunch
of
our
tests
and
tools
and
conformance
tests.
B
So
the
tldr
solution
is
I've
been
talking
to
gustavo
who's,
the
the
the
developer
of
goyamo
and
he's
going
to
roll
back
that
change
for
us
and
cut
into
release.
So
we
should
be
good
there.
A
B
What
you're
talking
about
is
cobra
cut
a
new
release
to
depend
on
an
older
version
of
goyamo
that
didn't
have
that
change
in
it.
Oh
this
way:
okay,
yes,
which
it
was
a
good
stop
gap
for
us,
but
gustavo
got
back
to
me
in
email
and
so
he's
just
gonna
cut
a
new
go
yama
release,
so
I'm
kind
of
just
gonna
hold
on
that.
Until
we
see
what
what's
happening
there.
A
Okay,
okay,
so
we
have
a
backwards
compatible
solution
for
if
we
run
out
of
time
waiting
for
gustavo
and
if
gustavo
cuts
his
new
release,
then
we
need
to
sink
in
cobra
and
then
get
that
into
cube.
Yes,.
F
B
A
Yeah,
it's
it's
definitely
interesting.
A
G
Yeah,
I
was
just
going
through
the
steps
to
get
debug
up
to
to
our
graduation
criteria
from
alpha
to
beta
one
of
the
things
that
I
added
was
completing
a
user
survey
to
see
see
if
there's
any
any
big
feedback,
any
any
major
things
that
we
want
to
change
before
leaving
leaving
alpha,
and
so
I
just
wanted
to
ask
around
about
the
the
method
of
doing
that.
G
I
don't
I
don't
see
a
lot
of
user
surveys
going
around,
so
I
was
just
planning
on
doing
something
like
creating
a
google
form
sending
it
to
the
mailing
list.
G
But
if
anyone
has
any
better,
better
ideas,
I'm
happy
to
do
other
things
too.
A
I
would
definitely
go
with
this
approach
and
send
it
over
to
cubedf.
That's
prob,
that
that
one
has
the
protest
reach
and
then
eventually
we
can
tweet
about
that,
and
some
of
us
will
retweet
the
topic
and
that
should
eventually
gather
sufficient
information
that
we
might
require
for
the
graduation.
A
A
Okay,
that
was
fast,
we're
25
past
and
we
stormed
through
all
the
topics.
Okay,
so
before
we
move
on
to
the
stand-ups,
does
anyone
is
new
to
the
call
I'm
just
quickly
looking
through.
H
So
so
I
just
added
something
to
customize
for
an
edit,
the
edit
command
to
add
and
remove
transformers
and
like
as
a
company,
we're
just
we've
got
a
pretty
complex
deployment
using
customize
and
on
top
of
kubernetes
of
our
software
of
our
sas
software.
So
thank
you
jeff
for
accepting
that
pull
request
and
just
kind
of
being
a
fly
on
the
wall.
Listening
in.
I
This
is
mike
here.
I
recently
joined
google
and
helping
out
sean
jonathan
morton
with
some
of
the
customized
stuff
cool.
Welcome.
A
Okay,
I
think
the
rest
of
the
names
I
am
pretty
familiar
with,
so
I
I
did
identify
a
new
person.
Okay,
welcome
both
of
you.
It's
definitely
a
pleasure
to
have
you
on
our
call.
Does
anyone
have
any
topics
that
they
want
to
walk
through
with
the
group.
A
J
Thanks
yeah
super
quick,
we've
actually
had
a
couple
of
points
of
recent
interest
in
using
kui
for
other
client
integrations.
I
mentioned
one
here.
It
seems
to
be
the
furthest
along,
but
over
the
past
couple
weeks
I
think
about
three
people
have
come
in
wanting
to
do
their
own
integrations
and
roll
out
versions
of
kui.
So
I
decided
to
mention
one:
they
actually
release
it.
You
go
to
the
website
and
they
actually
kind
of
mentioned.
They
actually
did
this
all
pretty
much
on
their
own.
They
read
her
documentation
and
and
made
something
happen.
J
So
that's
it's.
This
ends
up
not
being,
I
think,
they're
more
of
a
serverless
kind
of
thing,
but
this
is,
I
thought
it
was
kind
of
interesting.
Somebody
was
able
to
to
take
our
work
and
roll
their
own
pretty
much,
and
so
they
made
a
set
of
commands
to
pretty
much
be
kind
of
like
a
postman
as
far
as
I
can
tell
for
so
that
was
interesting.
There's
a
couple.
J
Others,
too,
that
I
haven't
seen
how
they've
heard
they've
got
where
they're
going
yet,
but
they've
been
doing
stuff
with
coulee,
so
when
they
make
progress
I'll,
let
you
guys
know.
The
second
thing
is
just
we've
been
really
continuing
to
refine
the
stuff
we
talked
about.
J
Last
time
I
was
on
the
call
at
least
I
missed
last
week's
last
times,
but
just
continued
refinements
to
see
how
we
can
refine
the
this
notebook
more
notebook-like
presentation,
so
we
can
have
a
terminal,
but
you
can
intersperse
commentary
essentially,
and
so
we've
done
some
some
container
refinements
and
you
can
look
at
it
yourself
with
the
links
we're
about
to
release
that
with
that.
With
those
changes,
I
think
we're
we're
in
pretty
good
shape.
So
maybe
we
can
think
about.
J
You
know
how
we
can
maybe
have
some.
Maybe
some
meat
points
for
some
of
the
documentation,
work
and
talk
about
that.
Maybe
next
time,
but
we've
made
pretty
substantial
progress
on
the
on
the.
E
A
Okay,
that's
good
news.
I'm
glad
to
hear
that.
Does
anyone
else
have
any
projects
that
or
stuff
that
they
work
in
the
past
couple
of
weeks,
two
three,
whatever
that
they
want
to
share
with
the
group.
E
A
I
did
mention
that
kubecon
and
there's
a
link
in
the
agenda
from
our
last
call
from
two
weeks
ago.
I
didn't
want
to
repeat
ourselves
over
and
over
again,
but
yes,
it's
happening
somewhere
mid-november.
A
If
you
haven't
heard
about
it,
it's
again
virtual
for
obvious
reasons,
there's
a
link
in
the
agenda
in
the
previous
one
when
we
will
be
holding
our
when
we
will
be
holding
our
six
cli
session.
A
I'll,
probably
remem
remind
about
the
topic
in
two
weeks,
which
will
be
shortly
before
the
kubecon
itself.
So,
and
I
guess
with
that
happy
thought
we
can
close
today's
goals
and
I'm
gonna
give
you
all
back
30
minutes
of
your
precious
time.
Thank
you
very
much
stay
safe
and
see
you
in
two
weeks.
Bye.