►
From YouTube: Keptn Community & Developer Meeting - March 11th, 2021
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
A
A
I'll
go
ahead
and
do
the
same
and
then
let's
get
started
so
there
were
actually
no
questions
or
discussions.
So
we
have
to
verify
from
last
meeting
if
we
missed
something,
please
let
us
know
and
also,
I
think,
right
now,
a
lot
of
discussions
and
the
questions.
Answers
are
actually
done
in
the
slack
channel
so,
but
if
there
is
something
we
want
to
discuss
in
this
meeting,
just
bring
it
up
and
add
it
to
their
channel.
A
We
already
discussed
this
last
week
a
little
bit.
I
just
want
to
highlight
this
again,
so
we
have
a
little
bit
of
a
new,
let's
say:
cadence,
we
are
keeping
the
community
focused
content
each
every
other
week
and
we
also
have
kind
of
feature,
presentations
and
more
presentations
from
the
captain,
maintainers
and
captain
core
team
on
the
weeks
in
between
so
actually
we're,
starting
today
with
features,
I
think,
related
to
captain
dot
8.1
already
and
next
week.
A
We
will
then
have
more
community
featured
content
and
we
also
keep
a
backlog
of
this.
So
if
you
want
to
present
something
here
in
the
captain
community
meeting,
please
feel
free
to
edit
up
there
in
the
in
the
meeting
in
our
pr
backlog.
So
we
actually
have
josh
already
lined
up
for
next
week
and
we
are
happy
to
to
host
you
also
here
to
presenting
this
plus
contributions
to
captain
another
thing
I
want
to
highlight.
A
Last
week,
captain
xero.8
has
been
released
and
it's
a
really
great
new
version,
but
that
also
means
please
go
ahead
and
upgrade
your
captain
installations,
also,
if
you're
developing
on
captain,
if
you're
riding
through
the
integrations
with
captain,
please
upgrade
your
installation.
There
are
a
couple
of
couple
of
things
that
have
changed
so
therefore,
there's
also
a
migration
guide.
A
So,
if
you're
interested
in
the
new
version
of
captain
it's
dot
8.1,
we
have
all
the
issues
that
we
are
currently
working
on
or
the
team
is
working
on
also
listed
in
in
our
planning
board.
But
actually
I
think
this
would
be
more
or
less
johanna's
responsibility
and
to
go
over
this
since
he
is
not
able
to
join
today.
I
will
just
skip
this
part.
A
B
Well
today,
I
want
to
show
you
two
pro
requests.
Both
are
related
to
our
integration
tests
and
the
adaptation
and
extension
of
those.
So,
as
you
might
know,
we
are
currently
working
on
supporting
the
capabilities
for
the
remote
execution
plane.
So
that
means
that,
for
example,
the
any
service
that
can
take
over
a
task
sequence
task
does
not
have
to
necessarily
run
within
the
same
cluster
as
the
remaining
captain
installation.
B
But
with
this
remote
execution
plane
feature
the
tasks,
executors
can
run
anywhere
and
communicate
with
captain
via
the
captain
api
and
therefore
it
also
made
sense
to
add
an
integration
test
for
that,
and
that
is
what
we've
done
here.
So
basically,
what
happens
here?
We
have
this
new
test
step
within
our
integration
test,
workflow,
where
we
installed
a
remote
execution
plane,
and
in
that
case
we
take
the
helm
service
and
the
jmeter
service,
which
now
have
their
own
helm,
charts
that
are
being
delivered
as
part
of
the
release.
B
What
happens
then
is
we
are
using
those
two
services
with
within
our
previous
continuous
delivery
integration
test,
which
is
the
test
where
we
basically
deploy
the
cards
and
the
cards.
The
e-service
first
to
the
dev
stage,
then
to
the
staging
stage
and
then
to
the
production
stage
or
well,
not
the
production
stage
anymore,
but
more
on
that
in
the
next
issue.
But
first
I
would
like
to
ask
if
there
are.
A
B
All
right,
if
there
are
no
further
questions,
I
would
like
to
continue
with
the
next
issue,
which
is
also
an
integration
test,
and
in
that
case,
for
the
parallel
executes
or
multiple
parallel
stage
execution
feature
that
has
been
introduced
in
captain
0.8
and
to
show
you
what
we
mean
with
this.
Let
me
show
you
this
example
shipyard
file.
So
this
is
the
shipyard
file
that
we
are
now
using
for
testing
the
continuous
delivery
use
case.
B
So
as
we
previously
did,
we
have
the
dev
stage
the
staging
staging
stage,
but
now,
instead
of
the
production
stage
which
we
previously
had,
we
have
now
a
production,
a
and
production
b
stage,
and
they
are
both
triggered
as
soon
as
the
delivery
sequence
in
the
here.
It
is
if
you
look
at
the
trigger
here,
there
are
both
triggered
after
the
delivery
sequence
in
the
previous
stage,
which
is
the
staging
stage,
has
been
finished.
So
that
means
that
first,
we
sequentially
deploy
to
the
dev
stage,
so
we
deploy
test,
evaluate
and
then
release.
B
Then
yeah
again
we
deploy
test,
evaluate
and
release,
and
then
this
delivery
stage
in
the
staging
stage
is
finished
and
then,
instead
of
just
triggering
one
sequence
after
that
which
we
got
two
sequences
which
are
then
executed
in
parallel,
so
there
are,
the
artifact
is
then
delivered
both
in
production
a
and
production
b
and
yeah.
Basically,
we
have
added
this
shipyard
to
the
continuous
integration
test
and
that
pretty
much
is
the
only
change
from
user
perspective
that
has
changed
for
this
use
case.
B
C
Thank
you
very
much
yeah.
I
plans
to
present
one
poor
request
today.
It's
about
showing
services
and
recent
sequence
in
the
stage
style
of
the
environment
screen
asset
table.
This
pull
request
is
still
on
a
review
and
open,
so
there
might
be
some
changes
still
coming
in,
but
yeah.
I
wanted
to
present
you
the
current
status
because
yeah
it's.
It
shows
already
a
quite
interesting
view.
C
C
If
there
was
a
problem
or
open
approval
on
this
stage
for
this
service
and
yeah,
the
wireframe
suggested
to
yeah
show
it
like
a
table
and
show
the
latest
sequence
here,
also
the
status
of
this
sequence,
either
if
it's
yeah
running
still
running
or
it
finished
successfully
or
with
a
failed
status,
and
we
also
show
the
evaluation
result
of
this
sequence
here.
Next
to
this
sequence,
details
and
of
course
the
most
interesting
part-
is
always
a
live
review.
C
So
I'm
showing
you
here
my
bridge
and
I
will
have
a
look
at
the
sock
shop
approve
and
I
will
just
trigger
here
a
delivery
so
that
something
is
happening
in
the
background.
While
I'm
showing
you
this
environment
screen,
as
you
can
see,
I
have
here
several
services
deployed
and
yeah,
because
I
don't
have
so
many
services.
C
So
here
is
a
delivery
sequence
going
on.
Let's
focus
here
on
the
stitching
stage
for
this
card
service
that
I
deployed
here.
The
delivery
is
already
finished
and
I
also
see
the
evaluation
here.
So
the
result
of
this
evaluation
can
be
also
easily
seen
when
I
click
on
this
one.
Of
course,
on
the
right
side,
the
services
are
sorted
by
importance
as
they
are
also
here.
C
So
the
latest
sequence
will
be
shown
on
top
and
that
will
be
the
sorting
for
the
services
so
that
I
can
see,
for
example,
here
there
is
an
open
approval
for
this
service
and
I
can
trigger
this
approval,
for
example,
or
also
if
there
are
problems
and
remediation
actions
running
currently
for
this
service.
It
will
be
on
top,
and
I
can
see
the
remediation
actions
that
are
going
on
at
the
moment.
A
Oh
thanks
yeah,
pretty
cool
thanks
for
this
update.
I
think
it
looks
really
good.
Are
there
any
more
questions?
I
know
that
we're
not
a
very
big
round
today,
but
let
us
know
if
you
have
any
questions.
Also,
let
us
know
if
you
have
already
tried
the
latest
version
of
captain
and
we
are
happy
about
all
the
feedback
that
we
can,
that
we
can
get
from
the
community.
A
Actually
josh
is
going
to
present
his
contribution
in
terms
of
the
spelling
checking
bot
that
is,
or
it's
not
yet
supported
in
terms
of
a
github
action
that
is
now
integrated
also
in
capital
and
really
has
improved
the
the
captain
project
by
by
removing
some
of
our
some
of
the
typos
that
we
made
in
the
project
so
that
that's
really
appreciated,
and
we
will
see
next
week
how
he
was
developing
the
spot
and
how
he
integrated
it.
So.