►
From YouTube: Keptn Community & Developer Meeting - May 6th, 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
Sign up to our community newsletter: https://keptn.sh/community/newsletter/
A
Hi
everyone
and
welcome
to
this
captain
community
and
developer
meeting
today.
It's
may
6th
it's
the
week
of
kubecon
and
yeah.
We
have
quite
a
big
crowd
here
today,
despite
kubecon,
so
really
cool
thanks
everyone
for
joining,
and
we
have
a
quite
a
long
list
on
the
agenda
that
we
want
to
go
through.
First
of
all,
it's
the
cnc
captain
is
the
cncf
project,
as
you
all
know,
so
we're
also
following
the
cncf
code
of
conduct.
Please
apply
to
this
code
of
conduct.
A
Yeah.
If
you
are
at
kubecon
this
week,
make
sure
to
also
join
us.
We
do
have
another
office
hour
tomorrow
morning:
9
a.m,
with
the
captain,
maintainers
and
also
captain
contributors.
So
there
will
be
also
folks
from
the
community
from
the
captain
community
joining
tomorrow.
A
You
will
find
the
link
here
we're
still
looking
for
a
code
owner
for
our
notification
service.
So
if
you
have
experience
in
developing
captain
services
or
want
to
join
the
captain
community
and
want
to
be
a
captain
contributor,
then
the
notification
service
is
one
of
the
services
that
we're
looking
for
contributors
so
feel
free
to
reach
out
to
us
and
maybe
take
on
our
ownership
of
this
repo
or
just
help
us
here
in
migrating
this
to
work
with
the
latest
version
of
captain.
A
What
we
also
created
in
the
last
week
is
a
way
for
you
to
explore
captain
if
you're
not
familiar
with
captain
right
now
to
explore
captain
without
the
need
to
install
captain.
So
there
is
a
public
demo
cluster
for
you
available
and
you
can
it's
a
read-only
cluster
and
you
can
click
through
captioning
experience,
quality,
gate
evaluations,
the
promotion
mechanisms
of
captain
how
slos
are
defining
captain.
So
all
that
you
would
do
with
your
own
captain
installation,
but
you
can
do
it
in
a
read-only
installation
and
there
will
be.
A
A
From
someone
sorry
for
this
okay,
so
I
think
for
the
ecosystem.
There
are,
we
know
a
couple
of
folks
are
working
on
integrations,
but
nothing
to
announce
for
this
week,
and
so
we
are
coming
now
to
to
to
the
to
the
part
where
we
actually
it's
kind
of
a
portal.
A
The
next
two
dates
for
our
community
and
developer
meetings
are
conflicting,
either
with
public
quality
or
with
other
duties
of
the
captain
core
maintainers.
So
first
question
is
for
next
meeting:
it's
a
public
holiday
for
a
lot
of
our
captain
core
maintainers.
Should
we
cancel
next
week's
meeting?
It
will
be
on
a
thursday.
A
It
would
be
a
public
holiday.
So
I
guess,
are
there
any
objections
to
not
cancel
the
meeting?
A
Okay,
because
I
think
it
will
be
mostly
otherwise
a
lot
of
you
cannot
join.
So
I
will
reach
out
to
the
cncf
to
also
remove
the
next
week's
meeting
from
the
calendar,
and
we
will
cancel
next
week's
meeting
for
the
meeting
on
may
20
20.
A
Okay,
maybe
a
quick
vote
of
hands
who
wants
to
move
it,
so
I
can
just
see
it
here
in
the
yeah:
that's
the
majority
make
sure
you
want
to
move
it
okay.
So
let's
just
put
it
actions.
A
Meanings,
okay,
so
I
will
have
this
done
and
so
I'm
handing
over
already
to
the
to
airmen
before
that.
Are
there
any
questions
on
the
things
I
just
announced
here.
A
Okay,
if
not,
I
mean
please
take
it
away.
D
Cool,
thank
you
very
much.
Yeah,
I'm
going
to
present
a
pull
request
in
captain's
bridge
today.
Actually,
this
one
also
allowed
me
to
have
insights
into
the
shipyard
controller.
D
It's
about
supporting,
more
advanced
stitching
environments,
and
here
we
have
a
request
that
in
case
that
I
will
show
you
the
details
just
here.
We
have
multiple
stages
that
all
yeah
derive
from
the
same
parent
stage
or
in
this
case
have
the
same
trigger
should
be
also
visualized
in
the
bridge
in
the
environment
screen.
D
So
yeah
you
saw
the
and
you
saw
the
shipyard
and
previously,
in
captain's
bridge,
we
would
show
in
the
environment
screen
just
a
list
of
all
stages
that
have
been
configured
in
your
shipyard
file.
You
lose
here
the
information
yeah,
which
sequence
is
first
and
which
stage
is
first
and
which
one
is
last.
Obviously
the
order
is
yeah
from
left.
D
Stop
and,
like
you
read,
but
yeah,
it's
very
difficult
to
know
that
or
to
find
that
out,
and
you
also
lose
the
information
that
production
a
b
and
c
derive
from
the
production
stage.
So
the
production
stage
is
the
parent
of
those
three
stages,
and
now
the
bridge
will
yeah
show
you
this
a
little
bit
different
for
the
production,
a
b
and
c
stages.
You
will
see
that
they
are
parallel
in
this
case
they
are
stacked
here
after
the
production
stage.
D
Yeah,
that's
basically
I
don't
have
a
deployment
here,
but
of
course,
when
you
select
the
stage
you
see
the
details
of
that
stage
and
also
you
have
this
scroll
bar
now.
So
if
you
have
many
stages
and
yeah
from
depth
in
staging
from
staging
in
production,
from
production
in
production,
a
b
and
c,
which
could
be
three
customer
environments,
you
see
those
details
now
in
your
environment
screen.
B
I
mean,
I
think,
the
the
issue
itself
also
included
a
change
of
the
width
of
the
middle
part,
meaning
that
we
give
it.
D
Yes,
there
are
still
some
ui
details,
so
this
pull
request
is
still
open
and
I'm
working
on
those
small
details,
as
you
can
see,
also
the
scroll
bar-
is
not
properly
aligned
here
with
some
headings,
and
so
this
is
some
css
details
which
I'm
working
on
still
and
also
yeah.
We
will
reduce
the
amount
of
this
details
on
the
right
side,
so
we
have
more
space
here.
C
D
No,
this
is
actually
yeah.
This
would
require
us
to
have
a
yeah,
canva
or
yeah
draw
this
elements
on
the
canva.
Currently
we
just
use
css,
and
these
boxes.
E
D
C
Not
yet,
let's
put
it
like
this,
but
I
can
definitely
use
them
in
github
actions
and
that's
a
real
benefit
there.
I'd
say
because
you
can
see
if
you
skip
a
stage
so,
for
instance,
what
if
you
want
to
group
your
stages
based
on
production,
but
you
say
for
customer
c
you're
skipping
staging,
but
you
want
to
group
it
there.
So,
but
that's
a
more
advanced
topic.
D
Yeah,
so
that
would
be
more
advanced
topic
also.
We
would
need
to
support
that
in
the
core,
but
yeah
I
see
could
be
an
enhancement
there
in
the
future.
Currently
you
yeah
just
have
it
in
that
order
and
yeah
vertically
stacked
if
they
are
parallel.
D
Yeah
two
more
things
that
I
just
want
to
mention
here
is:
let
me
just
find
those
two
bucks
in
the
bridge
that
have
been
found.
One
was
in
qualitygate's
only
use
case.
We
had
the
problem
that
yeah
in
case
that
you
have
a
sequence
that
is
named
evaluation
or
that
has
the
same
name
as
a
task
in
your
shipyard.
E
D
Several
parts
of
the
bridge
ui
that
are
broken
and
not
working,
for
example,
you
don't
see
the
heat
map
in
the
services
screen,
the
environment
screen
is
broken
and
so
on.
So
that
was
fixed
and
one
more
detail
also
in
the
integrations
page
the
bridge
shows-
or
previously
we
had
the
feature
here-
that
the
start
time
was
here,
parsed
and
displayed
by
the
bridge
so
that
you
just
can
copy
and
paste
this
comment
and
yeah.
D
For
some
reason
it
was
not
working
anymore,
and
this
is
now
also
fixed
again,
and
it
will
show
you
here
the
current
time
and
update
every
minute.
So
you
have
here
always
the
current
time
and
you
can
just
copy
and
paste
this
comment
and
if
your
environment
variables,
project
stage
and
service
are
set
or
replace
those
parameters,
you
can
trigger
an
evaluation.
D
With
this
comment,
yeah,
that's
actually
from
my
side
and
I'm
handing
over
to
elizabeth.
F
So
what
did
I
do
this
print?
So
maybe
you
have
already
seen
it
at
airmen's
screen
I
improved
or
minified
the
the
navigation
for
the
captain's
bridge.
So
it's
that
the
main
content
gets
more
space.
Now
I
have
chosen
with
the
new
x
expert,
appropriate
icons
for
that,
and
also
you
can
so.
The
the
information
which
screen
is
hidden
behind
the
icon
is
also
not
lost,
so
there
is
a
tooltip
for
or
your
convenience
so
that
you
can
just
use
it
so
yeah.
F
Perfect,
I
think
I
think
there
was
something
went
wrong
there.
Oh
I'm,
okay,
so
that
can
I
have
to
start
a
new
okay.
So
the
content
is
now
a
bit
has
more
space
now,
because
the
the
menu
is
shrinked
a
little
bit
and
yeah,
as
you
can
see,
the
appropriate
icons
were
chosen
and
also
the
two
tips
show
which
screen
is
hidden
behind
it.
So
hopefully
it's
now
a
bit
more
tidied
up.
F
F
The
third
thing
I
worked
on
is
the
new
settings
page
for
the
git
upstream
repository.
As
you
can
see,
I
already
configured
one
from
a
sock
shop,
so
this
information
is
loaded
already
from
the
api
and
we
can
try
yeah
try
to
set
one
here.
So
I
just
add
anything:
yes,
you
will
see.
I
get
an
error
because
the
kit
upstream
is
not
properly
configured
yeah,
it
could
not
be
said,
but
yeah,
okay,
so
now
it's
so
this.
F
F
Otherwise,
there
were
some
some
bug
fixes
or
some
a
lot
of
bug
fixes
for
me
to
sprint.
The
most
important,
I
think
is,
are
the
notification
that
popped
up
more
times
than
once.
If
you
toggled
the.
F
Version
check
it's
now
gone,
so
there
should
be
only
one
one
notification,
so
you
don't
get
spammed
with
it.
There
was
a
small
issue
with
the
project
picker,
so
this
is
also
fixed.
So
this
works
properly
again,
I
just
yeah.
This
is
the
same
thing.
F
We
also
had
a
small,
a
minor
issue
with
displaying
a
change
event
or
yeah
events
in
the
bridge.
It
should
started
so
it's
now
changed
again.
So
at
the
view
is
now
proper.
C
Thanks
so
I'll
I'll
continue,
so
my
sprint
had
a
lot
of
issues
with
type
critical
related
to
the
integration
tests
and
some
bug
fixes
and
then
some
smaller
other
tasks.
Let's
put
it
like
this,
so
I'll
have
some
links
here.
Regarding
the
integration
tests,
we
did
some
minor
fixes
and
we've
improved
some
of
the
log
output.
There's
nothing
really
worth
mentioning
here,
other
than
just
saying
that
it
was
done.
C
C
I
recommend
to
run
them
within
a
go
routine,
because
then
your
handle
code
will
eventually
return
nil
quite
quickly,
and
then
the
distributor
that
sent
you
the
cloud
event
basically
says.
Okay,
fine,
you
received
the
cloud
event.
I'm
done.
C
We
didn't
have
that
and
due
to
timing
issues
with
github,
for
instance,
our
helm
service
took
quite
a
long
time
in
this
function
in
this
method
here
and
it
took
30
to
40
seconds
to
respond,
and
eventually
we
ran
into
a
timeout
somewhere.
So
some
weird
timing
issues
to
be
honest
lesson
learned,
run
it
in
a
go
routine.
C
C
Then
a
couple
of
follow-up
issues,
including
this
one
came
from
that
bug.
So
we
started
to
improve
the
distributor
a
little
bit
in
terms
of
what,
if
we
have
a
slow
service
responding.
So
what,
if
you
forget
to
run
it
in
a
go
routine
yeah,
and
for
that
we
improved
the
so-called
cloud
events
cache
a
little
bit
such
that.
Let
me
see
where
the
code
is.
C
There
we
go
so
before
there
was
a
go
routine
that
was
sending
the
event
and
if
sending
the
event
was
successful,
we
added
it
into
the
cache
we
kind
of
do
it
the
other
way
around.
Now
we
add
it
to
the
cache
first,
then
we
send
the
event
and
if
an
error
happened,
we
remove
it
from
the
cloud
events
cache
such
that
in
the
next
loop
of
the
distributor.
C
C
Good
then,
the
next
thing-
I'm
not
gonna,
go
into
details
here,
but
just
saying
we
have
introduced
a
new
linter,
go
like
the
island
into
our
build
chain
and
remove
the
old
golind.
We're
hoping
that
our
code
review,
powered
by
review
dog
is
now
a
little
bit
more
meaningful
than
just
saying
hey.
There
is
a
comment
missing,
then
another
bug
fix
for
geometer
service.
C
C
C
So
you
know
what
you
might
need
to
adapt
for
your
captain,
contrib
and
captain
sandbox
services,
so
essentially
look
into
your
github
workflows
check
where
go
version
is
set
and
increase
it
to
116
and
in
your
docker
file,
make
sure
you
use
a
newer
version
for
the
builder
image
so
instead
of
golang
113
7
alpine,
we're
using
162
alpine
and
in
the
go
modules,
obviously
also
just
upgrade,
to
go.
1
16
from
go
113
and
last
but
not
least,
also
don't
forget
to
upgrade
your
local
gold
binary.
C
So
this
is
also
going
to
all
captain
core
developers.
Now
upgrade
your
go
binary
locally
to
116.,
I
think
113
will
still
work
but
make
use
of
the
new
features.
C
Unfortunately,
I
wasn't
able
to
finish
one
part
of
my
task,
which
was
to
enable
the
build
for
apple
silicon.
I'm
not
an
expert
with
macos
golang
builds.
The
only
thing
I
really
was
able
to
extract
from
the
locks
is
that
it
stopped
somewhere
around
compiling
the
helm
package
at
this
point
here.
This
is
where
it
was
the
last
message
and
it
stopped
with
an
error.
C
I
can't
really
make
out
anything
of
this,
so
if
anyone
knows
please
comment
on
this
issue
help
us
out
here,
other
than
that
we
cannot
provide
apple,
silicon
or
apple
m1.
Chip
based
binary.
A
Not
directly
to
your
to
your
issues,
but
thanks
christian
for
presenting,
I
just
wanted
to
jump
in
between,
because
we
see
a
couple
of
folks
from
the
community
joining
and
also
they
added
some
items
to
the
agenda.
I
just
wanted
to
clarify
that
we
kind
of
have
a
bi-weekly
cadence
in
this
community
meeting.
A
So
for
one
week
we
focus
more
on
captain
core
contributions,
while
on
the
other
week
we
focus
more
on
community
contributions,
and
for
this
week
we
have
a
lot
of
captain
core
maintainers
presenting
and
if
there
is
time
left
at
the
end,
we
will
also
go
through
all
the
the
other
agenda
items.
Unfortunately,
myself,
I
will
have
to
leave
a
little
bit
early,
so
johannes
would
take
over
this
part
then,
but
I
just
wanted
to
to
announce
that
we
do
not
forget
about
these
items.
A
Otherwise
we
could
just
carry
on
and
do
them
in
the
next
meeting,
but
thanks
everyone
for
joining
and
if
you
have
any
more
questions
that
cannot
be
addressed
in
this
kind
of
meetings,
then
also
please
reach
out
in
the
captain's
leg
and
get
in
touch
with
us.
A
So
sorry
for
interrupting
here-
and
I
think
it's
the
next
one
is
florian.
If
I
saw
this
correctly
in
the
agenda.
G
All
right,
so,
if
you
recall
the
last
couple
of
community
meetings,
we
showed
you
a
couple
of
github
actions
that
we've
implemented
so
one
for
setting
up
a
kubernetes
cluster
with
captain
on
it
installed
and
where
we
also
had
a
cabin
project.
G
E
G
To
send
events
to
to
captain
from
within
a
github
action,
and
in
this
sprint
it
was
time
to
actually
make
use
of
those
actions
and
to
combine
them
into
one
into
a
bigger
picture
that
we
had
in
mind
here,
which
is
the
delivery
of
captain
with
captain.
Actually,
so,
basically,
if
we
click
on
the,
if
we
go
to
the
issue,
so
that's
basically
the
picture
we
had
in
mind
so
basically
on
our
cabin
repository.
G
G
So
those
credentials
are
stored
in
our
github
secrets,
so
the
action
can
make
use
of
that
and
what
we
then
need
to
do
is
we
need
to
yeah
check
out
the
code
and
also
install
the
the
captain
cli
in
order
to
be
able
to
authenticate
with
at
our
captain
instance,
and
what
we
do
afterwards
is
after
we
have
authenticated
our
cli.
G
So
we
add
the
resource
for
the
captain
core
helm,
chart
and
also
the
helm
service
and
the
jmeter
service
help
chart
to
our
cabin
project,
and
then
we
used
send
event
github
action
that
bent
implemented
and
already
showed
presented
in
the
last
or
in
one
of
the
last
community
meetings,
and
basically
we
use
this
action
to
trigger
a
new
deployment
and,
as
you
can
see
here,
we
have
this
deployment
strategy
set
to
user
managed
and
what
we
can
also
do
is
here.
G
We
can
add
a
label
with
the
github
action
run,
and
this
will
you
will
see
that
in
a
second
provide
us
with
a
link
back
to
the
github
action
in
our
in
our
cabins
bridge
and
of
course,
the
type
of
the
event
is
sh.catherine.event.dev:
dot,
delivery
trigger
and
yeah.
Next,
let's
go
to
our
captain's
bridge.
G
G
G
C
G
Totally
right,
so
we
do
actually
have
some
load
tests
actually,
so
this
is
which
are
very
rudimentary,
but
this
shows
that
the
workflow
in
general
works
and
that
we
can
use
our
dinatrisos
to
evaluate
or
retrieve
the
values
that
we
would
like
to
evaluate
all
right.
So
in
that
case,
we
we
had.
G
We
reached
the
score
of
75,
which
gave
us
a
warning,
but
still
it
proceeded
with
going
into
the
next
stage
and
here
in
production
and
production
remote,
we
do
need
a
manual
approval,
so
yeah.
Let's
just
do
that.
So,
if
we
click
here,
then
the
deployment
for
the
delivery
workflow
in
that
stage
will
continue
and
also
while
that
is
running,
I
can
already
accept
this
new
version
in
the
production
remote,
and
you
should
now
see
all
right
here.
G
C
G
G
C
G
G
G
So,
as
you
can
see
here
in
the
swagger
dock,
the
path
to
this
endpoint
is
slash
state,
slash
project,
so
the
project
parameter
is
required
for
that
and
what
that
will
allow
you
to
do
is
you
can
also
pass
a
page
size
and
the
next
page
key.
So
we
have
pigeon
nation
supported
here
for
this
endpoint
and
the
response
of
that
looks
like
that.
G
So,
basically,
you
will
receive
an
array
containing
the
states
of
the
task
sequences
within
that
project,
and
basically
the
information
here
tells
you
the
the
name
of
the
sequence,
so
the
name
that
you
have
given
in
the
shipyard
yaml
file
and
also
the
service
that
this
task
sequence
execution
is
affected
by
then,
of
course,
the
project,
the
time
it
has
been
started,
then
the
captain
context
and
the
current
state.
So
this
can
be
either
triggered
or
finished
later
on.
G
We
might
have
potentially
additional
states
like
acute,
for
example,
if
a
task
sequence
execution
is
waiting
for
another
execution
to
finish
before
it
can
actually
start
and
then
further,
you
will
also
receive
an
array
containing
the
stages
that
this
sequence
is
affecting.
So
in
that
case
we
have
the
yeah.
We
have
the
staging
stage,
and
this
array
also
contains
information
about
the
latest
evaluation.
G
G
There
is
one
additional
property
that
is
missing
here,
but
I
will
update
the
description
afterwards
appropriately
appropriately,
so
you
will
also,
if
you,
for
example,
have
a
delivery
sequence
that
involves
a
deployment
for
a
certain
image.
You
will
also
get
a
a
property
called
deployed
image.
I
think
it's
called
our
last
image,
so
this
will
basically
indicate
which
image
of
the
service
has
been
deployed
in
that
stage,
and
the
reason
behind
that
is
that
we
would
like
to
use
this
sequence
state
endpoint
in
the
bridge
to
display
the
relevant
information
for
our
task
sequences.
G
So
if
we
go
to
the
bridge
here,
we
will
then
be
able
to
basically
generate
all
the
information
that
is
shown
here
in
this
in
this
left
column,
using
that
sequence,
state
endpoint
and
therefore
we
won't
have
to
fetch
all
the
event
phrases
for
all
the
task
sequences
and
then
create
those
information
from
all
those
responses.
So
this
should
enhance
their
performance
quite
a
bit
and
leads
to
a
lot
less
api
calls
being
sent.
C
G
It
shows
the
executions
right
so
if
one
sequence
hasn't
been
executed.
Yet
this
will
not
show
up
here.
C
Okay,
so
it's
basically
ordered
by
time
and
if
I
have
100
evolutions,
I
get
the
state
of
100
evaluations.
G
Exactly
yeah,
but
you
can,
of
course,
always
limit
the
the
size
of
the
response.
So
if
you
are
only
interested.
C
Yeah
just
but
I'm
I'm
I'm
a
little
bit.
I
was
a
little
bit
confused
because
of
the
end
point
name
suggesting
show
me
the
state
of
the
project,
which
would
be
in
my
mind
it
would
be
the
I
would
like
to
see.
Okay,
I
have
four
sequences
and
maybe
three
of
them
are
running
or
whatever,
and
something
like
that.
So
this
is
kind
of
I
I
wouldn't
call
it
state.
In
that
sense,
I
would
call
it
sequences.
C
D
I
have
also
one
question,
or
actually
one
additional
filter
that
we
will
need
for
the
bridge
since
the
bridge
is
polling
for
the
events
and
yeah
to
get
only
the
new
sequences
that
are
added
on
top.
G
I
think
the
best
way
to
go
about
that
is
to
also
edit
their
builder
there
yeah.
So
we
can
okay.
D
G
G
G
File,
so
we
can
yeah,
so
here
we
are
so
basically
what
we
had
here
is
we
if
we
received
multiple
events
by
the
http
polling
feature
which
is
used
by
the
remote
execution
play
mode
of
the
distributor
we
added
those
events
to
the
cache
after
they
have
been
sent.
I
think,
in
the
meantime,
christian
already
changed
the
logic
to
do
that
before
the
send
event
method,
but
nevertheless
we
were
iterating
over
an
array
of
pointers
to
those
events
and
the
sending
of
the
event
happened
in.
E
G
G
H
Okay,
so
I
will
show
some
changes:
I've
done
in
the
bridge
mission
screen,
okay,
so
the
first
thing
I've
done
is
to
introduce
a
service
filter
in
the
environment
screen.
H
So
now
you
can
filter
by
a
specific
service
and
then
only
that
service
will
be
shown
in
the
environment
screen
and
also,
if
you
also,
the
icons,
are
always
updated.
If
you
just
select
cards,
for
example,
the
quality
gates
acting
is
gone
because
the
cards
db
doesn't
have
a
field
for
the
gates.
H
H
Yeah
yeah,
this
was
the
first
thing,
the
next
thing
yeah
I
mean
you
forgot.
Also
this
stage
dial
on
the
right
side
is
also
filtered
by
the
selected
service.
So
if
I
select
cards
only
cards
is
enabled,
etc.
C
C
H
Okay,
any
questions.
H
H
Now
you
see
or
is
it
is
visualized
if
a
deployment
is
deployed
in
the
in
a
specific
stage,
so,
for
example,
in
for
employment,
0,
12
1,
you
don't
see
that
this
is
filled
and
the
evaluation
is
filled
in
therefore
staging,
and
that
means
the
deployment
does
not
is
not
anymore.
In
this
specific
stage,
it
is
filled
if
the
deployment
is
running
in
the
stage.
H
So
yeah
here
are
the
sequence
height
evolutions
and
for
the
other
deployment
depth
and
staging
is
filled
because
it
is
currently
deployed
os,
which
is
shown
there.
The
deployment
ui
for
the
deployed
artifacts,
so
yeah
also
this
is
shown
here
for
deployments
and
not
for
the
things
that
are
not
deployed.
C
So
for
zero,
twelve
one,
it
is
not
shown
because
in
defense,
staging
there's,
0
12
2,
currently.
H
Exactly
so
it's
there,
because
this
deployment
exists
in
this
stage
and
in
indefinite
in
staging,
but
deployment
o2
f1
does
not
exist
in
therefore
stitching.
C
B
True
because
now
I
have
to
specify
a
particular
deployment
and
then
to
get
the
deployment
url.
B
Just
one
question
in
class:
does
this
timeline
also
work
with
the
feature
that
ermine
was
showing
us
with
the
multiple
stages
in
parallel.
B
Really
great
work
here
all
right,
then,
let's
have
a
look
at
the
agenda,
but
what
I
can
see
is
that
yeah
we
reached
the
last
item
in
this
list.
It's
actually
a
question
from
someone
of
the
community.
Let
me
just
ask
the
person
to
raise
the
hand.
Then
I
will
allow
you
to
to
speak
thanks.
I
already
can
see
it.
B
B
Can
I
ask
you
to
introduce
yourself
real,
quick.
E
I
don't
remember
the
name
of
the
meter
here
tell
me
about
learn
about
the
books
and
stuff
about
that.
So
I'm
not
sure
about
the
book,
but
I
have
some
background
in
copenhagen.
B
Sorry
for
me,
it's
a
little
bit
difficult
to
understand
your
question.
There's
a
lot
of
background.
B
E
Yeah,
so
my
question
was
like
I'm
not
completely
like
in
sync,
with
the
flow.
F
B
Yep,
I
think
the
best
starting
point
also
to
to
learn
more
about
captain
is
first
check
out
our
website.
It's
captain.sh,
slash,
docs
and
here
just
follow
this
quick
start
which
helps
you
to
get
started
by
creating
your
greatest
cluster,
installing
captain
the
cli
and
then
installing
captain
on
the
cluster,
and
when
this
is
done
here,
we
have
a
link
of
tutorials
that
help
you
to
understand
the
concepts
and
all
the
approaches
that
captain
tries
to
solve.
B
And
here
you
can
see
in
the
different
tutorials
that
we
provide.
Let's
pick,
for
example,
the
first
one,
the
captain
full
tour
on
promisers,
and
this
is
then
a
step-by-step
guide
to
learn
captain
and
to
explore
it
and
to
get
familiar
with
all
the
use
cases
that
we
provide.
E
Page,
okay
and
something
more
about
like
webhook
like
basically
what
what
what
you
expect
in
that.
B
Task
related
questions
also
feel
free
to
ask
them
on
slack.
B
Okay,
does
this
help
and
and
answer
your
question
yeah
yeah
sure
perfect
thanks
all
right,
I
think
then
we
are
yeah.
We
are
through
this
meeting
really
great
stuff
that
we
saw
today
really
looking
forward
to
the
next
release.
To
get
this
also,
then
rolled
out.
Are
there
any
questions
or
is
the
feedback
question?
E
This
this
slack
is
different
from
c
c
and
c.
F,
one
like
you
have
the
channel
in.
B
C
cnc,
that's
true
yeah.
We
have
two
slack
channels
one.
This
is
the
the
captain
slack
where
also
more
channels
are
open,
one
for
general
questions,
then
a
one
for
announcements
and
so
on,
and
then
we
have
just
one
channel
on
the
cncf
space,
where
we
just
post
announcements
and
and
things
that
are
going
on
in
the
community,
but
our
active
slack
channel
is
that
one
that
is
provided
here.
It's
slack.cat.h.
B
Please
follow
this
link
and
then
join
this
particular
slack
workspace,
and
then
you
find
the
channels
in
there.