►
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
Hello,
everyone-
this
is
the
C
cluster
life
cycle
office
hour
meeting
today,
is
Wednesday
5th
of
July.
B
A
We
have
a
meeting
document,
I've
added
the
link
to
the
minute
to
the
admitted
document
to
the
chat.
If
you
don't
get
access
to
them
to
the
document.
Please
join
the
C
cluster
life
cycle
mailing
list.
The
address
of
the
main
list
is
in
the
chat
as
well
before,
starting
last
reminder
that
this
meeting
abide
to
the
cncf
cotton
control,
so
please
be
kind
with
each
other
and
if
you
need
to
speak,
use
the
rise
and
feature
in
the
in.
A
The
zoom
it
is,
it
is
a
reward
there.
B
A
Starting,
please
add
your
name
to
attend
the
attendee
list.
Thank
you
to
everyone
is
already
in
doing
this
and
you
have
a
topic
in
agenda
feel
free
to
add
to
them.
So
let's
get
started
as
usual.
At
the
beginning
of
the
meeting,
we
give
a
room
to
new
attendee
to
introduce
themselves
and
say
hi
to
everyone,
so
I
I
give
Roma,
feel
free
to
raise
the
Orient
and
introduce
yourself.
A
Okay,
it
seems
that
today
we
don't
have
a
new
what
the
so
we
can
move
to
open
proposal.
We
have
only
one
proposal,
which
is
the
change
of
super
to
support
and
manager.
Kubernetes
Jack
is
in
is
a
is
not
present
today
as
far
as
I
know,
so,
I
don't
think
that
there
are
updates.
A
I
don't
see
and
raise
it.
So,
let's
keep
going
discussion
topic.
I
have
the
first
one,
which
is
a
PSA
for
everyone.
Please
be
aware
that
code
3
is
for
the
1.5
release,
is
next
Tuesday
Tuesdays
11
of
July.
A
We
are
still
in
track
for
having
the
1.5
release
GA
the
25th
of
July,
starting
from
after
the
code
freeze.
So
that
means
starting
from
next
Tuesday
early
Cherry
Peaks
for
documentation,
bug
fixes,
test
fixing
and
in
test
Edition
are
allowed.
Otherwise,
no
changes
are
accepted
on
the
release
branch.
D
B
E
I
think
if
noaz
is
not
on
here,
oh
he's
I'll,
let
noisa
answer
that
he
just
cut
the
issues
for
most
of
the
providers.
Yesterday,
I
think.
C
Oh
sorry,
I
was
trying
to
get
context
on
the
next
question.
Can
you
please
repeat.
B
My
question
I
was
just
asking
if
some,
if,
if
we
have
some
providers
here,
who
already
started
picking
up
the
beta
and
have
feedback.
C
I
I
need
to
check
on
Azure
site.
If
you
have
started
testing
it
just
got
back
from
holiday.
E
You
you
have
a
list
of
all
those
tickets,
though,
that
you
created
right.
I
was
looking
for
those
in
slack.
E
If
you
want
to
make
a
quick
thread
in
the
cluster
API
channel
with
all
the
issues,
then
we
can.
We
could
trace
that
over
the
next
week
or
so.
A
So,
thank
you.
These
are.
These
are
good
call
out
so
custom
Pi
by
itself
does
not
mean
much.
Cluster
Pi
with
provider
means
a
lot,
so
we
we
really
need
providers
to
start
picking
up
the
new
release
this
year.
The
the
release,
theme
and
communication
team
did
a
great
job
in
opening
a
niche
issue
for
all
the
non-major
providers.
A
So
we
we
basically
engage
them
directly,
asking
to
start
adopting
the
new
ladies
provide
feedback.
I
saw
a
PR
in
Kappa
V
and
thank
you
Christian
Slaughter
for
starting
this
work,
I'm,
not
aware
of
other
providing
starting
this
work,
but
there
was
a
an
holiday
in
the
US.
So
maybe
something
with
will
get
moving
this
week.
A
And
just
passed
the
comment
in
in
the
chat
that
probably
wrap.
Oh
already
started
working
the
beta
so
looking
forward
for
feedback.
They
are
really
important
for
the
for.
C
Can
speak
about
this
Fabrizio,
so
we
have
a
proposal
in
here
which
talks
about
blocking
a
PR
if
an
area
label
is
not
added
to
the
peer
itself,
we
just
wanted
to
get
the
conversation
started
around
this
and
take
opinion
of
the
community.
What
they
think
think
so,
if
you'd
like
to
discuss,
please
feel
free,
I'll,
probably
try
to
take
a
note
or
feel
free
to
comment
on
the
issue.
A
D
D
A
Comments
on
this
topic:
good:
let's
keep
moving
provider
update
recharge
for
Kappa.
F
Yep,
so
we
are
starting
discussions
in
Kappa
about
rethinking
how
we
handle
the
networking.
We've
had
lots
of
issues
or
lots
of
requests
for
different
flavors
of
the
networking
other
than
the
opinionated
setup
that
we
currently
have
so
completely
private.
As
you
can
see
there,
it's
been
open
for
a
long
time.
We've
had
some
discussions
around
how
we
might
do
this
and
Andreas
has
started
to
put
a
proposal
together.
We
discussed
it
this
week
and
we
will
be
discussing
it
again
in
the
office
hours
on
Monday.
F
A
Oh
okay,
great
thank
you
so
much
for
for
the
update.
Maybe
just
could
you
give
a
reminder
when
the
cup
of
salaries.
A
Great,
so
if
someone
is
interesting
to
how
to
improve
networking
in
a
cluster
API
provider
for
AWS,
please
join
next
office
hour
and
take
a
look
at
this
proposal.
A
E
Yeah
I'm,
putting
together
the
list
for
cluster
API
1.6
release
team
I've
got
a
few
openings,
still
left
for
all
of
the
teams.
So
that's
the
release,
lead
team,
the
CI
team
and
the
comms
team.
If
anybody
is
looking
to
join
or
has
interest
or
knows
of
somebody
with
interest,
please
feel
free
to
reach
out
to
myself
or
anybody
on
the
cluster
API
release
team,
and
we
can
put
you
on
the
list.
A
B
You
Stefan,
but
you
also
share
this
on
slack
and
maybe
on
the
mailing
list,
because
most
of
you
are
not
here,
and
most
of
them
are
not
always
three
Imaging.
Okay,
I
see
it
yeah.
E
B
I
mean
might
be
also
good
because
we
have
so
many
managers,
so
so
many
channel
so
many
messages
channels.
So
probably
just
I,
don't
know
very
limited.
Target
group
of
we
only
get
those
who
are
reading
every
message
on
our
Channel.
A
A
If
I
remember
well,
some
time
ago,
we
discussed
that
we
are
going
to
postpone
to
the
next
release
cycle
the
the
work
for
moving
RCA
jobs
to
AWS
yeah.
Maybe
maybe
it
was
success
couple
of
time
ago.
Maybe
I
did
not
give
this
a,
but
one
of
the
options
that
we
consider
at
the
time
was
to
oversize
a
little
bit
the
CI
Senior
Team.
So
they
can
drive
this
effort.
Let's
keep
this
in
mind
when
doing
the
stuffing
and
yeah
I
cannot
I
can
only
Echo.
A
The
call
for
Action
working
in
the
CIA
in
the
release
team
is
a
great
way
to
learn.
We
had
a
a
very
nice
group
of
contributors
joining
working
with
the
team.
A
They
grow
it
up
in
the
contributor
ladder
and
then
they
make
a
name
for
themselves
in
the
in
in
the
community,
and
so
it
is
super
important
for
for
the
project,
but
it
is
also
a
great
opportunity
to
grow.
So
if
you
are
interested
reach
out
to
Joe.
F
I
guess
in
a
similar
vein
as
well
for
people
interested
in
providers
pretty
much
all
the
providers
could
do
is
more
help.
I
know
their
debits
provider
and
the
gcp
provider
are
bottlenecked
on
just
do
it,
as
is
most
open
source
on
doing
reviews
and
and
looking
at
the
issues.
But
if
anyone's
interested
in
developing
providers
to
get
involved,
I
would
say
just
reach
out
to
one
of
the
providers
in
the
slack
or
something
like
that,
because
it'd
be
greatly
appreciated.
D
A
Just
I
didn't
catch
the
main
problem.
What
is
Google
and
the
other
is.
F
Aws,
like
I
said
it
was,
is
just
I
guess
it's
a
lot
more
active
a
lot
more
used
than
the
gcp
one,
but
we
really
struggle
just
to
get
reviews
and
and
new
features
in.
A
B
D
B
Yeah
I
don't
know
if
someone
offer
released
him
want
to
take
it
over
and
I.
Don't
know
if
someone
already
mentioned
it,
but
one
five,
zero
beta
one
was
just
released
like
two
minutes
ago.
If
I
got
to
correct
me
from
Korean,
so
just
FY.
E
Yep
the
150
beta
one
was
just
released
just
like
Stefan
said
two
minutes
ago,
so
awesome
work,
team,
great.
A
Just
amazing
doing
the
release,
while
doing
the
meeting
is
a
real
multitasking.
Thank
you
guys
for
the
great
work
and
yeah.