►
From YouTube: Make Ingress-Nginx Work for you, and the Community - Fernando Diaz, IBM (Any Skill Level)
Description
Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18).
Make Ingress-Nginx Work for you, and the Community - Fernando Diaz, IBM (Any Skill Level)
Have you been using Ingress-Nginx in your deployment and have features you wish to Contribute to the community, but are unsure how? Don't worry with the easy to follow session, you'll be up and running in no time. This session is perfect for beginners or community experts alike who wish to get more involved with Nginx-Ingress. From our demos, you'll learn: 1. How the ingress-controller works, from the internals to the templates. 2. How to add a simple feature, eg. Annotation, ConfigMap config change. 3. Building and Deploying the Ingress Controller and description of resources. 4. Configuring the Ingress Controller using Annotations and the Config Map. 5. Tips for Contributing back.
About Fernando
Fernando Diaz is an active contributor to Kubernetes, mainly focusing on Ingress-Nginx. Fernando is currently a Cloud Developer for IBM and works on the IBM Cloud Container Service primarily focusing on ingress. In the past Fernando was an OpenStack Core Contributor, focusing on Barbican(Key Management) Development. He has spoken and held workshops at several OpenStack Summits. Born and raised in Miami, Florida, Fernando received his B.ASc. in Computer Science at Florida International University. Currently resides in Austin, Texas and helps keep Austin weird.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
The
purpose
of
this
presentation
is
to
kind
of
go
ahead
and
give
the
little
give
people
a
little
in
depth
about
nginx
ingress,
how
it
works
a
little
bit
about
it
and
then
also
how
to
contribute
back,
how
to
develop
different
features,
whether
they're
gonna
be
proprietary
features
for
for
whatever
it
is
that
you're
working
on
or
whether
it's
something
that
you
want
to
contribute
back
to
the
community.
So
we're
gonna
go
in-depth,
so
how
many
of
you
guys
actually
use
nginx,
ingress
and
a
deployments.
A
So
a
couple
of
you
guys
so
how
many
people
have
actually
created
an
annotation
or
a
config
map
change?
Ok,
so
a
few
of
you
feel
view
are
pretty
versed
in
it
so
yeah.
So
my
name
is
Fernando.
My
work
at
the
IBM
container
service
and
I
mainly
work
on
the
ingress
controller.
So
we
have
our
own
proprietary
ingress
controller
and
we're
also
looking
to
support
the
community
version.
So
I've
been
contributing
and
kind
of
getting
handle
on
things
and
learning
how
to
do
it.
A
So
I
found
an
easy
way
and
useful
way
of
actually
building
with
mini,
cube
and
testing
out
your
features.
So
that's
what
I'm
gonna
go
over
today,
so
just
a
brief
overview
right,
so
ingress
right.
What's
what's
the
actual
meaning
of
ingress,
so
pretty
much
is
going
in
something
right
like
I,
guess,
ingressing
back
here,
I
guess
like
I'm,
going
into
the
ingressing
into
something
so
so
I,
just
like
the
actual
definition
for
it.
A
But
in
kubernetes
we
have
an
ingress
resource,
which
is
this
API
object
which
is
going
to
manage
external,
is
going
to
manage
access
to
your
external
service
in
the
cluster.
So
that's
pretty
much
all
you
have
and
if,
if
you
don't
know
what
a
services,
it's
pretty
much
a
logical
set
of
pods
that
defines
that
set
of
pods
and
then
it
exposes
them
to
the
outside
world
using
either
cluster
IP
or
cost
IP,
they
just
stay
inside,
but
you
is
either
Note
port
or
load
balancer
and
mainly
gonna.
A
Go
over
the
note
port,
which
is
what
I
use
for
mini
cube,
and
then
you
have
the
ingress
controller,
which
what
that
does
is
it
monitors
the
ingress
resources
and
the
monitors
any
updates,
and
he
adds
anything
done
and
creates
pretty
much
this
configuration.
So
what
it
will
do
in
this
case
and
nginx
ingress
is
it
monitors
the
ingress
resources
and
it
will
build
an
engine
X
configuration
based
off
of
that
which
is
a
whole
set
of
rules
through
to
the
server
and
how
everything's
gonna
work.
So
so
we
have
that
and
yeah.
A
So
let
me
kind
of
show
you
a
little
diagram,
so
request
comes
in
it'll,
hit
the
ingress
resource,
and
usually
you
have
paths
so,
like
you
know,
you
can
have
slash.
Aswan
will
point
you
to
service
one
slash
as
to
appoint
you
to
service
two
and
then
it'll
go
ahead
and
hit
the
actual
application
on
the
pod.
So
that's
a
little
bit
of
how
it
works.
A
Oh,
so,
if,
if
you
see
node
port
right,
we're
gonna
we're
going
to
be
using
node
port
to
expose
items
on
mini
cube
and
what
node
port
does
is
it
exposes
the
service
on
the
on
the
same
part
of
each
selected
node
in
the
cluster,
so
each
node
Oh
technically
have
a
node
IP
and
a
node
port.
So
I'll
show
you
a
little
bit
how
that
works
later
in
the
demo.
So,
okay,
so
I,
don't
know
how
has
anyone
seen
any
confusion
between
what
nginx
version
to
use?
A
So
there's
there's
two
separate
ones,
and
sometimes
you
see
one
from
the
actual
kubernetes
community
and
then
there's
also
one
from
the
nginx
Inc
community
right
so
which
is
also
open
source.
But
there's
it's
kind
of
different
right,
like
one
of
them
is
built
on
the
other
one
and
a
lot
of
people,
wonder
which
one
should
I
use,
which
one
right
so
I'll
go
over
just
a
couple
of
small
differences,
but
they
pretty
much
work
in
different
ways
right.
A
The
community
version
from
the
kubernetes
community
builds
just
one
big,
raishin
and,
and
it
moves
pretty
fast,
the
community
moves
pretty
fast.
We
have
great
maintained
errs
and
all
these
features
are
always
being
added,
and
you
know
I
can
probably
get
together
if
anyone
later
and
see.
If
we
can,
we
can
I
can
go
over
like
a
road
map
what's
going
on
with
that,
and
so
it
has
a
bunch
of
different
third-party
modules
in
it
and
it
has
very
different
annotations.
A
So
one
thing
about
ingress
resources
is
they're,
not
super
portable,
because
the
annotations
are
pretty
much
based
off
the
ingress
resource.
That's
that's
being
used,
so
you
know,
there's
nginx,
kubernetes,
io
and
then
the
annotation
there's
you
know
nginx
org
and
then
the
annotation
for
this,
this
version
of
the
ingress
controller,
so
there's
lots
of
differences
and
when,
when
determining
what
to
do
I
mean
I.
In
my
opinion,
this
is
good
if
you're
always
gonna
follow
community
and
you
wish
to
contribute.
A
But
if
you're
working
on
a
more
proprietary
system-
and
you
need
you
want
something-
that's
that
has
less
changes
imposed.
Then
you
would
go
ahead
and
use
the
nginx
Inc
version,
which
you
know
tends
to
be
more
stable
because
there's
not
you
know
constant
activity
on
there
and
there
is
good
support
as
well
from
the
maintainer
z--
of
that
community.
But
but
it's
it
moves
in
a
different
direction
than
the
actual
kubernetes
community
ingress
controller.
A
A
We'll
look
at
the
documentation
page,
so
there's
actually
been
a
big
amount
of
contributors
now
and
one
of
the
things
that
people
want
is
documentation.
So
so
I
want
to
put
like
an
emphasis
on
that
and
then
the
internal
contains
all
the
the
main
logic
right
for
the
controller
where
it
listens,
what
it
does
where
it
sends
off.
You
know
the
requests
to
generate
the
file
and
it
uses.
Go
templates
to
you
know
pretty
much
add
all
the
different
variables
and
things
that
you
set
up,
either
via
annotation
or
via
config
map
and
then
yeah.
A
A
A
So
if
you
have
to
host
level
annotations
it'll
on
on
ingress
resource
with
the
same
host,
it'll
always
take
the
first
one
and
that's
something
that
hasn't
been
documented,
but
something
that
that's
going
to
be
available.
After
cube
con
so
and
then
configuration
Maps
pretty
much
edits
the
global
configuration
so
any
variables
that
you
said
there
will
apply
to
every
server
and
every
location.
A
A
A
So
I
created
a
branch
right
with
these
changes,
so
you
guys
can
review
them
after
so
they'll
be,
if
you
can,
if
you
want
to
you,
can
download
the
actual
presentation
and
there'll
be
a
link
on
one
of
the
slides,
and
you
can
actually
just
see
the
branch
and
see
kind
of
what
the
changes
are.
So
I'll
go
over
each
component.
So
can
everyone
see
this
by
the
way?
Yeah?
A
Okay?
So
so
here's
the
ingress
resource
right,
we're
giving
it
the
name
cube
con,
and
this
is
an
annotation
that
that
I
built
in
which
pretty
much
just
assigns
a
nickname
to
a
server.
So
it'll
in
the
server
configuration
you'll,
see
a
nickname
and
all
that's
gonna
say
is
we're
here
right
and
then
I
just
have
the
path
echo,
which
points
out
an
echo
server
service
that
I
created.
So
that's
just
kind
of
so
you
can
see
how
the
ingress
resource
works
and
we
can
just
do
some
testing
and
then.
A
So
we
go
to
the
annotations
that
go
and
we
just
add
a
new
variable
called
nickname
and
we
add
the
nickname
to
the
extractor.
We
import
the
new
parser
right,
which,
which
I'll
show
you
now,
which
all
it's
gonna
be
doing,
is
just
parsing
this
string.
So
we
have
there's
a
lot
of
good
built-in
tools
already
for
these
types
of
things
and
the
mood,
so
everything
in
an
annotation
right
now
has
to
be
a
string
even
if
it's
and
then
and
then
it's
later,
translated
into
what
it's
going
to
be
a
boolean
or
whatever.
A
So
a
lot
of
a
lot
of
the
logic
is
involve
string
parsing.
So
so
all
this
pretty
much
does
is
it
just
looks
for
nickname
right
looks
for
the
annotation
named
nickname
and
then
it
just
creates
it
and
generates
the
configuration.
So
it's
very
simple
I'll
show
you
what
the
configuration
looks
like
I
just
wrote
a
test
that
just
checks
that
the
right
variable
is
being
set.
A
And
configuration
okay,
so
then
I
added
the
type
nickname
and
if
you
see
in
the
actual
template,
if
the
server
contains
the
nickname
item,
that's
derived
from
the
annotation,
then
we're
just
going
to
add
a
comment.
That's
as
the
server's
nickname
is
server
nickname
and
that's
pretty
much
that
simple.
So
if
anyone
wants
to
get
started,
that's
a
very
simple
example.
Just
to
add
you
know
comments
or
add
any
type
of
configuration
into
into
the
template
and
then
nginx
will
go
process.
This
template
and
it'll
generate
the
nginx
comm
from
that.
A
So
I've
also
added
a
configuration
map
change.
So,
as
you
can
see
it's
it's
importing
it
from
from
all
config,
which
is
you
know
where
all
the
configuration
items
are
stored
and
what
that's
gonna
do
is.
If
you
actually
apply
that
config
map
change,
it's
gonna
go
ahead
and
make
a
path
called
slash,
hello
and
then
from
there
it'll
print
out
a
message
and
return
the
200
code
and
that
to
do
that,
it's
pretty
much
that
simple,
just
adding
that
in
the
template
and
then
just
setting
it
up
and
config
that
go
file.
A
And
then
all
you
do
there
is
just
pretty
much
define
define
default,
which
is
false
and
then
just
add
the
hello
cube
con
name,
as
you
can
see,
hello
cube
con.
So
now,
if
you
have
data
that
that's
just
as
hello
cube
con
and
then
you
put
that
as
true
then
what's
gonna
happen,
is
it's
just
going
to
generate
that
/,
hello
path
in
your
nginx
kampf?
A
So
then
that
way
on
every
server,
you'll
have
a
slash,
hello
path
that
will
print
out
hey
hello,
where
a
cube
Conn
so
I
can
I
can
give
you
life.
Demo.
I
was
kind
of
hard
getting
a
mini
cube
set
up
this
morning,
because
the
network
issues
but
I
think
think
of
everything.
I
want
pretty
well.
So
let's
see.
A
A
You're
welcome
so
I.
Also,
if
you
look
at
the
repository
that
I
made
I
also
added
a
list
of
commands
that
would
be
pretty
useful
for
I
want
to
kind
of
just
track.
What's
going
on
and
and
see
so
so,
I'll
show
you
a
few
things,
so
in
mini
cube,
it
takes
a
while
to
set
up
so
you
would,
you
would
start
mini
cube,
you
would
check
the
status
and
then
you
would
enable
the
ingress
add-on.
A
A
A
A
And
then
all
I
have
to
do
is
just
add
a
tag
and
and
just
run,
make
docker
build
and
it'll
go
ahead
and
just
push
push
that
image
to
my
repo
and
then
all
I
have
to
do
is
just
change
it
in
the
replication
controller
and
there
I
put
hello
nginx
ingress
controller,
one
change
it
to
that,
and
now
it's
running
my
code
on
there.
So
it's
pretty
simple
to
get
started,
make
also
make
sure
using
the
docker
daemon.
So
that
way,
your
your
inside,
the
mini
cubes
docker
and
it's
just
one
command
and.
A
Okay
and
then
we
can
see
that
it
downloaded
the
correct
image.
I
was
created
and
then
you
know
maybe
there
was
a
problem
with
the
HTTP
readiness,
but
that's
just
because
of
mini
cube
issue
this
morning
that
I
had
installing
him
so
I.
Also
added
I,
also
added
hello
comm
to
my
Etsy
hosts
and
I
created
this
ingress
resource.
So.
A
A
Okay,
so
now
we
can
see
what
what
the
configuration
looks
like.
So
you
can
see
right
now
we
have
the
actual
annotation
that
I
created
to
work
successfully.
It
was
able
to
have
the
server
nickname
and
who
were
here,
and
you
can
see
the
path
was
created.
That's
a
default
path.
You
can
see
the
slash,
echo
path
was
created
and
it's
pointing
to
the
default
echo
server.
A
So
we
can
go
ahead
and
curl
that
so
curl
hello,
comm
just
gives
us
the
regular
default
back-end,
which
was
set
up
in
the
replication
controller.
And
if
we
do
slash
echo,
we
should
see
the
echo
header
service
from
from
Google.
So
so
that's
pretty
simple.
Now,
let's,
let's
edit
the
annotation,
just
to
make
sure
that
it
it
takes
changes
so
editing
course
resource.
A
A
A
It
just
has
that
extra
hello
cube
con
value
set
to
a
string
of
true
which
will
be
translated
to
a
boolean
and
now,
if
we
exact
and
cut
the
configuration,
you'll
see
a
new
path
defined
as
hello
and
what
this
new
path
does
is
it'll,
just
return
to
200
and
a
string.
So
if
we
curl
hello,
comm
slash
hello,
you'll
get
hello
from
cube
con
Europe,
so
yeah,
so
that
seems
to
have
worked
successfully.
So
the
demos
going
pretty
well.
A
You
would
use
the
docker
daemon
how
I
described
and
then
the
docker
Damon
would
go
ahead
and
and
put
you
into
mini
cubes
docker
you'd
build
the
image
you
would
and
make
sure
that
the
ingress
add-on
is
enabled
and
that
the
add-on
manager
is
disabled.
So
you
can
change
the
images,
then
you
would
verify
that
the
image
was
changed
and
then
run
some
tests
so
and
right
now
the
end-to-end
tests
were
just
introduced.
A
So
you,
if
you
run,
make
e
to
e,
you
can
see
the
end-to-end
test
run
and-
and
this
is
kind
of
a
new
thing
that
was
released-
maybe
a
few
weeks
ago
to
like
a
month
or
so
ago,
and
so
now,
nginx
controller
in
the
community
version
now
has
n
scientists
which
make
making
it
making
a
you
know.
Different
enterprise
and
different
customers
rely
on
it
more
and
you
know
I
think
that's
one
thing:
that's
driving
adoption
a
lot
so.
A
A
Yes,
so
I
mean
this.
That
concludes
my
presentation.
I
have
a
little
survey
so
Manuel,
which
is
the
the
maintainer
of
the
project.
He
he's
trying
to
look
to
see
what
people
want
out
of
ingress
controller,
to
see
if
we
need
to
add
any
new
features
and
see
what
we
can
do
with
the
actual
ingress
controller.
So
so
yeah
I
mean
you.
A
Can
you
can
look
at
that
that
QR
code
and
you
can
just
you-
can
give
some
feedback
that'd
be
really
helpful
and
then
so
we
get
started
contributing
you
just
need
to
pretty
much
assign
the
CLA,
which
is
either
done
as
an
individual
or
through
your
company
you,
you
can
just
start
by
looking
at
any
issues
of
of
anything
that
you
see
there
and
and
just
go
forth
and
look
at
the
issues
and
and
usually
it's
pretty
easy
and
there'll
be
very
simple
ones.
Kind
of
like
this
whole
server
nickname.