►
From YouTube: Keptn Community Meeting - July 9th, 2020
Description
Meeting notes:
https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit#
July 9, 2020
Community Resources: https://github.com/keptn/community
https://github.com/keptn/community/blob/master/resources.md
Good first issues: https://goodfirstissue.dev/ or start here
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
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.
Ermin:
Update UI look and feel
https://github.com/keptn/keptn/pull/2026
Andreas:
Installer: https://github.com/keptn/keptn/issues/1960
Thomas:
API/Bridge Path: https://github.com/keptn/keptn/issues/1994
Health Checks: https://github.com/keptn/keptn/issues/1779
Florian:
Lighthouse Service: Added information on why evaluation has failed if preceding test has failed: https://github.com/keptn/keptn/issues/1585
CLI: Use correct kubectl context: https://github.com/keptn/keptn/issues/1942
Make core installation (quality gates) the new default: https://github.com/keptn/keptn/issues/1940
Ingress gateway configuration for helm-service:
https://github.com/keptn/keptn/pull/2009
Christian H.:
Version checker interrupts user when there's an error
Keptn API: Retrieve metadata of Keptn installation
Andi Grabner:
Version info on k8s labels: https://github.com/keptn/examples/issues/103
https://github.com/keptn/examples/pull/106/commits/dc953649cb022ff75c367325ac47bc677bbb3c20
Johannes:
MongoDB Directory Permissions Causes API to fail:
Issue: https://github.com/keptn/keptn/issues/1546
Docu: https://keptn.sh/docs/0.6.0/reference/troubleshooting/#keptn-on-minikube-causes-a-mongodb-issue-after-a-reboot
Project creation failed when using Git-upstream for GitHub: https://github.com/keptn/keptn/issues/2021
Roadmap → KEP / SPEC / Issues
KEP 18: Simplify installer - do not install istio nor NGINX-ingress - see: https://github.com/orgs/keptn/projects/1
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
Have you already spotted our new CNCF footer on keptn.sh? :)
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
We
have
again
a
lot
of
content
to
discuss
and
for
today,
I
just
want
to
start
briefly
with
some
community
resources,
since
we've
got
a
couple
of
requests
and
questions
where
to
find
some
resources
on
captain
and
where
to
find
that
it
is
born
articles
where
to
find
the
latest
presentation
material
where
to
find
like
other
things
like
the
calendar.
So
we
have
the
captain
community
git
repository.
A
So
if
you
go
here,
you
will
find
basically
everything
you
would
need
I
guess,
so
you
will
find
a
ways
how
to
communicate
and
get
in
touch
with
us.
You
will
find
information
on
the
latest
community
meetings.
You
will
also
find
the
meeting
calendar.
So
all
the
community
meetings
are
also
in
the
Google
Calendar,
so
make
sure
to
subscribe
to
miss
calendar.
You
have
all
the
other
links
here
and
then
you
might
not
have
seen
it,
but
it's
here's
another
list
of
other
captain
resources.
A
We
also
provide
here
a
link
to
the
captain,
Louis
that
you
can
use
if
you're
talking
about
captain
and
some
sly
fix
that
we
already
present
it
and
if
you
want
to
get
some
inspiration.
You'll
also
focus
here
and
I
said
the
resources
we
compile
a
list
of
resources.
So
if
you
ever
talk
about
captain,
if
you
write
an
article
about
captain,
just
let
us
know
or
open
a
PR
against
this
file
and
just
indicate
your
name
and
the
link
to
the
resource
that
you've
created.
A
A
That's
basically
it
from
a
very
short
introduction,
so
I'm
happy
to
see
also
some
new
captain
contributors
here
again,
if
you
want
to
start
with-
and
you
will
find
good
first
issues
by
this
link.
So
on
github
we
compiled
a
list
of
good
first
issues
and
we
already
got
a
couple
of
contributions.
The
last
weeks
so
I
think
finesse
to
community
meetings.
We
have
external
contributions
presenting
today
we
have
one
external
contributor
turning
the
meeting.
If
you
wants
a
presenter,
just
let
us
know
yeah.
A
Otherwise,
if
you
want
to
stay
in
touch
with
Captain,
make
sure
to
subscribe,
also
to
the
mailing
list
and
join
us.
It's
like
all
the
links
are
also
provided
at
the
top
of
this
document
and
I
shared
this
document,
also
in
the
chat.
So,
if
you're
joining
this
meeting,
you
should
be
able
to
find
all
those
links.
The
meeting
is
recorded
and
will
also
be
available
on
youtube
later
today
or
tomorrow.
A
B
So
there
is
not
much
to
show
yet,
but
the
UI
look
and
feel
of
the
bridge
has
changed
a
little
bit
and
let's
have
a
look
at
the
issue.
First
yeah.
It's
just
about
small
changes,
color
wise
that
the
font
size
has
changed
a
little
bit
and
also
the
visibility
of
failed
actress
has
improved
and,
as
usual,
I
will
do
a
live
presentation.
B
So
now,
when
you
enter
the
bridge,
you
will
see
the
left
menu.
The
color
of
the
left
menu
changed.
Also
the
the
fonts
of
the
labels
here
changed.
This
was
actually
a
bug
because
the
correct
fonts
were
not
loaded
in
the
previous
version,
since
we
use
the
barista
components
and
they
use
open
sense.
And
here
you
can
also
see
failed
event.
B
So
the
visibility
now
changed.
We
have
the
red
board
on
the
left
side
and
instead
of
just
the
border,
we
like
the
color
of
this
stages.
The
background
color
is
red,
so
it's
more
visible
yeah
and
the
background
colors
of
the
menu
on
the
right
top
sides
changed.
So
we
have
this
great
background
color
here
as
well
as
we
have
it
on
the
left
side
in
the
menu
yeah.
That's
actually
all
about
changes,
so
the
background
color,
the
shadow
of
the
header,
is
removed.
C
One
issue
of
keep
kept
eating
and,
as
you
probably
know,
kept
eating
here,
we
defined
the
goal
in
order
for
simplifying
the
installer
and
that
we
do
not
install
is
your
no
engine.
Eggs,
anymore
and
I
took
care
of
the
little
apart
and
here
I
removed
everything
related
to
Easter
and
nginx,
and
so
on,
and
by
doing
this
we
identified
that
we
do
not
need
any
script
anymore.
So,
basically,
we
only
have
to
apply
manifests
in
order
to
install
cap
and
that's
also
the
reason
yeah.
We
already
got
the
first
question.
C
So
I
identified
that
we
don't
need
a
script
anymore
and
therefore,
in
future
we
will
not
have
an
insular
part
anymore,
which
takes
care
of
the
installation.
Instead,
we
have
a
help
chart,
and
this
basically
is
one
really
large
request,
which
removes
lots
of
scripts
and
now
I
simply
would
like
to
show
you
how
you
can
use
their
old
read.
They
have
using
the
haven't
Eli
and.
C
C
Only
shimmy
now
it
should
be
better.
So
now,
I
repository
to
help
mature
code,
captain
latest
and
I'm
pointing
this
cabinet
is
repository
to
a
packet
inside
our
Google
Google
Cloud,
and
this
is
this-
is
accessible
from
the
outside
world.
So
what
I
can
now
do
and
I'm
lazy,
so
I'm
copying
command,
where
I
tell
him
to
install
exactly
a
new
release
which
are
called
helm,
which
is
contained
exactly
in
this
repository
and
also
the
chart
is
called
captain.
Then
I've
specified
a
namespace
and
I
also
set
some
values.
C
C
C
C
A
Would
have
a
question,
it's
this
one
point
or
another
way,
or
is
it
the
new
way
how
to
do
mix
it's
the
new
way
and
only
rate,
and
does
it
mean
that
you
need
to
have
help
installed
on
your
local
machine
because
you
just
installed
it
with
help
or
will
it
be
for
the
user
of
captain?
Will
it
be
the
same
experience
that
you
just
download
the
CLI
and
you
captain
install
and.
C
This
is
a
really
perfect
question
and
the
answer
is
the
user
will
have
the
same
behavior
as
before,
so
he
can
use
the
CLI
and
technically
the
captain.
Seal
I
contains
the
libraries
and
therefore,
in
the
background,
we
are
also
installing
captain
using
helm
in
the
silly,
but
the
user
does
not
have
to
have
had
an
installed
on
his
local
machine
right.
A
A
E
A
A
E
Problem,
yes,
this
printer
worked
on
two
items.
The
first
one
was
as
discussed
in
the
last
community
meeting
that
we
want
to
unify
the
API
and
bridge
on
the
ingress
on
one
on
one
service
so
that
we
don't
do
not
have
to
use
two
separate
host
names
and
therefore
also
no
to
not
not
need
to
use
C
by
one
people
anymore.
E
So
this
has
been
implemented,
and
currently
it
looks
like
this.
So
currently,
everything
on
my
host
is
exposed
on
and
the
API
came
in
and
so
on,
but
you
can
also
expose
it
directly
as
a
load
balancer
as
a
notepad
and
so
on,
and
if
I,
if
I
browse
directly
to
API,
kept
in
and
so
on,
I
will
get
directly
to
the
bridge.
E
A
E
E
E
D
E
G
E
G
Your
muted,
but
but
here
all
right
today,
I
want
to
show
you
four
full
requests.
The
first
one
considers
lighthouse
service
so
that
you
should
get
was
that
if
we
had
a
proceeding
test
execution,
for
example
by
the
change
the
service
and
test
run,
was
failing,
the
night
house
works
that
way
that
it
still
will
evaluate.
G
As
a
nice.
You
have
defined
in
your
as
an
AI
file
in
order
to
get
additional
information,
even
though
the
test
itself
explained,
and
the
way
it
works
in
that
case
is,
will
calculate
all
the
metrics
and
retrieve
them
and
calculate
score.
But
regardless
of
the
end
result
of
the
score,
it
will
overwrite
result
and
we
set
it
to
fail
because
the
preceding
test
run
has
failed,
and
the
issue
here
was
that
it's
was
not
performing
like
that
in
a
comprehensible
way.
G
G
G
If
you
export
it
cue,
convict
environment,
variable,
the
CLI
didn't
pick
that
up
and
still
use
the
cute
conflict.
That
was
said
fighting
for
that.
So
home
director
really
got
cube,
slash
conflict,
so
that
was
always
used
by
the
CLI.
If
you
wanted
to
use
another
cluster
by
exporting
that'll,
keep
kinetic
variable.
G
The
CLI
acknowledge
that
and
that
led
to
some
confusion,
especially
if
we,
for
example,
wanted
to
install
captain
on
mini
cube,
for
example,
or
metric,
even
at
this
very
usually
set
this
cube
config
file
variable
to
put
the
one
you
want
to
use
and
that
led
to
some
confusion
because
captain
and
try
to
install
itself,
maybe
the
brown
cluster
didn't
tend
to
install
it
on
and
that
has
been
fixed.
So
now,
if
you
set
the
cube,
frantic
variable,
he'll
I
will
use
that
keep
context
and
installer
captain
on
the
on
the
correct
cluster.
G
All
right,
let's
go
on
with
next
one,
so
this
is
young,
quite
a
big
change
in
terms
of
perspective
of
the
user.
So
if
you
recall
the
previous
calibrations,
when
you
executed
the
captain
install
command
without
any
other
parameters,
you
always
got
the
full
installation
and
only
by
adding
the
use
case,
quality
gates,
black
you
installed
the
captain,
horror
and
but
not
that
I
can
finish
the
delivery
services.
G
We
thought
it
would
make
more
sense
that
if
you
just
execute
the
cat
install
command
without
any
further
parameters,
you
would
just
get
the
core
and
then
you
can
extend
it
by
specifying
the
use
case
that
case
continuous
delivery.
So
this
is
not
gonna,
be
W
possible
of
ready
for
the
news
case
black,
and
that
way
you
will
get
the
new
installation,
but
yeah.
The
new,
normal
I
still
say
nowadays
will
be
been
a
core
installation
of
just
a
control
thing
which
will
support
the
quality,
various
cases
and
also
the
remediation
these
cases.
G
C
I,
don't
have
a
question
but
I've
a
nice
side,
Pro
side
effect
here.
So
if
you
decide
to
install
only
quality
gates
and
after
few
weeks,
you
would
also
like
to
use
captain
in
order
to
do
the
deployment
you
can
now
make
a
simple
health
upgrade
and
add
your
additional
components,
which
are
necessary
to
also
do
continuous
delivery.
G
G
This
change
was
necessary
because
assembly,
as
already
mentioned,
we
do
not
install
Easter
automatically
with
Captain
anymore,
but
you
can
provide
your
own
easier
installation
and
configure
it
in
a
way
that
you
that
best
fits
you.
So
now
you
can
also
bring
your
own
ingress
objects,
forest
you
and
do
not
have
to
rely
on
it
once
the
captain
automatically
set
up
for
you,
and
because
of
that,
we
had
to
introduce
a
way
for
the
user
to
configure
the
help
service
and
also
the
OpenShift
service
to
know
which
domains.
G
F
F
G
G
One
just
basically
extended
the
content
of
the
support
archive
by
checking
all
the
available
ingress
options
within
the
cluster,
so
basically
checks.
If
the
ingress
you
have
configured
is
reachable
and
the
types
of
services
that
are
being
deployed
in
the
cabinet
is
by
the
Installer
to
check
when
our
API
we
need
was
deployed
as
load
balancer
or
cluster
IP
or
node
port
and.
G
G
G
G
A
E
A
A
A
D
You
will
see,
come
on,
throw
it
so
here
we
have
there
good.
So
this
was
a
first,
the
first
one
and
let
me
quickly
just
getting
my
host
file
back
to
mom
state
and
the
second
one
was
cap.
Nobita
I
extend
the
captain
API
to
retrieve
metadata
of
the
captain.
Installation
was
labeled
as
good
first
issue,
I
have
to
say
no,
it
wasn't
a
good
first
issue.
It
was
actually
from
here
plane.
Yes,
well,
I'm,
sorry,
but
fun
made
it
so
now,
when
we
are
gonna
writing
support
archive,
we
can
write
one
you
can
see.
D
So
we
have
here
the
metadata
endpoint
introduced
where
we'll
return,
a
namespace
labels
version
bit
version
and
later
on,
captain
services
installed.
We
can
curl
the
API
endpoint
directly
right
now,
so
we
can
see
what
this
will
return.
So
if
the
bridge
version
captain
label
which
is
currently
set
to
to
captain
conversion
from
swagger,
UI
and
namespace,
and
last
but
not
least
in
the
can
I
rated
Support
Package.
D
F
Alright
yeah
I
have
two
issues:
I
want
to
share
with
you
folks.
The
first
one
is
that
yeah
a
while
ago,
Adam
reported
a
problem
with
mini
cube,
and
the
problem
is
that
when
you
have
mini
cooper,
cube
installed
on
your
machine
and
then
you
put
captain
mini
cube
and
you
start
and
stop
mini
cube
during
running
yeah
during
your
machine
is
running.
It's
everything
is
perfectly
fine,
but
when
you
reboot
reboot
your
your
VM
or
your
your
machine,
then
and
then
do
a
start
of
the
mini
cube
environment.
F
Then
there
is
a
problem
with
the
MongoDB.
The
problem
is
well-known:
it's
problems
the
permissions
of
the
of
the
of
a
local
folder,
and
we
agreed
to
not
address
this
problem
in
in
terms
of
a
captain
change,
because
it's
not
captain
related,
it's
Minnie,
Cube
related
and
thanks
to
our
Rockstar
Christian,
who
proposed,
or
we
gave
us
a
recommendation
how
to
fix
this
problem.
F
F
Alright,
then.
The
second
issue
is
a
problem
that
we
observed
in
the
last
couple
of
days
thanks
to
Emery.
He
also
brought
up
this
problem
and
it's
the
situation
that
a
captain
grade
project
does
not
work
because
and
it
does
not
work
when
you
specify
a
gear
ABS
upstream
to
github
repository
and
the
problem
is
that
since
a
couple
of
days,
it
takes
now
longer
to
clone
a
repo
from
github,
and
this
runs
into
a
timeout
on
the
captain
and
for
some
reason
it
takes
longer
than
five
seconds.
F
Alright
yep,
that's
from
my
end
now,
let's
move
on
yeah
I
heard
that
in
the
last
couple
of
community
meetings
you
heavily
discussed
the
cap.
18
and
andreas
showed
us
today
really
great
progress
on
this
cap,
and
this
cap
is
currently
driving
the
road
map
and
when
we
are
done
with
implementing
all
the
issues
for
cap
18,
then
we
are
ready
to
release
auto
7,
and
this
is
the
reason
why
I
want
to
now
go
on
to
the
broken
items.
F
Thanks
a
lot
for
that
because,
as
you
can
Umbra,
as
you
can
see
here
in
the
progress
column,
I
have
two
issues.
One
is
simplifying.
The
installation
and
I
will
take
care
of
updating
the
documentation,
and
the
second
issue
that
also
corresponds
to
cap
18
is
that
we
need
to
provide
documentation
how
to
expose
services
that
your
deploying
with
captain
and
therefore
I
also
I'm,
also
working
currently
on
an
issue
which
is
called
configure.
East
your
from
continuous
delivery,
all
right.
F
A
H
Can
you
see
it
yeah?
Okay?
So
this
is
the
issue
that
basically
it's
removed
the
platform,
several
options
from
platform
flag.
So
previously
we
have
many
installation
for
a
KS
e
KS
g
KD
and
the
gatsby
hotel,
cabana
self-assessing,
and
we
basically
remove
this
core
and
then
just
left
this
to
kubernetes
and
awkward
open
ship,
and
we
basically
make
the
kubernetes
as
a
default
value
if
user
doesn't
specify
any
platform.
I
think
that's
all
from
my
n.
H
F
F
All
right,
yeah
and
I
will
again
take
over
control
of
the
screen
and
I
already
updated
the
column
for
ready
for
review,
and
here
we
have
still
to
pull
requests
to
get
merged
and
floran
is
discussing
this
issue
next
time.
In
the
progress
column,
we
have
that
one
captain
configure
bridge
don't
expose
the
service.
F
Airman
and
I,
we
were
together
working
on
updating
the
documentation
for
the
captain
bridge.
Tomorrow
we
will
have
a
final
review
and
when
the
previous
done,
we
will
close
that
issue
and,
as
I
already
mentioned,
I'm
also
working
on
updating
the
documentation
for
the
install
process
and
also
for
exposing
services
that
get
deployed
by
captain.
F
C
F
Mm-Hmm
I
mean
from
an
implementation
side.
You
are
done.
You
showed
us
today
that
helm
no
upgrade
on
help
install
works
and
yeah
I'm.
Okay,
in
closing
this
one
and
I
all
really
want
to
ask
you
for
your
help
too,
to
get
those
two
documentation
issues
directly
done,
then,
are
you
okay,
when
I
move
it
over
to
ready
for
review
or
actually
to
close
it?
You.
F
Let's
close
it
perfect
and
let's
do
a
joint
work
on
updating
the
documentation.
Sure,
thanks
and
here
just
have
a
reminder
that
when
we
are
released
Kepner
at
7:00,
we
also
should
Deborah
should
make
the
jmeter
extended
service
and
deprecated,
and
the
captain
country,
people
cool
and
now
yeah.
This
brings
me
to
the
backlog:
let's
have
a
few
in
the
black
backlog
and
issues
that
are
ready
to
get
implemented
and
like
every
week,
I
asked
you
guys
to
raise
your
hand
whenever
you
want
to
do
a
certain
task.
F
H
F
F
F
F
F
B
F
B
G
C
Yeah
this,
if
you
need
discussion,
we
we
have
to
wrap
our
head
around
this.
How
we
can
do
this
because,
in
the
background
we
do
not
have,
for
example,
are
quite
I
mean
which
can
be
applied
without
hand
anymore.
So,
let's
discuss
on
the
issue
how
to
proceed
here
and
then
we
can
assign
some
fix
here.
Okay,.
F
All
right
guys,
yeah
today,
I
pulled
into
two
issues
and
I.
Think
the
core
team
knows
what
what
those
two
issues
mean.
The
first
one
is
preparing
the
captain
over
at
seven
documentation
and
double
checking,
whether
all
the
features
are
probably
documented
and
and
explained,
I
already
created
a
pull
request
and
a
branch
on
the
documentation
where
we
can
all
work
on
and
update
the
documentation,
the
way
it
should
be,
and
last
but
not
least,
it's
the
release
over
seven
issue
and
yeah.
F
F
F
F
F
F
F
After
we
have
a
release
branch,
where
we
have
a
possibility
to
test
the
new
version,
then
we
are
going
over
to
a
preparation
phase
where
we
double-checked
documentation,
then
also
the
tutorials
have
to
get
updated,
and
when
this
is
done,
we
will
then
test
captain
on
different
kubernetes
versions.
That's
a
cheeky
e
or
an
open
chef
cluster
or
a
mini
chef
cluster,
we're
testing
captain
on
and
then
finally
yeah.
We
go
over
to
officially
release
the
contra
pieces
as
well
as
as
Captain.
F
A
So
it's
still
okay
to
indicate
any
time
next
week
to
be
included
in
this
releasing
process
and
to
take
over
some
some
testing
efforts.
There
are
also
the
tutorials
that
will
be
updated
or
have
to
be
updated
to
match
the
new
release,
because
we
actually
once
the
release,
is
out.
We
encourage
all
the
folks
to
use
the
newest
release
and
not
to
use
not
to
on
a
new
installation
not
to
go
with
the
with
the
previous
version
anymore.