►
From YouTube: 2019-04-17 - Cluster API Office Hours
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
Are
you
talking
to
us
cuz
your
meet
it?
Oh,
that's,
wonderful,
okay,
so
hello
and
welcome
to
the
Wednesday
April
17th
edition
of
the
cluster
API
office
hours.
We
have
relatively
late
agenda
today.
So
if
you
have
any
topics
that
you
want
to
bring
up,
please
go
ahead
and
add
them
to
the
agenda.
Now
I
went
ahead
and
link
that
in
the
zoom
chat
for
folks
who
are
attending
live
and
also,
please
make
sure
to
add
yourself
to
the
attending
list
as
well
starting
off.
B
C
C
B
B
D
Thing
we
did
the
kickoff
meeting
yesterday,
I
link
to
the
notes
in
the
recording
actually
think
that's
a
link
to
the
discuss,
but
you
can
find
the
notes
in
the
recording.
In
there
we
came
up
with
a
document
that
is
going
to
be
a
place
to
put
our
various
proposals
for
the
extension
mechanism,
as
well
as
pros
and
cons
and
a
place
to
discuss
those
things
and
also
I'm.
D
C
C
One
important
thing
that
I
did
today
was
to
add
emoji
to
every
types
so
that
we
can
quickly
index
on
those,
but
other
than
that.
The
goal
is
to
have
like
in
the
in
the
next
two
weeks,
kind
of
like
a
proposal
built
up
and
with
clear
goals
for
each
type
and
boundaries,
and
one
thing
that
I
also
wanted
to
mention
is
folks
before
collaborating
on
that
minute.
F
Question
if
I
may,
a
very
quick
is
there
any
place
in
such
documents,
because
I
believe
I
might
be
adding
something
that
not
would
be
agreeable
to
everybody
in
yet
it
seems
mighty
useful
in
the
future.
I
have
a
maybe
section
in
the
document
say:
okay,
that's
out
of
focus
now,
but
let's
just
put
it
in
so
that
we
kind
of
don't
forget
it
going
forward.
But
do
you
believe
that
that
might
be
a
good
idea?
Bad
idea
agreeable
a
completely
wrong
place
on
location
to
do
it
in
or
just
something?
F
I,
the
networking,
storage
and
zones
force,
for
example,
as
being
examples,
and
those
are
a
little
so
in
case,
though
they're
not
being
considered
to
be
part
of
the
coop
proposal,
which
is
fair
enough.
I
just
don't
want
the
concert,
concepts
to
be
an
easter
or
or
forgotten,
and
maybe
have
additional
place
or
someplace
to
to
lease
them
so
that
we
don't
lose
track
of
them
in
case,
for
example,
for
storage.
C
Yes,
I
was
saying
there
or,
if
it's
like,
related
to
the
types
that
we
already
have
down
at
the
bottom.
There's
an
alternative,
this
section
that
we
can
outline
a
possible
term
that
we
have
considered,
but
so
far
the
movie.
What
we
have
right
now
for
the
types
is
should
be
like
kind
of
a
high
level
going
into
like
a
little
bit
more
details
than
like
the
high
level
requirements
document
that
we
are
putting
into
the
the
repo
story
probably
this
week.
C
But
if
we're
going
too
much
into
implementation,
detail
that
I
could
possibly
like
touch
other
work
streams
that
are
just
starting.
So
we
don't
want
to
go
in
too
many
details
and
for
yet
for
alternatives,
ideas
either
an
issue
if
it's
something
that
we
want
to
discuss
or
document
or
in
the
open
intersection.
If
it's
related
to
the
work
stream,
kappa.
F
F
F
B
You
thank
you
Michael
and
also
keep
in
mind
that
this
is
a
process
that
we're
building
up
as
we
go
to
so
there
really
isn't
any
specific
right
or
wrong
way
here,
yet
we're
still
trying
to
define
the
path
in
general
as
a
community.
So
all
right,
the
other
two
I'm
sorry
appreciate
it.
Thank
you,
yeah
all
right,
the
other
two
workstreams,
the
control
plane,
lifecycle
management
and
the
new
life
cycle
management
haven't
met
yet
the
kickoff
meeting
for
the
control
plane.
Lifecycle
management
is
Thursday
at
10
a.m.
H
I
We
can
we
keep
discussed
and
always
just
you
know,
hold
any
decision-making
till
we
get
back.
Most
of
the
original
conversation
it
was
just
was
gonna,
be
about
framing
what
we
want
to
accomplish
and
scope
boundaries.
So
you
know
I
think
if
we
hold
any
major
discussion
until
we
until
the
following
week,
it
seems
like
just
fixing
the
administrivia
first
of
what
what's
one
of
the
boundary
lines
that
we're
not
going
to
cross
or
whatever
once
we
are
going
to,
you
seems
like
a
fair
game.
I
B
C
I
B
C
And
there
is
also
the
PR
for
use
cases
which
I
opened
I
think
yesterday.
So
please
also
look
at
look
at
that
one.
It's
meant
to
be
as
a
staging
place
for
the
use
cases
and
a
reference
for
what
we
discuss
and
we
have
in
in
the
document
so
also
feel
free
to
PR
against
the
requirements
and
use
cases
after
they
get
merged
to
either
Iran.
E
Just
a
small
technical
question
about
disgust:
can
you
discuss
them
like
general,
how
we're
gonna
use
disgust,
because
that
seems
to
concern
all
work
streams
I
just
I
mean
it
took
me
a
little
while
now
to
figure
out
where
to
go.
I
did
find
cluster
API,
eventually
from
the
disgust
front
page,
but
once
I'm
there
I'm
kind
of
wondering.
Can
I
subscribe
to
things,
for
example,
because
we
switching
away
from
the
mailing
list
and
the
mailing
list?
E
A
For
example,
so
yeah
I
posted
something
in
the
slack
channel.
I
found
it
in
disgust
that
explains
how
to
figure
in
all
settings
for
disgust.
I,
don't
know
enough
about
it,
but
what
I
did
is
I
set
up
filters,
so
this
is
something
I
think
we
should
document
this,
because
people
are
going
to
have
this
problem
in
general.
B
Well
I
know
think
I
will
say
is
that
I
tried
mailing
list
mode
on
on
disgust
and
it
basically
turned
on
notifications
for
everything
regardless
of
topic.
So
you
probably
don't
want
to
use
that
what
I
did
do
was
I
enabled
the
check
box
to
send
email,
even
if
you
are
active
on
the
site
and
that
way,
when
you
sit
there
and
subscribe
to
a
particular
topic,
you
will
still
get
the
email
as
if
it
was
an
email
list.
Just
for
that
topic.
C
And
the
last
thing
I
want
to
note
about
discuss
is
that
it's
it's
not
necessarily
like
we're,
not
necessarily
moving
away
from
from
the
mailing
list.
Google
Groups.
This
is
to
have
an
additional
method
for
also
for,
for
example,
users
in
China
that
don't
have
access
to
Google
Groups,
so
we're
trying
to
replicate
the
communication
in
both
places
instead
of
settings
for
one,
because
people
are
used
to
do
group
so
longer
term,
we
will
be
able
to.
E
C
One
example
is
the
meeting
notes
that
we
have
in
Google
Docs
those
are
not
accessible
in
China.
So
after
each
meeting
in
through
hearings,
posted
I'm
also
posting
the
notes
and
recording
on
and
discuss.
Also
any
communication
there.
For
example,
the
data
model
work
stream
sent
I
personally
sent
to
the
mailing
list.
I
also
duplicated
the
same
communication
in
discuss
so
to
keep
both
which
is
updated.
At
the
same
time,
it's
not
ideal,
but
it's
just
community
effort.
It.
E
H
Based
on
the
common,
the
previous
comment
regarding
some
topic,
like
this
duration
stuff
in
the
requirement
there
has
been
also
some
contentious
topics.
The
people
will
probably
don't
have
a
agreement.
I
feel
that
probably
instead
like
because
he
I
think
it's
important
to
vote
for
one
we
own,
that's
why
we
should
merge
these
requirements
and
the
use
cases,
but
they
both
are
so
topic.
Could
probably
these
topics
make
like
an
issue
and
make
a
second
round
of
discussion
instead
of
blocking
the
whole
document?
H
Probably
so,
because
our
insurance
specific
topics
I
mean
it's
like
it's
not
something
to
prevent
us
to
move
forward
as
a
whole,
but
probably
some
people
don't
feel
comfortable
because
and
I
still
like
trying
to
discuss,
we
say
okay,
but
we
need
to
move
forward.
Probably
we
don't
need
to
to
do
either
way.
We
can
say
this
one
out
there
you
can
know
a
ride
to
a
conclusion.
You
know
short
term.
H
We
can
just
say:
okay,
let's
park,
this
is
a
successful
discussion,
so
we
can
move
forward
and
still
have
the
chance
to
to
keep
up
discussed
because
otherwise
it's
like
we
already
discussed
that.
Well,
yeah,
we
discussed
work
with.
You
know,
right
to
a
conclusion
so
easily
I
expect
that
to
happen
a
lot
with
the
data
model
that
Impala
is
going
to
be
stably
contentious
because
you
know
the
first
meeting
was
obvious:
how
many
ideas
on
the
table,
and
probably
we
need
to
start
moving
forward.
H
I
Know
it's
not
like.
Could
these
doesn't
have
this
problem
KK
itself?
The
the
answer
is
we
just
leave
in
set
lifecycle
to
frozen
as
issues
and
topics,
and
we
revisit
them
continually.
So
it's
totally
legitimate
to
have
an
idea,
but
maybe
it's
time
is
not
right
and
we
just
want
to
keep
it
open,
so
the
lifecycle
frozen
gives
it
so
that
the
bots
don't
automatically
close
those
issues,
and
you
know
there
there's.
There
still
were
after
four
years
like
issues
in
the
communities
days
from
the
original
100
to
the
tens
series
still
open.
I
So
you
know
it's
common
for
us
to
have
ideas,
but
maybe
the
timing
isn't
right
or
maybe
the
model
isn't
as
mature
as
we
would
like
it
to
be
for
us
to
make
certain
changes
or
maybe
there's
just
you
know,
not
consensus
on
where
you
want
to
go
so
I.
Think
opening
the
issue
to
have
the
discussion
or
using
an
issue
as
a
way
to
frame
the
conversation
and
then
bring
that
to
the
meetings
right,
I.
H
Believe
the
point
here
is
that
I'm,
sorry
so
Michael
just
to
be
free,
said
and
instead
Kate
is
important.
That
probably
something
this
is
not
introducing.
For
instance
by
me,
I
mean
it's
easier
for
me,
so
Michael
has
mentioned
before
something
he's
particularly
interest.
He
can
make
the
issue,
but
there
are
some
stuff
to
talk
some
vitamin
D
in
the
discussion.
The
problem
were
introducing
by
another
person
and
who
I
mean
I,
know
who
didn't
write
to
have
to
a
procedure
to
do
that.
But
it's
like
a
some
point
which
should
like
discuss.
H
This
topic
has
been
discussed
for
some
time,
probably
move
out
without
being
the
person
that
introduced.
It
is
like
a
decision
of
the
group
I
think
that's
a
slightly
different
that
when
someone
is
to
use
a
new
issue
for
what
these
already
been
agree
of,
but
they
agree
that
the
supposes
happens
all
around.
B
The
other
thing,
too
is
this
is
one
of
the
reasons
why
we
had
discussed
forum
set
up
so
that
we
can
take
some
of
these
topics
and
dive
into
more
detail
on
them
and
and
have
some
conversation
back
and
forth
on
them,
without
without
them
kind
of
eating
up
the
meeting
time
requiring
everybody
to
show
up
the
same
time
for
a
meeting
or
we're
trying
to
handle
it
through
comments
and
the
docks
or
things
like
that.
So
we
should
definitely
bring
some
of
those
topics
out,
have
some
discussion
around
them
so.
F
B
You
so
much
yeah
and
a
big
reason
why
we
don't
want
to
have
those
conversations
in
slack.
Is
we
don't
want
decisions
necessarily
being
made
based
on
who's
available
at
the
time
we
want
to
be
able
to
involve
the
entire
community
with
making
decisions?
So
you
know
the
mailing
list
discussed.
Those
types
of
things
provide
better
asynchronous
communication
to
have
those
discussions
and
being
inclusive
versus
just
a
small
group
of
people
that
happen
to
be
there
at
the
time
making
decisions
around
those
things
perfect.
B
B
We
do
have
a
PR
out
there
to
remove
some
of
the
the
old
participants
that
are
no
longer
around
to
add
myself
to
the
cluster
API
maintainer
x'
and
admins
also
update
the
security
contacts,
and
we
also
have
a
second
PR
out
there.
If
somebody
can
dig
it
up
to
add
david
to
the
owners
to
be
able
to
manage
the
documentation
as
well.