►
From YouTube: Keptn Community & Developer Meeting - April 22nd, 2021
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
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
community
and
developer
meeting
it's
april
22nd,
and
we
have
quite
an
agenda
for
today.
I
think.
A
This
long
list
of
agenda
items.
A
A
First
part
that
I
want
to
announce
is
that
we
have
sent
out
the
survey
the
last
couple
of
weeks
on
the
captain
newsletter
and
we
now
rework
this
and
we
are
coming
up
with
a
new
newsletter
for
it.
So
please
make
sure
to
also
subscribe
to
the
newsletter.
A
The
link
is
here
and
the
cadence
will
be
now
at
bye,
weekly
cadence,
with
all
the
latest
information
on
the
captain
project
with
latest
releases,
latest
blogs,
tutorials
everything
you
want
to
know
about
the
project
about
the
captain
project
new
integrations,
for
example,
everything
will
be.
A
Newsletter,
so
please
make
sure
to
subscribe
to
this
newsletter.
The
link
is
already
live.
We
put
it
in
here
live
today.
Please
subscribe
via
caption.sh.
A
Also,
please
update
your
captc
installations.
We
we've
been
in
contact
with
the
quite
some
captain
users,
and
some
of
them
are
still
running
about
seven.
Something
releases.
Please
make
sure
to
update
to
the
latest
version.
Maybe
the
latest
version
is
not
even
possible
because
it's
just
being
released
right
now,
but
if
you're
have
a
dot,
seven
dot,
something
running,
please
make
sure
to
upgrade
to
0.8
and
please
make
sure
to
keep
an
updating
captain
version.
This
helps.
B
A
A
The
notification
service
is
a
little
bit
left
behind,
but
we
know
that
there
are
some
organizations
out
there
and
some
folks
out
there
that
are
using
the
notification
service
and
if
you
like,
to
contribute
to
captain-
but
maybe
you
feel
not
ready
yet
for
captain
core,
then
this
notification
service
is
the
perfect
place
to
get
started
right.
A
Now
it's
basically
covering
three
different
notifications
for
microsoft
teams,
for
slack
and
for
webex,
but
if
you
feel
that
you're
an
expert
on
microsoft
teams
or
you're
an
expert
on
slack-
and
you
just
want
to
have
this
one
functionality
being
implemented-
and
you
can
take
ownership
of
this-
please
reach
out
to
us-
we're
happy
to
assist
you
here
if
you
want
to
or
if
you
want
to
help
us
in
upgrading
the
notification
service
and
also
then
maintaining
the
notification
service
for
your
favorite
notification
platform.
A
That
would
really
help
the
project
and
really
help
this
notification
service.
So
if
you,
if
you
want
to
participate
here,
please
let
us
know
you
can
also
just
put
a
comment
here
in
in
the
chat
I
see
quite
some
folks
are
joining
today.
So
this
is
kind
of
my
ask
for
today
and
now
I've
taken
four
minutes
of
our
meeting
time.
I
hope
that's
still
fine,
I'm
already
handing
over
to
johannes
the
other
things
you
can
read
them,
but
my
two
asks
for
today.
A
I
really
sign
up
for
the
newsletter
that
will
be
the
first
newsletter
on
monday.
It
will
have
great
content.
It
will
feature
the
community
rockstars
and
all
the
latest
updates
on
the
project,
and
the
second
ask
is
please:
if
you
are
interested
in
contributing
to
captain,
maybe
the
notification
service
is
for
you.
A
Okay,
with
this,
we
can
skip
the
other
two
parts
and
I'm
handing
over
here
to
johannes
for
the
release.
Notes.
Do
you
want
me
to
click
on
this,
or
do
you
want
to
share
your
screen?
Let.
B
B
The
last
pieces
are
currently
getting
finished
so,
and
we
are
confident
that
we
will
get
it
out
the
door
by
tomorrow
and,
let's
just
take
a
look
at
the
key
announcements
of
this
release,
it's
a
patch
release
with
not
that
many
feature
changes
but
really
cool
things
that
we
as
a
team,
have
accomplished.
B
First,
with
this
release,
we
did
some
changes
in
captain,
especially
in
the
helm
chart
of
captain,
so
that
we
are
now
able
to
deploy
captain
using
captain.
This
should
also
help
us
as
a
project
to
drive
the
vision
of
having
captain's
delivery
tool
as
we
are
using
than
it
by
our
own
and
new
features
or
new
ideas.
We
can
then
test
out
based
on
our
implementation
and
the
entire
ecosystem,
and
the
entire
community
can
take
a
benefit
of
that.
B
B
Next,
to
that,
we
also
did
some
improvements
in
the
captain
core
in
the
sense
of
hardening
captain
components,
and
one
important
note
on
that
is
that
captain
services
are
now
or
containers
are
now
running
as
non-root
users
to
make
it
more
secure,
and
some
changes
have
been
made
in
the
role
in
the
airbags
of
kunitz
and
on
the
bridge
side.
There
are
several
several
enhancements
when
it
comes
to
the
service
screen,
as
well
as
to
the
sequence
screen
for
the
sequence
screen.
B
We
are
now
able
to
better
visualize
multiple
sequences
that
are
executed
in
one
particular
stage.
They
are
now
separated
and
makes
it
easier
to
follow
the
sequence
execution
and
in
the
service
screen,
as
already
have
been
shown
in
the
last
review,
but
just
let
me
mention
it
again:
there
we
now
show
not
the
list
of
executions
that
happened
in
the
past,
but
rather
their
list
of
deployments
that
are
currently
running
for
this
particular
service.
B
This
should
also
make
it
easier
to
see
the
behavior
to
see
the
status
of
your
service
and
to
get
an
understanding
what
is
currently
deployed
or
where
an
evaluation
happened,
all
right
yeah.
I
have
to
add
a
screenshot
for
that,
but
this
will
happen
tomorrow
and
please
take
a
look
at
all
the
bug,
fixes
and
minor
changes
that
have
also
been
implemented
in
this
release
and
will
then
be
shipped
by
tomorrow
and,
as
usual,
to
upgrade
your
captain
installation.
B
Please
use
the
captain
cli
with
the
command
captain
upgrade
and
distance
automatically
takes
your
captain
or
lifts
it
from
a
odot
8.1
to
an
0.8.2
version,
all
right
yeah.
I
don't
want
to
take
too
much
time
on
that,
as
we
will
see
a
couple
of
features
I
mentioned
here
also
now
in
the
review-
and
this
is
the
point
where
I
want
hand
over
to
a
little
bit
showing
us
what
she
did
on
the
notification
bar
in
the
captain's
bridge.
C
C
Yeah,
oh
so
so,
basically
yeah
the
colors
changed
and-
and
what
I
also
did
is
that
there
is
only
one
notification
left
before
I
think
there
were
perversion,
one
notification
bar.
So
if
you
were
more
than
one
version
behind
there
would
be
like
four
or
six
or
something
like
that.
So
I
think
that's
more
a
bit
more
condensed.
Now.
E
B
E
Okay,
so
I
will
go
on
so
my
part
is
the
new
the
adjustments
to
the
chart
type
of
the
evaluation
before
it
was
not
possible.
Yeah
there
weren't
any
just
about.
E
There
was
just
one
thing,
one
as
slow
shown
in
the
over
overlay,
and
now
there
are
all
active
slos
shown
so
response
time
or
response
time,
90,
etc.
E
Additional
to
that,
the
value
also
shows
two
decimals
instead
of
zero
and
also
the
the
y-axis
on
the
on
the
right
changed,
so
that
also
lower
values
are
more
visible
and
not
with
an
interval
of
50
or
something
yeah
and
that's
basically,
that's
that's.
Basically
it.
B
E
A
Okay,
so,
as
you
heard,
we
are
working
on
a
cra
two
release
and
I
have
contributed
two
quick
bug
fixes
to
it
not
really
noteworthy
to
show
then
the
next
one
I
just
want
to
quickly
talk
a
little
bit
about
it.
We
were
alerted
about
the
codecof.your
security
issue.
This
is
all
public,
so
you
can
go
and
read
it
up.
If
you
want
to
essentially
the
way
we
use
code
cough
is
a
bash
script
that
we're
loading
wire,
curl
and
then
execute
this.
A
A
We
did
we
passed
to
this
script
or
at
least
which
one
did
we
have
in
the
github
action
and
whether
any
tokens
credentials
or
whatever
were
among
those
environment,
arrivals
and
luckily,
for
us,
our
setup
was
in
a
way
that
we
didn't
leak,
any
security,
relevant
credentials
or
anything
I
can
actually.
A
I
think
I
can
show
this
here
because
I
tested
this,
why
I
have
pull
requests,
and
this
is
basically
the
way
that
that
they
said
that
you
can
test
it
with.
So
just
instead
of
calling
the
bash
script
just
check
with
and
which
environment
variables
you
have
and
if
the
action
is
still
here.
Let
me.
A
A
So
here's
the
coverage
report
yeah
there
we
go
there,
you
can
see
which
environment
variables
we
have-
and
I
think
99
of
them
are
set
by
github
automatically
like
the
selenium,
whatever
we
don't
use,
selenium,
github
path
and
etc,
and
I
think
somewhere
down
below.
There
is
some
things
from
us
from
us.
A
Although
I
think
in
in
this
case
there
is
not
and
like.
This
is
one
way
to
verify
it
and
the
other
way
to
verify.
It
is
obviously
to
look
at
the
source
code
of
this
action
and
see
if
we
pass
any
credentials
as
environment
variables,
and
also
did
that.
Then
the
answer
was
no
like.
We
don't
pass
anything
here.
A
Another
one
also
related
to
github
actions.
We
had
a
contribution
by
jos,
josh
and
what
he
basically
did
is.
He
enabled
pull
requests,
or
at
least
the
ci
workflow
for
pull
requests
on
various
event
types
which
looked
fine
when
this
pi
was
merged,
but
it
turned
out
that
it
led
to
duplicate,
runs
in
the
ci
system
on
certain
events.
So,
for
instance,
if
I
open
a
pull
request
and
I
label
it
immediately-
I
would
get
two
runs,
and
this
is
not
just
true
for
when
I
do
it.
A
This
is
also
true
when
a
bot
like
dependebot
does
it
so
we
get
many
many
duplicate,
ci
runs,
which
is
just
not
worth
the
trouble,
and
I
looked
if
it
is
possible
to
detect
duplicate,
runs
and
then
cancel
the
second
run.
But
the
answer
is
this
is
not
easily
possible,
so
I
have
basically
I
had
to
revert
this
change
and
I
have
removed
the
types
setting
here
at
all.
A
A
Okay,
right
and
last
but
not
least,
I
did
some
small
contributions,
mainly
cleanups
or
some
ci
task
updates
on
some
captains
and
books
repositories,
which
is
also
not
really
worth
to
show,
because
this
is
really
like
one
or
two
lines
of
changes
for
like
10
repositories
and
that's
about
it
and
yeah.
With
that
I'll
hand
over
to
amin.
D
Thank
you
very
much.
I'm
going
to
present
the
pro
request
regarding
the
beta
sequence
visualization
when
having
more
than
one
sequence
in
a
stage.
Actually
I
showed
you
that
one
already
in
the
last
community
meeting,
it's
yeah
in
the
case
that
we
have
multiple
sequences
configured
in
one
stage.
Previously
all
the
tasks
were
just
listed
and
yeah
us
user
had
no
idea,
but
the
next
sequence
started
and
now,
with
the
yeah
new
feature
or
in
the
new
bridge.
D
You
can
see,
for
example,
in
yeah
this
case
we
have
a
failed
delivery
and
the
rollback
sequence
is
a
separate
sequence
that
was
executed
on
the
stage
and
yeah.
You
see
those
two
sequences.
D
What
I'm
showing
you
now,
what
has
improved
since
last
time
is,
as
you
can
see,
when
I
click
on
staging
the
last
sequence
that
was
executed
is
expanded
automatically,
for
example,
when
I
check
the
def,
so
the
last
sequence
here
is
expanded
automatically,
and
what
you
also
can
do
is,
for
example,
if
I'm
interested
into
that
task,
as
you
can
see,
when
I
click
through
the
tasks,
the
link,
the
deep
link
is
also
adjusted,
and
when
I
use
this
deep
link
again,
it
will
open
that
sequence
and
focus
that
task
so
expand
the
sequence
where
this
tasks
is
task
is
in
and
also
expands
that
event
there
yeah.
D
Also
you
have
the
option
now
to
have
a
look
at
the
the
payload
of
each
event,
and
you
can
also
have
a
look
at
the
payload
of
the
sequence
event,
so
the
sequence
triggered
event
and
also
the
sequence
finished.
One
is
here
at
the
very
bottom,
so
you
have
yeah
insights
also
into
the
sequence,
triggered
and
finished
event
payloads
from
this
screen
here,
yeah.
D
D
Now,
if
the
test
fails
or
if
one
of
the
tests
at
least
fails,
the
sequence
will
stop
there.
So
actually,
this
was
fixed
by
yeah.
The
pull
request
here
from
band
and
now
that
the
sequence
or
that
stage
is
marked
as
yeah
failed
and
yeah.
No
further
sequences
will
be
executed
there,
yeah
that
this
verified,
so
that
works
now
as
expected.
B
All
right,
then,
I'm
back
again.
What
do
I
have
to
share?
I
also
touched
some
code
in
this
sprint,
not
not
really
called
but
more
manifest.
First
of
all,
I
splitted
the
kubernetes
whole
captain
configure
bridge
into
two
purposes,
one
purpose
for
the
secret
management
and
the
other
one
for
restarting
a
pod.
Why
was
this
necessary
yeah?
Because
we
had
an
security
assessment
and
there
we
got
there
twice,
that
it
makes
sense
to
split
up
this
role
into
two
components,
because
there
are
two
responsibilities
baked
into.
B
As
I
said,
the
pot
handling
as
we
have
here
and
then
the
secret
handling
as
it's
covered
by
this
part-
and
this
is
important-
and
this
is
the
best
practice
to
have
all
secret
related.
B
B
Collection,
I
think
not,
I
think,
can't
really
show
that
it's
just
what
changes
in
their
role
of
of
kubernetes
and
the
second
one
was
very
similar.
B
B
Let
me
just
show
you:
I
created
a
captain,
get
secrets,
role
and
yep
assigned
it
to
the
kubernetes
to
the
configuration
service
so
that
he
just
has
the
permissions
to
read
and
not
to
delete
or
update
or
do
any
other
things
with
services,
as
he
does
not
require
that.
B
Here
you
get
now
the
recommendation
that
you
should
accept
it,
and
some
changes
have
been
made
here
in
the
text
as
well
as
here
on
on
the
username.
So
here
in
the
top
right
corner.
There
are
also
some
changes
made
in
the
text
as
well
as
year.
This
toggle
is
enabled
by
default
and
not
disabled
anymore.
A
I
have
a
recommendation
or
an
idea
here
now
that
we
release
every
four
weeks,
or
at
least
that's
the
plan,
how
about
we
notify
the
user?
Let's
say
six
weeks
after
the
installation,
hey
by
the
way,
you've
disabled
the
version
check.
If
you
want
to
get
blah
blah
blah-
and
please
enable
it
again
because
somehow
we
can,
we
can
estimate
that
there
is
a
new
version.
B
Correct
and
thanks
for
bringing
it
up,
because
I
forgot
that
we
do
that
now,
after
a
couple
of
days,
we
delete
the
configuration
order.
We
we
again
tell
the
user,
you
don't
have
this
enabled
when
you
do
that
you
get
notifications
about
new
releases.
How
many
days
is
it.
B
A
Weekly
week,
okay,
let's,
let's
see
how
users
respond.
That
would
be
annoying.
For
me
to
be
honest
if
it
is
weekly,
but
let's
say
every
four
weeks
or
something
because
that
makes
more
sense
for
our
release
schedule,
but
let
let's.
A
I
think
it's
a
really
cool
feature
that
we
now
enable
this,
as
people
were
not
sure
how
to
enable
it
again,
and
I
think
it
really
helps
them.
B
A
Yeah,
if
we
get
responses
that
it's
it
might
be
annoying
for
someone,
we
can
always
change
it.
A
B
All
right
and
then
since
lauren
is
not
here
today,
he
asked
me
to
show
what
he
did
in
this
sprint
and
yeah.
Let
me
go
over
his
issues.
First
of
all,
he
worked
on
a
github
action
that
allows
us
to
set
up
a
captain
installation
on
a
kubernetes
cluster.
B
B
Yep,
for
some
reason,
I'm
on
the
wrong
one
that
one
I
messed
up
with
the
links.
As
I
said
here,
he
pro
as
an
indie
captain
organization.
He
provided
a
github
action
that
prepares
who
need
this
cluster
on
tke
and
then
installs
captain
on
there
and
additionally,
you
get
all
the
features
and
scripts
like
installing
istio.
B
Then
this
one,
as
the
name
already
says
it,
sets
up
the
captain
project
with
doing
a
captain
grade
project
antenna
captain
create
service,
and
there
are
then
yeah.
That's
basically
it
setting
up
the
kubernetes
cluster
installing
captain
on
top
and
then
setting
up
the
project
and
service
so
that
we
are
then
ready
to
trigger
the
first
deployment.
B
You
can
also
reuse
that
action
when
you
want.
You
can
bake
it
into
your
ci
pipeline,
and
so
you
can
then
deploy
dynadres
on
your
cluster
and
also
set
up
or
deploy
the
diameters
sli
service
and
the
dynadris
service,
as
they
are
used
by
captain,
so
that
you
have
done
a
full
monitoring
available
and,
as
I
said,
that
one
is
currently
not
merged,
but
let's
just
take
a
look.
What
he
did
yeah
he
provided
the
action
itself
that
takes
a
couple
of
input.
B
Parameters
like
the
dynadris
tenant
api
token
pass
token
and
then
an
option
whether
to
enable
or
disable
self
monitoring
or
the
name
of
the
project.
There's
version
of
the
dynadress
service
and
time
address
sli
service
and
based
on
these
parameters.
It
then
sets
it
up
the
monitoring
and
monitoring
on
your
environment
and
yeah.
This
is
basically
basically
done
by
this
deployed:
dynadris
dot,
sh
script.
A
By
the
way,
because
you
just
have
this
open
line
30
to
line
38,
this
is
a
good
example
that
people
can
improve
on
not
criticizing
here.
Just
saying
it
could
be
improved
because
you
here
have
the
api
token
and
the
pass
token
as
an
environmental
arrival,
and
that
would
be
an
attack
vector
that
was
used
for
code
coverage,
dot
io.
A
In
our
case,
I
guess
it's
not
that
much
of
a
deal,
because
the
deploy
dynatrace's
h
script
is
in
the
same
repository
as
what
is
environment
is
defined.
But
the
moment
you
load
something
from
an
external
service
here
you
basically
risk
exposing
such
variables,
so
I'll
actually
keep
that
in
my
mind
and
see
if,
if
we
can
improve
something
here
or
at
least
recommend
it
to
to
florian.
B
Thanks
for
bringing
it
up,
yeah
security
is
always
an
important
point
to
consider
and
when
we
can
improve
especially
at
these
two
lines,
then
we
should
do
that.
A
Well,
for
one,
you
don't
need
it
as
an
environment
arrival.
You
could
pass
it
as
a
parameter
into
the
script.
That
only
is
that's
like
30
percent
better,
but
not
100
percent
better
and
the
other
option
I
need
to
investigate.
It
basically
depends
who
needs
the
secrets,
and
maybe
you
can
handle
the
secret
outside
of
the
action
somehow
okay,
but
this
is
really.
This
is
now
within
the
action
itself.
A
So
unless
there
is
any
code
loaded
afterwards
shouldn't
be
a
problem,
but
as
soon
as
we
load
some
code
from
outside,
obviously
it
could
be
a
problem
so
right
now
this
is
safe.
That's
what
I
want
to
clarify,
but
we
need
to
make
sure
it
will
be
safe
in
the
future.
When
we
do
some
changes
as
well.
B
Got
it
thanks
all
right
yeah
and
with
these
two
actions
in
place
now,
florian
also
got
or
I
went
one
step
further
because
he
combined
everything
into
a
github
workflow,
and
this
one
now
allows
us
to
create
a
cluster,
install
cabin
setup
monitoring
and
trigger
the
first
delivery.
And
let
me
show
you
that,
based
on
his
repository.
B
B
On
his
private
account,
but
will
be
moved
then
into
captain,
but
what
we
can
see
here
in
the
main
dot
jamal
of
this
work
workflow
I
mean
it's
really
straightforward.
As
I
said,
it's
first
set
up
captain
in
the
sense
of
creating
the
cluster
and
installing
then
this
particular
captain
version.
This
is,
then,
the
captain
that
takes
care
of
doing
the
delivery.
B
B
B
Just
to
let
you
know
this
one
should
be
from
a
logical
point
of
view
on
this
order,
and
I
think
we
are
currently
working
on
an
improvement
on
that,
so
that
this
production
environment
is
closer
to
that
because
it
it
kind
of
groups
or
should
be
in
this
particular
group,
and
what
we
have
now
right
here
is
a
deployed
captain
installation
in
depth
hardening
and
not
yet
in
broad,
because
here
we
set
up
an
approval
process
where
someone
has
to
take
care
of
accepting
it
and
then
triggering
the
delivery.
B
And
let's
just
take
a
look
into
this
delivery
process
because,
as
I
said,
the
script
also
uploads
jamita
scripts
and
they
are
executed,
and
we
have
also
an
evaluation,
then
are
triggered
to
get
more
insights
about
the
currently
the
data
store.
And
here
we
are
taking
a
look
at
the
cpu
time.
Error
rate
io
timeout
response
time
as
robot,
and
as
we
also
want
to
integrate
this
particular
setup
in
our
ci,
so
that
we
have
then
daily
deliveries.
B
We
get
more
and
better
insights
into
captain
itself,
so
that
we
also
can
improve
there
and
also
be
more
also
get
informations
when
something
get
worse,
yeah
and
I'm
really
looking
forward.
This
is,
I
think,
the
last
missing
piece
on
that
story
to
also
link
the
github
action.
I
showed
you
right
here
that
one
with
our
nightly
build
so
that
we
can
deliver
a
captain
on
a
daily.
B
B
A
Wow
there
is,
it
was
a
lot
of
content,
really
cool
progress,
so
right
now
there
are
no
questions
coming
in.
So
from
from
my
side,
just
the
kind
of
the
ask
please
sign
up
for
the
newsletter.
We
will
start
on
monday
to
send
it
out
and
it
will
always
have
the
information
on
the
captain
project
like
also
on
the
latest
releases.
So
if
you
want
to
stay
up
to
date,
please
make
sure
to
subscribe
to
the
newsletter
the
link.
A
And
you
will
find
it
also
on
captain.sh
community.
You
will
find
that
the
newsletter
there
if
there
are
no
more
questions
coming
in.
I
think
we
can
close
it
a
little
bit
earlier
and
I'm
really
looking
forward
to
the
new
release
to
execute
my
captain
upgrade
tomorrow
and
everyone
that
is
also
running
a
1.8
installation
of
captain
or
all
the
installation
of
captain
make
sure
to
upgrade
and
to
always
get
the
latest
and
greatest
of
captain.
A
Then
thanks.
Everyone,
I
think,
for
the
other
parts
we
kind
of
also
can
keep
it
for
the
community
focus
meeting
for
next
week.
So
we
are
closing
it
here
and
thanks
everyone
for
joining,
see
you
all
next
time.