►
From YouTube: OpenShift Commons Briefing #127: Load Balancing Applications with the OpenShift NGINX Router
Description
Load balancing applications with the OpenShift NGINX router. This presentation will cover:
- the basics of the OpenShift router and the NGINX implementation of it
- a demo of deploying the router
- some Q&A
A
Hello,
everybody
and
welcome
again
to
another
open
ship
Commons
briefing
this
time,
we're
having
the
good
folks
from
nginx
talk
to
us
about
load,
balancing
applications
with
the
openshift
nginx
router,
and
this
is
I-
think
we
did
talk
with
these
guys
almost
over
a
year
ago.
So
it's
a
very
timely
thing
and
they've
done
some
really
cool
work
with
the
open
ship
team
and
I'm
gonna.
Let
Damian
curry,
introduce
it.
A
The
format
for
today,
as
always,
is
if
you
have
questions,
ask
them
in
the
chat
we're
going
to
let
Damian
team
from
nginx
do
their
talk.
It's
not
super
long
and
do
their
demo
and
then
we'll
do
live
Q&A
at
the
end.
So
please
Dameon
without
any
further
ado.
Take
it
away
and
let's,
let's
hear
what's
going
on
now:
okay.
B
Great,
thank
you
very
much
hey
good
morning.
Everyone
did.
My
name
is
Damian
curry
I'm,
the
technical
business
development
manager
here
at
nginx
and
I'm
also
joined
by
Michael
plush
and
cough.
Who
is
one
of
our
engineers
who
did
a
lot
of
the
implemented
the
implementation
work
for
this,
and
so
what
we're
going
to
talk
about
today
is
load
balancing
applications
with
the
open,
shipped
and
gen-x
router.
B
Just
a
real
quick
agenda,
we're
just
going
to
go
over
the
the
basics
of
the
openshift
router
and
as
well
as
our
implementation
for
nginx
running
as
an
open,
shipped
router,
and
then
we're
going
to
run
through
a
quick
demo
just
to
give
you
an
idea
of
what
it
takes
to
go
ahead
and
deploy
the
nginx
rather
in
OpenShift,
and
then
we're
going
to
have
some
time
for
some
quick
questions.
So
just
a
very
high-level
I
mean
what
is
the
open
shift?
B
Router,
the
the
openshift
router
is
the
entry
point
for
all
external
requests
coming
into
the
cholesteral
x'
routing
requests
to
the
different
application,
pods
based
on
URI
or
hostname,
as
well
as
other
factors
they
can
use
in
there
as
well,
and
really
it
is
one
of
the
most
critical
parts
of
the
platform
without
the
router.
There
is
no
way
to
to
expose
your
applications
publicly
from
openshift.
Some
of
the
key
features
of
the
openshift
router
are
load
balancing
for
HTTP
and
HTTPS,
as
well
as
WebSocket
WebSocket
traffic.
B
B
So
what
we've
done
here
is
we've
built
a
implementation
to
be
able
to
run
nginx
or
nginx
plus
as
an
open
shift
router.
So
some
of
the
benefits
here
is,
you
know
we
we
added
in
full
support
for
all
of
the
routers
special
specifications.
Anything
that's
pretty
much
available
out
there
to
configure
and
deploy
the
router
is,
is
applicable
to
the
nginx
configurations
as
well.
We've
also
added
a
lot
of
customization
options.
Pretty
much
anything
you
can
do
in
nginx
is
possible
to
implement
in
the
OpenShift
router
functionality
as
well.
B
As
you
know,
it's
just
continuing
a
familiar
operational
experience.
Many
people
out
there
are
already
using
nginx
in
their
infrastructure
and
it's
good
to
just
have
a
standard
tool,
something
that
you're
already
used
to.
So
if
there
are
any
problems
in
troubleshooting
is
necessary.
It's
something
that
you're
familiar
with
as
well
as
we
port
all
the
latest
nginx
features
to
the
open
ships
router,
for
example.
We
just
recently
added
full
G
RPC
support,
which
is
available
in
our
router
implementation
as
well.
B
Our
implementation
is
also
100%
open-source
we've
we've
made
changes
in
and
upstream
them
to
the
open,
shipped
origin
as
well
as
publish
them,
some
different
features
in
our
own
github
repositories
as
well,
and
then.
Finally,
we
also
make
a
bit
available
all
of
the
advanced
features
that
are
available
in
nginx
plus.
B
B
If
you
use
the
OpenStack
your
OpenShift,
you
are
very
familiar
right
already.
The
only
other
changes
we
made
were
to
the
template.
Helper
dot
go
file,
so
basically
all
we
did
was
we
extended
the
support
to
be
able
to
handle
nginx
configuration
primitives
most
of
the
information
was
already
in
there,
but
there's
a
few
key
points
that
we
needed
to
add
to
be
able
to
properly
configure
an
engine,
X
installation
and
just
to
kind
of
give
you
an
example
here
this
this
right
here
on
the
screen.
B
This
is
all
the
actual
code
we
added
to
this
file.
It's
very
minimal
changes.
There
isn't
any
extra
overhead
going
on
here,
so
I
mean
in
total
it's
about
sixty
lines
of
code
and
that's
all
that
we
needed
to
add
to
enable
nginx
to
be
able
to
run
as
a
router.
Now,
obviously,
with
this
thing,
I
got
cleaned
up
to
cut
all
the
comment
to
so
you
get
an
idea
of
what
the
code
looks
like,
but
you
know
very,
very
simple
changes,
nothing,
nothing!
That's
going
to
impact
the
performance
of
openshift
and
then
so.
B
So
those
those
will
be
coming
down
the
line
event
soon,
all
right
and
then
real,
quick,
we're
going
to
run
through
a
fast
demo
here.
So
first
we're
just
going
to
do
very
basic
set
up
is
all
we
have
to
do
is
go
in
delete
the
default
router
we're
going
to
go
ahead
and
deploy
the
nginx
+
router,
and
then
we're
going
to
go
ahead.
And
you
know
it's
just
basically
expose
a
very
simple
web
application
just
to
verify
everything's
working
and
up
and
running.
B
B
We
built
the
image
created,
it
built
the
container
everything's
up
and
running,
and
then
we
went
ahead
and
just
uploaded
it
to
the
service,
the
service
registry
that
is
built
as
part
of
OpenShift,
and
so
now
we'll
just
go
from
here,
and
we
can
walk
through
the
last
couple
of
steps
to
go
ahead
and
get
this
thing.
So
the
first
thing
we're
going
to
do
is
we're
simply
going
to
do
a
quick
backup
of
the
default
router
about
the
correct
command.
B
B
Now,
as
we've
already
uploaded
the
nginx
Plus
image,
we
can
simply
deploy
the
new
router
with
a
single
command
here,
so
we're
just
going
to
go
ahead
and
deploy
a
new
router
and
we're
specifying
the
nginx
+
router
image
that
we
already
created
and
uploaded
to
our
registry
and
then
we're
simply
tagging
it
with
the
region
infra
to
go
ahead
and
make
sure
it
gets
deployed
on
the
master
nodes
in
this
cluster
that
we're
using
and
just
so
everybody
is
aware.
This
is
a
three
node
cluster
running
OpenShift
3.9
based
on
AWS.
B
Okay
and
so
we've
got
the
deploy.
Pod
is
up
and
running
so
now
we
should
be
able
to
wait
a
couple
minutes
here
as
all
the
pods
spin
up
and
we
have
a
router
up
and
running
so
now
we
should
be
able
to
go
back
here
and
we
have
look
into
our
registry,
so
everything
is
up
and
running
again
and
what
we
will
do
is
one
last
quick
change:
we're
going
to
open
up
a
tables
port
so
that
we
can
reach
the
status
dashboard.
B
B
So
one
will
be
behind
/t
and
the
other
one
will
be
behind
slash
coffee,
so
you
can
already
see
that
we
have
some
new
server
zones
being
generated,
so
you
can
see
the
cafe
example.com
and
then
we
can
also
see
that
we
have
some
new
configurations
running
here.
So
the
next
thing
we
can
do
is
we
go
back.
We
can
go
ahead
and
refresh
and
now
obviously
I've
modified
my
hosts
file
to
point
example.com
at
my
cluster
here
and
so
now
we
can
see
that
we
have
an
application
up
and
running
granted.
B
We
are
very
basic
here
just
showing
that
we
are
seeing
two
different
applications
running
in
two
different
pods.
So
that's
it.
That's!
That's
all
it's
necessary
to
do
to
build
the
nginx
+
router
and
get
it
running
in
an
open,
shipped
environment
and
from
there
everything
can
be
handled,
as
as
you
would
in
any
other
router
situation.
B
A
A
B
So
yeah
well
one
of
the
first
steps
we
had
there
was
actually
to
disabled
and
turn
off
the
default
router
now
it.
What
we
like
to
make
clear
here
is
that
this
is
not
an
add-on
route
or
anything
like
this.
This
is
a
new
default
so
now
going
forward.
Instead
of
having
the
default
only
option,
B
the
H,
a
proxy
based
router,
you
will
be
able
to
decide
whether
you
want
to
deploy
with
the
H
a
proxy
based
rather
or
the
nginx
base.
B
A
A
B
That's
the
big
it's
a
big
upside
and
downside
to
this.
It's
a
very
simple,
very
basic.
We
wanted
to
just
keep
it
as
easy
as
possible.
You
know
the
real
solution
here
is
we
just
want
to
provide
the
users
with
it
with
a
different
alternative.
You
know
just
to
give
them
choices
so
that
they're
not
walked
into
using
one
solution
for
the
router
I.
A
Think
this
is
great,
and
you
know
it's:
it
is
it's
I'm
relatively
simple
to
do
so.
I'm,
hoping
that
some
of
you
that
are
listening
in
will
give
us
your
feedback
on
it
and
once
you've
tried
it
out
and
tested
it.
You
reach
out
to
the
folks
at
nginx
and
give
them
their
feedback
as
well,
and
when
3-10
comes
out,
we'll
see
be
some
good
adoption,
I'm
hoping
for
this
offering
so
long.
Thank
you
very
much
for
taking
the
time
today
and
giving
us
that's
this
overview
and
insights
and
how
to
use
it.
A
Michael
is
there
anything
that
you
wanted
to
add
to
this
that
that
made
me
damien,
miss
no
I,
think
Damien
covered
everything.
Thank
you
so
much
perfect
and
and
I
have
to
say
Damien
and
Michael.
This
is
the
perfect
length
briefing
I.
Think
we've
done.
We
figured
out
how
to
how
to
keep
it
in
succinct
chunks
of
information
and
I'll
I'll
get
this
uploaded
onto
YouTube
shortly
and
we'll
see.
If
we
can't
get
you
some
feedback
and
on
this
and
watch
it
take
off
like
hotcakes.