►
From YouTube: Keptn Community & Developer Meeting - September 16, 2023
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
Learn more: https://keptn.sh
Get started: https://lifecycle.keptn.sh/docs/getti...
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/lifecycle-to...
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
C
D
A
E
D
E
B
B
F
F
D
E
So
we
had
a
good
attendance
which
was
awesome,
a
lot
of
people
there
and
introduced
themselves
and
a
lot
of
your
folks
and
then
Andre
gave
a
quick
overview
on
how
to
set
up
your
Dev
and
test
environments,
and
I
am
going
to
have
a
link
to
that
video
I'll
put
it
in
the
chat
in
a
bit
or
I'm.
Sorry
in
the
docs,
so
yeah
I
think
it
went
great
thanks,
Andre
for
for
doing
that
and
megave
a
nice
little
brief
overview
of
what
Captain
is
so
yeah.
D
Great
e
speaking
of
great
news,
we
just
released
also
version
08.2,
and
this
is
the
first
time
we
release
it
as
a
mono
report.
This
means
you
can
have
we
basically
released
separately
each
of
the
components
of
the
love
Captain,
and
the
great
thing
is
that
soon
to
come
is
a
separate
hand
chart
where
you
can
decide
what
to
install
out
of
the
toolkit.
So
we
will
be
finally
be
a
toolkit.
B
B
Yes,
okay,
so
during
the
first
term,
I
worked
on
the
Range
dot
interval
field
and
I
already
gave
a
demo
regarding
that
it
must
be
available
on
YouTube,
I
guess
for
the
second
term,
I
worked
on
the
aggregation
functions
which
basically
had
introduction
per
step
field
line
and
aggregation
field.
So
now
our
user
would
be
able
to
Define
an
interval
such
as
a
five
minute
and
then
a
step
interval
of
one
minute
so
like
the
interval
would
be
divided
into
five
parts.
B
In
this
case
a
one
one
minute
each
and
then
an
aggregation
function
would
be
applied
upon
that
five
five
metrics
The
Matrix
would
be
received
from
the
metric
provider,
so
I
have
a
deployment.
A
basic
Potato,
Head
application
running
already
in
my
cluster
and
Prometheus
deployed
in
my
cluster
I'll.
Just
quickly
apply
the
wait
analog
to
show
the
metric
provider.
So
this
is
a
basic
metric
provider
for
from
just
registering
parameters.
As
the
metric
provider
and
the
metric
provider
has
been
applied
and
the
captain
metric
has
been
applied
to
now.
B
Yeah,
so
the
it
is
working
properly,
the
value
is
2.84,
so,
like
the
data
was
divided
into
five
parts
and
an
average
function
was
applied
onto
the
those
that
data
and
we
finally
get
a
value
of
2.84
over
here
now
yeah.
That
was
all,
for
my
demo
just
add
a
quick
question,
while
I
Was
preparing
for
this
demo,
that
should
we
like
have
like.
We
have
an
interval
field
in
the
result
should
we
have
same
for
step
and
aggregation.
B
Yeah
the
aggregation
functions
we
have
are
a
maximum
or
the
maximum
value,
a
minimum
for
the
minimum
value.
Then
an
average
for
the
average
of
the
whole
data
random
median,
then
P90,
P95
and
P99
for
the
percentiles
of
the
data.
So
in
total
we
have
one
two,
three,
four,
seven,
seven
aggregation
functions
available.
That's.
B
B
G
Sure
do
you
want
to
keep
sharing
on
my
networks
being
flaky
and
I?
Don't
have
it
up
on
this
one
so
and
we
don't
need
to
hit
all
of
these
links.
Most
of
them
are
just
for
reference.
We
did
in
conjunction
with
the
zero
eight
two
release.
We
did
go
through
the
documentation
and
do
the
product
renames.
So
there's
a
couple
of
references
left
to
Captain
life
cycle
toolkit
and
klt
or
historical
purposes,
but
other
than
that
you
will
see
kept
in
every
place.
G
Well,
that
is
done.
If
you
see
something
we
missed
please.
Let
me
know
fast
this
next
one
I'd
like
a
little
Community,
the
I'm,
not
good
on
titles,
but
when
I
was
setting
up
the
docs
I
have
a
section,
it's
called
implementing
Captain
applications
or
something
which
is
just
a
lousy
title
and
I'm,
proposing
that
we
rename
that
section
to
be
user
guide
user
guides.
Does
anybody
have
an
objection
to
that.
G
Is
right
right
and
it's
implementing
Captain
applications
which
isn't
exactly
even
accurate?
It's
got
the
metrics
and
observability
stuff
in
it.
So,
okay,
so
I'll
do
a
PR
on
that
today
and
then
within
it
to
think
about
long-term
right
now,
there's
a
series
of
separate
pages
in
there.
There's
one
for
metrics
and
one
for
observability
or
hotel,
and
several
about
tasks
and
I
had
thought
about
subdividing
it.
G
So
it
would
be
by
the
individual
modules
yeah
which
in
a
way
I
like
in
a
way
I,
don't
I'm
inclined
to
leave
it
sort
of
the
list.
That's
there
now
it'll
be
less
work
to
implement
for
starters,
but
I'll
leave.
So
it
means
all
the
titles
will
be
when
you
click
in
the
left.
Margin
on
user
guides,
you'll
see
all
of
these
titles
and
down
the
line.
If
we
get
so
many
of
them
there
that
it
becomes
unwieldy,
maybe
we'll
have
to
think
about
subdividing
yeah,
but
that's.
D
D
G
G
G
G
G
G
We
have
we've
got
some
content
and
evaluations
took
some
material
that
was
written
up
for
an
old,
getting
started
guide
and
put
it
in
there.
It's
not
wonderful,
but
it's
better
than
what
we
had.
We
have
a
new
page
that
was
developed
about
how
you
can
use
Captain
to
run
tasks
before
and
after
the
deployment.
That's
done
not
on
kubernetes
such
as
on
a
VM.
So
we've
got
that
written
up.
We
have
a
right
now:
we've
just
got
the
existing
material
there.
G
G
They
had
a
better
title,
so
I
re-changed
the
title
and
put
a
couple
of
things
in
there
to
make
sure
that
it's
a
good
jumping
point.
When
you
come
out
of
the
getting
started
guide.
Does
it
actually
for
a
while
it
had
a
lot
of
miscellaneous,
very
interesting
information
about
implementing
tasks,
but
it
didn't
have
a
thing
that
said:
if
you
want
to
implement
a
task,
you
have
to
do
this
this.
G
So
that's
there
and
then
I
have
a
question
Natasha's
in
here,
I
pinged
him
I
was
hoping
he
would
show
up.
We
have
a
PR
that
has
a
few
comments
on
it
that
were
done
in
July
and
I
would
like
that
work
implemented.
Do
we
I
know
we
have?
We
now
have
a
policy
on
something
if
you
claim
an
issue
and
don't
do
anything
on
it
for
a
certain
amount
of
time
it
gets
stale
and
gets
available.
G
G
G
G
F
D
D
C
D
C
So
yeah,
it's
not
my
ticket
it's
from
floor,
but
I
assign
myself
and
look
into
it
previously.
So.
Currently
we
have
status
dot,
pass
or
status,
dot,
burning
properties
and
analysis,
crd
status,
which
are
not
visible
if
the
status
is
not
set
and
I
agree
with
the
Florian's
suggestion
that
we
should
actually
always
have
the
result
if
the
passwording
is
passed
or
failed
or
fulfilled
that
we
have
this
information
always
in
the
status
in
the
regard
not
regarding
in
which
state
the
crd
is
currently
the
thing
to
the
stick.
C
It
is
that
do
we
want
to
introduce
a
state
like
pending
progressing
finished,
or
do
we
want
to
handle
it
explicitly?
So,
whenever
the
status,
when
we
do
not
have
the
result,
then
the
pass
and
warning
are
set
to
false.
So
we
explicitly
fail
until
we
do
not
have
any
other,
but
I
would
probably
go
for
the
first
option,
so
we
have
a
status
dot
state
which
will
be
equal
to
pending
progressing
and
then
finished
or
completed,
and
when
it's
finished
the
pass
and
the
warning
States
will
be
set.
C
A
D
A
A
D
D
E
A
D
D
A
So
therefore,
we,
first
of
all,
don't
need
a
Prometheus
incident,
a
real
Prometheus
instance
running.
So
we
can
do
it
exactly
like
usual
here,
yeah
and
then
I
simplified
the
the
script
that
replaces
the
dates
the
from
and
two
placeholders,
because
now
we
don't
need
real
time
frames.
But
since
we
are
doing
the
mocked
response,
we
don't
really
need
any
real
values
there,
because
with
the
Maca
run
into
an
issue
where
the
command
wasn't
working,
so
simplify
that
a
little
bit
and
then
I
moved
all
the
resources
that
are
created
for
this
into
a
namespace.