►
From YouTube: Keptn Community Meeting - June 22, 2022
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
thanks
a
lot
for
starting
that
yeah
today,
because
of
my.
A
We're
using
another
service
from
the
app
for
the
meeting,
but
thanks
everyone
who
joined
so
agenda
for
today,
and
this
we
want
to
discuss
some
news,
preparation
to
cncf
integration
and
also
google
summer
of
code
projects.
B
Yeah,
I
put
something
on
the
the
the
word
doc
just
around
the
documentation
and
the
tutorials
and
how
they're
arranged
on
the
on
the
site.
B
C
See
that
I
also
had
a
question
about
logging
standards
throughout
all
of
the
sandbox
and-
and
you
know
I
guess-
services.
A
Yeah,
I
don't
think
that
we
have
any
strategies
right
now,
but
it's
definitely
something
we
could
discuss
and
they
put
some
best
practices
in,
because
now
whomever
develops
the
service
they're
responsible
for
their
logging
and
well
just
thanks
to
them.
If
login
is
present,
which
is
not
always
the
keys.
C
A
A
C
There
there
is,
but
it's
sort
of
debatable.
I
think
it's
a
bit
of
a
debate
because
you
have
things
like
loggers
which
is
sort
of
it's
not
maintained
anymore,
but
it's
still
used
by
a
lot
of
open
source
projects
so
and
they
have
zap
like
the
one
that
I
think
uber
uses.
So
I
guess
it's
a
debate
of
of
going
forward
which
one
we
want
to
choose.
A
Yeah,
so
personally,
I
think
that
we
should
use
any
standard
format,
of
course,
and
we
should
include
the
login
libraries
and
examples
right
inside
the
sdk.
So,
for
example,
we
have
golang
template
python
template
and
for
this
template
I
believe
we
should
include
login
by
default.
A
A
D
I
can
open
up
developer
doc
right
now
and
then
we
can
get
it
as
an
empty
one,
and
then
you
can
write
your
stuff
into
it
or
give
me
what
you
want
now
right
now,
yeah
good
time,
let's
get
the
developer
dot
going.
I
like
that.
D
A
And
probably
if
rajiv's
documentation
engine
is
ready,
we
could
start
actually
doing
it
right
for
this
engine.
D
Yep,
what
do
you
want
for
titled
developer,
guide,
developer,
documentation.
D
A
Yeah,
so
basically
how
we
could
organize
it,
so
we
could
create
a
repository
or
whatever,
so
that
we
put
content
there
and
then
rajiv's
tool
collects
it
so
that
it
gets
posted
on
the
website.
But
for
now
it
could
be
just
a
bunch
of
readme
pages
for
us,
maybe
with
some
markup,
and
then
we
just
this
multi-depository
thing.
While
we
go.
D
Okay,
let
me
take
a
look
and
actually
the
couple
of
pages
that
I
think
belong
in
there
I'll
put
in
there,
and
you
can
check
that
out
on
the
pr
tell
me
if
I
chose
something
I
shouldn't
have.
E
A
D
D
Written
up,
that's
in
the
software
repositories,
not
in
the
documentation,
set
right,
yep,
okay
and
then
let's
well,
let's
grab
so
I'm
talking
about.
What's
currently
in
the
documentation
set,
I
will
put
over
there
and
then
let's
create
issues,
for
I
mean
there's
always
there's
the
stuff.
That's
in
the
software
repos
and
some
stuff
people
want
just
to
have
there,
and
but
let's
make
a
list
of
where
we've
got
pieces
in
the
software
repos
that
need
to
turn
into
docs.
D
A
D
A
D
Yeah,
I'm,
unless,
unless
we're
going
to
leave
the
documentation
in
the
software
set
and
just
pull
it
in
that,
I
could
see
but
having
a
separate
tree
for
the
developer
documentation.
My
my
concern
is
when
you
do
that,
you
end
up
with
it
using
different
tools
and
stuff
gets
out
of
sync,
and
it
ends
up
the
developer.
Dock
isn't
as
good
as
the
other
dock.
C
A
Should
so
so
yeah?
Basically
what
I
propose
that
we
start
the
developer
documentation
targeting
the
new
documentation
engine
has
been
developed
by
rajiv
as
a
part
of
gsoc
and
for
that
to
be
target
multi-repository
approach,
so
instead
of
putting
everything
in
captain
github,
io,
etc,
we
built
the
structure
that
the
rajiv
could
consume
and
cook
under
the
augmentation
side,
but
we
develop
it
separately
for
the
moment.
A
C
A
Well,
rajiv
needs
some
sample
repositories
etc
to
play
vs.
So
why
don't?
I
think
that
we
can
just
have
it
as
one
of
the
examples.
D
D
D
Jerry
was
captain
captain
github.io.
Do
you
consider
that
documentation
as
code.
D
A
Yes,
documentation
in
the
repository
command
documentation
as
code
is
when
documentation
is
stored,
aligned
with
production
codebase
so
for,
for
example,
if
you
have
documentation
for
parameter
service,
it's
stored
in
the
parameter
service,
so
humber
does
a
modification
in
the
service.
They
expect
to
write
documentation
and
the
simple
request
and
then
base.
Basically,
it
gets
delivered
to
the
website
as
needed,
but
the
source
code
is
near.
The
production
code.
D
E
D
A
Okay,
so
okay,
then
I
will
create
probably
a
cab
and
dc
and
sorry
for
this
long
detour.
A
A
C
C
A
Yeah,
I
cannot
say
that,
from
my
experience
with
captain
startup,
we
have
close
to
zero
observability,
although
what
the
heck
happens
with
captain
on
startup
and
why
it
takes
so
long.
So
definitely
if
someone
wants
to
work
on
making
captain
observable,
that
is
a
lot
of
things
to
do.
A
A
B
Yeah
yeah
I'm
happy
to
take
that
one.
So
we've
I'll
just
share
my
screen
and
sort
of
talk
it
through.
If
I
can.
A
I'm
just
using
my
laptop
to
use
edit
metering
kernels,
so
I
cannot
share
my
screen
because
it
would
be
completely
useless
anyway.
D
B
Cool
so
thinking
thinking
as
a
kind
of
first
time,
captain
user,
I
hit
the
website.
I've
heard
about
captain,
I
hit
the
website
and
I've
got
two
big
calls
to
action,
quick
start
and
install
captain,
and
then
I
scroll
down
a
little
bit
and
I've
got
start
now
or
read
the
docs
so
they're
the
four
sort
of
places
I
could
go
now,
quick
start
and
install
captain
both
go.
If
you
see
when
I'm
hovering
over,
they
both
go
to
the
quick
start
page.
B
So
they
they
both
go
the
same
same
link,
which
is
a
bit
redundant
for
me,
but
then
so
does
the
start
now.
B
So
that's
the
first
thing:
we've
got
three
buttons
on
the
home
page
that
go
to
the
same
place.
Now
that's
a
small
issue
easily
fixed,
but
the
bigger
one.
Is
I
get
to
this
quick
start
page
and
ignoring
the
specific
text
about
five
minutes,
which
I
don't
think
it
is
five
minutes,
but
I
get
helm
which
is
great,
that
works
that
works
and
it
jumps
me
to
multi-stage
delivery.
So
you
know
I've
installed
and
I
want
to
get
going
and
actually
this
doesn't
work.
B
So
this
is,
this
is
for
an
old,
it
hasn't
been
maintained.
This
is
for
an
older
version
of
of
captain.
There
are
a
couple
of
different
issues,
one
this
doesn't
auth
the
cli.
It's
actually
up
here.
You
need
to
authenticate
the
cli
first,
but
even
then
the
captain
trigger
delivery
and
the
captain
create
project,
don't
respect
it.
Don't
include
the
new
git
upstream
requirement,
so
basically
that
shell
script
is
is
out
of
date
for
the
layer
captains.
B
Now
that
said
so,
so
as
a
new
user,
I
would
come
on
here
and
I
would
want
to.
I
would
be
excited,
I'd
want
to
use
it
and
I'd
get
to
a
certain
point
and
I'd
just
be
blocked.
So
then
I'd.
B
Slack
and
start
asking
questions
there
is
this
page,
though
the
explore
captain
page
which
links
to
the
new
killer,
coda
tutorial,
and
then
it
goes
on
to
install.
So,
basically,
what
I'm
saying
is:
could
we
just
retire?
This
quick
start
page
and
use
this
one
instead,
because
this
seems
to
me
to
be
the
new
quick
start.
C
Oh
he's
just
dropped
out,
but
I'll
tell
you
when
he's
back
in
okay
he's
just
going
off
the
stream
but
yeah
it's
interesting.
You
found
those
buttons.
I
wonder
how
many
other
people
found
that
yeah.
B
Because
for
me,
if
I
was
to
go
from
the
home
page
to
this
page,
I
could
say
right:
the
captain
end-to-end
delivery,
blah
blah
blah.
I
click
there
and
I
get
the
the
killer
code.
You
know
the
browser
version
and
then,
when
I'm
finished
and
I
go,
I
like
captain-
here's
how
I
install
it
and
here's
the
helm
command
again.
B
B
This
docker
run
command.
We
should
probably
get
rid
of
that,
but
yeah
the
the
shell
script
doesn't
doesn't
work.
That's
as
simple
as
that.
So
I
wonder
how
many
people
are
actually
attempting
that
and
saying?
Oh,
what
doesn't
work?
I'm
just
gonna
gonna
move
on.
C
Well,
they
will
like,
even
if
they
it's
such
a
hard
tool
to
to
pick
up
to
get
hit
around
all
those
concepts
like
even
shipyard
and
creating
the
project.
D
And
the
new
killer,
the
killer
coda
tutorial
exercise
is
really
nice.
It's
takes
about
45
minutes
to
get
through,
but
when
you
get
through
it,
you
actually
learned
something
I
mean
the
old
quick
start.
You
really
didn't
learn
anything
and
I
spent
all
my
time
trying
to
get
everything
working
and
with
killer
coda.
You
adam
did
some
beautiful
work
and
you
click
a
button
and
sit
there
and
watch
stuff
scroll
by
for
about
three
minutes
and
you're
all
set
up.
D
D
Yeah
and
and
then
and
he's
even
done
it
so
that
while
you're
waiting
for
that
three
minutes,
he's
got
a
little
something
for
you
to
read.
I
think
that's
where
he
says
you
know
you've
got
you
know
here:
we've
got
stages
and
stages.
Have
sequences
and
you've
got
a
pride.
You
know
he
gives
a
little
bit
of
introduction.
You
start
to
get
the
terminology.
D
When
you
get
through
doing
this,
you
actually
have
learned
a
little
something.
So
I
can't.
B
Take
all
the
credit
by
the
way
a
lot
of
this
was
was
off
silent
yourself.
So
please
don't
okay.
D
B
But
I
think
the
the
overarching
point,
one
all
roads
lead
to
that
quick
start
page,
which
is
broken
effectively
as
of
the
current
version,
and
we
have
now,
we
have
a
better
option.
B
That
is,
that
is
working
that
is
maintainable
and
also
it
does
away
with
all
of
those
installation
issues,
because
there's
a
there's,
a
myriad
different
options
for
kubernetes
distributions,
and
as
you
say
you,
you
spend
a
lot
of
time
figuring
out
which
one
works
with
with
you
know,
most
of
them
most
of
them
should.
But
I'm
a
fan
of
getting
people
started
as
quickly
as
possible
and
a
quick
start
to
me.
The
killer
code
is,
is
just
the
way
forward.
A
A
B
So
killer
coder
and
my
understanding
is
they're
offering
those
resources
there's
there's
sort
of
a
free
tier
they
they've
they've,
provided
us
now
what
questions?
What
what
information
do
we
need
from
the
killer,
coda
team
to
make
that
decision
about?
Yes,
it's
stable
enough.
A
So
I'm
not
too
concerned
about
being
stable
enough
as
long
as
they
remain
in
the
business.
We
are
fine
yeah
and
I
guess,
with
the
recent
down
of
qatar,
they
will
have
enough
customers
and
that
will
from
the
industry.
A
What
I
would
expect
is:
firstly,
ensuring
that
free
tariff
is
enough
for
us,
which
is
probably
not
and
if
so,
securing
budget
so
that
we
can
provide
a
good
experience
for
our
users
yeah,
because
there
are
multiple
examples.
So,
for
example,
you
want
to
host
a
workshop
for
captain
and
then
you
need
30
seats
to
try
out
captain
and
then
can
be
done
or
killer
coder
another
use
case.
We
just
keep
it
on
the
website.
The
users
connect.
A
B
Yeah,
I
guess
it's
a
bit
tough
because
they
don't
offer
statistics
for
the
free
tier,
but
even
so
we
we
don't
have
any
idea
of
how
many
people
were
going
through
the
normal
tutorial
anyway.
So
we
we
can't
go
to
them
and
say
we
usually
get
100
people
a
day
or
whatever
the
figure
we
don't.
We
don't
have
those
figures.
A
Yeah,
so
what
one
of
the
things
we
could
just
talk
to
kill
the
team
directly
say
that
here
we
would
like
to
set
it
up
whether
you
would
be
interested
to
collaborate
with
us
as
a
in
a
pilot
project
and
see
what
would
be
the
conditions.
A
Because
we
could
show
a
good
examples
of
killer
coder
being
used
in
the
cncf,
which
is
a
good
gross
opportunity
for
them,
and
it's
something
that
we
can
negotiate.
It's
something
that
we
can
explore
together.
B
Okay,
meg,
I
think
cell's
got
a
got
a
contact
over
there
or
he
he
was
kind
of
reaching
out
tonight
because
he
he
afsel
got
it
listed
on
the
home
page.
So
great,
that's
cool.
C
B
I
I
I
don't
and
well.
I
think
any
statistics
that
we
could
get
would
be
false
because
well
well
not
false,
but
misleading,
because
because.
A
We
can
announce
it
through
social
media,
actually,
like
killer
code
already
did
but
yeah.
This
is
why
I
suggested
that
we
work
closely
with
a
team
so
that
we
can
emulate
it
in
a
managed
environment,
so
basically
a
pilot
project.
Yes,
we
start
highlighting
killer
coders,
see
whether
we
scale
enough.
A
If
so,
what
is
the
cost
implications?
What
is
the
user
experience
implications
and
then
we
can
gradually
switch
towards
the
only
solution,
but
now
I
just
suggest
at
least
it
is
one
of
the
options.
D
B
Put
it
at
the
top
here
somewhere,
like
after
the
before
helm
or
or
maybe
down
here,
I'd
I'd
like
I'd,
actually
like
to
retire
the
kind
captain
if
we
can
get
killer
koda
working.
The
current
captain
was
a
a
stop
gap
solution
really:
okay,
because
the
the
hello
world
is
is
great,
but
it's
it
doesn't
really
provide
any
real
value.
It
doesn't
show
the
strength
of
captain
to
me
in
its
in
its
full
glory
and
then
yeah
next
steps
you
get
there
and,
as
we've
discussed,
that
doesn't
work
so
anyway.
A
But
I
think
that
we
all
agree
that
we
want
to
have
killer
code,
promote
it
more
and
to
get
adopted.
You
also
need
to
develop
more
tutorials,
because
color,
currently
killer
code
doesn't
show
the
full
value
of
captain.
Neither-
and
this
is
something
we're
going
to
work
on.
A
Oh
well,
I
think
that
we
need
to
have
use
cases
like
progressive
delivery,
remediation,
etc.
A
Captain
novice
argo
cd
using
captain
jenkins,
so
all
these
tutorials,
which
along
forgotten,
because
nobody
has
powers
to
maintain
them.
But
if
we
still
record
again,
we
could
package
it
and
show
it
with
some
practical
examples.
D
I'm
trying
to
figure
out,
I
mean
I
see
at
the
front
to
get
started
in
a
little
tutorial
like
what
we've
got,
but
are
we?
How
is
the
tutorial
superior
to
the
documentation
that
actually
gives
steps?
If
you
want
to
do
this,
you
need
to
do
this,
and
this
and
this
and
this
or
we
could
even
have
a
video
demonstration.
D
We
could
do
things
that
are
not
as
resource
intensive.
Just
to
maintain
I
mean,
if
we're
going
to
have.
Let's
say
we
have
10
tutorials
out
there
and
they
each
have
to
be
retested
and
probably
modified
for
each
release
and
we
have
a
new
release
once
a
month
I
mean
this
is
we
need
a
full-time
person
who
just
does
nothing
but
tutorials
at
that
point,.
A
So
you
have
to
separate
tutorials
and
demos,
because
if
you
want
to
have
showed
them
to
showcase
some
captain
features
for
your
information,
then
we
don't
even
have
to
maintain
the
latest
kept
conversion
there
and
at
least
not
every
month.
We
don't.
We
update
it
as
we
see
feasible,
and
this
is
actually
one
of
the
purposes
of
tutorials
to
just
show
the
value
of
capital
users
and
there
for
demos.
A
I
wouldn't
care
care
too
much
and
the
rest
is
actually
tutorials
guys,
which
are
version
specific,
and
for
that,
if
you
want
to
have
them,
you
will
have
to
maintain
them.
D
A
A
Recommendation
is
a
place
where
you
can
see
tutorials.
I
don't
think
that
so
for
me,
I
know
that
there
is
difference
between
tutorial
and
guide,
but
personally
I
do
not
care
as
a
user.
As
long
as
there
is
some
information
when
I
need
it,
I'm
fine,
whatever
it's
called.
D
D
So
now
what
I
would
like
is
some
I
would
like
some
more
advanced
tutorials
like.
I
would
like
a
good
long
like
45
minute
of
creating
good
slos.
I
think
that
would
be
a
powerful
tutorial.
D
Well,
that's
that's
an
issue
for
all
of
them
yeah
and
there's
a
lot
that
can
be
done
with
like
detailed
technical
videos
or
that
go
with
the
doc.
The
docs
say
you
do
this
this
this
and
this
and
throw
up
a
video.
A
A
So
the
next
captain
incubation
right,
yep,
so
quick
update.
I
submitted
all
the
information
to
the
cncf
so
now,
since
if
I
need
to
prepare
the
blog
posts,
announcements
and
after
that,
they
will
come
back
to
us
so
that
we
set
a
bit
for
announcements
when
it
happens.
I
don't
know
I'm
not
sure
how
long
it
takes
these
things
you
have
to
prepare,
but
yeah
the
ball
is
on
their
side.
A
Once
we
have
this
date
with
this
ncf,
we
will
also
communicate
with
all
other
stakeholders
so
whomever
we
want
to
participate
in
the
announcements
right,
like
blog
post,
etc.
Please
feel
free
to
prepare
already,
but
the
need
for
publishing
is
unknown
at
the
same.
A
A
A
A
There
will
be
also
a
huge
checklist
of
things
we
need
to
do
as
a
project,
something
crazy.
Some
things
are
quite
hard
like
transferring
the
project
infrastructure
to
the
cncf,
so
it
will
also
take
a
significant
amount
of
my
time
next
year,
starting
from
september,
I
guess,
but
it's
something
we
will
need
to
do
if
we
ever
wanted
to
reshare
the
graduating
status,
and
while
I
rather
prefer
to
focus
on
on
the
community
on
features
than
these
formalities,
so
I
will
be
postponing
them
as
much
as.
B
A
So,
first
of
all,
we
are
considered
as
a
cncf
member
project,
because
sandbox
projects
are
not
considered
since
yet
members
what
it
means
in
practice,
we
get
access
to
all
linux
foundation
infrastructure
like
lfx
tools,
including
colorfx
security.
We
get
access
to
their
computing
grids
if
needed.
The
issue
trackers
if
needed,
et
cetera
et
cetera.
Most
of
that
be
done
here
hear.
A
A
A
So
just
quick
update
here
we
started
coding
period,
so
all
four
projects
started
coding
here
or
there.
So
I
checked
with
students
with
mentors.
Nobody
said
there
is
anything
missing
for
the
coding
period,
but
if
you
see
something
like
that
in
your
projects,
please
highlight
it
so
bread
adam
make
your
own
mentors
and
how
other
projects
are
going
for.
You.
D
There
you
hear
me
better
if
I
unmute
yeah
the
the
documentation
engine
seems
to
be
starting.
I
think
we
may
have
something
that
we
can
start
looking
at
by
the
time
of
the
next
community
meeting.
D
B
Yeah
good
we've
sort
of
step,
one
was
to
get
it
running
with
the
job
executor
service,
which
we've
got
and
we've
got
a
video
of
that
which
is
on
youtube
step.
Two,
I'm
just
having
a
look.
I've
been
off
off
sick
for
a
few
days,
but
we
had
a
call
with
pepe
the
devrel
from
k6
and
we're
thinking
about
how
to
build
the
extensions
in
the
k6.
B
C
Now
one's
going
really
well,
we've
started
coding
and
we
we've
been
playing
around
with
flux
and
getting
the
event
sent
in
I've
made
a
small
go
up
just
to
receive
the
payload
because
it
doesn't
support
generic
posts.
Yeah
so
I'll
probably
put
a
proposal
into
flux
for
me
to
do
a
lot
of
coding
in
the
notification
controller.
C
So
I'm
going
to
start
gathering
requirements
for
that
because
at
the
moment
we
have
an
app
that
sits
in
the
middle.
But
ideally
we
want
to
change
it
at
the
flux
level.
So
at
the
moment
I'm
gathering
a
proposal
to
present
to
them
and
then
hopefully
I
can
make
it
so
I
can
see
the
cloud
event
instead,.
E
C
What
what
I
I
heard
at
the
cd
from
the
captain
was
considering
having
a
specification
from
cloud
event:
sorry
from
city
events
or
you're
gonna.
Do
your
own
thing?
Does
that
make
sense.
A
So
what
we
are
discussing
so
stevens
is
not
enough
for
captain,
because
we
have
a
bunch
of
other
events
that
are
not
just
not
present
there
and
we
were
discussing
with
fatimi
with
andrea,
with
others
about
either
spinning
of
application,
life
cycle
events
to
a
separate
standard
for
making
a
part
of
cd
events,
which
seems
to
be
feasible
for
me,
so
that
we
can
ensure
that
all
events
captain
needs
or
produces
actually
part
of
the
specification.
A
C
D
C
To
see
if
it's
feasible,
if
I
do
the
coding
that
it
can
cater
for
both,
I
just
have
to
do
a
bit
more
research
into
it.
C
Okay,
yeah
it's
a
little
bit
of
work
in
the
flux
because
I
haven't
set
it
up
yet,
but
I've
looked
all
through
the
card
and
I
know
what
I
need
to
do
so
I
just
have
to
convince
him
to
let
me
do
it.
A
C
Yeah,
we've
actually
technically
done
the
argo
city
integration.
Already
I
mean
we
can
do
small
features
to
make
it
better
and
easier
to
use,
but
yeah
a
lot
of
it
fluxes
harder
because
they
haven't.
They
don't
have
that
capability
in
yet
so
I'm
getting
me
hard
to
do
a
lot
of
the
the
flux
logic
around
syncing
and
then
talking
back
to
captain.
You
know
and
then
I'll
focus
on
the
big
piece
of
work
for
flux.
So
a
lot
of
it
will
be
focusing
on
flux
at
the
bottom.
F
A
C
And
a
quick
question
around
that,
so
I've
been
spending
quite
a
bit
time
with
me
and
we
we
do
peer
programming
and
I
do
it
under
my
name.
Is
that
a
problem?
If
I
do
the
commits
under
my
name
or
does
it
need
to
be
under
hers
or
it
doesn't
matter.
A
When
a
student
participates
in
a
common
development
environment,
so
they
require
that
basically,
the
students
for
dementia's
work
should
be
still
available
for
evaluation.
So
if
you
submit
some
small
purchases
et
cetera,
it's
one
thing.
But
if
you
submit
two
thirds
of
the
project,
then
it
becomes
difficult.