►
From YouTube: 2021-05-13 CAPZ Office Hours
Description
Cluster API Provider Azure office hours for 2021-05-13
Meeting agenda: http://bit.ly/k8s-capz-agenda
Join https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle if you don't have edit access to the meeting agenda.
B
All
right,
hello,
everyone
welcome
to
the
cluster
api
provider
azure
office
hours
meeting
today
is
13th
of
may
2021
before
we
get
started
a
few
housekeeping
things
to
keep
in
mind,
use
the
race
hand
feature
in
zoom
in
case
you
want
to
voice
your
opinion,
but
still
since
we
are
just
a
small
group,
I
think
it's
fine.
Even
if
you
don't
do
it,
we
are
a
kubernetes
six
projects,
so
we
follow
the
rules
there,
which
is
basically
be
kind
to
each
other.
B
C
Yeah
hi
there
guys
so
my
name's
daniel,
so
I
work
for
microsoft
and
I've
just
joined
the
azure
acting
so
I'm
working
on
the
kubernetes
part
of
that
so
hi
everyone.
That's
me.
B
Welcome
daniel
anyone
else.
B
I
don't
see
anybody
raising
that.
Okay,
all
right,
let's
get
started,
I
I
don't
see
any
psas
today.
So
that's
unless
anybody
wants
to
add
anything.
B
Now:
okay,
let's
jump
to
the
open
discussion.
So
I've
added
one
item
here.
So
let
me
just
go
ahead
and
discuss
this
so
so
this
is
recently
we
made
a
fix
for.
B
The
the
cloud
provider
config,
which
is
basically
like
we,
we
had
an
issue
where
we
created
clusters
prior
to
zero,
four
eight
and
when,
when
we
upgraded
the
providers
to
zero
four
nine
and
then
when
we
upgraded
the
clusters,
those
clusters
failed
because
it
couldn't
find
the
secret
azure.json.
B
This
is
because
we
split
them
into
control,
plane,
azure.json
and
worker
node.json
in
zero
four
nine
to
fix
that.
We
basically
like
copied
as
you.json.
B
With
the
control
plane,
as
you
do
json
so
this
this
was
kind
of
a
temporary
workaround
that
we
did
to
get
it
fixed
for
zero
four
x.
B
But
then
we
also
have
to
find
a
way
to
make
it
work
for
clusters,
which
eventually
will
get
upgraded
to
0
5x.
So,
but
we
also
don't
want
to
like
keep
this
hack
in
keep,
keep
it
going
around
in
the
main
branch
as
well.
So
so
I
just
want
to
get
get
an
opinion
on
how
to
handle
this.
B
There
were
a
few
few
things
that
that
the
worker
no
seeker
didn't
need.
So
that's
why
we
split
azure.json
into
control,
plane
and
worker
node,
which
was
done
in
this.
D
D
D
B
Right
right,
yeah,
so
basically,
the
old
clusters
expect
only
azure.json,
but
in
the
new
clusters
we
we
have
updated
the
templates
to
include
control
plane
for
control
plane.
As
you
do
this
one
for
control,
plane,
nodes
and
workers
known
as
utility
software.
B
Providers,
so
we
we
could
technically,
like
forward,
put
this
fix,
but
I'm
not
sure
how
long
we
want
to
do
this,
because
I
feel
that
this
kind
of
a
hack
that
we
wanted
to
do
for
zero
forex
for
backward
compatibility.
A
Sorry,
I
was
gonna
raise
my
hand,
but
I
couldn't
get
my
fingers
to
the
buttons
quick
enough.
So
could
we
have
some
kind
of
a
mutation
a
web
hook
to
handle
this.
B
B
A
One
other
item:
to
throw
up:
how
long
do
we
like,
I,
I
think
we
have
like
one
or
two
versions
of
backwards
compatibility
right
right.
That
was
my
understanding.
A
So
why
don't
when
we
go
and
put
out
5x
what
if
we
go
and
document
you
must
upgrade
to
5x
and
it
can
be
a
step
rise
upgrade
too.
So
if
somebody
went
from
4x
and
said,
okay,
hey,
we
need
to
upgrade
to
5x,
and
then
we
could
upgrade
to
6s
they
they
couldn't
jump
from
four
to
six.
If
you
jump
from
four
to
six,
then
you're
gonna
have
bad
day.
A
If
we
document
that
pretty
well
that
that's
that
falls
within
our
our
support
statement,
and
I,
I
think,
kind
of
leads
people
down
a
path
where
they
can
be
successful
even
later
stages.
Like
say,
say:
you
know,
someone
hasn't
upgraded
for
a
long
time.
They
still
have
a
pathway,
it's
just.
They
have
a
longer
path.
Maybe.
B
Right
yeah,
I
think
it
makes
sense
documented.
I
can
stuff
like
having
this
workaround
lying
lying
there,
but
do
you
want
to
like
remove
it
in
0
5x
itself,
or
we
still
want
to
keep
to
keep
it
to
05x
and
then
document
it
for
0
6x?
Maybe
because
we
support
two
versions.
A
I
would
I
would
keep
it
till
6
006
and
then
like
deprecate
in
five
and
say:
hey
this
is
going
away
and
then
in
the
next
one
drop
it
and
that
way
you
have
two
clean
cuts
before,
like
you
have
here's
where
you
can
use
it,
here's
where
it's
going
away.
B
B
Okay,
I
don't
see
any
other
topics.
Any
anybody
want
to
add
anything
in
the
last.
E
Minute,
I
guess,
since
this
is
probably
the
only
audience
that
really
cares,
I'll
just
mention
that
we
had
all
the
kubernetes
patch
releases
yesterday
and
I'm
working
on
building
the
reference
images
for
capsi
for
those,
but
imagebuilder
has
since
changed
to
use
gauss
for
validating
some
stuff,
and
so
so
anyway,
it
may
take
a
day
or
so
for
me
to
catch
up
with
those
changes,
since
there's
only
a
kubernetes
patch
release
like
once
a
month
now,
it's
pretty
often
the
whole
world
has
changed
by
the
time
we
get
to
building
things
again.
B
B
Okay,
then
we
I'll
give
you
like
45
minutes
back
of
your
time.
Thanks
everyone
for
attending
see
you
in
slack.