►
From YouTube: Keptn Community & Developer Meeting - May 24, 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
B
C
Oh
hi
Meg:
do
we
do
we
wait
a
second
for
Rashid
I
see
he
has
a
few
items
on
the
agenda
and
I
see
him
online
in
the
meeting
notes.
C
C
There's
been
a
proposal
to
move
users,
interests
towards
klt
and
move
our
support
more
towards
guilty,
and
this
translates
in
a
few
action,
but
Giovanni
is
taking
care
of.
We
discussed
this
already
in
the
refinement
yesterday.
If
you
want
to
recover
that
link
as
well,
but
basically
the
main
landing
page
of
Captain
will
now
redirect
to
klt
to
lifecycle
toolkit
and
the
new
page
for
the
landing
page
of
the
old
Captain
would
be
B1.
Captain.Sh
and
same
goes
for
the
docs.
This
does
not
change
anything
about
the
link
of
the
documentations,
just
the
landing
page.
C
So
if
you
have
saved
somewhere
to
link
for
how
to
version
1.3.0
adding
a
shipyard,
this
still
will
work,
and
there
is
also
another
communication
about
klt.
We
have
mentioned
last
time
that
there
is
a
problem
with
the
scarf
that
their
servers
are
having
issue
redirecting
when
user
download
the
images.
So
we
decided
also
to
remove
the
redirection
of
scarf
from
the
registry
in
klt.
As
well,
not
only
in
Captain
B1
for
now,
this
means
that
if
you
use
Helm
to
install
klt,
you
may
have
some
trouble
of
Crash
back
off
of
downloading
the
images.
C
So
you
may,
you
may
use
the
new
registry
that
we
provided
I
will
probably
paste
here
a
PR
after
I
think
this
has
not
been
merged
yet,
but
soon
enough,
we
will
release
the
new
chart
with
the
proper
images
and
I
think
these
are
the
news
and
then
I
see
that
Rashid
has
a
big
topic
about
up
outdated
documents.
Basically,
do
you
want
to
take
over.
E
Yeah
sure
so
first
I
would
like
to
like
tell
everyone
that
my
cfp
for
kcd
Mumbai,
just
got
accepted
yesterday,
I'll
be
speaking
about
how
we
can
Auto
scale
our
workloads
with
the
help
of
HPA
using
using
our
metric
server
so
about
the
topic.
I
was
just
going
through
the
metrics
operator
and
lifecycle
operator
and
I
saw
that
they
read
me
for
both
The
Operators
is
outdated.
E
E
D
So
I
guess
the
question
for
the
community
is
I
mean
what
should
we
do?
What
should
the
readme's
look
like?
Also
there's
two
questions
there.
One
is
you
know
from
my
standpoint,
which
is
very
biased.
We
have
a
lot
of
material
in
the
readme's
that
maybe
should
be
in
the
documentation
and
not
maintained
in
the
readme's.
Should
they
be
duplicated
I,
don't
know,
maybe
the
documentation
should
just
you
know,
give
a
brief
summary
and
save
for
more
details.
It's
on
the
readme,
but
how
do
we
maintain
these
things?
I
mean
it's.
A
C
C
That
was
fun.
I
was
asking
if
anybody
had
an
opinion
on
this,
like
in
my
experience,
one
of
the
last
readme
I
I,
checked
out.
This
was
directly
pointing
to
documentation,
so
this
can
also
be
that
we
just
put
the
link
for
each
of
the
operators
towards
the
documentation.
C
D
I
have
a
general
I
mean
it's
just
that
when
that
one
is
old,
I,
don't
even
know
what
you
know.
It's
all
a
question
of
how
we
want
to
do
it,
but
that's
I.
You
know
I
know
there
are
newer
videos
than
that.
One
we've
I've
also
I've
got
an
issue
with
video
maintenance
in
the
docks,
because
we
put
a
lot
of
links
to
videos
in
the
docs
and.
F
C
D
Perhaps
to
go
in
and
look
at
it
can.
C
And
about
the
architecture
I
think
we
do
have
already
an
issue
right.
D
Yeah
I
was
just
working
on
the
docs
for
it,
and
so
is.
D
D
Yeah
I
mean
I,
think
there
yeah
there
we
go
and
what
I
should
do
is
actually
just
add
an
issue
to
that
epic
for
architecture
to
as
stuff
gets.
When
we
get
stuff
from
the
out
of
the
readme
into
the
documentation,
we
should
update
the
readme
to
enter
some
remove
the
Redundant
material.
So,
okay.
C
D
D
C
For
the
install
this
is
already
work
in
progress.
We
have
a
lot
of
PR
now
right
right.
C
Can
you
remind
me
what
is
this
last
point?
Nothing
about
enabling
and
how
to
use
is
a
duplicate.
D
I,
don't
know
if
I
wrote
it
I
was
just.
It
was
just
things
that
I
was
putting
in
there
of
other
specifics
of
you
know,
I
think
the
bottom
line
is
probably
all
the
readmies
are
out
of
date
because
they
were
done
once
and
we
haven't
maintained
them.
So
I
thought
in
case
somebody
said:
oh
there,
the
readme's
are
fine.
These
were
other
places.
If
anybody
wanted
to
discuss
that
so.
C
D
D
D
You
know
a
lot
of
people,
it's
easier
to
write,
to
read
me
than
to
write
something
else,
but
so,
if
our
idea
is
and
and
we've
had
people
who
said
you
know
who's
going
to
read
the
documentation,
it's
open
source
and
if
they
want
to
use
this,
it's
just
go
to
the
readme's
and
I.
Think
that's
a
big
question.
If
that
is
not
our
policy,
then
we
know
what
to
do.
It'll
take
a
little
time.
D
Oh
Splendid,
you
could
write
it
into
the
documentation
too.
Yeah
sure
that's
on
the
list.
Actually
Bob
yeah.
How
do
you
pronounce
your
name?
Is
that
babia.
D
That
might
be
you
I
think
you
were
looking
for
some
writing
stuff.
This
could
be
some
interesting
stuff
for
you.
Yeah.
D
Okay,
let's
start
because
it's
I
just
we're
about
to
publish
the
getting
started
guides
and
going
through
those.
That's
I've
just
been
aware
of
there's
a
lot
of
holes
and
there's
some
of
them
are
just
dark
holes,
but
some
of
them
there's
good
material
in
the
readme's,
except
it's
a
little
outdated.
So
so
we'll
talk
about
it.
I
I'll
set
up
an
epic
and
we'll.
We
can
just
start
adding
issues
to
it.
So,
okay
and
we
have
new
people
here-
I,
don't
think
I
know
Jeffrey,
hello,
hello,.
B
D
B
C
F
C
C
C
If
not,
I
would
cut
it
here
thanks
everyone
for
joining,
we
were
so
many
today.
It
would
be
cool
if
you
yeah
reach
out
to
Mac
for
the
documentation,
Docs
PR
and
you
can
reach
out
to
me
or
to
any
of
the
other
guys
in
the
team
for
the
technical
PR.
C
Oh
I
am
Anna
Allianz
like.