►
From YouTube: Keptn Community & Developer Meeting - April 29th, 2021
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
Timecodes:
00:00 General announcements
11:20 Keptn Github Action
27:57 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
A
Hi
everyone
welcome
to
this
edition
of
the
captain
developer
in
community
meeting
today.
It's
april
29th.
B
A
Perfect
sunny
weather
here
in
central
europe
and
yeah,
we
have
a
couple
of
things
for
today,
so
I'm
really
excited
on
the
on
the
agenda
that
we
have
and
yeah
it's
a
cncf
project
meeting,
so
we're
following
the
cncf
code
of
conduct
here.
So
that
means
please
be
nice
to
each
other
as
always.
A
A
We
have
started
a
new
newsletter
format
just
last
week.
I
think
we
sent
out
the
first
edition
of
the
new
newsletter
so
make
sure
to
also
sign
up
for
the
newsletter.
It
will
have
all
the
latest
updates
on
new
releases
on
the
new
developments
around
captain
on
new
ecosystem
integration.
So
it's
a
great
way
to
keep
up
to
date
with
the
project
and
it
will
be
sent
out
bi-weekly.
So
there's
won't
be
spamming.
A
Your
inboxes,
it
will
be
a
bi-weekly
update
on
the
project
and
you
can
sign
up
here
in
the
the
first
edition
was
already
sent
out
on
monday.
The
next
one
will
come
on
monday
in
a
week,
so
after
cubecon
actually-
and
this
is
also
already
the
next
agenda-
point
2021
virtual
edition
in
virtually
in
europe.
This
edition
will
take
place
from
next
week
from
a
tuesday
to
friday,
and
there
is
even
a
presentation
and
a
talk
on
captain
in
the
little
scales.
A
It
is
all
around
how
to
evaluate
the
resilience
of
applications
by
using
captain
as
the
orchestrator
of
the
deployment
load
tests,
chaos,
tests,
evaluations
and
giving
you
basically
with
our
slo
evaluations,
giving
you
a
resilience
for,
if
you
want
to
say-
and
you
will
find
all
the
information
for
kubecon
on
the
dedicated
landing
page
captain.sh,
and
if
there
is
anything
that
you
are
missing.
A
Just
let
us
know
if
there
is
anything
you
want
to
learn
more
about
the
project
or
if
you
are
not
attending
kubecon,
but
still
want
to
get
in
touch
with
the
maintainers.
Please
also
join
us
in
these
office
hours.
We
have
two
sessions
dedicated
to
to
our
captain
project.
The
one
is
on
wednesday
around
noon
and
the
other
one
is
friday
morning.
It's
a
great
way
to
get
in
touch
with
with
some
of
the
maintainers,
and
it's
also
a
great
way
to
get
in
touch
with
some
of
our
captain
adopters.
A
Yeah
for
the
next
part,
if
there
are
any
questions,
just
put
them
in
the
chat,
and
I
will
make
sure
to
address
them
also,
but
I
will
just
go
through
through
the
first
parts
that
they
change
rather
quickly.
For
the
next
part,
we
are
looking
for
a
new
code
owner
of
a
service
that.
B
A
The
whole
purpose
of
this
service
is
that
you
can
subscribe
to
different
kinds
of
events
that
are
sent
from
captain,
and
these
events
will
then
be
pushed
directly
into
your
slack
workspace
or
into
your
microsoft
teams,
workspace
and
channels.
So
if
you
are,
if
you
want
to
help
out
with
within
the
captain
project-
and
if
you
think,
if
you
think
that's
interesting,
so
we
are
looking
actively
for
a
new
owner
of
this
captain
country
repository.
A
Currently,
it's
not
working
with
the
latest
version
of
captain,
so
the
first
task
would
be
to
kind
of
update
it
to
support
the
latest
version
of
captain.
If
you
think
this
is
something
that
might
fit
your
skill
set,
just
let
us
know
and
join
our
captain's
like,
and
let
us
know
that
you
want
to
kind
of
take
ownership,
or
at
least
maybe
do
a
contribution
on
the
service.
That
would
be
highly
appreciated,
then,
for
from
last
week,
we
did
not
go
into
any
detail.
I
just
want
to
have
these
links
here.
A
There's
a
new
blog
written
by
andy
on
automated
performance
resilience,
testing
with
meiotics
near
load,
it's
actually
the
software,
and
this
was
given
at
their
neolis
pack
event.
The
presentation
was
given
there,
and
so
they
followed
up
also
with
the
blog
on
this.
It's
really
cool
make
sure
to
check
it
out,
and
if
you
want
to
have
some
more
hands-on
training
and
feeling
on
captain,
then
we've
also
published
last
week
a
new
tutorial.
It
even
has
a
video
included
on
how
to
do
captain
quality
gates
with
premier
voice.
A
It
comes
with
a
demo
application.
It's
the
cncf
potato
head
application,
so
it
will
give
you
a
captain
on
k3s
everything
comes
with
a
you.
Just
have
to
bring
a
vm,
and
then
you
install
captain
on
k3s.
It
will
install
and
set
up
the
demo
application.
It
will
even
run
the
first
quality
game.
So
it's
it's
really
a
five
minute
installation
and
you
already
have
the
first
quartergate
evaluation
with
prometheus
and
it's
a
it's
really
a
nice
start
into
learning
how
how
captain
works,
some
updates
from
the
ecosystem.
A
So,
just
yesterday
I
think
our
friends,
friends
from
artillery
released
an
initial
version
on
their
artillery
integration.
Articulary
is
a
performance
testing
framework
and
you
can
just
use
now.
You
can
now
use
captain
with
artillery
and
captain
will
trigger
artillery
tests.
A
You
will
find
a
read
me
in
the
description
how
to
use
it
in
their
repository
in
the
captain
sandbox.
So
if
you're
already
using
artillery
or
you
want
to
get
used
or
you
want
to
get
started
with
performance
tests,
but
don't
want
to
use
cheap
meter
anymore,
then
artillery
is
really
a
great
start
here
so
make
sure
to.
A
So,
as
far
as
I've
seen,
it's
just
a
single
container
and
the
load
tests
are
described
as
amble
files.
So
it's
not
accidental
hell
anymore.
Now
it's
a
gamble
and
it's
way
easier.
It's
very
similar
to
locust,
I
guess,
but
what
I've
seen
everything
comes
within
the
container.
To
be
honest,
I
have
not
yet
tried
it
out
myself.
A
It
was
just
released,
I
think
yesterday
and
they
stated
as
a
very
initial
version,
so
there
will
be
more
coming,
but
if
you're
already
interested
in
checking
it
out,
it's
not
as
far
as
I've
seen
you
don't
have
to
create
an
account.
You
don't
have
to
to
install
any
other
software.
You
can
just
use
it
as
they
are
providing
the
service
integration.
A
Yes,
so
actually
we
have
two
candidates,
because
we
have
already
a
locust
integration
and
it
works
very
similar.
A
The
locust
binary
is
included
in
the
container
and
you
can
define
here
the
performance
tests
as
python
files
and
they
will
then
be
executed
by
the
locust
binary,
and
here
I
would
say
we
have
made
a
little
bit
more
progress
already,
because
this
service
already
now
supports
configuration
files,
both
a
configuration
file
that
is
very,
very
similar
to
the
gmeter
conf
that
we
already
have
in
the
in
the
captain
project,
where
you
basically
map
a
testing
strategy
to
the
performance
test
that
has
to
be
executed,
and
it
also
supports
the
native
locust
config
files.
A
A
The
captain
community-
and
we
are-
we
also
know
that
the
local
service
is
already
used
in
production
and
some
of
the
captain
adopters.
So
I
think
this
one
is
a
little
bit
more
mature
as
the
artillery
service,
but
please
give
both
services
a
try
and
then
we
could
decide
which
one
to
go
like
it's
the
it's,
the
first
replacement
of
the
chain
media
service.
I
think
that's
it's
already
due
that
we
kind
of
deprecated
there
and
then
maybe.
A
Maybe
we
can
discuss
in
the
next
meetings.
What
is
the
the
preference
which
service
you
want
to
use
if
it's
more
locust
or
if
it's
more
artillery
and
then
we
can
give
it
a
little
push
write
our
tests
for
these
integrations?
A
Has
anyone
already
tried
one
of
those
integrations
like
artillery
or.
A
A
Not
yet
but
yeah,
if
you
give
it
a
try,
let
us
know
maybe
in
the
captain's
lake
or
in
one
of
the
next
community
meetings,
and
we
can
gather
the
feedback
and
then
also
maybe
bring
it
back
to
the
community.
So
the
community
contributions
can
consider
this
and
improve
their
their
services.
A
So
with
this,
I
think
these
are
the
most
important
updates
are
currently
from
the
ecosystem.
There
is
more
going
on,
which
is
not
yet
released,
like
the
aws
space
integration
and
the
the
work
on
the
on
the
integration
of
one,
the
one
chart
from
the
gimplet
project,
but
I
think
this
is
more
more
to
be
shared
in
the
next
in
the
next
meetings.
A
B
Okay,
during
the
captain
development,
we
had
the
need
to
kick
off
a
captain
event
during
the
build
pipeline,
and
there
there
was
the
idea
to
create
actually
a
github
action
which
is
capable
of
sending
such
events
to
a
already
existing
captain
installation,
and
I
can
quickly
show
you
today
how
this
looks
like
it's
the
very
very
first
version
of
this
github
action,
but
it's
already
quite
useful
and
I
can
show
you
how
you
can
use
it.
B
What
you
can
see
here
is
on
the
right
side,
captain
installation
on
my
side.
It
has
a
really
simple
setup.
Only
one
stage
called
dev
and
there's
also
only
one
service,
they're,
already
well
known,
cards,
db,
mongodb
service,
of
course,
and
yeah.
There
were
already
a
couple
of
events
fired
into
this
captain
installation,
and
you
can
see
here.
B
For
example,
I
already
delivered
an
artifact
for
the
mongodb
or
cardsdp
service
here,
using
using
the
github
action,
and
I
can
replicate
this
now
and
show
you
how
you
can
set
it
up
to
actually
send
any
kind
of
event.
You
would
like
to
send
to
the
captain
installation
from
within
a
github
action
or
a
github
workflow.
B
Yes,
so
this
is
the
repository
of
the
github
action,
so
the
source
code
of
this
github
action
to
send
events
to
captain.
We
can
take
a
quick
look
at
the
parameters.
It's
really
simple.
It
only
requires
two
to
set
three
mandatory
parameters.
The
first
one
is,
of
course,
the
captain
api
url,
which
usually
looks
like
this.
Of
course,
your.
B
Url
with
the
path
api,
d1
event,
the
second
one
is
the
captain
api
token.
This
needs
to
be
a
valid
token
for
your
cap,
installation
oops
and
the
third
one
is
of
course,
the
event
you
want
to
send
right
now
the
the
captain
sent
event.
Github
action
is
quite
flexible,
so
there
is
really
no
restriction.
B
What
you
can
send
and
what
not-
and
I
will
just
go
now
to
my
private
repository
here,
where
I
have
a
yeah
set
up
a
repository
called
captain
send
event
github
action
demo,
and
I
will
use
this
repository
to
configure
a
workflow
which
is
using
the
captainsend
event
action
to
send
an
event
to
this
captain
installation
on
the
right
here
and
the
event
will
be
to
trigger
the
cards
to
be
cardstb
deployment
on
my
system.
B
So
I've
prepared
here
so
you
see
this
repository
is
pretty
empty.
It
just
has
this
dot
github
slash,
workflows,
folder,
as
you
know,
when
you
want
to
create
a
github
workflow
using
github
actions,
you
need
to
follow
this
convention
to
create
this
folder
folder
and
there
inside
of
it.
You
yeah
describe
your
workflows
using
yaml
files.
B
So
this
I
already
prepared
here
and
let's
take
a
look-
what
we
have
in
here
so
right
now,
it's
really
simple.
You
know
you
can
specify
when
you
want
to
trigger
your
workflow
using
the
on
field
here
here.
I've
just
chosen
to
trigger
this
whole
workflow
on
every
push
on
regardless
what
branch
and
this
will
actually
trigger,
then
the
workflow
when
I
do
a
git,
commit
and
get
pushed
to
this
repository.
B
If
you
look
here,
we
have
the
jobs
section
and,
of
course
it's
sent
captain
event
and
there
you
have
our
captain
sent
event
github
action
which
looks
right
now
like
this.
It
has
an
id
here's,
the
reference
to
the
to
the
github
action
and
you
can
specify,
with
with
the
width,
parameter
what
kind
of
arguments
you
want
to
pass
into
the
github
action,
as
we
saw
earlier,
it
needs
to
be
captain
url
and
gap.
Maybe
I
token,
if
you
would
to
push
now
something
to
this
repository.
B
It
would
of
course
fail
like
it
did
a
couple
of
minutes
ago.
It
should
have
been
said
that
I
have
forgot
to
put
an
event
to
this
workflow,
which
I
want
to
send
to
my
kept
installation.
So
I
now
need
to
decide
which
kind
of
event
I
want
to
send
yeah.
As
I
said
already,
I
want
to
again
send
a
trigger
delivery
event
to
the
captain
installation
to
trigger
my
my
deployment
of
cards
db.
B
B
B
I
think
it's
or
yes,
we
don't
need
to
use
git
right
now
we
can
just
we
can
just
edit
the
file
directly
here
in
github,
and
it
will
allow
us
to
do
a
commit
from
here.
But
of
course,
usually
you
do
it
from
your
local
environment,
where
you
use
git
to
commit
to
commit
and
push
to
your
repository
okay,
so
the
third
parameter
was
missing
and
the
third
parameter,
like
we
saw
in
the
documentation,
is
of
course
event
and
using
this
you
can
specify
really
any
captain
event.
B
I
think
the
syntax
for
doing
multi-line
strings
in
yarmulis
like
this
and
let's
just
put
here
oops
now
our
event
and
right
now
to
have
a
valid
syntax
here
we
need
to
put
it
a
couple
of
indentations
to
the
right,
so
this
would
be
actually
the
first
improvement.
I
could
imagine
so
that
you
can
actually
also
specify
your
event
in
files
which
are
read
by
the
which
are
read
by
the
by
the
github
action.
B
Then
you
don't
have
to
fiddle
around
here
in
line
with
this
format
and
so
on
yeah
right
now.
We,
it
only
supports
events
which
you
put
directly
here,
but
that
would
be
a
next
step
if
we
need
it
or
if
someone
want
to
improve
the
github
action,
feel
free
to
to
just
file
a
pull
request.
Okay,
we
have
here
our
event
just
directly
copied
from
the
installation.
B
What's
important
is
usually
we
already
had
here
a
captain
context.
We
will
just
delete
it
because
the
event
will
actually
get
the
new
captain
context
from
the
captain,
api,
of
course-
and
we
won't
don't
want
to
interfere
with
other
events
which
already
had
this
captain
context.
So
keep
this
in
mind
that
usually,
usually
you
don't
want
to
have
a
context
here,
captain
will
create
or
generate
a
new
one.
There
might
be
use
cases
where
you
would
like
to
use
an
existing
existing
capital
context,
but
in
my
case
I
want
to
use
a
fresh
workflow.
B
So
to
say,
using
a
new
fresh
captain
context
generated
by
captain.
Okay,
that's
the
first
thing
same
argument
goes
for
the
id.
It
will
be
chosen
by
or
generated
by,
captain
api,
and
I
also
get
rid
of
the
time
of
course,
because
it's
not
the
right
timestamp
I've
got
copied
from
an
already
sent
event.
B
Okay,
that's
basically
it.
A
B
Just
a
regular
captain,
a
regular
captain
event
and.
A
Can
I
ask
a
question
here
so
the
the
uses
part
here
on
the
send
captain
event
that
has
to
be
captain
slash,
github
action
send
event
at
main,
so
this
is
basically
referring
to
the
key
that
action.
That
captain
is
providing
and.
B
B
I
think
the
ids
can
be
chosen
by
the
user
if
I'm
correctly.
Yes,
I
think.
B
And
maybe,
when
we
do
releases
of
this
captain
send
event
action
you
can.
You
would
have
a
version
here
at
the
end
right
now.
It's
just
me
because
we
don't
have
a.
We
don't
have
a
release
for
that.
Okay,
that's
basically
it!
Let's
commit
this
changes.
I've
just
made
here
directly
in
github,
we'll
do
commit
here
and
with
this,
because
we
have
here
the
trigger
push
which
should
we.
We
should
already
see
here
the
workflow
starting.
B
Goes
rather
quickly,
and
here
it
gives
you
an
overview
actually
what
you
have
sent
it's
just
this
event,
of
course,
and
it
also
spits
out
which
capital
context
was
generated
by
the
by
the
api,
and
if
we
are
lucky
we
should
now
see
here.
I
think
it
was
already
this
one
was
it
started
today,
70?
Yes,
it
was
here
from
the
time
I
can
see
17
23
now
it's
17
24,
so
it
was.
It
was
exactly
this
delivery
here
which
was
kicked
off
by
by
a
github
action.
So
this
is,
I
think,
quite
useful.
B
You
can
imagine
you
have
your
own
repository
here
and
you
I
don't
know
someone
commits
a
special
file
or
content
to
your
repositories.
You
want
to
react
to
it,
kick
off
something
on
your
captain,
installation
and
so
on.
You
can
easily
do
this
via
this
action
here
and
you
basically
just
have
to
know
what
event
you
want
to
send
and
that's
it.
You
don't
have
to
fiddle
around
with
doing
the
http
request
manually
so
that
that's
basically
done
by
the
captain
and
yeah.
B
B
Of
course,
this
is
only
the
minimal
version.
I
would
say
there
are
plenty
of
plenty
of
room
of
improvements.
Of
course,
just
post
your
ideas
or
file,
any
pull
requests
to
this
github
send
event
action.
I
think
this
could
be
improved
in
any
way.
Right
now
we
have,
I
would
say,
minimal
version
which
is
already
quite
useful
and
can
be
used
for
well
such
use
cases
where
you
want
to
kick
off
anything
on
your
captain
installation.
Whenever
anything
happens
on
your
git
repository,
I
think,
as.
C
A
use
case
that
we
didn't
mention
yet
you
could
also
just
have
your
git
repository.
C
Like
your
your
config
repository,
where
you
have
your
health
charts
and
when
you
push
changes
to
those
health
charts,
you
could
trigger
a
delivery
same
as
what
you
would
do
with
the
cli,
but
you
do
it
automatically.
So
this
would
be
the
counter
productivity
github's
operator.
That
thomas
and
I
think,
have
shown
a
couple
of
weeks
ago.
A
B
Basically
do
cool
things
with
it,
a
couple
of
words
here
to
the
captain,
api,
url
and
captain
api
token
usually
just
keep
an
eye
on
not
storing
such
information
directly
here
anywhere,
but
I
think
it's
more
or
less
not
a
hundred
percent,
but
more
or
less
secure
to
keep
it
as
a
github
secret,
where
these
two
sensitive
information
are
secured
by
github
and
not
visible
to
anyone
who
will
do
them
with
things
with
with
it.
B
A
First
for
for
the
use
case,
this
christian
already
mentioned
that
if
someone
changes
or
updates
any
configuration
in
the
kit
management
poll
of
captain
to
then
trigger
a
new
delivery
or
trigger
a
new
sequence
and
what's
also
really
cool,
is
that
it
actually
gives
you
back
the
captain
context
of
the
newly
generated
event,
because
if
you,
if
you
might
need
it
for
some
subsequent
actions,
I
guess
this
is
part
of
the
github
actions
that
you
can
pick
it
up
and
then
maybe
use
it
in
the
next
section.
A
Already,
if
you
want
to
log
in
somewhere
or
if
you
want
to
maybe
trigger
even
a
second
event,
and
then
you
can
send
it
directly
from
the
the
same
github
workflow,
you
can
even
send
a
second.
A
Okay,
so
I
really
think
I
really
like
it.
I
think
it's
really
powerful,
although
it
because
you
can
give
it
just
the
payload
of
the
captain
event
without
the
captain
context,
without
the
time
and
without
the
id
and
then
just
sends
it
to
captain
and
the
triggers
triggers
whole
delivery
sequence,
pretty
cool
yeah
thanks
for
demoing,
this
you're
welcome.
Thank
you.
A
A
I
think
we
are
good
for
today
we
talked
about
artillery
service,
the
local
service
and
right
now,
just
the
the
github
action
where
you
can
send
arbitrary
captain
events
within
github
workflows
to
your
captain,
installation
so
make
sure
to
check
it
out
and
let
us
know
in
the
captions
like
what
you
built
with
the
github
action,
and
I
think
with
this
we
are
basically
through
the
agenda
and
the
for
all
the
points
we
we
wanted
to
discuss
for
today.