►
From YouTube: Kubernetes SIG CLI 20190130
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
We'll
begin,
okay,
so
I
feel
a
nonsense.
For
today
the
1:14
enhancement
freeze
is
happening.
January
29,
so
keep
in
mind
of
that.
If
you
are
working
on
new
enhancements,
also
some
news
with
regards
to
coop
coral
independence.
We
now
have
a
logo
for
the
repo.
Once
we
establish
a
new
repo
feel
free
to
take
a
look,
I
think
I
can
pull
it
up
here.
It's
looking
really
nice
and
we'd
like
to
give
a
huge
thanks
to
Ashley
McNamara
for
her
work
on
the
logo.
A
Moving
on,
we
have
some
tough,
great
updates.
So,
as
you
know,
or
as
you
may
or
may
not
know,
anyone
you
know
who's.
A
member
of
the
sig
is
free
to
sign
up
for
ought
to
be
on
call
for
about
two
weeks
to
take
a
look
at
our
test.
Grid,
keep
track
of
any
flakes
or
any
intermittent
failures,
and
just
overall
keep
the
sig
up
to
date
with
what's
going
on
with
tests,
I
believe
for
the
past
two
weeks
we
had
Maggie
on
call
is
Maggie
here,
yeah
I'm,
here
perfect.
B
So
during
the
past
week
there
are
two
kind
of
instant,
so
one
was
there.
I
was
a
stock
heart
issue
on
GCE,
which
caused
our
a
lot
of
our
testing
broken.
It
was
resolved
and
they
are
green.
Another
instant
was
the
testing
in
AWS,
it's
broken,
it's
still
broke,
and
now
someone
is
working
on
that.
So,
in
the
other,
the
reason
is
that
the
ADA
last
product
is
running
out
of
credit
and
there
someone
is
putting
back
and
money
on
that
project
to
guys
since
running
so
I
have
up
that
document.
A
C
Yeah
I
can
take
this
topic
so
basically,
currently
our
plugin
mechanism
that
we
have
implemented
always
searches
your
plugins
in
the
past.
In
your
execution,
which
basically
means
every
binary
with
a
cube,
CTO
prefix,
is
automatically
discovered
in
path
and
that
gets
turned
into
a
cube.
Cto
bugger
there
was
a
proposal
to
have
a
additional
directory
under
home
user
home
directory
q.
C
/
plugins
were
cited
from
the
path.
We
would
also
look
for
the
same
pattern.
The
benefit
of
this
approach
would
be
that
we
would
have
a
central
place
where
you
could
keep
all
your
cube.
Cto
plugins,
honestly
I,
don't
see
any
downside
of
this
approach.
It
definitely
makes
the
the
plugins
even
more
usable,
so
I'm,
just
looking
for
opinions
with
others.
It's
members
think
whether
it
is
okay
to
include
that
directory
and
a
search
path
or
cube.
Cto
plugins.
If
I
don't
see
a.
C
D
This
is
Matt
Farina
here
this
the
whole
plugins
and
where
you
put
them,
is
a
recent
thing.
We've
been
dealing
with
on
helm,
because
one
of
the
use
cases
that
has
come
up
is
yeah
you,
you
have
them
locally,
you
install
them,
but
sometimes
you
want
to
install
system-wide
plugins
right
and
in
some
environments
people
don't
even
have
access
to
install
the
plugins
it's
installed
by
an
administrator
into
a
higher
level
directory,
and
so
this
has
been
an
ask
and
I'm
trying
to
remember.
D
I'd
have
to
dig
it
up,
but
we
actually
had
specific
use
cases
and
organizations
that
wanted
this,
and
so
you'd
have
the
hierarchy
of.
Where
do
you
put
them?
And
how
does
that
work?
And
so
one
of
the
things
we
started
to
look
at
over
there
and
we
can
do
breaking
changes
right
now
in
home
is
actually
using
the
xdg
standard
on
this
I
just
dropped.
A
link
into
chat
here,
and
the
idea
was
is
here:
is
a
standard
around
the
hierarchy?
Should
work
in
a
system.
D
So
that
way
you
could
have
them
say
in
your
home
directory.
You
could
have
them
in
a
system
directory
and
here's
the
standard
for
how
the
hierarchy
works,
so
you
can
have
more
than
one
place
to
stick
that
plugin
and
have
stuff
worked
and
because
there's
some
other
use
cases
out
there,
and
so
I
would
say.
Since
we
ran
into
this
and
we
started
off
with
that
plug-in
directory
over
in
helm.
D
C
To
follow
the
sender's
if
we
already
have
summon
and
in
place-
and
definitely
one
of
the
concerns
that
were
raised
in
the
original
issue
at
length
in
the
agenda-
was
that
the
users
do
not
have
the
ability
to
install
system-wide
binaries.
That's
why
they
want
to
have
a
user-defined
directory,
so
I'm
I'm
hearing
your
voice
as
yet
another
plus
one
supporting.
The
idea
is
just
to
follow
the
senator
yeah.
D
And
it's
a
little
different
from
what
coop
does
today
so
I'm,
not
sure
it
would
fall
out,
but
you
could
probably
do
something
very
similar.
The
details
are
in
there.
I
haven't
mapped
it
to
Windows
and
you'll,
see
it's
it's
a
on
the
freedesktop.org
site,
so
I
think
it
may
be
more
POSIX
base,
but
I
know
others
have
mapped
this
whole
thing
to
Windows,
and
so,
if
you
go
beyond
it,
you
can
find
implementation
details
and
where
people
have
put
things
in
Windows
and
how
that
works
for
the
same
kind
of
thing.
D
A
No
I
mean
I
could
also
see
us
doing
a
mixture
of
this
standard,
plus
the
default
directory.
Possibly-
and
you
know
home,
that
cube
plugins
just
in
case,
we
cover
all
our
bases,
yeah
I,
you
know
personally,
I
would
be
also
in
favor
of
making
people's
lives
easier.
When
you
know
deciding
where
to
install
plugins.
A
C
C
So
that's
even
worse
than
than
the
initial
thing
that
I
stated
so
I
think
our
sick.
Since
when
do
you
care
about
the
fact
that
we
want
to
maintain
backwards,
compatibility
sorry
for
those
sort
of
noisy
place?
So
definitely
we
want
to
ensure
that
the
backwards
compatibility
works
from
the
threats
are
happening
between
sick
architecture
and
six
CLI
brand.
Even
once
want
us
to
have
a
n
minus
two
for
backwards
compatibility.
So
I
think
it
is
reasonable
to
straighten
out
the
tests
great
and
are.
E
C
E
C
I'll
have
a
look
at
that
get
history
for
that
file
and,
if
not
then
I'll
just
reach
out
either
to
earn
or
stis
and
try
to
figure
out
how
to
update
it
properly
so
that
it
actually
performs
what
we
what
we
will
be
wanted
it
to
test
for
114.
My
goal
would
be
that
we
have
these
tests
and
minus
one
if
we
set
it
up
in
time
for
114
to
the
N
minus
2
awesome.
If
not,
they
will.
C
C
G
H
A
C
C
A
F
Yeah,
hello,
everyone.
This
is
Jim
from
Easter,
okay.
So
currently
we
have
an
open
PR
for
integrate
customized
into
cube
cattle
as
a
sub
command,
and
we
have
finished
the
other
work.
Almost
there
is
only
one
blocking
issue
which
is
to
decide
if
we
want
to
require
API
version
unkind
in
customization
file,
so
I
want
to
share.
F
Okay,
so
in
we
have
an
issue
tracking
the
discussion
and
allowing
a
conversion
kind
of
as
absent
over
the
query.
Most
fields-
and
the
discussion
involves
certain
parts.
First-
is
what
is
the
proper
API
version
and
proper
name
for
those
fields?
And
finally,
we
define
that
you
have
this
as
an
accompanying
customized
of
config
dot
k
a
style,
as
the
version
will
be
we
1
beta
1.
The
cans
name
will
be
customization
with
capital
K.
F
So
that's
the
the
values
for
those
fields
and
now
do
we
need
to
require
those
fields
we
tend
to
allow
them
to
be
present,
since
in
this
case
we
can
support
our
current
customized
user.
They
won't
see
the
breaking
changes,
but
we
do
see
that
if
we
require
those
API
version
and
can't
there
might
be
some
other
benefits,
we
can
get
from
it.
I.
I
Guess
my
main
question
would
be:
are
we
using?
Are
we
loading
these
files
using
the
API
machinery
loading
mechanisms?
Ok,
if
we
are
not,
then
I
don't
have
strong
opinions
either
way.
I
would
like
to
know
what
the
plan
is
or
versioning
documenting
that
like,
if,
if
there
were
changes
that
needed
to
be
made
in
the
future,
what
would
our
plan
B
would
it
be
to
grab
the
version
and
then
start
requiring
explicit,
b1
and
a
few?
I
J
So
we
could
write
it
down,
make
that
into
a
way
a
web
page
on
the
site,
for
example.
So
far
all
we've
been
doing
is
on
the
infrequent
occasions
when
we
went
to
deprecated
a
field,
we'll
figure
out
some
migration
pattern
for
the
field.
If
that's
possible
market
deprecated
provide
warnings
and
then
at
some
point
cut
it
off
so
far
we
haven't
cut
anything
off.
Yet
we've
just
been
marking
things
as
deprecated.
It's
pretty
much
the
way
we,
you
know,
treat
proto
buffers
inside
Google,
so.
J
J
I
I
I
J
J
I
The
fact
that
you
have
history
on
some
of
these
sort
of
inflates,
migrations
or
in
place
you're
taking
up
the
old
and
transforming
it
to
the
next
revision.
That's
helpful
to
point
to
an
example
of
what
has
been
done
in
the
past
and
what
is
anticipated
to
be
done
in
the
normal.
Hills
may
be
helpful.
Yeah
sure
the
update
to
protect
remote
bases,
the
transitive
stuff
that
actually
get
pulled
into
the
pull
requests
in
progress
and
kubernetes,
or
does
that
need
to
be
refunded.
I
saw
a
merged.
F
J
A
C
Two
weeks
ago,
there'll
be
refactoring
back
package
keep
CTO
there
are.
There
are
a
few
leftovers
from
the
cleaning
that
we
did
and
the
previous
release
and
the
previous
release
I
started
doing
the
cleaning
it's
the
PR
I
have
only
globally.
It's
a
mess.
I'll
try
to
clean
up
within
the
next
weeks
and
put
it
together
and
submit.
If
you
are.
A
C
G
Yeah
for
context,
if
I
put
for
context,
I'll
publish
things
to
the
loneliness
the
eyes
on
them,
everyone
listens
they're,
getting
up
notifications
or
checks
those
regularly,
especially
people
who
don't
get
this
time.
The
issue
might
not
have
an
easy
way
of
finding
him.
So
I,
try
and
just
published
the
mailing
list,
because
I
think
a
lot
of
people
out
needs
your
time
managing
their
mail
and
can
set
up
filters
more
effectively
there.
A
discussion
should
always
happen
on
PR.
A
I
I
had
one
we
talked
for
a
while
about
having
a
way
to
service
warning
information
to
users,
whether
it's
in
response
to
use
of
deprecated
API
is
or
fields
or
unknown
fields,
or
using
like
an
out
of
out
of
support,
cube
control
version.
There
there's
just
a
lot
of
different
reasons.
We
might
want
to
service
information
to
users.
I
have
a
work
in
progress,
kind
of
proof
of
concept,
exploratory
pull
request,
I,
intended
to
get
that
into
an
efficient
proposal
for
114
and
didn't
make
it
so.
I
Let
users
know
hey
you're
using
a
thing:
that's
gonna
break
in
a
release
or
two,
instead
of
them
finding
out
after
they
upgrade
so
the
more
we
can
do
to
surface
the
current
state
of
what
a
users
depending
on,
especially
if
they're,
depending
on
old
things
that
have
been
announced.
You
know
as
deprecated
and
are
going
away,
but
not
everybody
reads
a
hundred
pages
of
release
notes,
understandably
the
better
so
I
will
link
to
that
and
no
no
action
required
now.
But
if
you
have
thoughts
or
feedback
I'll
be
great.