►
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
Foreign
today
is
Wednesday
July
19th,
and
this
is
the
cluster
API
office
hours.
If
you
are
joining
us
for
the
first
time
or
need
a
reminder,
you
need
to
join
those
sick
cluster
lifecycle,
mailing
list
in
order
to
get
access
to
this
agenda
document
and
I
also
just
want
to
remind
everyone
that
we
are
inviting
by
the
cncf
code
of
conduct.
If
you'd
like
to
speak
up,
please
raise
your
hand
and
I'll
make
sure
you
get
a
chance
to
speak
all
right.
A
So
if
you
are
able
to,
please
add
your
name
to
the
attend,
a
list
that
helps
us
an
idea
of
who's
joining
these
meetings
and
if
you
have
any
agenda
items
or
any
topics
you
want
to
bring
up
any
questions
feel
free
to
add
them
under
discussion
topics.
A
So,
first
off
we
usually
like
to
start
by
giving
a
chance
to
giving
a
chance
to
anyone
who's
new
to
the
meeting
to
say
hello
and
introduce
themselves.
So
if
that's
you,
if
you
want
to
say
hi
I,
will
go
ahead
and
mute
and
feel
free
to
speak
up
and
say
hello.
B
Hi
I'm
Nolan
I've,
been
on
community
calls
a
few
times.
I
know
some
of
you
here,
but
I'm
at
red
hat
and
looking
to
get
more
involved
with
Cappy,
so
I
think
you'll
be
seeing
me
around
some
more.
C
A
Okay,
if
not,
let's
move
on
welcome
new
folks,
let's
see
open
proposals,
I
don't
know
if
there
is
anything
right
now
that
is
active.
A
Does
anyone
have
anything
to
say
about
a
proposal?
That's
either
here
or
missing,
that
we
should
talk
about.
A
All
right
we're
also
at
the
very
end
of
the
really
cycle,
so
I
would
expect
most
new
proposals
to
start
popping
up
in
the
new
cycle
in
after
the
release.
Speaking
of
release
come
see
me,
you
have
the
first
item
about
the
1.5
release
who's.
Thinking
of
that
one.
Let's.
E
Go
ahead,
I
can
take
it
so
yeah
thanks,
Cecil,
hey
everyone.
We
released
cappy1.5.0
release
candidate
one
yesterday,
it's
a
release
candidate,
so
that
means
it's
up
for
testing
should
only
be
used
for
testing.
So,
if
you
file
find
any
issues,
please
file
a
bug
and
we'll
be
releasing
1.5.0
on
July
25th.
Once
again.
Thank
you.
All
contributors.
A
A
F
Flags
has
been
exemplary,
so
thank
you.
Thank
you.
Thank
you.
Okay!
Getting
back
into
getting
back
to
tanks!
Some
one
pointed
me
to
this
cncf
case
study
from
Mercedes-Benz.
The
document
is
worth
to
read
for
everyone
working
in
cluster
API,
so
I
occurred
here,
but
there
is
a
statement
that
that
really
make
me
proud
and
happy,
and
it
is
a
work.
F
Mercedes-Benz
Forks
are
basically
saying
that
working
with
this
sig
has
been
a
pleasure
and
that
it
is
likewise
for
us
working
in
Merchants
Bank
and
that
we
that
it
was
also
opportunity
for
them
to
to
shape
our
internal
process
of
on
top
of
community
process.
So
I
think
this
is
really
inspiring
for
everyone
in
this
meeting
so
spread
the
words.
This
good
publicity
for
everyone
working
up,
Upstream.
A
Thanks
for
sharing
fabrizo
and
thanks
Mercedes-Benz
for
doing
this
all
right
unless
there
are
any
questions
or
comments,
let's
move
on
to
the
next
one
Richard.
D
Yeah
sorry
represented
Kathy
last
night
on
the
Choose
Your
Own
Adventure
Show
I
gave
a
five
minute
pitch
for
Cappy,
so
voting
is
open
on
the
I
guess
this
stage
of
the
Party
Production
so
cross,
plane
versus
Cappy
for
cluster
provisioning
so
feel
free
to
vote.
I
guess
the
second
part
to
that
is
all
of
the
materials,
so
the
slides
and
the
demo
or
in
that
second
link
in
the
repos.
So
if
anyone
that
ever
wants
to
reuse
those
feel
free
to
use
them,
that's
it
really.
Thank.
A
You
that's
really
cool
thanks,
Richard
thanks
for
doing
this,
so
what
happens
with
the
winner?
What
do
you
get
if
you
win.
D
That's
like
really
I
I,
guess
they
they
take
the
The,
Chosen
cncf
product
or
sorry
projects
for
for
that
part
of
the
path
to
Productions,
and
so
they
will
use
it
to
to
implement
the
the
cluster
creation
and
cluster
life
cycle
management.
For
for
that
story,
so
there
will
be
material
that
comes
out
the
back
of
this
as
well.
B
A
All
right:
well,
everyone
check
it
out
if
you're
interested
awesome.
So
this
brings
us
to
the
end
of
our
very
short
discussion
topic
section
today.
F
Quick
call
again
for
providers
test
rc1,
send
feedback.
We
still
have
some
time
to
to
get
bug
if
we
catch
them
early.
A
Absolutely
and
then
yeah
I
guess
this
is
also
provider
update
session,
so
does
do
any
of
the
providers
have
any
updates
on
their
adoption
of
one
five
or
any
release
call-outs
or
anything.
A
G
Sure
I
I
don't
know
if
our
experience
is
representative
but
and
I
think
maybe
I
said
this
last
week,
but
we've
been
trying
to
integrate
RC
0
and
we'll
update
rc1.
Today
everything
looks
fairly
straightforward,
although
there's
a
fair
amount
of
code
change
due
to
control
runtime
being
updated,
but
in
our
case
we're
kind
of
stuck
because
we
depend
on
this
other
library
that
is
not
yet
updated
controller
runtime.
G
So
we're
not
able
to
run
all
our
tests
quite
yet
so
yeah
I'm
thinking
about
some
way
to
work
around
that,
even
if
it's
temporary
just
so,
we
can
actually
get
tests
to
run.
But
anyway,
that's
as
far
as
we've
gotten
the
one
other
thing.
Maybe
this
crowd
would
be
interested
in
is
we're
promoting
a
couple
people
to
maintainer,
John,
Hume
and
ashutosh
Kumar,
and
then
David
Justice,
who,
you
probably
all
know,
is
moving
to
Emeritus
maintainer
because
he's
just
too
busy
to
take
on
PRS.
A
No
thank
you
Matt.
Those
are
good
updates
and
congrats
to
Ashley,
Tasha
and
John,
and
thank
you
to
David
for
all
his
contributions.
H
I
don't
see
any
mention
about
cluster
API
provided
gcp,
but
even
though
I
haven't
taken
part
on
the
release,
I
would
like
to
point
out
that
it's
been
released,
I
think
on
Friday,
so
yeah
it's
available
one
four
zero,
so
I
will
add
it
to
the
notes
later
and
if
you
want
to
take
a
look
but
yeah
kudos
to
Richard
and
Carlos
who
worked
on
it.