►
From YouTube: EKS Blueprints and Keptn: Developer Experience
Description
In this session, our Community Rockstar Christian Heckelmann will demonstrate how EKS Blueprints can simplify your Keptn Installation process with a few lines of code.
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
A
A
B
B
B
We
have
installed
the
external
dns
add-on,
which
will
take
care
of
updating
our
route,
53
dns
entries
right
and
also
which
comes
with
the
cdks,
the
ability
to
provision
a
cm
certificate.
In
our
case,
we
have
created
here
in
wildcard
certificate
and
we
have
connected
our
cluster
already
to
dynatrace.
B
B
And
what
we
want
to
do
now
is
yeah
just
to
add
our
eks
blueprint
add-on
for
captain
to
our
configuration,
but
let's
first
go
through
the
configuration
a
little
bit
as
you
can
see,
with
only
38
lines
of
code.
We
have
provisioned
everything
I
told
you
before,
so
we
have
here
defined
our
cluster.
We
have
imported
our
cdk,
we
have
imported
the
blueprints
we've
imported,
the
dynatrace
add-on,
and
all
we
need
to
do
is
some
configurations
for
our
add-ons
right,
so
we
have
to
find
here.
Okay,
I
want
to
have
in
my
cluster
metric
server.
B
B
I've
installed
the
external
dns
add-on,
as
I
mentioned
before,
yeah,
to
update
our
route
53
records,
and
we
have
installed
the
nginx
ingress
controller
for
the
dynatrace
add-on.
We
have
stored
the
secrets
we
are
using
for
dynatrace
in
an
aws
secrets
manager,
which
we
also
use
now
for
our
captain.
Installation
and
all
we
need
to
do
then
is
yeah,
build
our
entire
stuff
right.
So
a
lot
or
a
few
lines
of
code
to
get
a
production
grade,
aws
eks
cluster,
with
a
lot
of
add-ons
onboard
it.
B
So
what
we
need
to
do
is,
after
I've
installed
the
captain
module
to
import
it
right.
So
what
we
did
before
was
just
in
my
project,
npma
install,
that's
it
and
I
have
here
typo,
it's
not
npn,
it's
npm,
but
nevertheless,
so
let's
get
started-
and
here
I
say
in
my
add-ons
configuration
I
want
to
have
a
new
captain-
control,
planet
or
captain
control,
plane,
add-on,
confirmed,
come
off
brackets
and
then
we
can
add
some
configuration
options.
B
As
I
said,
we
want
to
use
the
aws
secrets
manager
to
define
our
api
token
and
to
get
our
bridge
password
into
our
captain
installation.
So
I
say
I
want
to
use
my
sm
secret
name,
which
is
in
this
case
captain
sp,
and
then
I
want
to
say:
okay,
which
version
of
captain.
I
want
to
have
deployed,
there
is
a
default
version.
In
this
case
it
was
11
or
12
version,
but
there's
already
the
015
version
deployed.
So
I
say
I
want
to
have
version
0,
15
0,
and
that's
basically
it
so
now.
B
If
we
want
to
run
it,
it
will
deploy.
Captain
and
captain
is
available
or
the
bridge
is
available
through
service,
but
you
yeah,
don't
necessarily
want
to
go
through
a
service.
You
want
to
have
it
exposed
as
an
ingress
right.
So
what
we
just
need
to
do-
and
then
we
need
to
get
rid
of
this
pop-up
window
here
is
to
say
I
want
to
have
ingress,
enabled.
B
B
B
B
A
B
B
Caption2,
for
instance
right
so
this
will
take
some
time
now.
Let's
go
back
to
our
presentation
and
take
a
look
at
some
of
the
prerequisites.
We
need
to
run
all
of
this
stuff.
So,
first
of
all,
you
need
to
have
installed
nodejs
machine
right,
it's
cdk,
so
node.js
is
required.
Obviously,
then
you
need
an
aws
cli
installed
on
your
machine.
B
As
you
can
see
here
on
small
screenshot,
you
can
also
add
it
directly
into
the
code,
but
most
likely
not
the
best
idea
to
add
secrets
directly
to
the
code
right
and
as
this
yeah
is
still
running,
let's
take
a
look
at
the
quick
start.
So
if
you
want
to
start
with
the
eks
blueprints,
all
you
need
to
do
is
to
install
the
aws
cdk
to
your
machine
through
npm
can
check
the
version.
B
We
just
need
to
say
then,
in
directory,
okay
cdk,
in
an
app
with
a
language
typescript,
we
installed
3mpm
the
aws
quickstart
blueprint
we
installed
through
the
mpm,
our
control,
plane,
add-on
and
optionally.
If
you
want
to
later
on,
deploy
an
execution
plane.
You
can
do
this
as
well
with
an
add-on
from
us
right
and,
with
this
being
said,
we
will
yeah
wait
a
couple
of
minutes
and
we'll
be
back
in
yeah
as
soon
as
captain
is
available
right,
see.
You.
B
So
I
hope
you
haven't
recognized
that
we
had
a
little
cut
here
in
our
video
because
it
takes
some
time
to
to
deploy
all
the
stuff
and
the
problem
is:
if
you
have
yeah
your
cluster
only
size
the
to
one
node
and
you
deploy
a
lot
of
stuff
inside
then
the
outer
scaler
kicks
in
and
yeah.
It
took
a
couple
of
minutes
to
deploy
actual
captain,
but
as
you
see,
it
is
working
as
expected.
B
B
B
B
You
can
deploy
infrastructure
components
in
one
transaction,
as
you
can
see,
I
just
run
one
tdk
deploy.
Everything
was
there
as
expected
and
if
you
want
to
deploy
multiple
cabins,
just
throw
in
another
add-on
to
the
configuration-
and
you
will
have
another
one
at
the
next
runtime
right
and
as
already
mentioned,
the
captain
execution
plane
add-on
is
also
variable.
So
you
can
install
generically
every
execution
plane.
You
want
right
and
with
that
being
said
back
to
you,
thomas.