►
From YouTube: Keptn Community & Developer Meeting - Mar 08, 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
A
I
like
to
start
with
some
news
or
the
first
one
is
we
finally
have
a
curated
roadmap,
so
I
took
the
time
in
the
last
days
to
clean
up
a
bit.
The
roadmap
because
was
not
reflecting
the
reality.
Anymore
was
more
than
a
year
old
and
I
put
here
what
we
plan
to
work
on,
what's
in
the
backlog,
what
we
are
currently
working
on
and
what
we
just
released
and
it's
ready
for
you
to
print
in
preview.
A
For
instance,
I
know
that
used
to
you're
working
towards
the
data
dog
integration,
so
I
will
add
that
label
to
the
ticket
and
it
will
be
a
bring
here
and
filter
correctly.
But
one
cool
thing
is
that
we
don't
have
only
code
contributions
if
you
are
more
towards
the
community
support.
You
can
also
work
on
item
listed
here
or,
if
you're
more
towards
the
documentation
one.
A
A
But
this
is
a
nice
way
to
see
what's
currently
in
development
and
what's
upcoming
for
you
to
know
where
we
should
focus
our
efforts
and
with
that,
I
will
then
jump
into
the
next
status
report
for
the
lifecycle,
toolkit
and
Captain.
If
there
are
no
questions
from
the
community
in
the
chat
to
see
nothing,
if
you
have
any
questions,
please
feel
free
to
unmute
yourself
and
ask.
A
We
recently
did
a
big
change
where
we
split
our
operator
into
two
different
operators,
one
that
handles
only
metrics
and
the
other
one
that
handles
life
cycle,
and
we
also
did
a
renaming
for
that.
So,
if
you
have
something
in
place
minded
in
version
0.7,
you
will
have
the
scheduler
the
certificate
manager,
the
lifecycle
operator
that
handles
the
possibility
in
the
lifecycle,
delivery
of
your
application
and
finally,
The
Matrix
operator
that
has
this
generic
custom
server.
B
B
So,
as
I
already
presented
last
week,
we
put
some
effort
into
our
documentation,
setup
and
the
documentation
setup
is
now
ready
to
be
tested
by
everybody.
So
I
added.
We
have
now
three
different
levels
of
documentation,
so
the
first
one
is
more
likely
the
pull
request
preview.
So
now,
when
you
go
to
your
pull
request,
you
will
get
your
information
regarding
that
there
has
been
a
netlify
bill,
then
you
can
even
take
a
close
look
at
your
pull
request
at
the
changes
within
your
pull
request
and
you
can
click
around
and
take
a
look.
B
B
B
Will
check
through
the
branches,
and
then
there
is
the
life
page,
which
is
now
a
special
kind
of
way
to
to
to
show
the
presentation.
So
this
is
not
a
live
page
and
a
live
page
is
actually
a
version
which
is
which
is
an
orphaned
branch
in
our
kit
repository.
So,
instead
of
having
that
in
a
different
repository,
we
now
have
an
own
brand
within
our
repository
called
page,
which
contains
only
the
documentation
and
also
contains
the
documentation
for
different
versions.
Afterwards.
No,
so
there
will
be
a
folder.
B
A
matter
of
I
need
to
check
something
later
and
this
documentation
and
the
document
and
the
releases
up
here
are
created
based
on
the
branches.
My
my
path
now
I
know
where
Roto
stops.
Folders
are
I'm.
Sorry
I
was
missing
the
top
folders,
but
they
are
in
here
for
each
version.
We
have
here,
then
an
own
documentation,
folder,
which
will
Auto,
which
will
generate
automatically
this
menu
up
here
without
any
kind
of
configuration
Etc
where
the
latest
one
is
tagged
with
latest.
So
you
will
always
find
the
latest
version.
B
You
can
jump
here
also
to
earlier
version
of
the
documentation,
and
if
you
want
to
go
to
the
main
branch
you
have
here
the
development
link-
and
this
will
sorry-
we
have
to
pull
request
open
to
fix
this
link,
a
lifecycle
test.ch.
There
is
the
pull
request
open
to
fix
this
domain,
which
will
link
you
back
to
the
to
the
the
page,
and
we
have
here
the
same
thing,
which
will
then
link
you
to
the
production
page.
Also
within
your
pull
request
review.
B
If
you
want
to
check
something
on
another
Branch,
you
also
have
here.
The
development
will
bring
you
here,
and
you
have
here
the
link
to
Productions,
which
will
bring
you
to
the
main
reference
page
yeah.
As
I
said,
there
are
pull
requests
open
to
fix
this
link
properly
for
the
menu.
That's
actually
it.
There
is
one
part
missing
which
I
was
not
aware
of
was
that
there
is
also
for
on
releasing
we're.
Also
extracting
the
examples
to
an
example
repository.
This
is
something
which
I
will
deliver
today
as
an
own
separate,
GitHub
action.
B
So
it's
not
hidden
within
the
documentation,
build
anymore,
and
that's
actually
it
if
there
are.
No.
If
there
are
questions,
feel
free
to
ask
just
to
let
you
know
about
our
plan,
it
is
we
want
as
a
if
there
are
no
concerns,
no
issues
regarding
that
we
would
set
everything
to
life
within
this
week,
so
that
the
new
documentation
will
be
deployed
from
this
repository
rather
than
the
other
repository
and
Via
Network
file.
A
Not
really
I
think
it's
very
cool
that
we
have
a
setup
in
place.
One
thing:
maybe
it's
more,
a
fine-grained
refinement
can,
after
we
select
something
from
the
release
bar
on
the
top
the
drop
down
bar.
Can
that
name
be
there
yeah.
B
Also
something
I've
thought
about
currently
what
we
would
be-
maybe
maybe
also
adding
some
information
to
the
logo
or
something
so
that
you
have
when
you
are
in
a
PR
review
that
you're
dedicated.
Now
where
you
are
that's
something
I
also
thought
about,
and
may
I
use
the
time
for
an
additional
question
suggestion
feedback
I
put
into
the
channel
and
just
currently
want
to
ask
if
this
is
a
good
idea,
if
I
should
create
an
issue
for
that
totally,
okay
may
I
share
my
screen
again.
I'm.
A
B
So
I
regarding
we,
we
do
have
this
fancy
Community
repository,
In,
Here
Also,
within
our
project,
where
we
have
the
where
we
store
all
the
information
regarding
adopters
Etc.
This
is
sometimes
a
little
bit
outdated.
It
is.
It
is
also
hard
to
navigate
if
you
are
here,
I
prepared
a
little
POC,
which
is
including
this
repository
as
a
readme
with
minor
readme
adoption
so
as
a
with
minor
adaptions
to
the
markdown
file,
so
adding
just
the
information
I
can
to
to
better
show
you
that
I
put
like
this
markdown
definitions
up
top.
B
So
it's
not
like
really
changing
the
file,
but
it's
putting
informations
like
title
description
link
title
up
here
and
what
this
allows
me
then
is
I
can
include
this
repository
up
here
as
a
as
a
tree
can
add
those
files
here
be
aware
of
some
of
those
smartphone
files
do
not
have
those
changes,
so
they
are
not
aware,
and
then
I
can
take
a
look
at
all
the
at
all
those
files
within
the
web
page
like
what
is
our
community?
How
is
it
structured?
What
is
our
code
of
conduct?
B
The
question
for
me
is:
do
we
want
to
pursue
with
that,
because
we
can
also
use
that
for
if,
if
we
have
more
sub
projects,
I'm
not
sure
if
they
are
coming
or
not
coming,
we
can
use
the
same
approach,
because
it's
just
still
maintained
within
one
repository
and
we
can
add
them
to
multiple
repository.
If
we
would
like
to
that's
what,
if
your
two
pages
but
questions,
do
we
want
to
render
those
markdown
files,
also
within
our
pages
and
if
so,
where
do
I
create
the
issue
for
that.
A
B
Where
do
I
create
the
issue?
Do
I
create
the
issue
in
the
community
repository?
Do
I
create
the
issue
in
the
lifecycle.
Klt
repository
do
I
create
two
one
for
adapting
the
community
repository
and
one
four.
That's
just
more
like
the
organizational
part
to
have
an
overview
and
to
to
track
those
efforts
somehow
somewhat
well.
A
A
A
B
A
Okay,
then
we
have
some
shared
issue
here.
I
see:
oh
gosh,
sorry,
if
I
bought
your
name,
Moritz
and
Simon
issued
and
played.
A
Then,
let's
go
to
the
next
one:
getting
started
with
klt
developers,
perspective
of
klt
it's
architecture
and
how
it
works.
E
Hey
everyone,
it
was
me
this
is
my
first
meeting
and
I
recently
tried
to
get
involved
with
klt
and
I
thought.
I
can
get
some
questions
answered,
I
have.
F
E
E
So
yeah,
like
previously
when
I
was
in
caption
klt,
was
not
started
at
that
time
and
it
had
the
architecture
section,
which
was
pretty
good.
So
I
was
wondering
if
I
could
get
like
an
overview
of
how
klt
works
with
kubernetes,
because
that
architecture
thing
is
missing
currently
in
the
documentation
right.
A
Yes,
I
would
suggest
if
you
have
specific
questions
you
can
ask
them
now.
Otherwise
you
can
ping
us
on
Slack.
If
you
have
any
general
topics,
so
we
can
follow
up.
E
A
Text
here,
just
very
introductory
not
much
for
you
a
great
place
to
start
a
bit
with
this
is.
E
A
This
picture
is
a
bit
outdated.
For
instance,
we
don't
have
two
different
controllers
for
the
CLI
for
SLI
and
SLO.
Everything
is
bundled
together
at
the
moment
in
what
we
call
Captain
evaluation
yeah,
but
maybe
we
can
have
a
follow-up
over
slack
where
I
can
describe
it
more
all.
The
different
things
work
together.
E
C
A
Thank
you,
then
I
think
we
can
go
to
the
next
topic
about
the
data
dog
metric
Provider
from
sudipto.
What
do
you
like
to
discuss
about
this
sudipta.
F
A
Sure
perfect,
so
I
will
try
to
reserve
some
time
today,
or
tomorrow
too
also
have
a
look
actually
send
myself.
So
it's
in
my
notifications
and
I
won't
forget
about
that.
D
E
D
A
There
is
nothing
so
if
I
would
run
this
locally
now,
with
this
set
of
rules
yeah
do
we
need
to
change
any
yaml
file
or
everything
works
out
of
the
box?
No.
D
I
added
out
like
we
can
set
it
to
a
warning
or
error.
So
like
will,
the
warning
label
would
hinder
the
development
or
something.
A
I
would
add
everything
to
warning,
so
we
can
get
a
bit
of
understanding
about
what
are
the
rules
that
we
really
need
and
what
the
rules
that
okay,
we
can
disable,
because
with
customized
we
might
not
have
the
possibility
to
fix
them.