►
Description
Scaling Node.js Applications with Kubernetes and Docker - Erick Wendel, EW.IT
Speakers: Erick Wendel
Node.js and Microservices are a beautiful combination and a common reality of many developers. When we talk about Microservices, we need to consider many concepts such as release management, monitoring, and scale. Thus, could be good for some people and a terrible experience for others. Attendees will learn how Node.js, containers, and Kubernetes working together could help them to be more productive, scaling applications by configuration files without worries to deliver new features and make changes. On this talk using a production environment scenario as an example, attendees will learn the Kubernetes' basic components, tips to scale applications and useful Kubernetes configurations.
A
A
I'm
gonna
talk
about
Cuban,
et's
and
darker
and
a
lot
of
good
stuffs,
but
here
I'm
not
just
I'm,
not
selling
any
technology
I'm
just
showing
some
experiencing
that
I
viewing
and
something
that
I've
creating
at
home
or
at
my
job,
so
I
work
as
a
trainer
and
software
iPad
in
Brazil
work
with
financial
companies
and
a
lot
of
stuffs.
So,
first
of
all
who
here
has
work
it
with
docker
there's
a
lot
of
people
and
working
with
docker
swarm
in
production.
A
I'll
tell
is
not
so
much
okay
in
with
kubernetes,
oh,
oh,
that
is
amazing.
Okay,
so
this
talk
is
focused
on
real
scenarios.
We
will
talk
a
lot
about
a
lot
of
things
about
kubernetes
and
how
to
scale
applications.
We
will
talk
a
little
bit
about
no
chew
because
their
context,
but
with
these
chips
you
can
using
any
application.
In
any
scenario,
just
making
this
some
configuration.
I
will
show
also
some
tools
to
improve
your
courage,
coaster.
We
our
courage,
cluster
and
help
your
application.
A
Ok,
we
are
here
because
nodes
so
node.
We
know
that's
not
scales,
no,
they
are
using.
In
everywhere
we
can
use
a
Raspberry
Pi
on
servers
and
everywhere
and
when
we
we
think
about
no
do
you
think
node.
That
is
incredible.
We
can
use
everywhere
yeah.
What
do
we
know?
That's
scaling
the
application
scales
where
we
know
that
the
word
scale.
Sometimes
this
is
confusing
it's
taking
applications,
not
that
simple.
We
should
think
a
little
bit
more.
What
this
is
scaling
I
will
show
my
opinion.
A
All
of
this
is
based
on
my
experience
and
if
you
use
the
degree,
we
can
talk
a
little
bit
more
later.
Scaling
for
me
is
when
you
have
your
chaos
or
you
have
your
application
running
and
you
should
deploy
new
applications.
You
should
deploy
new
versions
and
you
should
understand
the
monitor
all
of
your
application.
It's
not
just
about
copies
here.
You
have
a
lot
of
customers,
a
lot
of
consumers
and
we
should
understand
what
our
application
is
doing
or
not.
So
it's
not
just
copies.
A
We
will
talk
a
little
bit
more
in
how
this
could
run,
and
here
we
are
here
to
talk
about
Cuban,
Indies
and
Cuban.
A
disease
is
also
called
by
yay.
So
I
spent
a
lot
of
time
to
make
this
animation
so
yeah
I
searched
my
mom
won't
see
that
yeah.
This
is
amazing,
so
yeah
I
come
here.
It
is
that
this
Orchestrator
is
also
called
by
doctor
captain.
So
it's
just
managing
your
container
manage
your
applications
to
make
some
decisions
make
you
have
shacks
understand.
A
How
is
the
health
care
of
your
application
and
help
you
make
something
good
and,
in
my
opinion,
one
thing
that
is
good
that
broke
some
fight
is
that
they
put
soft
engineers
and
ser
used
to
work
together.
Now
the
developers
will
create
the
manifest
files.
They
are
sorry
we
work
together
to
monitor
to
create
the
DevOps
pipeline
and
all
of
them
is
working
in
peace
in
working
together.
Thank
you,
ladies.
In
my
opinion,
one
of
the
best
features
is
rolling
update,
so
it's
the
ability
that
we
can
run
our
Fidesz
on
cluster.
A
We
thought
worries
we
can
make
their
days
granary
and
update
just
a
few
pieces
of
our
applications
or
micro
services,
and
we
can
check
before
this
goes
to
production.
Just
before
the
customer
tries
to
access
here
have
the
scenario
so
I
have
a
lot
of
consumers.
They
are
accessing
my
cabinet,
it's
not
actually
accessing
directly
the
companies.
We
have
also
like
a
pay
gateway
or
something
that
is
a
later
layer
before
going
to
communities.
But
in
this
case
I
have
a
few
versions
of
my
epic
product.
A
You
know:
you'll
deliver
a
new
version,
so
I
have
the
product
on
which
you
so
I'm
appealing
this
this
application
and
the
cabinets
will
make
some
health
checks.
They
will
ping
in
your
application
to
see
if
this
is
safe
are
not
used.
So
here
I
just
finished
the
deploy
the
Cuban
is
to
establish
some
connections.
We
paint
in
your
your
route.
They
say:
okay,
I'm
ready
to
receive
requests
when
I'm
ready
to
receive
requests.
The
kubernetes
we
redirect
our
of
nearing
comes,
choose
these
new
applications
and
then
we
just
remove
the
old
version.
A
Let's
think
about
another
scenario,
the
other
scenario
we
have
also
unemployment.
We
have
the
victory
right
now,
but
this
v3
is
not
safe.
Maybe
the
database
is
wrong
or
maybe
some
connections.
Some
third
part
objects--
is
not
working
and
then
it's
not
working
but
see
our
infrastructure
continues.
The
same.
The
companies
won't
redirect
other
incomes.
Should
this
wrong
application
and
just
kill
the
other
version.
So
our
our
if
a
structure
is
safe
and
it's
running
as
planed
I'm
gonna
talk
about
the
companies
so
companies.
A
When
you
look
at
the
documentation,
we
have
a
lot
of
lists,
a
lot
of
concepts,
a
lot
of
topics
to
understand,
but
here
I
brought
something
that
to
you.
Maybe
you
usually
do
in
your
home
or
when
you
think
you
moved
your
company's.
You
should
use
these
components.
So
first
I
will
talk
about
pots.
Pots
is
the
smallest
unit
of
your
code.
We
can
have
more
than
one
application
is
in
in
each
pod,
but
it's
not
recombinant.
It's
not
recommended
you
can
use
only
you
can
put
your
application
right
there,
your
docker
image.
A
You
can
have
your
database
as
well,
but
they
are
not
smart,
so
they
they
need
someone
to
control
them.
So
we're
gonna
talk
now
about
the
planet
so
deploy
MIT.
We
specify
how
many
happy
cuz,
how
many
copies
we
will
have
of
this
project.
What
is
the
limit?
How
many
memory
or
CPU
your
application
would
use
or
versions
so
I
can
deploy
a
version
1
and
version
2
at
the
same
time,
but
I
can
expose
this
data
for
a
different
way
and
how
I
will
be
date,
this
project
or
how
I
will
share
an
exposure.
A
My
cuz,
my
consumer
for
database
we
usually
use
stateful
set,
whereas
deployment
files
is
stateless,
a
stageful
set
could
just
persist,
data
storage.
We
can
use
unique
netfile
network
to
the
fires
and
we
can
make
everything
you
order.
We
can.
We
have
like
graceful
deletions.
I,
don't
remember
that
the
word,
but
we
can
delete
our
Bing
stays
is
in
order
as
well,
so
is
so
much
powerful
to
database.
Just
something
that
we
you
want
you
star
data.
Okay,
we
have
deployment
and
we
have
stateful
sets,
and
now
we
want
to
expose.
A
We
want
to
establish
a
connection
through
your
infrastructure,
and
here
we
have
the
service,
so
the
service
at
the
goal
is
to
expose
your
systems
to
the
world.
It
is
also
a
load
balancer
if
you
configure,
but
here
I'm,
exposing
only
the
pod.
Only
the
application
on
version,
one
I
will
only
make
a
load.
Balancer
I
have
all
the
other
types
of
services
to
inside
the
cabinets.
Cluster
I
can
say:
oh
this
application
is
running
on
per
on
port
3000,
so
will
expose
on
this
port.
A
You
know
you
can
have
like
an
alias
when
I
call
this
name.
They
will
redirect
to
the
client
voice.
Stateful
set
is
the
same
idea,
is
the
same
target
same
labels.
It
doesn't
change
so
much,
but
when
my
application
tries
to
access
a
stateful
set
the
database,
it
has
to
access
the
servers
and
the
search
will
route
you
for
the
current
instance.
So
if
you
want
more
replicas
or
more
instances
of
the
database,
you
just
put
there
in
the
search.
We
understand
what
they
have
to
do,
and
this
is
amazing.
A
Ok,
we
have
services,
we
have
deployment
and
all
of
them
are
running
inside
a
node,
so
the
node
is
just
the
VM
properly
and
the
VM
we
have
the
networking.
The
networking
is,
the
port
forwarding.
Understanding
inside
the
the
cluster
is
how
they
understand
in
the
responsible,
Forest
Service
communicate
itself.
We
have
the
cubelet
the
cubelets,
they
analyze
the
manifest
file
to
see
if
our
your
applications
running
as
planned,
like
limits
copies
or
everything
that
you
make
it
on
your
manifest
file,
the
cube,
let
me
run-
and
we
have
also
they
contain
the
runtime.
A
We
we
are
talking
about
soccer,
but
we
have
other
container
runtimes
as
well
that
you
can
run
inside
the
community
as
well.
Okay,
we
have
nodes
that
is
all
VMs
connected
and
we
have
the
master,
so
the
master
will
choose
and
we
make
some
decisions
about
your
cluster.
So
we
have
the
coaster
star
that
we
manage
and
start
all
information
about
the
cluster.
We
have
this
scheduler
when
we
have
a
new
pod.
A
We
have
to
choose,
send
this
new
pod
show
and
our
mood
and
understand
what
is
going
on
or
if
your
node
is
right
or
not
you
receive.
We
have
a
few
controllers
as
well.
We
have
no
controllers,
you
know
if
the
node
is
safe.
We
have
replication
controller
to
see
if
the
copies
in
the
amount
of
instance
is
correct,
it
will
have
also
the
API
server
that
we
use
is
a
front-end
that
we
use
to
perform
operations
on
the
control
plane
of
the
whole
kubernetes.
A
When
we
run
a
comment
on
the
communities
we
run
inside,
you
up
your
server,
but
now,
let's
see
how
the
master
or
how
is
the
behavior
of
kubernetes
compared
to
other
approach.
So
here
we
will
define
a
master
master,
manifest
config
file
that
would
be
Jason
or
Yama
file.
We
have
define
it
like.
We
have
a
desired
state.
My
desire
is
string
stances.
Okay,
I
will
run
tree
instance,
so
I
have
two
in
canada
and
I
have
one
in
brazil.
A
Okay,
my
current
state
is
exactly
the
same
than
my
desired
state,
but
imagines
for
somehow
the
the
server
in
Brazil
is
not
responding,
so
the
cabinets
will
make
some
checking
in
will
schedule
and
new
a
new
stage
to
other
node.
We
make
some
check-ins
and
now
the
node
in
Canada
we
receive
the
missing
part
and
I
will
have
this
idea
in
the
same.
Go
okay,
when
use
cabinets,
we
know,
that's,
nothing
is
bulletproof.
We
know
that
sometimes
using
just
docker
compose
or
just
using
our
properly
VM
itself
would
help.
A
And
now,
let's
talk
about,
why
it's
good,
so
my
opinion,
zero
downtime
a
few
days
when
you
can
test
when
you
can
check
your
application
before
exposing
short
customers,
you
can
replace
and
we
can
put
a
new
instance
with
no
worries
yeah.
Actually,
here
our
consumer
is
not
knowing
what
is
going
on.
You
just
switch
our
code.
You
can
use
cannery
deployments
in
a
lot
of
micro
services,
front
steps.
A
We
can
use
much
Rodgers
clusters,
we
can
use
raspberry
pie,
we
can
use
Linux
servers,
we
can
use
ever
where
the
word
just
join
the
VM
on
the
clusters.
So
this
is
so
amazing,
and
this
is
something
that
you
should
think
about
your
application,
so
you
have
only
one
API.
Your
FBI
is
not.
You
are
not
deploying
every
time,
so
maybe
cabinet
is
not
so
good
for
you,
because
you
have
so
much
afford
to
create
infrastructure
and
you
are
not
using
all
of
the
benefits.
A
So
if
you
have
a
lot
of
api's
or
you
should
have
more
than
one
stands,
so
you
have
to
provide
24
hours.
Our
very
first
structure
may
be
kubernetes
will
help
you
more,
and
this
is
some
poetic,
no
vendor
looking.
But
when
you
go
to
some
cloud
platform,
when
you
go,
is
your
AWS,
google?
We
have
the
same
manifest
file,
but
sometimes
the
configuration
would
be
different.
This
is
when
you
use
the
manifest
file.
A
Is
the
same
language,
the
same
idea,
the
same
attributes,
but
when
we
talk
about
the
external
services
such
as
storage
or
other
thing,
that
we
you
must
use
on
a
specific
call,
this
would
be
different,
okay-y
cabinets.
Why
we,
we
are
actually
using
other
stuffs
here.
We
are
just
making
our
production
or
deployment
pipeline,
and
maybe
why
should
we
change
or
should
consider
using
the
so
how
many
of
you
using
dr.
Campos
in
production,
Oh,
dr.
Campos,
so
dr.
Campos,
is
amazing.
We
can
use
like
I've
been
using
you
with
pertain
er.
A
If
something
goes
wrong,
I
just
click
there.
We
start
in
everything's,
okay,
but
when
we
think
about
scale
with
dr.
Campos,
we
should
enter
and
make
everything
manually.
So
it's
not
is
not
so
smart
in
other
fruits.
So,
with
your
application
dies,
you
can
make
like
an
alert,
send
you
an
alert
and
you
go
there
in
replace
or
restart,
and
we
have
dr.
swarm.
So
dr.
Schwarz
is
the
same
idea
than
the
in
carbon
eighties.
The
the
dr.
A
swamp
is
so
similar
than
cover
it
is
as
well,
but
if
it
works
only
on
the
container
and
time
of
the
darker
and
if
you
want
support,
you
go
to
the
darker
Enterprise,
but
at
the
same
time
the
Copernicus
is
a
little
bit
more
powerful
technically
so,
which
provides
check.
Health
checking
provides
the
inside
the
pod
level.
A
So
we
can
use
scheduling,
scanning,
namespace
and
role
basis
access,
so
you
can
create,
like
manifest
file
should
say,
watches
application
we
run
inside
the
cabernet
knees
a
little
bit,
and
this
is
my
scenario
so
at
my
company
and
some
customers
they
are
actually
using
acs
or
ace
or
ECS
in
production.
What
is
the
difference
here?
The
difference
here
is:
you
have
now
the
dependency
of
the
third
party
in
like
acs,
you
are
dependent
of
AC
to
VM.
A
So
if
you
want
to
scale
more,
you
have
a
little
time
to
a
new
VM
and
configure
sometimes,
and
but
this
up,
but
all
of
this
you
should
use
AWS
or
Asia
or
Google
platform.
So
you
should
learn
more
about
the
specific
version
of
your
go.
So
go
back.
How
to
do
is
start.
This
gift
is
amazing
hacker,
so
this
is
amazing
got
a
hack.
How
do
we
start
so
we
can
start
from
a
lot
of
places.
First
of
all,
I
love
this
gift,
yeah
I'm,
the
bad
guy.
Oh
yeah.
A
We
can
start
with
cube
a
DM
going
to
own
pram
solutions.
You
can
install
on
your
VM.
You
can
install
on
Raspberry
Pi
arm
or
whatever
you
want,
but
you
have
to
configure
networking
monitoring
the
master
node
you
have
to
configure
all
of
them
by
yourself.
This
is
sometimes
a
little
bit
harder
than
going
through
another
approach.
You
can
go
to
a
cloud
solution.
A
So
this
is
so
much
straightforward,
then
configure
and
manage
it
didn't
know
the
master
node,
okay,
so
in
a
velop
you
can
use
min
cube
so
I'm,
using
here
mini
cube
with
virtual
box
and
I
can
run
out
of
the
configuration
manifest
files
that
are
used
in
production
in
my
machine.
Let's
just
ask
how
we
threw
a
ram
and
to
show
the
power
of
the
mini
cube
of
this
presentation
in
demos
were
were
run
using
them
in
queue
before
going
to
mini,
cube,
EDM
or
cloud
solution.
A
We
should
run
our
manifest
file,
so
our
mudfest
file
first
had
to
say
what
is
the
kind?
What
is
the
component
that
you
are
creating,
so
in
this
case
is
deployment.
Ok,
what
is
the
metadata?
So
how
do
you
create
this
this
component
and
then
how
many
copies?
How
many
replicas
do
you
have
and
you
can
see
you
can
show
selectors.
The
selector
is
powerful
for
something
that
you
have
already
on
air
is
running
and
you
want
to
replace
this
instance
or
you
want
to
update
this
instance.
Use
these
match
labels.
A
We
have
the
template
as
well,
so
how
the
application
will
actually
work
or
we
were
actually
created
inside
our
cluster.
We
can
put
the
image,
don't
secrets
when
you're
using
docker
registry
private
to
docker
registry,
and
we
put
actually
the
container
itself,
so
you
can
put
environment
variables,
storage
and
everything
inside
this
fire.
A
Okay,
I
will
run
first,
the
monk
DB,
because
my
requirement
is
to
use
MongoDB
I,
created
and
I
will
expose
this
monkey
be
using
this
UI,
so
I'm
sure
I
can
use
the
CLI
or
I
can
use
manifest
files,
but
just
for
example,
reasons:
I'm
creating
from
CLI
here
I'm
got
the
body
that
is
fine.
We
get
the
SVC,
that
is
the
Serbs
and
the
monkey
bees
right.
You
run
after
that.
The
among
the
bees
is
correctly
configured
I.
A
So
it
looks
like
nice,
so
I
just
created
one
file
and
I
run.
A
few
comments
in
my
application
is
on
there.
So
fast,
let's
talk
about
tooling,
so
we
have
a
lot
of
things
about
kubernetes
that
I
really
love.
One
of
them
is
we
everything
is
pluggable
is
the
plug-in
play.
You
just
apply
a
pro
you,
you
just
run
oopsy
to
apply
in
a
file,
and
then
we
can
see
the
result
of
the
plug-in
the
plugins
just
share
each
other
understanding
each
other.
We
have
Easter.
A
So
here
I'm
just
running
the
demo
I
just
copy/paste
from
the
website,
but
they
saw
a
lot
of
components
for
us
and
if
you
go
to
one
of
them
we
can
see
the
Prometheus
Prometheus
is
a
monitoring
to
that.
We
can
run
queries
and
see
some
metrics
from
the
your
community
service.
So
here
I
have
a
lot
of
metrics
and
a
lot
of
data
that
comes
from
the
kubernetes
and
here
I
will
just
make
the
same
so
I'm
redirecting
the
request
from
my
iPod
chew.
A
My
my
machine
and
I
will
go
to
Griffin,
so
graph
wanna
is
the
data
visualization.
So
here
is
the
demo
from
the
GAR
phone
as
well,
so
you
can
get
informations
for
your
disk
memory,
create
alerts
and
install,
but
this
is
so
much
powerful
and
I
just
run
a
comment
and
then
I
have
everything
hands.
So
this
is
so
powerful.
We
have
elm,
so
the
helm
is
a
package
manager
is
our
NPM
for
children
eighties.
So
you
can
create
a
lot
of
stuffs
a
lot
of
packages
and
we
can
use.
A
Actually
this
is
stuff,
so
here
I
will
try
to
find
the
Reds.
Actually,
the
production
Reds
that
is
configured
with
cluster
is
if
configured,
if
everything
that
we
want
sure
any
production
and
then
I
will
install
these
Reds
I
will
install.
They
will
show
a
lot
of
suggestions
to
test
if
my
Redis
is
working
or
not
in
here,
I
have
the
password
and
everything.
That's
just
I
will
copy
paste
just
just
to
see
if
he's
working
or
not
and
then
I
enter
in
my
Radice
and
I,
just
pink.
The
safest
message
is
okay.
A
So,
with
three
comments:
I
have
everything
prepared
to
production,
so
if
I
just
try
to
create
the
Reds
from
myself,
I
have
five
or
six
files
to
configure
to
create
roles
and
to
create
passwords
for
everywhere.
So
it's
not
so
easy
to
make
it
enhance,
and
here
we
can
create
them
bullets.
So
with
templates
how
we
open
just
on
vs
code
and
we
have
the
template,
so
you
can
create
like
dynamic
files
and
you
can
change
these
files.
Just
changing
our
little
code.
A
So
here
I
have
all
of
the
dynamic
part
of
that
I
can
reuse
through
the
applications
and
I
have
here
the
serves
dynamic
as
well.
So
I
can
change
only
a
few
variables
and
when
I
go
to
I,
just
put
the
value
that
I
really
want.
Imagine
that
you
have
the
same
service
in
three
different
environment.
You
just
change
with
the
values
and
you
have
the
same
environment
working
everywhere.
The
same
actually
is
the
same
infrastructure
running
in
different
environments
with
different
values.
A
Okay,
we
are
here
to
talk
about
scaling,
nodejs
applications-
oh
I
love
that
yeah.
So
we
should
talk
about
what
is
the
scaling
so
scale
itself?
What
does
it
means
so
in
scale?
This
is
my
opinion.
Scale
again
is
something
that
you
can
control
the
chaos
you
can
control.
All
of
your
copies.
You
can
read
directly
your
requests
when
you
need,
so
if
you
need
more
instance,
if
you
need
to
update
any
time
this,
you
are
scaling
your
application.
If
you
are
worried
to
make
a
deploy
like
on
midday,
sometimes
you
are
not
scared.
A
This
is
my
opinion.
Okay
and
talking
about
Cuban.
It
is
a
scale.
Your
application,
if
you
forgot
everything
here,
just
remember
that
part.
This
part.
We
have
some
useful
configuration
that
make
some
that
helps.
Cuba
needs
to
to
run
your
coaster,
so
you
have
live
in
this
in
redness
probe,
who
never
know
about
living
in
sin
right.
Let's
probe,
okay,
Oh
liberties
around
this
probe,
so
Cuba
is
not
that
smart.
So
you
have
to
say:
oh
here
you
have
to
pink
this
URL
and
then,
if
you
respond
during
that
time,
then
is
okay.
A
Then
you
can
run
or
not.
Otherwise,
the
cabinet's
we
wait
like
10
seconds
5
seconds.
We
will
just
say:
oh
if
your
application
doesn't
crash
in
5
seconds,
maybe
it's
right,
but
sometimes
it's
not
it's
just
because
you
are
not
catching
the
exceptions.
So
here
we
have
a
lot
of
kochu,
but
let's
pay
attention
just
redness
and
live
in
this
pro,
so
there
Radley's,
you
say
to
the
closer:
oh,
are
you
ready
to
receive
requests?
Okay,
I'm
ready
to
receive
requests
so
how
many
times
I
have
to
wait
before
the
first
request?
A
Oh
I
will
choose
seconds
to
sack
to
establish
connections
in
stablish
like
third-party
connections
and
then,
if
this
first
request
we
spend
more
than
two
seconds
something
goes
round.
You
have
to
delete
this
instance
because
it's
trash,
so
we
work
a
new
stance
and
you
see
the
result.
The
living
has
promised
something
similar,
but
the
difference
is
the
kubernetes
is
making
a
lot
of
house
shakings
in
your
cluster
to
understand
if
it's
still
running
or
not
so
we
have.
A
Here
are
your
life
in
2
seconds
3
seconds,
and
here
we
have
how
many
times
I
will
wait
for
the
first
request
just
seconds:
ok,
ok,
I
will
have
the
timeout
seconds
as
well.
Sometimes
you
have
a
problem
with
like
internment
intermittent
problems
and
you
really
don't
know
what's
going
on,
but
the
criminals
making
this
half
check.
This
is
the
linear
application
in
creating
again-
and
you
actually
don't
know
what's
going
on.
You
just
know,
because
you
see
how
many
restarts
or
have
many
new
rep,
because
you
have
and
we
have
the
pod
out
scalar.
A
A
So
if
my
application
reads
50
percent,
then
the
value
that
I
put
there
I
would
3
more
intense
for
more
instance
and
actually
does
it
works
super
fine,
and
this
is
something
that
you
could
use
on
Black
Friday,
so
you
are
receiving
a
lot
of
requests,
ok,
communities,
but
more
in
more
and
more
instances,
but
if
I
don't
want
more
instances,
just
kill
them
off
and
then
this
is
fine.
So
this
is
super
nice.
A
But
ok.
This
is
a
lot
of
information.
I
know
that's
a
lot
of
things
on
internet
and
a
lot
of
things
that
we
do
actually
on
daily
day.
But
let's
just
summarize
everything
in
your
mind,
so
darker
cabinets
is
just
someone
that
is
a
code
is
someone
that
we
replace
your
application
when
they
are
not
healthy,
making
strategy
or
appie
date
or
application.
When
you
need
you
can
do
yes,
you
can
make
strategies
to
a
traditional
version
to
test
a
new
version.
A
You
can
make
load
balancers
just
using
services
and
making
your
target
just
choosing
which
applications
the
best
for
your
customers
and
if
your
application
is
not
safe.
If
your
application
is
not
responding,
you
have
automated
robots,
so
you
can
use
everything
inside
the
kubernetes
with
no
words.
So
all
of
this
content
of
darker
things
and
a
lot
of
stuff
that
have
been
doing
it's
alright
on
my
website.