►
From YouTube: Keptn Community & Developer Meeting - Feb 17, 2022
Description
At this meeting we discussed the Keptn 0.13.0 release, the upcoming Advisory Board meeting, and improvement in the Prometheus Integration Service.
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
Sign up to our newsletter: https://bit.ly/KeptnNews
A
And
the
recording
reason
hi
all
thanks
for
joining
the
captain
community
meeting.
Just
a
quick
reminder:
we
did
two
changes
in
the
schedule,
so
we
will
keep
captain
community
meetings,
as
is
during
this
time
slot
for
pm
utc,
but
they
will
happen
only
every
two
weeks
because
we
agreed
that
developer
meetings
would
start
at
9.
00
am
utc
effective
next
week.
A
So,
basically
now
we
have
captain
community
meetings
in
a
park
in
amazon
on
wednesday
in
in
the
united
states
and
zone
right
now
and
also
developer
meetings
on
thursdays
every
other
week
later
we
might
merge
meetings
somehow,
but
for
now
this
is
the
arrangement.
A
So
let
me
share
my
screen
and
yeah
thanks
a
lot
to
jorgen
and
patrick
for
joining
patrick.
Would
you
like
to
introduce
yourself.
A
How
do
you
see
it
so
yeah?
What
do
we
have
in
legend
today?
So,
first
of
all
your
reminder
we
got
through
it.
Then
we
have
a
0.30.0
release
actually
refresh
over
the
boat
or
the
ship.
I'm
not
sure
what
terminology
we
use
here
and
yeah.
I
believe
that
yeah
three
hours
ago,
so
what
the
key
items
here
that
there
is
a
lot
of
ux
improvements
for
the
bridge,
including
management
for
secrets,
uniform
market
location,
etc,
etc.
A
Also,
there
is
foundation
work
for
open
id
support,
so
now
you
can
use
open
id
to
connect
to
bridge
cli
and
distributor.
There
is
still
no
permission
model
behind
that,
but
it's
also
on
the
scope
of
cap
60.
So
looking
forward
to
that
to
be
landed.
A
Thank
you
so,
basically,
that's
all
for
the
release.
Try
it
out.
It
was
available
for
preview
and
yeah
thanks
a
lot
to
everyone
who
was
involved
and
highlight.
This
is
not
a
break-in
release,
so
you
should
be
able
to
flawlessly
update
okay,
then
the
next
topic
yeah
today
we
have
captain
advisor
report
meeting.
So
captain
has
a
number
of
advisors-
seven,
if
I
recall
correctly-
and
we
finally
be
able
to
organize
a
meeting
for
this
board-
I'm
currently
preparing
a
slide
deck
to
summarize
what
has
happened
since
the
last
meeting
in
september.
A
So
if
you
participated
in
a
christmas
update,
it's
basically
more
or
less
the
same
slide
there
with
some
updates.
So
if
you
want
to
review
it
and
share
some
feedback,
please
go
ahead,
so
I
will
be
presenting
three
topics
there.
So,
firstly,
incubation
status
too
long
did
the
trade
we
are
still
waiting
for
cncftc
and
we
are
still
looking
waiting
for
tax
security
to
start
the
security
review
of
captain,
but
that
we
also
don't
have
eta.
A
It
should
have
happened
this
month,
but
obviously
it's
not
happening
so
no
idea,
then
there
will
be
roadmap
update,
including
some
new
deliveries,
artifact
hub
job
executor,
service
event,
hooks
also
tutorial
changes
updates
to
the
roadmap,
and
specifically
today
we
will
go
through
the
documentation
roadmap
through
community
roadmap
and
also
through
the
feature
of
the
map,
because
what
was
presented
in
september,
everything
is
delivered,
it's
awesome
and
we
have
a
few
topics
on
the
list,
so
we
have
zero
downtime
upgrades.
We
have
airbag.
We
have.
A
A
part
of
their
back.
We
also
have
authentication
part
of
an
id
part
which
probably
deserves
to
be
a
separate
item
on
the
roadmap
plus.
We
still
need
to
update
the
roadmap,
but
we
have
jobs
work
by
thomas,
and
these
are
basically
his
stories
happening
right
now
and
if
you
would
like
to
share
any
additional
topics,
we
should
add,
for
example,
for
integrations,
etc.
Please,
let
me
know
I'm
happy
to
update
the
slide
deck.
I
have
plenty
of
time,
research.
B
I
mean
I
don't
know
how
much
the
ecosystem
around
captain
is
represented
in
in
that
meeting,
like
prometheus
service
chop
executor
service,
artifact
hub.
These
three
would
be
my
highlights
from
a
personal
perspective,
but
I
also
don't
know
if
that's
actually
in
scope
or
if
this
is.
A
A
C
B
A
Actually,
yesterday
we
had
a
user
group
with
adam
and
they
said
explicitly
that
probably
he
created
the
most
of
integrations
right
away
than
anybody
else
by
zapier
and
a
eft
so
yeah.
But
what
is
it
definitely
here?
Support
for
helm,
management
for
parameter
service
and
other
is
something
built
into
highlight.
I
think.
B
Some
of
those
are
really
just
technical
depths
that
we
resolved.
I
don't
think
those
are
the
real
highlights.
I
think
the
fact
that
we
are
making
sure
that
there
is
a
lot
of
work
now
putting
being
put
on
all
of
these
services
with
dedicated
people
as
well.
I
think
that's.
What
we
should
highlight
doesn't
need
to
be
the
help
chat
management
itself.
This
is
just
like
a
technical
depth
that
we
resolved.
Okay,.
A
Okay,
so
if
you
see
anything
else
that
could
be
added
just
edit
on
this
slide
also
yeah,
I
will
spend
some
time
for
the
communication
roadmap.
A
B
I
will
present,
I
will
present
some
of
the
changes
of
prometheus
service
now
in
my
next
part
anyway.
So
if
you
feel
like
something
is
really
awesome,
then
feel
free
to
take
it
in
there
sure
it
will
do.
Okay,
just.
A
C
I
just
saw
it
so
I
didn't
know
that
that
there
are
these
lights
for
for
today,
so
I
just
updated
the
yeah.
C
A
B
A
Yeah
adoption
community
marketing-
I
just
put
a
few
funny
screenshots,
but
basically
that's
it,
and
also
also
what
we
discussed
at
the
community
meetings
keep
on
valencia.
So
it's
we
are
still
confirming
it,
but
we
want
to
have
this
event
so.
A
A
But
yeah,
basically,
that's
it
from
me
for
today,
as
you
may
have
noticed,
we
have
also
started
contributing
slide
channel
to
help
newcomer
contributors,
but
yeah.
It's
a
rather
minor
update
before
it's
fully
documented,
but
hopefully
it
will
let
other
contributors
and
yeah.
Maybe
other
topics
which
was
highlighting
that
we
now
officially
reports
the
data
dope
integration
service
and
captain
sandbox
was
promoted
to
the
sandbox
on
tuesday.
A
Actually,
maybe
it's
also
something
I
would
like
to
add
to
the
roadmap,
because
it's
important
it's
basically
a
third
major
sli
provider
yeah.
We
also
discuss
the
asia
data
explorer.
Maybe
it
makes
sense
to
it
to
the
roadmap
if
the
dimitri
is
interested
but
yeah.
These
are
also
important.
C
Topics-
oleg
do
you
know,
have
the
like
the
statistics
in
terms
of
of
usage
or
adopters.
Have
they
signifi
significantly
changed
from
the?
From
last
time
we
presented
to
the
advisory
report.
A
So
currently
we
had
around
90
to
100
active
installations.
The
number
actually
jumped
before
dynasty
is
performed
because
they
were
workshops
etc.
But
this
is
approximate
number
what
I
actually
see
we
have.
I
see
research
in
downloads
and
the
in
traffic
to
slug.
So
even
if
the
number
didn't
change
significantly,
it
looks
like
the
community
becomes
more
active
and
yeah.
Hopefully
it
will
have
communicative
effect.
B
B
Which
means
to
me
that
there
is
more
people
in
the
captain
open
source
that
use
prometheus
as
well.
That
shows
two
things:
a
that:
the
efforts
that
we've
put
into
prometheus
or
into
prometheus
service
before
which
were
primarily
driven
by
jung.
So
thanks
for
that
are
now
finally
well
shaping,
and
we
can,
we
can
see
the
fruits
of
it
and
two.
We
need
to
continue
that
effort
and
I
hope
that's
okay,
if
I
just
use
this
as
a
segue
now
for
my
topic,
yeah,
please.
A
Go
ahead
with
your
topic,
and
thanks
for
this
highlight,
I
quarterly
believe
that
we
should
have
prometheus
as
a
first-class
citizen
well
and
actually
currently,
there's.
B
B
Yeah,
okay,
I
will
so
you
can
see
my
browser
now.
Yes,
okay,
yes,
so
let
me
quickly
go
over
the
changes.
We
did
to
prometheus
service
the
last
couple
of
weeks,
first
of
all,
big
thanks
to
paolo
one
of
our
new
contributors
here
who
started
by
making
sure
that
we
no
longer
need
to
delete
or
actually
restart
prometheus
itself.
When
we
update
its
configuration,
he
also
started
with
some
little
refactoring,
but
just
to
give
you
a
good
feeling
what
it
means
is
we
removed
this
function,
delete
pot
which
we
were
calling.
B
Probably
here
yeah,
so
what
we
did
is
we
applied
the
configuration
here
to
prometheus
alert
manager
to
prometheus
by
editing
the
config
map,
and
then
we
force
restart
that
prometheus
by
deleting
the
pods.
This
is
not
necessary
anymore,
since
a
couple
of
prometheus
versions,
because
there
is
a
config
reloader
built
in
so
this
is
really
nice
and
what
this
brings
us
is.
B
We
no
longer
need
to
reconnect
to
prometheus
if
we
do
a
port
forward
and
obviously
we
don't
lose
monitoring
data,
because
if
you
restart
prometheus,
it's
gone
like
for
a
minute
or
two
and
you
lose
monitoring
data
for
that
time.
So
really
great
enhancement,
and
that's
why
I
also
want
to
share
the
code
because
it
was
a
really
simple
enhancement.
B
Second,
enhancement
from
polo
was
that
we
no
longer
generate
alerts
like
we
configure
alerts
unless
a
remediation
yaml
is
present,
so
captain's
remediation
yaml.
Just
to
can
you
see
my
ide
now.
C
B
No
okay,
then
I
will
quickly
show
it
here.
B
So
captain's
remediation
yaml
is
looks
like
this.
It
says
if
a
problem
happens,
do
something
like
scale
up
or
toggle
a
feature
flag
or
you
can
configure
it
basically
to
do
a
lot
of
things
and
if
that's
not
present,
there's
no
point
for
prometheus
to
configure
alerts.
Because
what
would
happen?
Is
you
get
alerts
for
staging?
You
get
alerts
for
death
and
you
really
only
want
alerts
for
production.
If
that's
where
your
remediation
yaml
lives,
then
there
was
some
refactoring
involved.
I
don't
want
to
go
into
detail
for
that
long
story.
B
Short
less
code
means
less
bugs,
and
actually,
with
that
refactoring
we
managed
to
fix
a
very
old
bug.
So
that's
good
a
feature
request
that
we
did
is
we
now
allow
labels
and
deployments
to
be
used
as
as
live
placeholders,
so
I
will
actually
show
that
on
an
example
later,
but
we
can
now
use
dollar
deployment
in
the
sli
config
before
we
weren't
able
to
do
that.
B
I
don't
have
an
example
for
the
labels,
but
they
work
the
same
here
last
but
not
least
again,
some
refactoring
and
support
for
captain
0.12,
which
is
just
updating
the
distributor
and
adding
some
environment
variables.
B
C
Sorry
encryption
does
it
change
anything
because
oleg
man
mentioned
captain
013
and
here
it's
a
0-12.
B
A
Many
so
we
thoroughly
have
compatibility
matrix
for
services,
but
this
compatibility
matrix
is
always
dated.
So
we
need
to
something
change.
Something
and
yes,
we
discussed
last
week
so
mike
mcrobert's
joined
to
help
with
the
documentation
and
developer
experience.
A
So
once
we
get
passed
through
all
the
onboarding
stage,
we
can't
actually
do
massively
work
of
how
the
site
works,
and
we
currently
think
about
replacing
the
current
documentation
site
by
antoine
engine
is
a
lot
of
automation,
including
maybe
building
compatibility,
metrics
and
other
funny
things.
Let's
see.
B
There
we
go
so
now.
I
can
like
you
see
in
my
terminal
now,
and
you
see
my
ide
now.
Does
this
work
yeah?
Yes,
okay,
so
I
want
to
show
this
by
example,
and,
first
of
all
I
want
to
make
a
port
forward
to
my
prometheus
server,
which
is
going
to
be
available
on
localhost
8068..
B
B
I
forgot
to
add
prometheus
here
and
what
this
is
doing.
In
the
background,
it
is
prometheus
service
trying
to
fetch
the
slo
configuration
the
sli
configuration
and
a
potential
remediation
configuration
and
creating
targets
and
alerts
in
prometheus,
and
all
of
this
is
happening
without
prometheus
restarting.
So,
if
you
look
at
the
pots
of
prometheus,
you
can
see
they're
running
for
34
minutes,
they're
not
being
restarted,
and
if
we
refresh
here
at
some
point,
they
should
show
up
the
config
map.
Reloader
runs.
I
think
once
per
minute.
B
Let's
see
if
there
are
alerts
already,
no,
let's
wait
for
them
to
show
up.
In
the
meantime,
I
will
show
you
another
question
in.
C
The
meantime
did
you,
you
also
had
to
upgrade
the
prometheus
version
right
because
it
was
a
quite
old
version.
The
time
I
last
joined
the
the
meetings
it
was
like
212
or
something.
B
I
actually
don't
know
which
version
we're
using,
because
we
are
very
pragmatic
about
that
now
and
we're
just
using
the
prometheus
helm
chart
that's
provided
by
the
prometheus
community
and
with
that
already
comes
a
very
nice
version
that
just
works
out
of
the
box.
Yeah.
A
B
B
So,
let's
see
yeah
there
we
go
prometheus
service
has
now
configured
some
targets.
Some
of
them
are
red,
don't
worry
about
them,
focus
on
the
ones
that
are
not
red.
They
are
actively
fetching
metrics
and
scraping
the
metrics
endpoint.
B
It
well,
it
takes
some
time
again
and
then
it
will
show
up
eventually
in
prometheus
all
right,
while
we
wait
for
that,
I
want
to
quickly
jump
into
the
sli
configuration
and
the
dollar
deployment
flag
and
motivate
why
we
actually
need
it.
So
before
we
had
two
sli
configs
for
prometheus
in
our
examples
repository
one
that
we
call
sli,
config,
prometheus
blue-green
and
one
that
we
call
self-healing
and
the
main
difference
between
those
two
is
essentially
here
that
we
are
focusing
on
service
project
stage.
B
So,
for
instance,
carts
dash
sock
shop,
dash
production,
dash
cannery
or
for
the
cell
filling
part
we're
focusing
on
the
primary
part,
because
in
this
blue
green
deployment,
focused
scenario,
what
we
want
to
do
is
we
want
to
fetch
metrics
of
the
cannery
pot.
This
is
the
application
under
test
and
in
the
cell
healing
scenario,
we
want
to
fetch
metrics
and
produce
alerts
for
the
primary
part,
which
is
the
application.
That's
well
deployed
out
there
for
everyone
to
use
and
with
the
changes
that
I
did,
we
can
now
just
write
dollar
deployment.
B
And
completely
get
rid
of
the
self-healing
one
here
and
we'll
probably
even
rename
this
one
to
just
slight
config
prometheus
same
as
we
have
as
like
config
dyna
trace.yaml,
so
we're
now
closer
towards
future
parity
between
those
two
as
well.
Okay,
in
the
meantime,
er
prometheus
is
telling
me
it
has
been
successfully
configured.
B
Let's
take
a
look
if
there's
an
alert.
Yes,
so
the
allot
has
been
created
and
we
should
be
able
to
see
it
has
been
created
for
the
primary
part,
and
if
you
wonder,
where
is
the
values
coming
from
like
900
here?
This
is
coming
from
the
slo
configuration
that
we
that
I
have
already
pre-applied
before,
but
also,
as
you
see
it's
only
this
alert
for
production
here
and
there
is
no
alerts
for
staging
or
death
or
any
other
thing
that
shouldn't
be
there
all
right
with
that.
A
So
for
me,
I
really
like
the
integration
with
parameters
and
how
it
works.
Actually,
one
topic
I
keep
in
mind
is
headless
primitives,
so
the
motor
they
recently
produced.
So
what's
your
take
on
that
christian,
do
we
see
it
would
be
reasonable
to
integrate
it
inside
parameter
service?
A
Sorry,
can
you
repeat
the
question
so
recently
there
was
a
new
project
introduced
in
trapezos,
basically
a
headless
parameters
which
just
access
forwarder
for
open
telemetry,
so
I
wonder
whether
it
would
be
feasible
and
reasonable
to
implement
it
in
the
service
or
maybe
another
service.
B
It
would
make
more
sense
to
have
a
generic
open,
telemetry
based
service
and
then
integrate
that
with
the
open,
telemetry
prometheus
headless
project,
because
you
should
really
focus
on
do
one
thing
and
do
it
well
and
prometheus
service
as
it
is
right
now
well
right
now,
after
refactorings,
it
is
okayish,
but
I
wouldn't
want
to
add
more
content
to
it.
Let's
put
it
like
that.
A
Great
well
yeah
having
open,
telemetry
slide
provider
would
be
awesome
because
you
could
access
metrics
right
away,
though
without
prom
qrl
etc.
I
guess
slo
part
is
going
to
be
well
sli
part.
It
will
need
to
be
complete
right
on
the
service
side,
which
makes
it
a
bit
less
trivial
than
the
existing
computations.
B
B
Thanks,
okay,
then,
I
have
one
more
thing
to
just
quickly
announce
here
we
are
planning
to
deprecate
the
generic
executor
service,
which
is
a
captain
sandbox
project.
That
hasn't
really
received
a
lot
of
updates
in
the
last
couple
of
months,
and
there
is
a
let's
say,
a
natural
successor
of
generic
executor
service,
which
is
the
job
executor
service,
which
is
actively
maintained
and
getting
bug
fixes
security
updates,
etc.
So
we're
really
just
trying
to
to
get
grasp
now.
B
What
is
the
impact
of
deprecating
generic
executor
service?
Is
anyone
really
using
out,
is
using
it
out
there
and
how
are
they
using
it?
We
know
of
a
couple
of
people
already,
but
you
know
we,
we
cannot
really
estimate.
Is
it
five
people?
Is
it
100
people?
So
sorry?
So
if
you
are
using
generic
executor
service,
please
I
will
share
a
link
or,
as
a
link
actually
shared
in
the
meeting
notes,
go
to
that
link
post
on
the
github
repository
or
post
on
slack
even
get
in
touch
with
us.
B
Let
us
know
that
you're
using
it
it's
how
you're
using
it.
This
will
help
us
with
our
deprecation
yeah.
A
A
A
Well,
maybe
it's
something
we
will
need
to
discuss
eventually,
because
when
the
number
of
adoptions
grow,
making
decisions
about
duplicating
some
bits
of
apis
etc
would
be
really
important
and
without
usage
analytics.
It's
super
difficult
to
make
guesses,
but
we
passed
through
that
in
jenkins,
especially
when
we
were
doing
java
11
upgrade
and
we're
dropping
some
features
which
were
not
feasible
visible.
B
I
agree,
however,
we
shouldn't
make
it
too
complicated
for
sandbox
projects
in
the
end.
Sandbox
is
really
a
sandbox,
as
it
is
stated
there
and
right
now
we
are
just
seeing.
There
is
a
better
project
out
there
than
let's
just
use
the
beta
project
and
ensure
all
people
are
informed
about
the
change
and
are
able
to
to
migrate.
C
The
easy
plant
to
also
let's
say,
deprecate
other
services
that
are
in
the
sandbox
for
quite
some
time
and
have
not
been
maintained
and
then
last
time
I
checked,
we
had
a
couple
of
projects
that
are
they
never
made
the
jump
to
to
a
higher
captain
version,
but
they
are
not
maintained
by
the
smaller
captain
team
by
that,
but
like
really
the
community,
so
it
might
also
be
difficult
to
get
a
hold
of
them
again.
B
B
One
example
that
comes
into
my
mind
that
we
can
discuss
about
deprecating
would
be
the
low
cost
service
and
the
litmus
service,
because
eventually
we're
not
there
yet,
but
eventually
the
job
executor
service
can
take
both
of
these
use
cases.
And
when
that's
the
case,
then
we
can
discuss
deprecating,
those
we're
not
quite
there
yet
so
right
now.
I
think
it's
too
early
to
say
that,
but
I
don't
know
all
like.
What's
your
opinion
on
on,
let's
say
the
many
outdated
repositories
in
sandbox.
A
At
that,
my
approach
that
said
box
has
clear
quality
expectations,
so
the
repositories
might
be
abundant,
they
may
be
unstable,
they
might
have
no
maintainer,
and
if
you
use
it
of
this
representative,
there
is
a
clear
way
contributing
to
the
project.
A
Finding
someone
who
would
contribute
on
your
behalf
so
same
as
any
other
project's
work
players
rankings
whatever
there
is
always
this
huge
tale
of
integration
service,
let's
say
difficult
maintenance,
so
as
long
as
they
work
in
principle
as
long
as
they
don't
impact
other
integrations
and
as
long
as
they
do
not
impact
evolution
of
the
project,
it's
fine
to
just
keep
them
lingering
when
the
proper
expectation
is
set.
But
what
must
not
happen
is
that
these
projects
create
some
issues
for
evolution
of
captain
itself,
because.
C
I
I
would
be
happy
to
to
basically
set
up
again,
maybe
a
connection
to
when
we're
talking
about
locust
or
litmus
to
the
maintainers
of
the
of
the
projects,
because
I
was
heavily.
C
For
locust
and
litmus
and
low
cost,
I
will
put
it
in
the
chat
because
we
we
created
a
video
on
this
integration
and
this
video
is
still
featured
on
the
locust
website.
So
whenever
we
change
something
that
is
completely
changing
the
approach,
and
that
would
mean
if
we
remove
the
local
service
and
integrating
it
into
the
job
executor,
then
we
are
changing
completely
approach.
How
we
do
it,
then
we
might
want
to
reach
out
to
lars.
C
A
Yeah
also
for
such
tools,
we
always
need
to
keep
in
mind
that
at
some
point
there
might
be
use
case
for
the
web,
ui,
etc,
and
immediately
after
that,
just
using
job
executive
service
becomes
impossible.
C
One
last
item
yeah:
all
right,
I
will
be
presenting
captain
and
especially
the
journey
of
captain
in
the
cncf
next
week
on
a
kubernetes
meetup.
Virtually
it
will
be
in
in
cards
in
syria
and
it
will
be
yeah
more
focused
on
the
on
the
cncf
it
will.
We
will
do
it
in
german,
most
probably
because
the
the
meetup
language
is
german
and
it
will
be
a
short
presentation
with
daniel.
Not
I
cannot
remember
who,
which
company
is
affiliated
with,
but
it
will
be.
C
They
were
reaching
out
and
wanted
to
know
how
how
it's
actually
working
within
the
cncf
and
how
projects
are
going.
So
just
heads
up.
A
Have
a
great
presentation
and
yeah,
so
you
have
access
to
captain
account
or
just
focus
in
social
media
outreach
and
community
channel.
So
if
you
don't
forget,
we
try
to,
we
will
try
to
get
a
final
push
for
social
media
and,
if
you
forget
that
these
fingers-
okay,
thanks,
thank
you
too,
and
yeah
thanks.
Everyone
thanks!
So
much
have
a
nice.