►
From YouTube: Keptn Community & Developer Meeting - Apr 26, 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
Okay,
welcome
everybody
to
the
next
iteration
of
the
captain
community
meeting
and
today
is
April
26th
and
I'm.
Gonna
start
sharing
my
screen
here
with
the
Community
document.
Hopefully
everybody
can
see
that
please
put.
A
A
Cool
and
then,
let's
kick
it
off
right
away.
First
things:
first,
we're
gonna
have
a
new
Zoom
link
starting
from
next
week,
so
that
we
don't
always
have
to
start
this
meeting
and
stop
it
afterwards.
A
So
you
don't
need
the
Captain
Zoom
account
every
time
and
the
link
is
here
in
the
dock,
but
it
will
also
be
updated
in
all
the
different
places
so
on
the
website
in
the
calendar
everywhere,
and
also
on
the
cncf
Community
page
as
well.
So
you'll
find
the
link
the
new
one
everywhere,
if
you
have
bookmarks
take
care
to
update
them.
Of
course,
what
next
updates
on
the
next
releases?
A
Captain
1.4.0
is
going
to
be
released
soon.
Hopefully,
next
week
it's
gonna
have
some
some
minor
updates
to
yeah.
What
was
it
security
security
dependency
updates
mostly,
so
we
wanted
to
get
those
out
quickly,
just
to
be
sure,
and
then
also
lifecycle.
Toolkit
release
is
in
preparation.
A
It's
probably
going
to
be
0.7.1
instead
of
0.8,
since
we
don't
really
have
any
breaking
changes.
Yeah,
there's
only
a
small
part
missing.
That
flow
is
currently
working
on
I,
think
or
almost
done
already
so
yeah
we're
gonna
have
a
new
cool
feature.
It's
gonna
be
automatic,
app
Discovery,
where
you
don't
need
to
necessarily
Define
your
cat
and
apps
beforehand
yourself,
but
rather
we're
gonna
have
kind
of
an
auto
Discovery
feature
so
that
it's
easier
to
onboard
your
applications.
A
Okay,
then
I'm
going
to
continue.
We
had
a
security
issue
reported
to
us
in
very
early
versions
of
Captain,
basically
version
0.1.0
up
until
zero,
eight
two
after
Captain
LTS
version,
not
the
captain
life
cycle
toolkit
you
can
find
all
about
it
in
the
GitHub
security
advisory
that
we
already
published
about
this
yeah.
As
you
can
see
here,
those
Docker
images
are
affected
by
that
and
in
the
in
the
versions
that
we
put
in
here.
It's
super
old
versions.
Those
are
like
almost
like
over
two
years
old.
A
Please,
if
you
still
use
those
please
please,
please
update
yeah.
You
can
find
all
about
it
here.
We
have
a
tldr
and
a
nice
summary.
It's
not
such
a
big
deal,
because
it's
only
happening
on
on
build
time
and
not
actually
on
execution
time
or
runtime.
A
So
you
should
mostly
be
fine,
but
still
we
wanted
to
give
everything
every
Everybody
a
heads
up
on
that,
and
we
also
mitigated
it
already
by
deleting
the
images
that
were
affected
and
also
removing
tags
and
release
branches
for
those
affected
releases,
so
that
people
don't
accidentally
accidentally
come
in
and
rebuild
the
docker
images,
for
example,
because
then
you
would
actually
be
whatever
so
yeah.
This
should
mostly
be
mitigated
already.
A
B
Okay,
we've
got
some,
hopefully
some
big
changes
coming
with
this
next
release,
where
we're
starting
to
make
progress,
the
big
one
is
going
to
be
first
draft
of
reference
Pages
for
the
yaml
files
for
crds
and
some
other
accompanying
stuff.
That
goes
with
that
some
of
the
new
structuring
so
we're
not
there
we're
moving
along.
B
Are
we
let's
see?
Simon's,
not
reporting
Simon's
made
a
lot
of
improvements
to
the
captain.sh
landing
page
so
little
by
little
we're
making
progress
I'll
hand
it
back.
Oh
there's
Simon.
C
So
I'm,
my
part,
yeah
I,
have
just
two
topics.
Actually
the
one
is
the
new
klt
landing
page
I'll
link
the
pull
request
and
the
preview
here.
So
it
looks
now
a
little
bit
nicer
and
more
usable
and
not
like
and
abundant
documentation,
landing
page
with
a
lot
of
features
along
with
a
lot
of
new
layout
thingies.
So
if
you
have
any
things
you
want
to
add-
or
things
like
that,
now
is
the
time
for
the
pull
request.
We
want
to
get
this
released
with
0.7.1.
C
The
second
part
is
where
I
just
was
bored
last
week
is
the
doxian
TV1.
So
there
is
another
deploy
preview
where
it
was
a
little
bit
bored
last
week
and
had
a
little
bit
a
few
hours
left
and
I
migrated
the
captain
webpage
actually
to
to
doxy.
So
this
is
actually
the
same
content
just
with
doxy,
with
all
the
different
kind
of
releases.
On
top
the
question
is:
I
was
not
aware
how
fast
we
are
changing.
C
It's
not
really
beautiful,
but
in
the
end
it's
still
a
little
bit
better
than
the
old
page
they're,
also
redirecting
there
for
the
versions
and
things
like
that.
So
the
question
is:
if
we
want
to
proceed
with
that
or
if
I
should
just
clear
this
clear
this
Branch
actually
that's
well,
because
it
would
be
much
ready
for
the
next
releases.
So,
oh.
A
C
C
I
after
they
kept
my
offers,
I
removed
the
the
two
parts.
The
two
sections
after
Captain
offers
on
the
old
page
are
not
migrated.
So
because
that's
the
one
where
there
is
heavy
custom
JavaScript
involved
here,
this
one
is
there,
but.
A
A
C
A
Yeah,
okay,
but
great
stuff,
so
far,
awesome
kind
of
similar
feedback
to
the
other
landing
page.
The
buttons
are
not
really
consistent.
A
Cool
awesome,
stuff,
I
already
approved
the
klt
landing
page
broadcast
I.
Think
if
somebody
else
wants
to
review
this
as
well,
it
would
be
great,
and
we
kind
of
got
this
over
the
line.
B
Do
we
have
new
people
here
today,
I
see
an
Omer
whom
I
don't
recognize
and
hi
ayush.
B
D
Can
you
hear
me
yes,
okay,
yeah,
hey
yeah,
just
first
time,
turning
to
Captain
Madam,
just
to
new
redo,
Captain,
just
excited
about
the
concept
and
just
saying
what's
happening
there,
Omar
from
New
Zealand.
D
B
A
Then
have
a
great
day:
everybody
see
you
again
next
week
next
week
we
have
the
other
meeting
start
again.
So
the
which
one
is
that
the
Apec
Friday
one
at
what
is
it
10
a.m.
Central,
European,
Time,
so
yeah
see
you
then
hopefully
great.