►
From YouTube: Keptn Community & Developer Meeting - August 30, 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/getting-started/
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/lifecycle-toolkit
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
So
please
add
yourself
to
the
attendee
list:
I
share
in
the
chat
again
once
more
just
for
be
extra
safe
to
attend
a
meeting,
and
if
you
have
any
topics,
please
add
them
to
the
list
and
I
think
we
can
kick
it
off
with
the
community
time
block
from
Benita.
But
this
is
the
person
that
has
issues
joining,
so
maybe
they
will
watch
this.
Video
I
cannot
share,
unfortunately,
because
I
don't
have
a
login
I.
B
A
A
Maybe
can
be
caused
by
certain
file,
so
maybe
let's
deserve
some
time.
When
we
have
some
slack
of
time
to
support
this
Community
member,
then
some
announcement
from
me
and
Anna
will
be
at
kubecon
North,
American
Chicago,
and
we
had
our
talk
accepted
for
the
maintenance
track.
So
soonish
there
will
be
the
schedule
of
different
sessions
and
there
will
be
one
also
where
we
will
present
captain.
A
B
Yes,
just
not
links
if
you
want
them
we're
not
going
to
go
over
everything
in
just
wanted
to
update
what
we're
working
on
right
now,
working
on
the
contributing
guide.
We've
been
trying
to
do
that
work
for
several
months
and
it's
oh
little
bits
were
getting
done
so
I
decided
it
was
time
to
go
in
and
do
some
more
things.
So
these
are
open
PRS
that
are
out
there
if
anybody's
interested
in
reviewing
them.
B
A
A
A
B
B
The
sort
of
get
piece
would
love
to
have
some
feedback
from
community
members,
because
that's
really
hard
we're
using
basic
git,
but
so
this
is
supposed
to
be
a
little
bit
of
helpful
material
and
to
know
whether
you've
done
too
much
too
little
Etc
dark
Source
structure
and
a
new
one.
Thanks
to
Adam
I,
actually
wrote
that,
but
Adam
did
the
work
on
developing
with
GitHub
code
spaces
and
then
we've
added
a
little
piece
about.
B
We
have
questions
klt
by
Design
is
not
a
pipeline
and
it
doesn't
actually
do
sequential
execution,
but
people
want
to
know
how
to
do
it.
So
there
are
a
couple
of
ways
to
do
that.
So
this
summarizes
that
we
have
contribution
from
the
community,
with
information
on
custom,
grafona
dashboards,
an
improvement
in
the
instructions
for
running
otel
and
some
better
info
in
the
readme's
for
python,
runtime
and
container
runtime
Runners.
For
kept
in
tasks
so
next
week
we
need
to
coordinate,
but
I
think
it
sounds
like
next
week.
B
C
B
C
At
the
same
time
would
be
great
on
the
same
day.
So
if
we
want
to
just
coordinate
what
that
time
frame
is
I'm
good
to
do
that,
I
actually
wasn't
sure.
I
haven't
posted
because
I
think
our
our
blogs
are
through
medium
and
I,
haven't
actually
posted
through
medium
I.
Don't
even
have
an
account
there.
Does
anyone
have
an
account
there
and
that
could
post
the
blog
I?
The
draft
is
like
I,
don't
know:
99
complete
I'm
working
on
like
couple
images
that
we
may
want
to
put
in,
but.
A
A
A
D
C
B
C
B
Through
and
do
it,
but
then
it
all
has
to
be
approved
and
there's
so
there's
a
question
and
do
we
want
to
I'd
like
the
tree
as
quiet
as
possible,
so
but
I
think
we're
planning.
We've
got
a
bunch
of
open
PR's
right
now.
So
then
it
comes
into
Giovanni's
people
and
clashing
with
their
other
responsibilities.
I.
A
B
Soon
as
possible,
okay
and
then
yeah,
because
that's
what
we
sort
of
want
things
quiet,
it
just
gets
messy
if
there's
all
sorts
of
other
changes
happening
to
the
docs.
At
the
same
time,
that's
why
I've
been
working
on
the
community
Pages
too,
because
I
figure
we'll
do
the
main
docs
first
and
then
come
back
and
do
that
so
the
community,
all
these
Community
things
can
our
community
the
contributing
pieces.
Sorry
it's
early
for
me!
C
B
A
B
A
A
A
Not
really
beside
documentation
I
would
like
to
rethink
a
bit
our
documentation
website
after
the
name
change,
so
I
will
say
more
than
a
month
from
now,
because
we
are
working
towards
releasing
each
part
of
the
toolkit
independently.
So
you
can
really
pick
and
choose
your
tool
for
your
own
use
case.
Yeah,
therefore,
having
this
versioning
doesn't
make
much
sense,
since
each
part
of
the
capital
cycle
toolkit
has
a
different
version
because
can
evolve
dependently,
we
don't
have
a
unique
version
and
it
doesn't
make
sense
anymore
to
have
a
versioned
documentation.
A
So
just
throwing
out
the
idea
that
in
a
month
from
now,
I
would
like
to
focus
a
bit
the
effort
in
restructuring
our
documentation,
because
I
also
was
talking
with
Stacy.
Certain
pieces
do
not
evolve
with
the
software
they're.
Always
there
we
don't
need
to
version
them,
collect
the
block
if
we
want
to
have
a
blog
post
in
our
website
with
a
Neato
version
that
but
other
pieces
instead
require
some
versioning
like
specific
piece
of
content
for
the
metric
operator,
for
example,.
B
Right,
there's
several
other
and
there's
I've
got
that
implementing
section
is
just
sort
of
a
catch-all
that
I
know
needed
to
be
reorganized
and
I.
Think
we'll
organize
that
we'll
have
a
guide
for
metrics
and
a
guide
for
observability
and
back
to
by
the
way
with
this,
though,
back
to
the
top
page
that
upper
left
piece
that
says
Captain
life
cycle
toolkit
that
needs
to
change
on
Wednesday
too
right,
I.
B
A
A
A
Because
now
we
are
working
towards
release
each
component
independently,
the
search
manager
will
be
his
own
artifact.
The
different
Runners
to
execute
task
in
Captain
would
be
a
different
artifact
one
fortino
one
for
python.
Then
the
lifecycle
operator
will
be
the
another
artifact.
The
metric
operator
will
be
the
last
artifact,
so
you
can
pick
a
choose
based
on
your
use
case,
but
you
will
want
to
install,
and
then
there
was
a
nice
results
out
of
the
G-Shock
project
where,
where
is
it?
A
A
So
we
can
aggregate
directly
here,
not
just
by
average
right.
It
was
possible
in
the
past
but
mean
Max
median
average
percentiles
would
be
out
of
the
box
supported
and
we
are
working
hard.
I
see
enough
fighting
in
the
last
days
with
finishing
the
controller
for
the
analysis
CRT
to
support
the
future
parity
with
the
old
Captain.
We
want
in
terms
of
quality
gate,
so
the
current
setup
only
allows
less
or
greater
than
a
scalar
value
with
an
analysis
crd.
Instead,
it's
possible
to
run
more
complex
quality.
D
Update
from
you
and
yeah
in
the
upcoming
days,
I
will
definitely
try
to
like
contribute
in
Captain
and
if
you
have
any
suggestion
like
from
a
beginner
perspective
from
where
I
should
start
now,
because
I
had
a
lot
of
Gap
in
between,
because
I
was
busy
with
contributing
to
Z
sock
into
another
project.
But
now
that
I
am
done
with
that,
I'll
be
contributing
to
Captain
again
not
contribute
Captain
regularly.
A
E
A
C
I
would
also
like
to
bring
up
the
fact
that
we're
hosting
our
first
new
contributor
meeting
on
September
11th,
so
that
might
also
be
a
really
great
place
to
come
and
just
once
you've
sort
of
started
digging
in
and
you
find
some
is
some,
maybe
some
blockers
or
things
like
that,
where
it's
a
little
hard
to
understand
how
to
do
things,
bring
them
to
that
meeting
and
if
there's
like
a
topic
or
you
want
to
you
know,
have
us
explain
anything
in
more
detail.
We
can
do
that
there
as
well.