►
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
Cool
sorry,
I
coughed
air
right
at
the
beginning,
which
is
good
anyway.
Welcome
to
the
cluster
api
provider
aws
office
hours
on
monday,
the
7th
of
february
2022.
Just
a
reminder:
we
abide
by
the
cncf
code
of
conduct,
so
please
be
kind
to
each
other.
A
The
meeting
notes
I
will
share
in
a
minute
into
the
chat
window.
Please
add
yourself
to
the
list
of
the
attendees
and
any
topics
you
would
like
to
discuss
in
the
agenda.
Just
a
reminder:
we
use
the
raise
hands
feature.
So
if
you'd
like
to
talk,
please
raise
your
hand
and
then
that'll
be
good.
Looking
at
the
participant
list
is
anyone
new
to
a
kappa.
B
Hey
folks,
I'm
abhinav
and
I've
just
recently
got
to
know
about
kata
and
I've
actually
started
contributing
from
today
itself
and
I've
got
in
touch
with
richard
and
he
has
been
nothing
but
very
helpful
and
kind
to
me
so
far.
Thank
you
so
much
for
that.
Richard
and
yeah.
I
would
like
to
like
continue
contributing
to
the
project,
and
there
are
a
few
issues
that
I've
been
working
on
at
the
moment,
and
maybe
we
can
discuss
the
issues
in
this
meeting
itself
or
maybe
offline
like
in
the
black
funnel
yeah.
A
Cool
yeah
well
welcome
have
enough
yeah,
so
there
is
something
you
would
like
to
to
discuss
in
this
meeting.
Yeah
feel
free
in
the
in
the
in
that
document.
Sorry,
if
you,
if
you
add
it
to
that,
we
can,
we
can
talk
about
it.
So,
yes,
that's
no
problem,
so
yeah
future
meetings,
if
you're
like
stuck
with
anything
or
you-
have
want
to
get
a
wider
input
on
something
yeah
feel
free
to
add
it
to
any
of
the
office.
A
Hours
meetings
and
siddharth
will
be
coming
along,
probably
in
about
15
minutes,
but
she
will
be
joining
in
a
bit
and
yeah
winnie
on
your
comment
about
the
calendar,
invite
so
yeah
that
the
pr
has
been
done
in
the
kate's
community
repo
to
move
the
time,
but
it
doesn't
appear
to
have
moved
to
time
in
the
calendar.
A
A
I
definitely
know
the
time
is
not
work
cool.
So
let's
get
started
with
the
agenda,
so
we
don't
have
any
psas
today.
A
So
we
can
move
on
to
the
action
items
so
for
the
ones
that
sadif
had
so
siddiff
was
going
to
create
an
issue
for
the
flat
car
images,
so
she's
not
that
as
done,
but
we
can
once
the
left
joins.
We
can
come
back
to
that
if
needed.
A
I
had
an
action
item
also
to
update
the
launch
template
proposal,
which
I
will
we're
covering
later
on
in
the
in
the
agenda.
So
don't
need
to
talk
about
it
now
and
then
siddharth
also
had
a
action
item
to
review
the
ignition
pr.
A
We
both
took
an
action
item
to
see
if
there
was
any
built-in
notification
in
prowl.
So
I
didn't.
I
didn't
look
into
that
in
all
honesty,
and
I
know
that
siddiff
has
put
note
in
there
to
say
the
weekly
reminder
in
the
slack
channel
which
someone
checked
today,
which
is
good
cool
so
moving
on
to
the
gender.
If
there's
any
questions
on
that
to
start
with.
A
No
good
good
cool,
so
winnie
you
got
the
the
first
agenda
item
on
consistent
login.
C
C
So,
for
example
like
if
you
look
at
the
first
example,
some
reconciliator
started
like
level
0
somewhere
like
at
level
2
and
mostly
at
deriver
too.
But
there
are
some
inconsistencies
and
also
like.
If
you
look
at
number
two,
the
formats
of
the
controllers
are
actually
pretty
different.
So
even
if
you're
wondering
it's
like
wondering
about
for
a
while,
so
yes,
I
actually
listed
a
few
examples,
but
I
hope
to
gather
some
inputs
from
the
community
what
if
they
saw
anything
consistency
what
they
want
to
improve.
C
So
I
will
probably
post
it
in
a
slack
also
because
we
don't
have
a
lot
of
people
in
office
hour
but
feel
free
to
add,
like
your
your
cases
or
like
your
opinion,.
A
Cool
yeah
on
that
one
I
did
add
a
note
down
at
the
bottom
here
so
gokay
has
also
been
working
on
a
related
issue,
which
is
someone
raised
the
so
I
can
offer
that
one
as
well,
so
I
can
have
a
look,
so
it's
sort
of
related,
so
when
they
were,
they
were
looking
at
the
logs.
They
wanted
an
easy
way
to
be
able
to
grip.
A
A
A
Cool,
so
any
questions
on
that
no
no
raise
hands
cool,
so
the
next
one
is
me,
so
I
have
updated
the
launch
template
proposal
based
on
discussions
that
I
had
with
richard
chen,
who
is
doing
the
work.
A
So
if
you
have
any
comments,
that's
actually
the
that's
nothing.
So
yes,
the
proposal
is
there
is
this
pr,
so
you
can
either
add
any
comments
to
the
the
pr,
but
what
I've
also
done
is
added
it
as
a
github
discussion
as
well,
so
you
can
always
click
through
to
the
discussion
and
just
just
read
it
there.
If
you
want,
is
anyone
interested
in
me
just
taking
people
through
what
the
proposal
says
or
do
you
just
want
to
read
it.
D
Yeah,
I
have
gone
through
it,
so
I
I'm
pretty
new
and
maybe
it
sounds
like
a
new
question,
but
I
want
to
understand
like
so
in
this
proposal
we
are
talking
about
like
we
are
launching
the
aws
launch,
template
for
managed
machine
pools
right
and
currently
we
have
certain
fields
that
we
are
using,
like
the
ami
type
and
other
fields
that
you
were
mentioning.
So
my
question
is
like
how
introducing
aws
launch
template
will
help
others,
because
we
already
have
certain
fields.
A
Yeah,
that's
a
good
question,
so
there's
a
number
of
so
this.
This
problem
is
specifically
with
the
managed
machine
pools.
So
when,
when
you
create
a
managed
machine
pool
in
with
the
eks
api,
you
can
create
it
with
just
things
like
the
ami
and
the
instance
type,
which
doesn't
necessarily
create
a
launch
template
explicitly.
A
D
So
basically
launch
template
will
help
us
in
like
basically,
we
just
provide
the
id
and
it
auto
fills
all
the
four
fields.
Is
it
like
that
about
the
launch.
A
So
this
will
essentially
reuse
so
there's
basically
a
struct
that
we
use
in
the
aws
machine
pool
currently
where
it
exposes
some
of
the
properties
of
a
machine
pool
and
the
existing
controller,
for
that
will
create
a
a
launch
template
for
you
and
it
versions
it
as
well
for
you.
So
if
you
change
it
it
will,
it
will
create
a
new
version
of
that.
A
So
with
this
we're
proposing,
we
adopt
the
same
mechanism.
Basically,
so
it's
consistent
between
the
machine
pools
but
yeah,
that's
a
good
point
actually,
so
you
might
want
to
bring
your
own
machine
sort
of
bring
your
own
launch
template,
because
that's,
I
think
that
that
was
what
you're
sort
of
suggesting
what
you.
If
you
said,
you
just
supplied
a
launch
template
id.
D
A
A
Yeah,
that's
good,
that's
good
question
so
that
we
did
consider
one
alternative.
So
again
you
know
this
is
of
interest.
So
so
one
other
option
was:
let's
go
down.
A
A
D
So
like,
if
we
go
with
this
approach,
then
it
can
be
useful,
like
for
the
machine
pool
and
both
like
for
machine
food
and
manage
and
manage,
but
like
do
we
consider
like
during
proposals?
Do
we
also
consider
the
effect
estimation
or
something
some
like
any
efforts
that
we
require
to
do
it,
because
there
will
be
a
lot
of
changes
if
we
go.
A
D
This
up
so
do
we
also
consider
like,
while
selecting
any
solutions,
yeah.
A
Yeah
definitely
yeah
yeah,
yeah
yeah,
that's
a
good
point.
So
that's
I
guess
that's
effort
for
actually
implementation
and
then
there
I
there's
things
like
f
long
term
effort
if
we
need
to
deprecate
fields
across
multiple
specs.
So
actually
that's
one
of
the
things
that
you
know
this
alternative
that
we
considered
so
that
it
would
require
deprecation
fields
in
two
crds,
so
in
aws,
machine
pool
and
aws
management,
machine
pool,
which
is
a
lot
of
effort.
So
yeah,
that's
yeah.
It's
very
much
part
of
it.
A
But
yeah,
if
you,
you
know,
feel
free
to
comment
on
the
on
the
discussion
or
or
the
pr
yeah.
So
those
type
of
things
we
need
to
make
sure
that
we've
covered
off.
A
Cool
thanks
so
uh-huh
yeah,
so
this
is
a
another
one,
so
we
so
there
is
so.
We
currently
have
an
issue
with
the
release
notes
generation.
So
we
we
are
currently
using
the
the
cli
from
from
the
kubernetes
release
repo.
So
there
is
a
problem
with
that
at
the
moment.
So
there
was
a
discussion
about.
You
know
how
to
fix
that.
A
But
then
we
moved
on
to
a
discussion
as
to
whether
we
should
just
change
and
adopt
the
the
github
release,
notes
generation,
so
that's
built
in
now,
so
you
can
get
github
to
to
generate
that
change
list
for
you
and
then
instead
use
that
so
yeah.
So
that
was
really
just.
If
anyone
has
any
opinions
on
that,
so
we
can
configure
how
the
release
notes
look.
So
so
also
so
currently
we
have
a
problem
with
as
well
as
this
problem
here,
which
is
to
do
with
the
version
you
know
compilation.
A
We
also
have
a
problem
that
if
someone
in
the
release
note
block
of
a
pr
puts
none,
then
they
won't
that
change
won't
appear
in
the
release,
notes
where
they
basically
made
a
change
where,
even
if
you
put
done
it
would
be
listed,
but
it
would
just
take
the
pr
title
so
there
would
you
know
someone's
change
would
always
be
listed
and
it
was
only
if
you
put
a
release,
notes
section
in
there.
It
wouldn't
use
the
pr
title
where
it
would
use
that
note,
but
they
changed
that.
A
So
as
it
stands,
we
we
miss
changes
in
the
release,
notes
and
then
we've
got.
We've
also
got
this
problem
here,
so
yeah.
So
if
anyone
has
any
opinions
on,
you
know
whether
we
we
should
or
shouldn't
adopt
the
github
release,
notes
generation,
then
yeah
it'd
be
great
to
capture
it.
You
know
either
on
this
issue
or
in
slack
we
can,
because
we
use
the
kinds
and
we
we
generate
sections
in
the
release
notes.
So
we
can
control
which
kind
labels
go
into
which
part
of
the
release
notes.
A
So
you
can,
you
can
create
categories,
so
you
can
configure
the
release.
Notes
generation
and
then
you
can
say
which
labels
go
into
that
category,
so
we
we
do
have
some
control
of
that
and
the
other
thing
it
does
give
us
as
well.
I
I
personally,
like
I
don't
know
if
everyone
else
does
is.
Let
me
just
have
a
look,
so
it
looks.
A
It
will
look
something
like
that,
but
if
you
go
away
so
what
it
also
automatically
does,
is
it
it
identifies
new
contributors
and
it
explicitly
puts
a
section
in
there
say:
hey.
You
know:
sulei
made
his
first
contribution
with
this
change,
which
is
which
is
quite
a
nice
thing
to
have,
I
think,
but
yeah.
If,
if
anyone
has
opinions
strongly
or
you
know
whether
strongly
or
weekly,
either
way,
yeah
it'd
be
great
to
capture
them
on
the
issue.
A
So
sid
f
isn't
here,
so
we
can
jump
ahead
to
abanav
and
the
conversion
functions.
B
Yeah
sure
so
I
might
not
be
like
much
familiar
with
how
the
conversion
functions
are
currently
implemented
within
the
entire
repository.
But
I
was
seeing
some
auto
generated
functions
for
the
conversion
and
they
were
like
kind
of
recursion
that
not
recursion,
but
they
were
calling
one
another
repeatedly,
and
I
was
not
sure
how
I
would
implement
it
personally,
because
the
reference
that
you
pro
that
you
gave
me
for
implementing
one
of
my
own.
I
looked
at
the
current
implementation
for
other
conversion
functions
and
they
were
referencing.
Some
other
auto
generated
functions.
A
Yeah,
the
conversion
functions
are
horrible,
yeah,
so
there's
yeah
so
there's
so
there
is
there's
a
there's,
a
code
generation
part,
so
you
might
have
seen
it
in
the
make
file.
So.
A
Here
they
are
very
scary.
Yeah
there
we
go.
A
So
yeah
conversion,
that's
what
we
want
yeah
yeah,
so
we
have
the
the
the
we
use
this.
This
tool
called
conversion.
Gen
you'll
see
it
there
so
that
that
basically
does
it
will
generally
do
the
code
generation.
So
you'll
see
the
the
the
zed
files
so
yeah,
so
we
we
make
sure
we
run
that,
but
that
does
take
into
account
like
whether
you've
got
a
function.
You've
written
your
own
function
as
well,
so
it
will
also
generate
function,
names
for
you
and
all
that
sort
of
stuff.
A
But
then,
if
you've
created
your
own
function,
it
it
sort
of
takes
that
into
account
as
well.
So
let's
go
to
api.
A
Yeah,
so
the
what
that
generates
is
this.
You
know
the
zitted
underscore.
So
this
is
what
you
is
this
the
bit
you
were
referring
to
have
enough.
B
A
Sort
of
yeah
we
are
actually
before
we
get
into
that.
Do
you
want
to
do
so?
They
have
to
do
there.
Was
you
had
one
a
gender
item,
so
we
could
oh
yeah
yeah.
Did
you
want
to.
A
E
Oh
okay,
yeah,
so
it
is
about
our
sf
nfx
mentorship.
It
is,
it
is
accepted
and
now
accepting
applications
and
we
need
to
design
do
the
design
before
march
and
to
make
it
ready
for
the
intern
to
pick
up
the
like
issues
and
one
one
more
thing
I
want
to
mention
is
a
google
summer
of
code
applications
are
open.
If
anyone
has
any
topics
that
wants
to
add,
I
mean
I
can
definitely
go
ahead
and
do
the
application.
E
I
will
probably
not
be
volunteering
to
mentor
for
for
this
google
summer
of
code,
because
I
will
do
it
this
spring.
A
couple
of
possible
projects
that
could
be
suitable
for
the
this
internship
is
a
support
for
open
telemetry
and
another
thing
is
introducing
a
fault
injector
aws
fault,
injector,
to
increase
our
test
reliability.
E
Those
two
are
a
very
self-contained
to
two
issues.
If
we
wanna
go
ahead
and
do
it
but
yeah,
let
me
know
if
you
are
interested
in
mentoring,
we
can
do.
We
can
do
the
submission
together
because
I
think
you
need
to
be
a
project
maintainer
to
submit
and
yeah
one
more
thing
I
want
to
mention
before
moving
on.
Is
I
built
flat
fire
stable
image
for
kubernetes
v123.3
version
going
forward?
We
will
be
maintaining
the
these
flat
car
images
for
the
new
kubernetes
versions
too.
E
There's
no
one
on
the
flat
car
side
in
the
call
I
wanted
to
chat
about,
if
if
they
want
to
also
build
beta
and
also
flat
car
images,
which
I'm
thinking
will
be
too
much
to
maintain
and
just
building
stable
releases
should
be
enough,
given
that
these
are
only
reference
images,
those
are
not
supposed
to
be
used
in
production.
Actually,
so
yeah
just
wanted
to
bring
this
up.
Also,
I'm
done.
A
Cool
thanks
a
lot.
One
thing
we
did
also
talk
about,
so
that
was
that
you
may
be
interested
in
was
the
release
notes
generation
so
that
three
one
five
three
and
whether
we
adopt
the
github
release,
notes
or
generation
tooling.
Instead.
E
I
am
plus
one
to
that
and
I
like
the
idea
that
we
don't
have
to
have
some
custom
codes
to
actually
create
those
bugs
cleanups
sections
for
the
released
knots
yeah.
Definitely
we
can
go
ahead
and
change
that
I
am
having
issues
with
the
puzzle.
A
Cool
all
right,
I
will
yeah
I'll
update
the
the
issue,
then
brilliant
cool
so
shall
I
is,
does
anyone
else
have
any
gender
items
before
we
come
back
to
the
fun
of
conversion
functions.
A
No
cool
slow,
so
let's
stop
recording
at
this
point
and
then
we
can
we
can
then
then
you
can
screen
share
and
then
we
can
discuss
conversion
functions.