►
From YouTube: Keptn Refinement Meeting - April 4, 2023
Description
Meeting notes: https://docs.google.com/document/d/10Fig1eYFZ9iQFSYWkz0c4eTwzgJiPtQI5IsczbvLsuE/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
B
Yes,
I
just
took
a
look
because
I
took
a
look
at
the
the
captain
specific
and
the
Google
Google
rating.
If
they're
I
wanted
to
check,
if
there
are
any
errors
regarding
sitemap
or
something
like
that
for
the
captain
documentation
or
any
pages
with
some
just
simply,
some
kind
of
Errors
which
can
occur,
occur
and
I
found
out
that
I
checked
the
file
and
the
Google
verification,
the
verification
as
the
file
we
used
for
verification
Within.
B
But
the
first
problem
is
I
did
not
find
any
kind
of
Entry
regarding
lifecycle.cap.sh
within
the
Google
search
console
and
then
I
checked
the
verification
file
we
have
within
our
repository
and
I
saw
that
it's
actually
the
verification
file
from
captain.sh,
and
this
will
not
work.
So
in
the
end
it's
a
file.
We
do
not
need
it
either.
We
do
not
need
at
all
or
we.
B
If
we
want
to
have
search
console,
we
need
to
adapt
the
verification
approach,
either
with
a
new
file
which
is
cluttered
within
the
repository
or
a
DNS
entry
or
a
text
DNS
entry,
and
then
this
should
also
work.
The
question
is:
do
we
want
to
have
that
as
more
it
already
wrote?
We
do
know,
he
thinks
we
do
not
need
it
and
how
do
we
want
to
track?
So
how
do
we
want
to
do?
The
verification
is
most
likely.
The
question.
B
Now
you
see
as
a
what
what
as
a
I
can
only
speak
from
the
things
I
did
with
captain.github.io.
It
displays
error
in
the
sitemap
XML.
It
displays
error
when
there
are
canonical
tags.
Etc
are
not
properly
linked
and,
for
example,
I
use
this
to
take
a
look
at
all
the
kind
of
all
the
user
pages
and
taking
a
look.
What
is
what
what
gets
created
predecence
within
googly,
ranking
Etc
based
on
canonical
worlds
Etc?
B
Scarf
only
tricks
where
people
are
coming
from,
whereas
Google
the
Google
search
console,
also
shows
you.
The
errors
in
the
sitemap
XML
shows
you.
If
you
like,
I,
can
shortly
show
you
what
we
see
we've
kept
with
the
captain
web
page
and
I
share
my
screen
shortly.
B
B
So
what
we
I
don't
know,
not
even
that,
so
what
we
actually
do
see
is
so
it's
also
about
performance,
webwipers
and
all
the
usual
things.
So,
first
of
all,
you
get
the
the
performance
index
how
the
web
page
is
performing
regarding
the
impression
and
the
page
experience
for
the
for
the
users.
What
are
good
Pages?
What
are
bad
pages,
so
you
can
theoretically
improve
your
SEO,
it's
not
as
important,
but
it
also
gives
you
an
overview
over
the
sitemap
and
the
most
important
part
is
which
pages
are
found,
which
Pages
have
a
have?
B
C
So
I
only
noticed
that
we
have
that
by
accident
for
the
cap,
page
and
I,
don't
know
if
that
was
ever
really
used,
except
for
Simon.
Now.
A
C
Okay,
yeah
I
mean,
if
there's
a
use
for
us,
then
of
course,
but
then
we
should
also
make
it
fully
transparent
and
add
maintainers
and
blind.
B
A
B
B
But
this
is
also.
This
is
also
something
which,
which
I
totally
understand
from
a
perspective,
that
all
lifecycle,
toolkit
maintainers,
should
be
part.
But
there
is,
this
thing
is
I
would
say
everybody
can
be
part,
but
they
should
mention
themselves
and
write
me.
B
A
A
Any
any
it's
small
enough,
so
it's
not
too
big
that
we
need
to
split
or
anything
else
so
on
which
we
will
focus
on
improving
our
research,
our
documentation
actually.
C
A
C
A
The
second
ticket
that
we
have
to
refine
is
the
following
one
for
the
metric
server,
because
we
have
currently
a
limitation.
We
can
only
support
a
single
provider
if
you
want
to
use
multiple
Prometheus
instances,
because
I
have
one
Prometheus
that
watches
my
Dev
environment,
one
for
my
staging
environment
and
I
want
to
I,
don't
know
to
evaluate
metrics
before
the
promotion
in
staging
is
the
infrastructure
healthy
enough,
so
I
can
trigger
the
promotion
or
not.
I
cannot
because
I
can
only
look
at
a
single
Prometheus
instance
at
a
time.
A
Now,
let's
recall
things:
I
didn't
prepare.
Oh
yes,
so
the
captain
metric
should
have
a
different
field.
Now,
inside
spec
provider
we
set
the
name
we
should
have
the
type,
so
we
know
which
type
is
it
so
behind
the
scene,
the
captain
metric
controller
knows
which
provider
implementation
should
be
used,
and
this
one
should
be
one
of
the
following
that
we
Implement
datadoc
Prometheus
dynatrase.
E
C
A
C
A
So
what
I
was
saying
is
I
see
this
input
very
variable
that
we
should
have
within
the
metric
provider,
because
this
way
we
can
have
a
split
between
responsibility
of
a
developer.
That
says:
I
want
to
use
this
metric
and
then
from
the
platform
engineer
that
says
you
have
this
metrics
available
for
doing
your
scaling
or
whatsoever.
E
D
D
I
would
have
a
question:
will
we
kinda.
F
G
D
D
E
D
D
A
G
F
D
It
is
sorry
yeah,
it
is
a
breaking
change,
but
we
basically
can
do
it
without
losing
information
or
whatever
it's.