►
From YouTube: Keptn Community Meeting - May 7th, 2020
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
A
You're
welcome
everyone
to
the
next
captain
community
meeting,
starting
today
with
a
little
bit
of
a
new
format.
So
we
have
all
the
captain
folks.
Here
we
have
the
great
captain
community,
also
joining
here
and
starting
from
today
we
will
have
this
community
meeting
more
as
a
as
an
open
platform.
Let's
say
to
really
discuss
PR
s,
to
discuss
issues,
to
discuss
the
roadmap,
to
a
very
open
discussions
here
and
not
so
much
as
presenting
content
from
the
captain
team
as
like,
as
we
call
it
an
educational
content
in
the
form
of
the
webinar.
A
So
we
will
have
dedicated
webinar
sessions
where
you
can
learn
from
from
Captain
adopters,
captain
customers
and
other
captain
users
where
they
are
going
to
present
something,
but
in
this
kind
of
captain
community
meeting,
it's
really
a
work
meeting
where
we
discuss
on
captain
work
items
where
we
discuss
open
issues,
PRS
everything,
that's
really
developer,
related
roadmap
discussions
and
so
on
so
feel
free
to
join
us.
Also,
in
this
discussion
we
right
now
we
still
have
this
assumed
webinar,
but
I
will
allow
everyone
here
also
to
talk
so
I
will
click
through
the
attendee
list.
B
A
And
we'll
allow
everyone
to
talk,
so
if
you
want
to
raise
your
voice,
if
you
want
to
ask
questions,
feel
free
to
unmute
yourself,
if
you
just
ask
the
questions
and
for
today
what
we
have
planned
is
basically
we
try
this
new
format
the
first
time,
so
we
will
go
through
a
couple
of
noteworthy
issues
and
PRS.
We
have
a
couple
of
basically
the
core
captain
development
team.
We
have
listed
issues
here,
so
we
will
go
through
these
issues.
A
If
you
want
to
get
to
stay
up
to
date,
also
between
those
meetings,
so
this
will
be
weekly
cadence
starting
from
today.
But
if
you
want
to
stay
up
to
date
during
these
weekly
cadence,
then
please
join
our
slack
workspace
for
communication
with
the
boat
captain
community.
So
we
have
also
provided
the
link
here.
The
link
to
this
document
is
also
on
the
captain
community
site
on,
in
fact,
odd
count.
Slash
captain,
slash
community,
you
will
find
all
the
links
and
also
the
link
to
this
document.
A
We
already
have
a
couple
of
folks
running
and
they
will
also
be
allowed
to
talk
to
ask
questions
if
you
want
so
I
will
also
stop
my
sharing
and
yeah.
Let's
see
how
it
goes
for
the
first
time.
Thank
you
for
the
introduction
Union.
So
in
this
meeting
we
will
present
some
pool
requests
and
this
is
acting
like
a
review
meeting,
but
we
don't
want
to
go
into
too
much
details.
A
So
we've
compiled
a
list
of
pull
requests
for
you,
and
each
of
us
will
just
go
through
our
own
pull
requests
and
give
you
like
a
couple
of
sentences
of
what
is
happening
or
what
has
happened
for
this
pull
request,
so
the
first
one
I
want
to
show
you
is
the
community's
recommended
labels,
which
I've
opened
ready
here.
The
idea
here
was
to
adapt
our
templates
that
we
have
our
cards
microservice
in
our
captain.
A
Examples:
people
to
also
use
cuban
eaters
recommended
labels,
which
kind
of
make
it
easier
for
certain
other
applications
to
to
map
what
this
service,
what
this
Cuban
leaders
thought
is
actually
doing
so.
For
instance,
we've
added
this
cards
micro
service
as
a
component
API,
it's
managed
by
captain
and
it's
part
of
soft
shop
there's
a
couple
of
other
that
we
can
apply
and
that
should
be
applied
in
the
future
which
are
linked
up
here
and
yeah.
That's
that's
all
about
it.
A
With
this
pull
request,
the
second
pull
request
is
the
COI
Auto
documentation
which
is
available,
I.
Think
it's
it's
life
now
on
a
website
already.
This
is
just
the
deploy
preview,
but
if
you
go
to
reference
captain
CLI
commands
you
get
all
the
CLI
commands
listed
so,
for
instance,
captain
let's,
let's
go
for
the
one
that
I
actually
implement
it.
A
It's
captain
generate
docks,
so
there
we
go,
captain
generate
docks,
is
here
and
it
generates
like
a
documentation
for
this
command
and
basically,
all
that
you
can
see
here
is
auto-generated
from
what
we've
written
in
Cobra.
So
the
short
usage,
the
long
usage
examples
and
obviously
also
if
there's
a
route
command
the
commands,
the
options
that
are
inherited
from
the
route
command
and
with
that
being
said,
I'm
handed
over
to
Florian.
C
Alright
should
see
just
a
browser:
okay
I
want
to
present
two
issues.
Both
of
them
are
concerned,
configuration
service,
so
the
first
issue
I
want
to
present
this
extension
of
the
API
ratio
service.
So
previously,
that
component
has
been
used
to
manage
the
configuration
as
an
edifice
of
our
camping
projects.
So
that
means
it
was
responsible
to
manage
the
git
repository,
but
on
step
on
figuration,
but
recently,
especially
through
the
introduction
of
the
new
bridge.
C
If
I
better,
not
and
to
get
the
complete
status
of
a
project,
we
had
to
send
a
lot
of
requests
to
the
configuration
service
missplay
that
in
the
bridge
now
we
have
extended
the
endpoints
for
some
of
the
projects,
so,
instead
of
just
receiving
just
a
list
of
a
list
of
the
names
of
the
projects
that
are
currently
in
your
head,
classy
I'll
get
a
full-fledged
overview
with
for
each
project
to
get
still
the
name.
Then.
C
Additionally,
the
list
of
stages
within
this
project
and
also
the
services
put
in
each
stage
for
each
service.
You
get
currently
deployed
image
and
the
last
event
types
for
that
service
example,
a
last
configuration
change,
last
deployment,
divination
done,
etc,
and
and
then
we
want
to
go
into
too
much
detail
here.
But
the
can
of
course,
view
example
payloads
for
those
endpoints
in
this
issue
and
also
for
each
issue.
We
have
the
or
we're
now
going
to
link
the
pull
request,
so
you
can
have
a
closer
look
at
that
code.
C
C
C
C
B
Features
in
the
bridge,
I
will
start
with
the
heat
map
long
list,
actually
that's
a
fix
of
an
issue
we
had
when
you
have
a
long
list
of
SL
ice.
In
that
case,
or
in
this
example,
we
had
more
than
100
SL
ice
in
the
breakdown
and
there
we
had
a
issue
with
the
list
and
also
an
issue
with
the
heat
map
itself.
When
too
many
results
were
in
there,
we
had
issue
that
yeah
it.
B
B
Yeah
and
the
second
one
is
the
Jason
payload
visualization,
which
was
very
prominent
in
the
old
version.
We
had
one
big
tile
for
each
trace
in
our
event
list
and
when
you
clicked
anywhere
on
this
tile,
that
the
even
payload
expanded,
and
since
that
was
not
always
that
the
needed
use
case,
we
changed
that
to
have
a
dedicated
button.
In
the
view
when
you
click
on
this
button.
Next
to
the
timestamp,
then
model
dialog
is
opened
with
the
JSON
payload.
F
I've
implemented
new
option
in
the
installer,
which
is
called
now
ingress
insert
option,
and
you
have
three
possibilities:
either
to
reuse
nginx
or
to
stop
if
it
is
already
installed
or
to
override
it,
and
this
flag
here
in
the
insulin,
is
still
hidden,
as
as
it
is,
as
the
check
is
not
yet
really
mature.
Basically,
we
only
are
checking
whether
there
is
already
a
namespace
called
nginx
ingress
engine
X,
and
if
it
is
the
case,
for
example,
we
can
reuse
the
installer
and
create
the
Cuban
ETS
ingress.
F
World
cube
CTL
is
pointing
to
and
then
I'm
retrieving
all
kind
of
communities
made
metadata
like
config
maps,
secrets
and
so
on.
But
of
course,
I
do
not
collect
the
content
of
Secrets
just
made
a
secret
is
available
or
not.
We
can
have
a
look
afterwards
and
we
do
this
for
the
captain
namespace
and
also
for
the
captain
data
store
namespace.
As
we
can
see
here,
you.
F
Okay,
this
support
card
is
not
available
here
and
yeah.
We
warn
you
that
it
potentially
contains
sensitive
data,
of
course,
but,
as
already
said,
we
are
not
on
reading
any
secrets,
and
we
also
point
you
to
our
health
slack
channel,
where
you
can
ask
only
a
question
so
now,
let's
have
a
look
into
should
knock
now
into
this
archive,
which
I
generated.
F
For
example,
yeah
I'm
running
on
a
dominating
system
I
have
the
saliva
version
0.62,
the
API
was
reachable
I
have
one
project
which
is
called
sock
shop,
which
contains
a
single
stage
hardening,
but
no
services
yet
and
my
kept
domain
missus
girl.
Furthermore,
to
this
knitted
data,
I'm
collecting
all
kinds
of
logs,
for
example,
let's
have
a
look
into
the
into
the
logs
of
the
API
service,
and
here
it
is
I
only
did
a
create
project
and
a
create
service,
and
with
this
functionality,
mr.
F
D
D
There
should
be
more
information
when
it
comes
to
an
error
in
the
configuration
service.
What
we
saw
is
that
there
were
a
couple
of
scenarios
will
get
was
not
available
or
git
repository
was
not
initialized
and
so
on,
and
those
situations
resulted
in
broken
projects
and
it
was
really
difficult
to
to
figure
out
what
happened
and
for
making
life
easier.
We
added
a
couple
of
log
messages
to
the
configuration
service
and
also
provided
now
more
context.
Information.
D
I
will
continue
with
my
second
issue,
and
this
was
focused
on
providing
documentation
for
the
captain
bridge.
What
I
did
was
I
explained
the
feature
to
expose
the
bridge
and
to
lock
it
down.
This
is
the
opposite
of
exposing
the
bridge.
What
you
have
to
do
is
just
run
the
command
captain
configure
bridge
action
equals
expose.
Then
you
can
expose
the
bridge
and
the
other
way
around
is
just
by
specifying
the
action
lock
down.
D
D
A
Just
for
sorry
for
interrupting,
but
maybe
we
have
to
explain
why
we
need
the
basic
off
for
the
captain's
bridge.
I
think
we
have
not
shown
this
yet.
But
there
was
a
sneak
preview
when
you
scroll
over
the
documentation,
because
it's
now
also
available
to
expose
the
captain's
bridge
via
the
captain's
Eli.
So
if
you're
already
familiar
with
captain,
then
you
know
that
previously,
our
preferred
way
was
to
basically
do
the
huge
TTL
port
forward
to
get
access
to
your
captain's
bridge
or
to
use
one
of
our
shell
scripts,
where
we
just
yeah.
A
Both
ways
are
possible
and
but
if
we
recommend
you
to
set
up
basic
authentication
when
you
expose
the
bridge
so
that
the
bridge
is
not
shown
publicly
without
authentication,
but
you
can
provide
your
own
username
and
password.
So
it's
kind
of
its
security
in
a
basic
way
and
it's
not
exposed
completely
public
yep.
D
Thanks
for
the
clarification
now,
maybe
was
too
fast
scrolling
over
but
yeah.
We
now
provide
this
feature
and
when
you
do
captain
expose
bridge,
then
you
get
a
warning
that
you
should
enable
basic
authentication,
and
this
warning
directs
you
to
this
documentation
where
you
can
yeah
enable
or
disable
authentication
all
right
yeah.
D
A
D
Now
see
the
screen
throw
clip
yes,
okay,
yeah
bottom
month
ago,
I
showed
you
this
picture.
Where
I
talked
about
the
features
and
building
blocks.
For
the
cap
note
at
7:00
and
release,
we
still
are
heading
towards
this
direction.
Those
five
building
blocks
are
on
our
roadmap
and
we
are
working
on
that.
D
I
also
wrote
the
blog
post
about
this
captain
release
about
odor
at
7:00,
just
go
to
medium
and
to
the
captain
publications,
and
they
will
find
my
blog
post,
where
I
have
written
down
all
these
five
building
blocks
and
explained
them
all
so,
based
on
a
couple
of
examples,
and
that's
that's
not
pretty
cool,
because
I
have
to
honor
to
announce
that
captain
ordered
602
is
available.
He
released
it
about
an
hour
ago.
D
D
Okay,
then,
let's
have
a
look
on.
What's
done
done
for
captain
ordered
seven
is
the
topic
and
the
building
block
around
exposing
the
bridge
and
the
helm
upgrade.
There
is
one
task
remaining
for
the
captain.
Hoffman
proposal,
10
and
also
one
is
related
to
the
captain
core
and
one
is
related
to
the
captain's
bridge
and
the
focus
of
the
captain
core
team
for
the
next
two
weeks
will
be
mainly
on
the
use
case
around
manual
approving
deployment.
D
I
will
on
a
couple
and
in
about
two
or
three
slides
it
will
explain
and
then
what's
what's
the
topic
of
that
and
after
that,
after
the
manual
approval
use
case,
we
will
go
in
the
direction
of
providing
better
capabilities
for
the
self-healing
use
case,
but
this
status
is
still
backlog,
refinement
all
right.
What's
missing
there,
what's
missing
for
the
captain,
Hoffman
proposal
10
as
Florian
showed
us.
The
end
points
are
available.
D
All
the
end
points
for
getting
the
project
stage
and
service
are
there,
but
what's
missing
is
the
part
in
the
captain
CLI
and
this
implementation
is
still
open
to
do
and
what
you
should
be
possible.
Then
it's
just
typing
captain
get
project
and
you
will
get
all
the
information
that
Florian
showed
us
in
his
pull
request
directly
in
the
CLI.
The
same
is
true
for
the
services
and
the
stages.
D
All
right,
then,
let
me
jump
over
to
the
use
case
of
the
manual
approval
of
a
deployment,
just
a
quick,
wrap-up
or
reminder
of
what
is
it
about
in
Captain
ordered
six.
A
deployment
is
automatically
promoted
from
one
stage
to
the
next
one
and
folks
out
there.
They
told
us
that
this
should
not
be
the
case,
especially
when
it
comes
to
production
deployment
there.
You
want
to
have
a
person
in
place
that
takes
care
of
approving
a
deployment
or
declining
it,
and
this
is
the
use
case.
D
D
There
explain
how
you
can
use
this,
this
property
yep
to
configure
an
approval
based
on
an
evaluation
result
or
use
it
as
a
hard
stop
like
for
a
production
environment
where
you
want
to
have
an
approval,
regardless
of
the
quality,
and
this
use
case,
broken
down
into
its
issues
and
tasks
is
shown
here
in
total.
There
are
seven
tasks
to
do,
but
in
in
a
couple
of
minutes
we
will
go
through
those
tasks
and
discuss
them
in
more
details.
D
A
D
If,
thanks
for
the
reminder,
I'm
done
in
about
30
seconds,
because
what
I
want
to
show
you
is
also,
the
bridge
makes
an
evolution
step
and
the
evolution
step
is
from
a
bridge
that
just
shows
information
into
a
bridge
that
can
be
used
for
triggering
things
and
therefore
we
need
this
environment
screen
and
also
for
implementing
this
screen.
I
have
broken
down
this
user
story
into
four
tasks.
D
A
Thanks
for
the
segue,
so
we
have
a
lot
of
things
to
do.
Obviously,
but
why
are
we
actually
telling
you
this?
Because
we
do
you
see
the
opportunity
for
you
guys
for
everyone
that
is
listening
in
and
joining
in
to
help
us?
So
Johannes
has
shown
us
something
on
the
roadmap,
but
I
just
want
to
give
you
a
quick
reminder
that
there
is
also
things
that
are
not
on
a
roadmap
or
not
necessarily
on
a
roadmap
that
everyone
can
help
with.
So,
if
you're
a
beginner,
we
have
a
huge
huge.
A
We
have
a
list
of
good
first
issues
that
we
believe
are
that
you
should
be
able
to
do
without
having
too
much
knowledge
about
the
source
code
or
that
help
you
to
get
some
knowledge
of
the
source
code,
and
we
also
have
some
issues
labeled
with
Help
Wanted.
In
addition
to
that,
there's
not
too
many
of
the
Help
Wanted
one,
because
these
are
issues
where
we
think
you
need
a
little
bit
more
knowledge,
obviously,
but
they
should
still
be
doable
if
you
have
some
knowledge
of
the
project.
A
That
being
said,
those
issues
that
the
good
first
ones
and
the
Help
Wanted
once
they
are
always
available.
Please
approach
us:
why
a
slack
or
directly
in
assume
or
any
other
way
that
you
can
think
of
if
you
want
to
tackle
one
of
those
issues
and
we
can
assign
it
to
you
and
we
can
help
you
if
you
have
any
questions.
Obviously,
all
right
with
that
I
will
go
to
the
working
items.
A
We
have
our
Kanban
board
here
with
working
items.
Basically
we're
organized
in
backlog
items
that
we're
going
to
talk
about
today,
assigned
items,
that's
basically
as
soon
as
we
have
something
here
assigned
to
someone
it
moves
to
here
in
progress.
Don't
need
to
explain
it.
I
guess
and
ready
for
review
and
Dan
should
be
also
self-explanatory,
but
that
kind
of
shows
our
current
work
that
we're
doing,
and
it
also
shows
the
work
that
we
want
to
do
or
that
we
believe
that
should
be
done
in
the
next
couple
of
days.
A
A
A
D
The
next
issue
is
about
as
an
already
mention
is
about
implementing
the
get
endpoints
in
the
CLI,
in
other
words,
providing
the
CLI
commands
to
get
the
project
stage
service
when
Christian,
when
I'm
gonna
click.
Can
you
click
on
the
issue?
Please,
because
here
we
have
written
down
all
the
commands
that
should
be
implemented,
and
when
you
go
further
down,
you
will
also
get
the
expected
output
or
you
see
the
expected
output
of
each
command.
They
get
yeah.
D
When
you
stay
here,
please,
when
you
do
a
cap
and
get
projects,
you
get
a
list
of
all
the
project
and
there
you
get
the
name
and
the
creation
date
of
the
project.
The
same
is
true:
when
you
say
just
cap
and
get
project
XY
set
or
in
this
example,
sock
shopped
and
you
just
get
the
name
and
the
creation
date
of
this
project,
and
when
you
do
a
cap
and
get
projects
or
shop
minus
minus
output
equals
llamo.
D
A
D
A
E
F
D
B
D
A
B
E
A
A
A
There
we
go.
The
next
issue
is
related
to
captain's
bridge,
so
with
all
the
API
endpoints
that
Florian
has
shown
you
and
the
output
that
Johannes
has
shown
you
basically
now.
We
also
want
to
make
use
of
these
API
endpoints
in
captain's
bridge.
Right
now,
captain's
bridge
has
implemented
some
of
these
endpoints
in
another
way,
directly
accessing
the
configuration
service,
etc,
and
actually
with
that
pull
request.
A
So
if
that
task,
we
want
to
make
it
easier
within
captain's
bridge
to
just
reuse
the
existing
public
API
that
we
have
for
clearing
a
list
of
projects,
stages
and
services.
I
think
there
is
not
much
else
here
other
than
that
information.
It's
also
linked
to
the
other
issue
where
we
have
some
details
about
the
API
calls
other
than
that.
Obviously
we
have
a
very
nicely
documented
swagger
UI
for
each
of
the
API
calls
that
should
help
in
implementing
this
issue.
D
At
the
next
issues
is
also
a
good
starter.
It's
a
minor
Park
in
the
bridge
where
we
show
the
wrong
image
or
the
wrong
icon
for
a
start.
Evaluation
event,
as
you
can
see
here
in
the
screenshot,
it
shows
that
I
can,
with
the
know,
with
the
info
on
either
info
icon,
but
it
should
be
the
traffic
light
should
be
shown
there.
D
A
So,
basically,
right
now
in
captain's
bridge,
we
do
have
a
lot
of
cloud
events
that
we
are
showing
as
route
events
problem
detected
configuration
change,
deployment
finished,
but
also
service
creation
tests
finish
depending
on
on
what
your
route
event
is.
There's
a
lot
of
events
being
shown
in
here,
and
we
have
a
popular
request
now
that
we
can
fill.
That
is
because
sometimes
you
just
want
to
look
at
configuration
changes,
or
maybe
your
site,
reliability,
engineer,
and
you
just
want
to
see
the
problem
detected
messages
or
something
like
that.
A
D
A
Is
it
my
turn
again
yeah,
so
the
next
one
goes
with
our
integration
tests.
Right
now
we
have
an
integration
test
in
Travis
CI,
that's
using
the
fixed
version
of
Google
kubernetes
engine
I
believe
we're
right
now
using
1.14.
That's
what
the
issue
says.
We
want
to
extend
our
Travis
CI
tests
to
use
multiple
versions
of
Google
kubernetes,
to
also
double
check
that
we
didn't
break
any
Cuba
newest
version
support
so
like
right.
A
Now
we
support
114
and
115,
but
with
the
upcoming
0.7
release
we
also
plant-
or
at
least
we
want
to
investigate
whatever
we
support,
newer
versions
of
communities
and
that's
the
story
behind
the
issue.
Implementing
it
basically
requires
some
knowledge
about
Travis
CI,
but
other
than
that
should
be
fairly
simple.
D
And
here
you
can
see
here
an
example
of
a
ship
yacht
that
has
the
approval
strategy
configured
and
the
definition
of
tan
is
that
the
gatekeepers
service
sends
out
an
approval
trigger,
depending
on
this
configuration
and
when
you
go
a
little
bit
further
down
this,
this
table
shows
you
the
combinations,
supported
and
allowed,
and
there
should
also
be
tests
implemented,
that
you
verify
those
combinations
and
make
sure
that
the
correct
event
is
sent
out
whenever
the
shipyard
file
is
configured.
This
way.
A
A
A
Basically,
there
is
an
approval
going
on,
it
has
not
yet
been
approved
and
we
want
to
just
collect
all
of
these
events
in
a
special
collection
or
a
materialist
view
or
whatever
and
as
soon
as
a
provable
finished
event
is
received
for
such
an
approval.
We
obviously
need
to
check
if
it's
in
the
approval
triggered
and
then
remove
it
from
the
approval
triggered
collection.
D
All
right
and
allowed
to
retrieve
all
open
approvals.
Let
me
just
oh
yeah,
okay,
okay,
it's
it's
about
implementing
the
endpoint
that
allows
you
to
fetch
all
the
open
approval
events
from
the
configuration
service.
In
other
words,
this
task
has
dependency
to
the
previous
on
task,
because
when
the
table
is
there
and
the
collection
is
there
that
holds
all
the
open
approvals,
then
the
endpoint
should
be
implemented
on
top.
That
allows
you
to
query
those
yep
and
then
going
further.
D
C
A
You
right,
how
are
we
in
time
I
think
we
have
nine
minutes
left.
Should
we
go
on
yeah,
so
the
next
one
is
johannes
already
mentioned
they
follow
up
basically,
and
it
also
means
that
we
need
to
change
the
implementation,
indicate
keeper
and
react
on
an
approval,
finished
event
that
then,
since
the
configuration
changed
event
for
the
current
stage,
so
right
now,
this
configuration
changed.
Event
is
automatically
sent
as
soon
as
the
evaluation
in
the
current
stage
has
finished
successfully.
A
Now.
This
should
obviously
be
a
manual
step
in
case
that
the
manual
approval
is
activated
and
also
I,
just
see
that
T
and
E
the
definition
of
done.
We
need
to
check
that
the
image
tag
from
the
approval
finished
event
also
matches
the
corresponding
approval
triggered
event.
So
we
don't
want
people
to
allow
to
just
send
in
any
image
a
combination.
It
needs
to
be
a
combination
that
has
already
been
approved
or
where.
B
F
D
Actually,
it's
not
depending
oh
it
is
it
is.
It
is
the
final
implementation
of
the
entire
story,
because
when
we
have
the
the
end
point
to
get
all
the
open
approvals
and
when
we
have
the
feature
implemented
at
the
gate,
keeper
direct
on
an
approval
finished,
he
went
then
it
should
be
possible
to
use
the
CLI
to
do
this
and
therefore
we
need
to
introduce
two
commands.
D
A
D
A
A
So
then
we
have
another
one
for
captain's
bridge.
It
basically
is
also
we
didn't
label
it
as
a
good
first
issue,
but
if
you
have
some
knowledge
of
angular
should
be
fine.
Essentially,
we
want
to
create
a
menu
on
the
left
side,
where
we
split
the
current
view,
which
has
these
stages
and
the
services
on
one
page.
You
want
to
split
it
into
an
environment
screen
with
the
stages
and
a
services
screen
with
the
services
and
respective
cloud
events.
So
essentially
it's
just
splitting
one
screen
into
two
screens
and
implementing
a
menu.
A
D
Sure
when
we
have
the
environment
screen
and
when
we
have
the
stages,
the
overview
of
the
stages
moved
into
the
environment
screen,
then
the
stages
should
be
clickable.
In
other
words,
when
you
click
on
one
of
those
stages,
then
you
should
get
more
information
about
the
stage
itself.
As
you
can
see,
you
see
here
on
the
right
side,
you
should
get
meta
information
about
the
stage
where
you
see
the
deployment
strategy
and
the
test
strategy
that
is
configured
and
underneath
there
you'll
see
a
list
of
all
the
services
that
are
running
in
this
stage.
A
A
That's
fine,
oops,
actually
also
very
nice,
to
see
we
can
filter
and
you
already
have
four
tasks
already
assigned
so
yeah
I
guess,
as
the
time
is
coming
to
an
end,
we'll
skip
the
last
two.
We
have
assigned
12
issues.
Thank
you
for
all
your
contributions
that
you're
going
to
make.
Hopefully
is
there
anything
you
want
to
add
Johannes
yeah.
D
I
want
to
add
that
nobody
should
should
fear
some
pressure
that
this
must
be
done
by
next
week.
This
is
not
it's.
It
would
be
cool
when
we
get
all
those
tasks
finished,
but
when
there
is
the
case
that
another
a
bug
comes
in
or
another
issue
needs
to
be
fixed.
First
then
yeah
we
are
flexible
enough
to
to
shuffle
around
and
to
change
the
order
and
don't
feel
the
pressure
to
get
everything
done.
I
mean
in
in
one
week.
D
A
A
Yeah
I
think
thanks
everyone
for
joining
big,
shout
out
to
the
devil,
captain
development
team
for
because
of
the
new
release,
so
actually
in
Austrians,
it's
kind
of
a
practice
to
have
a
really
spear
of
the
unit
successfully
released.
So
maybe
you
can
have
a
beer.
Oh,
you
already
have
your
mug
on
the
table.
A
So
thanks
everyone
for
20.
We
will
meet
again
next
week
same
time
same
swimmingly.
So
what
you
can
do
is
just
as
a
quick
reminder
being
the
captain
community
page
or
on
the
captain
community
page.
It's
getting
up
to
the
college.
Captain
slash
community.
There
is
also
meeting
calendar
and
you
can
subscribe
to
this
calendar,
so
you
can
download
it
and
report
it
in
your
home
calendar
to
always
stay
up
to
date.
So
thanks
so
much
for
joining
and
see
you
all
next
week.
We're
not
thinking
see
you.