►
From YouTube: Introducing Kong Gateway Operator
Description
In our next #KongBuilders #livestream on November 16, Viktor Gamov from Kong will deep dive into Kong Gateway Operator.
Kong Gateway Operator is a next-generation deployment mechanism founded on the operator pattern that allows Kong Gateways to be provisioned in a dynamic and Kubernetes-native way, enabling automation of Kong cluster operations and management of the Gateway lifecycle.
A
A
B
What
is
happening?
Everybody
welcome
welcome
to
Kong
Builders
Kong
Builders.
It's
the
weekly
bi-weekly
two
times
a
month
show
where
I'm
going,
live
and
trying
to
hack
something
around
and
show
you
how
how
I'm
doing
sometimes
it
happens
to
be
a
pretty
huge
success.
Sometimes
it's
the
absolute
epic
fail.
Hopefully
today
is
going
to
be
a
huge
success,
so
welcome
before
we
start.
If
you're
watching
us
live.
If
you're
watching
us
live,
there's
a
small
chat
window.
B
Just
let
me
know
if
you
can
hear
me
well,
see
me
well
things
that
I
see
on
my
site.
It
looks
like
everything
goes
nice
and
everything
goes
smoothly
and
sounds
great,
but
let
me
know,
let
me
know
how
does
it
sound
on
your
side
and
loud
and
clear,
loud
and
clear?
I
see
that,
let's
test,
if
I
have
the
commenting
option
is
working
loud
and
clear
thanks
Carl
for
joining
us.
Let
me
see
if
I
can
do
this
one
bigger
yep
bigger.
B
All
right
so
looks
like
we're
going
we're
going
nice
and
strong
I
see.
The
bandwidth
is
also
good
loud
and
clear.
We
see
we
see.
People
from
from
the
LinkedIn
is
joining.
We
see
here,
let's
see
Jamal
well
welcome,
welcome
to
welcome
to
Kong
Builders
Emily.
Thank
you
so
much
for
being
such
awesome,
my
teammate
in
helping
me
to
monitor
all
this
social
channels.
I've
had
also
welcome.
Welcome
everybody.
Okay.
B
So
before
we
start
I
also
like
to
know,
I
will
be
doing
my
thing,
but
you
also
can
continue
to
write
down
in
the
comments
where
you're
coming
from.
What's
your
expertise
around
the
Quran
or
what
you're
struggling
with
I,
also
like
to
use
this
as
a
platform,
if
you
can
ask
some
some
questions,
let's
have
these
questions,
not
super
random,
so
it
would
be
somehow
related
to
to
the
topic
of
our
conversation.
It's
going
to
be
their
apis,
kubernetes,
Cloud
native.
B
What
have
you
as
I
as
it
was
announced?
We're
gonna,
be
talking
today
about
the
topic
that
I'm
personally
super
excited
to
talk
about
this
and
we're
going
to
be
talking
about
a
Gateway
operator.
So
if
you've
been
at
the
Kong,
Summit
you've
probably
seen
some
announcement
that
we
did
around
this
and
we
announced
as
a
cone
Gateway
operator
goes
into
technical
preview.
What
does
it
mean?
It
means
that
we
want
to
share
something
that
we're
building,
and
this
might
be
not
necessarily
kind
of
ready
for
Prime
Time
ready
for
production.
B
This
is
something
that
we
want
you
to
start
using
and
they
give
us
some
feedback,
so
you
can
also
participate
in
the
kind
of
you
might
have
some
some
use
cases
that
we
never
thought
that
would
be
applicable,
so
the
yeah
that
that
would
be
great.
And
yes,
absolutely
thanks
for
noticing
my
movember
stash
November.
This
is
the
in
November.
We
are
growing
mustache
to
raise
awareness
about
the
amount,
health
and
all
the
things
that
related
to
mental
health,
physical
health
of
the
man.
So
that's
that's
the
mustache!
B
Thank
you
so
much
for
noticing
this
and
as
I
can
see.
We
also
on
Twitch.
Twitch
is
great.
So
we
have
a
LinkedIn
YouTube,
twitch
Twitter.
We
we
go
in
live
on
all
the
channel.
B
What
you
like
so
today,
as
I,
said
Gateway
operator,
so
one
of
the
interesting
thing
about
these
Gateway
pattern
and
that
we
start
seeing
in
the
quite
the
recent
years
is
that
with
this,
traditional
tools
that
exist
to
to
deploy
all
sorts
of
workloads
to
kubernetes
Gateway
operator
is
actually
mirrors.
The
real
world
operator
experience.
B
So
you
have
a
system,
administrators,
a
team
of
SRE
teams,
history,
people
who
building
and
deploying
things
and
Gateway
pattern
mirrors
this
by
automating
those
things
and
that's
why
the
naming
is
a
gateway.
Conch
Gateway
is
the
product
and
a
gatewaycon
Gateway
operator
allows
to
deploy
this
into
into
your
kubernetes
cluster.
B
So
previously,
as
many
of
you
know,
that
if
you
go
to
the
docs.co.com
and
you're
looking
for
something
like
you
can
install
quonk
using
Helm
on
openshift
or
just
just
regular
Helm,
that's
what
it
is
still
a
supported
and
fully
supported
installation
approach
for
deploying
your
Quant
gateways
into
your
kubernetes
cluster.
However,
we
noticed
that
in
general,
when
we're
having
like
help
things
like
Helm,
when
we're
having
things
like
Helm,
we
more
rely
on
declarative
way.
B
So
you
kind
of
like
expressing
your
deployment
and
with
this
we
taking
this
deployment
and
just
creating
the
services
creating
deployments.
Persistent
volume
claims
database
installations,
all
those
kind
of
things.
B
So
if
you
want
to
customize
some
of
the
behavior,
there's,
there's
not
much
room
for
for
doing
this.
So
one
of
the
approaches
how
the
people
doing
is
just
embed
the
shell
scripts
inside
your
Helm
stuff
and
doing
some
of
the
some
of
the
customization
it
is.
It
is
kind
of
like
I'm
hacking
and
it
works.
B
It
solves
some
of
the
problems
that
people
might
have
with
this
type
of
installation,
but
it
is,
in
my
opinion,
a
little
bit
hacky
because
you
have
a
yaml
and
you
have
a
shield
shell
script
built
in
inside
the
yam.
Also,
in
my
opinion,
it
is
not
something
that
very
easy
to
maintain.
So
what
we're?
Thinking
with
this?
B
We
can
find
something
like
a
concept
of
operator
pattern
that
is
right
now,
I'm
not
showing
this
to
you,
which
is
unfortunate
here
we
go
operator
pattern.
It
is
something
that
already
widely
adopted
is
the
way
how
you
can
Implement
very
complex,
maybe
not
very
complex,
but
the
the
installations
where
you
need
to
deal
with.
You
know
some
of
the
complex
things.
B
It's
a
yes,
it's
nearly
impossible
to
get
the
syntax
correct
with
shell
inside
the
yaml
file.
That's
perfect,
I
I
need
to
screenshot
this
comment
in
the
post
everywhere
on
Twitter,
because
it
is.
It
is
generally
true
statement
in
many
cases,
but
you
think
about
this.
So
the
operator
pattern
is
something
that
allows
you
to
rely
on
experience
of
the
people
who
already
done
it
and
we
rely
on
experience
of
teams
that
work
say.
B
You
know
we
have
a
like
a
field
of
field
teams
who
work
on
in
the
on
deploying
this
Gateway.
We
have
experience
of
Cloud
team
who
run
the
Quan
connect,
which
is
our
Cloud
offering
and
is
being
like
a
true
software
company
that
also
consumes
the
software
that
they
built.
We
also
use
some
of
the
con
Ingress
controller
bits
inside
our
Cloud
offering
so
we
we
do
in
our
drinking
our
champagne
or
eat
our
dog
food.
B
So
with
the
operator
you
will
be
relying
on
someone's
work
already,
so
there's
a
open
source
operators.
There
are
some
commercial
operators
so
and
we
have
a
Quant
Gateway
operator,
which
is
comes
in
a
technical
preview.
So
I
think
that's
enough
for
the
premise
again,
if
you
have
any
confusion,
why
it
is
important,
why
how
this
will
work
potentially
in
the
future,
it
will
proceed
Helm
deployment
and
you
will
get
very
yes,
it's
going
to
be
opinionated
so,
but
as
a
user
of
a
complex
tool,
you
really
want
to
rely
on
yeah.
B
So
is
a
user
all
very
complex
tool?
You
want
to
rely
on
the
best
practices
you
want
to
rely
on
something
opinionated
and,
and
things
like
that,
so
for
the
next
for
the
next,
like
30,
40
minutes,
I'm
gonna
be
walking
you
through.
What's
what
involves
in
installation
and
how
you
can
use
it.
B
However,
as
always,
I
do
have
a
short
version
if
you're
super
busy,
if
you're
super
busy
with
with
your
life-
and
you
don't
have
a
time
to
join
me,
so
I
build
this
video
where
I
it's
under
seven
minutes.
I
did
the
deployment
of
of
the
Quan
Gateway
operator.
I
should
deployed
a
demo,
and
you
can
always
watch
this
afterwards.
B
Here
I'm
gonna
be
like
explaining
many
many
other
steps,
also
from
if
you
missed
some
of
the
announcements
that
came
from
the
Quantic
Summit,
you
can
watch
my
keynote
part
where
I
announced
a
project
called
incubator.com
issue.com.
That's
the
website,
incubator.com
hq.com.
B
This,
let
me
show
you
boom.
This
is
where
we
will
be
putting
more
and
more
projects
that
we.
A
B
And
we
will
be
building
more
and
more
stuff,
so
Gateway
operator.
This
is
what
we're
going
to
focus
today,
all
right
and
also
as
always,
you
can
go
and
check
everything
that
I
will
be
doing
today
is
in
our
GitHub,
conk
and
demo
scene.
So
the
repository
that
will
include
all
the
demos
I
will
push
this
demo.
That
I
will
be
showing
today,
and
you
will
be
able
to
do
this
yourself.
There's
a
fully
automated
version,
but
I
will
walk
you
through
the
steps
and
explain
what
is
going
on
there.
B
So
we're
gonna
we're
gonna
start
by
looking
to
these
instructions
in
incubator
website.
So
essentially,
the
this
approach
of
operator
allows
us
also
to
test
drive
some
of
the
Innovations
and
one
of
the
biggest
innovation
in
the
world
of
kubernetes.
Networking
that
relevant
for
Quang
as
a
as
a
company
or
as
an
open
source
project
is
emergence
of
Gateway
API.
B
So
kubernetes
Gateway
API,
it's
essentially
the
way
how
a
new
API
for
managing
it's
it's
a
new
API
that
will
be
by
functions.
It
will
supersede
Ingress
API,
but
it
will
not
make
it
deprecated
or
whatnot.
You
still
will
be
able
to
use.
Ingress
is
a
feature
complete,
so
Ingress
is
done.
It's
stable.
You
can
use
it
anywhere
where
you're
using
kubernetes.
B
Now,
with
with
Gateway
API
community
and
the
special
interest
group
around
the
networking
decide
to
well,
the
Ingress
has
a
certain
limitations
in
terms
of
what
kind
of
workloads
can
be
done
and
how
the
things
need
to
be
configured
and
how
you
can
interact
with
underlying
Gateway.
That
will
be
taken
care
of
actually
pushing
your
traffic
through,
because
only
thing
that
you
have
in
Ingress
is
essentially
Ingress
class,
so
essentially
you're
mentioning
the
Ingress
controller.
That
would
be
responsible
for
handling
this.
This
Ingress
so
there's
much
more.
B
Maybe
complex
configuration
needs
to
come
into
play
and
with
Gateway
API.
These
things
will
be
also
available
for
for
you
to
to
to
to
to
use
also
that
my
personal
favorite,
probably
is
the
good
separation
of
concerns
as
a
developer
and
I
just
want
to
make
sure
that
my
workloads
would
be
exposed
to
outside
world.
And
if
you
are
going
to
have
a
HTTP
route,
this
HTTP
route
will
be
will
be
provided
as
a
developer.
B
This
separately
from
you
know,
from
my
application
site,
so
I'm
support
we're
separating
concerns
of
developers
from
separating
of
from
concerns
of
operators,
so
the
yeah,
so
let's,
let's,
let's
focus
on
we're
gonna,
be
I-
will
be
wearing
all
these
hats
today,
with
with
different
hats
and
as
an
infrastructure
provider,
cluster
operator
or
whatever
so
I
already
have
a
my
current
cluster
deployed,
and
let
me
do
this:
one
I
will
start
K9s
in
my
cluster
and
after
that
we
will
be
switching
back
and
forth
and
seeing
what
I
have
here.
B
So,
let's
do,
let's
do
notes.
B
B
It's
would
be
unnecessary
step
because
all
these
crgs
will
be
installed
by
default
and
if
I'll
just
do
key
get
gateways,
Server
doesn't
have
any
resource
of
traffic
Gateway.
So
it
is
error.
So
there's
no
there's
nothing
installed
here.
So
there's,
no
there's
no
crd.
So
the
things
that
we
will
do
is
just
to
go
ahead
and
install
this
thing.
With
this.
The
Gateway
API
service
I
think
the
current
state
of
this
is
five
0.5.
Let's
take
a
look
so
if
I
will
go
into.
B
I
GitHub
repository
for
a
Gateway
API
kubernetes
Sig
in
the
config
folder
I
will
get
my
crgs
and
you
see
there
is
a
work
happening
around
adding
some
other
routes,
but
we
interested
in
releases
so
right
now
it's
the
current
release,
so
we're
going
to
be
using
this
one
and
also
I,
will
update
my
demo
previously
I
used
previously
I
used
0.5.0,
but
this
should
work
as
well
without
any
problems.
B
So
we're
going
in
and
installing
this
using
a
customize
command
and
the
way
how
it
works
in
in
customize.
If
I
will
go
here
into
customization,
the
the
the
customize
will
figure
out
how
to
get
all
these
things.
And
now,
if
we're
looking
into
standard,
we
will
have
a
three
things
that
we're
going
to
be
using
in
this
demo,
because
if
this
will
be
successful
and
you
you
would
like
to
learn
more,
we
can
go
with
more
advanced
use.
Cases
like
I'll
I'll
talk
about
this
later
now.
B
We're
gonna
need
this
Gateway
class
crg
that
will
be
allows
us
to
Define
kind
of
the
type
of
gateway
gateway
that
will
be
representing
actual
instance
of
Gateway
class
and
we're
going
to
be
using
today
HTTP
route,
which,
because
it's
the
only
one,
only
one
API-
that
is
already
part
of
the
beta
or
beta
version
of
this.
So.
B
So
customize
will
read
this
customization
file
and
install
only
those
crds.
So
that's
what
we're
going
to
be
doing
now.
B
Now
you
see,
the
error
is
now
is
different,
so
the
server
doesn't
have
any
resource
type
of
gateways
because
we
just
installed
the
crds
and
if
I'll
just
do
okay
get
crds
and
looking
for
Gateway
there
would
be
a
bunch
of
things
that
we
just
installed.
You
know
so
we
we
just
apply
this
and
install
this,
and
we
we
are
good
good
to
go
now
with
the
with
this
next
step.
B
It
would
be
installing
some
of
the
quonk
related
crd,
so
now
con
Gateway
operator
built
on
top
of
the
knowledge
that
we
gained
through
building
con
Ingress
controller
and
essentially
concrete
controller
that
you
installed
through
the
helm.
Is
this
kind
of
thing
that
you
running
today
in
production,
so
the
custom
resources
for
Quant?
Let's
see
if
I
will
just
do
nothing
here,
NFL
just
get
get
plugins.
B
Plugins,
so
it
doesn't
have
resource
plugins
or
resource
Quant.
Plugins.
There's,
nothing
is
here
so
Gabriel
is
asking
question,
is
Quant
API
Gateway
compliant
need
a
little
bit
more
information
from
your
Gabrielle.
What
does
it
mean
compliant
and
compliant
to
what
I
understand
this
kind
of
like
a
word
play
with
the
Gateway
API
API
Gateway,
and
all
this
kind
of
things
is
confusing.
Trust
me
I
feel
this
pain,
but
there's
nothing
more
difficult
in
computer
science
than
naming
things
so
yeah.
So,
okay.
B
So
the
great
question
is
this:
the
same
as
the
colon
Congress
controller.
We're
going
to
talk
about
this
in
a
few
seconds.
I
will
show
you
how
all
these
things
that
you
learned
from
the
years
of
using
Quan
still
can
play
out
with
this
architecture,
and
this
is
actually
quite
quite
interesting,
so
stay
tuned
for
I,
don't
know
a
few
few
minutes.
I'll
show
you
how
all
these
things
are.
You
know
work
together,
okay,
so
the
question
is:
okay,
so
is
counk.
Gateway
is
kubernetes,
Gateway
API
compliant.
B
Yes,
it
is.
It
is
the
it's
not
the
reference,
there's
no
such
thing
as
a
reference
implementation,
but
one
of
the
engineers
who
work
on
the
specifications
and
one
of
the
engineers
who
run
co-chairman
of
this
special
interest
group.
It
happens
to
be
the
same
person
and
it
happens
to
work
at
Kong,
Shane
odd,
shout
out
to
him
and
there's
another
gentleman
Rob
Scott
from
Google.
They,
they
co-um
coach
chairmans
of
this
specification.
B
So
as
you
should
expect,
Google
support
for
Gateway
API
in
the
Quan
support
for
Gateway
API
is
quite
Stellar.
So
that's
what
we're
going
to
be
drilling
down
in
in
this
in
this
series
now
with
this
where's.
My
so
next
thing
is
that
we're
doing
the
same
thing
we're
installing
Quant,
related
crds,
so
I
showed
you
that
there's
no
conch
plugins
we're
gonna
do
oops
just
too
much.
B
Okay,
we're
gonna,
install
Quant,
Gateway
crdis,
as
you
can
see
here
now,
if
I
will
just
do
some
of
the
crgs
Quant
consumers,
Ingress
plugins,
DCP
Ingress,
so
all
the
things
that
Quran
Ingress
controller
knows
how
to
handle
those
things
are
here
and
those
things
will
be
used
the
to
to
to
run
this
this
software
now.
So
there
is
a
thing
called
a
new
project,
Quant
Gateway
operator
docs.
B
That's
the
public
public
facing
repository
where
all
the
installations
crgs
will
will
be
so,
for
example,
if
I
go
to
CRT
all
this
customizations
that
we
need
to
install
those
things
are
available
here.
B
So
as
of
right
now,
corn
Gateway
operator,
it
is
not
all
these
installation
things
and
all
this
stuff
that
you
can
do
is
is
there,
but
actual
bits
of
you
know
go
code
that
do
the
things
are
not
still
in
the
in
in
the
private
repository
we
we're
working
on
making
this
available
for
public
in
one
way
or
another,
so
it
is
right
now
in
the
technical
preview.
So
we
we
give
you
access
to
bits
of
these
like
binary
bits
and
documentation
bits
and
by
the
way
this
is
the.
B
This
is
the
where
this
is
the
where
you
we
can
use
some
of
the
help
from
from
the
community.
So
if
you
go
to
this,
let
me
see
if
I
can,
if
I
can
comment
myself
to
this
one,
no
it
doesn't
look.
I
can
I
cannot
send
the
messages
to
chat,
but
if
you're
watching
this
in
the
recording,
these
links
will
be
best,
links
will
be
in
the
description
down
below
now,
the
let's,
let's
install
a
Gateway
crds,
we
install
crds.
B
Now,
let's
install
let's
install
quonk
Gateway,
so
if
I'll
just
go
get
gateways,
so
there's
no
Gateway
resources
available
here
now,
I
want
to
install
a
quonk,
Gateway
operator
bits.
B
B
Curator
controller
manager,
so
this
is
what
I
was
saying
when
I
was
talking
about
the
naming.
Things
are
hard
so
before
before
operator,
pattern
established
certain
nomenclature
in
naming
in
the
things
some
of
the
the
custom
code
that
you
run
inside
your
kubernetes
cluster
would
call
it
controller.
B
So
so
we
have
a
con
gate.
Con
Gateway
operator
controller
that
controls,
Quant,
Gateway
operator
and
manager,
manages
controller
I.
Guess
I,
guess
that's
the
that's
the
that's
the
idea,
and
this
is
basically
the
guy
that
will
be
responsible,
something
that
is
a
entity
that
will
be
responsible
for
creating
the
instances
of
of
the
gateways
which
we
will
do
in
the
next
step.
B
If
I'll,
just
you
can
get
gateways,
we
still
don't
have
a
gateways
because
we
didn't
create
those
as
a
Next
Step.
We
just
want
to
make
sure
that
my
installation
is
stabilized,
so
I
will
be
able
to
see
if
everything
is
up
and
running.
Everything
is
up
and
running,
so
the
the
deployment
is
up
and
running
now.
So,
let's,
let's
take
a
look
on
on
the
things
that
we
can.
We
can
do
with
these.
B
In
order
to
in
order
to
start
playing
around
with
this,
we
need
to
create
a
Gateway
class
so
inside
the
it's
kind
of
like
a
specification
convention
that
we
create
Gateway
class
and
in
order
to
control
the
crg.
So
in
order
to
react
to
the
crd,
we
need
to
specify
a
controller
that
will
be
listening
to
this
one
and
if
I
will
just
go
see
the
default.
B
And
I'll
just
do
zero
one,
creating
a
Gateway
class
and
I'll
just
do.
B
So
we
created
a
Gateway
class
and,
let's
see
if
we
have
this
where's,
the
status
status
conditions
accepted
through
so
we
created
this
Gateway
class.
So
if
you
are
familiar
with
the
object,
oriented
programming
class
we'll
be
defining
some
of
the
entity
now
we
need
to
create
instance
of
this,
and
for
this
we're
going
to
be
using.
B
Where
is
it
we're
going
to
be
using
this
Gateway
object?
So
one
of
the
configurations-
and
this
is
by
the
way-
comes
from
specification
if
I'm
going
into
Concepts
and
we're
going
into
API
overview,
we
have
a
Gateway
class.
This
is
clear
explanation
what
it
does
very
similar
to
other
classes
of
things
that
you
might
have
in
your
kubernetes
cluster.
B
That's
why
they
use
the
example
of
Ingress
class
that
we,
you
know,
know
from
the
Ingress
and
also
the
the
the
storage
class
if
you're
running
this
with
the
persistent
volume
claims
and
things
like
that
right.
So
this
is
the
kind
of
common
something
some
entity
that
describes
the
common
behavior
of
Gateway.
B
The
next
thing
is
that
we
have
actual
instance
of
getaway.
This
is
the
point
where
the
we
create
Gateway
objects.
So,
what's
going
to
happen
here,
when
the
controller
that
responsible
for
understanding
instances
of
Gateway
class
will
get
this
resource,
it
will
know
how
to
spin
actual
software
that
will
be
pushing
traffic.
In
our
case,
it
will
spin
up
two
things:
two
two
two
things:
it
will
spin
up
a.
B
Clunking
grass
controller,
which
is
gonna,
be
a
data
plane
and
controller
thing
that
will
be
understanding
and
interact
with
the
resources
in
kubernetes
and
that
will
spin
up
data
plane
that
will
be
represented
by
actual
instance
of
code.
So
let's
take
a
look:
how
we
can
do
this.
B
B
There's
nothing
on
the
clunk
system:
let's
go
to
namespaces
all
them
spaces
and
I'll
just
do
gateways
in
namespace
default.
We
created
a
Gateway
with
class
conk
with
address
of
this,
which
we
will
return
in
a
second,
but
let's
take
a
look
into
namespace
default
and
we're
gonna
do
into
deployment.
We
have
a
two
deployments
now
here
and
those
deployments
were
created
by
operator
these
deployments,
for
example,
data
plane
will
be.
Let's
let's
see
describe,
this
is
actual
data
plane.
This
is
actual
the
Quant
beat
that
will
be
running
your
traffic.
B
So
that's
why
you
can
see
all
this
configuration
is
pre
pre-configured
and
all
these
things
can
be
customized
and
can
be
modified
the
same
way
as
you
would
expect
for
just
configuring
one
outside
of
kubernetes
and
let's
take
a
look
so
scaling
replica,
says:
let's
see,
condition
available
medium
requirements
available
new
okay,
so
it
looks
like
it's
it's
up
and
running
and
what
is
a
control
plane?
So,
let's
take
a
look:
what's
the
what's
the
control
plane
here
and
the
control
plane
is
actually
a
quantity
and
grass
controller.
B
So
the
architecture
of
this
looks
something
like
this.
We
have
a
kubernetes.
Let
me
I,
don't
have
anything
to
draw
on
this
on
my
screen
today,
so
I
will
be
using.
My
I
will
be
using
my
hands
so
so
the
this
architecture
allows
us
to
have
some
manager,
that's
small,
tiny
thing
that
will
be
sitting
there.
Listening
all
these
configurations
from
Gateway
apis
in
Gateway
class
Gateway
and
we'll
be
installing
actual
software,
and
one
of
the
things
that,
if
I'll
go
back
into
here
and
see
if
I'll
just.
A
B
Get
gateways
it
gives
me
address
so
if
I'll
go
ahead,
just
copy
this
and
do
something
like
http.
B
I
get
the
response.
I
get
the
response
from
from
from
con
data
plane
other,
for
example,
some
other
implementations.
You
might
have
a
different
response,
and
the
cool
thing
is
that
you
can
have
multiple
gateways
configured
the
same
way
as
we
configure
this
Con
Gateway,
but
those
things
can
be
can
have
like
different
outcomes
in
the
response.
Initial
response
would
be
different,
for
example,
Kuma,
which
is
the
service
mesh
that
we
also
develop
here
at
Kong.
B
Kubernetes
Gateway
API,
so
Kuma
also
supports
a
kubernetes
Gateway
API
and
the
kuma
Gateway
built-in
Gateway
that
allows
to
traffic
fly
into
into
our
cluster
also
can
be
configured
here.
But
if
you
try
to
hit
this
URL,
you
will
not
get
anything
because
the
way
how
default
behavior
is
that
you
will
acquire
address,
but
there's
no
one
who
will
respond
responding
to
this
request.
So,
let's
see
what
the
comment,
let
me
see
if
I
can
fix
that?
B
Oh
okay,
so
it's
a
bigger
big
of
the
comment,
so
I
need
to
somehow
make
this
smaller.
So
that's
unfortunate
need
to
need
to
think
how
I
can
use
this
so
can
I
deploy
wrong
if
I
don't
have
a
cluster
admin
access
or
is
the
minimum
access
level
for
the
role
if
I
need
the
very
good
question?
So
if
you
don't
have
this
access,
you
need
to
have
someone
who
will
be
able
to
at
least
provision
a
just
crds
provision,
the
manager
once
you
provision
the
manager
all
this
required.
B
Our
back
rules
will
be
configured
and
after
that,
if
you
need
to-
and
the
Gateway
obviously
will
be
created.
This
is
a
this.
Is
where
this
is
where
this
picture
comes
into
play
and
as
a
if
you
have
this
abilities
to
deploy
this
you
can't
deploy.
If
you
don't
have
the
ability
to
deploy
those
things,
you
need
to
work
with
your
system,
administrators
or
or
whoever
will
be
provided,
deploying
the
things
as
a
developer.
B
B
The
also
like
all
this,
like
the
minimum
required
rules,
is
described
in
in
if
we're
going
into
here,
going
into
config
look
into
our
back
and
all
the
roles
are
described
here
and
you
will
be
able
to
see
what
kind
of
roles
in
the
will
required
to
get
access
to
certain
API
calls.
I
hope
makes
sense
now,
okay,
so
the
next
thing
is
that,
as
I
mentioned
from
this
picture,.
B
The
next
thing
is
that
I
mentioned
from
this
picture
is
that
now
we
have
a
class
deployed
Gateway
deployed
now.
Next
thing
is
that
let's
deploy
application
traditionally
the
viewers
of
the
show
who
are
not
the
first
timers,
they
know
that
have
a
the
application
that
I
use
in
all.
My
in
all
my
demos
and
in
my
demos,
I
use
application
that
called
a
code
service,
so
code
service
is
just
the
dummy
application
that
calls
rest
and
point
and
generates
some
the
random
quote.
B
Deployment
Back
to
Future,
so
it
will
have
a
two
things.
Let's
take
a
look
first,
how
does
it
look
like.
B
And
I'm
going
into
default,
namespace,
there's
looking
for
the
service
and
I
do
have
a
service
called
back
to
future
quote
service.
Just
let's
do
just
the
quick
port
forwarding
and
we
will
get
into
the
point.
Gcp.
B
This
is
a
Back
to
Future,
quote
some
of
the
things
that
I
also
added
here
for
to
to
explain
if
I
need
to
explain
some
of
the
load,
balancing
things
and
all
the
things
that,
as
a
header,
this
application
also
Returns
the
the
port
name,
the
port
name
of
this
application.
So
in
this
case
it's
a
58.45.
B
A
look,
it
is
a
I,
have
a
two
pods,
as
you
can
see
here,
and
those
pods.
The
reason
for
that,
because
I
have
a
two
replicas
just
to
demonstrate
the
load,
balancing
Works
in.
B
So
in
this
particular
case,
since
I'm
using
port
forwarding,
this
port
forwarding
only
will
be
attached
to
one
particular
one
particular
pot,
so
when
I
will
be
using
this
Gateway
API,
I,
think
or
HTTP
route,
rather,
you
will
see
how
the
load
balancing
works.
As
you
can
see
here,
it's
still
hitting
the
same
same
pod,
all
the
time
which
is
by
Design.
B
And
let
me
delete
this
port
forwarding,
so
we
will
not
get
confused
now
so
first
and
simple
thing
that
we're
going
to
be
trying
to
do
is
to
enable
first
each
GP
route
so
as
a
developer
HTTP
route.
This
is
something
that
you
will
be
shipping
your
with
your
application.
Similarly,
it's
very
similar
to
what
you
did
with
with
Ingress
with
this
HTTP
route,
so
HTTP
route
has
this
parent
ref.
B
It
should
be
route,
that's
the
resource
that
will
be
used
to
multiplexing
HTTP
connection.
B
A
strong
word
for
for
handling
HP
connections-
and
this
is,
let
me
see
less
the
comments
so
does
Gateway
scale
horizontally.
So
if
we're
talking
about
Quant
Gateway
that
will
be
running
here.
Yes,
that's
the
plan
to
support
this
in
support
integration
with
horizontal
autoscaler
within
kubernetes,
as
of
right
now,
I'm
not
sure
about
the
current
status
of
this,
because
we
still
are
doing
a
some
sort
of
the
technical
preview,
but
eventually
we
would
love
to
have
this
feature
as
well.
If
it's
not
there,
I
highly
recommend
you
to
do
next.
B
And
open
issue
just
open
issue,
and
we
can.
We
can
have
a
discussion
around
this
feature
as
well.
Not
the
issue
issue
will
be
open
in
the
grass
controller
and
open
discussion
here.
Let's
see
what
kind
of
feature
he
is
and
you
can
support
the
versions
of
data
plane,
control
plane,
the
yeah
that's
for
conformance
now.
Another
question
is,
would
you
recommend
multiple
gateways
in
production
or
one
could
serve
10
thousands
of
apis?
It's
really
depends
on
your
use
case
because
go
on
can
handle
multiple
in
hundreds
of
different
apis.
B
B
While
I
was
responding,
this
question
I
just
got
this
idea.
Maybe
it
will
be
crazy,
but
would
you
folks
would
be
interested
in
this
kind
of
like
a
the
Kong
Builders
when
we're
gonna
be
trying
to
you
know,
push
some
of
the
performance
stuff,
just
just
an
idea.
I
know
that
the
performance
usually
is
very
hot
topic.
So
let's
do
this
one,
okay,
so
if
now
I
will
be
sounding
like
really
pesky
YouTuber
by
the
way
subscribe
to.
B
Please
follow
me
on
Twitter
over
here,
somewhere
all
also
subscribe
to
this
channel.
Let's
do
this
one
if
this
video,
this
video
will
get
100
likes.
B
Probably
it's
easy,
like
hundreds
of
people
watching
this,
this
Channel
and
getting
100
likes,
it
would
be
easy
once
this
video
Hit
100
likes
I
will
record
Another
live
stream
where
we
start
talking
about
performance
in
kubernetes,
and
we
will
start
playing
around
with
of
all
this
like
scaling,
stuff
and
breaking
things
on
purpose,
with
the
sake
of
the
performance
testing,
and
we
answer
to
the
question
of
Gabriel
about
the
the
performance
about
multiple
100
000
CPI
versus
the
different
gateways
handling
different
different
routes.
So
it's
up
to
you!
B
B
Oh,
it's
important
we're
going
to
use
a
routing
by
hostname
if
I
would
use
if
I
would
use
a
DNS
as
a
hostname,
and
this
will
route
to
My
Back
to
Future
Port.
If
I
would
using
this
as
a
host
host
header
in
my
HTTP,
it
should
be
cool.
Then
this
thing
will
I
need
to
provide
this
hostname
when
I'm
looking
into
Gateway
API,
so
refer
related
documentation,
we're
looking
into
where?
Is
it
no?
No!
No!
No
I'm!
Looking
into.
B
Into
HTTP
route
and
specifically,
I'm
interested,
in
example,
of
HTTP
route
of.
B
A
B
Exposure
begins,
I
was
wondering
there's
if
there's
a
like
a
full
API
somewhere
introduction.
Let's
see,
guides
HTTP
routing.
B
Okay,
so
that's
the
first
thing
that
HTTP
route
based
on
hostname
example,
Gateway
based
on
hostname,
that's
the
first
thing
that
we're
gonna
try,
and
this
is
something
that
I
already
did.
I
know
this
works.
So
that's
why
I'm
pretty
confident
on
doing
this
type
of
jazz?
Let's
do
this
one
HTTP
route
by
host
now
I
know
that
I
need
to
bring
probably
the
best
HTTP,
probably
the
best
HTTP
client
out
there.
We
need
to
bring
the
insomnia
into
default.
B
All
right
here
we
go
uh-huh
and
that's
gonna
be
my
hostname
that
we're
gonna.
Let's
see
if
we
are
getting
any
responses
and
let's
close
this
one,
send
response
again,
we
should
get
no
routes
matched
and
when
I
enable
host
header
right
now,
so
I
enabled
host
header
and
holds
It
Back
to
Future
calling.builders.
Actually,
content
Builders
is
a
real
real
URL.
You
can
go
and
check
this
con.builders.
It's
a
real
URL
trust
me
and
when
I
hit
this,
we
get
the
get
the
response
now
interesting
enough.
B
What
I
want
to
show
you
that
is,
that
watch
for
the
send
or
repeat
on
interval
two
seconds
and
watch
if
these
different
portal
switching
to
different
names.
B
Because
now
the
load
balancing
is
working,
I
have
a
two
two
two
I
have
a
two
replicas
two
replicas
two
replicas
of
my
pod,
that
deployed
inside
the
grass
cluster
and
now
my
gateways
handles
this.
You
see
it's
via
con
3.0
and
also
the
it's
hitting
the
hitting
these
different
backends.
B
The
Next
Step
that
I
want
you
to
show
you
today
before
we
before
before
we
drop
in
so
this
is
going
to
be
like
a
foundation
of
installing
things
and
when
the
in
the
next
streams
we're
going
to
explore
some
other
some
other
cool
things
that
available
in
gateways,
so
Gateway
configuration
so
Gateway
configuration.
B
Is
it
something
that
not
described
in
in
Gateway
spec?
B
But
because
you
see
here
it's
a
part
of
a
Quant
Gateway
operator.
This
is
the
where
you
actually
will
be
able
to
customize
this
deployment.
You
will
be
able
to
customize
this
deployment
and
provide
the
different
configurations
before
I
jump
right
in.
Let
me
answer
the
question:
is
there
any
way
I
can
do?
B
B
The
just
too
much
text
on
the
screen
so
in
the
mesh
control
plane
case
are
there
requests
proceed
on
the
control
plane
or
our
side
guards
talk
to
each
other
directly.
Yes,
so
same
thing
with
the
mesh.
The
control
plane
is
not
involved
in
in
handling
any
in
your
request
stuff.
It's
it's
solely
purpose
of
handling
interaction
with
the
underlying
apis.
B
Similarly,
with
the
very
similar
to
the
things
that
we
have
with
the
control
plane,
data
plane
separation
in
the
Gateway
side
of
things,
quonk
Ingress
controller
never
handles
your
traffic.
Only
quonk
Gateway
handles
your
traffic.
So
that's
this,
that's
the
gist!
B
So,
let's,
let's
update
this
one
so,
but
by
default,
as
we
can
see
here
in
our
application
right
now,
we're
using
this
Quant
Gateway
Quan,
open
source,
just
I
just
want
to
see
if
I
will
be
able
to
use
Chrome
Gateway
image
potentially
so
if
I
go
to
do,
Hub
Hub
that
docker.
B
We
will
deploy
configuration
and,
after
that,
in
my
Gateway
class
I
will
attach
this
configuration
into
my
Gateway.
So
the
the
configuration
will
appear
inside
my
height
yep
now
container
image.
I
will
use
corn
con
Gateway,
just
for
example,
just
to
demonstrate
how
they
think
and
how
the
Gateway
operator
will
handle
the
upgrades.
The.
B
And
I'll
just
do
upgrade
again
what
it
will
do,
create
the
Gateway
configuration
and
update
Gateway
class
that
will
use
this
configuration.
Oh
shoot.
B
Configuration
invalid
in
a
valid
value
is
integer
must
be
string
what
let's
see
Gateway
data
pool
engine
deployment
version
invalid
value,
integer
spec
data
plane
version,
but
it
must
be
type
of
string
integer.
What
is
wrong
with
you?
Let's
do
this
one.
If
this
will
work,
let's
see
if
this
will
work.
B
B
Now,
in
a
few
seconds,
we
should
be
able,
if
I,
did
everything
correctly,
there's
a
chance
that
I
screwed
up
as
always
because
it's
the
the
Kong
Builders
data
plane.
Let's
see
if
data
plane
is
running
a
correct
version,
something
is
not
right.
B
Let's
see
if
I
will
go
and
do
things,
Kong,
namespace,
foreign
system
manager
and
manager
will
be
responsible.
Okay.
So
let's
see
error,
reconcile
error
data,
plane,
Gateway
controller
kind.
Then
then.
B
Pray
to
Jason
and
let's
see-
and
we
just
do
make
it
pretty
yeah,
because
it's
apparently
it's
not
the
it's,
not
the
Json
reconcile
error
controller
data,
plane
kind
that
the
plane
blah
blah
blah
named
space
default.
B
Oh
yeah,
because
I'm
using
the
I'm
copying
this
from.
If
I
will
can
I
do
this,
will
it
work
yeah,
no
copying
stuff
from
the
from
the
console
tool
is
not
super
easy.
B
B
Maybe
it
is
something
that
that's
very
that's
very
weird:
let's
see
if
I'll
just
do
it
in
zero.
Something
like
this!
Maybe
it's
something
to
do
with
this
type
of
thing.
B
Configured
so,
let's
see
reconcile
air
still
reconcile
air
steel
image.
Quant
a
Quant
Gateway
I
need
to
investigate
this.
But
meanwhile,
let's
get
back
to
say
the
old
version,
maybe
I'm
missing
something
I
need
to
I
need
to
look
it
up
and
see
if,
if
I'm
actually
missing
something.
B
Unsupported
data,
plane
images,
so
I
believe
this
is
something
that
I'm
doing
wrong
with
the
with
the
naming.
Let's,
let's
take
a
look
on
the
documentation,
shall
we
the?
Where
is
it?
Where
is
it
issues
we're
going
into
here
operator
docs?
Let's
see
to
do
incubator
website,
blah
blah
blah
full
documentation,
normally
yeah,
let's
see
container
image
that
should
work
and,
let's
see,
if
we'll.
A
B
Let's
see,
let's
see
what
am
I
missing:
container
image:
okay,
okay,
so
we're
not
doing
this
right,
we're
doing
this
right
right.
So,
let's
see
2.8,
you
know.
Are
we
going
to
be
doing
3.0.
B
Do
you
upgrade
and
we're
going
back
here.
B
That's
weird:
that's!
This
is
really
weird
where
documentation
doesn't
align
with
the
doesn't
do.
B
I'm
wondering
if
it's
a
Quant,
Quant
Gateway
3.0
data,
plane
control,
plane
data
plane.
That's
really!
That's
really
weird
I
need
to
investigate
this,
but
this
is
actually
a
good
thing
that
I
will
leave.
You
I
will
leave
you
hanging
this,
because
this
is
the
thing
that
I
will
probably
will
take
for
the
for
the
next
week.
For
now
now
you
know
how
to
install
Gateway,
at
least
it
works.
At
least
it
works
in
in
some
capacity
right.
B
At
least
it
works
at
some
point
yeah,
so
stick
around
for
maybe
next
week,
where
I
will
investigate
this
problem,
and
we
will.
We
will
talk
about
this
next
time
for
now.
Where
is
it?
Where
is
it
please
by
all
means
and
watching
this
Statistics
and
many
people
not
subscribing
to
this
YouTube
channel
and
not
enable
touch
this
touch
this
Bell
and
enable
notifications?