►
From YouTube: Keptn Community Meeting - September 10th, 2020
Description
September 10, 2020
Diary - what happened last week?
🎉 Keptn 0.7.1 released 🎉
CNCF Slack Channel: Join here
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
Good first issues: https://goodfirstissue.dev/ or start here
Noteworthy Issues & PRs (Review)
For each PR, please tell us if you updated the docs, or in case it was not necessary please say so.
Florian:
CloudEvents 1.0, remove eventbroker
https://github.com/keptn/keptn/issues/2254
Lighthouse-service and jmeter-service: Use .triggered, .started and .finished events
https://github.com/keptn/keptn/issues/2263
https://github.com/keptn/keptn/issues/2264
Andreas:
Johannes:
Keptn on OpenShift 4.4: https://github.com/keptn/keptn/issues/2157
Security requirements for CII Badge: https://bestpractices.coreinfrastructure.org/en/projects/3588 → https://github.com/keptn/keptn/issues/2205
Ermin:
Christian:
Roadmap → KEP / SPEC / Issues
KEP 06: The next generation of Shipyard: https://github.com/keptn/enhancement-proposals/pull/6
Work in progress:
https://github.com/keptn/keptn/projects/29
Backlog Refinement / Next Sprint:
https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Akeptn+user%3Akeptn-contrib+label%3A%22next-sprint%22
Planning Board: https://github.com/keptn/keptn/projects/29
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
And
the
recording
goes
on
hi
everyone
yeah
this
week.
We
want
to
talk
a
little
bit
about
the
captain,
0.71
release
that
we
pushed
out
this
week
and
actually
the
features
have
been
presented.
The
last
couple
of
meetings,
but
still
let
me
show
you
a
brief
summary
of
what
the
new
patch
release
of
0.7
contains.
A
A
Next
to
that,
captain
can
also
now
be
upgraded
using
the
captain
upgrade
command.
This
is
a
one-liner.
You
have
to
enter
in
your
command
line
and
this
command
takes
care
of
upgrading
your
capped,
node,
seven
to
another,
seven
one
from
a
technical
point
of
view.
It's
actually
a
helm
upgrade
that
this
command
perform
executes,
but
it's
still
very
convenient
and
a
nice
way
to
getting
updates
of
captain,
then
also
from
from
a
perspective
of
operating
captain
installing
captain,
you
can
now
set
a
root
context
for
your
endpoint.
A
This
is
necessary
in
case
you
install
captain
next
to
another
application,
and
you
would
then
share
the
same
route
at
the
end
point
and
for
customizing
your
api
endpoint.
You
have
now
the
possibility
to
add
a
prefix
to
your
captain
endpoint,
depending
on
how
you
want
to
separate
two
applications
from
each
other.
A
Well
then,
we
announced
a
two
new
cli
commands.
The
first
one
is
a
captain
delete
service
yeah.
The
community
was
asking
for
his
feature
now
for
a
while
and
it's
now
available
and
here
and
you
can
simply
delete
a
service
after
onboarding
or
creating
one,
and
this
one
will
get
rid
of
all
the
artifacts
that
are
stored
in
your
git
repository,
but
be
aware
that
we
don't
delete
the
events
in
the
mongodb
because
going
forward
we
need
to
think
about
or
going
forward
there
will
be
an
event
store.
A
A
Then
also,
please
check
out
the
ux
improvements
in
the
bridge.
They
are
awesome.
They
allow
you
now
to
have
more
features
in
the
environment
screen
and
it's
really
convenient
now
to
use
the
environment
screen
and
to
go
directly
to
a
failed
quality
gate
to
a
ongoing
remediation
or
to
the
step
of
approving
a
deployment
and,
last
but
not
least,
many
thanks
to
mark.
He
provided
us
a
great
tutorial
for
running
captain
openshift
4.4
cluster.
A
He
did
all
the
work.
I
was
just
doing
a
final
test.
I
took
his
tutorial
and
executed
that
one
on
my
machine
and
it
worked
out
really
really
smooth
mark,
also
provided
us
two
artifacts.
The
first
one
is
the
tutorial
itself.
Please
feel
free
to
check
that
one
out
and
to
install
captain
on
your
openshift
4.5,
cluster
or
4.4,
and
he
also
provides
a
youtube
video
where
he
shows
a
short
video
on
how
to
automate
everything
around
the
shift.
Setup.
A
Cool
then,
like
always
when
you
want
to
join
us
on
the
cncf
slack
channel.
Please
click
here
this
one
in
forwards,
you
to
the
cncf
slack
and
there's
also
a
mechanism
that
you
can
sign
up
for
a
captain
mailing
list,
and
then
you
will
receive
a
email
every
monday
morning
and
when
you
want
and
when
you
want
to
get
started
with
implementing
a
your
first
captain
feature,
then
please
check
out
the
list
of
good
first
issues.
A
They
are
provided
or
are
shown
here
at
this
website,
the
good
first
issue.dev
website
and
just
select
one
of
those
issues
post
your
your
github
account
and
then
we
will
assign
you
to
the
issue
and
you
are
ready
to
get
your
work
done
all
right.
Then,
let's
jump
directly
to
the
issues
that
have
been
implemented
this
week,
and
this
means
that
I
will
hand
over
to
florian
now.
B
You
should
see
my
screen
now,
okay,
today,
I
want
to
show
you
two
points
that
we've
worked
on
this
week.
So
the
first
one
considers
the
cloud
events
we
are
using
in
captain.
So
in
the
previous
versions,
including
071
of
captain,
we
have
used
our
cloud
events,
odot,
2
and
now
it's
time
to
upgrade
to
the
version
1.0
of
the
cloud
event
spec,
because
that
has
been
available
for
quite
some
time
now.
B
B
So
if
you
recall
the
last
few
community
meetings,
we
have
shown
the
shipyard
controller
a
couple
of
times
already
as
it
was
developed
further
and
further
and
now,
since
it
has
the
full
capability
of
going
through
a
task
sequence
of
a
shipyard
and
sending
out
triggered
events
waiting
for
the
correlating,
started
and
finished
events
to
come
in
and
then
trigger
the
next
task
sequence.
It's
now
time,
of
course,
to
adapt
all
the
execution
plane.
B
Services
like,
for
example,
the
helm
service,
lighthouse
service,
jnita
service,
etc,
to
be
able
to
use
those
triggered,
started
and
finished
events,
and
we
have
already
done
that
for
the
chain
meter
service
and
for
the
lighthouse
service.
So
yeah
here
are
the
two
coordinating
issues
for
that
and
and
full
requests.
Of
course,
you're
always
welcome
to
look
at
the
code
and
yeah
and
also,
of
course,
we've
updated.
B
D
A
A
A
When
you
go
there,
you
find
a
short
description
of
what
it
is
about.
Yeah,
it's
the
core
infrastructure
initiative
patch
and
it
kind
of
provides
requirements
or
a
list
of
requirements
that
you
as
an
open
source
project,
have
to
have
to
fulfill
like,
for
example,
standards
and
best
practices
for
reporting
issues,
new
features
or
vulnerabilities
and
so
on.
C
A
and
based
on
this
master
key.
We
then
can
derive
other
session
keys
or
the
api
key
and
so
on.
This
is
the
first
task
that
we
have
to
implement,
and
the
second
one
is
that
we
should
take
a
look
at
other
open
source
projects,
how
they
store
their
credentials
right
now.
We
store
them
in
a
kubernetes
secret,
but
let's
have
a
look:
let's
have
a
outreach,
how
other
projects
are
doing
that
so
that
we
can
then
figure
out
what's
the
best
way
to
deal
with
credentials
inside
the
cluster.
A
All
right
yeah,
this
was
this.
This
task
and,
as
I
said,
I
derived
two
follow-up
tasks
that
we
will
now
discuss
in
this
backlog,
refinement
and
yeah
next
step,
but
before
we
go
there
and
since
we
have
a
couple
of
new
folks
joining
this
meeting,
I
want
to
point
out
that
the
road
map
of
captain
is
always
provided
here.
A
E
E
A
D
Shipboard
controller
right,
so
basically,
the
home
service
will
then
understand
deployment
triggered
and
release
triggered
events,
and
but
this
we
are
splitting
basically
the
deployment
from
the
release
step,
and
I
have
to
do
this
issues
together.
So
in
combination
with
that
way-
and
I
will
yeah
probably
finish
this
next
week-
cool.
A
B
Says
description
of
how
you
can
back
up
and
restore
your
project
related
data
in
your
captain
installation?
This
is
the
pr
has
already
been
filed,
so
it's
currently
being
reviewed.
I
think
christian
ran
into
some
hiccups,
but
I've
already
corrected
those,
and
now
it
should
be
working
fine.
So,
basically,
here
we
have
the
instructions
for
both
versions:
zero,
six,
two
and
four
c:
zero.
Seven.
A
Okay
and
florian,
I
also
created
a
develop
folder
for
the
0.8
version
of
captain.
Can
you
please
also
add
your
instructions
to
the
to
the
new
folder
yep
already
done
perfect
thanks
a
lot
okay,
then,
unfortunately,
we
don't
have
christian
on
this
call,
but
he
is
working
on
getting
rid
of
the
installation
step
in
the
promesa
service.
Hopefully
he
can
join
next
week
and
we
have
still
this
issue
in
the
backlog
or
here
in
the
broadcast
column.
D
We
we
have,
or
we
need
specifications
for
the
handle
service
for
the
geometry
service
and
for
all
these
external
cabinet
services,
which
specify
the
required
fields
in
order
to
do
the
operation,
and
each
of
the
services
then
has
to
double
check
whether
all
this
information
is
available
or
not
so
a
classical
spec
is
not
necessary.
Now,
maybe,
let's
pull
this
back
into
the
backlog
and
as
soon
as
we
earlier,
we
can
address
this
okay.
A
C
Yeah,
it's
just
one
question
actually
two
seeing
that
we
have
milestone
zero,
seven,
two
right
now.
I
believe
we
should
reschedule
this
issue
for
zero.
Seven.
Two
and
the
second
one
is
so
I
can.
I
can
easily
set
the
api
token
to
256
bit.
That's
a
minor
change,
it's
a
one-liner
or
maybe
two-liner,
but
do
we
want
to
go
forward
having
two
secrets
or
two
tokens
like
a
master
secret
for
the
call
cluster
and
then
a
derived
api
token?
C
D
E
Yeah,
that's
an
open
task
still
in
the
bridge,
yeah
just
to
provide
an
http
interceptor
and
if
some
http
calls
should
fail
yet
just
to
show
an
error
message
to
the
user,
because
currently
there
is
nothing
happening.
So
if,
for
some
case
during
the
bridge
having
the
bridge
opened,
some
errors
happen.
Yeah,
the
user
is
not
informed
so
yeah
that
should
yeah
that's
a
minor
one
actually,
but
we'll
do.
A
All
right,
yeah,
then
jurgen
is
also
not
in
this
call
today,
but
he
assigned
himself
to
this
issue.
He
wants
to
do
the
outreach
to
the
to
the
other
projects
and
we'll
find
we'll
figure
out
how
those
projects
are
storing
their
credentials
so
that
we
also
have
an
answer
to
this
requirement.
Cii
page
requirement.
A
But
in
a
typical
setup
you
just
have
one
sli
provider
and
that's
the
reason
why
we
want
to
have
this
improvement
where
the
lighthouse
service
takes.
The
conf
takes
a
default
config
map
and
this
default.
Config
map
contains
the
default
sli
provider
and
when
there
is
no
project
specific
config
map,
then
we
have
to
fall
back
to
the
default
one.
A
A
A
Okay,
yeah,
with
the
new
feature
in
the
captain's
bridge
that
now
allows
a
captain
user
to
get
the
captain
api
token
and
the
captain
auth
command.
There
was
also
the
feature
request
to
get
a
download
link
to
the
captain,
cli
I
just
for
more
convenience
and
for
also
supporting
or
for
helping
users
that
are
mostly
used
to
the
to
the
user
interface
or
to
the
to
the
captains
bridge.
C
A
E
B
A
A
All
right,
yeah,
then
another
one.
This
is
not
that
much
related
to
the
captain
core,
it's
more
related
to
a
captain,
contrib
service,
it's
for
that
dynadress
sli
service,
because
this
service
has
the
capability
to
take
a
look
at
the
dynadress
dashboard
and
then
extract
the
slos
and
slis
from
this
dashboard,
and
a
couple
of
users
were
asking
whether
we
can
provide
some
help
to
create
this
dashboard.
A
And
with
this
feature,
or
with
this
issue
I
propose
or
would
yeah,
I
propose
to
specify
a
curl
command
for
the
dynadress
api.
That
will
then
create
the
dashboard
as
it's
shown
in
this
tenant,
and
you
can
also
find
some
supporting
material
right
here
in
this
youtube.
Video,
where
a
captain
user
is
using
this
new
feature
and
shows
how
it
works
and
how
it
ties
together.
D
A
That's
true,
let
me
ask
andy:
that's
that's
true:
let's
move
that
one
a
little
bit
up
the
next
one
and
this
one
is
related
to
the
dynadre
service,
because,
right
now
the
dynadress
service
does
a
couple
of
changes
in
a
dynadress
environment.
It
adds,
for
example,
tagging
rules.
It
adds
a
problem,
notification
and
management
zones
and
so
on,
and
we
should
make
it
customizable
so
that
we
can
turn
on
or
off
certain
features
and
in
this
issue,
for
these
five
features,
environment
variable
should
be
provided.
A
D
A
A
A
A
A
E
E
A
A
But
what
we
have
now
is
are
the
project
tiles
and
I
would
like
to
add
the
github
stream
url
of
a
project
right
here
yeah.
When
you
go
to
the
project
page,
you
you
find
your
project
and
then
you
should
also
get
a
link
to
the
git
upstream
in
case
it's
set
in
case.
It's
not,
then
just
provide
a
hint
and
explain
the
user.
How
to
configure
a
github.
A
Stream,
I
was
also
going
one
step
further
and
thought
about
adding
a
form-
a
very
small
as
a
small
form
to
this
tile,
where
you
can
then
define
your
git
url,
your
get
user
and
git
password,
but
for
the
scope
of
this
issue,
let's
stay
focused
on
just
providing
the
ul
here
and
because
I
also
have
to
figure
out
whether
we
need
an
additional
settings
page
that
would
allow
us
to
configure
and
to
customize
more
settings,
especially
in
regard
to
a
project
and
so
on.
This
should
not
be
implemented
in
this
issue.
A
A
Otherwise,
when
you
have
still
some
time
left,
feel
free
to
take
a
look
into
the
backlog
and
to
assign
yourself
to
an
issue
and
start
working
on
that
one
cool
and
when
you
want
to
get
started
with
a
good
first
issue,
there
are
always
a
couple
of
issues
further
down
here
on
the
bottom,
as
I
said,
just
take
a
look
assign
yourself
and
you
can
get
you
can.
Can
you
can
start
working
on
it?
A
A
So
it's
only
us,
it's
only
us,
okay
yeah!
It's
couple
of
folks
left
during
the
meeting.
That's
okay,
all
right!
Then.
I
think
we
are
now
at
the
end
of
today's
community
meeting,
because
there
are
no
further
agenda
items
here
on
the
sheet
so
that
I
will
close
it
now
and
we'll
say
thanks
for
joining,
see
you
next
time
and
have
a
nice
day.