►
From YouTube: Kubernetes SIG CLI 20190116
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
A
Other
interesting
stuff
is
there
is
a
new
worker
being
formed
that
will
affect
six
CLI,
which
is
designed
to
discuss
the
topic
of
supporting
of
yes,
which
will
be
very
important
topic,
especially
when
we
will
extract
keep
CTO
to
its
own
repository
other
will.
This
will
affect
us
significantly,
so
we
need
to
carefully
look
at
the
outcomes
of
that
working
group.
Finally,
there
was
a
blog
post
about
gypsy
TL
diff
on
humanities.
That
I
know
so
definitely
check
this
one
out
on
to
the
next
topic,
which
is
a
test
grid.
A
A
A
B
C
Alright,
so
yeah
we're
gonna,
give
an
update
on
customized.
We
are
so
the
current
state
of
customize
is
that
we
merged
a
PR
I
think
two
weeks
ago.
You
know
it
was
more
than
that
before
right
after
Kuk
on
which
had
customized
integration
into
the
resource
builder,
and
that
discussion
happened
on
the
PR.
The
cap
actually
had
it
as
a
sub
command,
and
so
there
is.
C
We
realized
that
not
everyone
got
to
participate
in
that
discussion
about
what
the
precise
UX
looks
like,
because
it
happened
on
the
PR
and
not
the
kept,
and
so
another
thing
we
realized
was
that
some
of
the
customized
functionality,
for
particularly
for
generating
secrets,
actually
would
be
a
surprise
to
users
and
potentially
a
security
issue,
because
users
might
not
realize
what
they're
running.
So.
C
We
think
we
want
that
regardless,
like
because
customized
like
processes,
files,
folks,
you're
gonna,
want
to
debug
and
experiment,
and
we
want
to
be
able
to
teach
users
about
how
this
stuff's
working
and
having
a
command
that
it
just
takes
in
the
customization
file
and
then
does
the
customizations
on
top
of
it.
It
shows
us
to
the
user
makes
a
lot
of
sense
to
have
in
there,
but
we
also
believe
that
we
can
get
a
much
better
experience
from
having
deeper
integrations
this.
D
C
Look
at
the
question
in
a
sec,
but
that
is
the
goal
that
is
the
UX
we
want.
It
provides
the
ability
to
do
more
interesting
things
like
tie
back,
maybe
errors
in
the
stuff
that
is
generated
from
customized
to
the
actual
files
and
file
numbers
where
that
error
came
from
and
these
sorts
of
things,
so
that
is
where
we
want
to
get.
We
will
do
that
as
a
separate
kept.
The
reason
is:
there's
UX.
We
want
to
discuss
there
and
just
a
lot
of
more
discussion
around
how
that
integration
is
going
to
work.
C
The
introducing
a
sub
command
is
pretty
straightforward,
since
customize
is
written
as
King
Cobra
as
a
command
already,
where
is
the
resource
builder
code
to
something
we
want
to
make
sure
we
keep
really
clean
and
UCL
runtime
is
code.
We
want
to
make
sure
you
want
to
keep
really
clean,
and
so
how
do
we
actually
bring
these
two
libraries
together?
C
We're
talking
about
customize,
this
is
the
right
spot.
If
you're
talking
about
scope
of
the
project,
which
is
kind
of
a
cross-cutting
thing
and
scope
impacts,
every
single
sake,
then
steering
committee
is
we're.
Not
sorry,
not
strictly
Sieg
architecture
is
the
right
location.
Steering
committee
is
not
the
right
location
for
either
one
of
those
things
so.
F
This
is
my
frame
just
to
jump
in
real,
quick,
just
to
add
to
what
David
asked
for
I
think
the
I
didn't
add
in
them
to
the
agenda.
I'm.
Sorry,
I,
didn't
the
points
were
actually
around
documentation
and
material
for
people
who
are
gonna.
Go
because
if
I
understand
the
customized
functionality
and
customization
yamo
was
baked
into
the
CLI
runtime
package,
and
so
there's
lots
of
projects
not
just
coop
control
that
consume
that,
and
so
one
of
the
things
that
would
be
the
ask,
is
about
documentation
and
material
for
consumers
of
that.
F
So
they
know
how
to
leverage
it
or
not,
depending
on
what
they
want
to
do.
What's
that
experience
was
one
of
the
asks
in
those
conversations
just
to
kind
of
fill
out
the
well-rounded
thing
of
I'm,
a
consumer
of
a
package
that
kubernetes
uses.
How
do
I
go
about
consuming
that
and
working
with
it
yeah.
C
Matcha-
and
one
do
you
know
where
we're
at
with
GL
a
runtime,
because
the
way
I
remembered
it
was,
is
that
we
are
publishing.
We
have
an
intention
right
to
get
the
coo
control
libraries
out
and
we're
in
kind
of
in
the
middle
of
moving
to
control
out,
but
until
control
has
actually
been
moved
out
of
kubernetes
all
of
the
repos
and
stuff
we're
creating
are
not
like
they're,
not
things
while
they
are
available
publicly
much
like
the
code
inside
kubernetes
is
available
publicly.
A
Not
that
worth
more
supportable
yeah,
that
is
correct.
We
extracted
those
as
part
of
the
overall
QC
of
extraction
out
of
the
main
repo.
We
do
publish
them.
We
are
the
initial
consumers
within
cube,
CTO
itself,
but
we're
more
towards
alpha
stage
rather
than
beta
or
GA,
for
god
forbid,
because
we
are
not
100%
sure
whether
the
current
contents
is
too
full
the
full
functionality
that
we
want
to
allow
people
to
use
that
hasn't
been
fully
fleshed
out,
and
until
that
happens
we
will
be
publishing
it.
A
F
So,
just
to
add,
on
top
of
that,
I
learned
on
the
list
anyway,
that
there's
two
projects
I
wasn't
aware
of,
are
actually
consuming
this
already
for
their
own
purposes.
Is
it
documented
anywhere
that
there's
a
lot
of
undocumented
things?
This
is
alpha
quality.
Is
that
actually
documented
for
them,
as
consumers
of
it,
I
was
surprised
there
were
projects,
I
didn't
even
realize.
People
are
already
consuming
this
and
using
this
in
their
own
ecosystem
projects.
So.
A
That's
fine
that
very
consuming
it.
It's
just.
We
we're
not
saying
clearly
that
this
is
a
supportive
feature.
We
will
try
hard
not
to
break
it
in
a
way
that
it
won't
be
backwards
compatible
because
we
are
the
first
consumers
of
it,
so
we
will
make
hard
use
of
it,
but
we
are
not
giving
this
as
a
hard
guarantees.
I
think
I,
think
Matt.
C
Your
point
yeah
look
looking
at
the
page,
I
see
that
sorry
I
know
looking
at
the
page
like
it's
not,
this
is
one
could
come
to
this
page
and
be
like.
Oh
awesome,
a
library
exists
for
me
to
use
right
and
not
realize
that,
like
that,
there's
no
support
for
this
thing
and
we
don't
like
we're
not
ready
for
other
people
to
use
it
unless
they're,
just
like
you
know,
ripping
all
the
safety
yards
off
right,
yeah.
F
And
like
if
I
go,
look
at
the
releases,
I
see
a
one
dot
13.2
release.
So
if
I
don't
know,
the
context
of
this
I
may
not
realize
that.
Oh,
this
package
is
really
not
an
ecosystem.
Consumers
are
not
necessarily
on
the
inside,
knowing
what
we
know
they
made.
You
say:
look
at
this
thing:
it's
version
113,
that's
stable,
that's
great
and
because
it's
version
with
it
looks
like
kubernetes
yeah.
B
A
So
if
you,
if
you
go
to
the
readme
of
of
the
package,
one
of
the
first
things
that
the
compatibility
is,
we
are
clearly
saying
there
are
no
compatibility
guarantees
for
this
repository.
It
is
direct
support
of
kubernetes,
so
branches
will
track
kubernetes
and
be
compatible
with
that
repo.
As
we
more
cleanly
separate
the
layers,
we
will
review
the
compatibility
guarantees
so.
G
B
C
G
F
And
eventually,
I
would
love
to
see
documentation
that
tells
folks
how
to
do
it.
I
understand,
given
the
number
of
people
on
it,
that's
a
tall
order,
and
if
you
say
you
know,
this
is
not
release
people
don't
necessarily
have
that
kind
of
expectation,
but
I'm.
Just
thinking
of
the
concerns
of
that
ecosystem,
consumer
consuming
a
library
and
that's
how
they're
gonna
see
it,
and
as
long
as
we're
clear
with
that
that
would
really
help
people
I
think
and
yeah.
It's
a
price.
There
are
people
using
this
in
their
production
applications.
How.
C
Can
we
maybe
get
help
from
the
people
who
want
to
use
this
like
I
got
I
think
maybe
that's
like
a
great
place
to
contribute
is
documentation
because
it's
kind
of
a
low
bar
and
we'd
love
to
take.
You
know.
I
bet
we
could
even
I
bet.
One
of
us
could
even
spend
half
an
hour
walking
someone
through
the
thing
if
they
would
then
willing
to
document
that
I'm
trying
to
sure
if.
A
They
are
already
consuming
it,
I
might
know
even
better
than
we
are,
so
any
efforts
on
improving
the
documentation
on
the
on
these
beat
on
the
on
these
bits
would
be
highly
appreciated.
So
if
you
mat
know
folks
that
are
actually
using
this
consuming
it
that,
most
importantly,
have
some
feedback
with
regards
to
the
functionality.
A
A
C
Point
if
we're
publishing
it
for
plug-in
authors,
we
should
be
clear
to
the
plug-in
authors
that
like
hey
this
is.
This
is
way
better
than
nothing
like.
Nothing
needs
to
bad
spot
to
be,
and
this
is
way
better
than
binnorie
combination.
Kubernetes,
that's
what
we're
spot
to
be
in.
Yes,
it's
not
we're
not
like
hey.
We
have
a
plug-in
SDK
expended.
A
G
A
H
You
it's
just
a
real,
quick
question
and
and
I
apologize.
If
you
addressed
this
earlier
when
talking
about
customized,
but
I,
think
that
some
of
the
discussion
around
this
was
presumed
that
coop,
CTL
or
coud
cuddle
or
however
you
pronounce,
it
is
taking
the
direction
that
everything
is
going
to
turn
into
a
plug
in
one
day,
like
we've
got
this
plug-in
mechanism,
it's
great.
H
It's
awesome,
we'll
just
use
that,
for
everything
and
I
feel
like
there
are
probably
some
technical
reasons
that
customized
was
not
implemented
as
a
plugin
and
I
would
just
kind
of
be
curious
about
the
state
of
plugins
today
like
if
they
really
are.
This
super
solid
thing
that
we
can
lean
on
or
if
we
still
have
some
progress.
That
needs
to
be
made
that
the
community
could
help
with
a.
A
Actually,
we,
as
of
today,
we
are
very
happy
with
the
current
state
of
the
plug-in
mechanism
and
that's
what
I'm
gonna
focus
and
I'm
gonna
pass
over
to
Phil
so
that
he
can
expand
on
the
customized
plugin
apart.
So
the
plugin
mechanism
by
itself
was
proven
to
be
working
just
fine,
both
from
the
discussion
that
I
had
in
during
cube
con
past
month
and
overall
from
the
feedback
that
we
gathered.
A
So
then
we
actually
are
moving
the
plug-in
mechanism
to
GA
because
it
was
beta
in
113
and
we
will
be
GA
ting
that
in
114,
unless
I'm
gonna
hear
some
major
objections
that
I
have
not
so
far.
So
the
plugin
mechanism
is
stable
and
it
is
I,
wouldn't
call
it
rock
solid,
but
we're
very
happy
with
the
outcome
of
the
plug-in
mechanism
itself.
So
I
hope
that
that
is
are
part
of
your
question.
I'm
gonna
pass
over
to
say
it.
A
C
Sure
I'll
just
say
that
II
like
when
we
talk
about
building
could
control
itself
as
plugins.
That
can
mean
a
lot
of
different
things
and
there's
like
aspirational
visions
right
where
you
have
like
all
the
code.
Control
is
actually
just
plugins
and
we
have
this
great
distribution
mechanism
and
we
can
update
different
sub
commands
at
different
release,
velocities
and
patch
them
independently
and
like
do
all
this
stuff
and
like
it
gets
a
cool
vision
to
think
of
there's.
C
Also
like
the
practical
matter
of
like
what
benefit
do
we
or
anyone
else
get
from
making
a
specific
command
a
plug-in
right
and
practically
right
now.
That
means
we
don't
get
any
benefit,
but
it's
much
harder
for
us
to
distribute
and
it's
a
larger
binary
for
people
to
download
I
have
this
conversation,
but
I
was
actually
all
in
on
the
like
all
plugins
vision.
A
year
ago,
I
talked
with
Clayton
at
Keuka
in
Austin
and
he's
like,
so
how
big
is
coop
control,
50
megabytes?
Okay,
how
many
commands
do
you
have
about
about
40?
C
Okay,
so
you
distribute
so
and
they're
all
about
the
same
size
right
because
most
of
the
code
size
is
vendor
door
like
static
right,
so
each
one
ends
up
being
about
50
megabytes.
So
now,
when
someone
wants
to
download
coop
control,
it's
a
two
gigabyte
file
instead
of
a
20
or
50
megabyte
file
right,
so
it's
like
so
then
that
led
to
well
git.
Does
this
actually
with
similes
okay?
So
now
we
compile
everything
into
the
same
binary.
C
It's
just
similes
into
the
same
binary
right
which
at
which
point
you
get
to
what
are
we
really
doing
for
ourselves
right,
we're
creating
a
bunch
of
sim
lights
to
exercise
the
plug-in
mechanism,
and
so
the
vision
doesn't
make
much
sense
unless
we're
getting
like
concrete
value
out
of
it
and
so
I,
don't
think
we're
gonna
build
anything
as
plugins
until
we
have
like
an
actual
benefit.
We
get
from
building
that
thing
as
a
plugin,
because.
F
So
one
tool
can
export
the
yeah
mol
and
proper
formatting.
Another
tool
can
import
it,
transform
it
export
it
again.
Another
tool
can
do
the
same.
There's
things
like
that
or
act
on
it.
Have
you
thought
much
about
the
philosophy
around
how
you
do
extensibility,
because
that's
kind
of
three
different
things
there?
Yes.
C
We
have
an
in
do
you
mind
if
I
cut
this
since,
since
we're
about
thirty
minutes
in
the
meeting
and
there's
a
couple
items
on
the
agenda
and
we
haven't
actually
done
intros
I
want
to
make
sure
people
who
came
here
like
with
something
on
the
agenda
actually
get
to
talk
to
it.
So
maybe
we'll
wrap
this
up.
Yes,
yes,
we
have
Matt
the
extensibility
we've
been
thinking
about
Moore's
like
we're,
starting
with
data-driven
commands.
I.
Think
that's
like
actually
something
we
understand
pretty.
C
Allow
websites
to
you
know,
provide
arbitrary
applications
without
having
to
download
that
stuff
right
is
that
you
establish,
you
know
a
format
for
publishing
the
functionality
and
then
the
browser
interprets
it
and
looking
at
coop
control
more
like
that,
other
plugin,
you
know
I
think
we'd
be
open
to
more
and
more
conversations
about
this,
but
we
do
when
I
like
we
are
focusing
on
like
what
are
the
simplest
biggest
hit
ways.
We
can
provide
users
the
ability
to
do
what
they
want
specifically.
H
H
If
we
talk
about
trying
to
extract
functionality
out
of
a
commonplace
is
such
that
other
people
such
that
there's,
like
a
level
playing
field
and
everybody
sort
of
operates,
the
same
more
versus
ecosystem
versus
non
core
that
the
effort
to
do
this
for
cloud
providers
is
the
other
model
that
comes
to
mind
pretty
quickly
and
I
feel
like
the
reason
that
that's
progressing
is
because
the
people
who
have
skin
in
the
game
are
actively
participating
in
you
know
what
the
best
way
to
to
provide
that
extensibility
is
I,
have
concerns
that
I
hear
a
dialogue
of
we
and
have
you
considered
and
I
would
love
for
there
to
be
of
more
continual
discussion
between
the
people
who
had
such
strong
opinions
on
customized,
because
I
think
this
is
a
great
forum,
for
you
know:
finding
the
right
boundaries
finding
the
right
places
for
extensibility.
C
That's
a
really
great
point:
Aaron
like
you
would
it
would
be
a
huge
difference
if
the
folks
that
really
want
like
we
have
like
a
lot
of
people
building
API
is
ok.
I
want
to
be
able
to
do
coop
control,
crate
or
whatever,
but
you
know,
without
those
people
actually
showing
up
or
or
willing
to
contribute,
it's
it's
gonna
be
slow
and
maybe
not
what
maybe
not
necessarily
as
good
of
an
outcome
as
it
could
be.
Otherwise.
So.
E
I
also
have
to
leave,
but
I
wanna.
Also
echo
Aaron's
point
I.
Think
it's
a
good
one.
I've
looked
back
at
the
multiple
projects,
slack
mail
or
slack
list,
and
there
is
almost
no
discussion
about
the
other
projects
like
if
you
look
at
the
customize
Channel
there's
like
a
half-dozen
questions
about
helm
and
they
basically
say:
well,
we
don't
really
know
about
helm,
and
then
you
go
to
the
helm
channel
you
search
for
customize,
it
doesn't
come
up
and
I've
talked
to
people
in
the
helm
community
about
customize
and
again.
E
F
Yeah
I
tend
to
agree
with
this,
so
there's
a
lot
of
projects
doing
a
lot
of
different
things
as
soon
as
you
step
outside
of
the
kubernetes
api
and
they're
doing
things
in
different
ways:
they've
got
shared
code
libraries.
Sometimes
they
have
entirely
different
processes,
sometimes
they're,
just
crazy,
bespoke
processes.
Sometimes
there's
commonalities
to
them.
F
C
And
maybe
we
could
have
like
PM's
or
or
this
sort
of
stuff
like
like
we're
we're
short-staffed
in
terms
of
execution
as
it
is
right
and
if
we
were
to
say,
pull
off
half
the
team
from
getting
coop
control
out
of
kubernetes
kubernetes
to
just
like
focus
on
engagements
like
I.
Think
that
would
not
necessarily
get
us
where
we
need
to
be
so.
Maybe
there's
an
opportunity
for
folks
who
excel
in
other
roles
to
come
to
come
help
and
facilitate
that
dialog.
F
A
I
was
about
to
propose
that
if
you
want
to
open
to
this
question
about
this
topic,
particularly
maybe
I
started
a
mailing
threat
to
the
60
Li,
maybe
look
in
sick
architecture
and
and
we
can
continue
the
discussion
over
there
and
so
that
we
can
focus
on
on
the
other
topics
that
we
have
in
the
agenda,
especially
that
I
know
there
is
one
person
knew
that
is
I
wanted
to
discuss
a
an
issue
that
he
wants
to
work
on,
so
I'm
gonna
right
break
it
here.
Well,.
A
Gets
a
chance
to
I
was
I
was
hoping
that
we're
gonna
do
interest
as
part
of
these
stand.
Ups
that
we
do
towards
the
end
of
the
meeting
like
we
usually
do.
Okay,
maybe
we
should
rethink
the
stand
ups
as
one
of
the
initial
steps
and
not
towards
the
end,
but
honestly,
both
both
ways.
Work
worked
fine
for
me,
but
since
today
it
wasn't
done
at
the
beginning.
So
let's
move
it
over
to
towards
the
end
of
the
as
usually
so.
C
George
that
speak,
you
I.
This
is
from
Twitter.
Actually
someone
on
Twitter,
you
know
wanted
to
talk
about
the
different
formats
and
how
do
we
make
sure
that
a
coop
control
is
able
to
consume
like
home
templates
or
other
formats
casein
that
or
whatever
it
is?
How
do
we
make
sure
that
there's
good
interoperability
here
and
so
added
to
the
agenda
based
on
that?
Okay,
George?
Isn't?
If
no
one
here
is
gonna
speak
to
this
topic,
I
suggest
we
just
delete
it
and
move
on
okay,
yeah!
That's
the.
F
C
D
Yeah
I'll
just
kind
of
introduce
myself
I'm
I'm
Matt
I
work
at
Beatport,
we're
kind
of
a
music
streaming
service
for
DJ's,
but
I
think
I'll
get
into
that
when
we
talking
to
stand-ups
just
to
kind
of
address
the
issue
that
I'm
I'm,
hoping
to
kind
of
make
my
first
contribution.
This
issue
is
addressing
kind
of
limitations
with
custom
columns
in
the
get
sub-command
so
with
custom
columns.
D
Currently,
when
you
provide
custom
columns
to
that
flag,
you'll
end
up
with
a
set
of
columns
that
you
provide,
but
only
those
columns
and
you
won't
be
able
to
see
any
of
the
default
columns,
and
so
some
of
the
suggestions
on
that
issue
word
that
we
could
add
another
flag
to
basically
force
the
default
homes
to
be
printed
as
well
as
some
custom
columns,
so
additional
so
similar
to
the
capital
L
flag.
We
could
add
a
capital
C
flag
that
would
add
custom
columns
to
the
new
columns
and
some
other
suggestions
were
provided
there.
D
D
C
G
G
You
know,
I
believe
right
now,
Kristen
columns
live
in
CLA
runtime.
Although
correct
me,
if
I'm
wrong
machi,
which
means
that
you
know
any
improvements
here
would
propagate
to
any
consumer
self
of
CLA
vinton
as
well
I,
don't
foresee
any
difficulties
or
issues
I
would
say
you
know
there
might
be
hesitation
on
maybe
some
people's
part,
because
we
would
be
introducing
a
new,
a
new
like
short
flag
and
I
know
those
have
been
in
the
past
to
twenty-twos.
G
B
A
G
A
J
K
There
there's
already
a
an
additional
printer
columns
functionality
I,
think
that
is
geared
towards
CR
DS
I,
wonder
that
that
sounds
you
know,
maybe
that
doesn't
I'm,
not
all
that
familiar
with
it,
but
maybe
that's
not
exactly
like
what
he's
asking
for
us
is
I'll.
Look
that
up
myself
in
the
codebase
and
see
how
that
fits
in
there,
something
already
in
the
code
base
for
that
additional
printer
columns
anyway,
I.
A
L
A
J
J
D
A
Okay,
final
topic
on
genre,
yeah,
yeah,.
K
So
I
just
wanted
to
bring
up
we've
already
that
this
exact
same
link
was
put
in
the
December
19th
meeting
and
it's
a
link
to
some
of
the
notes.
From
an
impromptu
meeting,
we
had
a
coupe
con
where
we
catalyzed
or
started
the
concept
of
looking
at
how
to
plan
long
term
and
we've
initially
come
up
with
about
five
high-level
areas
and
so
I'm,
hoping
that
my
ask
is,
for
all
the
participants
to
have
a
look
at
this
document
and
look
at
these
five
high-level
long
term
focus
areas
and
and
give
us
feedback
on.
K
You
know
which
focus
areas.
You
know
basically
on
what
what
we
think
on
this,
so
that
we
can
eventually
come
to
some
consensus
on
what
those
long-term
focus
areas
are,
so
that
we
can
begin
the
concrete,
long
term
planning
process
and
and
and
just
to
circle
back
the
the.
What
we're
hoping
to
do
is
is
get
consensus
on
which
what
are
the
high-level
areas
that
we
want
to
work
on
and
then
start
digging
into
each
one
of
these
individually
to
figure
out
how
we
would
address
them
and
so
for
it.
K
A
G
Basically,
you
know
as
part
of
one
of
the
commands
author
I
console,
we
have
to
focus
on
how
to
best
splitter
dependence
on
you
know
our
back
API
helpers,
our
back
storage
helpers
and
anything
that
goes
along
with
that
and
so
I
put
together
a
prototype,
and
here
I'll
link
it
now
but
I'll.
I
need
to
probably
titled
that
essentially,
my
hope
is
to
gather
visibility
for
this,
such
that
we
can
all
come
together
as
a
sig
and
decide.
G
M
Yes,
okay,
hey
hi,
sorry,
I,
don't
have
a
camera
right
now,
so
I
couldn't
show
you
show
you
guys
my
beautiful
face,
so
I
have
been
working
with
kubernetes
for
some
time
like
three
months
or
so.
I
work
in
a
company
called
a
ribbon
communications
I'm
based
out
of
Ottawa
Canada
and
I,
had
I
I
did
talk
with
a
fella
before
in
slack
and
I
I
wanted
to
work
on
an
issue
which
is
this
one
I.
Will
click
push
it
in
the
chat
box
right
now?
M
M
C
M
C
A
Or
expanding
functionality,
we
could
work
on
improving
the
show
completion
so
that
it
solves
the
initial
problems
so
that
he
only
typed
the
initial
couple
of
letters
of
the
pod
or
any
resource
name
and
the
rest
is
out
or
completed
if
it
is
a
possible
direction
of
this
issue
can
go
into,
and
since
this
is
an
old
issue
and
a
lot
of
topics
has
been
moving
and
has
changed
in
the
first
place,
it
would
be
good
if
you
could
propose
your
solution
during
one
of
the
next
meetings.
Maybe
what
would
be?
A
C
I
ask
quickly:
are
you
just
like?
Did
you
just
pick
this
issue
because
it
looked
like
not
that
maybe
maybe
a
good
starter
issue
and
you
wanted
to
get
started
or
is
this
like?
Where
you
do
you
feel
like?
Oh,
this
is
something
you
actually
want
to
solve,
because
if
you're
just
looking
to
get
started,
you
know
it's
possible
that
there's
we
might
be
able
to
give
you
something
better
than
this
one.
Given
that
you
actually
have
two
that
looks
like
this
solution
that
we
need
to
build,
isn't
straightforward
here.
It's
still
under
discussion.
M
M
If
there
was
something,
as
the
title
says,
if
you
see
teal
could
do
something
more
smart
and
as
soon
as
I
press
ENTER,
it
asked
me:
oh
did
you
mean
this
one,
then
press
one
or
or
if
you
want
to
just
delete,
for
example,
Q
3,
TL
q,
cuddle,
delete
pods
engine
X,
then
all
or
something
similar.
If
we
delete
all
the
pods
with
the
name,
engine,
X,
prefix
or
suffix,
or
something
prefix
would
makes
more
sense.
So
that's
how
I
started
googling
and
when
I'd
ended
up
in
this
issue
and
I
thought.
M
M
A
In
that
issue
and
show
up
on
one
of
the
next
sixty
line
meetings
and
in
this
constants
in
depth,
and
if
we
can
get
an
agreement
on
on
the
direction,
then
you
could
proceed
with
the
implementation.
I
want
to
I
want
to
ensure
that
the
entire
stick
is
okay
with
the
direction
that
you're
taking
this,
and
does
that
make
sense.
A
Is
kept
stands
for
kubernetes
enhancements
proposal,
which
is
a
document
that
lives
in
the
enhancements
repo
under
kubernetes
work
or
the
all.
The
proposed
changes
to
the
kubernetes
are
in
or
started
as
a
document
describing
the
proposed
changes
and
they
are
letting
over
there.
Although
the
majority
of
issues
caps
are
four
major
major
features,
not
sure
if
yours
is
set
one,
but
it
would
be
good
to
start
with
a
proposal
fully
described
in
the
issue
itself.
So.
M
A
M
A
That's
why
it
would
be
very
important
to
start
with
with
describing
your
approach
before
actually
implementing
it,
because
it
will
be
easier
for
you
to
sort
through
the
solution
and
as
well.
For
us,
it
will
be
easier
to
figure
out
whether
your
purpose
ocean
does
make
sense,
or
we
would
like
to
see
this
go
in
a
different
direction.
Does
that
make
sense.
M
A
C
A
A
Okay,
hearing
none
so
before
I'm,
gonna,
close
I'm
going
to
add
one
another
heads
up,
I'm
planning
to
do
some
major
shifting
inside
of
the
package
keeps
UTL
itself.
I
meant
to
do
it
before
when
we
were
closing
113
but
I
didn't
manage,
because
when
I
started
pulling
the
triggers
with
it
and
cleaning
the
package
keep
CTL
directory.
A
A
The
package,
keeps
ETL
described
version
at
describe,
structure
and
and
flatten
those
where
possible
and
and
generally
get
rid
of
a
couple
of
utils
that
that
live
in
package
keeps
you
deal
with
directory
and
either
split
them
into
separate
commands
that
are
actually
consuming
them
or
get
rid
of
those.
So
just
a
heads
up
that
there
will
be
some
major
refactoring
cleaning
going
on.
Okay.
So
with
that
I'm
gonna
close
the
meeting
for
today
and
see
you
in
two
weeks,
thank
you
all
right.