►
From YouTube: Keptn Documentation Office Hours - Jun 1, 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
B
B
I'd
say
it's
progressing,
it's
continuing,
but
the
meeting
are
all
overlapping
with
the
capital
meetings.
That's
why
I'm
never
here
anymore,
actually
and
last
week,
I
lost
three
kilos
into
I.
Think
three
days
so.
A
B
B
A
Well,
I
suppose
we
should
do
what
we
can
let's
see,
and
where
is
now
he
just
lost
it.
I
thought
I
had
this
all
set
up
here
there
we
go
yeah.
A
So
does
any:
oh,
we
have
open
PR.
Somebody
added
those
anybody
knows
anybody
here,
so
maybe
somebody's
coming.
Yes,.
B
A
Right,
oh
good,
yeah,
Josh,
Gonna,
Come,
there's
yes,.
A
Man
very
well
I,
see
you
don't
have
permissions
on
this
deck.
Let
me
near
White
and
I.
Can't
I
I'll,
give
you
permissions
after
this
meeting.
A
But
let's
see-
and
you
know
everybody
here-
I
guess
oh
shoot
I'm
skipped
doing
that.
Okay,
let's
check
out
are
these
your
PRS.
A
A
A
I'm
building
the
dark,
hey
good
good
that
looks
good.
We
should
get
I
think
we
should
get
this
merch.
We
need
to
add,
probably
need
to
add
some
hints
and
stuff,
maybe
to
make
life
easier
right,
but
let's
we
could
merge
what
we've
got
right,
as
everybody
agrees.
Simon
and
I
should
probably
take
a
quick
review
of
that.
A
A
A
A
I'm
dropping
out
yeah,
okay,
all
right
technology,
Simon,
what's
your
day
like
what
I'm
finding
is
that
we
have
to
like
to
approve
fast,
to
get
nobody
to
be
able
to
merge
these
things.
Are
you.
B
A
A
B
Because
I
I
I'm
stopped
starting
to
find
a
way
of
how
to
see
which
I
should
really
take
a
look
at
and
I
think
it
will
start
only
looking
at
pull
requests.
So
I'm
really
dedicatedly
mentioned
because
I'm
not
I,
do
not
have
that
much
time
left
to
review.
All
kind
of
pull
requests
are
now
assigned
to
because
as
soon
as
some
documentation
is
changed,
I'm
getting
assigned
with
this
documentation
approvals
and
it's
quite
a
lot.
It.
B
A
Yeah
but
yeah
it's
for
Adam,
though
we
I,
oh
god,
I've,
been
I,
had
a
bunch
of
PRS
that
need
emerging.
It's
like
one
person
would
approve
and
then
another
person
would
go
on
and
want
an
extra
period
and
put
that
in,
and
that
would
then
cancel
the
approval
to
think
what
okay
here's.
My
Adam's
already
looked
at
these
and
says:
they're
good
they're
ready
to
go
with
you
right
Adam,
but
let
me
give
them
a
quick
read
so
that
I'm
ready
for
that.
C
C
Yeah
absolutely
I
wonder
if
there's
a
way
to
better
highlight
things
that
are
stuck
for
a
while
in
this
sort
of
state
that
the
work
is
there.
It
just
needs
a
review,
maybe
maybe
we
can
create
a
a
dashboard
also.
You
know
something
that
just
says
come
on.
This
is
still.
This
is
still
just
stuck
because
yeah
I
don't
know
I'm
I'm
getting
buried
under
notifications
as
well.
I
mean
I,
wake
up
every
day
and
there's
at
least
100
years.
A
C
B
You
to
do
that
I
will
take
a
look.
I
will
see
as
I
can.
I
cannot
promise
anything
because
between
child
duties,
appointments
and
a
meeting
with
an
afternoon
with
five
hours
meeting
straight
all
right
nice
to
take
a
look
when
I
have
the
possibility
to
do
this
so
but
I
will
ping.
You
I
will
say
to
myself
a
reminder.
A
A
Okay,
cool,
okay,
what
else
so?
Actually,
let's.
C
I've
got
a
quick
question
for
maybe
for
Simon,
because
I
know
Simon.
You
set
this
up.
Originally
the
markdown
link
Checker
the
markdown
lending,
for
example,
I'm
looking
at
a
PR
now
and
it's
failed
I'm
sure
what
I'm
struggling
with
is
just
at
a
glance,
because
what
it
does
is
it
prints
out
all
of
the
links
and
all
of
the
ones
that
were
valid
as
well,
so
I'm,
just
I'm
really
struggling
to
see
which
I've
just
seen
it
there
line.
C
B
That
would
be
a
good
idea
actually
I.
Also
I.
Also
I
I
despise
markdown
link
check
because
of
its
how
it's
working
and
its
usability.
Let's
say
that
way:
it
would
be
cool
to
have
this
more
like
a
markdown
lint
rule
more
likely
than
a
markdown
link
Checker,
because
I
think
the
feedback
you're
getting
on.
Where
is
the
error
happening
and
things
like
that
are
really
really
really
bad?
You
also
have
to
look
for
the
links
you
do
not
see
the
line
or
things
like
that
where
it
is
happening.
B
A
B
Do
not
use
the
browsers,
so
you
do
not
use
the
browser
search.
You
need
to
use
the
the
the
lock
search
functionality.
That's
also
the
strange
part
so
as
I
also
posted
a
link
into
the
chat,
as
I
I
wanted
to
post
a
link
into
the
chat.
This
is
something
there
there
is
this
review
requested
by
me
functionality
from
GitHub,
which
you
can
take
a
look
at
there.
You
see
the
pull
request
where
you
actually
request
as
well.
B
I
can
shortly
show
this
this
this
this
this
one
when
Adam
do
you
have
a
pull
request
number.
C
Yeah
I
think
it
was
one
four
one.
One.
B
One
four
one
one
so,
okay,
we
I
know
it's,
so
we
have
done
this
mark
down,
link
check
with
other,
which
is
failing,
and
most
people
look
for
error.
They.
They
use
the
browser
and
type
in
here
error,
which
is
with
the
browser
search
which
is
not
working,
but
you
have
the
search
locked
on
the
top
right
and
you
put
in
in
here
error.
B
To
this
Arrow
Field,
that's
a
little
bit
sad.
That
GitHub
is
not
not
not
using
the
same
functionality,
but
here
you
see
it
soon:
okay,
yeah,
who
is
it
directly?
Please?
Please
provide
a
file
name
as
an
argument:
okay,
there's
a
directory
within
dot
ND
and
it's
its
name
so
that
you
cannot
search
for
that.
It
seems
like
the
second
arrow
is
that
this
link
is
dead.
Okay,
now.
B
C
I
think,
with
those
those
little
tips
that
it'll
at
least
be
a
lot
quicker,
perfect,
really
good.
A
A
Okay,
let
me
get
in
the
chair
here:
okay,
cool!
Let
me
go
back
if
nobody
else
has
any
other
thing.
I
would
like
to
briefly
has
have
everybody
seen,
there's
some
big
docs
changes
that
are
coming
they're
not
published,
and.
A
You
may
have
noticed,
though,
the
the
landing
page
has
changed
and
if
I
go
into
releases
development
I
can
see
what
is
waiting.
A
The
two
big
things
is,
first
of
all,
we
do
not
have
these
getting
started
guides.
We
have
an
intro
and
we
have
one
getting
started
with
Captain
metrics
observability
data
and
release
cycle.
A
They
are
they're
a
start,
we'll
see
I'm
I'm,
not
some
days,
I,
look
at
them
and
I
like
them,
and
some
days
I,
don't
the
other
big
thing
that
we
finally
have
a
lot
of
used
to
be
hidden
in
Concepts
and
tasks.
A
Some
usage
notes
some
examples:
files
what
we,
what
I
need
to
do
and
I've
got
one
out
there,
because
it
would
be
a
good
first
issue
for
somebody
is
to
have
links,
because
one
of
the
questions
we
have
is
that
we
have
the
AP
and
the
people
for
people
who
really
know
what
they're
doing
that.
This
makes
more
sense
to
me:
I'm
fine,
I'm,
starting
to
figure
it
out,
but
I
think
it's
hard
to
follow.
A
I
would
hate
to
have
to
do
something,
but
for
instance,
I
can
go
into
task
definition
and,
and
there
I
have
it
and
we
have,
and
so
we
have
The
Upfront
stuff,
and
then
we
go
on
to
the
spec
Etc
now
I
think
that
is
auto-generated,
so
it
will
always
be
up
to
date
and
has
that
Advantage,
but
to
me,
I
think
somebody
who's
trying
to
create
one
of
these
things
is
going
to
find
this
more
useful,
but
we
will
have
that
discussion.
A
Yeah
I
think
so
let
us
know
how
it
works.
There's
a
few
things
left
a
bunch
of
the
stuff
that
used
to
be
in
tasks
and
Concepts
is
gone
and
some
of
the
stuff
that
is
there
needs
to
go.
And,
of
course
we
need
a
lot
more
material
in
here,
but
but
there
is
some
progress
happening
at
last.
A
A
We're
going
to
Source
this
I've
got
this
started.
I've
actually
just
started.
Writing
up
some
of
the
first
sections,
Adam
I'm,
going
to
come
bug
you
someday
I
can
write
some
of
the
introductory
material
but
I'm
thinking
that
if
we
sent
you
out
to
a
customer
site
and
they
wanted
to
migrate
to
klt,
you
would
have
some
idea
of
how
you
would
get
started.
A
A
It's.
This
is
not
gonna
success.
Oh
we're
going
to
assemble
information
here
to
help
those
who
want
to
do
this.
Both
markets
under
development,
I'm,
hoping
that
we'll
have
enough
that
we
can
publish
it
for
0.9,
we're
still
waiting
for
0.8.
So
but
that's
probably
another
month
out
and
we've
started
that.
C
Does
not
not
related
to
this
I
think
this
is.
This
is
fine,
does
the
docs
remit,
or
does
this
call
cover
GitHub
readme's,
for
example?
Can
we
discuss.
C
The
thing
I
want
to
bring
up
is
sort
of
related
to
this,
but
we're
putting
focus
on
migrating
to
the
lifecycle
toolkit.
But
actually,
if
you
go
on
the
main
readme
for
the
lifecycle
toolkit
the
life
cycle
toolkit
itself,
the
status
of
things
are
still
in
Alpha
and
beta
and
and.
A
I,
don't
know
I,
know,
I,
think
it's
probably
at
my
end.
Maybe
I
will
turn
my
camera
off
and
see.
If
that's
the
problem,
yeah
that
those
statuses
Giovanni
said
those
are
accurate.
A
The
installation
and
that
has
installation
information
there
that
I'm
about
to
do
a
PR
to
delete
that
and
point
then
save
you
know
for
installation.
Instructions
go
to
the
installation
of
the
docs,
and
then
we've
got
that
obsolete
architecture,
information
that
Amisha
is
working
on
yeah
so
but
yeah
we,
it
did
came
up
in
another
meeting
earlier
this
week.
I
forget
which
one,
but
that
a
whole
bunch
of
the
readme's
are
out
of
date.
Inappropriate,
Etc
and
we've
got
I've,
actually
got
a
PR
out
there.
A
C
I
think
for
me,
coming
back
to
the
migrating
to
the
toolkit
discussion,
one
of
the
and
I'll
raise
this
on
the
issue
as
a
comment.
Of
course,
if
I
was
actually
wanting
to
migrate
to
the
toolkit,
I
would
want
to
know
when,
because
because
version
one
is
is
stable,
it
is
in
long-term
support.
So
from
the
outside
I'm
I'm
thinking,
okay,
well
version
one's
nice
and
stable,
the
toolkit
is
still
experimental
or
Alpha
Beta.
C
A
Think
if
I
understand
and
I,
this
is
not
but
I
think
what
the
the
guide
the
governance
board
is.
Hoping
is
that
in
six
months,
three
to
six
months
that
we
have
a
stable
product
that
I,
if
I,
if
does
that
mean
they're
going
to
make
it
an
LTS
I,
don't
know,
yeah
may
not
be
I
mean
we
may
still
go
on
and
add
features,
but
that
it
will.
We
will
quit
having
breaking
features
every
month,
I.
C
Think,
as
a
good
start,
just
just
getting
the
transparent
being
transparent
about
when
something
moves
from
alpha
to
Beta
to
stable
right,
you
know
why:
why
does
it
move
and
then
users
or
potential
users
or
adopters
can
at
least
make
an
informed
decision
about
how
far
away
it
is
because
it
might
be
still
in
beta?
But
it's
only
you
know
one
tiny
little
thing
away
and
having
that
in
Docs
would
actually
help
adoption
and
help
the
migration
right.
I
agree.
A
So
if
we're
three
to
six
months
from
something
stable,
then
Maybe
and
there's
a
couple
of
big
features
that
I
have
to
understand,
but
that
are
under
development
right
now.
That
I
think
are
considered
crucial.
A
One
of
them
is
the
ability
to
write
the
the
code
for
tasks
in
Python
and
maybe
some
other
languages.
The
other
is
the
container
which,
as
I
understand
it
is
going
to
be
kind
of
like
Jes
was
for
Captain
before
that.
That
I
can
that
my
captain
app
can
include
this
container
and
I
can
run
anything
I
want
to
in
it
yeah,
and
so
those
two
features
yeah
there's
some
big
features
that
are
close,
I
think.
C
A
And
those
will
make
a
difference
and
I.
You
know
what
what
I'm
hoping
is.
I
mean
migration
unless
you've
got
a
simple
migration
that
you
can
create
a
wizard
that
just
does
it
for
you,
and
that
means
two
products
that
are
very
similar
that
just
map
it's
going
to
be
primarily
a
documentation
thing.
But
as
we
work
through
that,
we
learn
something
that's
sort
of
My,
Hope
and
expectation.
Do
you
agree.
C
A
C
But
there
will
be,
there
will
be
an
audience
using
V1
that
could
use
the
toolkit
very,
very
honestly
and
convincingly.
You
know
yeah,
but
I
I,
don't
say
no,
it's
it's
not
just
like
an
upgrade.
It
is
a
completely
it's
a
it's
a
shift
in
methodology
right.
A
Think
it's
the
most
coherent
explanation
of
Captain
versus
klt
that
I've
seen
so
I'm
gonna
write
that
up
I'll
give
them
a
link
to
the
video
if
they
want
to
see
that,
but
to
First
say
that
you
know
and
then
and
have,
and
because
what
I
see
too,
is
that
there's
a
certain
number
of
people
who
are
running
V1
and
it's
starting
to
get
really
tough
because
their
world
is
getting
more
get
opsy.
And
you
know
people
are
doing
their
own
services,
not
part
of
the
monolithic
repo.
Where
everything
is
so
it
will
be.
A
You
know
they
will
be
moving
up
and
they
want
to
change
their
Paradigm
as
well.
But
then,
like
somebody,
said
to
me
yesterday
what
quality
Gates
don't
work
and
it's
like
yeah
all
the
fancy
calculations
you
get
with
calc
with
quality
gates
are
not
supported,
but
I,
don't
know,
I,
think
a
lot
of
people
are
probably
using
quality
Gates,
just
as
very
simple
evaluations.
A
C
I,
just
I
haven't
seen
a
discussion
on
on
GitHub
or
maybe
I've
missed
it
about.
You
know
going
back
to
what
you
said
about
the
python.
For
example,
where
was
the
where's
the
discussion
that
that
is
because
that
to
me
is
a
feature
we
could
in
theory,
one
one
argument
is
well,
you
can
go
to
a
version,
one
release
of
klt,
have
it
stable
without
python
at
all.
A
C
A
B
C
It's
just
the
way
it
is
and
but
it
all
goes
into
the
migration
guide,
because
actually
that
might
discussing
that
on
the
documentation
might
actually
encourage
people
to
migrate.
If
they
say
well,
it
is
stable
as
long
as
you
don't
need
python
right.
You
know
because
you
can
write
it
in
typescript,
so
you
can
make
the
argument.
It
isn't
an
alpha
or
beta.
It's
it's
actually
stable.
Now,
because
it's
in
typescript,
if
you're,
if
you're
judging
it
by
some
other
metric
like
can
it
do
Java
or
python?
Well.
Well,
no,
it's
it's
forever!
C
Gonna
be
unstable
uh-huh!
Until
that
functionality
is
there,
but
yeah.
A
And
then
somebody's
gonna
want
C,
plus
plus
or
C
sharp
or
C,
or
let's
do
assembler
yeah
good,
great
I.
Let
me
I'm
gonna,
ask
Giovanni
because
it
it
may
be
that
there
are
meetings
where
this
is
being
discussed
and
I
don't
make
all
the
meetings
and
I
don't
watch
all
the
recordings.
A
Right
but
yeah
and
I
think
there
are
small
and
that
you
know
when
you
have,
if
you're,
really
smart
people
who
like
have
small
discussions
in
the
hallway
or
they
go
to
a
conference
and
then
over
dinner
and
drinks
skydo.
We
need
to
do
that.
That's
not
a
terrible
thing,
but
it's
not
a
great
process
and
it's
not
real
open,
so
I
mean
I
know
once
they
decide
that
something
is
a
priority,
then
it
goes
through
the
refinement
meetings
and
those
are
public
and
there's
where
they
discussed
the
actual
implementation.
A
Yeah
I
mean
yeah,
because
we
do
we
have
the
known
limitations
list
and
if
there's
anything,
there's
in
there,
it's
in
the
release
notes.
But
if
there
was
a
limitation
in
0.6
say
that
isn't
fixed
by
0.7
to
0.7
list
isn't
going
to
include
it
but
or
even
if
it
did
I
mean
you
know
the
oh
God
and
I
hate
doing
this
kind
of
Doc,
but
where
you
have
your
your
known
limitations
and
then
with
the
new
release,
this
is
fixed.
This
is
fixed.
This
is
still
there.
C
A
C
If
we,
if
we
got
the
reasons
down
on
paper,
that
so
the
the
why
something
will
moves
from
one
state
to
the
other,
it
actually
it
it
could
you
could
make
the
argument
that
that
whole
discussion
goes
away
because
it
kind
of
unless
it's
announced
in
a
release
by
default.
It
stays
as
the
current
state
it's
in.
If
that
makes
sense
right,
because
I
know
that
this
thing
this
condition
hasn't
been
met
and
therefore
I
can
just
assume
it's
still
in
in
Alpha.
C
Whereas
if
I
can
look
at
the
captain
road
map
and
see
oh
buy
the
next
release
version,
we
will
get
this
x,
this
functionality
or
the
or
this
Improvement,
and
that
by
its
nature
of
being
there
and
on
the
road
map
and
I,
can
see
that
next
month,
I
know
klt
will
go
to
Beta
or
the
cert
manager.
So
I
can
actually
it's
removing
a
lot
of
the
work
from
the
maintainers,
because,
as
a
member
of
the
public
or
someone
evaluating
the
project,
I
can
see
that
I
can
do
that.
Maths
myself.
A
Right,
but
another
thing
to
think
is
like
okay:
if
we
release
0.8.0,
you
know
which
I
think
is
coming
soon
and
we
put
out
the
release,
notes
and
I
come
in
and
that's
the
first
release.
I
do
am
I
expected
to
read
the
release,
notes
for
all
the
previous
releases
to
know
of
any
Applause
that
there
might
be
any.
A
A
A
Right,
where
do
I
look
for
known
limitations,.
A
A
Want
to
get
started,
have
you
tried
for
people
who
want
to
get
started?
I'd
really
like
to
hear
if
those
getting
started
guides
work
for
them.
A
A
Because
because
one
thing
we're
trying
to
do
one
of
the
things
that
happened
with
Captain
V1
is
we
well
instead
of
getting
started
guides
we
had
all
these
tutorials,
most
of
which
were
obsolete.
They
didn't
get
maintained
and
stuff,
but
they
had
information
in
them
that
weren't
in
the
docks
anyplace
else.
A
So
we
had
people
who
never
looked
at
the
text.
They
just
worked
from
the
getting
started
from
these
tutorials
and
with
all
sorts
of
problems.
So
we
we
decided,
but
we
also
don't
want
to
duplicate
I
mean
we
don't
want
20
sets
of
installation
instructions.
So
the
getting
started
guides
that
you
know
the
step.
One
is
go
to
the
installation
documentation
and
follow
those
instructions
to
install,
which
is
a
little
less
handy
for
the
users.
But
if
we
only
have
one
place
where
we
have
those
instructions,
we
keep
them
up
to
date.
A
A
So
Yash,
when
we
get
your
PR's,
what
do
you
are
you
do
you
want
to
go
forward
and
do
some
more
of
these.
D
Sure
sure
definitely
would
like
to
contribute
to
the
migration
dog
also
the
ktl
one
because
Misha
had
talked
to
me
and
he
she
told
that
if
you
are
busy
working
contributing
guide,
then
I
can
work
on
it
and
if
you
are
able,
then
you
go
further.
You
proceed
it
with
the
given
issue.
A
C
Josh,
have
you
added
yourself
as
a
a
member
to
the
captain
organization?
Have
you
actually
kind
of
got
on
the
contributors
ladder
and
things.
D
I
have
been
contributing,
but
I
have
not
been
applied
for
the
member
post.
Basically,.
C
I
I
I'd
certainly
sponsor
sponsor
you.
If,
if
you
wanted
to.
D
A
A
Great
and
I
assume
you
did
brilliantly
on
your
exams.
Yes,.
A
A
Oh,
thank
you
all
for
attending.
Thank
you
for
your
PR's
Josh
and
we're
going
to
get
those
merged
and
move
on,
show
them
I'm
sure.
Definitely,
okay
have
a
great
week
and
we'll
talk
next
week.
Sure
you
know
where
I
am
in
the
meantime,
bye.