►
Description
Workshop: Cloud Native Development for Node.js Engineers - Luke Holmquist, Red Hat
As cloud services and deployment platforms have come to bear more and more responsibility for the “Enterprise” features of modern application development, Node.js becomes more appealing for enterprise engineers who want to take advantage of its light weight, quick startup time, developer productivity and overall happiness.
But cloud native development can seem daunting. How do you both write an app and also deal with automation, service discovery, observability, immutability, scalability and all of the other cloud native and practices?
It’s a lot to keep track of. It’s a lot to do. It’s scary!
But it doesn’t have to be. In this workshop you will learn how to develop and deploy Kubernetes managed Node.js applications. By the time we’re done, you will have created a Node.js application backed by Node.js microservices, and deployed it to a live Kubernetes cluster.
A
All
right,
I
suppose
we
could
get
started
as
a
speaker.
They
give
us
an
attendance
list,
so
we'll
probably
just
do
like
the
attendance
first.
If
you
guys
want
to
raise
your
hands,
if
you're
here
now
I'm
just
kidding,
that's
yeah,
we're
not
gonna.
Do
that
hi
everybody,
so
I'm,
Luke
Holmquist
that
were
for
Red
Hat
and
today
we're
gonna
be
talking
about
this
fun
topic
cloud.
Any
development
which
I'm
sure
you
may
have
gone
to
a
talk
that
today
or
maybe
possibly
tomorrow.
That
is
very
similar
because
I
saw
on
the
schedule.
A
That
was
very
a
lot
of
very
similar
things,
but
we'll
see
if
this
is
any
different
right.
So,
like
I,
said
I'm
a
engineer
at
Red,
Hat
Maya,
there's
my
twitter
handle,
if
you
want
to
follow
me,
also
a
huge
fish
fan.
So
if
anybody
is
also
a
huge
fish
fan
and
anybody
in
the
room
raise
of
hands,
nobody
awesome.
So
if
you
want
to
come
talk
to
me
later,
would
be
great
also.
This
episode.
This
picture
here
is
from
2009
and
I
realized
that
there's
that
whole
10-year
challenge
stupid
thing.
A
So
that's
from
that's
ten
years
ago,
and
this
is
what
I
look
like
now
in
2019,
so
there
you
go,
there's
the
challenge
completed
all
right,
so
yeah,
so
alright.
So
what
we
learned
says,
probably
some
some
ways
to
develop
and
deploy
cloud
native
applications,
super
Nettie's
or
slash
openshift.
It's
gonna
be
probably
the
platform
that
we're
gonna
use,
so
we're
gonna
need
for
this
workshop
and
it
is
only
an
hour
long.
A
So
we'll
try
to
go
quick
with
these
first
few
slides
that
I
have
that
kind
of
introduce
some
topic
or
some
concepts
and
then
the
second
half
of
it
will
just
be
like
in
the
actual
app
and
doing
some
things
so
right.
So
you'd
really
just
need
your
laptop
and
a
web
browser.
So
hopefully
everybody
has
a
web
browser
installed
on
their
laptop.
Hopefully
that
actually
has
JavaScript
enabled.
So
that
was
the
other.
That
was
the
other
thing
right,
so
right
so
first
survey.
So
who
is
sorry?
A
Did
you
not
have
a
web
browser
installed
that
we
were
like
yeah,
okay,
yeah
yeah?
So
anybody
here
writing
nodejs
applications.
I
mean
this
is
a
node
conference.
So
I
would
imagine,
I'd
see
a
bunch
of
hands
all
right
cool
anybody
using
containers
to
deploy
their
stuff.
All
right,
cool
have
fun
good
good
chunk
people
buddy
familiar
with
the
cube,
CTO
cube
cut',
oh
whatever
you
want
to
power,
you
ever
want
to
pronounce
it,
or
maybe
the
open
ship,
command-line
CLI
tools.
Anything
now.
A
That's
probably
why
you're
in
the
workshop
to
learn
a
little
bit
more
about
that
anybody
name,
a
handful
of
committees
objects,
no
yeah!
There
you
go
awesome,
any
anybody
can
name,
maybe
a
cloud
native
pattern
or
something
now
that
it's
probably
why
you're
here
to
find
out
also
who
do
I
have
for
anybody
from
your
up
here
anyway,
travel
from
Europe,
North,
America,
East,
Coast,
West,
Coast,
South,
America,
Asia,
okay,
cool
cool
Australia
I
was
gonna,
say
if
you
quote,
draw
from
that
impressive,
but
alright
anyway,
that's
enough
for
these
things
right.
A
So
some
cloud
native
patterns
that
were
you,
take
a
look
at
or
this
single
responsibility
pattern
which
I'm
sure
you've
heard
about
you
know
it's
like
do
one
thing:
do
it
well,
I'm,
just
kind
of
microservices?
Basically,
is
this
putting
things
into
containers
making
having
health
checks
for
your
app,
which
is
essentially
making
you
know,
checking
to
see
if
your
app
is
running
or
when,
if
it's
ready
to
run
and
we'll
see
examples
of
these
too
and
resilience
something
like
circuit
breaking.
A
So
what
is
kubernetes
I'm
sure
if
you
had
gone
to
one
of
the
talks
today,
that
is
about
chrome,
raised
you've
kind
of
already
learned
that
basically
it's
a
platform
for
container
organ
orchestration
and
a
lot
of
other
cool
buzzwords,
so
I'm
gonna
assume
that
you
guys
have
a
little
bit
of
info
on
what
Cooper
nase
is
so
just
to
kind
of
do
this
workshop
and
get
it
moving.
We'll
just
kind
of
keep
going
just
kind
of
I
just
wanted
to
kind
of.
A
Do
this
a
little
small
little
overview
of
some
of
these
concepts
right
for
coop
that
you
would
use
when
doing
you
know
Cabernets
deployments.
So
basically
you
have
this,
and
this
is
gonna
work
from
like
the
smallest
thing,
it's
gonna
go
kind
of
up
to
like
a
higher
level.
That's
kind
of
the
way
this
is
gonna
go.
A
So
a
container
is
the
smallest,
your
smallest
thing
you
have,
and
then
you
know
there's
these
container
images
that
you
combine
with
your
code
and
you
that's
actually
what
creates
the
container
and
then
those
containers
are
stored
in
an
imagery
in
image
registry
somewhere,
something
like
docker
hub.
If
you're
using
open
ship
open
ship
actually
has
its
own
internal
registry,
where
you
can
store
your
things
like
that,
maybe
Quay
I/o
or
something
else,
and
then
inside
the
image
straight
inside
the
registry.
A
So
what
an
appointment
is.
The
deployment
is
actually
just
the
descriptor
for
that
pod,
saying:
okay,
what
this
menu
replicas
I
want
this
much
CPU,
or
this
much
memory
or
whatever
something
I
forgot
to
mention:
I'm,
not
a
DevOps
person
at
all,
like
hate
it
if
yeah,
if
I
can
avoid
it,
I
will.
But
so
a
lot
of
this
stuff
is
gonna,
be
very
kind
of
more
of
a
high-level,
more
of
like
a
developer
focus
than
like,
like
oh,
we
need
to
boost
the
memory
for
this
and
make
it
had
this.
A
Have
this
many
CPUs
and
this
so
I'm?
Sorry,
if
that's
what
you're
looking
for
in
this
there's
more
there's,
actually
a
nice
for
jeaious
people
talk
tomorrow
morning
from
some
of
my
colleagues,
which
they
go,
earn
a
little
bit
more
depth
there.
So
if
you
want
to
check
that
out,
that's
it
9
o'clock
tomorrow,
quick
plug
right!
So
there's
this
other
concept
of
services.
This
is
essentially,
if
you
want
to
have
those
pods
and
those
deployments
accessible
physical
side,
then
you
put
a
service
on
top
of
that.
It's
kind
of
like
a
load
balancer.
A
So
if
you
have
multiple
pods
or
if
you
have
a
particular
container,
that
has
multiple
pods,
so
you
can
have
maybe
three
or
something
like
that.
The
service
will
connect
that
and
then
kind
of
low
balance
in
the
traffic
to
throughout
all
those,
and
it's
also
a
way
for
other
applications
that
you
might
have
in
your
cluster
to
talk
to
each
other
as
well
with
a
service.
And
then
this
is
something.
This
is
more
of
an
open
ship,
specific
thing
or
route.
A
And
then
we
have
a
namespace
and
that's
essentially
kind
of
like
the
grouping
of
kind
of
all
your
applications
or
all
your
services,
and
you
can
break
them
up
in
between.
You
know
a
bunch
of
different
ways
between
groups,
departments
and
they're,
all
kind
of
isolated
from
each
other
right.
So
we
talked
about
a
little
bit
of
a
kubernetes,
and
so
these
concepts
OpenShift,
is
basically
red-hats
implementation
of
kubernetes.
So
it's
if
you
wanted
to
run
just
doom
balloon
plain
kubernetes
on
openshift,
you
could
do
that
on
fish.
A
It
does
add
some
niceties
I'm,
not
gonna,
not
a
marketing
person,
so
I'm
not
gonna,
go
and
like
oh.
This
is
the
this
is
the
differences
and
stuff,
but
it
just
adds
some
things
on
top
of
it,
which
are
kind
of
nice
and
one
of
those
things
which
we
will
see
in
an
example
is
this
thing
called
source
to
image?
So
basically,
what
source
image
is?
Is
you
can
you
can
basically
take
your
code
and
take
a
specialized
docker
image
and
combine
them
together?
A
So
you
can
take
your
source
code,
though,
having
to
write
any
docker
files
or
anything
like
that
and
create
a
docker
image
and
a
resulting
image
that
you
then
you
could
then
deploy.
So,
if
you're
doing
on
that-
and
so
this
little
picture
here
actually
shows
kind
of
like
a
two-stage
one.
So
the
first
sort
of
top
part
is
kind
of
what
we're
talking
about
here.
A
Where
you
take
the
image
you
take
your
source
code,
this
build
happens
and
then
your
application
image
is
essentially
just
a
docker
image
there
right
so
and
then
within
an
open
ship.
There's
this
concept
of
the
build
and
we'll
see
that
in
a
minute,
alright,
so
I
kind
of
want
to
just
go
quick
through
that.
Ok,
good,
10
myths.
So
then
we
have
the
rest
of
the
the
kind
of
the
15
minutes
or
whatever
for
this
hour
to
kind
of
go
through
this.
A
So
if
anybody
everybody
wants
to
go
to
this
link,
this
will
open
up
an
ether
pad.
You
might
have
to
I'm,
not
sure
if
you're
gonna
have
to
say,
allow
the
it's
a
self-signed
certificate
on
here.
So
you
might
have
to
say
you
know
chromite
or
whatever
you're
using
might
freak
out,
so
you
might
just
have
to
allow
the
the
exception
and
I'm
gonna
actually
kind
of
switch
in
between
back
and
forth,
because
I
do
have
things
open.
A
B
A
So
yes,
so
when
you
and
when
you
go
when
you
do
go
into
that,
you're
gonna
see
all
these
users.
So
if
you
could
just
claim
one,
you
don't
put
your
name,
you
could
put
like
your
world
Warcraft
character,
name,
I,
don't
really
care
just
so
somebody
else
doesn't
use
it
and
we'll
use
that
and
you'll
use
that
username
with
the
password
of
openshift
I'm
coming
up
as
your
logins
for
things.
B
A
B
B
A
A
All
right,
I
guess
we'll
just
have
to
restart
the
thing
which
might
take
a
little
time
to
come
up,
but
maybe
we
can
just
they
can
just
go
through
the
slides
and
then,
if
it
does
come
up,
it
will
be
up
for
a
little
while
and
if
we
do
run
it
and
I'm
sure
we'll
run
out
of
time.
But
if
we
run
out
of
time
the
slide
should
be
somewhat
self-explanatory
and
then
like
this
should
be
up
once
we,
after
after
everything.
So
oh.
A
B
A
Okay
right,
so
what
you
were
supposed
to
do
there
was
go
to
this
etherpad
and
what
you're
gonna
do
is
when
this
all
the
stuff
comes
back
up,
we're
gonna
everybody's
gonna
kind
of
take
one
of
those
users.
These
are
one
through
whatever
it
is,
and
if
the
user,
one
or
user,
to
use
the
user,
whatever
user
number
is
OMA
ship
will
be
the
password
and
then
once
setup.
We're
actually
go
to
this
cool
terminal.
A
B
A
We're
gonna
kind
of
treat
a
new
project
and
that
kind
of
thing,
so
all
right,
let's
wait
a
few
minutes
for
that
thing,
so
you
guys
we
could
talk
about
something
else
while
we're
while
we're
waiting.
You
know
how
is
what
was
your
I
guess?
What
have
people
gone
to
already?
What's
your
favorite
talk,
that's
happened
other
than
this
one
right
now
as
and
did
anybody
like
anybody
from
New
York,
New
York
from
upstate?
A
A
A
This
okay
cool,
so
this
is
a
view
of
OpenShift
right
here,
all
these
things
or
pods
we,
which
we
heard
about
a
few
minutes
ago,
all
these
other
things
we'll
all
these
are
applications,
and
that
kind
of
thing
this
is
actually
our
terminal
app
that
we're
waiting
and
actually
it
is
running
these
little
circles.
You
know
that
when
they're
blue,
it
means
that
they're
they're
now
running
the
etherpad
thing,
which
is
here
it
says,
is
now
running
also.
So
if
we
go
back
to
the
etherpad,
let's
see
if
that
comes
up,
is
it
working?
A
Oh
all,
right
cool!
It
is
slow
yeah,
but
it's
working.
It
is
working
okay,
yeah
right,
so,
okay,
cool,
all
right,
I,
think
we're
back
in
business
here
which
yeah
awesome.
Okay.
So
when
that
comes
up
like
we
said
before,
we're
gonna
claim
the
username.
Everybody
claim
username.
That
comes
up
which
it
is
coming
up.
A
A
A
A
A
A
But
if
it
asks
you
to
log
in
I,
would
you
can
use
user
and
then
try
a
I?
Don't
want
everybody
use
the
same
user,
so
that's
gonna
kind
of
be
in
a
shoe.
If
we
don't
do
that,
but
there's
75
total.
So
if
I
have
to
I
can
be
like
1
2,
3
4,
5
6,
the
console
is
good.
Ok,
let's
see,
if
we're
a
bunch
of
Engineers
here,
I
feel
like
we
could
figure
something
out.
A
A
A
You,
okay,
so
you're
you
can
be
used
or
30
yeah
an
issue.
Okay,
so
I'll
just
put
take
in
there.
Okay,
now
it
looks
like
people
are
in
there
and
they're
doing
stuff,
which
is
great.
Oh,
so
the
password
is
gonna,
be
open
shift
yeah!
Oh
sorry,
I
can
go
back
to
the
slide,
so
you
can
see
the
actual
stuff
right
yeah,
so
the
password
will
be
a
will,
be
OpenShift.
A
So
if
we
go
back
to
here
right,
okay,
so
once
you
start
getting
into
the
terminal,
does
anybody
need
me
to
put
up
the
link
for
the
terminal?
Essentially,
it's
the
bitly
link,
slash
montreal,
2019
terminal
I
think
it
is
I
can
go
back
one.
This
is
just
a
thing
for
the
terminal,
just
as
well
as
it
quick,
whatever
yeah.
So
once
you
go
in
there,
you'll
see
I'm
gonna
have
to
click,
allow
for
some
permissions.
B
A
B
A
A
A
If
you
want
to
use
nano
as
your
editor
instead,
VI
do
this
export
command
here,
but
I
would
I
would
recommend
doing
this
export
host
command.
You
don't
have
to
put
that
back
slash
if
you're
just
writing
it.
All
out
of
this
is
if
you're
going
to
copy
and
paste,
and
this
slides
are
on
actually
that
first
slide.
If
you
were
to
actually
go
to
it,
but
because
we're
going
to
use
this
host
variable
and
a
couple
of
examples.
So
if
we
have
it
set
up
already,
you'll
be
good.
A
A
All
right,
if
anybody
needs
me
to
go
back,
I
can
and
so
now
we're
gonna
open
up
the
web
console
with
the
thing
that
I've
been
kind
of
clicking
through
so
now
you
guys
can
actually
get
your
own
one.
So
if
you
guys
want
to
go
to
that
link,
username
password
is
the
same
as
what
you
logged
in
with
the
with
the
terminal.
A
A
So
when
you,
when
you
first
open
up,
you
might
actually
see
this
kind
of
view.
I
would
just
you
would
just
go
into
it'll.
You'll
have
like
one
thing
on.
Of
course
you
can't
actually
see
me
pointing
at
my
screen
on
that.
This
would
be
the
right-hand
side,
you'll,
probably
just
see
like
user
and
then
the
number
user
you
are
so
you
just
actually
click
that,
and
that
goes
into
your
namespace
or
your
project
or
if
you
created
one
on
the
command
line,
you
could
go
into
that
one
too.
So
this
is
the
one.
B
A
A
Okay,
actually,
if
you
put
the
ette
that
you
put
to
eat,
if
you
did
it
as
HTTP
I
think
it
would
open
up
the
that
console
instead,
but
we're
not
yeah
alright,
so
right,
we're
just
gonna.
Try
to
do.
Is
it's
a
very
simple
nodejs
app
to
get
deployed.
You
know,
so
you
know
you
might
have
something
like
this
very
basic
Express,
app,
I'm,
sure
everybody's
kind
of
familiar
with
this.
What
this
looks
like
so
we'll
go
quick
and
then,
in
order
to
make
this
into
a
container,
we
need
a
docker
file.
It
might
select.
A
A
A
A
Yeah,
so
we
have
this
appointment,
you
can
do
this
cube.
Kiddo
get
deployment,
hello,
which
is
the
name
of
the
deployment
and
oh,
is
for
the
output,
and
you
did
yeah
mol
you'll
see
what
your
deployment
is.
What
it
looks
like
in
Yama
format,
you
could
also
describe
it,
and
that
gives
a
little
bit
more
readable
things
for
the
desk.
Oh,
you
could
also
do
a
Oh
JSON
and
that
will
output
in
I.
You
guessed
it
JSON
format
instead
of
VMO.
A
Is
that
they
change
so
that
if
you
were
to
type
that
one
that's
on
the
screen,
it
would
actually
not
work,
because
that's
not
pod
name,
but
you
can
also
do
that
if
you're
in
the
web
console
by
clicking
in
that
role,
blue
circle
that
we
looked
at
earlier
and
you
can
click
on
logs
and
and
check
and
check
that
out
there
all
right.
So
now
we
have
something
deployed.
How
do
we
actually
expose
that
and
be
able
to
get
access
to
it?
A
We
have
to
create
a
service
for
that,
so
I'm,
just
doing
plain,
cube
or
any
stuff,
you
know.
Do
a
cube.
Ctl
expose
you
want!
You
ever
want
to
expose
the
deployment
with
the
name
of
hello.
We're
gonna
tell
it
to
bind
to
port
8080,
and
here
we're
gonna
use
a
type
of
node
port.
There's
a
couple
different
types:
we're
not
I'm
not
going
to
go
into
what
those
are,
but
essentially
node
port
is
kind
of
the
most
basic
ways
of
exposing
things
it.
A
A
Right
yeah,
so
you
can
see
the
service
that
you
created.
If
you
do
cube,
CT
I'll
get
service
with
Hello
as
the
name
of
the
service
and
their
show
again,
the
mo
yeah
and
now
actually
to
get
the
the
port
that
the
new
port
that
the
service
creative
force,
the
dynamic
thing
you
could
do
this
command,
basically
we're
getting
we're
getting
the
service
and
inside.
If
you
were
actually
to
get
that
service
as
a
JSON
output,
then
you
can
actually
see
you
know
where
it's
located
so
in
this
particular
using
a
JSON
path.
A
A
A
A
B
B
A
Do
all
right
all
right,
so
if
you
wanted
to
roll
out
a
new
version
of
the
application,
you
can
just
set
the
image
to
basically
a
new
version
of
the
doctor
image.
That's
that's
here
and
then
that
will
I'm
just
gonna
run
through
this.
We
can
get
to
the
actual
real
application
that
actually
has
the
cloud
native
pattern.
A
So
if
you
don't
want
to
type
this
in
its
find
their
slides-
and
you
could
kind
of
work
on
this
later
so
basically
what
you
do
is
you
would
just
deploy
a
new
image
with
the
new
version
and
that
will
actually
just
update
the
image
right
and
then
and
then
this
is
just
the
way
you
would
clean
up.
You
leave
this
stuff
and
basically
it's
saying
that
services
and
deployments
are
actually
independent
of
each
other.
So
if
you
delete
a
service,
it
doesn't
actually
delete
the
deployment
yeah
because
they're
not
connected
that
way.
A
I
mean
they
sort
of
connected,
but
if
you
they
can
live,
you
know
independently
from
each
other,
all
right
right.
So
we
deployed
a
thing.
We
saw
pod
so
deployments
so
a
service.
We
saw
how
to
run
in
a
container
image
in
kubernetes
and
how
to
expose
that
all
right.
So
now
we're
actually
gonna
build
a
real
application
here.
So,
okay!
So
if
you're
in
your
terminal,
what
we
can
clone
this
this
repo
here.
B
A
If
anybody
needs
me
to
go
back
just
let
me
know
basically
I'll
make
this
bigger
just
for
this.
So
basically,
what
this
app
is
is
is
we're
going
to
be
basically
hitting
a
couple
different
services
and
we're
gonna
basically
return.
This
Elizabethan
insult,
like
an
insult
from
the
time
of
probably
the
1600,
or
something
like
that.
England
we're
gonna
be
insulted.
That
way
that
the
way
the
app
is
broken
up.
There's
this
front-end
service,
that's
running!
That
then
goes
into
this
insult
service.
That's
that's!
Just
an
ode
regular
note
service.
A
That
service
actually
calls
two
different
ones:
an
adjective
service
and
announce
service
to
get
back
an
adjective
and
a
noun,
and
then
all
that
stuff
is
put
together
and
sent
back
to
the
browser
within
each
of
those
in
front
of
in
front
of
each
of
those
services.
We
have
a
circuit
breaker
that
one
here
we're
using
a
possum
jas,
which
is
one
circuit,
breaker
implementation,
I
think
brakes
is
another
one.
There
might
be
a
couple
other
then
maybe
a
couple
others
right,
okay
right!
A
So
if
you
have
that
repo
cloned,
what
we're
gonna
do
is
so
you
go
into
that
directory,
you
can
cat
the
deploy
SH
to
see
kind
of
what
we're
doing
here.
There's
a
couple.
We're
gonna
do
kind
of
a
couple
different
things
here.
So
the
majority,
the
services
we're
just
gonna,
do
the
regular
deploy
like
we
saw
from
the
the
other
app.
It's
just
gonna.
You
know
push
up
a
docker
image,
that's
already
been
created
and
it's
gonna
expose
that
and
then
it's
actually
gonna
create
routes.
So
we
don't
have
to
worry
about
doing
that.
A
No
port
stuff
anymore,
because
that's
just
a
pain.
But
if
you
look
in
that
file,
we
there's
the
the
kind
of
the
noun
service
has
been
commented
out.
That
I
actually
wanted
to
have
us
deploy
a
different
way
using
a
tool
called
node
shift
which
will
do
sort
of
that
s2i
flow
of
deploying
things
just
to
kind
of
get
a
different
kind
of
perspective
on
different
ways
of
deployment.
And
so,
if
you
run
that
deploy
script
now
you
should
be
able
to
have
you.
Should
it
should
be
pretty
quick,
deploying
the
front
servus
I!
A
A
A
So,
if
you're,
actually
so,
if
you
go
to
the
like
your
web
console
or
the
dev
console
in
Chrome
or
wherever
browsers,
are
using
you'll-
see
that
it's
the
circuit
breaker
is
breaking
so
it's
failing
and
it
is
because
I
don't
know
if
you
can
see
it,
I
don't
know
if
it
shows
it
in
here,
but
the
the
the
URL
that's
trying
to
hit
is
a
little
host
8080,
it's
not
actually
trying
to
hit.
It
has
the
the
one
that
we're
actually
running
on
on
our
kubernetes
cluster.
So
we
need
to
fix
that.
A
Well,
while
we're
fixing
that
if
you
what
you
want
it,
if
you
want
to
back
in
the
terminal,
go
into
the
now
directory,
do
an
NPM
run
deploy
this
will
actually
kick
off
the
node
shift
thing
which
will
take
a
little
bit
because
it's
gonna,
basically,
what
that's
going
to
do.
It's
gonna
package
up
the
code,
that's
in
the
noun
directory,
it's
gonna
send
that
up
to
OpenShift
and
it's
going
to
combine
it
with
an
s2.
I
image
it's
gonna,
build
that
which
means
it's
gonna.
A
Do
an
NPM
install
all
on
the
cluster
once
that
gets
done,
then
it
will
create
the
deployment
it'll
create
a
service
and
I'll
create
a
route,
and
it
will
deploy
that
pod
and
everything
will
be
running
but
it'll
just
take
a
few.
You
know
maybe
a
minute
or
two,
while
does
the
NPM
install
you
know
on
the
hosted
service?
A
So
if
we
have
that
running
when
we,
while
we
create
this
sort
of
this
external
configuration
that
we're
gonna
see
to
to
fix
the
issue
with,
it's
still
pointing
to
little
host
all
right
and
then
what
we'll
and
we'll
come
back
to
and
yeah.
So
these
were
the
slides,
basically
saying
hey
look.
This
thing
is
broken
because
it's
looking
pointing
at
a
local
host,
so
we're
skipping
around
a
little
bit.
Alright,
so
we're
gonna
check
out
this
external
configuration
thing
and
we're
gonna
do
it.
A
Iii
do
have
slides
where
you
do
do
from
the
command
line,
which
is
farther
down.
It's
editing
the
ammo
files
and
I
just
very
dislike,
hitting
yell
files,
because
I
don't
know
where
the
tabs
and
spaces
are
supposed
to
be
on
those
things,
so
we're
gonna
do
it
from
the
console.
So
if
you
go
back
to
the
go
to
your
web
console
and
just
follow
me,
if
you
want
under
resources,
config
Maps
and
then
we
say,
create
a
config
map,
we're
gonna
call
we're
gonna
name
it
insult
service.
A
Just
with
the
you
told
service,
the
key
was
gonna.
Now
that
you're
gonna
have.
This
is
gonna,
be
all
uppercase.
It's
gonna
just
be
insult
underscore
service
and
the
value
here
that
we're
going
to
do
is
it's
going
to
be
the
Roshan.
Your
searching,
yeah
yeah,
the
valuable
here
we're
gonna
have
here,
is
gonna
actually
going
to
be
the
route
to
the
insult
service.
A
A
A
It
is
getting
insults
with
adjectives
and
actually
the
same
now,
because
I
have
yet
to
deploy
the
noun
the
noun
thing,
the
noun
service.
Sorry,
so
Creek
config
map
insult
service
service
capitals
underscore
service.
So
then
your
value
is
actually
going
to
be
that
route
that
you
copied.
Slash
API,
slash
insult.
A
So
if
we
create
that
that
will
create
our
config
map
and
now
we're
gonna
go
back
kind
of
back
to
the
overview
and
then
our
front
end.
Here
we
can
click.
This
front
end
thing
to
go
into
our
front
end
deployment,
hopefully
I'm,
not
losing
anybody
in
environment,
we're
gonna,
click
on
add
value
from
config
map
or
secret.
A
This
name
we're
gonna,
actually
be
insult
service
where
it's
going
to
be
capitals
and
skull
insult
underscore
service.
All
caps,
the
resource
that
we're
going
to
use
is
the
insult
service.
Config
map
that
we
just
created
and
the
key
that
we're
going
to
use
is
the
insult
service
key
that
we
created
for
that
for
that
and
then,
if
you
click
save
that
will
actually
trigger.
A
B
A
A
B
A
Alright,
let's
see
where
we
were
on
the
slides,
alright,
so
that
was
config
nap.
So
that's
one
pattern
is
kind
of
having
your
some
configurations,
not
necessarily
within
your
app,
but
in
an
external
resource
that
you
can
change,
and
so
every
time
you
change
that,
then
your
deployment
could
rehab
can
happen
again,
but
you're
not
actually
changing
code.
So
that's
a
good
thing
to
kind
of
keep
things
separate
and
you
should
think
pot
of
pods
to
is
is
things
that
you
know
that
will
will
die
I'll.
A
You
know
sort
of
consistently
I'm
not
consistent,
but
like
it's
there
and
they
should
be
somewhat
stateless
because
you
know
they
can
go
up
and
down
like
a
bunch.
So
you
want
to
keep
as
little
as
little
state
as
you
pop,
as
you
can
probably
out
of
in
you
know
in
the
pod
and
keep
it
in
these
other
different
external
configurations.
This
just
walks
through
going
on.
A
So
if
you
would
did
want
to
do
it
for
the
command
line
and
you
were
playing
along
with
the
slides-
and
this
is
just
another
way
of
doing
it-
and
you
actually
have
to
edit
the
deployment
and
edit
some
yamo
and
that's
why
I'd
rather
do
it
from
the
the
web
console
because
editing
amyl
isn't
my
my
favorite
thing,
alright,
so
health
checks
which
you're
alive
Elena
stand
readiness
URLs
this
here's
another
pattern.
So
essentially
what
aliveness
probe
is
is
basically
checking
to
see.
A
If
your
app
is
alive
and
readiness
is
you
know
it's
something
that
you
can
check
just
make
see
if
your
app
is
ready
yet
and
with
a
combination
of
these,
you
could
actually
make
it.
So
you
have
zero
downtime
when
redeploying
your
app
applications,
so
something
with
so
with
all
these
application.
This
particular
application
that
we're
doing
all
the
services
there's
actually
a
module
called
queue
probe
which,
if
you
add
that
it'll
actually
add
these
slash,
API
slash
health,
live
NS
and
the
readiness
probes
to
your
expressed
applications.
A
So
you
don't
have
to
worry
about
it,
because
those
are
the
defaults
for
kubernetes
and
slashin
OpenShift,
but
if
you
did
want
it,
if
you
did
have
other
you
or
say
your
URL
that
you
wanted
to
hit
or
change
it
up,
you
could
modify
that
and
then
you
know
when
you're
requiring
you
add,
the
apne
I
can
do
the
options
and
stuff.
So
all
the
app
all
of
these
services
within
this
elisa
be
thin
and
soul.
App.
Do
you
has
this
already
kind
of
installed
there?
A
So
if
you
were
to,
if
you
happen
to
have
that
that
front-end
path
already
in
your
terminal-
and
you
went
to
these
these
out-
you
know
these
api's
or
you
could
just
do
it
from
the
web
browser
as
well.
You
go
to
those
api's.
It
should
just
return.
Okay,
that's
just
that's
the
default
thing
it
does.
It
just
returns
a
200,
ok,.
A
But
right
now
there
and
we'll
we'll
actually
do
this
from
from
the
from
the
web
console,
because
it
is
easier
than
editing
the
thing.
So
if
so,
if
we
wanted
to
add
the
actual
so
right
now
those
those
you
those
api's
in
the
URL,
the
URLs,
the
rest
api
is-
are
there
in
the
app
but
they're
not
configured
inside
the
cluster,
for
that
particular
deployment.
A
So
again,
if
we
go
in
here
into
this
deployment
for
front-end,
we
could
say
configuration
here.
It
actually
says:
hey
you,
don't
have
any
health
checks.
Do
you
want
to
add
them,
yeah
sure
we
do
so.
You
can
add
it
readiness
one
so
the
path
for
that
would
would
be
slash.
Api,
slash,
health,
slash,
ready,
Ness,
if
that's
the
right,
Innes
one
yeah
and
then
port
is
a
DAT,
because
that's
the
port
that
the
app
actually
applications
running
on
and
then
you
can
just
leave.
You
know
if
you
wanted
to
leave
the
defaults
here.
A
Basically,
the
initial
delay
is
saying:
how
long
should
I
wait
before
or
doing
this
ping
and
then
the
timeout?
Is
you
know
how
long
to
wait
after
the
counter
starts
before
checking
health,
or
actually
it's
not
right?
Cuz
I
read
the
wrong
one.
Yeah
I
could
read
that
right
and
11's
has
has
very
similar.
A
Options
as
well
so
right
now
we're
just
gonna,
add
a
readiness
one
and
then
that's
it,
and
then
basically,
every
kind
of
configuration
change
that
we've
been
doing
here
has
been
redeploying
this
front.
Nf
sorry.
This
is
now
we're
up
to
the
third
time.
So
that's
why
it
is
a
good
idea
to
keep
things
any
kind
of
configurations,
kind
of
kind
of
separate
there
too.
A
So
we've
actually
went
in
here
into
the
configuration.
Now
we
can
see
that
it's
we
have
this
readiness
probe
here
and
it
doesn't
have
to
be.
It
doesn't
have
to
be
a
rest
endpoint
either
it
could
be
like
you
could
tell
these
these
probes
to
run
a
command
from
like
the
command
line
or
something
like
that
to
see.
If
you're,
if
you're
you
know
your
app
is
ready
or
if
your
app
is
still
alive,
so
yeah
alright.
So
we
don't
have
too
much
time
here.
A
So
go
quick,
a
one
kind
of
more
more
concept
here,
which
is
probably
the
most
important
one
and
because
that's
resilience,
which
is
the
circuit
breaking
stuff.
So
we
saw
this
diagram
earlier.
There's
circuit
breakers.
Basically,
before
you
know,
every
single
app
here
and
here
we're
using
this
thing
called
a
possum
which
you
know
has
some
options.
This
particular
error.
Threshold
percent
is
saying
this
one
says.
Basically,
if
there's
70%
of
things
that
happen,
our
errors,
then
we're
gonna
trip
the
circuit
and
we're
gonna.
A
Timeout
here
is
how
long
like,
if
we're
making
a
rest
like
a
rest,
call
like
how
long
should
that
happen
before
we
say
it's
failing,
this
is
500
milliseconds,
so
we
probably
want
to
up
that
possible
and
then
once
things
do
open,
it's
like
this
reset
time
saying.
How
long
should
we
wait
to
to
close
the
circuit?
So
we
can
try
again,
that's
with
it
and.
A
Something
it's
not
really
a
big,
a
big
thing
there.
So
in
this
example,
this
is
just
a
node
example.
Here
we
have.
This
function
called
get
noun,
which
gets
a
URL
from
some
service
and
if,
if
it
passes,
then
we're
going
to
return
some
some
data,
we
create
our
new
circuit
and
then
we
say:
ok,
you
know
on
failure,
we're
gonna,
just
output
to
the
console,
but
as
a
fallback,
if
it
does
error,
we're
just
going
to
return,
we're
gonna
call
this
function.
That
returns
this
object
that
says
noun
and
dung
scrapers.
A
The
is
the
value
of
of
the
return
value.
This
is
actually
I,
think
the
the
the
getting
the
noun
service
in
in
the
code
right
and
then
this
is
just
saying
hey
on
this
thing.
We
do
the
circuit
fire,
which
calls
that
function
that
we
previously
so
that's
the
fire
function
will
actually
call
the
get
now
function
there
and
then
you
know
do
all
that
stuff
and
then
we
can
also
do
it
inside
the
browser
to
which
it
also
works
and
has
very
similar
options.
A
A
But
this
is
saying-
and
we
can
do
this
from-
we
can
actually
do
this
from
the
web
console
again
here
what
that
example
is
saying
they
wanted
to
take
down
and
I
don't
have
it
here
so
just
follow
along.
But
if
you,
if
you
took
down,
they
wanted
to
basically
say,
let's
take
down
one
one
of
those
services,
so
in
this
case
I'm
doing
the
adjective
1.
If
you
want
to
do
noun,
that's
fine
too,
so
we
can
actually
scale
it
down
to
zero
from
the
command.
A
A
A
Know
we're
just
moving
fast
because
if
you
don't
really
have
any
time
left
but
right
and
that's
saying
so
yeah.
Basically,
this
is
saying
edit,
the
edit.
The
deployment
file
for
the
noun
bring
the
amount
of
replicas
to
zero.
Basically
saying
just
don't
have
any
more
pods,
you
test
the
service,
and
you
can
see
that
it's
failing,
then
you
just
bring
them
back
up
and
the
pods
start
working
again.
B
A
You
know
deploying
deploying
with
just
using
the
regular
vanilla,
Cabrini
stuff
we
saw
using
node
shift
so
about
creating
routes.
So
these
different
sort
of
patterns
or
patterns,
as
my
six-year-old
likes
to
say
you
know,
of
keeping
things
separate
and
external
configurations
and
circuit
breaking
and
putting
in
using
health
checks.
A
So
since
we
don't
have
any
time,
I
do
I
want.
If
we
did,
I
was
gonna.
Do
this
thing?
Where
how
would
you
actually
do
like
a
modern
web
application
because
they
want
the
application
for
front-end?
Here,
it's
actually
some
I.
You
know
it's
just
HTML,
but
it's
also
being
served
by
it's
just
a
regular
web
app,
it's
just
being
served
and
it's
also
being
to
serve
like
an
express
server.
But
how
would
you
do
like
just
like
if
you
were
gonna,
do
like
a
react
app
or
like
angular,
amber
something
like
that
there's?
A
Actually,
we
actually
have
an
s2i
image.
That's
specific
for
those
kinds
of
things,
and
you
don't
have
to
do
this
now,
because
I
know
we're
sort
of
at
the
time,
but
basically
this
allows
you
to
this.
This
s2i
image
will
take
your
like
in
this
example.
It's
just
this
react.
Web
app
is
a
basic,
create
react,
whip
create
react,
app
application,
that's
all
it
is,
and
it
basically
will
take
that
code.
It
will
Rhianna,
it
will
run
the
npm
build
or
your
on
build
whatever
you're
using.
A
It
will
take
that
it'll,
take
what
you've
built
and
that
output
directory,
and
then
it
will
just
it'll
actually
do
ill
use,
NPM,
serve
or
I.
Think
technically,
it's
npx
serve
it'll
use
the
serve
module
to
then
serve
that
code.
That's
that's
one
way
you
can
do
it.
You
can
actually
also
do
some
slight
modification
or
s-some
some
vibrant
variables,
where
you
can
actually
run
the
full
roll
server
or
the
dev
server
of
that
modern
web
app
on
open
shift
and
then
connect
your
code.
A
You
know
like
a
Narsingh
kind
of
thing
in
between
so
changes
you
make
locally,
they
will
reflect
and
that
whole
kind
of
loop
of
change,
making
a
change
locally
in
it
propagating
up
to
the
running
container,
and
then
you
can
see
the
changes
and
stuff
and
then
the
other
thing
that
this
is
great
for
is
kind
of
that
to
state
if
I'll
just
go
back
to
a
really
quick
just
to
confuse
everybody.
Here
was
this.
A
So
this
two-stage
thing
here,
because
really
when
you
create
a
modern
web
app
like
a
web
application,
you're,
not
necessarily
it's
all,
it
is
HTML
and
JavaScript.
It's
not
necessarily
a
node
app
right,
like
you
use
no
to
build
your
things,
but
you
really
don't
use
node
to
serve
it
necessarily
and
that's
something
like
nginx
or
Apache,
or
some
sort
of
HTTP
server
is
better
suited
for
that.
So
this
allows
you
to
do
this.
A
Whatever
you
have
0
node
code
at
all,
because
all
is
is
HTML
and
that
kind
of
stuff
I've
written
a
few
blog
posts
on
that
called
modern
map
applications
on
openshift.
You
can
google,
that
or
not.
If
you
wanted
to
learn
more
or
just
come
and
talk
to
me
if
you
want
to-
or
you
don't
have
to
talk
to
me
at
all,
if
you
don't
want
to
so
I'm,
actually
gonna
skip
the
questions
section
and
just
say.
A
Thank
you
because
this
was
a
very
interesting
interesting
thing
just
last,
if
so,
I'm,
usually
the
person
walking
around
aimlessly
because
I
have
nobody
to
talk
to.
So
if
you
find
yourself
in
that
position
where
you
like
walking
on
because
don't
really
know
anybody-
and
you
see
me-
you
can
just
randomly
come
and
talk
to
me,
so
you
don't
have
to
be
in
that
position
anymore.
Just
it
has
nothing
to
do
with
this
talk.
It's
just
it's
just
how
you
know
it's
good.
This
is
how
things
happen
in
conferences.
A
So
if
you
find
yourself
it's
kind
of
a
mostly
walking
around
and
been
like
I,
don't
know
what
to
do
because
I,
don't
know
anybody
here
and
you
see,
and
you
see
me
just
you
can
come
up
in
how
we
can
have
random
conversations
and
how
interesting
this
talk
was,
or
or
fish
or
Star,
Wars
or
war
Warcraft
or
anything
really
yeah.
So,
but
alright,
thank
you
so
much
for
enduring
that.