►
From YouTube: 2021-06-24 CAPZ Office Hours
Description
Cluster API Provider Azure office hours for 2021-06-24
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.
A
C
I
I
guess
my
open
discussion
thing
is
really
more
of
a
psa.
If
we
want
to
do
it
now,
because
I
don't
think
so
I'll
go
ahead.
Just
like
last
month,
unfortunately,
kubernetes
patches
came
out,
and
then
we
had
some
issues
in
the
pipeline.
The
windows
versions
from
last
thursday
are
published
and-
and
I
had
and
I
figured
I
think
we
figured
out
a
way
forward
to
fix
what
broke
so
probably
by
tomorrow.
They'll
all
be
done.
B
C
C
A
B
Yeah
so
also
sort
of
a
psa,
I
guess,
but
as
we're
getting
closer
to
the
release,
we
started
working
on
the
release
notes
for
cappy
with
the
captain
maintainers.
I
think
we're
hoping
to
get
that
ready
by
end
of
today,
but
I
in
the
meantime,
since
this
is
a
really
big
release,
there's
hundreds
of
commits
in
it.
B
I
thought
we
should
get
a
head
start
on
our
release,
notes
and
try
to
maybe
highlight
what
our
users
should
pay
attention
to
like
what
are
the
things
in
the
release
that
we
care
about
showing
since,
like,
I
think
it's
going
to
be
really
hard
to
digest.
The
entire
t
of
the
release
notes
like
if
you're,
a
user
and
you're
trying
to
go
through
every
feature
in
bug
fix
that
merged.
B
So
I
started
a
dock
which,
for
now
just
has
like
a
really
rough
draft
with,
like
the
generated
release,
notes
basically-
and
I'm
not
even
sure
that
includes
everything
that
has
two
so
far,
because
I
was
still
trying
to
figure
out
how
to
get
it
from
zero
four
zero,
but
without
stuff
that
went
into
the
patches
since
we
branched
off.
At
some
point,
after
releasing
from
master
branch
for
a
while
so
yeah,
but
everything-
that's
just
to
say,
I'd
love
some
help
on
that.
B
But
if
you
have
other
suggestions
of
things
that
are
in
the
release
that
should
be
called
out
there
please
add
to
it
and
then
let's
write
like
a
one
to
two
sentence
summary
for
each
one
to
describe
like
what
it
does
and
why
it's?
Why
it's
a
big
deal
so
yeah,
that's
the
dock!
Everyone
here
should
have
access
already,
but
let
me
know
if
you
don't.
B
B
A
B
B
A
B
B
B
A
B
B
D
So
hopefully
I
get
that
done
and
then
the
other
issue
that
I
will
the
other
thing
I
have
to
do
that
I
will
create
a
different
issue
for
is
updating
the
actual
templates
and
then
adding
a
deprecation
warning
saying
that
this
is
going
away.
I
guess
in
the
next
release
or
something
that
environment
variables
are
going
away.
You
have
to
use
the
actual
cluster
identity.
D
B
D
A
A
D
D
A
A
C
C
Wait
a
second,
let
me
make
sure
yeah
all
right,
so
I've
I'll
make
it
a
little
wider.
So
I've
had
this
pr
out
there
for
a
little
while,
but
you
know
it's
not
very
well
timed
with
respect
to
the
release
that
we're
doing
so.
I
don't
expect
we
need
to
merge
it
anytime
soon,
but
essentially
this
replaces
the
jaeger,
collector
and
and
the
stuff
we're
doing
for
tracing
with
the
open
telemetry
component
tree.
C
It's
been
sitting
out
here
for
a
while,
so
I
kind
of
went
nuts
on
it
yesterday
and
I
have
another
pr
that
eventually
I'll
put
out
there,
that
adds
jaeger
back
in
because
it
seemed
kind
of
like
fender
lock-in
or
not
quite
kosher.
If
the
only
place
you
can
view
traces
is
in
azure
where
you
might
have
to
pay
for
it,
so
I
put
jaeger
back
in
there
and
so,
let's
hope
this
works.
C
So
at
the
beginning,
the
meaning
literally
all
the
prep
I
did-
was
make
tilt
up
and
I
got
lucky
with
calico,
so
it
actually
came
all
the
way
up.
For
some
reason,
ephemeral
failed,
but
I
don't
care
so
I
just
started
up
windows,
so
there
would
be
some
actual
traces
to
look
at
you
can
see.
Now
we
have
an
open,
telomere,
telemetry,
collector
agent
and
an
open
telemetry
collector
resource.
C
It's
it's
the
definition
of
an
unstable
api.
So,
but
the
nice
thing
you
can
do
now
is
click
on
jager
all
in
one,
for
example,
and
you
get
this
link
here
view
traces
that
opens
up
the
jager
all
in
one
component
and
you
can
just
query
four
traces
and
we
should
have
some
by
now,
because
we've
been
actually
deploying
stuff-
and
here
we
go.
Let's
find
something.
That's
interesting
that
took
more
than
a
second,
let's
say.
C
This
is
just
running
on
it
in
memory
it
doesn't
have
a
real
backing
store,
like
obviously
jager
really
should,
but
for
development
purposes.
This
is
they're
out
of
the
box.
I
don't
think
it's
using
a
lot
of
memory
and
it's
super
convenient
for
doing
this
kind
of
stuff,
but
then
we're
also
as
long
as
you
go
ahead
and
put
in
tilt
settings
a
key
to
an
azure
app
inside
sportspace.
C
You
send
them
here
as
well.
It's
a
little
hard
to
find
because
there's
a
million
things
here
related
to
metrics
and
we're
not
populating
metrics
we're
only
populating
traces.
But
if
you
click
on
transaction
search
say
show
me:
what's
happened
in
the
last
30
minutes.
You
get
essentially
a
similar
view
to
what
we're
looking
at
in
jager.
Let's
find
a
meaty
one
here
to
poke
at
come
on.
C
That's
it
pretty
much.
The
overall
take-home
story,
I
guess,
is
you
know
we
can
it's
a
big
win
for
us
to
have
open
telemetry,
which
we
already
did,
but
now
now
we're
kind
of
all
in
on
the
otlp,
their
recommended
collectors
and
stuff
like
that,
and
the
nice
thing
is
so
we
can
collect
everything
in
one
way
and
then
fan
it
out
and
send
it
to
whoever
we
want
in
this
case
we're
sending
it
to
jaeger,
even
though
we're
not
collecting
traces
in
the
jaeger
jaeger's
preferred
format.
In
the
first
place.
C
C
C
C
C
D
C
And
if
you
don't
set
it
to
that
right
now
it
actually
you
get
a
warning
until
which
might
be
a
little
heavy-handed,
especially
now
that
we
have
jaeger
in
there
as
a
default.
So
I
might,
we
might
think
about
changing
that,
because
a
warning
shows
up.
As
you
know,
it's
kind
of
in
your
face
here
and
tilt.
C
So
I
guess
my
overall
question
is
what
I'm
running,
what
I'm
showing
you
here
amounts
to
an
xxl,
it's
a
huge
ton
of
code
change,
and
so
I
probably
prefer
to
stage
it
the
way
it
is
now
and
have
this
be
a
follow-on
pr,
but
I
also
don't
want
to
distract
from
the
release
stuff.
So
just
look
at
it
when
you
have
time,
if
you
can.
A
C
A
That
was
a
fantastic
demo
and
I
please
encourage
anyone
who
would
like
to
do
a
demo
in
the
future.
Please
do
we
love
seeing
it
or
I
do
at
least
I
don't
want
to
speak
for
anybody,
but
that
was
a
great
job
man.
Thank
you
all,
right
with
that
said,
we
have
one
more
week
to
sprint
towards
the
finish
line
and
get
zero
five
zero
out.
I
want
to
thank
everybody
for
their
effort
so
far
and
look
forward
to
getting
this
new
release
out
and
then
talking
about
it
with
everybody.