►
From YouTube: Keptn Community Meeting - Oct 12, 2022 - Part I
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,
hello,
hello,
welcome
to
the
captain
community
meeting
so
today
is
October
12th
and
we
have
actually
quite
a
long
agenda
on
the
list
today.
So
thanks
to
everyone
who
joined.
A
On
king,
unless
there
are
some
other
topics,
I
just
want
to
go
through
that
again
and
let's
see
whether
we
reach
then
today,
but
I
hope
so
so.
First
of
all,
quick
update
so
for
America's
meetings,
so
Thursday
4
pm
UTC
for
now
I
will
be
opposing
them
because
there
is
not
that
much
participation.
A
This
time
is
not
very
convenient
to
me
and
unless
there
is
a
demand
to
have
this
meeting,
there
will
be
well
I
removed
them
from
calendar
on
baby
I
will
remove
them
from
Captain
community
calendar.
If
you
want
this
meeting
to
happen
just
shop,
so
developer
meetings
remain
in
place,
but
not
America's.
Coming
into
meeting
for
now.
A
Okay,
now
the
next
item,
which
is
yeah
quite
quick
so
for
Capital
Community,
we
have
a
halogen
the
published
so
again,
so
what
we
discussed
in
the
community
meeting
class
time
in
addition
to
the
community,
we
will
have
a
kind
of
public
Workshop
later,
maybe
in
the
beginning
of
November,
but
most
likely
in
the
beginning
in
November
to
just
discuss
future
of
Captain
to
brainstorm
for
life
cycle
controller
and
other
bits
so
coming
in
today
is
in-person
event.
There
will
be
no
broadcast.
A
There
is
no
budget
for
that
this
year.
So
basically,
we
will
probably
ask
participants
to
do
a
re-recording,
but
for
now
it's
fully
on
site
and
there
is
a
bunch
of
topics.
So
thanks
to
everyone
who
is
presenting
and
yeah,
so
some
important
topics
for
this
meeting
so
yeah
and
the
breadth
and
Anna
will
be
speaking
about
the
use
cases
for
Captain,
then
I'll
make
will
talk
about
the
documentation
and
where
it's
going
and
then
the
focus
would
be
on
what's
next
for
Captain.
A
So
of
course,
Captain
life
cycle
controller
is
on
the
list.
Also
some
other
developments
and
discussions
we
have.
So
if
you
want
to
share
your
vision
for
where
Captain
should
be
gone,
that
are
basically
two
big
opportunities.
So
first
just
drop
every
thing
in
the
chat,
so
I
will
ask
Alloys
to
include
command
and
maybe
incorporate
feedback
from
others
how
it
should
go
and
another
opportunities.
A
We
have
maintenance
track
talk,
so
we
have
four
presenters,
Thomas,
Brett,
Andy
and
Anna
and
yeah
again
it
will
be
mostly
focused
on
Captain
Evolution
and
where
it
should
go.
So
again,
it's
another
opportunity.
If
you
want
to
share
your
feedback,
your
vision,
you
can
just
do
that.
A
Okay,
so
one
quick
item
for
those
who
go
to
the
event,
please
address
VP
here,
because
we
need
to
under
understand
how
many
people
would
be
joining
the
event
this
year.
There
are
so
many
events
happening
comparable,
so
I
literally
have
no
idea
how
many
people
we
could
get
10
or
70
well
70s
the
limit
for
the
room,
but
yeah
it
would
be
nice
and
also
spoiler
alert.
There
is
Cube
cruise.
This
is
basically
a
joint
sponsored
event
open
for
those
who
participate
in
the
cloud
native
Community.
A
Donatress
is
one
of
the
sponsors
and
yeah.
Basically,
all
were
Captain.
Project
numbers
are
also
invited
to
participate,
so
just
make
sure
to
register,
because
before
before
it
runs
out
of
tickets,
and
if
you
go
there
make
sure
to
put
a
captain
flag
somewhere,
I'm,
pretty
sure
that
others,
like
gitlab,
will
enjoy
that
okay
yeah.
A
So
another
quick
update
is
that
yeah
in
Captain
life
cycle
controller
there.
So
basically
what
Suresh
was
asking
at
the
previous
meeting.
So
there
is
a
bunch
of
work
happening
to
make
the
project
available
for
the
evolution,
and
there
is
a
bunch
of
updates
I
just
joining
and
Thomas
could
speak
about
it.
A
But
one
of
key
highlights
that
now
there
are
tutorials
Etc
being
launched,
so
there
was
already
a
release
for
0.1
with
basic
functionality
and
0.2
is
focused
on
observability
and
traceability,
basically
on
showing
what
happens
inside
the
system
and
the
results
a
tutorial
for
that
pending.
So
if
you
want
to
try
it
out,
it's
a
good
opportunity,
so
Thomas
Giovanni.
Would
you
like
to
add
something.
B
A
B
Make
it
also
easier
to
the
wall
installation
process?
Maybe
because
you
discovered
that
it's
a
bit
cumbersome,
let
us
know
so
we
can
really
make
it
better
for
you
to
install
use
and
contribute
afterwards
to
the
project
back
and
one
spoiler.
We
will
do
another
release
as
soon
as
all
the
small
pieces
and
pieces
for
the
observability
are
put
in
place,
and
this
should
occur
around
this
week
so
expect
0.2
either
end
of
the
day.
If
everything
works,
fine
or
worst
case,
Friday.
C
Yes,
so,
and
if
some
of
you
want
to
contribute
and
find
out
that
it
might
be
a
bit
cumbersome
to
set
up
a
development
environment
and
so
on,
which
should
hopefully
not
be
the
case,
then
please
also
reach
out
to
us
we're
trying
to
make
your
experiences
easy
as
possible,
and
if
you
need
help
setting
this
up,
just
feel
free
to
reach
out
to
some
to
one
of
us
on
the
captain
select
Channel,
and
we
will
try
to
find
out
what
what's
the
problem
and
how
we
could
make
this
better.
A
Okay,
yeah,
so
no
it's
totally
relevant.
So
for
that
yeah
there
is
a
life
cycle
controller.
There
is
also
my
GitHub
discussions
being
used
and
basically,
as
I
said
at
the
previous
meeting,
I
will
be
spending
some
time
improving
documentation
and
actually
putting
some
beats.
We
have
a
lot
of
combat
and
slide
decks
and
I
would
like
to
initialize
the
documentation
structure.
A
So
it's
ready
for
feedback
thanks
to
Mac
and
Thomas
for
reviewing
and
yeah
I
would
appreciate
another
round
of
reviews
before
I
start
submitting
pull
requests
and
basically
this
is
an
expanded
version
and
you
should
be
able
to
comment
here
if
you
have
some
ideas,
so
I
need
to
some
to
do
some
updates
based
on
conversation
with
Thomas,
so,
for
example,
leaving
out
architecture,
maybe
to
a
separate
folder.
For
now.
A
Mm-Hmm
and
maybe
one
question
to
contributors,
so
do
you
want
to
use
a
weekend
for
now
or
just
a
documentation.
A
Because
iviki
is
enabled
for
this
service.
There
is
also
some
items
like
release
checklist
here,
so
I
wonder
whether
you
want
to
use
Wiki
or
whether
it
should
be
just
put
into
the
documentation,
and
then
you
should
disable
weekend.
C
We
should
have
it
in
the
weekend
because
yeah,
you
could
see,
please
simply
add
some
things
without
creating
a
pull
request
and
so
on,
but
that's
only
my
opinion
so.
A
So
one
thing
I
can
do,
I
can
take
it,
put
it
to
the
developer
guide
and
maybe
I
could
create
an
initial
template
out
of
that.
So,
for
example,
for
new
release,
we
create
an
issue.
It
would
include
this
template
and
then
we
can
also
leverage
a
new
feature.
We
enabled
for
sub
tasks
so
that
you
can
easily
create
subtasks
from
the
stem
that
shouldn't
be
needed
or
just
click
a
checkbox.
Would
it
work
for.
C
You
but
I
think
it
would
make
sense
as
a
as
an
issue
template,
for
instance,
yeah,
because
in
this
way
we
could
also
change
it
very
easily
and
could
could
Mark
the
things
we
have
there
before
releasing.
A
So
yeah,
maybe
I,
will
do
the
same
for
Captain,
because
today
we
also
have
weak
pages
and
maybe
for
the
team.
It
would
be
convenient,
especially
when
we
talk
about
LCS,
which
has
more
steps,
for
example,
for
services
also
to
have
it
as
issue
templates.