►
From YouTube: Keptn Community Meeting - Aug 03, 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
A
B
A
I
don't
know
how
to
make
it
larger.
Unfortunately,
okay,
a
couple
of
quick
bits
of
news
for
those
who
don't
know
release
18
of
captain
has
been
released.
There
is
actually
an
18.0
and
18.1.
They
had
a
small.
Oh
thanks,
deepai
and
I
got
I
killed
myself
in
the
middle
of
your
name.
Sorry
about
that
yeah
yeah,
the
continuing
to
work
on
the
doc
changes
we
now
have
basically-
and
it's
all
incrementally,
oh
before
we
go
on
with
that
stuff.
Does
anybody
have
anything
to
add
to
the
agenda?
A
C
I've
got
a
pull
request
open
for
the
job
executor
service,
which
allows
pushing
to
prometheus
and
things,
but
it's
literally
that's
it.
It's
there's
a
pull
request
to
open,
I
suppose
so.
It
doesn't
really
need
to
be
an
agenda
item.
C
It'll
be
docs
for
the
job
executor
service.
So
not
not
mainline
call.
A
Oh,
it's
in
captain.github.com.
C
No,
it's
it's.
One
of
the
captain
car
says.
A
Oh
okay,
I
want
to
sell,
go
look
for
the
pr
or
you
can.
You
can
add
it
to
the
agenda.
If
you
want
to
everybody
should
have
rights,
let's
say:
okay,
so,
oh,
let's
go.
I
was
gonna.
Do
news?
Wasn't
I
again
I'm
so
good
at
this?
So
we
have
we're
what
I
trying
to
do.
We
want
one
section:
that's
managing
projects
that
my
goal
is.
This
will
be
the
information
about
everything
you
do
with
projects
that
you
do
with
all
projects.
A
So
you
create,
you
need
the
upstream
and
you
can
update
and
you
can
delete
and
all
these
sorts
of
things
and
that's
under
manage
projects.
The
other
section
I
don't
have
a
good
title
for
for
now,
I'm
calling
define
projects.
What
I
want
that
to
be
is
sort
of
sections
about
here's,
how
you
do
remediation,
here's,
how
you
do
evaluation.
A
I
would
like
I'm
hoping
that
we're
going
to
get
some
content
there,
that's
a
little
less
shallow
than
what
we've
got
now
and
then
have
some
what
I
would
call
glue
documents
that
say
you
know
you
could.
If
you
want
to
do
development
and
hardening-
and
you
know
you
could
go-
you
can
put
these
together
this
way
or
whatever
I
still.
A
I
don't
know,
that's
the
general
right
now.
What
we've
got
is.
We've
now
got
separate
sections
in
the
dock,
and
I've
pulled
together
all
of
the
relevant
content
that
we've
currently
got
into
those
and
it's
kind
of
a
mess.
When
I
look
at
it,
it's
like
we
need
to
do
some
work
here.
A
So
that's
where
we
are
the
gsoc
project
for
the
new
doc
engine
seems
to
be
proceeding
nicely
and
hopefully
we're
going
to
be
able
to
move
on
to
that
I'm
hoping
by
september.
C
Yeah,
just
a
quick
question
on
the
on
the
docks
and
the
new
dock
engine
are:
are
we
planning
to
just
lift
and
shift
all
the
existing
docks,
or
is
there
kind
of
a
restructure
going
on
there?
Yes,.
A
Both
because
because
you
know
because
of
resources,
I
suppose
the
by
definition
we
need
to
restructure,
because
one
of
the
reasons
we're
going
to
the
new
dock
engine
is
will
actually
be
able
to
version
docks.
So
we
will
no
longer
when
you
go
to
the
dock.
Page
you'll
no
longer
have
the
long
list
of
previous
releases
there.
You
will
get
the
latest
and
then
there
will
be
a
drop
down
menu
where
you
can
select.
A
I
think
it's
going
to
be
the
last
three
releases
or
something
to
go
to
so
because
of
that
that
right
there
and
I'm
what
I'm
starting
to
squirm
about
is
exactly
once
once
we
have
releases
that
are
latest,
then
it
will
be
easy
to
have.
You
know
latest
minus
one
latest
minus
two.
What
we're
going
to
do
for
the
transition
so
say
it's
at.
You
know:
release
20
that
we
first
go
live
with
docusaurus.
A
We
have
stuff
like
concepts
and
installation
which
is
outside
of
the
release
specific.
How?
What
is
that
going
to
look
like
when
we
first
do
this,
and
I
don't
know
yet,
but
there
will
be
community
discussion
discussions
and
I'm
hoping
lots
of
people
will
chime
in
long
term,
and
so
I've
already
started
doing
some
restructuring
like,
for
instance,
installation
used
to
be
a
subpage
under
operations
or
under
operate,
and
it's
now
its
own
section
and
I've
got
the
different
tasks.
A
A
A
What
I
realized
was
that
we
had
a
lot
of
information
for
about
how
to
install,
but
the
only
place
where
you
actually
had
kind
of
a
sequential
list.
That
said,
you
need
to
do
this
and
then
this
and
then
this
and
this
order
was
in
the
old
tutorials,
and
so
we
were
getting
a
lot
of
postings
and
help
where
they
were
trying
to
do
a
real
installation
based
on
what
they've
done
in
the
tutorials
and,
of
course,
a
lot
of
the
tutorials.
A
You
know
we
cheated
a
little
bit
to
try
to
get
them
up
and
working
more
quickly
to
say
nothing
of
the
fact
that
they're
several
visions
out
of
shape,
so
so
that
was
it,
but
so
to
have
sort
of
that
list.
That
has
links
to
everything.
So
there
is
restructuring
a
lot
more
restructuring
is
needed
and
I
would
love
input
from
anybody
of
something
you
see
that
needs
restructuring
so
which
do
you
have
something
specific
in
mind.
C
No,
not
really
just
you
you
exactly
what
you
just
said.
Basically,
there's
a
lot
of
duplicate
content,
there's
a
lot
of
sort
of
bits
and
pieces
all
over
the
place,
and
I
don't
I,
the
new
docs
engine
looks
fantastic,
but
I
don't
think
it's
in
and
of
itself.
You
know
lift
and
shift,
and
everything
to
there
is
just
going
to
solve
our
problems.
A
Exactly
and
and
conversely,
without
a
new
doc
engine,
we
could
solve
a
lot
of
the
problems.
A
lot
of
it
is
just
sort
of
writing
and
yeah.
I
want
to
say
we
already
well,
we've
got
actually
somebody
who
didn't
come,
but
somebody
who'd
already
come
on
that
he's,
he's
interested
in
being
a
technical
writer
and
wanted
to
know
if
he
could
contribute
some
stuff
here
and
then
he's
trying
to
install
kept,
and
I
get
this
list
and
he's
like
okay.
A
A
I
think
there's
been
an
obsession
with
the
brand
new
users
and
you
know
so
it's
sort
of
the
high
level
simple
stuff
has
everybody
seen
the
new
tutorial,
the
end
to
end
that
adam
and
absar,
and
I
did
together
adam's
the
brains
of
it.
But
if,
if
you
have
not
seen
that,
I
strongly
recommend
it,
I
think
it's
really
good.
A
It's
you,
you
open
it
up
and
wait
for
three
minutes
and
most
of
the
installation
setup
is
done
for
you,
so
they
don't
have
to
the
old
tutorials.
If
you
got
them
to
work,
you
spent
an
hour
at
least
trying
to
get
getting
everything
set
up,
and
then
you
had
time
for
a
couple
of
trivial
exercises.
A
We've
now
got
a
lot
more
information
in
there.
You
learn
a
lot
more.
So
I
think
that's
a
good
start.
C
C
You
know
to
get
through
because
because
it's
basically
a
full
end
to
end
of
every
core
use
case,
that
captain
offers
from
quality
gates
to
self-healing,
to
you
know,
building
a
pseudo
pipeline
and
and
with
with
it
being
quite
a
lot
in
there,
it
does
take
about
an
hour
to
actually
run
through
it
all.
So
maybe
we
can
shrink
that
down.
Maybe
feedback
from
the
community.
C
You
think
there's
things
that
we
cover
in
there
that
aren't
really
necessary
for
beginners,
especially,
I
don't
think
we
we've
met
yet
dp
dp
on
on
a
core
I'll.
Take
it
you're,
quite
new
to
captain,
so
I'd
be
very
interested
in
your
feedback
as
a
sort
of
relatively
new
user.
B
C
Yeah
and
maybe
maybe
meg-
maybe
that's
also
what
we
can
do.
Actually
it's
a
very
good
point,
dpr
is,
is
yo
because
a
video
we
can
actually
edit
down.
You
know
to
just
the
highlights,
so
it's
a
three
minute
video,
maybe
on
the
on
the
home
page
or
I
don't
know,
maybe.
A
C
A
Yeah
and
that's
yeah,
it's
always
yeah
so
much
I
like
it
because
I
can
get
through
it
in
45
minutes
and
to
me
to
me
it's
a
to
me
it's
about
a
right,
because
when
I
get
through
that,
I
have
some
idea
of
what
captain
is
like
and
now
what
I'm
looking
forward
to.
Oh,
but
I'd
also
like
us
to
have
some
instead
of
everybody,
goes
out
and
writes
their
own
introductory
tutorial.
A
I'd
like
us
to
have
a
good
little
stream
for
really
learning
how
to
do
slis
and
slos
and
maybe
have
like
a
video
and
then
with
a
killer
code,
exercise
that
you
could
work
through
or
something
yeah
yeah
so
and
then,
and
also
help
identifying.
Oh
another
thing
to
watch
for
and
where
I
can
use
help
to
me.
A
I
was
shocked
when
I
saw
we
did
not
have
reference
pages,
for
we
have
reference
pages
for
the
cli
and
the
api,
but
we
did
not
have
reference
pages
for
all
of
these
files
that
you
can
figure
so
I've
started
doing.
Those
shipyard
is
up
there,
which
they
all
need
a
lot
of
work,
but
I
think
shipyard
is
off
to
a
good
start.
A
C
C
A
Right
right,
I
would
say
we're
and
I
I
could
write
up
a
little
bit,
what
I
know
when
we
first
cut
and
the
reason
why
I
checked
thomas's,
either
or
question.
I
said
yes,
when
we
first
cut
over
it's
going
to
look
a
lot
like
whatever
we
have
now,
only
everything
will
be
at
the
top
level.
So
we'll
go
we'll
start
out
with
you
know,
concepts
in
the
tutorial,
not
sure
which
of
those
go
first
installation
and
then
manage
projects
to
find
projects
operate.
A
Your
captain,
I
think
we're
going
to
have
a
separate,
developer's
guide
right
now
we
sort
of
have
a
couple
that
you
know.
Custom
integrations,
I
think,
is
the
section
now
and
oleg
is
working
on
specking
that
out
in
his
copious
free
time,
but
that
will
probably
actually
be
done
in
its
separate
repo
and
then
one
nice
thing
with
docusaurus
is
we
will
be
able
to
easily
combine
documents
from
different
repos
into
one
doc,
set
that
they
will
see.
A
So
but
the
initially
that's
you
know
so
it's
it's
sort
of
this
candy
and
and
actually
I
kind
of
screwed
up
I
set
up
the
I
pulled
the
installation
section
out
of
the
release
specific
parts
and
I
shouldn't
have
done
it
as
early
as
I
did,
but
since
I'd
done
it
I
did
not
want
to
invest
the
time
to
undo
that,
so
that
is
already
outside
and
that's
a
slight
problem,
because
in
installation
are
instructions
for
upgrading.
A
C
A
A
A
But
but
a
lot
of
what
I
have,
I
mean
a
lot
of
the
good
new
content
that
we're
getting
I'm
sitting
here.
You
know
I'm
not
a
technical
writer
and
plagiarizer,
but
watching
what
comes
in
to
help
and
when
they
get
an
answer
trying
to
capture
that,
but
oh
and
one
nice
little
piece.
Another
thing,
if
you
have
not
seen
let
me
go
over
here-
and
this
is
pure
adam-
is
something
that
it's
we
all
know
it.
We
all
talk
about
it.
A
A
A
It
is
under
concepts
here,
but
it's
I
think
it's
brilliant.
It's
lighthearted
a
value
to
tone,
but
he
gets
down
here
and
then
he
talks
about
tooling,
and
you
know
one
team
can
use
circle
ci
and
another
one
can
use
jenkins
and
here's
your
testing
tools
and
out
of
the
box.
You've
got
jmeter,
but
you
can
use
anything.
You
want
observability
tools
and.
A
Some
oh
yeah,
and
this
I
I
really
like
this.
It
made
things
clear
to
me
that
I
sort
of
knew,
but
you
know
helm
surface-
is
listening
for
this
event:
j
meters.
Listening
for
this
now
you
people
that
are
out
there
talking
to
customers.
When
you
see
you
know,
when
you
see
a
subject,
that's
not
there!
A
A
Qualitygate
allows
conducting
a
deployment
release
validation
by
ensuring
that
defined
quality
criteria
are
met.
I
think
that's
true,
but
it
doesn't
grab
me
and
there's
a
lot
of
that
all
over.
So
when
you
see
things
I'm
you
know,
people
ask
questions
another
issue
that
I
have
my
eye
on
that
I
haven't
gotten
into
yet.
A
But
to
me,
when
I
go
into
the
captain
bridge
now
down
here,
here's
the
views.
Here's
your
project
view.
Here's
your
environment,
view
services,
view
et
cetera.
I
have
no
idea
how
to
use
any
of
this
stuff
and
there's
a
little
bit
more
there,
and
then
we
never
integrate.
A
C
The
thing
that
would
concern
me
about
this
is
keeping
those
screenshots
up
to
date.
Yep
it
I
mean
the
bridge
isn't,
doesn't
hasn't
changed
that
much.
You
know
the
core,
but
but
there
will
come
a
point
where
you're
spending
so
long
keeping
these
potentially
keeping
these
screenshots
up
to
date
as
well.
Unless
you
can
get
clever
and
do
an
automated
deployment
of
captain
pre-release
and
grab
some
screenshots
for
them
in
the.
A
States
yeah,
no,
I
I
totally
agree
and
it's
a
real
problem,
because
also
because
then
the
other
thing
I
can
say
is
now
I
I
just
wrote
something
up
and
that
you
know
you
go
here
and
you
click
on
this
item
and
you
click
on
that
item.
Without
seeing
the
screenshot,
it's
not
nearly
as
clear
as
what
you
do,
but
we
certainly
don't
want
gratuit
yeah
and
I
have
a
feeling
that
a
lot
of
these
may
be
out
of
date.
A
Now
it
looks
like
looking
at
the
release
notes
for
release
18
there's
a
lot
of
changes
to
the
bridge,
there's
a
bunch
of
new
stuff-
and
I
don't
I
don't
know
if
that's
reflected
here
yet
so.
C
C
Here's
a
question
to
everyone,
I
suppose,
and
we
can
kind
of
discuss
it
offline
and
and
figure
it
out,
but
the
you
know
those
sort
of
like
walk
through
I'm
sure
there'll
be
websites
or
products
out
there
that
allow
you
to
put
in
your
your
screenshots
and
then
create
like
an
interactive
overview.
So
it's
like
a
tour
basically.
B
C
C
Again
easy
to
say
I
don't
know,
I
don't
know
if
it's
possible
or
or
there's
something
out
there
that
does
it
or
or
what
I
imagine
there
will
be,
but.
C
Yes,
there's
a
thought
exercise
for
everyone.
Just
have
a
have
a
little
google
and
see
what
you
can
find.
A
Right
right
or
of
course,
another
thing
we
could
do
would
be
a
little
video
and
then
like
the
docs
could
sort
of
describe
and,
and
some
of
it
too,
I
think
mo.
There
may
come
a
time
where
we
do
a
massive
change,
but
most
of
the
changes
from
time
to
time
are
going
to
be
small.
So
if
we
had
a
video,
we
could
say
we're
doing
this
for
release.
A
18.0,
yeah
and
19.0
might
end
up
being
slightly
different,
but
we
would
have
warned
them
of
that
so
yeah
button
going
through
and
then
again
too.
I
don't
know
how
much
I
just
want
to
learn
to
use
the
bridge
versus
I'm
trying
to
do
my
quality
gates.
Now
I
want
to
monitor
them
or
I
want
to
trigger
them,
and
we
have.
We
also
have
a
big
separation
here
like
in
under
the
bridge.
We
find
how
you
trigger
a
sequence
on
the
bridge
in
quality
gates.
A
A
C
A
B
Yeah,
I
would
say
I
would
go
yeah.
I
was
just
you
know,
googling
about
what
adam
said
previously
about
having
those
interactive
window
panels
on
the
website.
I
think
that's
actually
a
good
thing
from
an
user
perspective
from
a
new
user
perspective,
it
just
easily
lets
you,
you
know,
get
through
everything
and
set
everything
up,
and
also
the
embedding
videos
in
the
website
is
also
a
good
idea
and
something
I'm
on
the
same
page
with
so
yeah.
C
B
C
Okay,
cool
yeah,
I'm
in
australia,
so
we're
not
we're,
not
a
million
miles
away
yeah.
So
I
can.
I
can
help
you
get
up
to
speed
with
captain
and
then,
if
you
want
to
do
some
videos,
then
the
more
that
would
be
absolutely
fantastic.
C
Sure
yep
yeah
reach
out
more
than
happy
to
help.
I.
C
We
could
get
like
if
we
could
start
with
deciding
sort
of
the
poor
use
cases
like
I'm
a
brand
new
captain
news.
I've
just
hit
the
website
for
the
first
time.
I
just
want
an
overview
of
what
it
does.
That's
one
video
and
then
another
video,
as
you
said,
meg,
would
be
like
cool.
I
I
now
know
what
it
does.
How
do
I
set
up
a
project
and
that's
it?
You
know
the
little
nice
little
bite-sized
videos
great
and
then
we
might
have
them.
We
might
already
have
this
stuff,
I'm
sure
we
do
on
youtube.
A
Yeah,
there's
a
well
there's
all
the
stuff
that
andy's,
but
it's
andy's
done,
got
in
andy's
videos,
I
just
love
them,
but
but
they're
all
sort
of
targeted
and
to
take
one
you
know
and
maybe
make
it
more
generic
and
we
might
find
something.
That's
just
what
we
need
to
or
and
also
short
term.
We
might
have
find
something
that's
80
of
what
we
need.
A
Well,
we
could
put
a
link
into
that
from
the
documentation
for
now
and
then,
knowing
that
later
on,
we
wanted
to
do
something
that
was
more
yeah
and
and
then
the
other
thing
for
something
like
shipyard.
A
I
want
this
to
be,
and
this
is
all
going
to
be
a
huge
reference
page,
but
this
is
where
we've
got
every
last
detail.
For
instance,
here's
where
I
don't
know
a
couple
weeks
ago
somebody
came
on.
Can
I
run
my
sequences
in
parallel
and
I
don't
think
we
don't
have
a
search
engine,
but
I've
got
get
grip.
So
I
did
the
source
tree
and
there
was
nothing
about
that.
So
we
now
tell
them
there
about
that.
A
C
A
Right,
I
have
a
question
another
one.
A
B
So
I
think
I've
I've
posted
I've
posted
a
link
onto
the
captain's
specification
and
there
are
most
all
of
the
events.
B
A
A
So
then,
okay,
there's
another
question
with
the
and
part
of
me
is:
if,
if
the
tools
will
do
it
and
I'm
still
not
100
sure,
if
they
would
would
it
does
this
just
be
long
over
where
it
is
or
should
this
be
in
the
dock,
especially
if
we
had
the
ability
to
have
the
docks
just
pull
suck
that
in
exactly
or
we
could
all
take
it
as
source
and
alter
it?
A
B
B
Developer
facing
and
the
second
one
is
captain
user
facing,
so
it
might
make
sense
to
simplify
the
thing
which
is
specified
in
the
spec
for
the
users
or
simply
reference
to
the
spec.
If,
if
some
users
want
to
get
more
into
depth,.
A
A
C
Yeah
so,
as
as
thomas
says,
leave
the
source
where
it
is,
but
then
we
get
that
plug-in
on
the
new
docs
engine.
As
I
understand
it,
you
just
give
it
that
markdown
link
and
it
just
like
copies
and
paste,
basically
behind
the
scenes
it
just
syncs.
A
Yeah
and
then
and
yeah,
that's
what
then
I
start
saying:
well,
maybe
it
could
be
written
better,
but
if
it's
just
writing
we
can
always
modify
what's
in
the
spec
and
yeah,
so
that
might
be
okay.
I
may
until
we
have
that
just
so,
we
start
seeing
things.
A
I
think
I'm
going
to
make
a
cloud
events
reference
page
and
I
mean
it's
all
we
got
to
go
incrementally
and
for
now
I
will
copy
that
in
and
then
at
the
bottom
of
it.
I
will
give
them
a
link
to
and
say
you
know,
what's
on
this
page
is
a
snapshot
in
time
and
the
official
one
is
here
and
they
will
at
least
have
that
link.
Does
that
make
sense
for
temporary.
C
B
I
think
normally
this
should
be
possible,
but
to
be
honest,
I'm
I
didn't
read
this
back
until
now,
so
I
only
know
that
the
cloud
events
are
specified
there,
because
I
needed
them
some
at
some.
Some
point
in
time.
C
B
A
A
C
What
this
has
been
very
good
for
in
in
practical
terms,
is
pointing
you
know
a
captain,
a
potential
captain
user
to
this
and
saying
you're
going
to
want
to
trigger
a
sequence
here
is
the
the
template
for
how
you
trigger
a
sequence,
for
example,
so
they've
got
that
json
payload,
so
I'm
not
having
to
rewrite
it
over
and
over
and
over
again,
but
primarily
I
see
the
audience
for
this
particular
document
being
devs.
B
A
C
But
yeah
it
doesn't
say
anywhere
that
because,
because
the
way
you
would
read
this
as
a
brand
new
captain
user
is
these
are
the
things
I
can
do
with
captain
and
that's
it.
You
know
I
can
do
a
test,
an
evaluation
or
release,
and
but
on
the
shipyard
side,
we're
saying
well,
your
tasks
can
be
anything
so
there's
a
bit
of
a
mismatch
there,
because
you
meant
your
mind
leaps
to
well.
C
C
A
C
A
C
A
A
A
I
would
really
I'm
hoping
for
the
values.yaml
reference
page
that
eventually
we
can
have
that
suck
the
content
in
or
even
just
the
the
synopsis
of
what
the
file
looks
like
the
default
file,
suck
that
into
the
documentation
and
maybe
have
the
rest
of
the
documentation
authored
as
the
doc
and
there's
a
few.
That
would
be
like
that.
Shipyard
might
actually
be
that
way.
So.
B
C
So,
actually,
one
more
as
you're
talking
one
more
thing
that
came
up
on
on
slack,
which
is
obviously
would
generate.
We've
got
charts.captain.sh
for
the
helm,
charts
for
the
call.
Could
we
do
something
similar
and
again
answers
aren't
necessary
here,
but
just
a
thought
could
we
do
something
similar
print
captain
sandbox
repos?
Would
that
be
good
or
not
arguments
for
and
against
and
also,
as
you've
just
said,
the
values.yaml
for
all
of
the
helm
charts
at
the
moment.
If
I
go
to
the
helm,
repos.
C
There's
no
sort
of
way
I
can
without
downloading
the
tj
tgz
file
and
unpacking
the
actual
helm
chart
itself
and
having
a
look
at
values.yaml.
There's
no
way.
I
can
see
like
a
reference
page
for
each
of
the
core
services
for
the
values,
and
that
would
just
be
really
nice
on
github.
Just
to
be
able
to
see
that
you
know
in
plain
text.
C
A
A
B
A
C
My
my
only
concern-
and
it
is
a
personal
thing-
is
more
having
more
get
repos
and
it's
just
more
places
now,
if
that
polar
inner
tool
that
I
keep
talking
about
is
is
as
good
as
it
sounds,
don't
care
because
then
the
the
website
becomes
the
central
hub.
If
I
don't
want
to
search
through
github,
if
I'm
not
a
developer,
I
can
still
search
for
the
search
engine.
I
don't
care
if
it's
in
a
million
places
on
github
then,
but
as
it
is
now
yeah.
C
So
before
we
get
the
new
doc
engine,
it's
going
to
be
it's
going
to
be
interesting,
but
I
don't
see
that
there's
no,
no
one's
come
to
me
and
said:
oh,
we
need
50
new
git
repos.
So
maybe
I'm
worrying
about
nothing.
A
Yeah
yeah
and
it
would
stage-
and
that's
it
and
part
of
me
too.
Of
course,
those
of
you
who
know
me
I'm
such
an
old-school
unit,
unix
person-
it's
just
disgusting,
but
I
like
the
reference
page
that
has
differences
between
versions
and
see
also
at
the
bottoms,
and
I
don't
know
that
we
want
that
in
the
readme
files
in
the
so
yeah.
A
A
lot
of
me
likes
the
idea
and,
of
course,
even
in
the
worst
case
well,
and
what
we're
what
I
think
we're
talking
about
doing
for
so
like
cloud
events,
I
may
draft
this
up
in
the
next
couple
of
days
and
we
can
look
at
it
for
the
time
being,
I'm
going
to
copy
paste
that
into
the
reference
page,
but
at
the
bottom
of
the
c.
Also,
I
will
include
a
link
to
where
and
say
something.
You
know
that
this
is
a
copy
using
the
the
the
single
source
of
truth
is
over
here.
C
It
does
I'm
also
sort
of
wondering
what
what
we're
dropping,
because
it
sounds
like
in
the
new
like
the
new
docs
engine,
is
going
to
be
adding
a
lot
of
stuff.
And
I
just
wonder
what
what
what
we
should
actually
drop
from
the
website
and
what
does
really
genuinely
live
in
a
git
repo,
hidden
away
off
to
the
side.
A
Which
is
yeah
well
yeah,
then,
especially,
if
you
look
at
the
whole
website.
Well,
we
all
know
what
I
want
to
kill
out
of
there,
but
but
yeah
something
right
now
having
the
and
then
the
you
know
the
engineers
of
oleg
in
particular,
you
know,
but
everything
you
know
it's
in
the
get
repo
there
we've
got
so
freaking
many
get
repos.
C
A
A
And
then
because
the
one
other
thing
now
in
this
see
part
of
me
thinks
that
yeah
that
a
high
that
the
hybrid
reference
pages
would
be
best,
though,
because,
like
the
differences
between
versions
and
like
for
values.yaml
at
17,
that
becomes
really
important
right
now,
and
it's
actually
nicely
written
up
for
upgrade.
C
A
Right,
it's
more,
it's
well
he's
got
both
he's
got
the
text
and
then
he's
got
this.
This
was
moritz
and
I
was
like
whoa
you're,
a
serious
powerhouse
when
it
comes
to
this,
but
the
problem
with
the
now
the
problem.
On
the
other
side,
the
way
this
is
done
right.
This
was
written
when
17
was
the
hot
new
release,
and
this
is
for
upgrading
from
16
to
17..
A
Now
I
think,
when
we're
on
release,
20
or
25,
or
certainly
at
20,
it
would
be
nice
to
have
a
place
to
go
and
say
that's
everything
that
that
changed
at
17,
because
we
might
change
some
more
stuff
at
19
or
something
like
that
yeah
and
and
that
I
would
kind.
I
almost
want
to
just
take
this
whole
thing
and
put
it
into
the
differences
between
versions
and
the
values.yamo
reference
page,
but.
C
A
A
That's
kind
of
the
nice
thing
about
differences
between
versions
to
me,
it's
like
on
the
reference
page
and
it
also
because
realistically,
my
ex
I
remember
a
time
in
the
early
days
of
unix
when
there
were
the
prevailing
thought
was
all
of
those
reference
pages
should
be
exactly
for
that
release
and
people
who
were
running
hybrid
organizations
that
had
like
five
different
releases
running
we're
going
to
keep
five
different
sets
of
man
pages.
They
were
all
printed
then
around
and
they
were
going
to
look
at
the
right
one
for
each
one.
A
Well,
that
never
happened.
Everybody
had
one
set
and
they
looked
at
it.
That
was
close
enough
and
then
every
once
in
a
while
they'd
get
in
a
lot
of
trouble,
trying
to
use
something
that
wasn't
supported
on
that
particular
release,
and
that
was
when
we
started
coming
up
with
the
differences
between
versions.
It
was
nice
to
see
that
most
of
this
is
the
same,
for
whatever
version
you've
got
and
here's
where
the
differences
are
so
that
that
and
the
fact
that
I
you
know,
studied
history.
A
That's
always
my
view,
but
I
I
kind
of
think
it's
legitimate,
we'll
you
know
we'll
have
as
we
go
forward.
You
know
now.
It
may
be
that
when
we're
at
release
30,
this
won't
matter
anymore,
but
you
know
someplace.
I
just
read,
I
don't
know
one
of
the
guides.
I
saw
something
and
oh
yeah,
it's
I
think
the
the
separate
execute
plane
executor
plane
is
in
is
new
in
release
eight
and
it's
like
okay,
we're
on
18.
I
don't
really
care
about
that
anymore.
A
C
A
Points,
I
might
hold
differences
between
versions.
Just
the
other
thing
is,
is
that
somebody
I
I've
been
using
it
for
a
while.
I
know
what
it
is
and
I'm
looking
for
information
about
continuous
dash
delivery
or
something
so
I
google
that-
and
I
get
the
hit-
and
I
see
that
it
was
changed
at
this
point,
so
I
might
give
one
extra
version
for
different
yeah,
but
I
I
think
that's
the
general.
I
think
you're
right.
A
A
This
has
been
fun.
Okay,
I
should
actually
I'm
going
to
stop
sharing.
I
don't
know
how
people
do
this
stuff.
I
don't
have
enough
things.
I
can
do,
let's
see
so
well
I'll
update
the
notes
for
the
minutes
later,
but
so
we
have
a
short-term
path
full
on
some
of
these
reference
pages,
and
we
can
do
that.
We
can
look
at
you
know
anything
we
do
is
better
than
what
we've
currently
got
right
and
we
can
look
at
it
and
sometimes
when
you
look
at
something
you
see-
oh
no,
that's
not
right.
C
Yeah,
I'm
very
interested
in
in
those
videos
tp
on-
let's,
let's
definitely
keep
in
touch
on
that
and
what
will
what?
What
I
think
I
need
to
do.
I
don't
know
about
anyone
else-
is
try
and
figure
out
the
the
topics
for
the
video.
Basically,
you
know
I'm
a
brand
new
captain
user.
C
A
Although
I
don't
know,
but
then,
where
do
we
jump
to,
I
mean
there's
a
point
where
I
just
want
the
reference
material,
because
I
know
what
I'm
doing,
but
it
seems
to
me,
okay
for
the
slis
and
slos
you're,
going
to
start
out
with
those
that,
like
the
slis
that
map
directly
to
the
queries
that
you've
got
coming
from
your
observability.
A
C
A
C
C
I
think
you
can
get
a
lot
more
in
docs
than
you
ever
will
in
a
video,
but
the
video
has
a
very
good
place
in
that
there's
a
million
tools
out
there
and
I've
only
got
five
minutes.
I
just
want
a
very
quick
overview
of
how
to
do
this
thing.
I'll
dig
into
the
details
later
in
the
docs,
but
I
just
want
to
get
something.
A
You
know
and
has
like
the
high
points
we
do
this,
and
you
know
the
doc
has
more
the
other
thing
that
that
I
will
say:
yeah.
Well,
I'm
more
of
a
I'm
less
visual
than
most
probably
of
our
cus
of
our
users
are
but
we've
all.
Actually,
we've
already
got
this
issue
with
our
end-to-end
tutorial.
I
go
through
that
and
then
later
on,
I'm
doing
something
it's
like.
Oh,
there
was
something
in
that
video
about
that,
and
I
want
to
look
that
up
well.
A
C
Yeah
yeah,
I
agree.
Maybe
at
the
top
of
the
page
we
have
the
the
short
sharp
overview
that
had,
and
maybe
we
self-impose
a
time
limit
of
like
four
minutes
or
five
minutes
or
whatever
it
is
so
so
it
doesn't
get
waffly
and
then
at
the
end
of
the
video
you
just
say.
Well,
if
you
need
more
go
to
the
docs
which
are
below
and
then
they
can
be
really
as
verbose
as
you
like.
You've
already
got
the
mental
image
of
what
you're
trying
to
achieve.
A
And
the
other
thing
to
work
too
is
videos,
verses
or
videos
and
killer
coda
tutorials,
because
I
also
think
that
most
of
us
learn
better
when
we
actually
have
to
do
something.
I
can
sit
and
watch
the
best
demo
in
the
world.
It's
like
I've
got
that
and
then
I
turn
around
to
my
system
and
I'm
like
what
so
being
able
to
actually
do
it
and
or
maybe
have
you
know
the
tutorial
where
you
do
it
in
the
video
that
runs
through
the
tutorial
and
you
see
how
they
did
it.
A
So
if
you
get
in
trouble,
you've
got
that
so
yeah,
it's
you
know
so.
C
The
trailers
really
is
what
they
are
they're
short
sharp
teasers
of
of
this
is
what
you
could
be
doing
right
right.
You
know
it's,
it's
not
every
nth
detail
of
of
everything
that
you
could
do
just
like.
Well,
you,
wouldn't
you
wouldn't
have
the
the
entire
film,
but
it's
enough
to
get
someone
hooked
and
go
well
yeah.
Okay.
I
want
to
invest
a
bit
more
time
in
that
right.
C
C
C
A
Right
yeah,
I
love
well
christian-
did
that
one
for
setting
up
the
development
environment
a
little
while
ago
and
I
thought
they
were,
he
did
and
he
did
two
10-minute
ones.
I
think
I
think
the
first
one
was
almost
straight
setting
up
kept
and
then
the
second
one
was
the
developer
tools,
but
I'm
sure
by
now
that
was
what
three
months
ago,
it's
probably
hopelessly
obsolete.
C
B
I
think
I'm
here
more
as
a
contributor
than
a
user,
so
yeah,
okay,.
B
B
B
B
Yeah,
I
think
some
of
the
things
you
mentioned
like
putting
in
the
dog
section.
I
think
I
can
walk
on
some
of
those,
but
then
again,
I'm
back
here
after
a
month
or
two,
so
I
have
to
catch
up
a
lot.
You
know
because
a
lot
of
progress
has
been
made
so
yeah.
I
think
I
will
look
into
it.
A
Right,
yeah,
good
good
and
that's
yeah.
That's
that's
one
of
the
things
you
know
and-
and
you
do
like
for
any
of
this
stuff-
it's
like
you
know.
I
have
this
big
picture
where
we're
going,
but
you
chunk
it
down
into
little
pieces.
So
maybe
you'll
work
on
something
for
three
or
four
weeks
and
then
something
else
will
come
along.
Well,
you'll
have
a
little
bit
of
it
done.
You
will
move.
We've
moved
forward
on
that.
Maybe
you'll
go
off
and
do
something
else
then
so
yeah.
A
C
Sorry,
I'm
I'm
gonna
have
to
drop,
but
a
really
good
call.