►
From YouTube: Keptn Community Meeting - November 25th, 2019
Description
Keptn 0.6.0.beta
Discussion of PR: Add description for remediation strategy
PR: https://github.com/keptn/spec/pull/11
Discussion of PR: Proposal: Extend shipyard with approval
PR: https://github.com/keptn/spec/pull/3
Discussion of PR: Adding labels to the start-evaluation event
PR: https://github.com/keptn/spec/pull/10
A
A
Oh,
if
not
release
it
was,
it
has
been
released
last
Friday
and
we
want
to
just
touch
a
little
bit
on
what
you
can
expect,
what
to
use
it
and
what
you
can
receive,
who
will
receive
in
the
next
couple
of
days
from
their
team.
After
that,
we
are
going
to
discuss
three
pull
requests
that
are
currently
open
up
for
the
captain's
back
and
yeah.
When
we
are
here,
we
will
talk
about
those
I'm
changes
and
will
ask
the
community
for
additional
feedback.
B
A
A
A
There
you
can
find
ya
a
summary
of
all
the
changes
we
made
and
also
a
short
summary
of
the
focus
of
today's
release
itself,
as
I
said,
and
it's
all
about
kept
quality
gates.
This
means
that
you
can
now
use
this
feature
as
a
standalone
feature
within
your
continuous
integration
or
continuous
delivery
pipelines,
and
this
gives
flexibility
to
ya
know.
A
This
allows
you
to
enrich
your
city
pipelines
with
the
concept
of
quality
--get
and
for
configuring,
this
quality
gate
and
you
have
to
come
up
with
a
service
level,
objective
file
and
service
level
indicators,
but
we
will
support
or
we
will
help
you
with
that,
because
a
specification
of
SLO
and
SLI
is
available
in
the
code.
Captain
aspect
repository.
A
One
very
important
note
to
mention
is
that
the
very
famous
speedometer
service
has
been
exchanged
by
another
service.
It's
called
the
lighthouse
service
now
and
this
lighthouse
service
is
taking
over
the
responsibility
of
fetching
data
from
an
external
provider
and
service
level
indicator
provider.
Then
it
takes
the
stator.
Does
the
test
or
the
aberration
and
then
returns
the
evaluation
result
to
them
to
the
recipient.
C
B
Can
really
define
your
service
level
objectives
which
are
afterwards
automatically
checked
by
by
the
life
of
service,
and
one
really
nice
thing.
I,
especially
like
from
the
lighthouse
services
that,
before
the
PT
meter,
must
tightly
coupled
to
the
cell
I
provided
two,
for
example,
dynaTrace
from
me
choice
and
now
in
this
release
we
decoupled
this,
and
so
we
do
not
have
to
recompile
the
lighthouse
service.
B
A
B
Here
especially
know
the
teachers
because
implemented
this,
so
Ischia
was
used
for
especially
roasting
the
traffic
between
the
cannery
and
the
primary
version
and
when
you
are
only
using
the
captain,
quality
gates
standalone.
So
you
do
not
need
this
functionality,
so
we
do
not
need
SEO
and
we
can
simply
go
home
with
some
nginx
and
then
a
simple
ingress
provided
by
communities,
and
this,
of
course,
in
another
time,
slims
down
our
footprint
and
makes
it
easier
for
customers
to
install
cap.
D
Was
a
perfect
over
here
now
we
should
hey
come
on
I
guess
I
would
have
a
question
because
looking
at
the
docks
it
says
when
I
want
to
verify
the
captain
installation
there
is
still
is
still
there.
So
is
there
an
option
where
we
can
decide
to
install
it
still
or
is
it
more
yep?
So
we
did
with
the
new
release
will
be
easier
by
default
or
not
by
default
and
in
the
dock
slave
itself,
because
it's
better,
maybe
so
not
captain.
A
Thanks
for
pointing
that
out
by
default,
we
installed
we
install
captain
as
it
was
in
in
ordered
five,
and
so
that
a
user
want
wanted
change
his
his
captain
environment,
but
you
can
now
run
the
install
command
by
specifying
the
use
case,
quality
gates.
Let
me
just
quickly
go
to
to
this
page,
where
you
can
see
that
here
you
have
now
the
option
to
use
order
to
install
captain
for
a
specific
use
case,
and
in
this
case
you
can
a
specified
quality
gates,
and
then
you
won't
installed
steel
and
you
get
them
nginx.
B
A
And
then
we
one
jump
over
to
the
first
pull
request
for
the
captain's
back.
This
pull
request
is
actually
it's
not
that.
Actually
it's
not
change,
it's
more
and
pull
request
where
we
add
missing
information,
because,
right
now
the
explanation
of
the
remediation
strategy
was
missing
in
the
specification
and
this
pull
request
at
this
description
to.
B
A
shipyard
certification
so
when
we
go
into
the
changed
files,
malaya
really,
that
is
I-
entered
descriptions
about
the
remediation
strategy.
So
you
can
remember
when
pennant
race
receives
a
problem
event
problem
open
event:
you
can
define
some
remediation
actions
and
if
you
choose
nomination
to
be
automated
for
your
production
stage,
for
example,
then
this
remediation
actions
are
executed
and
this
information
was
simply
missing
in
their
descriptions
of
of
the
shipper.
B
So
now.
This
newer
approval
strategy
allows
you
to
make
a
distinction
between
passes
and
morning,
so
you
can
choose
an
automatic
approval
strategy
for
pass
and
men
on
approval
strategy
for
morning,
and
this
was
not
possible
before
and
now
we
split
this
to
prove
this
to
emulation
results,
and
now
you
have
to
complete
one
possibility
so
on
combinations
and
can
be
team
right,
and
this
is
gives.
B
E
What
about
a
quick
question?
What
about
the
case
when
it's
neither
person
of
warning,
but
it's
actually
failed?
Is
there
any
option
for
the
end-user
to
get
notified
and
still
being
able
to
push
something
out?
So,
for
instance,
you
have
an
emergency
fixer
didn't
know
you
have
to
get
out.
Maybe
the
quality
gates
have
an
issue
and
therefore
be
comes
back
with
a
failure
failure
but
at
least
having
the
option
to
say
if
it's
failed,
there's
still
a
manual
approval
step
possible
in
case
you
already
have
two.
B
So
we
decided
not
to
take
this
into
the
shipyard
file,
but
and
to
have
the
possibility
to
push
an
artifact
into
the
next
stage
if
it's
really
needed.
So
this
will
be
done
by
the
bridge
or
the
CLI,
but
this
does
not
need
to
be
specified
in
the
ship.
It
fine,
okay
and
the
initial
implementation,
of
course,
will
even
support
these
two
flags
or
these
two
properties,
and
then
we
can
extend
this
Eli
or
the
bridge.
A
A
Well
adhere
is
pretty
pretty
obvious
because,
let's
assume
you
are
running
or
you're
using
captain
quality
ads
feature
within
your
CSV
pipeline
and
your
Alexia
at
sea.
Deep
I
plan
yeah
has,
for
example,
a
built
number
or
I
plan
number
of
execution
number,
and
you
want
to
add
this
information
and
to
the
or
you
want
to
bring
this
information
to
captain
and
then
captain
starts
an
evaluation
text.
A
B
How
does
enable
is
exactly
it
should
look
like
maybe
can
changes.
This
is
ongoing
discussion,
so
here,
for
example,
we
defined
an
object
which
is,
of
course
the
most
general,
because
an
object
can
be
anything,
but
it
also
makes
it
probably
the
most
hardest
to
query
afterwards.
So
we
have
here
to
find
a
trade-off
between
flexibility
and
also
how
we
can
easily
clear
it
afterwards.
B
A
A
As
you
know,
each
captain
cloud
event
requires
those
elements
in
the
or
requires
those
elements
which
are
the
content
type.
The
data
block,
the
ID,
the
captain
context,
the
source,
spec
version
time
and
type,
and
in
the
data
block
data
block,
we
allow
any
provider
to
add
data
in
there
and
our
first
idea
was
to
add
an
additional
property
right
here,
but
as
we,
he
took
a
look
into
the
cloud
event
specification.
A
A
A
C
Meaning
right
so
you
could
apply,
like
you
say
your
object,
but
your
value
could
be
multiple
labels,
as
opposed
to
just
a
sing.
You
know
instead
of
a
list
of
individual
labels
and
keys,
and
you
mean
dear
comma,
separated
yeah
I
mean
comma
separated,
be
fine
as
well
I.
Just
it
just
seems
that
the
if
you
have
to,
if
you
create
an
object,
then
you
create
multiple
labels
in
that
object
like
individual.
You
know
at
key
value
pairs
at
that
object.
C
It,
like
you,
had
listed
here
like
test
ID
builder,
that
your
day,
your
career,
I,
guess
technically
you're
overloading
it
here,
but
I
don't
know
just
maybe
it's
just
the
part.
Maybe
I
just
read
it
in
the
way
the
format
was
it
just
I.
Think
it's
fine!
You
know
it's
fine,
I'm,
sorry,
I
didn't
realize
I
didn't
realize
you
were
kind
of
already
doing
that
so
hello
you're
doing
a
separate
object,
but
that's
that's.