►
From YouTube: Keptn Community & Developer Meeting - May 3, 2023
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
Sign up to our newsletter: https://bit.ly/KeptnNews
A
Earth
welcome
everyone
to
the
next
iteration
of
the
committee
meeting,
today's
May,
the
3rd
closer
Star
Wars
talk,
but
tomorrow
we
have
some
news
here
as
a
friendly
reminder.
A
If
you're
here
you
manage
to
find
the
correct
link,
we
changed
the
zoom
link
instead
of
using
the
private
Zoom
room
of
this
account,
we
are
using
a
public
meeting,
so
you
won't
have
this
waiting
for
the
host
to
approve
your
entrance
and
we
updated
the
website
to
the
community
pages
and
also
thanks
Anna
for
updating
the
calendar
in
the
main
community
group
of
Captain.
So
now
everything
should
be
pointing
towards
this
new
link
and
then
some
news
about
the
status
of
Captain
B1
and
the
klt.
A
Accepting
the
1.4
is
kind
of
cooked
everything
is
there,
but
we
are
prioritizing
klt
and
this
we
will
most
likely
come
today
right
after
this
committee
meeting
I
just
need
to
test
one
last
thing:
the
helm,
charts
to
make
sure
that
everything
works.
Fine.
Otherwise,
thanks
a
lot
for
everyone
that
contribute
to
the
new
version.
We
have
a
very
cool
new
feature,
called
automation,
automatic
discovery
of
your
captain
application.
A
A
The
next
one
will
be
on
May
the
10th,
and
here
you
can
ask
the
technical
committee
everything
that
you
want
to
know
about
the
technical
direction
of
Captain
or,
if
you
have
any
question
about
a
specific
captain,
captain
captain
enhancement
proposal
or
you
want
to
include
a
new
integration,
just
join
this
meeting.
We
can
discuss
it
or
also,
if
you
have
any
issue,
feel
free
to
talk
with
us
about
anything.
A
Okie
dokie,
then
we
have
items
for
the
documentation
here.
One
topic
about
me
later
about
the
documentation.
So
thanks
a
lot
Mike
for
going
over
this
revamp
of
the
documentation,
but
I
have
some
issues.
So
let
me
first
of
all
open
what
is
it?
I
lost
it
teaser
to
go
from
here.
A
Because
because
if
you
look
at
the
releases,
we
also
version
the
documentation.
So
if
you
look
at
the
documentation,
0.7-
and
this
was
duplicated
and
not
available
anymore-
you
won't
see
it
and
the
question
is:
do
you
want
to
have
an
historical
versioning
of
the
things
in
the
documentation
or
not?
Furthermore,
do
you
prefer
having
a
high
level
view
about
what
concept
the
klt
provides
you
with,
or
would
you
like
to
have
a
more
fine-grained
details
about
every
field
is
used
for
like
DC,
more
human,
readable
format
and
also
the
difference
between
the
different
versions?
B
B
More
piece
of
it,
if
you
go
into
implementing
Captain
applications
right
now,
there's
titling
issues
but
yeah
integrate.
This
is
a
lot
of
material
that
was
on
the
app
Concepts
page,
so
the
the
the
mic
on
my
concept
open
for
discussion,
but
is
that
the
implementing
this
becomes
more
sort
of
guides.
Things
of
how
you
put
stuff
put
everything
together,
and
then
you
have
the
reference
page
that
has
every
nasty
little
detail
about
each
field
that
you
have
to
fill
out
in
the
crd.
B
So
it
is
this.
This
material
is
not
going
away,
we'll
be
adding
to
it.
I
need
to
talk
to
flow,
but
something
about
the
apps.
The
automatic
app
Discovery
Etc.
A
Yeah,
my
major
question
is:
does
the
community
is
happy
with
something
like
this
one,
which
is
generated
and
okay
here?
We
need
to
provide
better
documentation
for
sure
that
is
automatically
generated
from
the
code
and
the
versions
are
available
here
or
do
they
prefer
something
like
where?
Is
it
yeah
like
this
one,
more
human
friendly
with
the
difference
between
the
versions?
B
C
To
be
honest,
when
I'm
using
happen,
the
other
thing
is
for
the
crds
I
think
it's
easier
to
maintain
it
auto-generated,
because
that's
a
lot
of
things
but
I
also
like
the
examples
in
the
yaml
references,
but
those
should
be,
maybe
then
listed
within
the
different
concepts
right
so
having
this
Concepts
and
the
with
the
examples
and
the
actual
crd
reference
order
generated
would
be
my
take
on
it.
B
The
reason
for
the
difference
is
by
the
way
for
differences
between
versions
is
like
I
pray,
I
mean
I,
know
if
I've,
if
I've
been
using
klts
I
mean
right
now,
it's
all
new,
but
the
time
will
settle
down.
I've
been
doing
the
evaluation
provider
and
I
upgrade
to
a
new
release
and
evaluation
provider
is
gone.
I
can't
find
it
there's
nothing
that
I
guess
I
could
go
back
to
the
release,
notes,
dig
back
and
find
you
know.
In
other
words,
it's
changes.
B
It's
because
in
my
mind,
I
thought
I
know
how
to
use
this
I.
You
know
or
to
tell
me
the
as
it
happens
in
zero
seven
one.
The
evaluation
definition
is
going
to
looks
like
the
metrics
definition
is
going
to
look
slightly
different
because
of
this
and
it
just
I
I,
don't
want
to
have
to
sit
here
and
look
at
two
different
sets
of
almost
identical
documentation
and
do
sort
of
a
you
know.
A
manual
grab
down
it
to
find
where
there's
a
difference,
but.
B
D
Typical
scenario
we
had
with
Captain
LTS
is
that
people
were
upgrading
from
7
to
15
16.,
so
still
having
the
difference
in
between
each
release
doesn't
really
give
me
anything.
What
be
good
is
like.
We
had
there
a
single
landing
page
where
I
have
all
of
the
instruction
of
what
is
to
be
done
to
upgrade
from
one
version
to
the
other
I.
C
B
What
if
you
have
a
large
group
of
people
working
with
this
and
one
person
goes
in
and
upgrades
and
then
somebody
else
comes
along
and
they're
expected
to
do
something?
And
it's
like
well
where's
this
field
that
I
knew
about
or
why
does
this
change
either.
A
C
B
They're,
you
know
it's.
It's
too
different.
I've
I've
been
through
this
there's.
There
are
arguments
on
both
sides.
Now,
though,
the
one
that
bothers
me
is,
we
don't
have
Auto
generate
the
ability
to
Auto
generate
documentation
that
what,
as
a
user
I,
see
the
ammo
file,
that's
what
I
have
to
fill
in.
That's
what
I
need
to
know
how
to
fill
in.
B
It
seems
to
me
rather
difficult
to
get
from
what
we're
Auto,
generating
to
to
what
the
ammo
file
looks
like
that.
It's
not
for
the
faint
of
heart.
B
Right-
and
that
was
I
mean,
but
this
is
what
we
cannot
generate.
You
know
if
we
could
Auto
generate
how
you
fill
out
the
yaml
files.
That
would
be.
You
know,
embed
that
there
are
apparently
severe
limits
as
to
how
much
formatting
we
can
do
with
anything.
We
embed
in
the
code.
D
A
B
And
we
need
the
definition
of
the
fields,
also
like
the
human
readable.
What
we
put
there
I
mean
that
that's
going
to
have
to
be
authored
now
it
certainly
could
be
theoretically
authored
within
the
code
and
generate
something
out,
but.
E
A
B
A
E
E
E
B
B
The
kind
of
the
concepts
doesn't
put
them
together,
because
it's
still
it's
all
talking
about
an
app
or
a
metric
that
my
vision
of
what
is
you
know.
Ref
is
reference
and
guide,
separated
it's
sort
of
standard,
but
so
like,
for
instance,
under
implementing
your
you
know,
we've
got
the
installation,
that's
and
then
implementing
you.
Have
these
other
pieces
and.
A
A
In
to
don't
block
the
world
meeting,
since
we
have
also
some
other
topics
to
discuss,
maybe
we
suggest
Mac
to
sync
with
Andy
on
the
specific
topic
to
see,
because
he
has
a
lot
of
knowledge
about
end
user.
How
do
they
read
the
documentation,
what
they
look
for
when
they
check
for
documentation?
What
are
the
things
that
are
missing
in
the.
B
F
No,
it's
nothing
really
that
important,
just
oh,
my
God
as
soon
he's
messing
around
perfect.
So,
first
of
all
the
new
landing
page,
we
already
showed
it
in
the
last
in
the
last
in
the
community
meeting
for
the
other
region,
just
in
the
last
community
meeting,
it
was
just
a
preview
pull
request
and
a
preview.
F
Now
we
already
have
it
merged
and
we
have
a
fine
and
nice
looking
landing
page
for
the
for
the
yeah
for
captain
klt
or
actually,
if
you
have
any
kind
of
suggestions,
please
let
us
know
we
can
always
adapt
improve,
but
we
think
it's
a
great
start
and
it
looks
way
better
than
the
old
one.
With
a
little
bit
more
information,
we
also
can
increase,
improve
the
information.
Just
let
us
know
what
you
think
and
we
will.
Hopefully
we
have
time.
F
That's
part
one
and
the
part
two
is
I
also
a
long
time
ago.
I
started
this
talk,
toxic
exploration
and
I.
Actually
there
is
a
really
big
pull
request.
Do
not
look
at
the
files,
look
at
the
preview
yeah
what
what
I
actually
did
when
you
take
a
look
at
like
at
the
documentation?
Pages
actually
I
prepared
everything
to
be
using
doxy
so
up
on
the
top,
so
it's
not
well
styled
currently
and
there
needs
to
be
style
adaptions,
but
those
are
just
minor.
F
This
is
just
a
really
few
things
to
do,
but
when
you
go
to
the
through
the
to
the
releases
actually
on
the
on
the
top
right,
this
is
actually
using
the
default.
Epoxy
I'll
call
it
the
doxy
layout
Etc,
and
it's
also
adapted
for
the
releases.
So
the
the
changes
are
that
big,
because
I
moved
all
the
documentations
into
different
folders,
so
that
we
have
different
releases
with
all
those
kind
of
information
which
can
be
easier
used
for
others.
F
The
question
is
now:
this
pull
request
is
already
this
pool
because
it's
just
still
an
exploration,
but
with
little
effort
we
can
make
this
happen
and
we
can
replace
actually
the
old
documentation
with
the
new
one
to
make
it
easier
to
navigate.
There
are
still
a
few
sections.
For
example,
this
community
tab
will
be
removed
by
the
community
tab
of
our
other,
which
we
have
in
the
klt,
and
things
like
that.
F
B
And
does
this
give
us
some
sort
of
a
search
working?
We
have
a
search
button
in
the
upper
right.
Does
it
actually
work?
I
did
not
check
if
this
is
working.
B
I
mean
I,
like
the
looks
of
this
better,
but
even
if
I
didn't
having
any
sort
of
search
capacity,
I
think
would
be
extremely
worth.
Something.
F
E
F
Tried
to
to
edit
the
copyright
text
at
the
bottom
and
I
committed
it
by
accident.
Sorry,
I,
didn't
put
it
I
didn't,
did
not
try
to
polish
it,
because
it's
more
about
how
it
looks
like
currently
and
if
you
want
to
continue
on
that
path
and
if
we
want
to
finish
it
because
it's
not
much
effort
actually
the
whole
process,
it
was
just
more
like
moving
files
around
and
adapting
the
style
a
little
bit,
but
this
is
usable
and
can
be
achieved
by
anybody
and
also
I
think.
F
But
we
I
also
found
some
nice
things,
which
we
can
also
apply
to
the
klt,
for
example
the
having
that
okay
having
the
version
in
the
not
writing
documentation
on
the
left
side,
but
also
providing
on
the
menu
on
top
the
version
like
we
do
for
release
0.19.
It's
really
helpful,
I
think
because
people
know
in
which
documentation
they
actually
are,
which
we
maybe
need
to
adapt
for
the
klt
documentation
too.
Yes,.
B
A
F
F
B
I
mean
the
we're
not
actually
taking
down
Captain
V1.
It's
out
we're
not
going
to
be
contributing
a
lot,
but
Community
could
it
means
that
we've
got
the
two
sets
of
documentation
using
the
same
set
of
tools,
otherwise.
B
F
A
A
F
Them
so,
for
example,
you
can
do
that,
so
the
the
Old
Link
when
you
go
to
the
to
the
to
the
oil
bar,
the
Old
Link,
would
be
Doc,
slash,
0.10,
point
x
or
something
uh-huh,
and
we
have
a
little
rewrite
which
will
point
to
the
current.
So
this
is
also
included
already,
so
it
will
also
rewrite
to
the
news
that
the
docs
are
in
there
and
it
will
also
redirect
to
the
10.x
stock.
So
it's
it's
covering
all
the
old
links
actually
coming
getting
in
and
pointing
to
the
pages.
F
Yeah
there's
an
already
right,
which
will
also
take
you
to
the
newest
page,
actually
to
the
to
the
new
all
Rewritten
page.
So
all
the
links
out
there
will
still
work,
but
there
is
still
any
way.
Another
discussion
then
going
on
regarding
klt
and
how
we
handle
the
klt
links
when
the
domain
changes
and
how
we
point
the
people
to
the
right.
The
whole
switching
the
web
page,
if
you
want
to
keep
the
links
intact,
is
a
really
different
topic.
F
I
have
there
are
some
suggestions
and
solutions
to
the
problem,
but
this
is
something
we
need
to
discuss
in
a
different
kind
of
matter,
because,
ideally,
we
will
change
some
kind
of
URL,
so
we
will
change
a
little
bit
the
folder
structure,
maybe
of
the
klt
or
adapted
in
a
way
that
we
can
differentiate
if
the
user
wanted
to
go
to
Captain
or
klt.
Actually.
So
no,
but
this
is
a
whole
different
topic
where
we
will
most
likely
generate
a
new
ticket
out
of
it
most
likely.
F
E
A
A
F
There's
also,
we
most
likely
things
we
need
to
do,
and
this
is
this
is
actually
taking
a
lot
of
effort.
If
we
want
to
take
this
effort,
just
some
thought
I
put
in
there
and
I
just
say
them
out
loud
now,
because
we
have
this
new
section,
we
empty
Community
selection.
We
have
the
do.