►
From YouTube: API Gateway decK With CI/CD
Description
In this demo from Kong Summit, Michael Heap introduces Kong’s declarative configuration capabilities and how to use your CI system to lint and apply these configurations in a variety of environments. Test your changes in a staging environment, then apply exactly the same config to production with a click of a button.
Try Kong Gateway: https://konghq.com/install/
For more Kong demos and use cases, watch our Kong Summit 2021 videos: https://konghq.com/kong-summit/2021-videos
▬▬▬▬▬▬ TIMECODES ▬▬▬▬▬▬
0:00 Intro
1:07 Introducing decK
2:08 Configuring Kong Gateway (Add service, route and plugin)
5:37 Using decK With CI/CD
9:16 Reviewing Changes
13:12 Distributed Configuration
14:38 From Zero to Running With Kong, Pulumi, Ansible, and decK
#APIgateway #CICD #decK #KongGateway
A
A
A
A
A
few
years
ago,
I
wrote
a
book
on
configuration
change
management
with
ansible
for
red
hat
and,
despite
that,
I've
still
broken
production
with
a
configuration
change.
Recently,
let's
start
by
introducing
deck
a
configuration,
management
and
drift
detection
tool
for
kong.
Now,
that's
a
bit
of
a
mouthful.
So
what
does
it
actually
mean?
A
Well
that
can
both
export
and
import
your
service
configuration
providing
backups
and
a
way
to
save
your
state
as
a
text
file,
it
can
run
the
diff
between
your
proposed
configuration
and
actual
config.
You
can
validate
a
declarative
configuration
file
and
automate
distributed
configuration
changes
in
a
cid
cd
platform.
A
A
A
A
A
A
So
this
has
worked
pretty
well.
We
made
a
change
to
the
rate
limiting
config
we've
applied
the
change
with
deck.
We've
shown
that
that
change
has
taken
effect
in
the
ui
but
being
able
to
manage
conflict.
Declaratively
is
great,
but
now
you're
the
only
person
that
can
make
any
changes
unless
you're
editing
the
config
file
on
your
machine.
There
are
no
guarantees
that
you
have
the
most
recent
configuration,
and
this
is
where
using
deck
with
ci
cd
comes
in.
A
We
can
treat
a
github
repo
as
our
source
of
truth
for
the
gateway
config.
So
let's
go
ahead
and
do
that
I've
got
this
deck
cicd
repo
that
I
created
earlier.
There's
nothing
in
here.
If
I
refresh
we're
going
to
do
it
all
from
scratch,
which
means
going
back
to
my
editor
and
creating
the
new
github
actions,
workflow
and
I'll,
just
call
it
push.yaml.
A
A
A
A
So
perhaps
you
don't
want
configuration
changes
applying
directly
to
production.
After
all,
that's
not
safer
than
people
making
changes
on
their
local
machine.
Let's
add
an
approval
step
to
our
actions.
Workflow
that
uses
deck
diff
to
show
what
would
change
and
then
have
someone
click
a
button
to
say.
Yes,
this
is
good.
I
want
to
apply
it
so
back
to
our
github
repo.
A
A
A
There
it
is,
but
it
hasn't
actually
made
that
change
it's
just
showing
what
we
do.
What
happens
is
this
deck
sync
job
will
run
and
it's
waiting
for
deployment
approval.
So
I
need
to
review
the
pending
deployments.
I've
looked
at
diff
deck
yeah
looks
good
to
me
and
approve,
and
now
github
actions
will
pick
that
job
up
and
run
deck.
Sync
against
our
production,
environment.
A
Here
it
goes,
seven
seconds
succeeded
and
we
can
see
that
it
went
from
ten
minutes
to
three
and
if
I
go
back
to
the
ui
and
refresh
we're
back
down
to
three
minutes
now,
our
configuration
is
in
github,
it's
versions.
We
can
see
who
changed
it,
how
they
changed
it
and
we
can
add
getting
approvals
like
no
more
making
changes
in
production,
one
person
on
their
own.
Now
you
can
have
change
management,
enforced.
A
A
It's
a
a
little
bit
bigger
and
this
is
a
small
one.
This
is
a
small
config
file,
there's
only
about
six
services
with
a
few
routes
and
it's
200
lines.
Long
to
help
with
this
deck
supports,
distributed
configuration
and
you
can
manage
each
service
as
its
own
file
and
it
will
merge
them
all
together,
and
this
means
that
each
team
you
arrive
can
manage
their
own
configuration.
A
A
Oh,
I
forgot
to
pass
in
which
stack
so
we're
gonna.
Do
it
live
see,
it
doesn't
exist.
Yes,
we
want
to
create
it.
So
pluma
is
a
great
tool
for
declaratively,
creating
infrastructure,
and
I
will
show
you
the
the
config
that
I'm
using
in
just
a
second.
I
just
need
to
say
yes,
I
want
that
whilst
that's
running,
let's
take
a
look.
A
A
A
A
One
last
thing:
a
deck
also
works
with
con
connect
or
hosted
control,
plane
solution.
All
the
demos
today
have
used
the
on-prem
gateway,
but
you
can
use
deck
connect
sync
to
manage
services
within
kinect
2..
In
fact,
migrating
from
onframe
to
connect
can
be
done
with
deck
in
just
60
seconds,
which
is
pretty
awesome.
Don't
you
think,
and
with
that
it
brings
us
to
the
end
of
the
session.