►
From YouTube: Kubernetes SIG CLI 20190313
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
B
C
B
A
A
A
A
D
A
A
E
D
The
time
and
as
we
go
then
to
the
more
deep
actual
truth
visualization,
you
see
I'm
like
so.
The
question
is:
can
we,
how
can
we
architected
so
that
we
can
allow
for
that
without
forcing
people
into
a
real
graphical
model
in
where
they
have
to
really
change
their
workflows
and
change
their
habits?
I'm
gonna
change
the
way
they
credential
I
logged
in
and
all
that
stuff,
so
I
thought
the
basic.
Basically,
the
realization
we
have
is
that
electron
I
think
is
that
it's
a
pretty
nice
technology
vehicle.
B
D
Demonstrated
by
quite
a
few
other
high
profile
projects,
all
aware
of
it'll
be
good
vehicle
for
allowing
along
women,
so
the
these
that
he
is
using
using
electron
as
a
foundation
for
delivering
these
graphics.
We
can
offer
to
our
developers
a
couple
of
different
modes
of
operation.
I
think
this
flexibility
is
a
key
part.
A
D
To
in
a
second
I'll
show
you
all
three
a
couple
of
these
modes:
the
first
is
that
I
call
it
the
pop-up
mode.
Ids
I
want
to
stay
in
my
terminal,
I
love,
my
terminal,
my
favorite
CSH
or
bash
and
I
turn
whatever.
It
is,
I'm
very
happy
with
that,
but
every
once
in
a
while
I
want
it
at
my
direction.
Make
a
foray
into
graphical
I
want
a
quick
pop
up,
so
I
can
see.
How
does
it
look
right,
close
the
pop-up
and.
D
D
Is
going
back
and
really
make
many
more
navigation?
Let's
approach
it
is
popular.
I
won't
talk
about
the
third
one
today,
but
just
to
mention
it
that,
because
it's
all
my
badly
of
the
option,
your
bunny
miss
and
a
browser
and
we're
actually
accessories-
have
explored
that
within
some
other
directions
and
there's
mixing
work
there
as
well.
But
I
want
like
when
you
think
today-
and
this
quickly
mentioned
that
that
is
that
there's
I
think
that
option
dope
the
options
I
think
for
us
are
a
wide
open.
After
that,
we
thought
about.
D
D
Can
explore
all
kinds
of
possible
possibilities
of
integration
based
on
this
is
called
yeah.
So
this
is
a
quick
list
of
the
new
and
notable
South.
If
you
might
in
case
you
just
you
can
sort
of
get
a
sense
of
the
progress
we've
made
over
the
past
six
weeks,
or
so
you
have.
The
ability
now
to
a
pretty
flexible
way
to
custom
client
builds,
so
you
can
external
to
the
main
cooing
repo.
You
can
add
your
own
repo
that
picks
and
chooses
that
core
plugins
you
want.
You
write
your
own
plugins.
D
D
D
So
stick
to
a
couple
of
these
scenarios.
Hopefully
I'll
show
you
some
of
the
new
stuff
and
some
of
the
old
stuff
as
we
go.
So
there
is
that
so
here's
to
cuddle
okay-
and
we
have
a
Kui,
simple
plug-in
inside
thing-
really
I'll
talk
to
you.
So
the
idea
is
that
I'm,
using
KU,
cuddle
or
cocoa
Tokui
and
ask
your
code
and
it
works
just
as
I
expected
I
can
use
that
an
adultery.
D
If
I
want
to
answer
the
question,
what
are
my
pugs,
but
the
graphical
mode,
maybe
is
that
I
can
just
append
a
sort
of
little
qualifier
to
the
community.
Instead
of
saying
it
and
ask
your
I
can
see,
and
this
window
pops
up,
I
can
I
can
resize
it
and
they
sort
of
crack
crafted
it
so
that
in
this
kind
of
pop-up
mode,
the
there's
no
little
command
line
there.
There's
no
interactivity
other
than
the
view.
D
D
D
D
You
never
quickly
answer
question
then
I
think
that's
one
thing
that
I
discovered
was
not
only
is
it
asynchronous
and
the
complex
interrelations,
but
even
if
you
want
to
stick
in
your
you're,
a
skier
terminal
which
I
want
to
do
as
well
as
anybody,
sometimes
you
ask
a
question
that
you
think
might
need
some
graphical
help
and
then,
while
you're
there,
you
can
sort
of
a
manned
and
explore
the
it
a
little
bit
within
that
local
confines
of
the
question
that
you're
asking.
What
is
the
status?
My
father?
D
Well,
a
natural
next
step
is
what
are
the
bogs
or
the
containers.
So
hopefully
we
can
allow
for
that
kind
of
quick,
but
quick
transition
is
even
within
public.
That's
the
first
time.
Second
style
is:
we
can
open
up
the
phone
on
the
full
terminal,
replacements
and
so
I
could
sink
the
same
same
basic
experience,
but
now
I
have
an
actual
command
line
system.
D
D
D
Next
step,
I'm
really
quickly
is
we
have
some
initial
work
with
integrating
with
this
do
and
Keala
it's
pretty
elementary,
but
so
on.
One
of
the
parts
of
kuya
that
you
could
be
pretty
pretty
flexibility
is
that
plugins
can
enrich
the
command
tree
in
the
same
way
that
you
would
sort
of
do
a
amount
of
UNIX
file
system.
You
can
sort
of
override
or
enrich
the
command
structure
of
the
an
existing
tree,
just
like,
but
plugging
in
new
commands.
So
in
this
case
get
access
may
not
be
an
existing
man.
D
This
is
really
just
for
demo
purposes,
but
I
can
do
that
now.
I
can
see
in
this
case
I'm
showing
pulling
out
the
data
from
Keala
directly.
This
is
actually
querying
the
ple
yaaaaaay
to
get
his
apt
list
model
and
then
each
of
the
cells
there
is
actually
we
have
elf
API,
but
because
we're
in
a
terminal,
as
opposed
to
a
really
monolithic
custom
design,
right
I
can
do
the
same
old
and
say
if
I
would
think
about
doing
have
to
change.
D
Can
do
that
just
by
querying
by
adding
it
is
a
query
plan
to
the
command
line,
as
you
can
see
in
this
case,
the
data
fills
in
and
I
have
two
different
tables,
mother
and
I'm,
getting
a
tabular
graphic
on
kind
of
you,
but
with
the
terminal
experience
where
I
connect
that
option
that
me,
but
it
flex
the
crowd.
What
I
want
to
see
in
sampling
the
filtering
and
I
see.
D
D
D
D
D
For
example,
I
know
that
each
cloud
provider
is
going
to
have
the
integration
story,
how
you
integrate
the
cloud
providers
notion
of
clusters
with
the
coop
config
notion
of
that
definition,
and
so
maybe
we
can
even
offer
on
a
per
provider
basis
the
ability
for
the
providers
to
ever
offer
when
I
took
context.
Maybe
I
don't
have.
A
D
D
F
A
D
We
yeah
so
I
think
so
it's
already
firstly,
and
we
switch
to
the
ER
get
up
repo,
so
we've
already
open
sourced
it
underneath
the
IBM
or
not
you
to
license,
and
this
I
think
I
think
we're
we.
We
are
under
no
illusions
that
being
underneath
the
IBM
org
is
not
the
right
place
to
be
I,
don't
think
it's
gonna
get
us
any
contributors,
and
so
I
think
honor
and
we're
happy
to
shift
this
to
another
word.
But
that's,
you
know
require
a
larger
discussions,
but
yeah.
F
Tools
and
in
different
awesome
projects
that
might
fall
outside
the
scope
of
the
project
based
on
kind
of
the
original
idea
of
the
architecture,
and
so
we
don't
want
maybe
say
release,
for
instance,
to
feel
like
that
these
ever
have
to
be
on
their
radar
or
like
say
p.m.
or
this
sort
of
thing,
but
at
the
same
time
like
it
gives
a
spot
for
us
members
of
the
community
and
and
everyone
else
to
collaborate
on
these
yeah
yeah.
We
need
to.
We
need
to
figure
that
out,
because
that's
come
up
actually
before
I.
F
F
Okay,
I
think
that's
like
kind
of
a
longer-term
thing
too.
Right
like
it
sounds
like
it
looks
like
you
guys,
are
making
great
project
great
progress
and
I
don't
want
it
I
think
trying
trying
to
switch
works
right
now.
It
probably
slow
you
guys
down,
but
knowing
that
that's
something
you're
open
to
is
really
helpful.
Thank
you.
Yeah.
G
Yeah,
we're
actually
hoping
that
if
we
did
switch,
orgs
I
would
actually
accelerate
things.
As
Nick
said
you
know,
one
of
our
goals
would
really
to
try
to
get
people
interested
in
this
and
get
outside
committers.
So
as
an
extent,
you
know
if
we
could
figure
out
the
right
place
for
this.
We
would
really
see
that
as
beneficial.
A
F
A
A
H
So
this
PR
is
a
change
in
kubernetes
website
brittle.
So
the
change
there
is
cognitive
1.14
release,
so
what
they
really
it
is
release.
The
change
will
be
shown
on
kaa
style.
As
for
the
website,
Docs,
and
the
main
purpose
of
my
PR
is
to
reflect
the
customization
customized
integration
in
Cube
control,
I
added
a
new
page
in
one
of
the
session
for
tip
control.
H
The
new
pager
added
is
to
how
to
manage
the
objects,
how
to
manage
the
resources
using
customized
in
cube
control,
and
there
I
listed
all
the
features
in
customize
and
give
main
description
like
how
you
want
to
use
this
field
also
for
each
of
the
field.
I
gave
a
simple
example:
besides,
the
new
page
added
I
also
did
some
other
changes
that
one
of
the
change
is
to
change.
H
A
B
F
F
F
There
is
some
stuff
in
here,
that's
new,
so
the
look
some
of
the
sections
like
printing
and
debugging,
or
mostly
copied
from
the
existing
Doc's
site
and
kind
of
reformatted
and
retraced,
but
the
philosophy
and
intention
is,
it
hasn't
been
altered.
Some
of
the
sections
are
basically
copied
from
the
customized
documentation
again
changed
the
wordings
changed,
but
the
philosophy
and
intention
is
not
altered.
A
couple
sections.
If
you
want
to
scroll
down
on
the
left-hand
nav
there
Sean,
specifically
the
app
cost
composition
in
deployment
selections
does
contain
stuff.
F
F
This
is
an
example
right,
and
so
this
is
using
customize
effectively
to
tell
users
how
to
create
basically
the
base
versions
of
their
applications
in
customized,
specific
flags
and
specific,
like
fields
such
as
the
resource
allocations
and
probably
count
in
the
sort
of
thing
for
specific
employment
targets
and
environments.
So
I'm
still
on
the
fence
about
whether
to
include
this
stuff
in
the
first
iteration
I.
F
On
the
other
hand,
unlike
most
of
the
other
stuff
here,
we
don't
have
a
lot
of
feedback
on
customers
using
this
stuff
in
production
for
directory
structure,
we
do
have
quite
a
bit
for
the
repo
repositories.
I
think
we
have
enough
understanding
of
that.
While
the
branch
is
specifically,
we
probably
have
less
I
think
the
concepts
are
probably
pretty.
F
There's
nothing
radical
in
here.
I
think
certain
decisions
could
be
made
differently,
but
this
isn't
like
completely
something
totally
new.
It's
get
branches
and
just
kind
of
different
ways
of
allowing
allowing
code
config
changes
to
be
committed
at
different
times
for
different
purposes
anyway.
So
that's
a
long-winded
way
of
saying,
if
you
think
of
yourself
as
an
expert
or
an
owner
responsible
for
this
area.
This
is
what
we're
gonna
be
telling
our
users
to
do.
You
probably
want
to
take
a
look
and
make
sure
that
your
opinions
are
being
represented
here.
F
And
again,
this
is
immediate
hood.
The
freeze
is
Monday
or
docks,
so
I
mean
this
actually
doesn't
we're
kind
of.
We
can
change
this
at
any
time
kind
of
because
we
were
publishing
it
ourselves
using
amplify,
but
but
the
release
is
coming
up
really
quick,
I
think
on
the
25th
so
and
I'd
like
to
have
it
all
settled
by
it.
They
do.
F
This
is
a
bad
idea
why
it
won't
work
and
say
here's
the
alternatives
that
I'd
rather
have
right,
because,
instead
of
just
asking
for
people
to
solve
problems,
I
find
that
soliciting
feedback
by
giving
your
own
ideas
is
is
pretty
effective.
So
that's
the
context
of
why
see
me
maybe
open
five
or
six
caps
in
the
last
week
is
to
kind
of
facilitate
that
workflow.
F
This
cap
with
the
headers,
is
actually
what
I
would
like
to
see
get
merged
because
I
think
this,
this
one's
important
for
us
to
have
more
observability,
there's
a
couple
things
I
think
that
are
going
to
be
possibly
quite
valuable.
Here.
One
is
adding
a
header
for
deprecation
on
coop
control
commands
when
we
send
when
the
control
sends
a
request
from
a
command.
That's
deprecated,
adding
a
header
for
that.
If
we
can
get
API
the
API
server
to
a
lot
enable
logging
that
in
place,
so
then
cluster
admins
can
you
can
think
of
an
organization?
F
F
B
F
Have
that
tool,
there's
other
stuffin,
no
I
think
would
be
useful
or
for
everyone.
Ideally
folks
could
see
how
users
are
interacting
with
their
clusters.
That
means
maybe
they
can
bring
that
information
back
to
us
on,
say
here's
what
people
using
could
control
here's
roughly
how
users
are
interacting
with
our
systems.
Now
you
know
where
to
focus
your
energy
to
help
us
the
other
pieces.
It
helps
people
that
maybe
run
their
own
clusters
understand
how
users
interact
with
the
systems.
They
know
what
tools
they
need
to
build
themselves.
F
Number
of
other
companies
will
talk
to
at
least
three
or
four
I'll
end
up
wrapping
to
controlability
their
own
tools
and
forking
it
and
taking
the
libraries
books
are
really
just
building
their
own
stuff.
It
seems
like
because
they
really-
or
maybe
your
companies
are
building
their
own
stuff.
That's
really
constantly
what
their
needs
are
using
coop
control
as
a
foundation
for
that
and
so
giving
them.
F
The
ability
to
see
like
what
people
are
doing
maybe
allows
them
to
better
invest
in
their
own
tools,
so
we'll
have
to
work
with
API
machinery
actually
to
make
sure
this.
Just
it's
logged
in
a
same
fashion
that
is
discoverable
and
can
be
pulled
into
analytic
systems.
Thinking
users
can
decide.
Cluster
administrators
could
decide
to
then
then
take
the
data
they
own
and
input
in
systems
that
allows
them
to
view
it.
F
A
B
A
E
Guess
feedbacks
appreciate
it
on
that.
Definitely
also,
if
you
take
a
look
at
that
PR
right
now,
we
we
mainly
just
duplicate
everything,
including
generated
code,
which
I
think
we
could
do
without
especially
if
we,
you
know
for
pretty
adamant
on
seeing
this
sort
of
code
duplication
as
a
as
a
band-aid.
Until
we're
able
to
you
know
actually
split
that
keeps
keeping
full
Reaper
out.
F
E
B
B
E
Also
on
that
note
not
saying
you
know,
this
could
be
a
particularly
better
way,
but
another
way
we
sort
of
considered
doing
this
in
the
past
was
through
the
use
of
plugins.
So
maybe
we
could
you
like.
We
could
probably
bring
the
discussion
up
again
of
making
reconcile,
or
even
just
the
auth
subtree
Napoleon,
the.
B
But
the
problem
is
that
we
have
to
command.
We
haven't
duplicated
it,
maybe
deprecating
it
will
be
a
solution
towards
you
know,
externalizing
it
and
making
it
actually.
A
plug-in
will
have
to
do
some
more
saying
for
the
qcp
or
convert
at
some
point
in
time,
because
that
is
one
of
the
commands
that
will
have
to
stay
in
the
main
granny's
repo
and
the
reason
for
that.
It
is
relying
on
the
internals
for
the
conversions
and
we
cannot-
or
rather
we
don't
want
to
have
the
internals
inside
of
the
keeps
we
both
because
internalist
exists.
A
A
F
Sorry,
what
was
that
I?
Just
one
last
thing
is
I
just
want
to
make
sure
that
everyone
is.
We
didn't
drop
the
ball
on
figuring
out,
updating
the
owners
files,
it's
just
taking
the
backseat
to
the
docks
and
a
couple
other
things
that
are
have
deadlines
that
are
coming
up
in
shortly.
But
we
didn't
forget
about
that
thing
and
we're
gonna
continue.
Make
sure
that.
C
Okay,
also
on
one
last
thing:
I
guess
I:
this
is
Ahmed.
Do
we
know
who's
the
admin
for
today,
six
or
so
we
can
do
it.
Transfer
I
think,
there's
like
there
needs
to
be
handoffs
on
both
sides
over
like
some
email
that
comes
from
github
right,
yeah,
I,
think.