►
From YouTube: Keptn Documentation Office Hours - Mar 30, 2023
Description
Meeting notes: https://docs.google.com/document/d/156pqw4r_O6O7O-YDm9DfuuBUS3GvAXmvjjDyFEpbwUY/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
A
B
A
B
C
B
A
I,
don't
think
they'll
I
mean
you
can
apply
for
multiple
ones,
but
I
think
you
can
only
get
one
because
there's
some
overlap
and
both
of
them
are
supposed
to
be
close
to
full-time
work,
I
think
but
I
don't
know
for
sure,
I
I,
don't
know
all
the
rules
and
I
don't
know
who's
supposed
to
be
figuring
this
out.
So
there's
a
little
bit
of
bed
limit
our
end
and
I
apologize
for
that
I.
B
A
A
C
A
A
A
A
Okay
and
I
probably
put
it
out
too
long.
The
question
of
rescheduling
this
meeting
I
chose
this
time,
because
I
thought
it
was
a
day
that
we
didn't
have
other
community
meetings
and
we
put
it
in
an
hour
that
I
thought
would
be
convenient
for
all
the
people
in
India
and
Australia
and
I'm
getting
the
impression
that
many
of
the
people
in
India
have
University
obligations.
At
this
time,
though,
we
may
need
another
time
slot,
but
we
need
to
hear
from
them
before
we
can
do
anything
about
that.
Right.
B
B
Okay,
so
in
a
in
a
nutshell,
basically
the
the
markdown
Lin
thing,
maybe
is
a
bit
drastic
or
maybe
we
can
configure
the
rules
so
that
the
most
serious
or
egregious
sort
of
violations
cause
the
pr
to
be
blocked
or
or
you
know,
fail
the
little
tick
there.
But
it
just
seems
a
bit
drastic.
Like
you
miss
one
line
or
you
add
one
extra
line
and
the
whole
PR
just
goes
red
and
then
okay.
A
A
A
A
Can
get
I
just
there
are
no
simple
PR's
I,
just
spotted
that
I
approved
it
anyhow,
but
I
know.
Mark
Dan
does
not
like
two
blank
lines
in
a
row:
I
actually
I
had
one
that
I
think
it
was
bitching
about
one
line
between
list
items
and
that
I
would
actually
object
to.
But
so
I
just
made
this
suggestion
to
remove
one
of
those
lines,
but
it's
not
committed.
So
why
is
it
just
failing?
So
maybe
it's
maybe.
B
C
A
B
C
Here
is
the
the
the
thing
I
would
say:
if
it's
manual
work,
it
would
block,
but
we
have
a
make
Target,
which
will
fix
all
the
minor
issues
like
that
automatically
without
using
the
English
you
can,
you
can
run,
make
markdown
link
fix
and
it
will
apply
all
the
all
the
as
it
will
handle
all
the
violation
marked
on
linked
can't
as
I
can
handle
on
its
own
and
empty
lines,
and
things
like
that
we'll
fix
those
immediately.
So
it's
not
like
you
have
to
do
a
lot
of
manual
work.
C
A
C
C
C
A
B
There
is
actually
you're
absolutely
right,
I,
just
the
other
thought
and
I.
Don't
know
whether
this
is
technically
possible.
Is
let's
just
not.
Let's
put
this
in
a
GitHub
action
so
that,
even
if
whatever
I
push
GitHub
takes
care
of
it
is
that
possible.
I
mean
I'm,
I'm
saying
this
like
this
is
technically
possible.
I,
don't
know
these
are
just
ideas.
Yeah.
C
This
is,
this
is
there's
a
lot
of
fuzz
around
it
anyways
with
the
discussion.
What
do
you
want
as
a
because
what
does
a
developer
want?
So
most
senior
developers
do
not
like
if
C
I
am
English
with
their
commits
and
ads
commits,
and
things
like
that
to
change
code.
That's
that's!
The
the
question
is
what
is
acceptable
to
the
user?
Technically,
it's
not
a
problem,
but
what's
what
do
you
as
a?
B
A
C
A
C
A
A
B
B
Bother
a
leading
to
abandoned
PRS,
so
maybe
yeah
I
mean
that's.
The
best
solution
really
is:
let's
discuss
this
with
everybody,
because
there's
only
four
of
us
on
this
call.
We
can't
really
go
and
make
decisions
and
there's
going
to
be
a
lot
more
voices
and
a
lot
more.
You
know,
Simon.
You
made
a
very
good
point
about
developers,
we're
just
talking
about
docs
here,
there's
a
lot
of
different
opinions.
C
There
are
certain
things
we
could
definitely
do
actually
there's
this.
On
the
one
hand,
we
could
improve
the
action
if
it
fails
to
write
a
comma
or
to
write
a
comment
with
hey
run,
make
McDonald's
fix
if
it's
not
working,
take
a
look
at
the
doctor.
So
if
you
cannot
run
it,
take
a
look
at
the
documentation
here,
yeah
and
why
we
are
doing
this
because
most
of
the
time
feedback
helps
people
to
understand.
What's
going
on,
and
we
can,
we
can
try
to
add,
add
this.
B
One
of
the
the
best
examples
of
that
is
is
I,
keep
missing
the
dco
and
it's
it's
obviously
my
fault,
it's
just
a
typo
or
haven't
you
know,
but
on
the
cross
it
actually
gives
me
direct
instructions.
You
know
dummy
copy
and
paste
that
that
fix
and
and
I
you
know,
that's
not
irritating,
then,
because
I've
got
the
way
to
fix
it.
You
know
the
irritating
thing
is
just
getting
the
Red
Cross
and
going
oh.
How
do
I
fix
that
now.
A
Oh
I'm,
not
getting
any
of
the
instructions
to
work,
what
I
discovered
what
I
I,
because
I
go
back
and
I
did
commit
digests
what
I'm
seeing
is
when
there's
like,
merges
and
rebases
and
and
stuff
like
that,
I
need
to
use.
You
know
I'm
in
the
habit
of
it.
If
you
give
me
a
stupid,
merge
description
for
the
commit
and
I
go
with
it
and
I
need
to
add
to
the
app
that
I've
signed
off
on
it,
but.
A
I
know
yeah
I,
usually
I'm,
calling
somebody
up
and
begging
them
to
watch
over
my
shoulder
because
I
don't
completely
but
Simon
in
the
stuff
you
wrote
up,
which
is
not
in
the
docs
section,
but
you
wrote
up
some
stuff
about
that
in
the
top
level
of
life
cycle.
If
we
go
through
and
set
up
all
our
files
does
that
assignment
happen
automatically,
so
we
don't
have
as
many
chances
to
forget
to
do
it
and
screw
up.
I
haven't
done
all
that
stuff
that
you
documented.
A
C
A
B
Oh
no,
no,
maybe
maybe
it
was
misleading.
So
there
is
absolutely
no
issue
with
dco
the
the
commit
the
contributor
guide
is
fantastic.
The
it's
correct
what
it
says
the
prepare
commit
message:
if
you
don't
have
a
prepare,
prepare
commit-
and
you
forget
to
add
the
dash
s
if
it's
user
error,
my
point
was
actually
that
the
warning
is
good
on
the.
B
So
it
will
fail
correctly,
but
to
get
me
to
to
solve
the
problem.
It's
excellent
because
it
gives
me
how
to
solve
the
problem
right
there
on
the
pr.
So
we
can
use
that
that
model
that
that
the
fact
that
that's
great
and
and
and
do
the
same
with
markdownlin
so
just
give
that
hint
to
the
user
I
was
I,
was
just
using
dco
as
an
example
of
what
we've
actually
done
really
well.
A
B
B
A
A
B
Well,
no
there's
two
there's
two
things:
there
was
the
markdown
issues
that
we've
discussed
already,
but
then,
if
a
single,
if
there's
a
PR
with
a
single
commit
which
I
emit
in
code,
development
is
probably
an
edge
case,
but
in
docs
it
could
actually
be
a
significant
number
of
PRS.
If,
if
something
things
are
very,
very
small,
what
I
hit
on
that
PR
is.
B
Know
that
so
and
and
the
pr
has
to
be
conventional,
commit
so
docs,
colon
whatever,
but
it's
too
late,
because
I've
already
made
the
commit
with
you
know,
whatever
random
text
right
so
then
I've
got
to
go
back
and
amend
the
commit
and
rebase
the
branch,
and
it's
just
again,
it's
just
seems
silly.
So
then
to
honestly
get
rounded
I
just
made
another
commit
which
is.
Is
it
says
it's
fair
to
do
and
in
this
case
I
could
I
could
actually
genuinely
make
another
useful
commit
on
the
pr.
B
C
C
That's
not
something
which
is
a
little
bit
a
little
bit,
not
to
say
I.
Had
this
discussion
already
regarding
even
Monica
within
dinosaurs
and
I
do
think
semantic
pull
requests
do
make
sense
for
your
squash
merch.
So
you
you
you're,
hitting
an
area
where
I
said
semantic
pull
requests.
It's
I
think
we
only
check
the
title
or
it's
not
that
we
are
checking
the
that
we're
checking
the
commits
I
think
so.
B
So
this
one
1156
it
was
moaning
because
I
did
the
commit
I
raised
the
pr
and
I
changed
the
name
of
I
made
sure
because
I
know
about
the
conventional,
the
whatever
commits
I
made
sure
it
was
docs,
colon,
blah,
blah
blah.
But
obviously
my
commit
message
was:
you
know
this
fixes
issue,
whatever
whatever
random
string,
I
decided
to
put
in
the
commit.
B
C
This
is
this,
is
something
I
send
a
link
in
the
chat
with
the
with
the
with
the
recording
files
and
there's
also
the
reasoning
behind.
We
chose
that,
but
this
is
something
where,
where
the
question
is
more
to
to
educate
the
the
how
to
say,
there
are
two
options
to
that:
on
the
one
hand,
this
this
was
chosen
because
git,
if
there's
one
commit
git,
takes
this
one
commit,
as
you
ask
question,
merge
message.
C
So
there
are,
there
are
these
two
sites
where
you
either
take
this
this
as
a
we
can
say,
hey
to
our
maintainers,
when
you
squash
much
pay
more
attention
and
see
that
it
is
a
proper,
proper
title
used
for
this
cross
merge.
Even
if
it's
one
commit,
then
we
can
deactivate
this.
So
the
question
is
what
is
I?
Currently
it's
a
safety
net
for
the
maintainers
to
have
proper,
commit
messages,
and
this
is
now.
C
C
This
would
be
the
the
easiest
way.
The
easiest
solution
would
be
when
we
can
configure
GitHub
I
think
there
is
somewhere
a
setting,
but
we
need
to
take
a
talk
with
this
with
Giovanni
and
more
hits
more
likely.
Also,
so
that
we
change
it
to
to
the
to
the
squash
message
to
be
the
message
for
us
to
be
the
pull
request,
title
and
the
pull
request
as
a
description
rather
the
rather
than
the
rather
than
the
commit
title
and
the
commit
message.
A
B
Again,
I
think
a
an
open
discussion,
because
there's
probably
lots
of
very
very
good
reasons
why
it
is
the
way
it
is
I'm.
Obviously,
looking
at
my
tiny
little
piece
of
of
use
case,
it
might
be
an
absolutely
awful
idea
and
then
that's
absolutely
fine
yeah.
That's
that's
just
start
having
that
discussion,
I
guess.
A
Because
I
do
know
that
which
I
hardly
ever
do
anything
that
doesn't
require
a
second
commit,
but
I've
lately
I've
had
a
couple
of
new
PRS
that
I
type
in
a
good
commit
message
and
when
I
go
to
GitHub
to
actually
create
the
pr
what
it
has
picked
up
for
the
title
is
actually
the
name
of
my
branch
and
not
what
I
typed
in
as
a
message.
It's
not
consistent.
Sometimes
it
happens
and
sometimes
it
doesn't
but
and
I
haven't
it.
A
B
B
Okay,
cool
in
that
case,
I've
got
one
other
thing
which
is
is
just
generally:
let's,
let's
start
it
again,
let's
start
a
discussion
in
the
community
about
how
we,
particularly
for
docs
I,
think
coders
is
a
different
thing,
because
code
obviously
is
critical.
You
know
if
you
get
the
wrong
code
merged,
whereas
docs
is
a
bit
more
forgiving.
A
B
A
A
C
A
Do
a
quick,
a
quick
merge
to
get
like
something
set
up,
so
I
can
do
little
ones
in
there
and
I'm
about
ready
to
just
write
a
whole
section
at
a
time
and
make
you
know
2
000
line
PR,
but
at
least
I
get
to
do
it
all
while
it's
in
my
head,
rather
than
having
to
wait
for
a
week
or
instead
of
waiting
for
a
week
or
two
for
something
that
I
thought
I
could
get
merged
in
an
hour.
So.
C
A
Am
but
for
the
life
cycle
toolkit
requires
two
approvals
so
for
Captain.
If
somebody
else
writes
it
and
I
can
approve
it
and
if
I
think
I
have
the
expertise
to
approve
it
once
in
a
while.
It's
something
that
I
really
think
somebody
else
would
there
look
at,
but
yeah,
but
I
have
permissions
with
one
approval.
So
with
my
approval,
I
can
merge
it,
but
with
klt
I
need
a
second
one,
and
if
it's
something
good
and
Meaty
that's
great,
but
but
we
can't
with
everything
in
one
repo
we
can't
have.
C
B
C
Within
the
inventory
there
is
is
a
ticket
where
we
can
say:
hey
I
want
to
so
this
has
been
merged
yesterday.
So,
where
we
can
say,
hey
I
want
to
get
access
to
this,
and
that
kind
of
repository
as
this
and
as
our
to
this,
so
we
have
this
setting.
Did
you?
Did
you
get
the
peribolos
changes?
Did
you
have
a
look
at
the
peripherals
changes
we
do?
We
did.
C
This
is
this,
makes
it
a
little
bit
easier.
There's
still
there's
still
the
need
from
the
governance
committee
to
approve
them
and
merge
them.
But
what
is
the
process
we
have
peribolos
running
and
with
peripolos?
We
have
this
this,
although
we
can
create
an
issue
where
we
say:
hey
new
issue
and
I
want
to
organization,
membership
and
I
can
say
get
started
and
which
level
I
do
want
to
have.
C
With
my
GitHub
with
my
GitHub
membership,
there
are
certain
things
for
a
trust
member
being
in
approval
for
a
sub
project
being
a
maintainer.
Just
to
this
is
more
likely
the
requirement
list,
and
there
is
also
the
the
need
in
here
for
creating
then
and
pull
request
according
to
that,
and
we
have
within
our
config
repository,
we
have
there
this
Captain
folder,
which
handles
our
captain
GitHub
organization
and
we
have
so-called
different
type
of
work
groups.
C
For
example,
we
have
the
talks,
work
group
or
it
can
be
a
a
where
you
can
have
access
to
certain
repositories
regarding
the
doctor.
So,
regarding
the
old
documentations
and
for
example,
we
then
have
this
life
cycle
toolkit
where
we
also
have
a
work
group,
and
we
see
that
admins
are
Morehead
and
Giovanni
and,
for
example,
approvers
are,
are
Mac
in
this
kind
of
way
and
those
are
the
repositories
affecting
and
with
a
pull
request.
You
can
add
your
GitHub
handle
there
and
as
soon
as
this
gets
approved
and
merge,
it
will
be
applied.
B
A
C
That
yeah,
that's
that's!
That's!
That's
not
a
second
part!
Actually
with
this
with
this,
as
we
can
create,
we
can
create
an
own,
so
we
can
create
here
within
the
docs.
We
can
even
add
the
lifecycle
toolkit
as
a
as
I.
We
should
maybe
as
a
we.
This
is
not
a
question
so
because
the
developers
do
not
want
to
have
the
doc
people
there
as
maintainers,
so
we
only
can
change
that
to
approvers
actually,
but
we
could
create
a
new,
a
new
work
group.
C
C
Perfect
what
what
this
tool
does-
and
this
is
the
thing
there
is-
the
code
owner
file,
which
is
then
the
important
part
because,
based
on
those
on
those
settings,
we
are
creating.
For
example,
teams
like
we
have
this
box
approvers,
which
has
two
sub
teams,
the
the
dock
maintainers
and
the
doc
admins,
and
we
can
use
those
teams,
then,
in
the
code
owner
file
to
Define
what
type
of
code
you
should
you
should
actually
review
and
take
a
look
at.
C
C
But
it
should
be
whatever
as
long
as
the
teams
are
public,
they
should
work
in
the
I
hear
it
is
so
the
code
owners
file
and
using
the
standard,
GitHub
username
or
ad
org
team
name
format.
So
you
can
Define
that
in
your
code
owners
file
based
on
the
team
name,
your
your
your
reviews,
more
likely
and
with
that
we
I
think
we
have
the
right
Tools
in
place.
We
just
need
to
set
them
up
properly
and
get
them
running
and
working
together
properly.
C
A
B
A
B
An
aside
I
think
this
would
be
a
fantastic
like
take
this
whole
topic
and
do
a
presentation
on
this
to
the
captain
to
just
the
open
source
Community,
because
I
think
it's
something
that
a
lot
of
projects
are
going
to
struggle
with
and
how
Captain
has
solved.
This
is
really
valuable
information,
yeah.
C
B
A
A
You
can
make
this
I
want
to
go
back
to
the
to
this
even
quickly,
because
I
have
no
idea
what's
going
on
in
concludes
and
track
here
for
the
these.
No
it's
season
of
docs
right.
What
are
just
a
high
level?
What
are
the
potential
projects
that
we
have
and
then
how?
Many
of
these
are
we
going
to
be
able
to
do
what
I
know
of
is
architecture,
documentation.
A
C
A
A
B
My
my
opinion
there
is
that,
as
I
mentioned
before,
like
before
the
call,
if,
if,
if,
if
the,
if
we
can't
get
the
installation,
if
we
can't
get
the
initial
experience
right,
then
nothing
else
matters
that
much
to
be
honest,
because
people
won't
even
get
there.
So
I
think
this
is
perfect,
because
you're
gonna
as
a
brand
new
user,
you're
gonna,
come
on
to
the
site.
You're
gonna
try
and
you're
gonna
try
out
the
killer
Coda.
Once
we've
got
it.
B
Presumably
you're
gonna
decide
it's
wonderful,
you're
going
to
want
to
try
and
install
it
that
has
to
go
well,
then
you're
gonna
have
to
figure
out
how
it
works,
which
is
architecture
and
then
you're.
Basically,
if
you're
really
that
interested
you're
into
the
code
and
the
GitHub
repositories
anyway,
and
then
on
the
contributor
side,
the
docs,
tooling,
one
I
think
these
three
projects
really
nicely
cover
a
good
chunk
of
what
we
need
at
the
moment.
Right.
A
And
then
what
I?
What
my
plan
is
is
in
addition
to
these,
this
leaves
the
whole
area
of
how
you
actually
put
together
your
captain,
app
I
mean
it
will
some
of
that'll.
You
know
because
a
lot
of
it
is
just
the
labels
and
annotations
and
stuff
which
I
think
we're
gonna
have
to
do
under
installation,
because
nothing
runs
till
you
do
that,
but
then
get
into
more,
like
you
know
me,
and
it's
maybe
walking
through
a
series
of
app
of
Captain
apps
that
are
actually
a
little
more
interest.
A
A
A
B
A
A
A
So
when
somebody,
if
somebody,
if
somebody
invade,
does
this
at
the
season
of
docs
project
they're
going
to
have
to
create
their
own
epic
and
take
what
they
want
out
of
this
and
we'll
close
this
once,
but
what
we
have.
These
are
Giovanni's,
headers,
so
goal
problem
and
any
technical
details
and
between
technical
details
and
DOD.
One
of
those
is
this:
I
do
different
ways,
but
one
of
them
should
list
sword
of
the
table
of
contents.
A
For
what
the
section
I
mean
these
epics
should
be
for
docs
should
be
sort
of
a
section
of
the
docs,
so
it
should
be
sort
of
a
rough
table
of
contents
of
what
we
think
we
can
have
it's
a
work
in
progress,
it'll
change
as
work
goes,
but
somebody
can
always
look
here
and
see
what
we're
currently
thinking
or
look
and
see
gee.
They
forgot
about
this
and
add
a
note,
and
then
we
have
tasks
for
the
actual
work
to
be
done
and
what
I
did,
because
we
need
to
do
something
fast.
A
So
what
I
propose
is
the
phase
one
which
I
am
working
on
now
and
hopefully
in
the
next
week
or
so,
where
I'm
going
to
go
through
and
pull.
We've
got
a
couple
of
excellent
videos.
Adam
did
one
of
them
and
I'm
going
to
pull
some
basic
steps
out
of
that
and
Target
and
put
together
some
a
little
bit
of
documentation
and
include
links
to
the
videos
that
they
can
use
and
I'm
going
to
do
that
as
a
quick
and
dirty
project.
A
So,
there's
one
that
we
have
nothing,
but
we
need
something
you
know
just
like
we
had
for
Captain.
We
need
something
that
says
you
need
this
much
space
and
you
need
this
version
of
kubernetes
and
there
may
be
other.
You
know,
I,
don't
know
if
we
can
support
every
bloody
version
of
Argo
CD
that
was
ever
released
or,
if
we're
going
to
say
we
or-
and
we
might
say,
we've
tested
it
on
these
releases
in
forward
and
it
might
work
on
the
others.
We
just
haven't
tested
it.
A
But
we'll
have
that
and
we
need
to
think
about
the
you
know
the
kubernetes,
the
standard
thing
you've
probably
got
your
existing
one,
there's
going
to
be
more
interesting
things
there,
but
so
that's
the
approach
here.
I
just
ran
this
to
refinement
this
week
and
just
got
agreement
in
the
refinement
meeting.
A
So
I'm
going
to
be
doing
a
quick
and
dirty
on
installation
and
Adam
you
can
ping
me.
I
will
definitely
make
you
a
reviewer
on
it
can
pull
together
what
we've
got
and
make
it
a
little
bit
better
and
then
much
of
that
will
be
overridden
improved,
discarded
whatever.
When
we
get
to
the
real
project,
that
methodology
makes
sense
for
people
I.
B
Was
looking
through
the
issues
and
maybe
not
these
issues
just
some.
The
only
thing
that
was
missing
for
me
was
who
could
provide
the
you
were
raising
questions
but
I
didn't
the
it
wasn't
clear
who
could
provide
the
information
and
again
I'm
thinking
about
new
contributors?
So
if
they
come
along
and
go?
Oh
that
sounds
interesting.
The
first
question
they're
going
to
have
is
well
who
do
I
speak
to
so
then
they
get
on
Slack
and
and
ping
us
or
you
directly.
B
A
A
A
A
A
A
A
We'll
put
that
as
an
idea,
what
I
am
proposing
is
that
this
be
I
think
this
becomes
a
good
roadmap
for
when
you're
working
at
so
people
who
are
preparing
proposals
for
season
of
docs
I'm,
going
to
recommend
that
they
set
up
an
epic
and
put
down
what
they
can
in
it
and
then
use
that
as
Source.
You
know
they
can
largely
I,
think
copy
and
paste
that
information
into
their
proposal,
or
maybe
I,
don't
know
if
they
can
link.
A
A
A
But
it
all
what
it
also
means
is
that
at
any
given
time
anybody
can
look
and
either
just
thought
of
you
know
in
thought
questions
and
you
can
see
what
tasks
they
have
identified
and
if
one
of
those
or
you
know
can
ping
somebody
and
say:
can
we
get
this
done
faster
or
you
know
all
sorts
of
things?
It
becomes
a
road
map
that
everybody
can
look
at
easily
to
know
where
we
are
on
something.
A
A
A
They
were
not
getting
Rec
sheets,
the
only
one
who's
showing
up
and
he's,
probably
not
even
so.
Okay,
so
I'm,
just
gonna
Mark.
That
next
meeting
is
next
week's
meeting
is
canceled
because
of
Passover
people
are
going
to
love
that
and
and
we'll
go
from
that.
So
I'll
see
you
every
little
in
two
weeks,
maybe
at
a
different
time.
If
we
can
find
a
time
that
more
people
can
attend.