►
From YouTube: Knative Community Meetup Feb/ Fast iteration on Knative applications using Tilt by Evan Anderson
Description
Demo:
Knative makes deploying cloud-native serverless applications easy, but what about building those applications? Tools like Tilt and Skaffold enable tight “inner loop” development on Kubernetes, but how do they interact with the Knative autoscaler or event-driven applications? Come see Evan build an application using Tilt and Knative.
A
A
What
people
are
are
here
are
calling
the
inner
loop
development
experience
with
tilt,
which
is
pretty
neat,
and
I
hadn't
seen
written
up
combining
it
with
k-native
before
and
we'll
talk
a
little
bit
at
the
end
about
both
how
it
works
and
how
it's
gotten
better
recently,
and
it
was
used
to
be
a
bit
tricky
and
yeah.
Thank
you
all
for
joining.
A
So
it's
just
slower
to
run
this
stuff
on
the
cloud
where
it's
got
access
to
all
the
other
stuff
you
want,
where
you
can
hook
it
up
to
a
k-native
broker,
where
you
can
hook
it
up
to
your
existing.
You
know
redis
or
cassandra
or
whatever
database
environment.
You've
got
you've,
got
all
those
secrets
there
and
stuff
like
that:
it's
easier
to
hook
up
stuff
like
ssl
in
the
cloud
when
you've
got
a
publicly
accessible
endpoint
than
when
you're
running
on
your
local
machine.
A
So
the
idea
is
really
sort
of
as
a
wrap
around
local,
not
local,
but
you
know
your
development
environment
setup
experience
and
for
those
of
you,
who've
had
a
set
up
your
development
environment
script.
You
can
see
why
maybe
having
some
standard
infrastructure
for
doing
it,
that's
designed
for
speed
would
make
sense.
A
A
A
Yes,
great,
okay,
so
we're
gonna
start
with
a
pretty
simple
react
application
and
you
can
see,
I
reloaded
it
and
it's
got
styles
and
stuff,
and
so
this
actually
consists
of
two
components.
So
we've
got
a
react
single
page
app
over
here
and
you
know:
here's
the
standard
react
header
pretty
much,
and
then
here's
a
message
list
that
I've
implemented
down
below.
A
A
You
do
need
to
reload,
but
you
can
see
that
already
it's
red,
I'm
gonna
switch
it
back
to
white
because
you
even
my
non-designer
eyes,
can
tell
that
that's
kind
of
ugly,
and
so
it's
also
pretty
easy
for
me
to
mess
around
and
say
you
know:
oh
hey!
What
if
I
want
to
make
count,
be
a
string
instead
and
then
I
can
go
over
here
and
I
can
reload
and
nothing
has
changed.
But
now
I
could
mess
with
this
and
say.
A
So
this
is
going
to
give
us
a
list
of
tuples,
so
we
get
a
tuple
and
we're
going
to
return
because
we
want
the
same
format,
so
I
don't
have
to
go
back
and
mess
with
both
sides
of
code
at
once.
I
zero
is
going
to
be
the
name
and
count
is
going
to
be
the
value
which
is
going
to
be
a
string,
but
I
adjusted
the
other
side
to
be
happy
with
strings,
and
so
I
save
this
and
I
come
over
here.
B
A
A
So
and
now
I'm
going
to
show
you
so
when
tilt
is
running,
it
actually
also
starts
an
internal
web
server
in
addition
to
that
stream,
so
you
can
actually
scroll
through
and
see
all
of
the
you
know,
all
of
the
internal
logs
and
all
the
builds
and
so
forth
that
have
gone
on.
So
you
can
see
one
file
changed
here.
A
And
one
of
the
magic
things
that
makes
this
so
fast
is
that
tilt
actually
cheats
and
supports
a
concept
called
live
update
where,
if
your
container
is
built
correctly,
it
will
copy
the
files
directly
into
the
container
and
then
either
run
a
command
in
the
container
to
update
it
or
if
your
application
already
supports
noticing
when
the
file's
changed.
It
will
just
do
that
and
you
won't
get
a
new
container
image
since
we're
running
with
nodemon,
which
rebuilt
your
node
application
every
time.
The
files
change
that
happens
automatically.
A
And
so
we
don't,
we
don't
actually
need
to
deploy
a
new
k-native
revision,
for
example,
while
we're
in
this
inner
loop
trying
things
out.
Instead,
we
just
have
a
bunch
of
containers
which
are
dirty
effectively,
and
so
you
wouldn't
necessarily
want
to
use
this
for
your
production
environment.
But
it's
really
fast
for
development,
and
you
also
have
access
to
like
your
kubernetes
secrets
and
things
like
that.
A
A
But
if
I
didn't
do
that
then
yeah
when
it
shut
down
and
started
back
up
again,
then
all
the
live
updates
would
disappear
until
I
saved
and
then
everything
would
get
copied
over
and
it
would
update
okay
thanks
yeah,
so
yeah,
that's
a
good
point
and
I
used
to
have
min
scale
settings
in
there
and
then
I
took
them
out.
I
was
like.
I
don't
need
these
anymore
great,
and
so
I
should
probably
put
those
back
in
and
we
can
watch
that
in
a
little
bit
too.
A
But
the
other
thing-
that's
really
smart.
That
tilt
does
is
that
it's
got
some
definitions
of
what's
in
your
project
and
if
the
code
didn't
change,
then
it's
not
going
to
kick
off
a
new
build.
If
your
kubernetes
yaml
didn't
change,
then
it
doesn't
need
to
update
the
resource
and
so
that
lets
it
do
these
steps
as
fast
as
they
can
be.
A
So
yeah
I
took
an
existing
react
application.
I
built
the
react,
application
first
developed
on
it
all
locally,
and
then
I've
got
two
files
that
I
had
to
add
is
pretty
much
the
sum
total
in
order
to
get
things
working
on,
it
was
actually
one
more
change.
I
also
ended
up
adding
a
single
command
that
started
both
both
the
api
server
and
the
react
server.
A
When
I
got
started,
it
was
really
easy
to
just
run
two
separate
processes,
but
if
I
want
to
run
a
single
container
at
the
end
of
the
day,
then
I
wanted
to
to
put
them
all
into
one
place.
You
could
also
do
this
as
two
different
containers-
one's
a
sidecar
of
the
other,
but
I
decided
I
would
just
bundle
it
all
into
one
container
and
so
yeah.
So
the
two
things
that
you
need.
A
You
absolutely
need
a
tilt
file
and
you
probably
want
a
kubernetes
manifest,
and
so
I
wrote
a
k-native
service
for
this
and
we're
going
to
take
a
look
at
these
files
a
little
bit
so
we're
going
to
start
with
the
tilt
file,
which
is
the
instructions
for
tilt
and
I've
annotated.
All
this
stuff,
so
if
you
follow
the
vanilla
path
for
tilt,
you
end
up
with
a
docker
file
and
then
you
get
to
do
all
sorts
of
fun
in
optimizing.
A
A
You
know
ready
to
go
and
then
just
use
pack
build
to
verify.
It
worked
and
then
load
the
pack
extension
up
here
on
the
first
line
and
then
down
here
define
here's
where
to
you
know:
here's
where
to
push
it
ignore
these
files.
My
you
know,
git
ignores
and
stuff
like
that,
my
eslints
and
then
ignore
the
tilt
file
and
the
service
yaml
for
the
build,
because
we
don't
use
them
anymore
or
we
don't
use
them
in
the
build
weather,
vela.
B
A
Do
have
a
variable
that
I
needed
to
set
so
yeah.
If
you
have
this,
if
you,
if
you,
if
you
have
the
slides,
you
can
skip
ahead
and
see
the
answer
so
there's
this
build
pack
section
at
the
top
and
then
there's
this:
how
to
build
the
build
pack.
The
sort
of
the
ignore
thing
is
kind
of
nice.
The
key
part
is
this:
live
update,
so
fall
back
on
says
when
one
of
these
files
has
changed,
you
have
to
do
a
build.
A
You
can't
just
push
it
up
there
again,
because
the
package
json
has
the
command,
that's
used
to
start
things,
and
so
that's
how
that
happens,
and
then
sync
dot
to
workspace
workspaces,
where
all
your
code
gets
loaded
in
the
build
pack,
and
so
this
is
basically
saying
any.
You
know
anytime
a
file
changes
under
dot.
A
That's
not
one
of
the
ignored
files
copy
it
up
and
depth
says
these
are
the
directories
that
are
involved
in
this
build
and
again
I'm
lazy,
and
so
I'm
like
everything
into
one
container,
go,
and
so
I
actually
have
two
npm
node
modules
directories
and
everything
else,
one
nested
inside
the
other
and
we'll
take
a
look
at
that
later
on
when
we
look
at
the
application
a
little
more.
So
that's
the
that's
the
get
me
a
container
side
of
the
tilt.
A
A
So
when
you
need
to
fill
in
an
image,
those
are
the
places
where
you
would
go
to
look
for
an
image
to
fill
in,
and
this
next
thing
is
a
nice
thing
that
tilt
has
because
tilt's
building
these
kind
of
weird
things
and
is
running
stuff
in
a
not
really
immutable
container
kind
of
way
by
default.
It
will
only
work
against
things
like
mini
cube
or
known
ephemeral
spaces.
A
So
if
you
have
a
cluster,
that
is
a
real
cluster,
you
need
to
add
this.
Allow
kubernetes
contexts
to
say.
Yes,
you
can
work
against
this
cluster.
Otherwise
it
will.
You
know
if
I
take
this
line
out
and
I
try
to
run
tilt
up,
it
will
say:
oh
no,
you
know
I
don't
I
don't
know
what's
going
on
here,
but
you
might
be
running
against
production.
A
A
If
it
had
a
selector
on
the
object,
then
it
could
kind
of
look
at
the
selector
and
say:
oh
it's
probably
these
pods,
but
since
we've
hidden
all
the
selectors
away,
so
that
users
don't
need
to
know
about
them.
We
do
need
to
tell
tilt
about
them,
and
now
here
is
the
tilt
yaml
that
or
the
the
k
native
service
yaml
that
vla
wanted
to
see,
and
you
can
see
that
right
now
I
don't
have
metadata
annotations
for
min
scale.
A
I
don't
need
both,
so
I
just
said:
go
through
the
no
reload
endpoint
which
takes
out
that
outer
shell
restart
everything
loop
and
just
uses
the
inner
more
efficient,
node
loop
and
then
vla
wanted
to
know
about
setting
environment
variables
and
you
have
to
if
you
want
to
run
in
a
production-like
environment,
meaning
when
the
host
header
or
the
host
environment
variable
is
set.
You
need
to
oh
there's
a
special
tilt
extension.
I
never
saw
that
cool
nifty
I'll
have
to
check
that
out.
A
A
A
A
But
since
0.23
live
updates
supports
multiple
pods
prior
to
that
you
needed
to
be
careful
because
tilt
would
fall
back
to
doing
a
full
container,
build
and
push
the
slow
path
effectively
if
it
discovered
that
there
was
more
than
one
pod,
it
needed
to
push
live
updates
too.
So
you
don't
have
to
worry
about
that
anymore,
which
is
great.
A
Like
oh
clean
up
these
images
from
somewhere
else,
they
go
away
when
the
cluster
goes
away
and
again,
I'm
using
build
packs
so
that
I
don't
have
to
figure
out
how
to
build
an
optimized
docker
file
and
instead,
I
can
just
say
you
know,
figure
out
what
I'm
running
in
this
case
node
and
do
it.
If
I
make
a
change
that
does
trigger
a
build
pack
build,
it
takes
a
couple
of
minutes.
So
that
is
a
drawback.
If
I
wrote
it
my
optimized
docker
file,
it
might
be
faster,
other
fun
stuff.
A
The
vs
code,
built-in
browser,
makes
it
really
easy
to
just
stay
in
one
window
and
not
be
flipping
back
and
forth.
Quite
so
much
I
sort
of
wish.
I
could
open
more
than
one,
and
I
sort
of
I'm
glad
that
I
can't
and
then
as
a
fun
little
thing.
If
you
mess
up
one
of
your
updates
or
something
like
that,
the
tilt
extension
will
quack
when
you
get
an
error,
so
I'm
probably
going
to
show
that
off
now.
A
A
I
did
not
try
to
run
it
locally
on
mini
cube.
I
like
running
on
real
clusters
that
aren't
my
laptop
because
once
my
laptop
is
doing
zoom
in
two
or
three
other
things,
it
doesn't
like
running,
mini
cube2
and
running
mini
cube
on
some
other
machine
seems
like
it
invites
all
the
pain
of
both
worlds.
It's
hard
to
reach
that
mini
cube
machine
from
my
web
browser
and
it's
still
a
small
confined
space
rather
than
being
able
to
scale
up
to
lots
of
stuff
if
needed.
C
A
A
A
A
It
will
print
over
here
on
line.
13
got
an
identifier,
want
a
comma
and
then,
besides
the
fact
that
vs
code
has
a
nice
formatter
that
shows
you
that
everything
is
wrong.
It
tells
you
on
line
13,
it
was
expecting
a
comma
and
it
got
something
else,
and
so
that's
basically
you
can
debug
it
through
this
web
ui
and
then
central's
asking.
A
A
A
But
kind
of
a
fun
extra
bonus
thing
if
you
decide
that
you
want
to
on
cluster
registry.
For
some
reason
I
have
mostly
tested
it
with
container
d
ubuntu
stuff,
I
haven't
tested
it
very
thoroughly
on
all
the
cloud
providers
yet,
but
it's
on
my
list
to
do
some
time,
let's
see
and
then
yeah.
So
if
we
go
back
to
that,
what
was
it.
B
A
A
A
A
A
A
A
A
A
A
A
This
will
run,
go
get
if
you
need
it
and
then
co-publish
and
they
give
you
this
variable
called
expected
ref,
which
is
the
name
that
they
want
you
to
publish
to,
and
then
they
will
replace
that
ref
in
your
in
your
kubernetes
artifacts,
where
they
find
it
with.
You
know
the
name
that
they've
made
up
each
time.
A
A
One
thing
I
haven't
investigated
deeply:
they
will
explain
to
you
why
they
run
a
build
and
I'm
not
sure
I've
got
quite
all
of
the
settings
correct,
because
occasionally
I
change
something
that
I
don't
think
should
generate
a
build
like
the
service
yaml
and
sometimes
it
kicks
off
a
build,
and
I
haven't
debugged.
Why?
Because
it
doesn't
happen
very
often,
usually
I'm
not
changing
the
service
ammo.
All
the
time.
A
C
C
A
C
D
D
It's
in
the
bottom
part
of
your
screen
if
it
doesn't
appear
there
and
thank
you
thank
you,
alex
josh
roland
villa.
Thank
you.
Everyone
for
joining
us
today.
Please
follow
up
on
the
conversation
on
slack
and
twitter
and
then
miss
the
next
k
native
meetup.
So
thank
you
again
for
for
everything.
Thank
you
evan!
That's!
That
was
really
interactive
and
great.
So
we
hope
to
see
you
at
the
next
canadian
meetup
and
yeah
follow
up
the
on
the
conversation.
Please.