►
From YouTube: Kubernetes SIG CLI 20190619
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
afternoon,
good
evening,
depending
on
where
you
are
today,
is
June
19th,
and
this
is
yet
another
six-year
live
meeting.
Welcome
everyone.
Before
we
get
to
the
main
topics.
I
would
like
to
encourage
all
of
you
to
add
yourself
in
the
attendee
and
agenda
I
linked
the
agenda
and
the
chat
currently
there's
only
one
announcement
that
I
have
the
route
of
115
release
was
delayed.
You
to
test
issues.
The
sick
scaling
is
currently
working
on
fixing
those
the
state
out
of
from
yesterday
was
that
it
will
be
delayed
until
today.
A
A
B
A
B
A
A
E
Okay,
can
you
see
it?
Yes,
I
see
his
train
right
here,
you
know.
Okay,
this
is
gonna,
be
short,
because
the
release
notes
are
there
and
so
forth.
Yesterday
we
cut
2.1
of
customize
and
it's
got
a
lot
of
internal
changes
and
one
external
change
is
kind
of
a
big
deal,
so
the
internal
changes
are
now
that
customized
me
means
resource
order.
When
it's
been
reading
a
way,
it
reads:
resources
in
depth,
first
form.
E
So
if
you
want
to
control
your
output,
the
resource
ordering
output,
you
can
now
just
edit
your
customization
file
and
specify
things
in
the
order.
You
want
them
to
appear
to
get
that
appearance.
You
have
to
use
a
special
flag
because
we
didn't
want
to
break
existing
behavior
and
people
are
currently
depending
on
the
current
output
of
customize.
So
anyway,
that's
all
explaining
the
release
notes.
Please
take
a
look.
E
The
other
thing
is
that
there's
plugins,
so
you
can
write,
there's
a
framework
for
writing
generators
which
create
resources
and
transformers
which
modify
resources
and
the
plug-in
framework
is
actually
used
internally
by
customize
itself.
So
everything
that
customized
does
now
has
been
reexpress
tin,
plugin
form.
This
is
to
make
sure
the
framework
makes
sense
and
to
help
clarify
what
kind
of
api
a
plugin
on
would
need
and
expect.
So
that
api
is
alpha.
E
Now
you
have
access
to
a
plugin
author
has
access
to
you
know
various
packages
that
are
used
or
customized,
for
you
know
loading
and
manipulating
resources,
and
so
on.
So
as
that
settles
down
as
people
people
do
use,
transformers
and
generator
plug-ins
will
find
out
more
about
the
api
and
locking
down
a
little
bit
further
in
future
releases.
So
right
now
it's
alpha.
It's
gonna,
it's
gonna
change.
E
There's
a
couple
more
things:
there's
a
flag
to
remove
locusts
restrictions,
which
wasn't
a
very
popular
feature.
There's
a
new
field
called
inventory,
which
will
generate
a
config
map
that
contains
an
inventory
of
all
of
the
objects
that
are
part
of
your
build,
and
this
can
be
used
on
the
server
side
to
do
intelligent
pruning
and
then
there's
a
bunch
of
miscellaneous
field
changes
that
you
can
go
ahead
and
read
about
in
place
notes.
So
that's
it.
A
C
C
The
cap
is
here
it's
about
expanding
the
pair,
how
we
handle
patterns
in
customized,
so
first
I'm
going
to
talk
about.
What's
the
current
stress
you
with
select
four
patches,
so
in
current
customized
we
have
two
type
of
patties.
One
is
strategic,
merge
patch,
the
other
is
Jason
patch,
and
each
of
them
have
this
different
format.
C
Let's
say
for
one
patch:
it
can
only
be
applied
to
one
resource
if
you
want
to
apply
the
same
patch
to
multiple
resources
or
to
different
resources,
you
have
to
write
multiple
pages,
so
that
is
the
limitation
of
current
patches
and
in
this
cap,
we'd
like
to
extend
the
patching
mechanism
and
making
it
possible
to
support
multiple
targets
by
only
one
patch
throw.
So
this
is
related
through
some
usage.
Like
maybe
you
want,
you
may
be
some
user.
They
want
to
buy
one
patch,
they
change
all
the
container
arguments
or
buy
patch.
C
They
inject
an
actual
container
to
all
the
other
containers
and
different
resources,
and
the
proposal
I
have
here
is
to
change
the
patch
type
to
a
different
struct,
and
here
at
least
have
details
like
what
field
it
should
and
yeah.
So
let
me,
let's
take
a
look
at
my
example.
So,
by
this
new
proposal
we
have
patches
it's
just
one
single
field:
we
don't
have
strategic
market.
C
Roger
is
a
patch
six
now
group
anymore,
so
those
will
be
covered
by
the
same
patches
directive
and
in
this,
in
this
patches
is
a
list
of
object
like
in
each
of
the
item.
You
can
specify
what
what
is
the
patch
file
and
what
is
the
type
of
that
patch
file
either
strategic,
more
patch
or
recent
patch.
The
more
interesting
part
is
the
target
so
for
a
target
you
can
specify
what
is
my
group
reversion
kind
and
object,
or
we
can
specify
what
is
the
match?
Annotation
a
label
selector.
C
C
A
Yeah,
but
that
should
not
change
the
type
of
the
patch.
The
pastor
you
wrote
inside
of
the
path
to
Padgham
will
be
always
there.
There
is
no
difference
in
the
patch
structure,
because
either
you're
using
strategic,
merge
parts
which
has
a
different
form
than
the
Jason
patch.
You
can't
mix
and
match
those
two
nor
apply
SMP
and
then
say
this
is
a
Jason
patch
because
it
won't
work.
A
C
C
A
C
C
A
I
I
would
really
like
to
see
some
of
the
outcomes
of
the
SiC
work
to
influence,
keep
CTO
at
the
end
of
at
some
point
in
time,
because
I
do
hope
that,
even
though
the
usability
I
will
be
touching,
sig
apps
will
be
touching.
The
web
UI
part
I,
think
cube.
Cto
will
be
the
biggest
consumer
of
the
advices
from
the
sake
usability.
A
It
still
hasn't
been
fully
completed.
It'll
probably
take
some
more
time
to
get
the
yeah.
This
thing
running
but
I'm
guessing
I'm,
not
sure
if
I'll
be
able
to
personally
attend
the
additional
estate
meetings,
but
it
would
be
good
if
some
of
us
and
I'll
definitely
ask
members
of
sig
usability
to
report
back
to
the
our
sick
from
time
to
time
with
regards
to
eventual
guidelines
or
requirements
that
would
like
to
see
being
applied
within
the
QC
deal
as
I'm
thinking.
The
cube
see
deal
has
a
lot
of
things
that
we
can
improve.
A
A
F
A
A
B
Minutes
so
there's
really
not
much
to
report
with
the
coop
cuddle
independence,
although
we
definitely
will
have
plenty
of
bars
coming
out
as
soon
as
we
unfreeze.
Maybe
today,
maybe
tomorrow,
whenever
the
unfreeze
happens,
I've
already
started
some
PRS
to
move
some
of
our
our
most
our
most
independent
chunks
of
code,
which
is
basically
a
package
coupe
cuddle
you
till
which
everybody
else
depends
on
moving
that
first
to
staging
and
then
some
the
things
that
depend
on
that
matcha
was
mentioning.
B
Now
the
ability
to
the
last
one
is:
is
the
printing
we're
relying
on
internal
objects
on
printing,
but
we're
going
to
actually
remove
that
dependency?
Now
we
can
now
at
116
we
can
assume
server-side
printing
according
to
Jordan,
so
so
that
PR
will
be
coming
out
and
I'll
probably
have
to
clean
up
a
bunch
of
tests
with
that,
but
that
will
be
coming
out
soon
as
well.
Those
are
the
three
areas
remaining
once
we
get
those
three
areas
and
everything
can
go
into
staging
and
we'll
have
our
own
repository.
A
B
B
B
F
F
Landing
page
pretty
soon,
today
or
tomorrow,
we
actually
got
a
big
tweet
to
two
out
of
about
of
pucon,
and
I
started
to
blog,
and
so
we've
actually
had
a
bit
of
momentum
with
three
hundred
and
thirty
stars
now
about
sixteen
hundred
claps
and
followers
on
the
medium
blog.
So
returning
to
get
some
books
momentum,
there
I
think
so.
Yeah,
that's
making
pretty
good
progress.
All
friends
a
lot
of
refinements.
D
F
A
If
you're
new
to
sixty
line
meetings,
I
just
posted
the
link
to
Kui,
if
you
haven't
checked
that
one,
yet
you
should
definitely
go
look
through
our
meeting
notes.
Nick
has
done
a
very
awesome
introduction
into
Kui
a
couple
weeks
back.
The
recording
is
definitely
somewhere
on
YouTube
already,
so
you
know
just
scroll
through
the
again
then
find
Kui.
It
should
be
there
and
just
watched
and
see
if
you
haven't
got
a
chance,
definitely
give
it
a
try
on
yourself
thanks.
F
Migi,
the
UI
is
pretty
dramatically
improved
since
then.
Now
that
the
tabs
look
like
conventional
tabs,
the
we
have
tap
completion
actually
so
cross-platform
to
add
completion
of
kubernetes
resource
names
and
namespaces
and
get
branches.
You
know
so
we're
really
starting
to
refine
and
Richard
sent
census
videos.
So
we,
while
the
blogs,
cover
some
of
the
new
features,
but
the
intention
is
really
start.
This
cadence
of
announcements
and
and
blogging
because
we're
going
to
be
pretty
rapid
progress.
F
A
G
H
A
B
H
A
Good,
that's
good
I,
don't
think
we
have
any
first
time
issues
we,
we
should
probably
work
on
it,
I'm,
hoping
that
we'll
have
some
more
time
later
this
year
to
actually
structure
the
amount
of
issues
that
we
have
overall.
A
A
It
might
take
me
some
time
to
go
through
my
slack
if
I'm
a
little
bit
behind
with
all
the
alternate
notifications
currently
and
the
worst
part,
is
that
I'll
be
leaving
for
PTO
within
the
next
two
weeks.
So,
if
and
and
and
what
Shawn
just
said,
he
will
be
out
as
well.
So
please
don't
get
done
run
away.
If
we
don't
speak
during
the
month
of
July,
because,
as
you
probably
expect,
a
lot
of
people
will
be
out
and
moving
back
and
forth
due
to
holiday
season.
H
A
A
Okay,
I
think,
since
there
are
no
other
topics,
questions
or
concerns
that
people
have,
we
might
want
to
close
this
meeting
earlier
today,
I'm
gonna
give
you
back
about
15
minutes
of
your
time.
Thank
you
very
much
for
joining
the
meeting
and
see
you
in
a
couple
of
weeks,
because
I'll
be
out
the
next
time
you
guys
all
meet
she'll
be
back
and
in
August,
though.