►
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
today
is
thursday
december
9th,
and
this
is
the
cluster
api
provider
azure
office
hours.
If
you
have
any
topics
or
any
questions
or
demos
or
anything
you'd
like
to
add
to
the
agenda,
please
add
them
under
the
open
discussion
area.
A
For
now,
the
agenda
is
pretty
light,
so
we'll
just
get
right
in
and
it
should
be
a
short
one.
So
do
we
first,
do
we
have
anyone
new
here
who
wants
to
say
hi
or
introduce
themselves?
A
Okay,
I
think
so.
Okay,
all
right,
if
you
haven't,
please
add
your
name
to
the
attendee
list
and
I
guess
milestone
review-
will
just
do
at
the
same
time
as
this
one.
So
I
just
wanted
to
go
over,
so
we
had
said
a
while
back
that
we
would
try
to
do
a
release
on
december
15th
before
the
holidays,
and
then
that
would
be
1.1.
A
Cap
e
is
not
doing
a
release
like
a
1.1
release
until
mid-january,
and
we
had
kind
of
defined
some
things
that
we
wanted
to
see
in
the
release.
So
at
this
point,
there's
like
a
good
amount
of
stuff,
that's
been
done,
that's
very
valuable!
I
think
that
could
you
know,
be
great
to
see
in
a
release,
but
at
the
same
time,
some
of
the
things
that
we
said
we
wanted
to
do.
A
I
think
mainly
I'm
thinking
of
the
azure
cluster
template
type
to
support
cluster
class
and
then
making
most
of
the
azure
services
async.
Those
two
are
still
in
progress
and
haven't
completed,
so
I
just
wanted
to
see
with
the
group
what
we
wanted
to
do.
A
We
could
still
cut
the
release
as
planned
on
december
15th
and
then
what's
in
there
makes
the
cut
and
then,
if
not,
it
will
just
have
to
wait
until
1.2,
it's
possible
that
we'll
have
maybe,
like
some
of
the
services,
be
async,
but
some
of
them
not,
but
that's
not
a
problem
really
or
we
could
say,
there's
no
rush.
Let's
just
do
the
same
as
cappy
and
release
mid-january
just
wanted
to
see.
If
people
had
thoughts
on
that.
B
With
my
analogican,
I
think
we
discussed
this
a
while
back
that
we
want
to
try
to
stay
aligned
with
copy
with
releases
right,
especially
in
terms
of
numbers.
So
in
my
opinion,
it
makes
a
lot
of
sense
to
delay
until
copy
releases,
1.1.
B
A
Okay,
I
guess
the
only
argument
I
would
have
like
pro
releasing
next
week
is
that
we
did
have
some
improvements
for
aks
that
were
emerged
a
while
back
and
there's
a
lot
of
flakiness
before
that
improvement
was
merged.
I
forget
what
the
exact
I
think
this
was
one
of
them,
but
so
it
would
be
nice
to
get
that
release
to
folks
earlier
I
like
sooner
rather
than
later.
So
that's
just
one
yeah
david.
D
Yeah,
I
can
speak
to
that
directly.
Can
everybody
hear
me?
Alright?
Yes,
okay,
fantastic,
okay!
So
in
the
scenario
where
you're
building
managed
clusters
across
different
regions,
for
example,
let's
imagine
our
tests
are
running
in
the
western
u.s
and
we
are
spinning
up
a
cluster
in
west
europe
in
the
scenario
where
our
tests
are
running
here,
we're
going
to
make
we're
going
to
hit
a
load
balancer
when
we
go
to
talk
to
azure
and
it's
going
to
load
balance
us
to
the
closest
region
right.
D
So
when
we
do
that,
let's
imagine
we
get
load
balance
to
western
u.s
and
from
there
we're
asking
azure.
Hey
tell
me
if
these
vmss,
these
virtual
machine
scale
sets
have
been
created
in
western
europe,
we
have
seen
spikey
traffic
where
it'll
be
north
of
20
minutes
before
we
find
out
those
resources
were
created
and
that
that's
what
led
to
our
tests
being
so
flaky
is
that
cross-region
replication
of
this
these
resource
metadata
values
were
too
slow
that
our
tests
were
actually
not
not,
it
wasn't
functional.
D
So
I
I
think
it's
actually
critical
for
anybody
using
managed
machine
pools
to
to
have
this
this
functionality,
whether
we
wait
or
whether
we
do
it
sooner
that's
up
to
the
group,
I
suppose,
but
it
definitely
is
something
that
will
make
their
lives
a
lot
better.
B
A
It
wasn't,
it
was
a
it
wasn't,
a
clean
cherry
pick
and
eventually
we
just
said
since
we're
releasing
soon.
There's
no
point
in
you
know
doing
the
manual
chair
thick,
so
I
mean
we
can
always
come
back
on
that,
but
so
I
guess
that
would
be
the
the
reason
I'd
say.
We
want
to
release
and
yeah.
C
A
It
would
it
just
wasn't
a
clean
cherry
pick
into
the
1.0
branch,
so
we
would
have
had
to
like
manually
resolve
the
merge
conflicts
which
we
could
do
we
just
at
the
time.
But
there
was,
you
know
no
point
in
doing
that,
since
the
big
release
was
coming
up.
A
But
now,
if
we
delay
the
big
release,
it's
maybe
more
worth
it
so
yeah.
I
don't
know.
A
The
other
thing
is
in
terms
of
what's
coming
next
for
1.2.
I
think
we
already
have
a
lot
just
from
what
we
had
talked
about
in
this
discussion
right
here.
I
think
the
big
one
is
that's
getting
a
lot
of
upvotes
also.
Is
the
azure
managed
clusters
getting
those
out
of
experimental,
so
I
would
propose
that
that
be
our
focus
for
the
next
release
cycle,
maybe
along
with
just
the
cluster
class.
A
A
I'm
leaning
towards
releasing,
but
I
don't
know,
does
anyone
have
any
strong
objections?
I
guess
your
opinions.
I
think
I
guess
the
way
I
see
it
is
it's.
A
We
need
to
get
into
the
habit
of
doing
the
releases
when
we
said
we
would
do
them,
regardless
of
which
work
was
not
completed,
and
since
this
time
we
said
we
would
do
it
december
15th.
I
think
it's
fair
to
do
it
then,
if
next
time
we
think
we
should
align
with
kathy.
We
should
say
that
ahead
of
time.
C
C
I
I
didn't
realize
the
aksfix
was
dangling
out
there
and
we
couldn't
put
it
in
a
patch.
A
Cool
all
right
that
sounds
good,
and
then
I
guess
we
still
have
yeah
a
couple
of
days.
So
maybe
some
of
the
async
work
we'll
get
over
the
line.
A
lot
of
the
pr's
are
open,
pretty
much
almost
there,
but
have
been
kind
of
in
a
rebase
tangle.
So
so,
hopefully
that
will
move
forward
very
fast
once
we
unblock
it
all
right.
So
that's
all
I
had
for
the
release.
A
I
guess
the
other
only
point
I
had
was
just
a
reminder
that
this
is
our
last
office
hours
of
the
year
since
the
next
one
will
fall.
I
think
on
december
23rd
or
something
like
that,
so
I
guess
we'll
see
everyone
in
the
new
year.
I
know
some
of
the
maintainers
are
taking
time
off
during
the
holidays,
so
if
your
pr
is
not
getting
reviewed
as
fast
as
usual
or
if
you're
not
getting,
you
know,
replies
like
please
keep
that
in
mind,
but
we
do
like
welcome
prs.
A
If
you
wanna,
you
know
work
on
some
stuff,
some
cool
stuff
during
the
the
holidays
or
if
you
have
a
bit
of
a
slower
time
so
yeah,
that's
all
I
wanted
to
say.
Does
anyone
else
have
anything
to
add.
A
All
right,
yeah,
david
you're
out
after
tomorrow,
okay,
so.
D
A
All
good
enjoy
your
vacation
and
I
think
cheyenne
is
back
tomorrow,
so
we'll
lose
one
maintainer
and
get
one
back
and
then
him
and
I
will
take
care
of
the
release
next
week
and
then
I'm
out
the
week
after
that
cool
all
right.
A
Well,
on
that
note,
happy
holidays
everyone
and
see
y'all
in
the
new
year.