►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Function to Container - Building a FaaS Experience - Evan Anderson, VMware
Function as a Service (FaaS) is a hot topic in serverless and cloud computing at the moment, and there are a variety of open-source and CNCF projects which provide some level of serverless capability. Many of these open-source serverless solutions actually operate at the level of the container abstraction, which makes them a powerful bridge for traditional application models, but sacrifices the simplicity of the "functions" approach. Function buildpacks aim to provide this developer simplicity by injecting both a main method and invocation glue such as an HTTP server into the application code before building a container image. Unlike traditional buildpacks which aim to package a complete application with specific protocol bindings specified by the developer, function buildpacks rely on inversion of control to adapt business logic (in the form of a CloudEvents-processing function) to the protocol needs of the application.
A
Thank
you.
Thank
you
and
yeah.
I'm
happy
to
discuss
any
of
this
stuff
catch
me
outside
my
twitter's.
At
the
end,
there's
a
couple
calls
to
action
at
the
end
too.
So
you
know
the
end
of
the
talk.
Hopefully
I'll
have
motivated
you
to
do
some
of
that
stuff,
but
we're
going
to
start
with
a
little
trip
down
memory
lane.
A
So
this
is
a
lot
about
application
developers,
folks
whose
job
it
is
wow,
that's
a
little
out.
Can
we
get
down
just
a
tiny
bit?
Okay,
folks,
who
are
mostly
not
worried
about
the
stuff
we're
doing
here
today,
they're
mostly
worried
about
solving
business
problems
and
producing
business
value,
so
looks
like
it's
a
little
loud
still,
I've
been
told
I'm
out
loud.
Thank
you.
A
So
when
everything
started,
you
know
you
started
with
maine
and
we
experiment
with
functional
languages
and
object-oriented
languages
along
the
way
we
figured
out
different
ways
to
organize
our
code,
and
so
we've
been
doing
this
for
40
years
50
years.
So
if
you
were
in
the
late
1970s
and
you
were
going
to
build
well,
you
didn't
build
a
web
service,
then,
but
a
network
service.
A
You
got
all
of
this
setup
code
to
write
before
you
actually
got
around
to
doing
anything
interesting
and
then
it
was
kind
of
painful
to
do
interesting
things
because
you
had
to
worry
about
like
buffer
overflows
and
yeah.
Maybe
c
isn't
the
greatest
language
nowadays,
but
in
the
80s
we
figured
out
hey.
A
Here's
where
I
made
my
introduction
to
programming
cgi
bin
did
the
same
thing
for
http,
so
you
put
your
perl
script
on
a
path
and
you
got
all
of
your
arguments
like
all
of
your
http
headers
passed
in
as
environment
variables.
You
got
the
body
passed
in
as
the
request
body
and
you
spat
back
some
htm,
some
hdp
headers
and
then
a
body,
and
I
think
that
even
works
I
haven't
tried
it,
but
but
that
made
things
a
lot
easier
for
writing
programs,
and
so
lots
of
people
got
started.
A
So
then
spring
boot
came
along
and
leveraged
java
annotations,
and
so
now
you
can
actually
stick
that
hey
this
code
is
for
slash
right
next
to
your.
You
know
right
next
to
the
function
that
actually
provides
that
output,
and
this
is
pretty
nice
from
a
productivity
point
of
view.
You
can
see,
there's
no
main
anywhere
listed
in
here
somewhere,
there's,
there's
a
class,
that's
annotated
with
spring
with
spring
boot
controller.
I
think,
and
then
it
just
starts
that
up
and
wires
everything
together
for
you
and
then
I
put
faz
in
the
title
here.
A
How
does
that
all
have
to
do
with
faz?
Well,
this
is
an
actual
sample
from
the
aws
documentation
for
lambda,
and
you
can
see
that
it's
basically
extracted
out
all
of
this
handling
and
you
get
a
package
set
of
data
and
you
can
just
pull
out
the
pieces.
You
need
hello,
first
name
and
last
name
from
the
event.
It's
already
unpacked
the
json
for
you
and
because
this
is
node.js
and
they're
not
using
async
and
await
in
this
particular
model.
A
They
hand
you
a
callback
that
you
call
at
the
end,
because
that's
just
what
you
do
in
javascript
everywhere
else.
You
would
just
return
data,
but
this
allows
you
in
javascript
to
chain
your
callbacks
and
so
forth,
and
then
the
real
reason
for
doing
this
is
that
before
we
were
mostly
talking
about
programming
models
changing.
A
So
if
we
want
to
do
the
same
thing
in
kubernetes,
well,
okay,
we
have
to
wrap
it
with
express,
that's
not
too
bad,
but
it's
not
quite
as
pretty
as
this
other
thing
was
it.
You
know
this
is
just
export
to
function
and
now,
like
we
got
to
worry
about
our
ports
again
we're
serving
on
localhost,
oh
and
then
we've
got
this
extra
little
file
here,
it's
in
a
special
language.
It's
not
your
main
programming
language.
A
A
We've
gone
wrong
somewhere
along
the
way
here,
and
docker
files
were
a
great
way
to
bootstrap
an
ecosystem.
You
can
do
a
lot
of
cool
stuff
with
docker
files,
but
we
shouldn't
be
exposing
them
to
end
users
on
a
regular
basis,
because
I
kind
of
think
of
it,
like
a
swiss
army
knife,
it's
great
when
you're
in
a
jam
and
you
just
need
a
screwdriver
or
you
just
need
a
knife
or
something
like
that.
A
So
the
first
step
is
when
we're
building
one
of
these.
We
need
to
know
what
that
good
interface
looks
like
and
so
for
function
as
a
service.
You
can
sometimes
just
like
look
at
what
someone
else
has
done:
that's
not
actually
a
bad
place
to
go
if
there's
already
a
place
where
people
say.
Oh,
this
is
great.
A
A
So
once
we
figured
out
what
that
shape
is
what
that
good
function.
Signature
looks
like:
we
need
to
figure
out
how
to
take
that
user's
code
and
turn
it
into
something.
That's
a
container
that
matches
the
outside's
shape,
because
we
still
have
that
outside
shape.
It's
still
kubernetes,
or
in
my
case
I'm
often
thinking
about
k-native,
but
k-native
is
really
just
http
serving
processes
on
kubernetes.
A
So
it
kind
of
looks
like
kubernetes
again
anyway,
and
so
in
this
case,
we've
got
that
nice
little
function
that
we
just
pulled
off
of
the
aws
web
page.
Someone
can
copy
and
paste
use
all
the
knowledge
they've
already
got,
and
then
we're
going
to
slap
express
js
around
it
and
we're
going
to
slap
the
cloud
events
sdk
around
it
and
we'll
get
something.
That's
pretty
close.
A
And
to
package
up
all
this
stuff,
that's
in
that
docker
file
in
a
generic
way.
We
can
use
a
tool
like
cloud
events
if
you're,
if
you're
doing
java
or
if
you're
doing
go,
there's
some
nice
tools,
jib
and
co.
That
will
do
this
based
on
other
stuff,
like
co
uses,
your
your
actual
kubernetes
yaml
manifests
and
jib
uses
like
your
palm.xml,
but
in
the
generic
case,
buildpacks
lets
you
encode.
A
This
is
how
to
build
me
a
container,
and
so
you
can
just
say
pack
build,
give
it
an
image
name
that
you
want
and
then
builder,
such
and
so,
and
that
gives
you
an
infrastructure
where
you
can
actually
build
things
up
with
build
packs,
and
you
can
actually
compose
multiple
layers.
The
same
way
you
can
in
docker,
but
so
you
can
say,
hey,
I
need
python
and
I'm
building
a
flask
app
with
a
requirements.txt.
A
You
get
a
lot
of
features
out
of
the
box.
They've
thought
about
things
like
caching,
that's
one
of
the
things
when
you're
doing
when
you're
building
a
docker
file,
you
may
think
about.
Oh
hey!
I
want
to
copy
in
my
package.json
first
and
then
run
the
right,
npm
command
to
fetch
in
all
my
dependencies
and
then
I'll
copy
in
the
rest
of
the
code.
So
if
I
change
any
code,
that's
not
my
package
json
or
my
package
lock,
then
I'm
going
to
get
you
know
I'm
going
to
only
have
to
do
the
build
steps.
A
A
You
have
an
image
that
just
does
that.
There's
a
cool
feature
in
build
packs
where
they've
got
a
detect
phase
and
then
a
run
and
then
a
build
phase,
and
so
you
can
actually
build
an
image
that
can
build
both
java
and
python,
and
you
end
up
with
two
different
build
packs,
one
of
which
raises
its
hand
and
says
I
can
build
this.
It
looks
like
python
one
that
says
I
can
build
this.
It
looks
like
java
and
if
you
have
both
java
and
python
in
there,
it
may
get
a
little
confused.
A
A
So
this
is
roughly
what
my
build
pack
looks
like,
but
you
can
see
I've
just
added
one
more
build
pack
to
the
end
of
the
list
of
build
packs
to
run,
which
is
to
add
in
the
function
part,
so
we're
getting
c
python
and
we're
getting
pip
and
pip
install
and
we're
setting
environment
variables
and
stuff
like
that.
If
it's
needed-
and
so
that's
that's
another
nice
feature
of
build
packs
here,
there's
other
ways
to
do
it.
This
is
not
build
packs.
A
So
some
of
the
other
things
you
should
think
about
as
you're
building
a
happy
developer
environment
are
templates
for
getting
started.
So
the
react,
the
react
project
has
a
great,
create
react
app
that
gets.
You
started
with
an
actual
thing.
You
can
just
start
running
and
then
you
can
start
poking
at
it
and
changing
it
and
so
forth
and
there's
a
lot
of
stuff
in
there,
but,
like
you,
don't
have
to
do
it
all
at
once.
A
You
can
also
set
up
a
bunch
of
conventions
where
you
say:
oh
hey,
we
know
that
you
know
that
we're
building
a
python
container,
usually
it
needs
about
this
much
cpu,
and
this
much
ram
will
spit
out
a
you
know
manifest
for
you
or
some
you
know
store
something
that
gives
you
some
default
recommendations
on
how
much
resources
you
have.
So
you
don't
end
up
with
you
know.
Oh
look.
I've
got
500
pods
sitting
on.
A
A
You
can
also
auto
wire
up
health
and
liveness
probes
so
that
you
know
hey,
we
know
we're
building
a
web
app.
Maybe
we
should
check
that
the
web
app
port
is
open
or
that
get
slash
works
or
something
like
that.
You
can
also
wire
in
guard
rails,
so
you
can
do
work
in
these
tools
to
generate
an
s-bom
or
to
apply
other
supply
chain
policies
scanning
and
so
forth,
in
a
way
that
users
just
run
the
tool
and
they
don't
need
to
think
about.
Did
I
wire
this
up?
A
A
A
A
A
So
that's
actually
what
I'm
going
to
demo
here
and
then
run
lets
you
run
the
container
locally
because
as
great
as
it
is
with
tools
like
telepresence
and
so
forth,
sometimes
it's
easier
if
you've
got
the
thing
locally
to
poke
at
and
you
can
do
a
mountain
or
you
can
attach
a
debugger
or
something
like
that.
So.
A
A
And
we'll
say,
create
and
we'll
say
that
we're
going
to
use
the
aws
python
language,
which
is
a
special
version.
I
made
that
knows
how
to
package
up
the
samples
from
the
aws
python
like
if
you
take
a
if
you
take
a
function
from
the
aws
docs
and
you
copy
it
in
this
python.
This
should
be
able
to
run
it
and
wrap
it
and
run
it
on
k
native
and
we're
gonna.
A
A
So
if
this
is
python,
maybe
I
say:
oh,
I
probably
need
a
half
a
cpu
and
I
probably
need
like
150
megs
of
ram
and
then
my
actual
function
is
pretty
small
by
default,
we're
going
to
look
for
something
called
lambda
function
and
inside
a
function
called
lambda
handler.
So
here
we
go,
we've
got
a
little
function
and
we
are
going
to
just.
A
This
is
really
good
when
you've
got
a
stage
that
you
don't
necessarily
want
to
spit
out.
A
lot
of
logs
for
is
just
let
the
user
know
that
something's
happening.
You
can
do
dots
going
back
and
forth.
You
can
do
spinny
round,
but
that
ascii
or
that
unicode
art
really
helps.
People
know
that
it's
not
just
stuck
so
right.
Now
it's
building
the
image.
A
A
A
A
A
A
A
We
print
out
in
the
status
all
kinds
of
nice
information
like
the
url.
This
address
url
is
how
you
can
reach
it
on
the
local
cluster
if
you
want
to
avoid
going
off
cluster.
So
there's
actually
two
different
addresses
here,
but
we
repeat
a
lot
of
the
information
from
above
with
what
we've
actually
observed,
and
we
do
a
lot
of
work
to
make
sure
that
when
we
say
ready,
you
can
actually
hit
that
url,
which
makes
your
test
a
lot
easier,
because
you
can
just
wait
for
something
to
hit
ready
and
then
know
it
works.
A
A
My
guess
is
about
50
to
60
of
the
time.
So
you
know
I
can.
I
can
just
keep
flipping
that
coin
and
hope
I
keep
getting
heads,
but
it's
better
to
make
some
of
this
stuff
pluggable
so
particularly
templates,
and
that
getting
started
type
of
experience.
We
want
to
make
it
so
that
you
can
bash
together
your
own,
your
own
template
for
what
a
function
looks
like
and
distribute
that
to
your
developers.
A
And
so
I've
talked
about
all
this
in
the
sense
of
k-nativ,
but
this
doesn't
apply
only
to
k-native.
This
applies
to
anywhere,
where
you're,
trying
to
up-level
the
developer,
experience
beyond
docker
files
and
kubernetes,
and
if
I've
managed
to
convince
you
that
that's
a
good
idea,
the
first
thing
to
do
is
to
think
about
what
is
that
higher
level
abstraction
that
you
want
your
developers
to
think
about.
A
A
If
it
gives
you
the
feeling
that
oh
man,
I
always
wish,
I
picked
the
other
one
when
I
picked
something,
maybe
you
got
it
wrong,
but
figure
out
that
runtime
contract
so
for
k-native,
it's
you've
got
a
web
server.
It
listens
on
the
port
environment
variable,
but
you
know
maybe
you're
using
cada
and
you're
streaming
stuff
that
pulls
off
of
kinesis
and
the
answer
is:
hey.
You
pull
off
of
kinesis
on
a
well-known.
A
You
know,
environment
variable
or
something
like
that.
You
know
or
a
secret
there's
a
secret
file,
that's
a
file
at
a
certain
spot.
When
you
start
up,
you
start
reading
from
your
kinesis
stream
at
that
spot,
whatever
that
is
standardize
that
and
then
you
can
start
building
containers
that
do
that
and
the
great
thing
about
standardizing
it.
You
can
start
with
docker
files.
A
Docker
files
are
not
a
bad
tool
but
they're,
not
the
tool.
You
should
be
using
all
the
time.
I
was
trying
to
make
analogies
on
twitter
the
other
day,
and
I
said
like
yeah,
it's
the
swiss
army
knife
and
sometimes
you
want
a
scalpel
and
you
want
to
do
really
fine
stuff,
and
you
don't
really
want
your
swiss
army
knife
for
surgery
and
sometimes
you
are
putting
together
an
ikea
set,
and
you
don't
really
want
your
swiss
army
knife
because
you
know
the
screwdriver
doesn't
lock
and
it'll
keep
twisting
and
you'll
be
saddened.
A
I'm
I'm
encouraging
build
packs
here
because
I
think,
having
more
build,
packs
and
being
able
to
build
off
of
like
there's
a
lot
of
patching
involved
in
keeping
build
packs
up
to
date.
Like
oh
there's,
a
vulnerability
in
python,
we
need
to
package
a
new
python
yeah.
You
can
put
yourself
in
the
business
of
packaging
new
python
every
day
or
probably
every
three
weeks
but
or
if
we
as
a
community
can
all
come
together
and
say:
hey
here's
a
place
where
we're
going
to
maintain
some
baseline
pieces.
A
I
think
that
we
can
save
a
lot
of
effort.
Nsbom
and
tools
like
that
will
also
help
us
detect
those
vulnerabilities
but,
having
you
know,
100
organizations,
each
rushing
out
to
patch
python
feels
like
a
waste
to
me
and
then
try
it
out.
Try
it
out
yourself
putting
together
this
demo
was
awesome.
I
found
like
two
bugs
that
I'm
sending
prs
for
and
do
user
studies
get
your
users
to
try
this
stuff
out
sit
down
with
them.
Say:
hey.
Does
this
actually
make
your
life
better?
A
If
I
told
you
you
had
to
use
this,
would
you
be
angry?
Meh
ecstatic,
like
you,
know,
hey
I
used
to
do
it
this
other
way.
This
way
seems
about
the
same.
It
takes
about
the
same
amount
of
time.
It's
all
good,
hey.
This
seems
like
it's
twice
as
fast
and
I
don't
have
to
copy
strings
from
here
to
there
I
love
it
or
you
know,
hey.
I
had
these
five
tools
that
I
built
around
the
old
workflow.
A
Those
tools
are
part
of
your
developer.
Experience
too.
If
you
break
those
tools,
you're
breaking
that
developer
experience,
so
try
out
new
things
with
your
actual
target
customers
ask
them.
Questions
they'll,
probably
be
really
excited
to
know
that
you
care
also
try
things
with
different
languages.
A
Maybe
you'd
use
java
all
the
time,
try,
python
or
node
or
ruby,
where
you
don't
have
a
type
system
in
the
same
way
you
do
with
java,
and
you
don't
have
a
lot
of
the
other
tools
and
you've
got
other
conventions
instead,
they're
not
bad
languages,
but
they
don't
all
work
the
same
and
if
you're
a
python
person
you
know
try
java
or
try
rust
or
something
like
that.
Try
go
and
see
how
that
changes.
The
way
you
think
about
things,
so
thank
you.
A
A
We
are
just
getting
ready
to
do
another
round
of
user
studies
on
it
to
see
how
people
use
it,
what
they
really
wish
it
could
be,
and
if
you're
interested
join
us
on
slack.knative.dev,
that
will
give
you
an
auto
invite
if
you
turn
those
two
things
around
and
you
put
the
slack
part.
Second,
then
you
get
to
an
sso
login
and
everything's
terrible
and
yeah
join
us
in
the
function.
Sandbox
and
let
us
know
what
you
think.