►
Description
A Kubernetes community meeting about the Azure provider for Cluster API. Cluster API brings familiar, declarative APIs to Kubernetes cluster creation, configuration, and management.
A
Cool
hello,
everybody.
It
is
september,
8th,
2022..
This
is
the
kubernetes
sid
cluster
life
cycle,
cluster
api
provider,
azure
office
hours.
A
We
meet
here,
9
a.m,
pacific
time
every
thursday
we're
just
we're
abiding
by
the
cncf
code
of
conduct
since
we're
a
sig
cluster
life
cycle
project
which
basically
boils
down
to
be
courteous
to
everyone
else,
try
to
use
the
raise
hands
feature
in
zoom,
so
we
don't
talk
over
each
other
and
keep
the
participants
window
open.
That's
good
advice
for
me.
I
forget
to
do
that.
A
Okay,
sorry,
I
got
a
bunch
of
a
mac
os
warning
and
error
messages
about
my
audio,
not
working,
but
I'm
gonna
ignore
those
cool.
So
if
you
wouldn't
mind
adding
your
name
to
the
attendee
list
here
just
so,
we
have
a
record,
so
people
can
basically
look
each
other
up.
Later
is
one
of
the
reasons,
and
if
anybody
here
is
here
for
the
first
time
and
wants
to
introduce
themselves
I'll,
go
ahead
and
mute
for
a
second,
you
can
just
unmute
and
say
hello.
A
I
think
I
recognize
everyone,
so
probably
not
all
right.
Let's
move
on
to
open
discussion,
john!
You
want
to
talk
about
your
aks.
C
Yes,
so
yeah
currently
for
azure
managed
clusters.
The
only
aks
features
that
are
implemented
are
ga
features
and
since
there's
at
least
one
request
open
for
a
feature
only
available
in
preview
right
now,
jack
and
cecile
encouraged
me
to
start
a
discussion
on
how
capzi
should
generally
handle
aks
preview
features.
C
So
I
opened
up
the
issue
and
started
a
slack
thread
about
this
too.
To
get
some
initial
feedback,
and,
like
I
mentioned
in
the
thread
whether
or
not
aks
preview
features,
are
something
you'd
use
in
cap.
Z
is
probably
the
most
helpful
feedback
at
this
stage
before
we
dive
too
deep
into
how
this
will
look
or
actually
be
implemented.
C
So
I
know
mike
and
zane
have
already
chimed
in
on
the
issue
and
slack
to
say
that
they'd
be
interested
in
using
aks
preview
features
from
capsi.
So
mike
I
see
you're
on
the
call.
Do
you
or
does
anyone
else?
Have
any
thoughts
they'd
like
to
bring
up
now.
D
Yeah,
so
I
think
this
would
be
really
interesting
if
it
could
be
done
in
a
way
with
a
few
of
the
caveats
that
have
been
mentioned
in
slack
and
supporting
every
preview
feature
under
the
sun.
I
think,
would
be
a
real
big
pain
and
would
detract
from
being
able
to
support
the
features
that
are
out
of
preview
and
really,
you
know,
maintain
the
project
overall,
but
for
some
of
the
ones.
D
I
think
that
if
we
had
a
way
of
measuring
or
gauging
somehow
the
the
true
interest
in
a
preview
feature
ahead
of
time,
you
know
whether
it
be
through
some
sort
of
feedback
solicitation
from
microsoft
itself,
based
upon
their
customer
feedback
or
something
or
just
you
know,
number
of
issues
that
people
have
requested
of.
Saying
hey,
you
know:
can
we
provide
this?
D
I
don't
necessarily
see
a
lot
of
harm
in
it
if
we're
careful
with
the
way
in
which
we
do
the
apis,
the
eventual
deprecation
and
changes
to
them.
I'm
a
little
concerned
about
that
from
a
long-term
maintainability
perspective,
especially
if
the
api,
you
know
declarations
or
contract
changes,.
D
But
but
overall
I'm
supportive
of
it,
and
maybe
that's
just
because
I'm
you
know
my
self-interest
comes
into
play
because
there's
a
few
features
that
I
would
love
to
be
able
to
do
a
preview
feature
of,
but
at
the
same
time
you
know
I
am
a
I'm
a
little
on
the
fence
of
it
just
because
of
a
few
concerns.
But
I
there's
nothing
that
makes
me
say.
I
don't
think
this
is
something
we
shouldn't
take
a
hard
look
at.
C
Cool
steve,
you
have
your
hand
up.
E
Yeah,
you
know
so.
Certainly
I
think
that
there
will
be
a
handful
of
of
preview
features
that
a
lot
of
people
want
to
get
their
hands
on
it.
In
my
experience,
it
tends
to
be
the
networking
ones
there's
so
many
changes
happening
to
aks
networking
that
the
customers
want
to
want
to
work
with
that.
I
think
it
would
be
very
important
to
at
least
have
those
items
so
yeah,
it's
probably
kind
of
an
on-demand
basis,
but
having
the
process
laid
out
and
being
able
to
rapidly
respond
to
those.
C
Cool
does
anyone
else,
have
anything
they'd
like
to
share
now
and
if
not
totally
feel
free
to
just
add
on
to
the
issue
or
the
slide
thread?
Oh
dane,
go
ahead.
C
Sounds
good
mike,
you
have
your
hand
up.
D
Yeah,
the
one
of
the
thought
that
I
had
with
this
is
the
one
advantage
I
could
also
see
for
captain
z
as
a
whole,
with
this
is
just
the
ability
to
preemptively
develop
on
some
features
that
are
coming
down,
the
pipe
versus
being
retroactive
on
it.
So
if
we
were
to
say,
oh,
we
can't
do
any
work
on
preview.
You
know
features
that
are
still
in
preview
until
they're
out
of
preview,
we're
going
to
be
behind
the
curve,
potentially
significantly
always
on
new
things.
D
If
we
somehow
work
in
a
way
to
say
hey,
we
can
do
these
preview
features
when
we,
as
at
the
very
least
when
they're
close
to
being
released-
or
I
don't
know
something
at
least
that
way
there.
We
can
turn
them
out
to
the
ga
when
the
product
gets
close
to
ga
as
well,
so
that
could
that
could
be
a
big
win
from
that
perspective,
as
well.
C
Yeah
that
makes
sense
cool.
I
don't
see
any
other
hands
raised,
so
I
think
what
I'll
do
for
now
is
I'll.
Keep
the
issue
open
and
just
get
some
just
wait
for
some
more
feedback
on
that,
and
then
maybe
next
week
would
be
a
good
time
to
check
in
and
start
to
kind
of
prioritize.
This
a
little
more
concretely
does
that
sound,
reasonable.
A
I
can't
find
the
raise
hand
button,
but
I
wanted
to
chime
in
at
the
end
with
what
mike
was
saying
that
if
we
wait
until
you
know
they're
they're
out
of
preview,
then
we
waited
too
long
sort
of
related
to
that.
We
have
a
pr
that's
out
right
now
to
to
maybe
open
the
door
to
just
to
back
to
back
porting
patches
for
aks
features,
essentially
which
kind
of
breaks
december.
A
But
jack
is
arguing,
and
I
agree
with
him
that
you
know
these
are
important
enough-
that
a
patch
release
might
contain
actual
aks
related
features
reflecting
that
customers
really
want
to
use
this
stuff,
and
also
like
we
said
you
know.
Sometimes
these
features
stay
in
preview
for
a
long
time,
and
so
it's
kind
of
unreasonable
for
us
not
to
take
a
look
at
supporting
them.
A
Next
thing
I
just
put
this
in
here
because
I
looked
at
last
week's
recording
and
I'm
not
sure
we
followed
up
on
this.
I
guess
mike
we
mumbled
about
doing
this.
Should
I
go
add
an
issue
for
this,
so
we
don't
forget,
or
is
it
something
that's
in
progress.
D
A
B
Mike
no
no
worries
well
add
gh
issue,
all
right.
A
And
then
the
last
one,
this
is
kind
of
an
update
for
a
release,
so
we're
trying
very
hard
to
get
1.5
release
done
yesterday.
This
is
sort
of
the
first
time
we're
trying
to
hold
ourselves
to
our
new
schedule,
which
is
you
know,
we're
going
to
release
on
time.
When
the
milestone
says
and
as
you
might
expect,
some
things
came
up
specifically,
we
don't
have.
We
wanted
to
get
a
redefinition
of
how
often
we're
going
to
release
and
what
kinds
of
things
can
go
into
a
patch
release.
A
A
A
But
as
far
as
I
know,
we
just
have
those
two
issues.
I
can't
really.
We
can't
really
say
for
sure
when
the
server
side
apply
thing
will
land,
but
probably
today,
and
then
we'll
go
ahead
and
cut
the
release,
because
since
this
will
be
the
first
cap
c
release
to
vendor
in
capi
1.2,
that's
essentially
one
of
the
required
changes
we
have
to
catch
up
with
that
we
spaced
out
into
the
last
minute.
So
but
that's
all.
A
I
know
about
the
release,
basically
two
more
things
to
finish
and
then
we
should
be
good
to
go.
On
the
other
hand,
if
it
lags
you
know
late
tonight,
we
also
have
a
rule,
although
it's
not
in
the
dock,
but
we
have
an
unsaid
rule
that
we
don't
release
on
friday.
So
we
might
decide
just
to
wait
till
monday
in
that
case,
but
hopefully
today
any
questions
about
that.