►
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Intro: Virtual Kubelet - Sravan Rengarajan, Microsoft & Ria Bhatia, Microsoft
Join us for KubeCon + CloudNativeCon in San Diego November 18 - 21. Learn more at https://bit.ly/2XTN3ho. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
Virtual Kubelet is a newly inducted project in CNCF that allows Kubernetes clusters to scale efficiently to any cloud provider of their choice. This session will go through the architecture of the project, applicable scenarios with public cloud providers, and demos to burst out existing kubernetes clusters without adding additional infrastructure. The session will also go through existing Virtual Kubelet implementations, and how users of Kubernetes can utilize the providers. This includes implementations from AWS, VMWare, Azure, HashiCorp and more. If you want to adopt Kubernetes and containerization, but not deal with managing more infrastructure then this is for you.
https://sched.co/NrrT
A
Hi
everyone
I'm
RIA,
Bhatia
I,
am
part
of
Microsoft,
but
I'm.
Also
a
core
maintainer
on
virtual
kulit
I've
been
part
of
this
project
since
its
inception
in
the
beginning.
So
I'm
excited
to
talk
to
you
guys
about
it,
and
we
also
have
one
of
our
providers,
which
is
Asher's
virtual
node
providers.
Here,
hi.
A
On
Twitter,
if
you
want
to
reach
out
I,
have
a
dog
named
drew
she's,
a
rescue
puppy
from
Taiwan
actually,
and
then
here
are
links
which
might
not
be
too
useful
because
you
can't
click
on
any
of
these.
But
when
we
put
them
up
on
on
like
the
website,
the
CN
CF
website
you'll
be
able
to
see
it,
but
basically
that's
also
my
github
handle.
So
if
you
want
to
reach
out
there,
you
can.
B
A
Cool
brittle
couplet,
since
it
our
logo,
it
was
voted
on
by
the
community
and
we
decided
to
do
this
I
kind
of,
like
it
kind
of
looks
like
star
trek
to
the
next
slide.
What
happened?
Why
did
we
open-source
this?
So
a
long
time
ago
we
had
this
project
called
the
azure
container
instances
connector,
which
was
created
by
Brendan
burns,
one
of
the
cofounders
of
kubernetes.
A
He
had
this
idea
that
we
should
start
to
abstract
the
core
infrastructure
of
of
what
people
were
in
kubernetes
on
so
today
we
run
it
on
a
bunch
of
VMs,
but
customers
don't
necessarily
want
to
run
all
that
infrastructure
or
see
it.
They
really
just
want
to
see
their
containers
or
possibly
just
their
apps.
So
this
was
kind
of
the
first.
Oh
look
over.
There
oh
go.
A
Okay,
apparently
I
have
to
be
here,
but
basically
he
he
was
like
what
if
customer
is
basically
customer
like
we
don't
want
to
see
infrastructure
we
don't
have
to.
We
don't
want
to
manage
it,
so
the
FCI
connector
happened.
We
also
released
a
service
called
your
container
instances
and
a
bunch
of
other
platforms
kind
of
followed
that
lead
like
a
tube
AWS
Margate
Alibaba
cloud
elastic
container
instances.
A
So
these
are
all
examples
of
services
that
just
spin
up
containers
on
the
fly
and
they
charge
it
by
second,
and
you
get
to
specify
the
amount
of
cores
in
memory
that
you
want
for
that
specific
container.
But
you
don't
you
don't
see
any
of
the
underlying
VM
infrastructure
from
there
we
took
they
say
a
connector
project
and
realized
that
we
wanted
to
be
able
to
scale
out
these
kinds
of
container
instances,
but
we
didn't
want
to
make
her
own
just
read
system.
A
So
we
wanted
to
utilize
kubernetes
for
scaling
and
for
service
discovery
and
for
all
of
the
other
good
bits
that
kubernetes
has.
So
that's
when
we
created
virtual
couplet.
We
also
realized
that
if
we
wanted
to
open
source
it
and
have
a
community
around
it,
we
should
also
allow
other
providers
to
plug
into
it.
So
we
really
just
created
this
interface
into
what
it
means
to
be
like
the
couplet
in
kubernetes.
A
A
So
in
the
next
year
we're
gonna
be
gathering
some
case
studies
and
going
to,
hopefully
you
one
day
be
an
inconvenient,
and
we
also
just
announced
1.0
so
basically
with
us
saying
that
we're
one
dot
o--
we're
saying
that
we're
stable,
we're,
not
gonna
change
the
interface
drastically
and
that
anyone
that
plugs
into
our
interface
can
be
certain
that
virgil
kuba
on
its
own.
It's
basically
production-ready.
So
if
you
want
to
run
production
workloads
on
this,
you
can
we've
also
revamped
the
entire
repo,
so
everyone
used
to
be
plugged
in
to
the
same
binary.
A
So
when
we
build
everything
would
be
one
binary.
Like
all
of
the
providers,
alibaba's
provider
who
always
provider
address
provider,
was
one
binary.
We
have
just
split
everything
out
so
now
everyone
has
their
own
repo
and
if
you
build
a
virtual
coop
with
binary
it's
specific
to
your
provider,
so
that'll
help
with
a
lot
of
like
efficiency,
things.
Things
like
that
and
yeah.
A
B
A
Basically,
this
is
a
snapshot
of
what
happened
about
two
years
ago
before
cou
Cana
Austin.
We
got
together
a
bunch
of
people
at
Microsoft,
and
then
we
also
partnered
with
a
company
named
hyper
SH,
just
no
longer
with
us
as
a
company,
but
we
moved
the
project
from
being
typescript
to
being
written
and
go
and
that's
when
we
really
stood
so
virtual
cool.
It's
all
ready
to
go,
and
it
was
also
written
by
some
cool
people
that
were
part
of
this
cloud.
Developer
advocate
team
at
Microsoft.
A
B
B
So
what
we've
done
with
the
virtual
cupola
is:
we've
created
a
pod
that,
when
it
gets
placed
on
a
kubernetes
cluster,
it
registers
itself
as
a
node.
So
the
kubernetes
cluster
thinks
that
there's
actually
another
kulit
there
and
that
coolbut
represents
a
note.
And
that
way
you
can
schedule
pods
out
to
this
virtual
node,
since
it's
not
an
actual,
since
it's
not
a
real
node.
The
capacity
of
this
is
actually
backed
by
a
number
of
a
number
of
providers.
B
Different
infrastructure,
including
Azure,
container
instances
or
poly
Baba
elastic
container
instances,
Amazon,
Fargate
and
whatnot,
and
going
along
with
with
what
Rio
is
saying
we
want.
We
want
to
make
kubernetes
we're
pod
centric
nodes
is
a
a
concept
right
now
in
kubernetes,
but
as
developers
one
shouldn't
have
to
manage
and
provision
nodes
all
the
time
you
want
to
be
dealing
with
pods
as
much
as
you
can
yeah.
A
With
this,
how
do
we
tell
providers
like
how
they
should
expose
those
resources
to
customers,
because
the
customer
says
I
need
to
scale
up
to
maybe
a
million
containers,
but
the
provider
is
showing
that
it
could
scale
up
to
million
containers.
Kubernetes
will
schedule
all
those
pods,
but
that
might
not
be
true.
So
then,
as
a
customer,
you
might
only
get
a
thousand
containers
scheduled
because
that
number
was
faulty.
A
So
that's
something
that
we're
thinking
about
and
there's
a
couple
other
things
like
a
couple
things
that
we
don't
do
like
privileged
containers
expect
to
interact
directly
with
no
resources.
We
don't
allow
that
with
VK.
You
cannot
directly
talk
to
the
node.
You
can't
directly
access
any
of
the
node
files
or
anything
like
that.
So
some
monitoring
things
don't
work
exactly
as
expected.
So
yeah
there's
just
a
couple
things
that
you
have
to
think
about
and
then
a
note
is
a
single
fault
domain.
A
B
A
B
Going
off
of
our,
he
was
saying
a
lot
of
the
work
that
we're
doing
in
the
the
virtual
cooler
right
now.
Project
right
now
is
to
be
more
compatible
with
the
full
kubernetes
api,
whether
that's
being
obviously
being
able
to
create
delete.
Pods
gather
metrics
from
pods
attach
of
volumes,
support,
GPU
type
of
pods,
etc.
You
name
it
yeah
all.
A
Right
so
virtual
kou,
but
that
was
kind
of
what
the
node
does
and
I
tried
to
give
a
little
bit
of
an
explanation
of
what
BK
did
layer
it.
On
top
of
it
I'm
the
virtual
Kubla
itself.
We
treat
the
concept
with
pods
and
nodes
in
the
abstract,
so
we're
literally
just
passing
through
a
string
when
you
see
a
node,
a
virtual
couplet
node,
it's
just
a
string,
that's
being
passed
through
to
kubernetes
and
notice
about
a
resource
again,
but
the
way
that
we've
set
it
up.
It
isn't
technically.
A
So
the
specifics
of
how
you
create
a
pod
delete
a
pod
update,
a
pod.
Add
files
like
volumes,
for
example,
and
things
like
that
or
like
config,
Maps
and
secrets,
and
all
that
are
all
contained
within
the
interface
itself,
but
the
logic
or
how
all
that
happens.
Is
your
service
API.
So
all
the
provider
API
s
could
connect
it
up
to
the
kubernetes
api
is
through
those
through
that
interface.
The
common
code
in
virtual
cupola
is
relatively
small,
because
it's
very
provider
specific
code.
A
We
basically
are
a
home
for
all
of
these
providers
to
interact
together,
but
the
logic
for
how
things
work
are
held
within
the
provider
repos
itself.
What
an
interesting
one
is
basically
serves
discovery,
because
how
do
you
do
that
when
you
just
have
a
concept
of
like
a
node
popping
up
kubernetes,
you
need
a
coup
proxy,
basically
on
the
node
to
be
able
to
talk
out
to
the
to
the
world
and
have
service
discovery
in
Azure.
I
know
what
we've
done.
A
Is
we
spin
up
a
coup
proxy
as
a
sidecar
to
every
container
instance
that
spins
up,
but
the
way
that
maybe
Alibaba
does
that
or
Huawei
does
that
might
be
different?
I
actually
think
they
do
very,
very
similar
thing,
but
that's
come
completely
obstructed
away
from
the
user
in
Carre's
today
and
managed
service.
You
would
actually
see
that
ku
proxy
or
an
that
couplet
for
this.
You
just
see
this
node
with
no
couplet
and
no
ku
proxy,
and
none
of
that.
It's
all
abstract
it
away,
which
is
kind
of
nice
if
it
works
sure.
C
A
D
C
A
C
A
You
can
have
a
bigger
cluster
with
this
one
node
has
that
you
can
layer
multiple
pods,
X
amount
of
pods
that
isn't
bounded
by
a
node
resource.
I.
Think
that
answers
your
question.
Hopefully
you
could
layer
Bernays
in
kubernetes.
If
that
was
another
question,
you're
asking,
if
you
can
like
have
virtual
couplets
spin
out
to
another
kubernetes
cluster,
that's
completely
possible
because
it's
just
an
API
that
you're
calling
out
to
well.
A
Okay,
yvk
we've
basically
abstracted
away
what
it
means
to
be
a
couplet
in
kubernetes
and
that's
actually
really
interesting
to
a
lot
of
people.
For
example,
if
you're
trying
to
mask
another
Orchestrator-
and
you
want
to
use
the
kubernetes
api
is,
but
you
don't
want
to
lose
everything
you've
built
with
another
Orchestrator.
So
if
you
go
check
out
our
repo
right
now,
there's
some
interesting
have
things
happening
from
other
providers
that
are
trying
to
do
that
yeah.
A
So
a
couple
of
use
cases
we
have
the
one
I
talked
about
before
for
fast
bursting
if
you
have
a
sudden
amount
of
load,
basically,
for
example,
if
you're
a
meter
reading
company
and
you
need
to
scale
up
your
the
amount
of
compute
resources
that
you
have
depending
on
if
there
was
a
national
disaster.
So
if
there's
a
natural
disaster,
you
need
to
now
read
all
of
the
meters
to
understand
how
much
electricity
is
there
and
what's
gone
down
and
what
you
need
to
go
and
fix
in
that
use
case
virtual
people.
A
B
A
So
this
is
what,
if
you
want
to
be
a
provider.
This
is
what
you
end
up
doing
you
end
up
filling
in
this
code.
If
you
can
understand
how
to
create
a
pod
and
delete
a
pod
and
update
will
update
it's
a
little
bit
questionable,
because
no
one's
really
done
that
yet,
but
basically
delete
a
pod
and
get
a
pod
and
possibly
get
logs.
A
You
can
be
a
provider
in
virtual
couplet,
it's
a
really
low
bar,
so
if
you're
Domino's
and
you
want
to,
if
you
create
a
pod-
and
you
want
to
get
a
pizza
one
that
like
when
you
get
that
pod,
you
can
do
it
I,
don't
know
if
I
explained
that
very
well,
but
anyone
can
be
a
provider.
So
please
join
us,
and
this
is
really
what
you
have
to
do.
You
just
have
to
provide
the
backend
plumbing
necessary
and
support
the
lifecycle
management
of
pods
in
kubernetes.
A
That's
all
your
logic,
it's
not
something
we
do,
but
all
of
the
code
is
open
source,
so
you
can
copy
and
paste
from
any
of
the
other
providers
or
look
at
it.
Yeah
so
extend
kubernetes
to
anything
that
you
want
I've
heard
of
some
interesting.
A
couple
other
use
cases
that
I've
heard
of
is
they
want
a
mask.
Someone
wanted
to
mask
a
satellite
that
was
orbiting
Earth
as
a
node
in
kubernetes.
So
you
can
think
you
now
with
virtual
couplet.
You
can
use
kubernetes
and
the
commands.
A
That's
an
example:
I
really
like
because
I
love
pizza,
but
for
example,
if
you
created
a
pod,
it
would
spin
out
to
Domino's
and
order
you
pizza,
but
you
have
to
create
that
logic.
But
yeah.
A
lot
of
people
are
using
it
for
the
fast
bercy's
case,
where
they
just
spin
up
a
bunch
of
containers
really
quickly,
but
you
can
also
mask
maybe
IOT
edge
use
cases,
so
you
could
have
a
node
representing
a
device,
so
you
could
have
a
node
representing
a
fridge
and
any
time
you
spin
out
a
pod
to
that
fridge.
A
B
Here's
some
examples
of
providers
that
have
already
implemented
the
virtual
equivalent
interface
Alibaba
as
your
AWS,
just
to
name
a
few
few
big
ones.
This
is
a
sample
architecture,
diagram
of
what
it
would
look
like
with
an
IOT
I
just
did
a
deployment.
So
Azorean
was
saying
we
want
the
the
user
to
just
who's
already
familiar
with
kubernetes,
not
have
to
learn
anything
new.
You
can
manage
all.
B
Can
all
software
and
containers
on
your
edge
devices
just
by
using
the
IOT
edge
provider
with
your
already
existing
kubernetes
cluster,
you
don't
have
to
worry
about
nodes
or
what
or
anything
like
that.
You
can
just
spawned
off
workloads
or
containers
to
those
edge
devices.
I
saw
yesterday
that
there
was
a
cool
lightning
talk
of
the
guy
that
built
a
kubernetes
cluster,
with
just
a
bunch
of
rabbits,
raspberry
PI's
and
using
tape
and
a
grubber
band
together.
So
you
has
its
own
kubernetes
cluster
and
you
can
use
that
for
testing,
for
example
yeah.
B
So
this
is
what
it
looks
like
with
Azure.
So
in
Azure
we
have
a
service
called
agile
kubernetes
service,
so
I
managed
kubernetes,
offering
where
Azure
takes
care
of
managing
all
of
the
master
nodes.
So
you,
as
a
customer,
only
have
to
worry
about
the
worker
nodes
and
the
workloads
that
are
on
the,
but
even
as
you
have
to
manage
and
own
and
plan
for
capacity
on
the
worker
nodes,
this
can
get
very
expensive.
Worker
nodes
can
be
underutilized
and
the
startup
time
to
add
more
worker
nodes.
B
If
you
need
to
scale
on-demand
pretty
quickly,
it
can
be
very
slow.
So
we've
introduced
an
offering
called
as
your
virtual
IKS
virtual
nodes,
which
uses
the
virtual
couplet
project,
and
now
you
can.
You
can
burst
out
capacity
of
your
pods
to
Azure
container
instances,
as
your
container
instances
is
Asher's
serverless
containers
offering
where
a
user
can
just
send
a
deployed
containers
and
we
manage
all
the
infrastructure
so
as
you
as
a
user,
only
have
to
worry
about
developing
your
application
packaging
into
a
container
and
and
giving
it
out
here.
Yes,
yeah
this.
B
B
A
This
is
an
open-source
project.
You
can
pave
it
onto
any
kubernetes
cluster,
so
it
doesn't
matter.
If
we
offer
it,
we
don't
support
it.
I
mean
I.
Guess
would
support
it
now
in
Azure,
but
with
open
chefs.
We
wouldn't
exactly
support
it,
but
as
long
as
you
have
access
to
your
VMs,
you
can
deploy
a
virtual
couplet
and
it
will
spin
out
to
a
CI.
You
have
to
fill
in
the
details
yourself,
so
go
to
our
virtual
couplet
repo
itself
for
those
instructions.
So
yes,
yeah.
That's.
B
A
really
good
point
the
washer
provides
here
is
we
we
do
a
lot
of
that
set
up
for
you
and
configure
a
lot
of
networking
and
do
some
other
plumbing
to
make
the
experience
of
installing
VK
and
deploying
pods
to
a
CI,
more
seamless
but
yeah,
theoretically,
any
kubernetes
cluster.
Even
if
it's
open
ship
you
can
install
virtual
coolant
and
burst
out
to
a
CI
or
anyone.
The
other
providers.
B
B
So,
instead
of
having
let
you
know,
let's
say
they
run
a
three
node
cluster
right
now,
instead
of
having
five
nodes
and
two
of
those
nodes
being
very
underutilized
and
then
paying
for
them
24/7
now
they
just
can
take
their
three
node
cluster
and
then
spin
off
extra
pause
into
a
CI.
Whenever
that
marketing
campaign
is
done,
maybe
it's
over
a
weekend
or
something
they
can
spin
that
back
down.
B
This
diagram
shows
you
that
you
know
some
of
the
virtual
machines
there's
going
to
be
empty
space,
that's
wasted,
but
if
you're
using
virtual
nodes,
you
can
just
spin
out
the
pods
to
as
your
container
instances
and
then
create
and
destroy
them,
as
you
wish.
One
thing
I
didn't
mention
is
also.
This
is
a
lot
faster
in
terms
of
speed,
because
you're
you
don't
have
to
spin
up
new
virtual
machines
to
put
the
pods
on
them
as
your
container
instances.
B
So
this
is
a
part
of
the
pod
spec
that
you
need
to
include
when
using
virtual
coolant
and
I'll
show
action.
I'll
show
a
full
yeah
mo
file
in
a
bit,
but
what
this
shows
is
in
on
the
virtual
node,
we
add,
what's
called
a
taint
in
kubernetes,
you
can
think
of
it
as
kind
of
like
a
lock
and
if
you
add
toleration
x'
to
your
pod
spec.
This
is
basically
the
key
to
be
able
to
provision
we're
clothes
on
to
the
node.
With
that
lock.
B
The
reason
why
we
do
this
is,
as
Rio
was
saying,
the
full
compatibility
of
the
kubernetes
api
look,
there's,
not
not.
Everything
is
available
with
with
virtual
couplet,
so
some
special
types
of
workloads
might
not
work
the
way
that
they're
expected
and
if
you
use
as
your
container
instances,
for
example,
yeah.
E
D
D
B
A
B
A
Another
thing,
I
think
another
reason
for
why
this
project
a
lot
of
people
like
it,
is
the
fact
that
it
obstructs
away
the
couplet
so
much
so
past
the
bercy's
case.
It's
really
useful
for
Microsoft,
but
it's
not
super
useful
for
some
other
companies.
Another
thing
is
customers,
don't
want
to
have
to
see
VMs
or
manage
them.
So
in
that
standpoint,
that's
why
I
like
Amazon
and
Alibaba
have
implemented
this,
not
just
because
maybe
their
infrastructure
was
already
fast,
but
because
they
don't
want
their
customers
to
have
to
think
about
nodes
anymore.
A
G
Hello,
so
I
see
it.
This
is
a
really
good
use
case,
but
I'm
just
worried
like
how
does,
or
rather
I
have
a
question
that.
How
does
the
underlying
things
like
the
network
and
like
how
does
even
as
you're
in
a
case,
how
does
it
address
those
things
like
how
do
I
enforce,
to
which
network
it
goes
to
all
the
energies?
We
have
a
concept
of
energies
in
Azure
right.
How
does
that
enforce
that?
Where
goes
the
security?
Do
we
put
network
policies
or
how
do
we
do
it?
Yeah.
E
B
That's
that's
one
way
you
can
do
that
with
Azure
container
instances.
The
azure
networking
team
has
done
a
lot
of
special
work
in
order
for
the
pods
that
are
deployed
to
a
CI
to
be
with
to
be
contained
within
the
same
virtual
network
as
the
full
aks
cluster,
so
I
need
any
features
that
you
can
get
with.
Add
your
virtual
networks,
whether
it's
NS,
G's
or
custom,
routing,
DNS,
etc.
D
G
B
C
B
D
A
That
that's
something
that
we
chose,
because
the
network
is
very
provider
specific
right.
If
you
go
to
alibaba's
cloud
or
you
go
to
Amazon's
Cloud
or
you
go
to
Google's
cloud,
the
network
policies
in
the
way
that
people
create
networks
is
very
specific
to
a
cloud
provider.
We
don't
have
networks
that
span
Google
and
Microsoft.
Yet,
right,
like
you,
can't
create
a
network
for
a
cluster,
that's
an
edger
and
have
it
span
there.
So
it's
provided
specific.
You
have
to
figure
it
out
yourself
from
our
perspective.
A
So
the
note
you
can
still
see
the
node
resource
there
and
when
you
basically
describe
that
node
you'll
still
be
able
to
see
what
OS
type
it
is,
how
much
compute
resources
you
have
and
how
much
disk
space
you
have
I
would
just
be
wary
about
that,
because
they're
fake
numbers,
they're
numbers
that
the
provider
chooses
to
pass
through
for
the
OS
type.
It's
the
same
thing
like
we'll
make
it
easier
for
you
to
spin
out
to
that
specific
OS
type.
A
B
When
you
add,
when
you
deploy
a
pod
to
the
virtual
node,
it's
just
like
any
other
pod
yoots,
but
you
can
specify
how
much
CPU
and
memory
that'll
be
in
that
pod
and
you
can
use
the
coop
Caudill
commands
to
see
how
much
is
actually
being
utilized,
but
that
that
information
is
returned
from
a
CI.
But
at
a
pod
level.
Yes,.
F
B
See
this
information
so
since
these
pods
are
living
on
a
CI,
a
CI
or
a
recent
ACI
case,
we
emit
a
number
of
metrics
out
which
can
be
consumed
either
within
the
cluster
itself
or
with
in
Azure
Monitor
offerings.
So
that
includes
like
network
network
I/o
memory,
CPU
a
few
others
disk
I
believe
as
well.
So
that
that's
one
way
you
can.
You
can
read
that
ok.
B
So
and
a
real,
quick,
another
piece
of
code
that
you
can
add
to
your
yeah
Moses
with
affinities.
So
using
this
you
can
choose
certain
pods
to
go
on
to
the
virtual
node.
The
thing
I
showed
before
is
just
the
key
in
order
to
deploy
onto
the
node
with
the
lock.
If
you
want
a
specific
pod
to
get
placed
on
the
virtual
node
you
can
do
you
can
add
this
affinity,
you
can
either
do
the
preferred
during
scheduled
or
scheduling
or
required
during
scheduling
and.
E
In
normal
covenant
cluster,
we
have
monitor
like
promise
promises
and
they
can
fetch
metrics
from
kool-aid
that
the
metrics
about
that
node
and
about
port
and
our
workload
on
that
bunker
vehicle
a
title
interface.
There
is
no
such
an
interface
that
is
posted
mattress
to
the
monitor
components.
So
if
I
chose
to
use
a
component
as
pose
and
specify
and
provider,
so
I
can
only
depend
on
the
monitors
that
provided
by
the
provider
or
I
can
still
integrate
it
with
promises
of
other
cornetist
monitor
system,
yeah.
B
So
I
mean
I
can
speak
for
a
CI.
We
make
sure
that
the
metrics
that
are
emitted
are
written
back
to
the
metric
server
of
the
kubernetes
cluster,
so
you
can
use
Prometheus
and
an
Ravana
and
actually
read
CPU
and
memory.
You
can
also
write
custom
metrics,
such
as
like
requests
per
second,
that
are
being
tracked
by
your
AC
iPod
to
the
metric
server,
and
then
that
can
be
all
read
through
a
familiar
monitoring
solution
like
Prometheus.
B
A
Right
now,
but
as
we
get
to
maybe
v2,
maybe
these
are
standards
we
should
make
in
virtual
it
for
providers,
because
today
only
the
interface
is
production-ready.
We
haven't
virtual
coop,
but
the
project
hasn't
said
that
any
of
the
providers
are
production
ready
because
we
have
no
standards
around.
Those
so,
like
sure,
has
gone
out
on
their
own
and
said
that
their
GA,
but
virtual
coop
with
the
project,
does
not
have
like
an
interaction
with
Azure
to
make
sure
that
they're
actually
ready
to
be
GA
and
I.
A
B
B
Just
to
wrap
up
and
then
we
can
take
more
questions
at
the
end,
this
is
a
sample
llamo
filed
that
you
can
use
with
virtual
couplet.
A
lot
of
this
should
look
familiar
to
you.
You
can
just
you
can
use
that
images
as
as
normal
I
use
it
an
image.
That's
an
azure
container
registry.
You
can
read
from
kubernetes
secrets,
and
here
I
use
the
node
selector
placement
constraint
instead
of
affinity,
and
then
my
toleration
is
here
as
well
and
then
I'm
gonna
hand
it
back
to
you.
A
C
A
We
can
take
some
questions
up
here
if
you
guys
want
to
come
up
or
a
stick
around,
but
thank
you
so
much
for
your
listening.
It's
good
to
see
that
a
lot
of
people
are
still
excited
about
this
project
and
I
mean
we're
gardening
more
and
more
popularity,
as
time
goes
on,
which
is
really
awesome
and
so
come
join
us
for
a
really
open
community.
We
have
a
slack
channel
in
kubernetes
and
yeah
we'd
love
to
talk
to
you.
So
thank
you.