►
Description
#Knative #OpenSource
How many resources does your application require? How much time do you spend optimising those? There are several use cases, in which we want to keep our deployment as lightweight as possible, either because our application does not require much or because our use case is resource constraint to begin with.
In those situations, K3s provides a lightweight alternative to other Kubernetes distributions; combined with Knative, we can optimise the start time, simplicity of our operation and reach a lightweight footprint that helps us minimise costs.
In this talk, Anais will showcase setting up Knative on a K3s cluster and utilise Prometheus to monitor our deployment.
Anaïs is a Site Reliability Engineer at Civo, a cloud computing company based on Kubernetes. When she is not advocating DevOps best practices, she runs her own YouTube Channel centered around cloud native technologies. Before transitioning to the cloud native ecosystem, Anaïs helped blockchain projects scale and find adoption. As CNCF ambassador, her passion lies in making tools and platforms more accessible to developers and community members.
Meetup recorded April 28.
A
Can
you
see
it
yes,
awesome,
okay,
so
yeah
the
demo
was
supposed
to
be
that
was
kind
of
my
idea
about
k3s
and
using
k-native
on
top
of
k3s.
I
would
go
into
more
detail
on
that,
but
then
it
ended
up
being
more
about
my
experience.
So
far
with
k
native
and
the
approach
I
took
about
learning
about
it
and
what
I've
set
up
so
far
or
like
how
I'm
using
keynative
so
far.
So
this
is
my
name.
I've
just
changed
job
roles
and
started
at
the
sre
team
at
xivo.
A
Civ
is
a
cloud
computing
company.
That's
based
on
cubanita,
specifically
using
k3s,
I'm
also
a
computer.
I'm
also
doing
my
computer
science
degree
right
now
and
that's
why
I'm
a
bit
like
limited
in
time.
I
didn't
have
time
to
prepare
the
kind
of
demo
that
I
would
have
liked
to
show.
I
guess
yeah
you
can
find
me
on
twitter
at
wilysonics
yeah.
So
what
am
I?
What
do
I
want
to
share
with
you?
I
kind
of
wanted
to
share
my.
A
I
guess
my
learning
experience
just
with
kubernetes
and
then
also
k
native.
I
was
working
for
the
past
years
in
the
blockchain
space,
doing
community
management
and
developer
relations,
and
then
I
got
a
nice
offer
at
code
fresh
several
months
ago
and
changed
industry
and
got
into
this
space,
which
is
really
exciting.
So
before
like
up
to
like
nine
months
ago,
I
didn't
know
what
qubanitas
was
basically,
so
I'm
still
like
learning
about
all
of
this
quite
a
lot
and
having
having
still
this
fresh
perspective
on
different
tools.
A
I
guess
that
is
for
some
projects,
quite
quite
interesting
and
helpful
yeah.
So
about
eight
months
ago,
seven
months
ago
I
found
out
about
this
landscape
and
I
was
like
wow.
This
is
quite
a
lot
to
learn
and
yeah,
it's
quite
overwhelming
when
you
get
started
in
a
in
a
new
industry
and
then
it's
like.
Oh,
these
are
all
the
different
projects
that
exist
that
you
can
use
and
some
of
them
overlap
some
of
them
you
might
want
to
use
instead
of
others,
which
can
be
quite
confusing.
A
So,
ultimately,
when
you
get
started
with
a
new
industry
or
like
a
new
topic,
I
guess
you
start
to
learn
about
different,
like
you
start
to
try
to
find
your
way
through
and
try
to
find
different
blog
posts,
content
tutorials
that
you
can
use
to
learn
about
it
and
you
might
end
up
reading
some
books
about
it.
You
might
end
up
having
really
interesting
conversations.
A
The
problem
is,
with
the
current
situation
around
the
world,
it's
quite
difficult
to
meet
people
in
person
and
have
interesting
conversations
and
get
to
know
people
from
whom
you
can
learn
from
and
understand
how
they
are
using
a
certain
technology
right.
So
it's
it
provides
additional
challenges.
I
would
say
learning
about
a
new
space.
A
So
but
ultimately,
the
problem
with
all
of
this
is
that
when
somebody
new
gets
started
with
a
with
a
topic
with
a
industry
or
technology,
they
don't
necessarily
have
a
point
of
reference
at
work
or,
and
they
don't
necessarily
know
whom
to
reach
out
to
on
on
social
media.
Before
I
got
started,
all
of
my
connections
were
on
the
blockchain
space,
so
there
was
really
nobody
whom
I
could
refer
to
and
I'll
get
to
that
a
bit
more
in
a
second
on
how
the
k-native
community
helped
me
but
yeah.
A
So,
ultimately,
whenever
you
see
usually
a
presentation
online
or
you
or
you
find
documentation
or
blog
posts,
tutorials
anything
really.
It's
just
a
knowledge
snapshot
of
somebody
like
somebody's
just
sharing
a
part
of
their
knowledge
about
a
specific
tool
or
topic
in
one
point
in
time
and
you
and
don't
really
get
to
know
what
went
into
that
like
what
went
into
those
different
knowledge
buckets
that
made
that
person
understand
the
technology
in
a
certain
way
or
be
able
to
explain
it
in
a
certain
way.
So
that's
why
I
decided.
A
Okay,
I'm
just
going
to
make
everything
that
I'm
learning
public
on
a
on
a
youtube
channel
as
well
as
on
public
notes.
So
over
here
is
actually
my
first
video
on
k
native
I'm
saying
first
video,
because
I'm
trying
to
to
get
better
at
using
it.
So
I
probably
will
have
to
update
my
notes
as
well
soon
on
it
with
me
learning
more
but
yeah.
A
So
I
thought:
hey,
let's
just
make
it
all
public
to
like,
first
of
all
for
projects
to
know
what
actually
like
what
is
the
first
experience
using
the
documentation
and
getting
started.
So
this
video
is
definitely
not
perfect,
but
if
you're
curious
on
how
I
first
use
gay
native,
then
please
do
check
it
out
because
it
might
be
interesting
for
you
to
to
improve
the
resources
or
help
me
improve
my
use
of
k-native
as
well.
A
So
it's
also
kind
of
a
selfish
reason
that
if
you're
just
getting
started,
and
then
you
decide
to
work
in
public,
ultimately,
you
have
more
people
reaching
out
and
and
helping
and
contribute
and
so
on.
So
there
are
really
lots
of
benefits.
Besides
that,
other
people
might
find
this
useful
in
knowing
okay.
What
what
do
like?
What
is
the
order
or
like
how
do
people
learn
about
something
new
yeah?
So
I
wanted
to
use
it
like
initially
for
this
demo.
A
I
wanted
to
do
k
native
on
k3s,
but,
as
mentioned
like
the
time
was
not
there
for
me
to
do
something
really
interesting.
Also,
ultimately,
when
you're
just
getting
started
with
something
with
a
new
technology,
you
don't
know
what's
possible
and
you
don't
know,
what's
not
possible.
So
maybe
what
I
was
trying
to
like
to-
or
what
I
thought
might
be
interesting
in
my
mind,
is
actually
not
something
that
k
native
users
usually
would
do
right.
A
A
That's
how
I
got
that's
how
I
learned
first
about
k
native
and
then
now
it's
just
me
like
trying
new
things.
Ultimately,
so
I
thought
it
might
be
like
cool
to
use
k
native
on
k3,
since
k3s
is
a
lot
of
times
used
on
raspberry
pi
classes.
Now
my
verse
baby,
pi
cluster
is
not
working
right
now,
but
me
getting
started
c.
A
Vocevo
is
based
on
k-3s,
so
you
can
spin
up
k-3s
clusters,
but
ultimately,
in
the
end,
there
was
no
difference
between
using
the
kfc
world
clusters
versus
using
any
other
kubernetes
cluster.
So
it
just
demo.
It
just
really
doesn't
matter
whether
I
would
have
done
it
on
k3s
or
another
kubernetes
distribution.
A
K3S
was
developed
by
ranger
on
it's
based
on
an
other
project.
They
started
and
then
basically
advanced
from
there.
It's
a
fully
certified
kubernetes
distribution
and
the
main
advantage
is
that
it's
really
small
in
size
and
that's
why
it's
really
used
on
like
resource
constraint,
environments
generally
and
you
can
install
it
also
really
easily
if
you
want
to
spin
up
locally.
I
just
haven't
done
that.
Well,
not
for
this
demo,
so
yeah.
Why
did
I
start
using
k
native
well?
A
It
makes
you
feel
a
bit
like
a
wizard
when
you
just
get
started
first,
so
it's
really
like
for
a
user
for
for
a
person
who's
just
getting
for
some
yeah
for
somebody
who's
just
getting
started
with
kubernetes.
It's
really
interesting
to
see.
Okay.
What
can
you
actually
do
with
it
and
with
the
documentation?
A
There's
this
first
instant
success
experience
that
gets
you
going
and
want
to
explore
more
about
it.
So,
for
instance,
when
I
show
that
to
to
people
who
have
never
used
kubernetes
right
for
them,
it's
really
exciting
it's
more
exciting
than
if
I
show
them
files
and
files
of
yaml
file,
because
that
just
confuses
them
a
lot
of
times
and
they
don't
know
how
does
different
components
interact
and
they
don't
know
which
ones
they
would
use
and
so
on,
and
then
it
takes
time
to
explain
it.
A
And
so
generally
it's
just
it's
nice
if
I
can
just
show
some
magic
in
a
few
lines
of
yammer
and
with
a
few
yeah
resources
as
possible.
So
that's
really
cool
overall,
and
so,
as
mentioned,
I
got
started
because
I
wanted
to
have
a
nice
demo
for
our
talk
and
that's
how
I
got
first
to
try
it
out
and
then
also
like
throughout
the
past
months.
I
have
been
sometimes
engaging
on
the
slack
channel
and
I
just
want
to
say
that
the
community
is
really
really
amazing.
A
There
are
several
different
projects
that
I've
tried
out
throughout
the
past
months
and
which
is
really
nice
to
to
feel
like.
You
can
ask
those
newbie
questions
in
the
slack
channel,
which
is
not
a
given.
So
I
highly
encourage
everybody
to
to
keep
fostering
that,
because
I
think
that
you
have
a
really
nice
community
already,
where
that's
yeah.
A
That's
definitely
not
not
a
common
thing
like,
especially
if
you're
getting
started
in
the
space
and
then
you're
just
joining
different
channels,
and
you
don't
know
whom
to
reach
out
to
to
ask
questions
and
so
on
or
which
channel
to
post
them.
So
the
k
native
community
has
been
really
really
welcoming
and
yeah.
I
was
about
a
few
weeks
ago
in
a
live
stream
from
red
hat
developers.
A
Just
talking
about
my
kubernetes
experience
and
then
there
was
a
demo
of
knativ,
and
I
mentioned
it
just
kind
of
blocked
out
of
me
that
it
was
super
easy
to
get
started
with
canadians
now
for
many
people.
It's
not
that
easy,
and
I
completely
understand
that,
but
like
once,
you
get
the
hang
of
it
and
you
know
what
to
what
resources
to
use
and
what
to
look
out
for
like
it.
It's
actually
quite
straightforward.
A
Now,
if
you're
first
looking
at
it,
it's
obviously
like
for
many
people
overwhelming
now
I
got
a
sneak
peek
in
a
new
documentation,
which
is
a
lot
less
overwhelming,
which
I
have
to
say,
which
I
already
gave
feedback
and
my
thoughts
on
but
yeah.
Overall,
it's
it's
comparable,
quite
like
really
easy
to
get
started
with
the
documentation
and
then
there's
also,
as
mentioned
like
in
demos.
A
When
I
show
canada
this
it,
it
feels
like
there's
less
to
learn
for
people,
and
there
is
overall
less
to
learn
like
I
yeah
there's
a
there's,
a
hand
raised,
feel
free
to
comment
feel
free
to
jump
in
if
you
have
any
thoughts
suggest
or
like
yeah.
Oh,
I
was
just
wondering
if
you'd
use
the
command
line
at
all
or
if
you
were
using
entirely
m,
I
was
using
the
command
line,
sometimes
no,
no,
not
consistently
yeah,
but
yeah,
and
otherwise
I
was
using.
A
I
was
using
mainly
yaml
yeah,
so
I
mean
overall,
it's
it's
really
straightforward.
There
was
like
some.
I
remember
there
was
it
for
my
first
demo.
I
set
it
up
like
then
the
day
before
and
it
worked
and
then
for
my
second
demo
I
was
trying
the
same
process
and
it
didn't
work,
and
I
had
people
like
help
me
out
and
so
on.
A
So
but
overall,
it's
it's
fairly
straightforward
and
then,
like
my
personal
experience
so
far,
so
I
don't
like
using
different
tools
and
projects
for
which
I
don't
have
really
a
reason.
So
I
had
a
really
bad
experience
with
just
with
kubernetes
services.
Like
half
a
year
ago,
when
I
first
learned
about
it,
I
was
so
confused,
so
I
tried
to
avoid
any
service
mesh
as
much
as
possible
and
then
using
k-nate.
A
It's
really
great
for
demos
and
just
to
show
people
why
you
like
humanities
as
well,
if
they,
if
they
wonder
what,
where
you,
where
you
choose
to
to
use
it,
one
of
the
reasons
I
guess
and
then
something
that
I
realized
is
actually
I
relied
really
heavily
on
the
documentation.
Usually
I
would
use
tutorials
and
different
examples
like
specific
examples,
but
I
actually
could
find
not
that
many
written
tutorials,
maybe
it's
something
in
like
the
places
that
I
looked
at.
A
So
if
you,
if
you
have
any
use
case
or
any
way
that
you're
using
k
native,
I
just
want
to
say
that
it
would
be
really
really
helpful
if
it's
just
like
a
readme
or
just
anywhere
on
your
link.
That
may
be
on
a
k.
Native
specific
resource
that
would
be
one
of
my
main
feedback
points
that
it
would
be
really
amazing
if
more
more
people,
I
guess,
document
their
use
case
because,
like
mentioned
as
a
beginner,
you
do
not
know
what
is
possible.
A
What
is
not
possible,
so
you
can
try
different
things
and
then
try
to
see
when
you
hit
a
block,
but
ultimately
yeah.
That's
just
different
ways
of
how
people
learn.
I
guess
so.
That's
just
one
of
the
few
comments
I
have
and
yeah
the
documentation
is
great.
I
think,
and
really
comprehensive
and
straightforward
as
well
so
yeah
demo
time
what
have
I
actually
done
with
with
canada.
So
in
this
case
I
tried
to
see
like
just
as
a
I
guess.
A
A
I
guess
so
yeah
then
I'm
using
kinetic
serving
I
haven't,
tried
the
eventing
component
yet
so
mainly
because
I
also
didn't
really
have,
I
guess
a
use
case
for
it
of
like
me
specifically
trying
it
out,
but
I
guess
it
will
change
it's
like
with
some
of
those
tools
that
I'm
using
it's
in
like
after
some
months.
It's
just
it
clicks
and
I'm
like.
Oh
that's
why
you
would
use
it
and
then
I
start
using
like
a
specific
tool
all
the
time.
A
So
when
you
have
a
new
revision
going
out
to
specify
basically
the
traffic
spot
that
you
want
to
have,
that
was
super
easy
to
do
and
straightforward,
and
also
the
examples
and
the
documentation
were
really
great
for
that,
and
then
I
started
just
playing
around
with
grafana
prometheus
and
kyali
to
just
visualize
that
well
the
traffic
and
get
more
involved
with
the
monitoring
side
of
things
and
yeah.
Just
remember:
I'm
still
learning
about
all
of
this.
This
is
really
like.
Super
beginner's
perspective
right
yeah.
A
So
let's
go
back
to
the
demo,
because
I
still
want
to
show
you
a
few
things.
So
here's
basically
the
traffic
splitting
that
I
currently
have.
I
don't
know
if
that's
like,
actually
how
that's
perfectly
done
like
this
is
really
just
me
trying
it
out.
So
don't
judge
too
much
it's
all
on
my
github.
So
if
you
have
any
comments
on
how
I
can
improve
those
things,
then
please
do.
A
A
That's
currently
running,
I
mean
it's
not
it
doesn't
have
any
traffic
going
through
it
yet
so
I
just
what
I
would
do
next
is
just
deploy
this
the
traffic
splitting
and
then
send
some
traffic
to
it
and
observe
it
on
kiali.
Now
this
is
really
straightforward.
I
think
I
mean
I'm
not
sure
if
I
should
show
it.
This
would
just
be
my
little
demo.
Okay
go
for
it,
okay,
cool,
so
yeah,
so
let
me
just
send
some
well.
This
is
that,
okay,
let's
just
deploy
the
traffic
splitting
yemo.
A
A
A
A
Now.
This
is
now
the
graph
that
shows
the
traffic,
which
is
obviously
really
nice
to
see
so
there's
supposed
to
be
a
50
50
about
50,
50,
split
of
traffic
between
the
first
revision
and
the
second
revision
and
yeah.
That's
just
something
really
nice
to
see
that
you
can
easily
do
that
with
so
little
like
so
few
resources.
Ultimately,
then
what
you
would
usually
need
for
humanity's
deployment
yeah.
This
is
really
like
all
I
wanted
to
show.