►
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
Hello,
everybody
welcome
to
cluster
api
azure
office
hours.
Cluster
api
is
and
cluster
api
api
provider.
Azure
are
both
projects
of
the
sig
cluster
life
cycle,
kubernetes
subproject.
A
So
at
the
beginning,
we
try
and
well,
if
you
want
to
add
your
name
to
the
attendee
list
here,
please
do
so
if
anybody
here
is
here
for
the
first
time
and
wants
to
say
hello
I'll
give
a
minute
for
you
to
identify
yourself
and
tell
us
why
you're
here.
B
Hello:
everyone,
my
name,
is
danny
brazo,
I'm
a
software
engineer,
labor
apprentice,
we're
in
the
microsoft
option
for
improv
team
and,
like
the
question
that
I'm
here
today,
I
want
to
talk
to
you
a
little
bit
about
the
cluster
api
extension
for
australia
cli.
C
A
So,
let's
move
on
to
open
discussion.
First
thing:
everybody
is
probably
aware
of
this.
I
think
everybody
here
had
a
big
hand
in
it.
Actually,
so
pat
yourself
on
the
back,
there's
a
new
release
version
one
three,
oh
there's,
actually
quite
a
few
changes
in
here
I
don't
know.
Is
there
anything
you
want
to
highlight
cecile.
D
No,
nothing
thanks,
nothing
about
the
content.
I
guess.
Maybe
we
should
talk
about
our
trial
to
do
a
really
status
and
deprecation
of
do
you
want
to
talk
about
that.
A
Yeah,
what
did
we
come
up
with
in
the
slack
thread?
It
seemed
like
the
consensus
from
elsewhere
was
just
yeah.
We
should
do
it
more
often,
but
do
we
get
more
concrete
than
that.
D
Yeah
so
for
now
I'm
proposing
that
we
try
doing
every
two
months.
I
feel
like
more
than
two
months
is
too
often
and
my
two
month
might
even
be
too
much
and
we
might
decide
to
scale
back
a
bit.
But
let's
try
this
out.
So
I
opened
the
new
milestone
for
1.4
and
that
is
targeted
for
july
6,
since
that's
two
months
from
the
last
release,
and
so
in
issues.
D
A
D
We
go
so
we'll
try
to
like
put
a
due
date
every
time
we
start
a
milestone
before
like
right
after
we
get
a
new
release,
we
create
the
milestone
for
the
next
release
and
we'll
try
to
put
the
due
date
at
that
time.
We
decide
when
we're
going
to
release
the
next
one,
and
that
gives
people
a
good
idea
of
when
to
expect
the
release
and
we'll
try
to
stick
to
that
date
as
much
as
possible.
You
know,
except
like
any
unforeseen.
D
D
If
you
missed
the
release,
because
you
want
to
get
a
feature
in
and
your
future
doesn't
get
in,
you
know
you
can
catch
the
next
one,
hopefully
they're,
regular
enough,
that
it's
not
too
much
of
a
pain
and
then
with
that,
in
terms
of
like
supporting
previous
releases
or
backboarding
to
previous
releases,
we
said:
let's
try
to
give
each
release
of
four
month
maintenance
period
for
now,
because
you
know
we're
a
pretty
small
team
and
more
would
be
too
much
overhead.
D
So
we'll
try
to
have
you
know
right
now
we
just
released
1.3,
so
1.3
and
1.2
are
the
two
currently
supported
releases
that
we're
backboarding
to
if
anything
comes
up
as
a
bug
and
then
as
soon
as
1.4
gets
released,
1.2
gets
archived
and
then
we
start
maintaining
1.3
and
1.4,
so
n
minus
1.
D
Great
question
the
only
place
it's
documented
right
now
is
onsec,
because
we,
you
know
just
came
up
with
it
with
this
release
and
are
trying
it
out
right
now,
I'm
thinking,
maybe
we
like
try
it
out
for
this
really
cycle
and
then
with
the
1.4
release.
We
document
it.
So
maybe
I'll
open
an
issue
and
put
it
in
the
milestone.
So
it's
there
and
you
know
if
we
feel
like
it's
working
well
enough,
then
we
can
document
it.
A
So
we
want
to,
I
mean,
since
we're
intending
to
get
back
to
our
previous
tradition
of
wait.
Where'd,
it
go
sorry.
I
want
to
go
through
some
random
tabs.
A
There
we
go
do
we
want
to
go
through
the
milestone
review
now
or
at
the
end,
since
we
haven't
been
doing
that,
but
we
want
to
get
back
to
it.
A
And
just
fly
over
it
right
now,
since
we
have
the
page
open
and
then
we
can
get
onto
the
rest
of
the
agenda.
Let's
try
that
I
mean
we
don't
need
to
go
through
each
one,
but
does
it
do
people
have
any
status
to
report?
I
can
tell
you
this
one
at
the
end
is
just
basically
waiting
for
some
refinement
on
the
e2e
test,
so
probably
we'll
be
able
to
merge
it
today
or
tomorrow.
I'm
guessing
async
manage
clusters
is
a
huge
one
that
everybody's
had
eyes
on.
D
Yeah,
I
got
some
a
few
good
comments
yesterday,
so
I'm
addressing
those
but
it's
basically
under
review
and
we're
just
iterating
until
we
get
an
approval.
F
Yeah,
I
can
add,
for
the
satcher
support,
so
I
think
we're
very
close
to
getting
this
done.
So
there's
one
pr
for
the
community
galleries,
support
and
once
this
is
in
then
yeah,
the
other
pr
with
the
template
should
be
just
promoted.
Oh
no
wait
actually
not
so
we're
still
working
on
getting
the
fat
car
images
in
the
like
the
production
gallery
like
on
the
on
the
flatter
side.
F
So
yeah
I
mean
I
don't
know
if
this
is
how
long
it
will
take
but
like
over
like,
except
that
the
yeah,
the
the
rest
is
ready.
F
Well
so
like
the
e3
tests
require
the
images
which
the
idea
was
that
yeah
they
will
be
hosted
in
the
in
the
flatware
subscription
and
so
on,
but
yeah.
Maybe
I
can
talk
about
that
in
a
minute,
as
I
made
it
out
in
there.
E
F
Yeah
thanks
yeah,
I
thought
like.
If
there
is
nothing
on
the
agenda,
then
I
can
just
let
you
know
that
yeah,
I'm
adding
this
community
gathering
support,
which
is
new
in
the
in
azure,
which
allows
like
consuming
the
images
from
different
tenants
and
subscriptions
like
without
going
through
the
marketplace.
So
it's
quite
handy
and
it's
in
the
public
preview
right
now
and
yeah.
F
This
is
the
requisite
for
the
for
the
flat
car
support
and
yeah
we're
working
on
getting
like
the
the
gallery,
which
will
be
shared
in
the
in
the
in
the
flat
car
subscription.
F
But
I
actually
had
this
thought
that
maybe
the
reference
images
which
are
now
published
in
the
marketplace-
maybe
they
could
be
migrated
to
the
community
gallery
as
well,
since
the
like
the
like
the
publishing
process,
is
much
simpler
and
yeah.
I
just
just.
I
didn't
create
any
issue
for
it.
Yet
I
just
wanted
to
know
your
your
thoughts
about
it.
A
I
think
that'd
be
great
you're,
blazing
the
trail
that
we
kind
of
hope
to
follow.
In
general,
we
restructured
the
marketplace
offer
just
recently,
and
actually
we
haven't
quite
finished
that
to
stop
using
up
too
many
skus
and
everything,
but
it's
still
just
kind
of
a
hacky
work
around.
A
G
Oh
sorry,
I
did
see
your
hand,
oh
so
cecile,
and
I
did
some
stuff
in
image
builder
a
couple
months
ago,
which
I
think
is
on
a
branch
right
now
to
kind
of
build
those
and
publish
into
marketplace.
So
I
might
be
able
to
leverage
that
to
start
start
that
process
as
well.
G
F
Yeah,
it's
it's
the
same,
so
it's
just
just
that
the
sig
is
shirt
like
when,
when
you
share
the
sig
and
so
you're
building
pretty
much
to
the
sick
and
then
you
share
the
sick
and
you
have
like
a
special
name
which
you
need
to
refer
to
yeah.
So
if,
if
that
would
be
like
a
viable
option,
then
maybe
flat
parameters
can
be
pushed
to
the
sick
instead
of
the
vodka
ones
like,
depending
on
the
bandwidth
and
like
who
gets
the
the
one
published
faster
sure.
D
D
I
believe,
that's
not
the
case
anymore
and
you
can
just
on
board
the
publisher,
but
if
we
still
have
to
onboard
like
every
subscription
that
needs
to
use
it,
that's
you
know
not
very
good
for
like
wider
usage
and
then
also
like,
I
think
it's
still
in
preview,
so
it'd
be
nice
to
wait
for
a
ga
before
we
start
taking
a
real
dependency
on
it.
D
Maybe
we
can
start
testing
it
like
in
our
end-to-end
tests
like
we're
doing
a
flat
card,
maybe
adding
one
for
ubuntu
just
to
scaffold
it
but
yeah,
I'm
not
sure.
If
we
know
the
g
date
publicly
or
not.
I
I
don't
know
what
it
is.
F
Yeah,
I
think
it
was
very
close,
like
june
or
july
1st,
so
yeah,
I
will
create
an
issue
then
to
migrate.
Those
images.
H
What
do
we
think
of
just
putting
it
behind
a
feature
flag,
while
it's
in
preview.
F
I
mean
to
me,
it
seems
like
so
tiny
that
it
doesn't
need
the
the
feature
gate
and
also
the
work
we're
doing
like
changes
the
types
a
little
bit
and
I
would
encourage
people
to
use
that
so
like
there
will
be
like.
Instead
of
the
sharp
gallery
filled,
there
will
be
community
the
compute
gallery,
and
this
one
will
support
both
the
plain
six
and
also
the
shard
calories.
F
D
Cecil,
I'm
curious:
do
you
know
what
the
backwards
compatibility
story
is
for
existing?
I
guess
for
existing
vms.
It
doesn't
matter
because
we
build
a
uvm
every
time,
but
for
existing
skill
sets,
can
you
switch
from
a
marketplace
image
to
a
community
gallery
or
is
it
like?
You
have
to
create
a
new
skill
set
and
you
can't
switch
from
one
to
the
other.
F
D
D
D
B
Yes
might
actually
do
you
mind
like
going
to
the
length
to
the
project,
but
yes,
at
the
meantime,
like,
unfortunately,
I
wasn't
able
to
record
a
demo,
so
I'm
just
going
to
be
talking
to
you
a
little
bit
about
the
project
itself.
B
So
a
little
bit
of
background
project
is
the
cluster
api
extension
for
azure
cli,
pretty
much.
It
aims
to
help
you
create,
create
the
quality
maintenance
kubernetes
clusters
on
azure
by
leveraging
the
the
power
of
cluster
api.
What
what?
Basically?
B
What
it
means
is
that
it
will
help
you
and
guide
you
to
creating
workload
clusters,
and
we
have
some
different
commands
that
allows
you
to
do
so.
So
the
main
part
of
it
will
be
to
guide
you
through,
like
the
entire
process
of
creating
a
workflow
plaster
and
then
afterwards
yeah,
I'm
sorry
at
first.
It
will
help
you
out
to
identify
any
existing
work
and
management
cluster
or
create
a
new
one,
and
then
afterwards
it
helped
me
out
to
just
build
workload
clusters,
and
this
is
accomplished
within
the
azure
cell
life.
B
Once
again,
it
is
an
extension
of
it,
so
you'll
be
running
ac,
cappy
and
also
like
you
can
run
the
help
command
just
to
get
a
more
sense
of
like
the
entire
capability
of
it.
But,
like
the
main
section,
is
creating
a
workload
cluster,
and
this
is
accomplished
by
ac.
Happy
create
matthewman's
scrolling
up
a
little
bit,
so
you
can
show
a
little
bit
of
the
demo.
B
So
what
what
this
command
pretty
much
do?
Is
it
guides
you
through,
like
deciding
and
figuring
out,
if
to
see,
if
you
have
like
already
like
a
kubernetes
cluster
and
to
see
if
you
have
like
the
class
api
provider,
components
installed
and
if
you
don't
it'll
help
you
to
just
installing
them
and
ask
you
like
you'll,
just
make
sure
that
you're
aware
of
like
what
is
going
on
with
the
process
and
if
you're
missing
something
to
help
you
just
create
it
and
or
just
install
it.
B
So
you
you
can
go
through
the
process
of
generating,
like
the
templates
as
well,
and
then
just
creating
your
workload
cluster.
That's
currently
the
biggest
status
of
the
project.
B
What
we're
trying
to
or
kind
of
like
milestones
for
the
project
will
be
like,
besides
just
helping
out,
create
these
templates
but
different
options
that
we
have
for
the
project.
It
will
be
like
also
allowing
you,
as
a
user,
bringing
your
custom
templates
for
the
workload
cluster
pretty
much.
I
allow
you
to
bring
this
and
they
will
help
you
to
run
out
the
process
by
creating
the
management
cluster
and
the
workload
plus
is
based
on
the
specifications
that
you
have
provided.
B
The
other
different
milestones
that
we
have
are
like,
allowing
you
to
probably
cast
the
artifacts
locally,
so
you
don't
have
to
retrieve
them
every
single
time
and
like
they
were
also
looking
for
the
integration
of
azure
workbook
identities
to
bring
up
like
just
simplifies
the
requirements
pre-requirements
of
like
the
different
variables
you
need,
and
finally
we're
looking
and
exploring
to
bring
the
integration
of
cluster
classes
integration
into
the
project
with
the
hopefully
the
fish,
hopefully
that
with
the
future,
soon
adoption
of
it
that's
kind
of
like
the
overall
of
the
project.
B
If
anyone
has
questions
feel
free
to
ask.
Thank
you.
A
A
B
Cool,
and
as
I
was
mentioning
this,
like
tells
you
a
little
bit
of
what
the
capability
of
the
extension
is
and,
as
you
can
see
like,
you
are
able
to
create
a
workload
cluster,
delete
it
or
just
have
some
information
about
it
so
like
that
the
name
section
of
or
your
main
command
will
be
ac
copy.
Create
that
I
don't
know
marketing.
You
just
showed
the
help
yeah.
Thank
you
so
much
so
so
be
working.
B
This
allows
you
to
give
you
the
flexibility
of
to
specify
the
different
components
that
you
may
need,
or
the
specifications
for
your
cluster
itself
like,
as
you
see
like
you,
we
have
the
control,
plane,
machine
counts
and
different
types
of
it,
so
it
is
really
flexible
in
the
sense
of
like
you
can
specify
it,
but
we
also
have
seen
the
need
of
also
different
users
to
bring
their
own
templates.
B
So
we
that's
kind
of
like
one
of
the
the
features
of
milestones
that
we're
working
on
so
pretty
much
what
it
means
like
you
will
be
able
to
assign
or
direct
to
like
a
url
or
for
your
custom
templates
or
like
a
local
file,
and
then
this
command
will
help
you
and
guide
you
to
building
that
workload
cluster
and
also
like
one
of
the
current
methods.
I'm
sorry,
I
just
forgot.
I've
been
working
on
like
in
the
integration
of
a
pivot
method
or
option.
B
What
would
pretty
much
be
seen
like
some
user
requirement
or
integralization
of
quality
api
for
creating
a
cluster
is
creating
a
management
cluster,
but
sometimes
they
don't
necessarily
need
the
much
closer
to
be
permanent.
So
we
just
do
or
pivot
that
we
we
essentially
start
leveraging
the
the
the
power
cluster
ctl
and
its
smooth
capability
to
move
like
the
cluster
workload
objects
into
your
final
workload.
Cluster.
C
Yeah
yeah
that'll
be
thank
you
so
much.
A
Just
just
for
retrospective,
because
maybe
some
people
have
seen
this
before-
I
demoed
a
much
earlier
version
of
this
like
over
a
year
ago,
and
you
know
I
think
it's
super
useful,
because
essentially
the
main
value
I
see
it
is
it
does
all
the
fiddly
stuff
in
the
quick
start
for
you
without
you
having
to
worry
about.
Where
do
I
download
kind
from
where
do
I
get
all
these
things?
A
What
environment
variables
do
I
set,
and
so
that's
a
big
value,
but
we've
heard
a
lot
of
mostly
internal
azure
teams
asking
for
basically
a
replacement
for
aks
engine.
They
want
like
a
fire
and
forget
tool.
They
don't
want
to
understand
cappy,
they
don't
care
about
management
clusters.
They
just
want
what
we
consider
best
practices
generate
a
workload
cluster
and
then
they're
going
to
test
their
stuff
on
that.
A
A
H
Yeah
I
have
two
two
pieces
of
feedback,
one
I
have
or
actually
question
feedback.
So
this
is
really
cool
and
it
makes
it
so
much
easier
so
much
so
that
it
would
be
really
neat
if
it
was
part
of
the
quick
start
itself.
So
have
we
evaluated
the
idea
of
our
quick
start,
documentation
being
less
about
all
the
intrinsics
of
building
cluster
api
and
more
about
hey?
You
can
use
this
tool
to
get
you
started
quickly
and
then
you
know
a
more
in-depth
view
of
hey.
H
H
That's
question
one
feedback,
possibly
I
wonder
if
we
could
run
like
locally
like
a
really
small
k3s
or
something
like
that
and
skip
over
setting
up
an
entire
cluster
locally
and
figuring
out
how
to
you
know,
maybe
skip
over
the
bootstrap
side
and
just
run
this
stuff
quickly
target
the
building
the
cluster
as
opposed
to
building
a
local.
D
H
And
then
building
another
one
abroad
and
then
pivoting
to
reduce
the
these.
You
know,
impact
of
you
know
two
cluster
deployments
just
cure.
If
folks
been
thinking
about
stuff
like
that.
B
Yes,
I
actually
I'm
sorry.
I
might
have
been
a
little
bit
nervous,
my
skip
for
over
my
steps,
and
actually
we
are
actively
also
looking
on
k23
3ds,
to
see
if
it's
a
viable
option
we
are
like
still
debating
if
it
should
be
like
an
additional
option
or
instead
of
being
the
replacement
of
currently
reducing
kind
as
our
temporary
bootstrap
cluster
and
to
be
more
specific
for
the
management
one
side
of
it.
So
we've
just
been
exploring
those
options
as
well.
A
And
as
far
as
the
quick
start,
I
think
that'd
be
great.
I
think
once
this
is
maybe
just
a
little
more
mature
and
we're
confident
can
handle
all
versions
of
the
happy
path.
Then
I
think
yeah
with
the
first
thing,
our
quick
start
for
azure,
maybe
should
be
hey,
just
go
use
this
tool.
But
if
you
really
want
to
know
what's
going
on,
you
can
do
it
the
hard
way.
D
B
Yeah,
actually,
we
just
been
working
on
this.
I
we
have
encountered
this
issue
so
like
in
terms
of
like
best
panders.
What
we're
looking
for,
like
just
a
deleting
a
pivot
cluster
will
be
just
it
itself
will
be
to
go
through
having
another
pivot
so
like.
Essentially,
your
self-managed
cluster
you'll
have
to
pivot
into
like
a
temporal
cluster
and
then
afterwards
delete
the
that
cluster,
but
then
by
running
the
command
on
the
management
cluster.
To
do
so
and
then
afterwards
to
get
rid
of
the
management
cluster.
B
But
we
seem
like,
as
we
are
also
like
working
directly
with
the
associate
li,
probably
or
direct
path,
might
be
to
just
directly
delete
the
the
components
on
the
resource
group
itself
to
prepare,
instead
of
giving
you,
through
the
entire
process
of
like
essentially
doing
another
pivot.
F
D
My
question
was:
I
see
that
there's
been
lots
of
improvements
lately
and
the
last
release
like
if
I
download
captain
cli
the
capy
extension
right
now.
I
get
a
release
from
over,
I
think
a
year
ago.
So
what
what
are
the
plans
around?
Releasing
a
new
version.
A
All
right
yeah
go
ahead.
B
Yeah,
no,
what
I
have
we
have
in
perspective
would
be
like,
as
it
was
mentioned,
just
to
have
a
little
bit
more
maturity
and
then
so,
hopefully
we
can
have
the
real
wins
as
soon
as
possible
yeah.
So
we
probably
you
can
like
the
users
can
have
like
the
new
user
experience
that
we've
been
working
on
and
like
the
features
that
we've
been
working
on.
A
We
might
want
to
consider
doing
a
release
as
soon
as
we
can
justify
it,
because
now
that
I
think
about
it,
we
found
that
one
bug.
So
I'm
pretty
sure
if
you,
if
you
install
it
on
top
of
the
current
version
of
azcli,
there's
some
exception
that
gets
thrown,
that
we
weren't
expecting
because
the
cli
itself
has
changed
quite
a
bit.
You
know
you
remember
that
one
so
we
might
want
to
because
it
may
be
the
case
that
the
zero
zero
three
extension
actually
is
missing
has
some
bugs,
as
a
result
of
that.
A
So
we
can
talk
about
it,
but
maybe
we
should
do
a
release
soon.
Just
so
people
can
try
it
out.
G
Is
there
a
way
to
like
install
like
a
branch
or
something
like
like?
Can
I
install
it
from
master
as
like
or
in
the
main
branch
for
to
to
just
try
out
like
a
preview,
because
I
think
you
were
adding
like
a
url
or
something
yeah,
just
follow
the
developer
instructions
pretty
straightforward.
I
think
cool
yeah,
that
being
able
to
install
from
a
pre-defined
template
it's
going
to
be
super
useful
for
the
windows.
G
G
So
you
may
have
know
from
it
from
a
windows
perspective
I
mean
running
it
on
wsl
will
be
fine,
oh
okay,
sure
I
think
it
like.
That's
probably
from
a
development
perspective
and
the
other
position
people
will
be
using.
It
is
in
like
ci
development
flows
and
so
they'll
be
able
to
run
that
on
a
on
a
linux
machine
from
there.