►
From YouTube: Building Apps with Containers, Functions and Managed Services - Patrick Chanezon & Scott Coulton
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
Building Apps with Containers, Functions and Managed Services - Patrick Chanezon & Scott Coulton
Cloud native applications are composed of many technologies and components, but three canonical abstraction emerged in the past few years that help developers structure their architecture: container, functions responding to events, and managed services. This talk will explain how to develop (Docker, local Kubernetes, virtual Kubelet, OpenFaaS), deploy (managed Kubernetes, functions and services) and package (CNAB specification and tooling) applications using these three components and look at not only deployment workflows but also at day 2 concerns that a developer would need to consider in the cloud native landscape. We will demo every topic and a Github repository will be available for developers to reproduce the demos and learn at their own pace.
https://sched.co/Nrll
B
A
B
So
I'm
Scott
Colton
I'm
based
out
of
Sydney
Australia
I
work
in
the
developer,
advocacy
team
for
Marcus,
often
specializing
cuban
Edy's
and
container
runtimes,
and
all
those
lots
of
things
being
adopted
in
the
docking
captains
project
for
about
four
years.
So
it
probably
feel
was
the
only
one
that
was
older
than
me
and
I'm,
unfortunately
bought
red
hot.
So
you
got
kicked
out
so
now.
I'm,
like
you,
know,
T.
A
So
today
we're
going
to
talk
about
one
big
topic,
which
is
over
the
past
few
years.
People
have
been
using
docker
and
then
kubernetes
to
build
these
cloud
native
applications,
but
nowadays,
more
and
more,
these
applications
become
more
complex
and
typically
you're,
building
an
application
with
three
components:
containers,
server,
less
functions
that
respond
to
events
and
manage
cloud
services.
So
in
this
talk
we're
going
to
try
to
cover
the
developer
experience
for
that.
How
do
you
package
your
application
when
it
contains
all
these
components?
And
how
do
you
make
it
scale?
A
One
of
the
thing
I
wanted
to
say
is
one
of
the
reasons
why
I
was
super
happy
to
join
Microsoft
is
that
Microsoft's
mission
is
around
productivity.
So
it's
about
empowering
every
person,
an
organization
on
the
planet
to
achieve
more
and
it
started
with
Bill
Gates,
creating
visual
basics,
which
started
in
developer
tools
and
so
Microsoft
always
had
a
strong
story
around
trying
to
make
developers
more
productive
and
I.
Think
with
the
history
of
cloud
native
applications
over
the
past
five
years.
A
A
Over
the
past
three
years,
there's
been
a
lot
of
portable
surveillance
platforms
that
emerge
on
top
of
kubernetes.
So
you
have
things
like
the
FN
project
by
Oracle,
which,
which
characteristic
that
it
has
a
nice
way
of
composing
functions,
nucleo,
which
is
a
super
high
performance
and
more
suited
for
intensive
data
processing
opened
fast,
which
is
like
the
Swiss
Army
knife
surveillance
platforms.
It
can
do
a
lot
of
things
and
it's
super
easy
to
use
and
get
started.
Galactic
fog
and
open
wisk.
More
recently,
there's
been
two
projects
that
are
more
like
middleware.
A
On
top
of
which
you
can
build
a
function,
experience
which
are
key
native
and
kada,
so
we'll
talk
a
little
bit
about
Kira
here
and
the
the
CNC
F
has
a
surveillance
working
group.
So
these
diagrams
that
show
what
a
portable
serverless
offering
is
are
coming
from
their
white
paper
that
I
highly
recommend.
If
you,
if
you're
new
to
this
space
on
the
azure
side,
we
have
our
own
first
party
service,
that's
called
Azure
functions
that
we
manage
at
Microsoft,
but
all
the
runtime,
for
it
is
open
source.
A
A
The
dev
experience
I
wanted
to
talk
to
you
about
is
it's
called
the
azure
deck
spaces
and
it's
it's
a
service
that
we
operate
in
Azure
and
that
lets
you
as
a
developer
and
it's
tied
with
a
it's
tied
with
the
visual
studio
code
extension
so
that
you
as
a
developer
when
you're
building
an
application.
You
don't
need
to
know
anything
about
kubernetes.
You
don't
need
to
have
the
runtime
of
the
language
that
you're
developing
in
installed
on
your
machine.
A
So
the
way
the
experience
works
is
that
you
have
a
vs
code,
plug-in
and
there's
a
command
line
as
well
called
easy.
Yes,
and
that
vs
code
plug-in
interacts
with
a
server-side
controller
that
you
install
in
a
namespace
in
your
kubernetes
cluster,
and
so
once
the
connection
between
the
two
is
established.
The
vegans
code
extension
is
able
to
prime
your
project.
A
I
should
talk
to
the
team
about
that,
because
there's
lots
of
options
there
and
then
it's
deploying
it
with
the
hand
chart,
and
then
it
opens
a
connection
for
debugging,
so
you're
in
vs
code
you
initialize
your
project
and
then
you
can
start
debugging
in
the
cloud
right
away
and
your
code
can
leverage
a
series
of
services
that
that
are
already
set
up
in
Azure
and
there's
an
ingress
controller
in
there.
Also
that
can
create
URLs
yeah.
A
So
so
let
me,
let
me
show
you
what
it
looks
like
so
I'm
here
in
I'm
here
in
there.
Let
me
first
so
here
in
order
to
play
with
kubernetes
I
always
use
docker
desktop,
so
I
have
my
local
kubernetes
cluster,
which
is
still
starting
and
then
here
in
darker,
desktop
I
can
switch
context
and
here
I'm,
going
to
use
a
pat
IKS
cluster,
which
is
a
cluster
in
Asscher.
A
That's
managed
by
IKS
that
I
have
created
and
so
I
check
that
my
context
is
right,
I'm
just
going
to
clear
that
out
and
so
I'm
just
going
to
do
a
coupe
card
or
get
nose
to
show
you
that
this
is
not
the
one.
On
my
laptop,
it's
the
one
in
IKS
that
I'm
connected
to
I
opened
it
I
created
it
65
days
ago.
A
I
hope
I
won't
have
any
problem
with
accounting,
because
I
should
delete
my
cluster
more
often
so
then
I
do
a
coop
cattle
get
namespaces
and
you
will
see
that
I
have
installed
assured
that
spaces
in
my
cluster.
So
there's
one
instruction
with
the
Azure
command
line
to
do
that
once
I've
done
that
it
creates
this
ACDs
namespace
and
when
I
do
good
card
or
get
all
an
easy.
Yes.
So
when
I
look
at
what's
inside
of
that
namespace
you
will
see.
A
A
So
once
I've
done
that
I
can
start
working
on
my
project,
so
I'm
just
going
to
do
a
code
in
GDS
node
web
front-end.
So
that's
a
simple,
that's
a
very
simple
node.js
application.
Just
to
show
you
what
the
experience
looks
like
as
a
developer
and
so
in
there
I
don't
have
much
I
just
have
like
a
node
project
package
of
JSON
and
some
CSS
and
JavaScript.
So
it's
an
index.html
page,
so
pretty
simple
application.
I
don't
have
much
and
I'm
a
web
developer.
I,
don't
know
anything
about
kubernetes,
but
I
want
to
start.
A
It
asked
me
whether
I
want
to
have
a
public
endpoint
for
my
application,
so
in
this
case
I'm
going
to
click
yes,
but
if
it's
a
really
secret
application,
I
could
say
no,
and
you
can
see
what's
happening
there
is
that
here,
I
have
a
darker
file
that
appears
no
I
haven't
installed
the
extension
yet
so
I
have
a
docker
file
that
appears
some
configuration
for
Azure
dev
spaces.
That
I
could
modify
and
then
a
hand
short
and
in
here
could
I
have
a
launch
configuration
which
means
that
I
can
start
debugging.
A
My
application
right
away
with
that
launch
configuration
so
I,
don't
need
to
setup
anything
and
if
I
go
in
a
debug
mode
there
you
can
see
I
have
a
launch
server
on
a
DDS
and
if
I
click
there,
you
can
see
it's
launching
something.
It's
executing
a
DDS
up
with
some
port
mapping
and
what
this
sgds
up
command-line
is
going
to
do.
Is
it's
going
to
connect
to
assure
to
the
to
my
aks
cluster
to
the
controller
ACDs
controller
on
the
other
side,
and
it's
going
to
push
the
code
over
there
or
sync.
A
Okay,
so
so
I
think
this
is
ready
and
if
I
go,
if
I
go
in
the
in
the
files,
if
I
go
in
server
server,
the
GS
in
there
I
can
put
put
a
breakpoint
in
there
and
when
I
go
in
my
terminal,
it
tells
me
that
it's
available
at
a
public
endpoint.
So
if
I
go
at
that
public
endpoint
I
can
give
that
to
some
of
my
colleagues
and
here
I'm
hitting
the
azure,
the
azure
load
balancer.
A
That
goes
inside
of
my
kubernetes
cluster,
via
the
ingress
controller
to
that
URL
and
inside
of
it
I
end
up
into
my
application
in
debug
mode,
and
so
here
I
can.
If
I
go
in
the
debug
view,
I
can
see
on
my
local
variables
and
I
could
modify
this.
For
example,
I
could
say:
oh
now,
actually
actually
I
need
to
modify
it
there.
So
I
should
have
created
a
variable,
but
basically
I
can
stop
debugging
my
app
there
and
when
I
say
continue,
it's
saying
hello
from
what
phone
and
over
there.
A
So
so
that's
debugging
with
EDS
the
the
other
experience
I
wanted
to
show
you.
So
yes,
in
addition
to
that,
has
has
a
few
sorry
in
addition
to
that,
has
a
few
interesting
features
where,
with
the
URL
that
it
creates
for
you,
you
can
create
different
branches
so
that
developers,
one
developer,
can
have
their
own
version
of
a
certain
part
of
a
multi-service
app
running
at
a
certain
URL.
Well,
the
rest
of
the
developers
in
the
team
can
use
the
same
other
set
of
services.
A
So
it's
really
for
teams
to
collaborate
together
on
applications
that
use
lots
of
services
in
common
now.
There's
another
developer
experience!
That's
really
cool
that
I
wanted
to
show
you,
which
is
called
life
share,
so
vs
code
life
share.
Lets
you
collaborate
with
someone
who
has
vs
code
on
their
machine,
and
you
can
hear
I'm
able
to
give
access
to
the
code
on
my
machine
terminal
and
a
host
on
my
machine
to
Scott
here.
A
Who
has
nothing
from
this
application
without
having
him
to
install
anything,
and
the
beauty
of
it
is
that
live
share
works
really
well
with
a
GDS
with
a
dev
spaces,
which
means
that
he'll
be
able
from
his
machine
to
debug
the
application
that
we
saw
in
my
kubernetes
cluster
without
having
access
to
it.
Just
who
live
share
so
we're
at
45.
A
Maybe
I'll
just
skip
that
demo,
because
I
think
it's
pretty
long.
I'll
I'll
add
to
the
slide
a
link
that
I
gave
that
demo
a
docker
con,
and
so
you
can
watch
that
that
demo
there,
because
it
takes
at
least
five
minutes,
and
we
have
just
20
minutes
more
and
and
there's
more
stuff.
I
wanted
to
show
you,
but
just
just
you
know
that
both
are
working
together
and
then
the
third
experience
I
wanted
to
show.
You
is
vs
code,
remote
extension
for
containers.
So
that's
something
that
came
out
very
recently.
A
It's
an
open
source
extension
for
yes
code
and
what
it's
doing
is
that
it
lets.
You
create
some
configuration
in
the
for
your
vs
code
project
so
that
vs
code
is
split
into
two
parts:
the
local
part
that
has
the
themes
and
the
UI
all
the
extensions,
and
then
it
can
run
the
server
part
of
vs
code
with
its
own
set
of
extensions
inside
of
a
docker
container,
which
means
that,
and
so
you
can
use
that
with
your
local
docker
engine.
A
And
so
what
that
means
is
that
in
your
github
project,
if
you
set
up
that
configure
that
vs
code
configuration
with
a
docker
file
for
your
project,
every
developer,
who
is
going
to
join
their
your
team
when
they're
doing
a
gig
check
out
or
get
clone
of
the
project
they
can
launch
in
debug
mode
in
in
vs
code
right
away,
and
all
of
them
will
have
a
similar
experience.
They
don't
need
to
have
any
runtime
installed
on
their
machine.
They
use
docker
and
that
code
is
mounted
inside
of
inside
of
the
docker
container.
A
And
so
you
can
customize
all
these
containers
and
I'm
just
going
to
show
you
what
that
looks
like,
so
that
that
Jesus
could
remote
extension.
That's
something
that
that
was
announced.
I
think
a
month
and
a
half
ago,
so
it's
six
weeks,
six
weeks
old,
it
came
out
in
the
regular
version
of
es
code
two
weeks
ago
and
in
addition
to
the
current,
can
do
also
SSH
and
wsl
if
you're
on
Windows.
A
So
behind
the
scenes
it's
taking
the
docker
file
that
I
have
in
my
project
it's
building
a
docker
image
with
it
and
then
it's
doing
your
docker
run
with
that
code
base
inside
of
that
docker
image
and
in
that
docker
image.
There's
a
vs
code,
server,
that's
running
so
that
and
plus
it
creates
a
launched.
A
JSON
with
a
debug
configuration
for
for
that
project,
which
means
I,
can
say,
I,
want
to
launch
that
program
and
is
going
to
like
launch
my.
A
This
is
a
node
application
again
and
then
I
can
ask
for
a
new
terminal
in
there
and
the
new
terminal
is
going
to
be
inside
of
the
container.
So
here
you
can
see.
I
have
BS
code
server
running
on
my
node
process
and
if
I
do
a
curl
of
local
host
on
port
3000,
so
I'm
I
hit
the
breakpoint
that
I
had
in
there
inside
of
my
code.
A
So
here,
I'm
debugging,
a
node.js
application
inside
of
a
container
and
I
didn't
have
anything
to
do
to
set
up
all
that
logistics,
so
I'm
just
going
to
say,
yeah
continue
and
yeah.
So
that
just
works.
So
that's
that's
a
remote
extension
in
terms
of
development,
there's
just
one
more
so
these
were
the
two.
The
two
experiences
I
wanted
to
show
you.
Let
me
go
to
to
the
right
to
the
right
slide.
A
Yeah,
in
addition
to
that,
when
you
want
to
debug
either
functions
or
containers
in
a
kubernetes
cluster,
there
are
a
bunch
of
other
projects
you
can
take.
A
look
at
squash
is
one
from
the
blue
team,
thus
telepresence,
which
is
a
gif
project,
thus
casing
and
tilt,
which
is
pretty
recent
I,
have
if
you're
looking
for
my
slide
for
Doc
Ock
on
I
have
a
bunch
of
explanation
about
how
to
use
all
of
them.
So
that
covers
the
developer
experience
now,
Scott
is
going
to
talk
about
application
packages
packaging.
A
A
B
Myself,
I'm
not
really
much
of
an
application,
developer,
I'm
more
of
an
ops,
ops,
e-types
person,
so
I'm
going
to
show
you
scene
up,
which
is
an
open
specification
from
both
Microsoft
and
docker,
and
also
I
believe
how
she
clapping,
bitNami
and
now
I'm
working
with
it
and
what
it
actually
does
is
as
an
obstruction
over
tools
that
you
already
have.
So
these
tools
could
be
home.
B
These
tools
could
be
ansible,
these
source
could
be
Papa,
it
could
be
anything
and
basically
what
it
does
is
give
you
a
framework
to
be
able
to
deploy
these
applications
and
code
that
you
already
have
in
an
obstructive
way.
This
allows
you
to
have
your
deployment
pipeline
really
really
slim
down,
so
instead
of
having
multiple,
binaries
or
multiple
things
like
that,
you
can
have
just
a
single
way
to
deploy
things.
The
best
thing
about
Cena
is
the
invocation.
Image
is
a
container,
so
you
don't
need
any
binaries.
B
Microsoft
has
a
has
a
implementation
of
Cena
called
portal,
and
what
this
actually
gives
you
and
why
you
would
want
to
use
porter
is
we
have
built
things
called
mix-ins
and
what
mix-ins
are
is
the
smarts
to
talk
to
a
cloud
native
API?
So
if
you
wanted
to
play
the
coupie
needies,
you
don't
need
to
know
anything
about
kubernetes,
except
the
deployment
mechanism
that
you
want.
The
mixin
will
look
after
the
smarts
I'm
talking
to
the
kubernetes
api,
for
you
same
with
the
juror
same
with
terraform
and
also
helm.
B
So
if
you've
already
got
helm
charts
and
you
wanted
to
play
them
and
pass
different
variables,
three
different
animals,
because
you
can
do
that
with
Porter,
then
that
you
don't
need
to
know
anything
about
how
there's
a
hound
mix
in
there
for
you.
So
basically,
you
just
put
the
variables
that
you
want
into
into
the
code
and
away
you
go.
So
it's
actually
really
really
simple
and
the
good
thing
about
see.
Now,
whether
you
use
our
implementation
or
you
use
docker
apps,
which
is
it's
implementation,
it's
not
trying
to
replace
any
tools
that
you've
got.
B
It's
actually
working
with
the
tools
you've
got
and
if
you
build
a
scene
out
correctly,
you
should
be
able
to
use
docker
up
all
border.
They
should
be
totally
interchangeable.
The
other
good
thing
about
seeing
our
bundles
is
there's
work
going
on
in
the
OCI
at
the
moment
to
allow
bundles
to
be
pushed
to
the
OCI
registry.
So
what
this
means
is
you
can
actually
push
your
scene
out
bundles
up
with
your
images
and
the
application.
B
If
you
go
to
a
node
autoscaler
again,
it's
going
to
be
like
two
minutes
before
the
kubernetes
node
is
ready,
at
least,
if
not
more
so,
a
project
was
started
inside
Microsoft
daenerys
in
CNC,
F,
Codd,
virtual
Kubler,
and
what
that
allows
you
to
do
is
interface
to
container
runtime
and
make
it
look
like
it's
a
node,
that's
in
the
cloud.
So
if
your
honor's,
your
that
will
be
a
CI
if
you're
on
Alibaba
Cloud
I,
believe
it's
a
Fiat,
but
there's
there's
a
lots
out
there
if
you're
an
AWS
that
would
be
far
gate.
B
So
what
this
allows
you
to
do
is
actually
scale
your
pods
across
vertically,
without
having
the
wait
for
a
node
to
spin
up
so
it'll
hit
the
ACI
API
and
it
will
spin
up
a
pod
straightaway
for
you
and
when
you're
doing
a
highly
transactional
sort
of
workload.
This
can
save
you
time
and
also
could
save
you
money.
B
Virtual
couplet
doesn't
give
you
a
full
full,
a
full
node,
but
it
does
give
you
enough
that
you
can
get
away
with
a
whole
a
whole
heap
of
stuff.
So
you
can
see
all
the
different
stuff
there,
so
you
get
all
the
normal
get
blood
stuff
and
virtual
people
at
the
open-source
implementation.
There
is
some
limitation
networking
coming
back
into
the
cluster
and
bits
and
pieces
like
that.
B
If
you
use
the
the
implementation
in
honors
Europe,
we
call
it
virtual
nude
and
we'll
set
up
the
center
I
provider
and
we'll
set
up
a
whole
heap
of
networking
to
speak
back
to
your
cluster.
So
if
there's
any
resources
in
your
cluster
that
you
need
to
speak
back
to
you'll
be
able
to
do
that,
Alibaba
cloud
has
taken
it
one
step
further
and
they've
got
Project
Lead
Viking,
which
looks
after
DNS
resolution
across
there
they're
clouds.
At
the
moment
we
do
IP
across
on
the
CNI.
B
B
But
we
need
something
to
look
after
the
scaling,
and
this
is
where
cater
comes
in.
So
when,
when
HTTP
request
comes
in
through
kubernetes,
what
we
want
to
do
is
actually
scale
it
and
we
want
to
scale
it
to
virtual
node.
But
we
need
something
to
look
after
that
and
look
at
the
metrics
coming
into
the
cluster
and
then
scale
it
across
to
the
appropriate
place
with
which
is
virtual
node
for
us
or
virtual
Kubler.
So
Cairo
looks
after
that.
So
Kenna
can
work
with
a
whole
heap
of
technologies
to
look
at
metrics.
B
That's
a
habit,
it's
from
Deus
labs
and
it's
got
a
serious
and
what
a
Cirrus
does
is
allows
a
zero
scale
effect
on
a
pod,
because
on
kubernetes,
if
you
scale
the
pod
to
zero
and
you
have
a
service
endpoint,
once
traffic
goes
there
like
it
gets
lost
and
there's
a
whole
issue.
There.
Osiris
is
another
event
component
that
sits.
Aron
allows
the
service
to
have
no
pods
beneath
belief
it
and
then
once
it
needs
the
pods
of
edibles
can't
scale
them
up.
B
So
this
is
what
cattle
looks
like.
If
you
see
there,
the
external
trigger
Schloss
scaling
pods,
you
got
the
Cooper
Nettie's
a
TD
store.
There.
You've
got
the
controller
and
all
the
parts
of
QP
Nene's
and
the
horizontal
pod
auto
spell
it.
So
you
can
see
there
it's
looking
after,
so
the
Keller
doesn't
actually
replace
our
horizontal
pod
autoscaler.
It
actually
works
with
it.
B
So
what
we're
going
to
do
now
is
just
run
a
demo.
Just
it
takes
a
minute,
and
so
basically,
what
we're
going
to
do
is
we're
gonna
use
pod
up
and
we're
going
to
install
rabbitmq
via
home,
then
we're
gonna.
Do
a
deployment
and
I'll
go
through
deployments
and
we're
gonna
install
a
publisher
in
a
consumer
and
we're
going
to
scale
it
all
on
virtual
note,
right
now
with
a
single
command,
so
we
just
go
port
are
well.
B
B
So,
as
you
can
see
there,
it's
insulin,
camera
cat
I
had
a
demo
now
I'm
gonna
come
back
to
this
because
it
takes
a
minute
for
a
RabbitMQ
to
get
up
start
up.
But,
as
you
can
see
now,
it's
already
invoking
helm
so
just
with
a
single
single
command
of
it
invoked
helm
and
I'm
gonna
do
some
coop
entities
deployment.
So
let's
have
a
look
at
what
those
deployments
are
and
we'll
come
back
and
look
at
the
horizontal
port
autoscaler.
B
Oh,
and
so,
as
you
can
see
with
that,
with
that
si
nab
bundle,
what
we've
done
is
we've
installed
RabbitMQ
and
then
what
we're
going
to
do
is
we're
going
to
do
a
deployment
and
it's
just
a
sample
deployment
and
but
the
you'll
notice
down
the
bottom
here.
What
we're
gonna
do
is
we're.
Gonna
say
this
deployment
right
here
has
a
no
toleration,
only
the
run
on
virtual
couplet,
so
that's
not
gonna
run
on
a
normal.
On
a
normal
note,
it's
only
in
the
scale
onto
virtual
couplet.
B
B
Then
we
look
at
what
we're
going
to
do
is
we're
going
to
use
a
custom
resource
definition
that
Kenny
uses
just
to
have
a
scaled
object,
and
this
will
look
and
see
the
pollen
interview
intervals
and
everything
that
needs
to
happen
within
the
RabbitMQ
stack
and
then
we're
just
going
to
run
the
batch
job,
which
is
the
publish.
So
we
can
see,
we
can
see
things
start
to
scale
off,
and
so,
as
you
can
see
there,
that
was
a
whole
lot
of
stuff
I
just
to
play
with
a
single
command.
B
So
it
like
seen
up
it's
pretty
awesome.
So
let's
go
back
so
rabbit
infused
wasn't
started.
So
what
I'll
do
is
just
go
to
my
other
terminals.
So,
as
you
can
see
here,
we've
just
got
a
zero
I'm.
A
cast
Buster
but
you'll
see
that
there's
an
extra
node
there.
That
looks
a
little
bit
different,
so
you
can
see
there
that
I've
got
a
virtual
node
running
and
my
plus
is
running
114,
which
is
the
latest
that
we
can
run
on
a
draw
and
the
virtual
and
the
virtual
cube,
let's
run
in
there.
B
So
the
virtual
people
it's
acting
like
a
single
node,
but
what
it's
actually
doing
is
is
talking
to
the
a
CI
API
and
what
it's
getting
back.
It's
returning
into
like
calls
that
communities
knows
natively
that
a
node
has
so
let's
go
back
and
hope
that
so
a
virtual
ability,
so
we've
just
deploy,
as
you
can
see,
they're
RabbitMQ
now
we're
deploying
the
consumer.
So
if
we
go
over.
B
Killed
up
puts
up
a
loop,
so
that's
going
to
get
the
horizontal
product
autoscaler
and
if
you
have
here
so
what
we
can
see
here
is
you
can
see
a
whole
heap
of
pods
terminating,
that's
okay,
because
they
were
actually
running
surplus
functions,
but
you
can
see
there
on
the
node
that
it's
actually
only
to
play
non-virtual
couplet.
So
none
of
these
none
of
the
scaling
event
that
Patrick
needed
is
actually
happening
on
my
aks
cluster,
so
performance
of
all
the
other
applications
I've
got
running.
B
There
is
actually
nothing
because
I'm
offending
all
this
load
is
actual
load.
That's
just
happened
into
virtual
crew
blood,
which
is
awesome,
and
then,
if
I
go
back
to
my
scaling,
you
can
see
now
that
I'm
starting
to
get
a
scaling
events
happen.
So
you
can
see
I
had
a
zero
replica
of
the
consumer
and
that's
because
I
had
no
traffic
and
as
weird
son
into
the
pods,
you
can
see
the
rappers
replicas
are
going
up
depending
on
the
Chaffee.
So
before
I
had
HDB's
scale
to
0-0.
B
B
So
let's
go
back
to
the
slides
and
the
good
thing
about
this
particular
demo
as
well
is
I've
opened
sourced
it.
If
you
want
the
code-
and
you
want
to
run
this
yourself
there-
it
is,
although
it's
all
there,
it's
all
in
C
now,
all
you
need
is
a
juror
account,
because
it
does
need
virtual
node.
If
you
know
virtual
people
it
enough,
and
you
can
get
virtual
people
at
working
on
another
cloud
provider,
it
just
take
the
C
it
and
that
yeah
just
think
the
C.
B
Now
bundles
and
you'll
be
able
to
deploy
them
there
and
then
there's
all
these
other
things.
That
Patrick
spoke
about,
that's
where
they
come,
and
that's
all
where
you
can
get
all
the
different
things
and,
of
course
down
the
bottom.
If
you
want
to
work
for
Microsoft,
especially
in
China,
we're
looking
for
cloud
developer,
advocates
the
drain
mine
and
Patrick
steam.
So,
if
you're
looking
for
a
new
job,
you
love
containers
and
you're
in
China,
come
and
see
us
after
the
talk
any
questions.