►
From YouTube: Kubernetes SIG CLI 20210922
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
september
22nd-
and
this
is
another
of
our
bi-weekly
six
year-
life
calls.
My
name
is
mate
and
I'll
be
your
host.
Today,
our
agenda
is
pretty
much
packed
with
topics
but
also
announcements,
although
one
is
still
secret
for
one
tiny
little
more
moments.
A
Most
importantly,
we
are
having
kubecon
in
couple
more
weeks.
I
can't
remember
because
I
always
forget
to
check
when
it
is
whether
that's
second
or
third
week
of
of
october,
but
most
importantly,
we
will
be
having
a
six
cli
updates
here
in
kubecon.
I've
linked
this
session
in
the
agenda.
A
You
can
feel
free
to
add
added
to
your
sched
and,
additionally,
if
I
remember
correctly,
katrina
will
be
there
in
person
and
we'll
be
doing
meet
and
greet
so
if
you're,
there
feel
free
to
say
hello,
and
now
the
most
important
announcement
is.
We
are
changing
leadership.
A
That
means
we
will
be
welcoming
a
new
6,
cli,
lead
and
technical
chair,
and
that
will
be
katrina.
Katrina
did
an
amazing
job
with
customize.
Over
the
past
couple
of
months
she
joined
was
mentored
by
both
eddie
and
philip
did
an
amazing
job,
structurizing
customized
meetings.
She
set
up
customized
blockers,
crop
that
we're
doing
monthly
and
is
doing
an
amazing
job,
supporting
myself,
eddie
and
sean
with
the
sig
leadership
roles,
which
basically
is
it's
about
time
for
her
to
to
pick
up
the
chair
role
and
the
technical
lead
role.
A
At
the
same
time,
phil
is
deciding
to
step
down
entirely
from
six
cli.
A
He
has
been
one
of
the
person
that
set
up
six
eli
years
ago
and
over
the
past
couple
of
years,
while
mentoring
katrina,
he
was
providing
the
technical
guidance
by
being
technical
leader,
so
he
will
be
resigning
from
that
one
as
long
along
this
and
finally
I'll
be
stepping
down
as
a
chair
similarly
to
phil,
but
this
time
oh
I'll
I'll,
be
chair
for
the
next
few
months,
I'll
make
sure
to
pass
all
the
proper
tooling
and
whatever
tricks
that
are
needed
to
run
these
meetings
over
to
eddie
sean
and
katrina.
A
I've
been
chair
for
almost
four
years.
I
thought
that
there
was
three,
but
it
was
actually
four.
I
dig
it
up
just
before
this
call
I
stepped
in
in
february
2018,
so
at
the
end
of
this
year,
I'll
step
down
as
a
chair,
but
I'll
continue
serving
as
a
technical
leader
for
for
some
more
time,
especially
that
6
july
is
still
dear
to
my
heart.
A
So
those
are
the
big
announcements,
I'll
be
sending
appropriate
emails
to
both
cube
dev
and
cli
right
after
this
call
big
congratulations
to
katrina
and
thank
you
very
much
for
to
phil
for
all
the
support
and
help
and
technical
guidance
that
he
has
been
driving
us
through
the
years.
A
C
Yeah,
we're
very
excited
to
have
katrina
on
officially
and
thank
you
mache
for
leading
and
defining
what
the
opening
of
our
meetings
looks
like
for
years
to
come.
So
I
have
I've
used
it
in
many
other
places.
Since
so.
Thank
you
and
phil
too,
for
his
technical
leadership
and
founding,
and
I
didn't
know
this,
but
phil
is
actually
on
steering
at
one
point
so
yeah.
If.
A
I
remember
correctly:
phil
was
at
on
the
steering
pretty
much
around
the
time
when
I
stepped
in
into
6
eli
to
help
him,
because
he
was
a
little
bit
overwhelmed.
He
after
fabiano
left
for
his
extended
pto
phil
was,
I
think,
left
the
only
person
running
six
cli
and
at
the
same
time
he
was
also
appointed
for
for
steering.
A
So
he
was
doing
both
and
that's
why
he
reached
out
to
me
and
that's
how
the
entire
story
happens.
Since
then,
a
lot
has
changed
in
sixth
july
over
the
past
four
years.
A
We
we
still
have
big
plans
for
sure
so
and
I'll
definitely
I'll
be
around
to
help
guide
the
the
technical
side
of
the
things
and
I'll.
Let
someone
else
handle
the
organizational
side
of
things
this
time.
A
Okay,
moving
on
to
introductions
do
we
have
anyone
that
is
new
to
this
call
that
would
like
to
introduce
themselves
say
a
few
words
what
they
are
expecting,
what
they
want
to
work
on,
or,
basically
anything
or
just
say,
hi.
A
A
A
D
Oh
okay,
cool,
so
hello,
everyone,
so
my
name
is
munchie,
so
I'm
working
for
google
so
for
I
have
been
working
on
the
the
kubernetes
project
for
different
various
projects
for
years.
In
case
someone
doesn't
know
me
so
I
have
been
working
on
to
control,
apply,
customize
and
the
tributer
and
other
stuff.
D
Okay,
so
so
I'm
proposing
this
clip,
which
is
about
creating
a
new
public
pr
and
function
registry,
so
it
can
help
the
term
communities
to
contribute
and
discover
useful
crm
functions.
D
D
So,
as
google
we
have,
we
have
created
karen
a
function
registry
for
mostly
for
google,
authored
functions
and
the
we
want
to.
We.
We
want
to
have
a
similar
thing
for
for
the
community,
and
then
we
can
potentially
like
contribute
some
of
our
generic
functions.
There
currently
there's
a
problem,
but
there's
a
issue
that
not
everyone
in
the
communities
can
contribute
to
a
google
on
the
project.
D
And
then
I
can't
develop
a
little
deeper
into
the
proposal,
so
the
proposal
is
to
have
a
tool
component
so
why
it's
a
repost
owned
by
cncf
and
sponsored
by
the
6
ai.
So
this
repo
is
used
to
host
the
index
for
the
prm
functions
in
the
registry
and
there
is
also
a
going
to
have
a
website.
So
the
website
going
to
present
the
dog
examples
to
the
end
users
for
like
discoverabilities.
D
Quickly,
talk
about
the
potential
model
for
managed
registry,
so
one
way
is
that
where
you
have
centralized
index
and
the
centralized
release
management,
so
that
means
so
everything,
including
source
code
doc
and
the
release
all
happens
in
one
repo.
D
So
this
it's
what
we
are
using
in
cab
function,
right,
cab
function,
catalog
at
google.
D
And
there's
another
management
model,
which
is
we
have
a
centralized
index,
but
we
have
a
distributed
release
management.
So
this
this
model
is
similar
to
what
we
are
currently
does
for
crew
index,
so
which
is
the
plugins,
are
built
separately
from
the
ripple,
but
the
ripple
is
just
hosting
the
metadata
for
this
plugins.
D
And
then
so
for
six
cli,
we
can
actually
mix
these
two
models
together
for
for
the
six
ai
on
the
time
functions.
For
example,
customers
want
to
build
and
distribute
some
current
functions.
We
can
actually
do
it
in
tree
and
for
others
functions
from
the
communities.
We
can
manage
the
source
code
out
of
tree
and
have
the
index
have
the
metadata
in
the
as
index
in
the
repo.
D
So
when
we
have
the
source
code
of
out
of
trees,
then
of
course
we
want
to
think
about
security
and
the
trust.
So
then
we
introduced
a
concept
called
publishers,
so
a
publisher
can
be
a
kubernetes
project
or
communities
or
companies.
So
when.
D
A
contributor
wants
to
publish
functions
they
need
to.
They
can
choose
to
publish
on
behalf
of
a
publisher.
D
So,
for
example,
can
katrina's
can
publish
a
public
current
function
for
customized
community
and
the
like
for
another
contributor
can
publish
functions,
for
example,
for
google
like
that,
and
we
want
to
enforce
several
rules
to
ensure
that
it
is
published
by
the
red
person.
D
D
So
the
publishers
is
responsible
for
the
security
for
their
crm
functions.
6I
is
not
so.
This
is
a
little
similar
like
crew
plugins.
D
So
I
imagine
we
can
have
a
website
probably
like
using
this
url
and
the
users
then
can
browse
this
website
to
discover
their
term
function.
They
want
to
use.
A
I'll,
let
other
folks
ask
questions
before
I'll
I'll
save
mine.
C
D
D
D
Okay,
here
is
an
example,
so
it
takes
a
a
resource
list
and
which
it
can
contains
a
list
of
parent
resources
and
then,
of
course,
functions
can
manipulate
these
resources
or
validate
the
resources.
D
It
can
be
used
to
like
do
some
customizations
on
your
configurations.
Resources,
for
example.
I
can
do
like
set
labels
on
some
certain
resources
using
functions.
D
Yes,
so
it
can
also
like
using
the
result
to
generator
views
that
can
be
potentially
consumed
by
some
other
tools,
so
yeah.
This
is
adopt
by
customized
cap
and
some
other
tools.
D
Does
the
answer
your
question
id
it
does?
Thank
you.
A
So
I
had
a
question
about,
I
think,
towards
the
end.
As
one
of
the
users
saw,
you
did
mention
that
it
is
possible
to
pick
a
different
link
for
a
catalog
does
mean
that
a
user
of
customize
can
pick
which
registry
it
can
consume.
A
Data
from
this
is
basically
something
similar
to
crew
has,
because
before
crew
was
only
using
a
single
catalog,
meaning
the
one
that
we
maintain
in
crew
index
and
there
was
no
option
for
users
to
specify
their
own,
so
you,
by
default.
We
always
assume
that
you're
gonna
trust
the
upstream
upstream
index
and
we've
heard
different
opinions
that
users
would
want
to
be
able
to
customize
that
index
and,
for
example,
created
their
own
curated
index
for
crew
plugins.
A
A
You
could
always
add
there
additional
indexes,
but
the
default
wouldn't
have
to
be
the
the
upstream,
which
you
might
think
as
an
insecure
or
or
similarly,
whereas
the
curated
registry
could
be
either
company
approved
and
some
additional
security
checks
might
have
been
performed
on.
Those
internal
repos
is
the
the
catalogs
something
along
those
lines.
B
B
So
it
touches
on
more
of
the
answers
to
those
questions
I
would
say,
but
one
of
the
ideas
that
that
is
baked
into
that
is
the
long
lines
of
what
you
said
where
we
do
like
the
idea
of
having
customized
like
if
we
build,
as
in
the
proposal,
we're
looking
at
the
moment,
an
official
registry
having
a
very
small
set
of
plugins
that
are
essentially
things
that
customize
would
like
to
provide
as
built-ins
by
default,
but
for
technical
reasons,
they're
not
really
suitable
for
being
built
in
and
those
would
act
as
though
they
were
built-ins,
essentially
because
customize
would
be
compiled
in
a
way
that
trusts
those,
but
it
would
be
a
fairly
small
set,
and
then
there
would
be
a
secondary
registry
that
would
be
organized
by
by
publisher
as
in
this
proposal,
and
it
didn't
have
to
be
with
a
filter
like
this.
B
I
do
have
some
feedback
for
the
cap
that
I'll
that
I'll
provide
on
the
on
the
pr,
but
I
think
it's
very
nice
model
that
it's
basically
an
index
and
we
can
build
and
provide
different
permutations
of
that
very
easily
if
we
have
all
the
metadata
to
do
that,
like
we'd
auto-generated,
all
the
different
catalogs
one
for
each
publisher,
one
for
level
of
support,
one
for
customized,
built-in,
etc
since
we're
driving
it
all
off
very
explicit
metadata.
I
think
this
is
super
powerful,
and
this
drives
very
well
with
the
other
cap.
A
Yeah
I,
as
long
as
it
this
follows
the
what
we
set
up
in
the
crew
index.
I
think
I'm
I'm
okay
with
that,
because
we
did
have
several
iterations
on
the
career
index
and
this
one
is
definitely
using
reusing
a
lot
of
the
content.
So
I
don't
have
any
objections.
Personally.
A
Okay
hearing
none.
Thank
you
very
much,
wenge
and
katrina
for
explaining
this
to
us.
E
Last
last
meeting
we
talked
about,
there
was
an
issue
where
somebody
was
trying
to
do
kubeco
run
with
an
override
that
set
the
limit
and
they
weren't
able
to
do
that
without
replacing
the
entire
spec.
So
we
talked
about
creating
a
a
way
to
say
what
type
of
override
you
want
to
perform.
So
excuse
me,
instead
of
like
a
a
json,
instead
of
doing
a
a
total
merge,
we
talked
about
doing
like
a
an
rfc
6902
json
patch,
which
gives
you
the
ability
to
say
specific
operations
like
I
want
to.
E
Node
in
the
in
the
in
the
ammo,
for
example-
or
I
also
added
in
in
this
pr
the
ability
to
do
a
strategic,
merge
patch,
so
I
kind
of
modeled
it
off
of
the
types
that
are
available
in
cuddle
patch
and
then,
when
I
was
looking
at
this,
I
also
noticed
cube.
Color
exposed
also
has
the
same
override
capabilities,
so
so
I
made
it
so
so
I
did
a
little
bit
of
refactoring,
so
it
could
share
the
same
override
code
between
run
and
expose.
E
A
Hey
you
made
fast
work
on
that
one
thanks,
brian
sure
yeah.
Definitely,
if
I
remember
correctly,
expose
does
use
all
of
the
primitives
from
from
run,
including
all
the
generators
that
we
got
rid
of
in
the
past,
so
good
catch
on
on
fixing
also
exposed
in
parallel
with
run.
A
E
Oh
actually
yeah,
but
but
we
may
have
talked
about
it-
on
boat,
strap
too.
A
Yeah,
definitely
we
just
need
someone
to
review
that
and
I
think
it's
pretty
safe
to
say
that
it's
it's
it's
a
very
good
approach.
C
A
F
Not
too
much
to
share
this
week:
okay,
midstream,
okay
katrina
with
regards
to
customize.
B
I
guess
a
quick
update
that,
with
regards
to
cubecon
talks,
jeff
and
I
have
been
hard
at
work
on
on
hours-
we're
doing
a
presentation
on
customized
extensions.
It's
also
kind
of
related
to
the
topic
we
were
discussing
earlier
and
we're
going
to
be
doing
a
bunch
of
doc
updates
ahead
of
that
too.
So
that's
something
to
look
forward
to.
B
Natasha
is
also
here
and
natasha.
If
you
want
to
talk
about
your
work
yeah.
No,
I
don't
have
anything
to
add
thanks.