►
From YouTube: Kubernetes SIG CLI 20220406 - KRM Functions
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
Hello
and
welcome
to
the
karen
function
sub
project
meeting.
It
is
wednesday
april
6th.
We
don't
really
have
much
on
the
agenda
today,
so
I'll
give
opportunity
for
everybody
to
contribute
a
topic.
If
there's
anything,
you
want
to
bring
up
and
otherwise
we'll
just
do
some
quick
stand-ups.
A
So
first
of
all
call
for
topics.
Does
anybody
have
a
topic
they
want
to
bring
today?
That's
not
in
the
agenda.
A
Hearing
nothing
stand
up,
so
customized
hasn't
really
done
anything
in
particular
with
the
karen
function
sub
project.
Lately
we've
been
really
busy
with
preparing
for
the
cube
cuddle
release,
because
we
were
part
of
q
pedal.
We
had
to
go
through
a
whole
update
process
and
we're
doing
some
virtual
maintenance
right
now
for
the
functions
registry
side.
Is
there
someone
who
can
give
us
an
update
bunch
of
your
natasha.
B
So
I've
been
working
on
that,
I
think
the
past
couple
weeks.
It's
been
paused,
but
I'm
hoping
to
get
back
to
it
this
or
next
week
a
lot
of
the
infrastructure
is
set
up.
I
think
the
remaining
work
before
we
can
start
like
asking
people
to
use.
It
is
to
finish
setting
up
the
release
pipeline
and
then
make
the
contribution.
B
Docs
really
clear.
So
hopefully
we'll
finish
that,
like
in
the
next
month
or
so.
C
So
natasha
one
question
regarding
the
regarding
that,
so
last
I
remember
last
time
you
said
someone
are
willing
to
help
with
the
website
work.
So
it's
have
you
confirmed
with
that
person.
B
Oh,
I
was
saying
that
customize
has
some
people
that
volunteered
to
work
on
the
website
and
that
I
could
see
if
they
would
be
interested
in
working
on
this
website,
but
I'm
not
sure
they
sort
of
seem
to
have
dropped
off
from
working
on
the
customized
one
katrina.
Do
you
know
they're,
like
still
around.
B
Yeah,
so
I
don't
think
we
have
anyone
to
work
on
the
function
registry
website.
C
So
from
me,
the
update
is
so
I'm,
as
I
mentioned
earlier,
so
I'm
working
on
having
karen
functions
running
as
a
service
in
a
server
running
access
service.
So
in
our
poc
we,
what
we
did
is
we
built
a
wrapper
server
to
wrap
current
current
functions
so
that
when
someone
want
to
evaluate
function,
they
can
send
a
request.
C
C
So,
while
I
have
a
so
currently,
I
have
a
pr
but
it
hasn't
been
merged.
Yet
so
I
think
by
next
meet
our
next
meeting.
I
should
probably
be
able
to
create
a
proposal
to
our
functions
back
way
too.
I
guess.
A
C
It
has
some
like
some
some
other
when
you
use
that
approach.
It
has
some
other
works
to
do
that,
for
example,
you
need
to
look
at
the
the
metadata
of
the
current
functions.
You
are
going
to
evaluate
to
figure
out
what
is
the
the
entry
point
or
the
command
of
that
container,
because
right
now
how
our
wrapper
server
works?
C
Is
we
put
it
in
in
it
containers
in
a
pod
and
in
the
init
containers
we
copy
over
this
wrapper
server
binary
into
the
that
krm
function
to
be
evaluated
so
that
when
we.
C
And
yeah,
so
with
that
the
wrapper
server
binary
need
to
look
at
the
krm
function,
the
the
metadata
from
the
osa
image.
So
this
is
additional
work
that
it
needs
to
do
so.
If
this
two
thing
is
one
it's
one
binary,
then
it
doesn't
have
to
do
this.
This
work
at
all,
because
when
you
look
at
a
cam
function,
image
itself,
when
you
insert
it,
you
cannot
tell
what
is
the
entry
point.
C
Currently,
this
wrapper
server
only
only
only
works
with
one
cam
functions,
but
ideally,
if
this
we
can
have
something
that
it
can
serve
multiple
current
functions.
That
is
even
better,
I
think,
but
for
that
part
it
hasn't
been
flashed
out
yet.
A
Like
customize
supports,
exec
functions
as
well
that
aren't
in
containers,
so
that
would
have
different
characteristics
right
versus
what
you're
talking
about
with
the
metadata
existing
and
being
available,
but
also
needing
to
be
used
to
figure
out
what
the
entry
point
is.
And
so
are
you
considering
exact
functions
in
your
design,
or
are
you
only
dealing
with
container
functions.
C
So,
for
our
like
for
our
poc
at
google's,
we
for
first
party
functions.
We
did
did
something
like
extract
binary
out
and
execute
that,
so
that's
the
kind
of
the
exact
mode
in
customize.
But
that's
the
first
party
functions
that
we
wrote.
C
We
are
also
going
to
support
third-party
functions
that
like
authored
by
users
or
some
other
team,
so
so
for
that
we
are,
we
are.
We
want
to
still
write
in
the
container
instead
of
trying
to
do
the
exact
mode.
A
Okay,
yeah,
I'm
going
to
be
very
interested
to
see
the
pr
when
you
open
up
it's
an
interesting
problem
for
sure,
especially
because
part
of
the
reason
that
I
think
this
standard
is
great
and
successful
is
how
simple
it
is
in
terms
of
just
requiring
some
ammo
in
and
you
do
your
work
and
then
some
camel
out.
So
hopefully
we
can
maintain
that
simplicity
and
still
get
all
the
functionality
that
you're
that
you're
needing
from
the
hosted
version
of
how
we
want
to
run
it
yep.
A
A
All
right
carrying
nothing
I'll,
just
call
this
a
short
meeting
thanks
everyone
for
coming.
C
And
one
more
question:
one
more
things
we
I
want
to
bring
up
so
in
the
our
slack
channel
so
seems
some.
There
are
some
other
folks
that
are
interested
interested
in
the
topic,
but
they
cannot
make
it
at
this
time.
So
should
we
consider
a
different
time.
A
Yeah,
we
can
definitely
consider
a
different
time.
I
was
under
the
impression
that
they
had
an
extremely
different
time
zone
requirement
that
would
make
it
difficult
to
find
any
overlap.
But
if
that's
not
the
case-
and
it's
just
a
meeting
conflict,
then
for
sure
we
can
move
this
one,
we
have
to
work
around
the
other
six
cli
meetings.
Obviously,
but
besides
that,
I'm
pretty
flexible
personally.
A
Yeah,
I
can
take
an
action
to
contact
them
in
slack
and
see
if
there's
another
time
that
would
work
for
them,
and
we
did
record
this
today
so
we'll
be
able
to
share
it
with
them.
This
time.
Sorry
about
not
doing
that
last
time.