►
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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.
Overview and State of Knative - Mauricio Salatino, VMware & Carlos Santana, IBM
As the most widely-adopted serverless platform on Kubernetes, Knative offers a simplified developer experience deploying and managing stateless and event-driven applications. In this session, we'll give attendees an overview of the Knative philosophy of being Kubernetes-native and working well with existing Kubernetes tools. Then we'll provide a demo of FaaS using Knative and conclude with a roadmap for what's next. Most importantly, we'll provide information on how you can get involved either as a contributor or end-user who wants to give feedback on its future direction. With its recent donation to the CNCF at the incubating level, there's never been a better time to get started with Knative.
A
A
B
A
So
I
I
like,
I
said
I
know
there
was
a
lot
of
talks
at
this
time.
So
I
really
appreciate
so
many
people
coming
in
to
know
about
the
kennedy
project
and
the
open
source
aspect
of
it
and
we're
going
to
talk
a
little
bit
about
joining
cncf
and
a
little
bit
about
the
the
function
so
just
to
survey
the
room
who
who
have
contributed
to
2k
native
a
dog
or
code.
B
A
Don't
miss
out
the
the
next
one.
We're
going
to
have
one
in
detroit
and
the
cfp
will
come
in
will
come
out
soon.
So
if
this
you
have
a
chance,
but
if
you're
not
you're,
learning,
k-native
or
using
k-native.
Those
are
the
type
of
talks
that
are
the
program
committee
and
part
of
the
programming
committee
that
we're
looking
for
so
don't
don't
be
afraid
if
you're
known
contribute
to
canadian
one
of
the
main
talks
that
we're
looking
for
is
end
user
companies
or
end-user
organizations.
A
A
A
It
could
be
a
piece
of
blog
post,
it
could
be
a
tutorial,
it
could
be
just
joining
slack
and
answering
questions
on
stack
overflow,
creating
an
issue
creating
an
issue
explaining
like
I
have
this
issue,
and
this
is
a
a
reproduce
that
is
easy
to
reproduce.
Sometimes
people
just
say
they
have
an
issue
and
that's
it,
but
we
always
ask
those
excellent
folks
that
write
all
the
information
like
this
is
how
to
reproduce
it
in
a
in
a
simpler
way.
So
that's
that's.
A
Con
everything
counts,
actually
those
counts
into
contributions
for
voting
for
our
members.
So
currently,
if
you
are
contributing
those
those
type
of
things
you
can
vote
in
the
toc
elections,
the
technical
oversight
committee
is
having
elections
right
now
and
you
can
go
online
and
vote.
If
you
are,
you
are
a
contributor
and-
and
we
count
those
contributors
in
the
dev
stacks
like
we,
the
dev
stacks
that
we
use
for
kubernetes
on
the
other
cncf
projects.
A
B
A
More
here
so,
if
and
and
take
and
take
stickers
out
right
to
give
to
your
friends
or
if
you
are
doing
meetups
in
your
country,
where
you're
from
about
k
native
right,
you're,
giving
a
talk,
you
know
you
can
give
stickers
out
and
we're
going
to
have
a
cncf
store.
So
if,
if
that's
something
that
you
want
to
continue
doing
like
running
meetups
and
be
an
ambassador
or
an
advocate
for
k
native
now
we're
in
cncf,
we
have
funds,
we
we
have.
We
have
money.
B
A
Can
use
to
give
swag
so
we're
trying
to
get
the
store
up
up
up
and
running.
I
think
we're
going
to
first
thing
is
going
to
be
t-shirts.
We
didn't
have
them
for
here,
but
for
detroit
I
hope
we.
Hopefully
we
have
both
stickers
t-shirts
and,
if
lindsay
can
get
me
socks,
I
really
want
to
suck
skating
in
the
socks.
I.
B
A
Are
the
two
people
random
people
up
here?
My
name
is
carlos
antana.
I
play
the
guitar
make
millions,
and
now
I
heard
the
kubernetes
is
awesome
and
people
are
making
more
millions
out
of
kubernetes.
So
I
need
to
to
get
in
there,
I'm
an
architect
in
ibm.
I
work
with
a
lot
of
customers,
insurance
companies,
bank
companies
trying
to
make
their
software
and
ibm
software
run
on
kubernetes
the
best
way
possible.
A
With
devops
and
upstream
I
work
on
k,
native
and
steering
committee
and
in
kubernetes,
I'm
in
the
sig
release
recently
joined
there
and
the
release
team
lead
for
release,
notes
125,
helping
124.
So
if
you
are
in
also
in
kubernetes
upstream,
come
say:
hi,
because
I'm
trying
to
meet
and
learn
that
that
journey
about
all
the
six
and
maricio.
B
Yeah,
so
my
name
is
latino.
I
will
be
super
short.
I'm
I'm
working
for
vmware,
upstream
k
native
as
well
working
on
functions
a
lot
these
days
working
also
a
little
bit
on
creative
eventing,
but
I
I'm
truly
passionate
and
close
to
developers.
So
I'm
really
pushing
forward
to
get
like
a
great
developer
experience
there
on
the
functions
project.
It's
pretty
exciting.
We
will
be
showing
a
bit
of
that
now.
A
B
It's
like
just
a
quiz
game,
pretty
simple
stuff,
but
if
you
don't
see
it
before
you
play,
it
might
be
too
fast
for
for
some
some
people
there
so
usually
like
this
is
a
quiz
game.
You
go
there.
You
just
generate
a
player's
name,
because
we
don't
want
you
to
enter
your
crazy
names
and
then,
when
you
have
one
that
you
like,
then
you
start
playing
right.
B
As
you
can
imagine,
this
is
being
built
by
functions,
but
that
basically
means
that
each
question
processing,
like
the
inputs
that
you're
providing
it's
just
a
function
that
will
be
get
started
in
a
kubernetes
cluster
right.
So
the
moment
you
start
the
question
you
will
see
here
a
timer
and
you
have
10
seconds
to
to
answer.
If
you
save
some
time,
for
example,
five
seconds
there,
that's
going
to
count
in
your
your
points,
experience
right
like
an
I
corrected,
maybe
kind
of
like
kind
of
like
okay.
B
So
I
get
10
points
there
and
you
can
see
here
that
you
know
a
function
was
created
there
and
bootstrapped
in
the
cluster.
I
can
do
that
for
question
two,
which
is
a
little
bit
different.
It
has
some
pressing
buttons
and
stuff,
and
you
will
see
that
as
soon
as
the
timer
runs
out,
a
new
function
will
be
created
in
the
cluster
right.
If
we
are
all
playing
at
the
same
time,
we
will
just
be
sending
a
lot
of
you
know.
Putting
a
lot
of
demand
on
the
system.
B
So
functions
will
be
a
scale
up
dynamically
by
k
native
well.
What
I
wanted
to
explain
here
is
in
the
last
like
in
the
last
screen
here
you
have
like
this
tweet
button,
basically
that
when
you
click
it,
it
will
take
you
to
twitter
and
if
you
tweet
and
you
rank
high
in
the
leaderboard,
we
will
be.
You
know,
sharing
some
swag
in
there
as
well.
So
now
you
know
how
it
works,
let's
go
through
the
presentation
and
then
we
will
be
playing
together
at
the
end,
carlos.
A
It's
good
to
spread
it
out
event
driven
applications
which
is
async
operations.
I
think
cloud
events
it's
based
on
cloud
events,
which
is
another
cncf
project
on
those
we
have
a
reference
implementation,
but
k
native,
is
also
an
api.
So
you
can
take
an
api
for
developer
experience.
We
made
the
api
v
1.0,
so
you
say
it's
a
stable
api
that
we
feel
confident
going
out
to
do
conformance.
A
A
The
way
you
manage
so
a
lot
of
questions
when
you
have
for
running
k
native,
usually
the
answer
is
like
you:
do
it
the
kubernetes
way
right?
So
we
put
the
developer
experience
that
abstraction,
but
at
the
end
of
the
day
a
lot
of
people
like
to
use
it
because
some
of
the
lower
level
questions
they
get
answered
like
you,
do
it
either
the
kubernetes
way
or
a
cloud
provider
way.
A
Canada
features,
we
can
say
the
simpler
abstractions
that
get
very
appealing
to
folks
is
the
I
didn't
doom
scrolling
right.
We
have
twitter
twitter
doom
scrolling,
we
have
yamamoto
scrolling.
Would
you
start
with
a
yaml
with
the
ingress
and
the
cert
manager
and
the
deployment
and
the
service
and
get
the
labels
correct?
A
And
then
you
have
the
hpa
and
you
can
have
maybe
some
service
mesh,
routing
thing
percentages
and
weight
by
the
end
of
the
day
you
have
a
lot
of
yammer,
so
what
we
try
to
do
is
like
abstract
that
into
a
simpler
abstraction
that
it
literally
is
like
10
lines
of
code
that
you
can
get
started
with
a
serving
yama
file.
Would
you
specify
here's
the
container
and
here's
the
port,
and
if
the
port
is
8080,
you
can
just
omit
that
the
other
one
is
auto
scaling
like
this
morning.
A
They
were
talking
about
the
in
the
keynote
of
the
energy
efficiency,
of
how
much
cpu
is
wasted.
So
what
we
want
to
do
is
have
as
many
pods
right
that
have
been
packing
into
into
auto
scaling,
so
you
can
have
maximum
efficiencies
to
get
as
many
deployment,
definitions
right
and
those
deployment.
Definitions
will
be
sometimes
scaled
to
zero
and
will
not
consume
energy.
A
Well,
we
want
to
see
what
is
working
for
companies
and
share
that
and
build
that
in,
but
at
least
in
in
k
native
we
have
one.
That
is
time
based.
Basically,
you
give
it
like.
I
want
to
roll
out
this
the
new
revision
in
one
hour,
so
it
would
split
that
one
hour
in
100
increments
and
it
will
start
running
out
the
percentage
of
the
traffic
right
from
zero
to
100
because
you
don't
want
to
like
suddenly
like
send
all
the
traffic
to
the
new
revision.
A
The
other
one
is
event
integrations,
and
this
is
where
we
have
a
need
for
sources.
So
we
have
the
the
we
have
channels
and
subscriptions
that
is
kind
of
a
direct
communication
messaging
platform.
But
we
also
have
a
kind
of
a
hub
or
broker
pattern
that
you
can
have
consumers
or
or
syncs
that
tap
into
that
into
those
cloud.
Events
based
on
different
filters
and
those
can
be
dynamic
filters
which
is
a
is
behind
a
feature
flag.
A
So
if
you
have
seen
demos
or
examples
of
being
like
strict
to
some
attributes
of
that
color
event,
there's
a
dynamic
filter
for
that.
For
that
event,
integration,
but
we
need
event
sources
more
from
the
community
and
then
handling
events
is
like
somebody
produces
events.
It
could
be
a
cloud
provider,
it
could
be
pops
up
from
from
google,
it
could
be
trigger.
Mesh
has
a
lot
of
integrations.
A
They
can
send
you
events
from
different
providers
and
cloud
providers,
or
it
could
be
your
own
events
in
your
application,
so
you're
handling
events
and
producing
events,
and
that's
there
was
a
great
talk
yesterday
by
pablo.
That
explains.
How
do
I
handle
events?
Do
I
reply?
Do
I
reply
with
an
error
which
is
an
interesting
aspect
to
that?
A
The
other
one
is
pluggable,
since
we
are
using
kubernetes,
we
are
careful
of
choosing
the
abstractions,
but
also
we
are
needing
help
from
the
community
in
terms
of
like
what
are
the
things
that
we
expose
into
those
in
those
type
of
things
by
using
kubernetes
right,
you
can
have
controllers
web
hooks
that
annotate
certain
things
we
have
to
leave
that
alone,
because
you
have
the
need
for
introducing
kind
of
specific
configurations
in
those
in
those
deployments.
But
it's
pluggable
in
the
terms
of
you
can
have
cloud
events
or
you
can
have.
A
For
example,
I
was
mentioning
the
broker
so
right
now,
if
you,
your
data,
core
assistance
of
events
is
rather
than
q,
plug
it
in
if
you're
doing
dev
in
a
kind
cluster
in
your
computer,
you
can
have
the
in-memory
one
or
if
your
system,
you
already
established
your
infrastructure
on
kafka,
you
can
tap,
you
can
plug
the
kafka,
so
the
abstraction
is
pluggable
in
the
things
that
you
do
and
you
don't
have
to
change
the
definition
of
the
trigger
or
the
handler
for
that.
So
we
try
to
make
it
very,
very
pluggable.
A
This
is
this
is
one
that
I
added
last
minute,
which
is
came
out
out
of
this
week,
and
we
still
have
some
information
of
k
native
that
people
have
heard
in
the
past
and
I
just
wanted
to
have
some
miss
buster.
So
the
first
one
I
think
it
comes
out
a
lot
like
I
can
use
k
native
because
it's
just
istio
and
I
don't
know
how
to
use
istio
and
is
so
big
that
I
can
like
burns.
My
laptop
up
right
and
I
cannot
figure
out-
you
don't
have
to
use
istio.
A
A
We
have
our
own
ingress.
That
is
small
enough
that
implements
the
the
minimum
things
that
we
need
is
called
courier
and
we
have
contour
and
and
is
still
there,
it's
still
without
the
mesh
and
with
the
mesh.
But
you
don't
have
to
use
istio,
not
saying
that
this
is
bad
or
anything.
It's
like.
Not
anyone,
not
everyone
is
using
estee.
A
A
A
You
can
add
that
I
think
yesterday
somebody
asked
about
arm
and
like
we,
we
run
raspberry,
I'm
a
fan
of
running
k-native
for
raspberry
pi,
because
I
have
a
little
bit
a
lot
of
small
applications
there,
but
not
not
running
so
they
run
when
there's
an
event
in
the
like
in
my
house,
in
auto
automation
and
iran.
So
it
supports
our
controllers.
Are
building
go
and
there
the
images
are
multi
architecture,
so
you
can
run
it
in
arm.
A
I
already
mentioned
the
dynamic
filters
and
header-based
routing
you
can
have
the
dns
of
that
function
or
or
service
have
an
extra
sub-domain
that
you
can
target
the
url,
but
there's
applications
that
you
want
to
do
certain
things
by
header
from
an
application
that
want
to
get
to
a
revision
or
the
last
revision.
You
can
have
a
header
and
then
have
the
routing
to
that
to
that
service.
A
So
those
kind
of
the
myth
busters
that
some
people
try
k
native
and
they
were
not
able
to
get
it
into
their
production
application
because
they
were
missing
one
or
two
features.
So
I
just
wanted
to
point
out
a
few
of
them
that
give
it
another
shot.
And
if
you
find
something
that
is
blocking
you,
you
know
tell
us
and
we
can
help
you
out.
A
A
No
one
wants
to
be
like
this,
the
single
company
in
the
first
company
to
use
k
native
in
production,
but
we
have
some
companies
in
production
and
some
companies
building
a
platform
see
people
like
red
hat,
ibm,
vmware,
google,
where
are
the
the
the
main,
the
first
ones
and
trigger
mesh,
which
is
a
it's
a
startup
that
basically
started
out
of
the
the
innovation
of
k,
native
and
cloud
events.
But
we
have
case
studies
in
the
website.
A
A
A
B
A
A
The
the
project
structures-
these
are
the
we
have
a
steering
committee.
We
have
a
technical
committee
steering
works
with
more
of
the
community
and
the
health
of
the
project,
the
oversight
technical
committee
we
having
I
mentioned
at
the
beginning.
We
have
in
elections.
So
if
you
can
vote,
go
ahead
and
vote
for
one
of
the
candidates
and
working
groups
were
divided
into
working
groups
so,
depending
on
your
preference
or
your
skills
or
the
things
that
you
want
to
learn,
join
a
working
group
and
you
can
just
join
there's
no
requirements.
A
You
can
join
the
meetings,
start
learning
what
they're
working
on
from
productivity
that
work
on
infra
to
serving
and
things
like
venting.
I
think,
there's
a
new
one
functions.
You
say
it's
a
hot
one
that
is
just
became
a
working
group
roadmap,
we're
looking
into
api
gateway,
kubernetes,
ingress,
v2
things
that
we
presented
yesterday
like
container
freezer
and
a
security
audit.
That
is
kind
of
a
check
mark,
saying
that
we
say
require
it's
one
of
the
many
requirements
to
go
into
cncf
graduation
and
we
started
like
that
process.
A
Evan
is
is
working
on
that
and
also
if
you
are
a
security
person,
we
would
like
to
see
you
join.
So
we
have
an
open
community
that
we
want
to
hear
what
are
the
things
maybe
we
put
in
the
rfp
and
also
when
the
outcome
of
like
what
are
the
security
findings
dealing
with
like
the
tls
version
and
the
the
ciphers
and
all
so
you
in
that
space.
We
need
people
like
that
like
to
help
us
out
clicker
there
you
go.
B
Okay,
so
yeah,
I
think
that,
like
following
that
message
and
the
state
of
the
project,
I
would
say
that
k
native
functions
is
a
very
good
place
to
start
contributing.
We
are
actively
looking
for
new
contributors,
and
this
is
the
good
thing
about
functions.
Is
that
it's
like
a
polyglot
place,
no
matter
which
language
you
know,
you
can
definitely
contribute
to
the
project.
If
you
are
into
go,
you
can
contribute
into
the
cli
and
that's
what
I
want
to
quickly
show
you
kind
of
like
what
you
can
do
with
functions
today.
B
B
B
Pretty
pretty
simple
stuff
again,
this
funk
cli
allows
you
to
scaffold
the
project.
This
is
just
a
very
simple,
simple
source
code
here,
like
nothing.
It's
just
saying
you
know
this
is
a
function.
It's
going
to
do
something
here.
This
is
where
you
write
your
code,
and
this
is
the
output
of
the
function
right.
So
hey
maintainers
right,
so
pretty
simple
function.
It's
not
going
to
do
much,
but
the
experience
behind
this
is
like
the
idea
of
here.
B
You
know,
with
your
docker
demon
in
your
laptop,
you
can
do
it
remotely
in
a
cluster,
and
what
we
see
here
is
that
the
function
you
know
the
container
was
built.
It's
now
pushing
this
function
container
to
the
docker
register,
in
this
case
docker
hub
with
my
you
know,
with
my
account
and
then
the
next
step.
It's
going
to
be
deploying
that
into
the
kubernetes
cluster.
That
is
running
so
as
a
developer.
I
can
focus
on
writing
code.
The
code
of
that
function.
B
I
can
connect
that
function
to
a
database
or
do
whatever
you
want
to
do
in
the
function
and
then
just
use
the
func
cli
just
to
move
that
into
a
cluster.
That
can
be
like
the
your
development
cluster,
for
example.
Now
it's
deploying
the
function
and
at
the
end
of
this
kind
of
like
running
this
command,
what
I'm
expecting
to
have
is
just
a
url
that
I
can
basically
access
by
just
doing
an
http
request
right,
so
I
went
from
having
no
project
whatsoever
to
a
function
that
runs
inside
kubernetes.
It's
leveraging
the
entire.
B
You
know
framework
of
k
native
in
this
case
it's
automatically
a
scaling
based
on
demand
and
also
it's
going
to
be
downscaled
to
zero.
If
I
don't
use
it
for
a
while
in
just
three
minutes,
which
is
pretty
nice.
In
my
opinion
and
again
this
is
polling
lot,
so
I
can
create
like
a
function
using
java
or
I
can
create
a
function
using
rust
or
any
other.
You
know
energy
efficient
language.
B
B
Like
the
answer
of
like
a
player
you're
going
to
just
store
that
in
in
redis
and
then
you
will
have
like
we
will
have
like
a
leaderboard
screen
which
basically
has
a
different
function
that
goes
to
release,
get
all
the
scores
for
you,
your
your.
You
know
your
play
your
game
play
and
then
just
crunch
that
data
and
then
send
it
to.
You
know
like
a
view
that
it's
basically
a
ranking
when
you
start
building
these
applications,
you
start
do
we
have
how
much
time
do
we
have.
B
When
you
start
building
this
kind
of
like
application,
you
will
start
realizing
that,
for
example,
in
this
case,
if
your
functions
are
like
the
ones
that
I
show
that
are
synchronous,
you
need
to
like
send
an
http
request
to
the
function.
So
the
function
can
do
something
you
will
start
dealing
with
latency
issues
right
like
in
this
case,
every
time
that
I
want
to
evaluate
the
score
for
a
level
I
need
to
go
to
the
function,
calculate
the
score,
then
go
to
redis
store.
B
You
know
the
score
and
then
go
back
with
the
answer
to
the
to
the
to
the
user
right.
So
all
that
kind
of
thing
takes
time.
So
it's
like
when
you
start
building
functions.
The
way
of
the
you
know
the
mental
model
that
you
use
in
order
to
code
these
functions,
it's
a
little
bit
different
to
normal
applications
that
if
you
are
working
with
lambdas
or
any
other,
you
know
function
platform,
it's
pretty
much
the
same,
but
you
need
to
kind
of
like
be
aware
as
a
developer.
B
The
functions
that
we
have
used
here
for
the
levels
are
all
synchronous,
so
they
all
have.
This
kind
of
like
latency
problem,
you
need
to
wait
for
the
functions
to
return
in
order
to
continue
playing
the
game
in
this
case,
but
because
for
that
we
are
only
using
k
native
serving
right
like
the
serving
part
of
the
project.
We
can
also
start
using
the
eventing
part
of
the
project,
which
will
give
us
like
a
more
reactive
approach
right.
B
So,
every
time
that
we
score
like
one
of
these
levels,
we
are
emitting
a
cloud
event
to
a
native
broker,
which
is
a
cloud
7
router
and
that
event
is
being
routed
to
the
front
end,
which
is
then
forwarded
to
the
user
interface.
You
know
that's
client-side,
it's
in
my
browser
running
here,
so
we
have
cloud
events
running
all
over
the
like
moving
around
all
over
the
place,
and
we
have
this
very,
very
generic
infrastructure
that
we
can
wire
dynamically
for
our
applications.
We
can
connect
more
pieces
if
you
want
to.
B
We
can
route
those
events
to
multiple
functions,
to
keep
doing,
processing
and
stuff.
In
my
opinion,
this
provides
you.
This
gives
you
a
very
nice
developer
experience,
because,
when
you're
building
functions
in
order
to
use
all
these
messaging
and
cloud
events
and
all
that
stuff
as
a
developer,
I
only
need
to
use
http.
B
I
don't
need
to
just
you
know,
connect
to
a
message
broker
or
connect
to
kafka
or
have
an
extra
dependency
in
my
application
to
generate
cloud
events,
and
in
this
case
we
are
using
our
socket
as
like
a
bi-directional
channel
from
the
you
know
from
the
cluster
to
the
browser,
in
this
case,
so
pretty
simple
and
complicated
stuff.
At
the
same
time,
we
are
planning
to
put
this.
B
B
Robocop
in
detroit,
we
can
do
that.
We
can
do
that.
We
can
do
a
hackathon
as
well
right
yeah
before
I
start
and
share
this
playing,
I
wanted
to
just
run
a
set
of
commands.
I
think
that
that's
pretty
much
it.
I
want
to
check
that
the
leaderboard
is
there,
you
get
the
qr
code.
Yes,
I
will
just
share
it
in
a
bit.
So
as
soon
as
this
is,
you
know
working
which
is
now
right
now.
I
will
just
share
the
qr
code
with
you
folks.
B
A
B
B
B
A
A
Yeah,
I
think
the
the
end
the
end
slide
right.
We
do
have
an
extra
slide,
that's
true
yeah,
so
it's
a
call
out
for
the
community
to
join
us.
Like
I
said
you
can
help
in
any
capacity
if
you're,
good,
writing,
docs,
you're,
good,
advocating
you're,
good,
organizing
and
working
with
the
community.
We
need
help
in
that
and
also
security
network,
all
the
aspects
of
of
the
of
the
project.
So
we
we
work
on
everyone
that
wants
to
either
learn
or
contribute.
B
Yeah-
and
I
want
to
say,
like
functions-
is
definitely
an
easy
entry
point
for
people
that
it's
already
coding
different
kind
of
applications.
It's
a
polyglot
place.
So
if
you
want
to
come
just
reach
out,
there
are
a
bunch
of
canadian
function,
maintainers
here
as
well,
so
you
know
just
get
in
touch
and
templates.
They
can
help.
A
A
C
C
C
No
I'm
joking,
that's
great
great
stuff!
You
know
what
I'm
coming
from
a
sort
of
different
words:
the
telco
world
that
we're
from
vodafone,
and
we
are
running
now
a
new,
a
lot
of
new
activities
on
cloud
and
I
got
into
knitting
from
colleagues.
You
know
supporting
us
other
companies
and
it's
really
very
interesting.
C
C
B
A
You
do
it
officially,
okay,
so
so
the
question
is
you
as
a
platform
team
is
in
charge
of
the
cluster
and
giving
the
developers
access
to
to
the
functions?
How
the
best
to
run
a
monitor
that
cluster?
I
guess
right.
So
one
level
is
the
kubernetes
level
that
we're
just
launching
pods
launching
deployments
so
those
you
super,
your
your
standard
monitoring
stack
and
then
we
have
evan
can
talk
a
little
bit
more
after
we
finish
in
details
about
the
open
sensors
and
the
open
telemetry
of
the
controllers
of
k
native.
I
think
that's
also.
A
A
And
the
cube
proxy
cycle,
so
those
are
like
k
native
components
that
you
want
to
tap
into
observability,
to
see
how
are
the
health
and
how
did
you
scale
them?
So
there's
there's
aspects
of
like
com,
making
the
hpa
of
those
components,
so
they
can
have
redundancy
and
scaling.
So
those
those
type
of
type
of
things
are
in
the
website.