►
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
Okay,
I,
don't
know
everyone.
This
chemistics.
A
Of
conduct
which
comes
down
to
please
be
nice
to
each
other.
Please
use
array
sense
feature
when
you
want
to
say
something.
If
you
have
anything
you
want
to
talk
about,
you
probably
should
make
this
a
little
bit
bigger,
feel
free
to
add
it
to
the
agenda.
We
have
very
latest
Channel
today,
so
yeah.
It's
a
lot
of
space.
A
Yeah
and
if
you
don't
have
access
to
the
document,
you
can
join
the
sector,
life
cycle
made,
invest
and
you
should
find
it
via
Google.
A
It
should
be
it
so
open
proposals,
pre-personalizing
book.
Does
anyone
want
to
talk
about
it.
B
C
B
All
hear
me:
okay
yeah,
so
the
reason
why
we
did
this
proposal
was
originally
opened
was
because
we
wanted
to
be
able
to
mutate
the
machine
spec
to
provide
a
static
IP
address
when
we
started
this
effort
back
in
October,
it
appeared
that
that
ipam
was
not
as
far
along
as
it
is
now
within
Cappy
and
Cap
B.
B
A
Yeah
that
sounds
fair.
To
be
honest,
I'm
already
forgot
this
oh
I
missed
it.
I,
don't
know
I,
don't
remember.
A
Basically,
I
was
I
would
say,
maybe
I
mean
if,
if
from
your
side,
you
don't
need
anymore,
maybe
maybe
just
post
like
a
warning
here
like
hey,
we
will
play
busy,
stop
this
effort
and
just
see
if
someone
else
wants
to
pick
it
up
for
I,
guess:
I,
guess
their
own
use
case
or
their
own
reasons
and
I
think
if
maybe
give
them
like
two
or
three
weeks
or
something
that
we
can
close
it
I
mean
they
can
still
reopen
it
if
they
see
it
in
a
month
or
two.
B
Okay,
for
sure
I
can
do
that
yeah.
This
is
my
first
enhancement
in
in
Cappy.
So
certainly,
if
there's
anything
precedent
for
how
these
things
are,
we're
done
I'm
pretty
open
to
hear
it.
So
thank
you.
A
Yep
I
think
that
that's
fine,
okay
proposals
does
anyone
talk
about
them,
I'm
interested
since
forever,
so
probably
not
same
here.
Group
I
think
they
have
a
point
down
there
and
obviously
okay
good.
So
basically
we
have
two
points
as
of
now
at
least
so.
First
one
is
just
mine,
so
we
had
a
following
PR.
So,
okay,
maybe
some
context
so
I
think
a
lot
of
provide
associated
in
kubernator.
Six.
It's
using
are
using
the
the
Upstream
image
promotion
for
release
images.
A
So
basically
it
works
like
this.
Whenever,
whenever
pull
request
is
merged,
we
push,
we
push
an
image
to
a
staging
repository
and
later
on,
it's
promoted
all
of
the
providers
using
that
mechanism
are
probably
using
Google
Cloud
build
because
I
think
that's
the
only
way
that
it
works.
A
So
what
we
had
here
was
basically
the
pr
a
change
in
the
machine
type
that
we
use
in
Google,
Cloud,
build
I.
Think
the
reason
was
basically
that
the
old
one
is
going
away,
I'm,
not
sure
if
it's
an
applicator
or
just
old,
but
that's
the
reason
was
like
the
other.
One
is
cheaper
and
it's
just
more
future
proof.
So
basically,
just
the
PSA
here,
if
any
other
providers
are
using
Cloud,
build
as
well
probably
makes
sense
to
think
about
also
changing
the
machine
type
for
the
cloudboard.
D
One
yeah
sorry
I
I,
because
I
just
added
my
topic
yeah,
but
go
on
your
topic.
First,
okay,.
A
Okay,
any
any
questions
about
that
by
CCC
or
the
organization.
That's
great
I
don't
have
much
more
context.
I
was
just
seeing
that
PR
when
I
got
back
and
I
was
wondering
if
he
told
any
okay
I
think
we
can
go
to
the
next
one
or
you
can
add
all
your
links
and
then
start
that's
right.
No
rush.
D
Okay,
may
I
yeah,
absolutely
I
I,
just
to
remind
the
yeah
yeah.
The
PRS
I
introduced
this
proposal
a
few
months
ago,
but
there
may
the
peer
our
peers.
You
know
that
doesn't
progress
currently
so
I'd
like
to
request
for
the
review
to
maintainers.
D
We
just
add
that
locked,
missed
comments
for
cluster
CTL,
all
about
status
and
history,
and
we
submitted
history
appears
a
few
months
ago
and
I
already
applied
all
the
comments,
the
previous
all
the
viewers
given
so
give
us
so
yeah.
If
there's
no
problem,
I'd
like
to
request
her
already
again.
A
Can
you
please
just
post
another
comment
on
each
of
those
just
with
CeCe
the
folks
who
have
it
before
and
and
just
ask
them
for
another
round
of
ready.
I
mean
I,
I
added
it
here,
but
I'm
not
sure
how
many.
D
A
Are
in
a
meeting
right
now,
so
just
that
there
was
a
seat
async
and
what
I
can
tell
you
is
that
the
last
few
weeks,
a
lot
of
books
were
a
lot
were
really
busy
with
kubecon
and
other
stuff
and
in
finishing
the
104.
This
is
that's.
Probably
that's.
Probably
one
reason
why
why
they
had
a
lot
of
time
to
review,
but
it's
it's
a
fair
ask.
Just
do
it
as
well
as
soon
just
okay.
C
A
A
C
Hey
yeah,
I
guess
random
last
minute
topic
was
anyone
who
was
at
kubecon
want
to
talk
about
the
Cappy
related
sessions
and
discussions
that
happened.
So
those
of
us
who
weren't
there.
A
I
think
we
can
do
that
this
red
shot
here
as
well.
No,
okay,
okay,
just
give
me
a
second
I.
Just
look
for
the
foreign.
A
A
A
very
very
short
glance
at
the
slides
and
people
can
look
at
places,
but
basically
hobby
suited
some
sort
of
introduction,
like
the
last
one
or
two
contributor
Summits
for
folks
who
are
there.
Basically
just
I
really
keep
it
short
here,
just
a
bit
about
stats
and
contributions
and
and
stuff
that
we
did
in
the
past.
A
And
then
we
had
a
bunch
of
topics
to
talk
about,
and
then
we
voted
for
two
of
them.
So
basically
that's
a
list
of
topics
but
I
go
to
the
notes
to
the
tool
that
we
actually
talked
about.
A
Provider
clusters
and
manage
kubernetes,
basically
20
minutes
for
each
of
them
mixed
Wireless
clusters,
we're
looking
at
use
cases
and
just
asking
around
essentially
who
needs
it,
for
which
reason
yeah
I,
don't
know,
should
I
go
to
the
points
or
should
we
just
give
people
time
to
look
at
the
async
and
discuss
teachers
next
week,
I,
don't
know
I
mean
I
can
read
over
them,
I'm,
not
sure
how
much
benefit
it
is,
but
I
think
it
was
nice.
A
We
had
like
20
30
40
people
there
and
we
did
like
the
last
few
times.
Basically
just
talking
a
bit
about
I've
got
some
topics,
but
as
always,
no
decisions
made
or
anything
just
brainstorming
and
that's
I
read
over
today
and
thanks
to
Richard
for
writing
this
up
by
the
way
I
think
it
captures
most
of
what
we
talked
about.
A
It
or
maybe
one
thing
yeah,
so
we
talked
a
bit
of
what
mixed
providers,
but
we
also
talk
about
manage
kubernetes
and
we
had
some
sort
of
hey.
Let's
try
to
make
this
happen
a
moment,
but
and
basically
what
we
were
saying
like
that,
we
we
tried
I
mean
SEO
as
usual
folks
have
to
volunteer,
but
what
we're
trying
to
push
forward
is
basically
the
machine
pool
machine,
essentially
that
PR
I,
unfortunately
didn't
have
time
to
review
it.
A
Yet,
but
I'll
try
to
do
the
system
next
week,
then
Richard
is
working
on
the
machine
pool
supporting
cluster
class,
so
he
was
saying
that
he
is
getting
back
to
it
soon
and
then
we
basically
have
I
think
it's
a
web
PR
at
that
point
from
check
the
topic
around.
How
can
we,
let's
say
deal
with
different
manuscripts
implementations
in
a
sense
of
the
control
plane?
A
Endpoint
doesn't
always
come
from
an
infrastructure
cluster,
so
basically
those
three
topics
and
then
our
impression
was
like
okay,
that
should
I
mean
that
should
push
machine
pools,
step
forward.
That
should
let
us
converge
basically
in
a
sense
that,
yes,
you
can
also
use
cluster
class
in
combination
with
managed
kubernetes
and
machine
pools,
and
it's
not
like
50
of
people
use
classic
class
and
50
US
manage
kubernetes
or
some
other
percentages,
but
it
feels
like
we
have
some
sort
of
split
right
now
that
you
have
to
choose.
A
A
Okay,
any
other
last
topics.
A
Otherwise,
three
two
one
have
a
nice
week
and
see
you
next
week.
Bye.