►
From YouTube: Keptn Community & Developer Meeting - April 1st, 2021
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
00:00 Intro
02:58 LFX Project - Keptn CLI feature
12:22 LFX Project - Prometheus integration
32:15 Closing remarks
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
Join our Keptn community newsletter: https://keptn.sh/community/newsletter/
A
Hi
everyone
and
welcome
to
this
week's
community
and
developer
meeting.
I
see.
B
A
A
couple
of
folks
have
joined.
That's
great.
Today
is
april
1st
no
jokes
beside
the
shirt
jokes
that
I
already
made
before
the
recording.
I
think
a
lot
of
jokes,
maybe
we'll
hear
a
joke
or
prank
later
on,
but
yeah
thanks
everyone
for
joining,
let's
jump
directly
into
the
agenda
for
today
and
by
the
way.
Please
also
add
your
name
when
you're
joining
this
meeting
so
agenda.
B
A
I
just
we
still
keep
track
a
little
bit
of
the
spell
check.
I
got
rid
of
the
line
for
the
captain
tutorials
because
I
just
opened
the
issue
and
we
kept
all
the
tutorials
and
we
will
track
it
there.
If
we
also
open
an
issue
on
the
captain
dock,
so
we
can
also
track
it
there.
We
don't
have
to
to
carry
it
with
with
the
other
items
here.
A
One
part
I
want
to
highlight
is
we
just
released
a
new
blog
article
this
week,
together
with
our
friends
from
litmus
chaos,
we
have
written
a
blog
on
how
to
evaluate
application,
resilience
with
captain
quality
gates
and
the
chaos
is
introduced,
which
is
kind
of
the
the
basis
why
we
want
to
evaluate
the
recipients.
The
chaos
is
introduced
with
litmus
chaos.
You
might
know.
We
also
have
an
integration
with
this
with
this
project.
A
If
you're
interested
there's
a
link
here
feel
free
to
share
it,
and
we
also
have
the
tutorial,
probably
that
was
already
announced
last
week,
but
you
will
also
find
a
link
to
the
tutorial
here.
A
Otherwise,
I
will
just
also
link
the
tutorial
here,
so
you
can
give
it
a
try
yourself.
If
you
want-
and
you
can
you
can
do
this
yourself
with
that.
Let
me
just
have
a
look
who
is
joining
as
well,
so
we
have
joining
and
he
is
one
of
our
mentees
in
this
period
of
the
lfx
mentorships
thanks
for
joining,
and
we
know
that
you
have
something.
A
You
also
want
to
share
you're
working
currently
on
your
project,
you're
right
in
the
middle
of
the
project,
and
it's
it's
about
enhancing
the
captain
cli
to
also
allow
it
to
generate
the
stop
or
the
the
skeleton
for
a
new
captain
service.
A
So
with
that,
I'm
just
asking
if
there
are
any
other
questions
to
the
things
I
just
announced
that
I
just
said,
then
we
can
take
it
here.
C
Visible
yeah,
so
I
have
been
working
on
the
lfx
mentorship
project
and
this
is
the
issue
that
it
was
based
on.
Basically,
my
project
deals
with
creating
a
service
template
for
captain
right
from
your
captain
cli.
So
there
are
some
definitions,
tasks
that
I've
done.
I
have
reached
around
until
this
checkbox
should
the
integration
test
and
the
other
things
are
left
we'll
also
have.
C
I
also
quickly
demonstrate
of
what
I've
built
and
there
were
some
meetings,
weekly
meetings,
and
there
were
some
discussions
and
I
have
detailed
documented
them
on
a
draft
work
in
progress
here
under
the
research
phase.
I
have
documented
what
were
the
hurdles
and
what
were
the
solutions
that
we
took,
and
why
did
we
take
them
and
why
we
found
it
better,
so
you
can
go
through
and
leave
any
comments
or
suggestions
if
you
like
to
make
it
better
and
more
efficient.
C
So
like
this,
is
the
issue
states
that
we
basically
need
to
just
create
a
service
template
by
taking
in
these
three
parameters?
Basically,
the
service
mean
that
the
developer
wants
to
generate
the
service
of
the
docker
image,
name,
that
it
will
be
pulled
from
the
docker
hub
or
any
other
docker
repository
and
the
list
of
cloud
events
like
captain
cloud
events
that
the
service
will
still
get
into.
C
So
we
could
know
that
we
have
a
template
repository,
which
is
just
under
the
captain.
Sandbox
github
organization,
users
or
developers
could
basically
clone
this.
Follow
the
readme
follow
through
all
these
steps
and
they
will
be
able
to
like
create
the
service,
but
we
are
automating
the
whole
process.
C
That's
the
whole
project
about
so,
basically
that
there
won't
be
needs
of
any
more
steps
you
can
directly
do
all
this
at
all
will
be
automated
directly
from
the
captain
cnn,
so
that
is
a
gist
and
I'll
just
quickly
get
into
demonstration
of
how
it's
going
to
work.
C
This
is
a
local
build
which
I
built
from
my
branch
of
which
I'm
working
on
so
I'm
gonna
say:
captain
generate
captain
service
and
this
has
auto
completion
enabled
so
I'm
just
pressing
my
tab
to
quickly
auto
complete.
So
in
this,
you
can
pass
three
parameters,
as
the
issue
mentions.
If
I
hit
tab
once
tap
twice,
it's
going
to
tell
me
what
all
the
parameters
I
can
pass.
So
again,
let's
come
on
to
the
image
name
like
it
says
that
I
need
to
pass
an
image.
C
So
let's
say
that,
then,
if
not
right
and
let's
say
I'm
off
pulling
a
service
name,
simple
service
and
the
second
parameter
is
or
argument
is
the
service
name,
and
let's
say
I
want
to
name
the
service
random
service.
Note
that
the
docker
image
its
name,
simple
service,
but
I
can
name
any
service
locally.
Whatever
I
want,
so
I'm
gonna
name
it
random
servers
and
I
can
pass
the
comma
separated
list
of
captain
cloud
emails
now.
What
I
want
to
listen
to
so
in
this
case,
like
you,
can
visit
the
documentation.
C
Okay,
okay,
yeah,
here
it
is,
you
can
visit
the
documentation,
and
these
are
some
example-
events
that
your
servers
can
listen
to.
So
I'm
just
gonna
copy
one
of
these
and
I'm
simply
gonna
base
the
basic
and
once
I
press
enter
right
now
it
shows
work
in
progress
and
I
am
hit
so
there's
no
detailed
logging.
I
will
add
detail
logging
as
the
work
proceeds.
So
now
a
folder
named
random
service
is
generated
right.
C
So
if
I
just
cd
into
this
random
service
folder
and
I
list
what
is
all
in
it,
so
basically
it's
the
template
service
that
is
being
legit,
but
it
does
not
hold
any
placeholders
because
I'll
just
show
you
in
this
let's
say
I
wanna
visit
the
scaffold,
so
it
has
the
image
of
whatever
I
had
given
in
the
arguments.
So
this
is
not
a
template
service
anymore.
This
is
a
properly
full-fledged
generator
service.
C
It's
not
a
placeholder
anymore,
so
whatever
the
readme
suggests
of
where
our
let's
take
example
of
service.yaml
that
is
present
in
the
deployed
folder.
So,
as
you
can
see
here,
also
that's
a
comment
that
it
needs
to
be
replaced
with
my
image.
Name,
but
it's
already
replaced
so
the
cli
has
automated
all
this
project,
so
that
is
about
it.
That
is
how
far
we
have
come
so
right
now.
What
I'm
working
on
is
that
no
both
been
checked.
Basically.
C
So,
for
example,
I
am
running
a
captain
cli
portion
of
0.8.0,
but
if
you
go
to
our
our
templates
service
template
repository
and
if
you
look
for
tax,
it's
all
basically
named
up
suffix,
twitter
and
hyphen
alpha.
So
I'm
working
on
a
system
that
automatically
like
detects
your
captain,
cli
version
and
it
like
pulls
the
closest
tab,
closest
release
as
possible
so
that
it
does
not
always
pull
the
mark
to
branch.
C
So
I'm
working
on
both
case
scenarios,
for
example,
say
we
release
a
patch
fix
like
0.8.2
on
our
captain
cli,
but
we
do
not
have
0.8.2
in
our
service
template
because
we
do
not
want
to
add
another
process
in
our
captain.
Cli
release
right,
so
it
could
automatically
smartly
detect
that.
Okay,
it's
zero
point
eight,
so
it
could
pick
up
zero
point,
eight
point
zero
or
whatever
is
present
the
closing
version.
That's
present
in
the
capital
service
template
and
it
will,
of
course,
prompt
the
user.
C
That's
downloading
this
version
so
right
now,
the
only
work
left
mostly
is
the
integration
testing,
that
is,
the
production
of
the
docker
yaml
and
all
the
testing
that
needs
to
be
done.
The
service
is
good
to
go.
C
Is
it
working
fine
and
once
it
is
done,
its
crypto
goes
so,
for
example,
like
the
cloning
of
the
whole
repository,
so
this
repository
was
cloned
basically
to
the
user's
local
desktop,
and
this
was
achieved
using
this
library,
a
third-party
library
named
google,
it's
an
open
source
library,
so
we
first
thought
because
downloading
the
tar
file
and
unpacking
it
would
be
tedious
and
would
have
will
have
chances
to
break
so
we
found
out
this
solution
and
we
had
discussed
over
it,
and
I
have
documented
it
in
my
draft
pr
of
why
we
decided
to
go
with
google.
C
So
if
there's
any
suggestions,
you
can
go
through
the
code.
I
have
been
like
adding
comments,
so
if
there's
any
suggestions
feel
free
to
leave
a
comment,
early
review,
I'll
look
into
it.
So
that
is
how
it
that's
almost
it.
That's
about
it
regarding
the
cli
enhancements
for
now
like.
If
you
have
any
questions,
please
feel
free
to.
A
Some
downl
with
this,
the
gold
library
that
is
using
here.
A
It's
a
a
great
idea
to
to
use
this
and
really
great
progress.
You've
been
so
far
thanks
for
for
sharing,
really
looking
forward,
also
great
to
see
that
the
auto
completion
and
it's
working,
how
everything
now
comes
together,
really
cool.
A
So
while
raj
is
joining
as
well,
I
just
want
to
highlight
two
things
that
I
just
added
to
the
meeting
document.
A
Let
me
share
again:
that's
just
that.
Actually
we
have
two
new
tutorials
edit.
One
was
just
emerged
a
couple
of
minutes
ago.
It's
around
argo,
rollouts
and
doing
canary
releases
with
captain
and
article
rollouts.
So
basically
captain
is
orchestrating
the
rollout
process
and
and
having
the
quality
gate
in
between
for
each
phase
of
the
canary
robots.
When
you
think
of
this
first
to
25
percent
of
the
rollout
of
50
75
and
in
between
there's
always
a
captain
quality
gate.
This
was
contributed
by
andy.
A
I
think
he's
not
jumping
today,
but
thanks
for
for
contributing
this,
and
the
other
one
I
mentioned
earlier
is
around
using
vintmoscare's
experiments
and
evaporation
with
captain.
So
with
this
I
think
yeah
I
can
see
raj
here
so
I'm
handing
over,
and
I
would
ask
you
to
also
share
your
project.
C
C
Okay,
so
the
primary
task
is
that
the
currently
promoted
service
is
installing
prometheus
and
alert
manager
from
inside
from
the
port,
and
the
plan
is
to
install
promises
externally
and
promoter
service
can
help
to
configure
all
the
scrap
jobs
and
alert
manager
configs
using
the
captain
cli
tool.
So
what
I
did
is
I
move
out
all
the
from
this
related
and
alert
manager
related
code
outside
of
the
promised
service.
C
Now
you
can
install
prometheus
externally
and
configure
prometheus
within
captain,
so
I'll
just
go
through
a
tutorial
which
is
the
sockshop1
so
I'll
just
follow
this
sock
shop,
one
sock
shop,
so
the
main
step
is
the
13
step
so
which,
which
is
which
is
going
to
change
so
I'll,
follow
till
12,
step
and
I'll.
C
Show
you
how
the
new
promises,
one
monitoring
setup
can
be
done.
So
I
have
to
configure
the
shock
shop
one.
So
here's
my
cluster.
This
is
a
simple
decay
cluster,
my
stu
and
everything
is
running
here.
C
Okay,
so
I'll
just
on
board
the
shock
shop
one.
So
I
already
have.
I
have
to
install
shock
shop
using.
C
C
C
C
Service
so
successfully,
okay,
it
is
already
there
services-
I
guess-
okay
already
there.
So
these
are
some
of
the
tests
like
what
you
call
it
j
meter
test
to
these
are
the
functional
tests
I
think
already
performed
I'll.
C
And
so
I'll
go
ahead
and
onboard
this
db
service,
I
think
already
it
is
already
there.
I
guess
yeah
already
there
and
I'll
move
forward,
and
I
can
skip
this
step.
If
you
want,
I
can
directly
go.
A
It's
already
done
once,
but
you
can
still
do
it
another
time.
That's
no
problem.
C
C
C
A
Started
the
this
one
when
you
click
on
fuse
sequence,
but
actually
it
says.
A
Finished
so
the
the
very
last
one
that
should
or
the
first
one
sorry
the
top
one
I
think,
okay,
so
it
says
here,
is
that
I
can,
with
the
with
an
error
in
it
in
the
deployment
time,
it's
the
on
the
right
hand,
side
there.
There
is
an
icon
yeah
this
one.
A
No,
don't
worry,
we
can
wait
for
it.
In
the
background
to
finish,
we
can
take
a
look
on
the,
how
you
you
add
the
the
promethouse
and
it
will
fit.
It
should
finish
it
in
the
background.
C
Yeah,
so
so
these
are
the
like,
and
this
will
this
load
gen
will
generate
some
traffic
on
three
stages
so
that
these
are
the
general
procedure.
So
the
main
thing
is
here:
so
how
will
configure
external
promises
and
how
we
can
set
up
it?
So
the
steps
are
just
a
few
changes,
so
you
have
to
first
install
promises
before
the
promoter
service
captain
promoter
service.
So
what
I'll
do
I'll
install
prometheus?
C
Is
created
and
I'll
just
go
and
install
from
this,
so
this
chart
will
install
some
other
other
things
like
push
gear
to
a
node
exporter
which
is
not
required.
We
only
need
the
prometheus
server
and
the
late
manager,
but
it
is
okay.
C
So
if
you
see
so
these
are
a
few
things
which
is
not
required.
We
only
require
the
server
and
the
led
manager
for
captain,
so
it
is
now
creating.
C
It
created-
and
the
second
thing
is
the
config
map,
which
is
required
to
configure
elect
manager
and
from
this
server.
C
So
there
are
two
main
config
map.
One
is
the
server
config
map,
another
one
is
the
elect
manager,
config
map,
so
server
configmap
have
all
the
scrap
job
details
for
the
prometheus
and
I'll.
Let
manager
you
know
like
it
will
have
all
the
elect
rules
and
all-
and
there
will
be
one
more
config
which
will
create.
That
is
the
template
one,
how
the
template
led
template
will
look
like,
so
it
will
created
by
the
captain
parameter
service
once
we
configure
it.
C
So
the
thing
is
we
have
to
configure
a
promoter
service
so
how
we
can
configure
the
promoter
service,
so
currently
it
is
not
being
released.
So
these
are
the
local
changes
you
have
to
do.
So
there
are
some
envs
you
have
to
configure
during
installation
of
promoter
service,
so
these
are
the
envs.
C
So
these
cnvs
will
take
a
few
information
like.
Where
is
your
promises
installed?
Where
is
the
installation
of
elet
manager
and
labels,
config
map
name
and
all
so
I'll?
Just
configure
the
few
things
so
my
promises
name
space
is
monitoring
and
I
have
to
change
the
config
map
name,
so
my
config
map
name
is
so
gives
it
that
config
map
monitoring
some
con
from
which
is
config
map
name.
Is
this
one
server
one
I'll
just
change?
It
respond
nt
and
also
the
led.
C
Manager,
so
labels
are
same,
there
is
no
change
in
our
labels
and
the
element
manager
namespace
is
correct,
so
this
changes
is
in
the
pr,
so
it
is
not
merged
yet
so
I
build
a
local
docker
image
of
captain
promises
service
and
I
just
replace
the
promised
service
here.
So
sorry
image
of
the
promoter
service
here.
So
this
is
my
local
image
so
I'll
install
the
deployment
using
this
manifest.
C
C
C
So
if
I
go
to
the
targets
I
can
see
the
targets
are
of
the
node
exporter
and
other
exporters.
So
this
is
not
this
is
these
are
not
the
stock
shop
one?
So
once
I
configure
the
sockshop
for
promoters,
so
we
can
see
a
few
more
met,
a
few
more
targets
right
now.
There
are
almost
one
two
three
four
seven
targets,
and
once
I
configure
the
shock
shop
one
you
can
see
the
other
targets.
Also
so
I'll
just
go
ahead
and
configure.
C
I
think
you
can
see.
Okay,
you
can
see
my
prometheus.
C
C
Shock
shop
yeah:
these
are
the
stock
shop,
scrap
jobs.
You
can
see
it
has
been
patched
in
this
config
web.
So
once
I
restart
my
sorry
once
I
rerun
my
port
forward,
so
I
can
see
the
changes.
C
A
I
think
it
has
not
been
promoted
to
the
other
stages.
Probably
evolution
is
stuck
because
maybe
you've
configured
it
already
once
with
prometheus,
and
it's
still
kind
of
looking
up
the
promoter's
installation.
C
No,
it
is
down,
it
was
the
previous
one.
Just
I
think,
yeah
this
the
production
one
is
down
only
the
development.
One
is
up,
so
you
can
see
only
the
development
one
yeah.
So
this
is
the
new
announcement
in
the
permitted
service.
Any
questions.
A
C
The
prometheus
is,
there
is
a
we
are
doing
the
restart
by
the
prompter
service,
so
prompted
service.
What
promoter
service
will
do?
It
will
delete
that
pod
delete
this
alert
manager,
port
and
server
port.
A
B
C
C
A
Okay,
got
it
and
the
the
alert
manager
is
somehow
not
coming
up,
not
sure
if
it's
related
to
your
configuration
or
if
it
was
already
in
the
beginning
that
it's
not
it's
not
starting.
A
C
C
Yeah
the
alert
manager
template
is
already
exist
because
this
will
create
by
the
captain
service.
So
we
have
to
delete
this
one
first,
so
this
one,
this
one
will
be
created
by
the
prometheus
service
captain
promoter
service.
So
we
have
to
delete
this.
A
Okay
got
it
yeah.
I
think
what
we
have
to
test
is
how
it
behaves
when
there
is
a
captain
configure
monitoring
for
another
service
right
now.
We
have
only
the
the
shopping
cart
of
sockshop,
but
once
we
have
two
or
more
services
how
the
the
config
map
is
created,
especially
with
the
alert
manager
that
I
guess
there
would
have
be
kind
of
a
some
editing
needed
reading
the
conflict
map
and
writing
it
again,
as
it
might.
A
That
we
want
to
configure
or
one
service
at
a
time,
but
there
might
be
more
services
in
one
project
and
we
will
need
to
execute
the
character,
configure,
monitor
yeah.
C
So
this
template
is
common
for
everyone,
so
yeah.
I
think
we
have
to
I'll
make
this
independent.
So
it
is
just
appending
in
here.
There
are
some
rules
in
the
element
manager
you
can
see.
It
is
just
appending
the
from
this
service
here
on
the
webhook.
C
A
Okay,
yeah
thanks
are
there
any
more.
A
Questions,
if
not,
then
let
me
just
share
again,
but
I
guess.
A
That
no
one
added
anything
more
to
the
agenda,
so
I
think
this
was
it
for
this
week's
edition
for
the
captain
community
and
developer
meeting
thanks
so
much
for
your
presentations
really
looking
forward
to
see
the
next
progress
in
the
project.
So
I
think
you're
really
on
the
on
the
right
track
and
we
really
can
see.
B
A
Your
contributions
are
also
improving
the
captain
project,
which
is
really
great
if
there
is
nothing
more
just
opening
up
for
questions
here,.
A
Otherwise,
we
can
close
it
a
little
bit
earlier
than
usual
thanks
everyone
for
joining
happy
easter,
at
least
yeah,
in
not
sure
if
everyone
is
celebrating
but
those
who
are
celebrating
at
easter-
and
we
see
you
all
next
thursday
thanks
everyone
for
joining
have
a
nice
day,
bye,
bye,.