►
From YouTube: Keptn Community Meeting - June 18th, 2020
Description
Meeting notes https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit#heading=h.soc9vznzl3lk
June 18, 2020
Community Rockstar 🚀 program launched
Good first issues: https://goodfirstissue.dev/ or start here
Keptn mailing list / google group: https://groups.google.com/forum/#!forum/keptn
Community feedback:
Gabriel Prioli: can’t join today
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:
Require user/password for exposing CLI:
https://github.com/keptn/keptn/pull/1915
New Remediation-Service:
https://github.com/keptn/keptn/issues/1849
Ermin:
Notify user of new available Keptn Bridge in UI
Notify user of new available keptns bridge in UI · Issue #1547 · keptn/keptn
Bridge EAP https://keptn.sh/docs/0.6.0/reference/keptnsbridge/#early-access-version-of-keptn-bridge
Andreas:
RBAC https://github.com/keptn/keptn/issues/1862
Example configuration-service https://github.com/keptn/keptn/blob/master/installer/manifests/keptn/rbac.yaml
https://github.com/keptn/keptn/blob/master/installer/manifests/keptn/core.yaml
Contributing guidelines https://github.com/keptn-sandbox/contributing
Johannes:
Split of Upgrader (with/without helm upgrade), update of release notes: https://github.com/keptn/keptn/pull/1914 +
keptn/docs: https://github.com/keptn/keptn.github.io/pull/560
Move Keptn's MongoDB Credentials into a Kubernetes secret: https://github.com/keptn/keptn/issues/1528
Christian K.:
KEP 18 for Installer Changes: https://github.com/keptn/enhancement-proposals/pull/18/files
Zohaib:
https://github.com/keptn/keptn/pull/1922 (has not been presented)
Roadmap → KEP / SPEC / Issues:
KEP 09 - Spec change of remediation action config
SPEC 31 - Implementation of spec change as proposed in KEP 09
#1846: Testing: Platform/integration test for self-healing use case
#1847: Testing: Integration test for use-case of scaling a pod based on a Prometheus alert
Work in progress:
https://github.com/keptn/keptn/projects/29
Backlog Refinement / Next Sprint:
see 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
So
we
have
a
lot
of
folks
in
the
capital
community
and
we
know
the
community
is
doing
great
and
a
lot
of
people
are
putting
a
lot
of
effort
into
the
community
work
and
they're
contributing
to
capture
and
you're
writing
extensions
for
Captain.
So
we
thought
about
kind
of
bringing
a
program
to
life,
to
appreciate
those
people
and
the
community
program.
You
might
have
already
seen
it
in.
We
have
a
small
description
on
the
community
page.
A
So
your
name
does
not
show
up
here
at
the
moment,
but
I'm
sure
the
PR
will
be
merged
quite
fast.
So
congratulations,
Christian!
You
are
awarded
our
first
community
rock
star
thanks
so
much
for
your
work
on
the
captain
core
on
the
on
your
gift
life
contributions.
You've
done
a
webinar
together
with
envy,
so
you've
really
shown
all
those
excellent
contributions
in
the
thank
you
so
much
from
the
whole
captain
community
for
you.
Thank
you.
It's
big.
A
A
Thanks
Christian
again
for
all
your
you're
working
contributions
to
captain
yeah
thanks:
oh
maybe
it's
maybe
a
minor
detail
here-
can
be
used
like
the
github
names
and
linked
them
sure.
Absolutely
so,
if
you
don't
mind,
can
you
just
file
up
your
against
against
this
and
we
will
merge
it
again.
So,
let's
see
if
we
can
do
this
meeting
so
if
you
also
want
to
become
a
community
rock
star,
it's
kind
of
a
good
segue
to
the
next
point.
You
can
start
with
some
good
first
issues.
A
We
are
still
listed
always
listed
since
a
couple
of
weeks
on
the
good
first
issued
top
def
website
and
also
there
is
a
link
to
good
first
issues.
So
we
always
have
a
couple
of
good
first
issues
and
actually
later
in
this
meeting,
I'm,
not
sure
if
we
have
more
community
members
joining
this
meeting,
but
we
have
already
some
good
first
issue
contributors
since
last
week.
So
that's
that's
pretty
amazing.
If
you
want
to
stay
in
touch,
it's
like
the
usual
ways
to
Anna's
on
slack.
Follow
us
on
Twitter
also
join.
A
It
kept
a
mailing
list.
We
are
announcing
here
also
new
public
speaking
events.
We
are
doing
quite
regularly,
meetups
and
webinars,
so
if
you
turn
it
from
the
Google
Group
and
all
the
feet,
all
the
updates
directly
to
your
inbox
I
think.
The
next
part
we
can
skip
Gabriel
was
actually
asking
for
some
discussions
with
the
captain
team,
but
unfortunately
it
can't
run
today
so
we're
skipping.
This
and
yeah
I
think
I'm
handing
over
to
Florian
I
guess
to
present
some
of
them
is
PRS
like
this
Bob
here
all
right.
Thank
you
here.
D
C
Now
we
have
two
mandatory
additional
parameters,
which
is
the
user
and
the
password,
and
it
works
just
as
you
would
imagine.
As
you
know,
if
you
execute
that
command,
the
bridge
will
be
secured
by
a
basic
authentication
automatically
and
yeah.
Here
is
the
full
request
for
that,
where
I
found
what
message
to
do
that?
Also,
since
we
introduced
additional
role
based
access
control,
restrictions,
I've
also
outlined
the
required
permissions
for
the
API
service.
That
does
the
actual
configuration
of
the
humanities
resources
in
order
to
enable
their
bridge
access
all
right
there.
Any
questions
about
that.
C
C
C
Maybe
let's
look
at
at
the
issue
that
you
described
here
so
basically
in
order
to
to
support
the
new
kind
of
remediation
workflow,
where
you
are
able
to
define
multiple
actions
for
several
kinds
of
problems
in
order
to
step-by-step
execute
those
actions
evaluate
if
they
have
reached
the
desired
effect
and
then,
if
necessary,
execute
the
next
action
and
so
on.
We
had
we
implement
a
remediation
service
and
this
one
now
again
listens
to
captain
the
problem.
But
open
events
then,
basically
triggers
the
first
action
that
has
been
found
for
this
kind
of
problem.
C
Then
waves
or
also
updates
the
status
of
the
current
remediation
workflow
in
the
configuration
service
and
as
soon
as
an
action
has
been
finished,
it
evaluates
or
waits
for
a
certain
amount
of
time
and
evaluates
the
remediation
action
waits
for
response
of
the
SMI
service
of
the
lighthouse
service
in
order
to
to
check
the
evaluation
and
then,
if
necessary,
execute
the
next
action
and
so
on.
Until
the
remediation
has
been
finished
or
until
there
are
no
further
action
is
defined
in
the
remediation
file,
and
that
was
a
lot
of
talking.
C
So
maybe
just
look
at
sample
remediation
workflow
in
the
bridge.
So,
as
you
can
see
here
we
have
the
problem
open
event
and
then
the
remediation
workflow
has
been
triggered,
which
also
caused
the
status
change.
An
action
has
been
executed.
In
that
case
a
feature
total
has
been
done
and
the
action
has
started
finished.
The
evaluation
has
been
finished.
C
In
that
case
it
didn't
reach
the
sorry
effect
and
then
the
next
action
has
been
executed,
and
that
case
the
evaluation
also
failed,
but
we
don't
have
an
answer
I
provided,
but
in
that
case
we
ran
out
of
actions
and
remediation
workflow
is
finished
and
also
if
you
want
to
look
at
the
detailed
flow
of
events
during
that
workflow,
you
can
look
at
this
issue
here.
There
are,
unless,
through
a
sequence
diagram
by
the
time
of
the
whole
workflow
and.
A
D
You
very
much
yeah
as
I'm,
basically
working
on
the
captain's
bridge
I'm
going
to
present
you
for
request
that
I
actually
already
announced
last
time
with
the
possibility
to
notify
users
and
now
we're
using
that
feature
to
notify
you
about
a
new
available
captain
bridge
in
the
UI.
So,
basically,
the
idea
is
that
we
have
a
version
Jason
where
we
now
are,
or
the
version
of
the
latest
captain's
bridge
that
is
available
and
we'll
show
you
a
notification
on
top
of
the
bridge
when
there
is
a
new
version
available
behind
that
feature.
D
There
is
a
lot
more.
There
is
also
use
the
User
Content
can
enable
or
disable
this
functionality,
because
we
of
course
collect
statistical
data
when
you
enable
that
feature
and
for
when
you
have
that
feature
enabled
you
will
get
that
notification.
I
have
also,
as
always,
a
short
demonstration
of
that
one
in
a
bridge
that
I
have
deployed
on
my
demo
cluster
when
you
start
a
bridge
with
this
version
check
for
the
very
first
time
you
get
notified
about
this
new
feature,
and
you
can
opt-in
to
activate
it.
D
So
as
long
as
you
don't
have
activated
it
or
haven't
used
it,
yet
you
get
the
information
that
there
is
no,
this
new
feature
available
and
you
can
decline
or
accept
that
one
here
and
of
course
you
can
always
change
your
decision
here
on
the
right
top
corner
in
this
user
menu,
where
you
can
see
your
current
captain
version
and
that
current
bridge
version-
and
in
my
case,
because
I
have
your
bridge
deployed
that
is
in
development.
It
says
that
there
is
an
invalid
version
for
this
automatic
version
check.
D
So
it
cannot
execute
this
version
check.
But
of
course,
I
also
have
example,
which
demonstrates
the
notification.
So
here
I
have
the
bridge
version:
0,
7,
0,
minus
EAP,
so
an
older
EAP
version
of
the
bridge
deployed,
and
it
says
there
is
a
new
captain
bridge
0
7
0
EAP
20
2006
17
available,
and
it
says
also.
This
is
a
pre-release
version
that
might
contain
experimental
features.
So
please
be
aware
of
and
for
details.
D
E
We
already
have
in
the
role
which
now
allows
you
to
create,
get
and
also
to
meet
secrets,
but
only
missing
the
captain
namespace,
because
this
is
a
this-
is
road
and
not
the
classroom.
So
this
role
is
limited
to
the
captain
instance
and
finally,
you
have
to
bind
this
role.
This
kept
many
secrets
or
to
the
service
accounts
to
the
captain,
configuration
service
account
and
therefore
you
can
use
this
role
by
name.
A
That's
nice,
so
I'm
a
code
person,
I
hate,
reading
instructions,
I
rather
look
at
TIFF
files.
Would
it
be
possible
that
we
just
linked
the
pull
requests
in
our
contributing
guide,
so
people
can
refer
to
the
pull
request
as
an
example,
because
there's
a
lot
of
written
things
and
in
reality
it's
like
10
lines
of
of
Yama
file
that
you
have
to
edit.
So
it
sounds
more
complicated
than
it
actually
is
sure.
A
F
Okay,
now
you
can
see
my
screen
and
hear
my
voice.
Well,
I
was
working
on
two
issues.
I
want
to
present
today.
The
first
one
is
that
we,
as
a
team,
decided
to
split
the
upgrader,
the
upgrade
mechanism
into
two
versions,
so
to
say
one
that
automatically
converts
helm,
2
releases
into
Helms
really
releases.
This
is
the
recommended
way
when
you
have
environment
where
our
trusts
running
captain
and
the
second
upgrader
doesn't
know
upgrade
of
the
helm
releases
but
provides
yeah.
Doesn't
it
does
no
upgrade,
but
we
still
provide
our
instructions.
F
How
you
can
do
that
then
manually,
and
this
is
shown
in
the
upgrader
documentation-
and
this
is
where
I
want
to
go.
Next,
let's
have
a
look
on
the
documentation
here.
You
can
see
yeah
well,
the
upgrade
mechanism
from
captain
ordered
6
2
to
2
or
at
7,
and
here
we
highlight
that
captain
ordered
7,
uses,
helm,
3
and
also
the
consequences
when
you
don't
convert
your
helm
releases
and
also
be
aware
that
helm
2
will
be
end-of-life
or
they
will
stop
to
support
helm
to
in
starting
with
August
13th.
F
And
here
are
the
explanations
for
the
two
chops:
the
first
one
is
without
doing
the
helm,
upgrade
it's
just
executing,
then
the
kubernetes
job
young,
as
mentioned
here,
it's
the
upgrade
chop
tamil
and
below
you-
will
find
all
the
instructions
to
convert
your
helm
releases
manually
yeah.
You
need
to
help
file
to
CLI,
then
the
helm
of
our
three
CLI
and
then
you
get
all
your
helm
releases
on
your
cluster
by
doing
a
helm
list
a
cuckoo
and
we
step
plug
in
you
need
to
install
in
this
step,
helm
three
plug-in
install.
F
You
then
can
manually
convert
all
your
helm
releases
from
two
to
three
and
finally,
when
you
want
or
when
you
don't
need
tiller
anymore
on
your
cluster,
you
also
can
use
this
plug-in
by
doing
a
cleanup,
and
this
removes
tiller
from
your
community
system
and
in
case
you
have
a
environment
where
it's
just
running
at
none
here,
then
you
can
use
the
upgrader.
That
automatically
does
the
job
that
is
written
down
here
and
therefore
you
deploy
the
kubernetes
job.
F
A
C
A
A
Before
you
hand
over
to
Christian,
because
there
was
some
discussion
in
the
chat
and
I
just
realized
that
I
think
by
accident,
it
has
been
restricted
to
only
I
think
to
only
panelists.
So
I
would
like
to
ask
Andy
to
basically
also
talk
about
your
question.
You
have
in
the
chat
you're
out
in
the
meeting,
because
attendees
could
not
read
the
question
and
also
could
not
read
the
answer
from
Florian.
G
Thanks
for
the
reminder,
for
whatever
reason,
I
couldn't
post
it
in
QA,
that's
where
I
used
to
Chet
and
I
accidentally
just
said
panelist.
It
was
my
mistake.
Yes,
my
my
question
was
what
is
actually
happening
at
the
end
of
the
remediations
when
nothing
wrong,
the
problem
is
actually
not
solved
and
I
was
wondering
in
case.
We
have
any
option
to
then
say
in
case
of
success,
to
something
or
in
case
of
failure.
Do
something.
C
That's
a
good
point
and
actually
that
in
this
case
we
profit
from
the
event
based
approach.
We
have
here
in
captain
because
this
could
be
implemented
by
writing
a
custom
service
that
simply
listens
to
the
remediation
that
finished
events
and
in
those
events,
we
have
the
information
whether
remediation
workflow
has
been
successful
or
not,
and
depending
on
that
information,
we
act.
Yeah.
G
No,
that's
actually
good
point,
because
that
would
mean
it's,
let's
say
in
case
of
success
and
may
get
a
select
notification,
because
this
like
service,
is
listening
for
that
or
in
case
of
a
failed
remediation.
I
could,
let's
say,
use
a
ServiceNow
integration
and
then
have
it
create
a
ticket
to
escalate.
G
I'm
just
I'm,
just
wondering
I
mean
this
is
obviously
all
possible.
It's
great
still
wondering
if
we
should
for
future
consider
a
in
the
remediation
files,
a
in
on
era
and
an
on
success.
Look
I,
don't
know
ma'am
I
may
overthink.
This
whole
thing,
I
think
what
you
are
explaining.
What
your
answer
was
perfect
right,
because
I
have
the
full
flexibility,
but
just
thinking
out
loud
if
it
makes
sense
to
extend
it
in
the
future.
G
F
Can
maybe
two
to
explain
it
to
order
to
show
it
to
everyone?
I,
with
this
remediation
use
case
that
florian
showed
us
today,
you
have
the
possibility
to
add
as
many
actions
as
you
want
to
your
remediation
workflow.
In
this
case
it
was
revelation
workflow
of
two
actions
scaling
and
it
was
both
what
was
a
toggling
of
a
future
flag,
but
that
you
can
also
add
a
third
one,
and
this
could
also
be
an
escalation
step.
A
So
I
have
a
task.
That's
actually
a
task
for
all
of
you.
We're
currently
thinking
a
little
bit
internally.
How
we
can
do
captain
installation
in
the
future
and
that
led
to
a
discussion
about
why
do
we
need
to
install
SEO
and
nginx
ingress
and
I
have
here
the
captain
enhancement
proposal
number
eighteen,
that
I'm
asking
all
of
you
to
read
and
to
comment
on
and
I'm
just
going
to
quickly
go
or
the
main
things
that
this
enhancement
proposal
is
proposing.
A
So
the
main
thing
is
the
cap:
nîmes
dollar
should
no
longer
automatically
installed
sto
or
nginx
ingress
and
Captain
API,
as
well
as
bridge,
are
also
no
longer
exposed
using
a
nice
new
virtual
service
or
any
ingress
objects.
Instead,
what
we
want
to
do
is
we
want
to
expose
API
and
bridge
why
our
plain
old
Cuba
needed
services
of
type
note
port
or
load
balancer.
A
If,
if
that's
what
the
user
wants
to
do,
I'm
gonna
skip
the
motivation
behind
this
feel
free
to
read
and
comment
on
this
and
I'm
gonna
just
go
over
to
what
it
will
feel
like
to
the
user.
So
for
the
user
there
will
be
two
flags
provided
in
the
Installer.
The
first
one
is
the
captain
API
service
type,
which
can
be
either
a
cluster,
be
note,
port,
a
load
balancer
and
the
captain
bridge
service
type,
which
has
the
same
options
available
and
for
both
options.
A
Cluster
IP
will
be
the
default
option,
so
by
default,
your
captain
installation
will
not
be
reachable
from
the
outside,
which,
in
my
opinion,
is
a
really
smart
default
in
terms
of
security.
So
if
you
don't
know
what
you're
doing
the
first
thing
you
will
have
is
cluster
P,
and
you
can't
do
anything
wrong
with
that.
If
you
don't
want
to
access
your
captain
cluster,
you
can
either
use
a
plain
old
human
nearest
port
forward.
A
If
you
really
want
to-
or
you
always
have
the
option
to
manually
edit
your
service,
for
instance,
using
cube,
cuddle
and
set
the
type
to
node
port,
a
load
balancer
afterwards.
So
there
is
nothing
that's
being
happening
here
that
can
prove
that
cannot
be
reverted
or
that
is
like
locked
in
or
something
you
can
edit
this
afterwards.
A
All
the
time
and
the
main
benefit
that
I
see
from
this
approach
is
that
we
are
only
relying
on
human
neatest
features
and
not
on
like
SEO
or
nginx
ingress,
and
this
will
make
troubleshooting
API
or
bridge
issues
regarding
IPS
that
are
being
exposed
or
not
a
lot
easier
in.
In
addition,
right
now,
captain
is
managing
so
many
things
in
a
background
using
SEO
and
virtual
services
like
SSL
Certificates.
This
is
no
longer
a
thing.
If
we
implement
this,
it's
something
that
the
user
now
will
have
full
control.
A
So
if
you
already
have
a
nice
new
installation
with
SSL
configured
and
other
things
configured,
it's
quite
easy
to
just
expose,
API
or
bridge.
Why
are
your
existing
SEO
installation
using
ingress
manifests
or
virtual
services?
And
you
don't
have
to
rely
on
captain
doing
that,
for
you
all
right,
there's
a
lot
more
to
this,
especially
from
a
technical
standpoint
which
I'm
not
going
to
discuss
here.
We
can
discuss
this
on
the
enhancement
proposal.
A
B
I
only
had
one
little
PR
I
can
I
can
share
it.
For
a
second
give
me
a
second,
so
it's
really
complicated
and
a
lot
of
changes,
so
I
added
a
string
and
print
out
the
string
is
good.
Upstream
repository
was
not
defined
with
the
cut
and
create
project.
So
that's,
basically
it
all
right.
So
this
week
I
I
had
the
lazy
task.
It's.
B
A
Awesome
yeah,
but
thanks
anyway,
that's
cool
then
take
a
look
at
the
next
one,
so
I
think
he
had
to
drop
out
of
the
meeting.
I
cannot
see
him
anymore
in
the
meeting.
Unfortunately,
he
dropped
out
properly.
He
will
make
in
his
work
in
next
week's
meeting,
so
we
can
basically
skip
this
part
if
he
comes
back.
We
can
always
go
back
to
this
and
take
a
look
otherwise
I
will
hand
over
to
since
it's
a
spec
change,
maybe
to
Andreas
or
your
honest
or
Christian
I'm,
actually
not
sure
and.
F
Well,
yeah:
this
is
again
on
this
back
that
is
driving
the
roadmap
right
now.
The
spec
change
and
it's
all
about
the
remediation
the
enhancements
regarding
the
remediation
workflow,
but
us
work.
Lauren
showed
us
today,
it's
working
right
now
and
it's
working
fine
I
also
proved
it,
and
what's
now
missing
is
testing
testing
it
out
and
yeah.
Therefore
we
need
to
do
those
two
issues:
testing
it
in
sense
of
an
integration
test
and
also
testing
it
in
sense
of
an
end-to-end
scenario
using
parameters
for
monitoring.
F
F
C
Which
was
multi
service,
WebSocket
logging?
Simply
because
we
don't
need
it
right
now,
and
it
would
require
too
much
effort
that
we
can
concentrate
on
other
issues
right
now,
so
yeah
from
a
user
perspective,
it's
not
too
spectacular!
So
that's
why
I
chose
to
not
present
it
today
because,
as
the
neighbor
says,
it
was
a
chore
for
the
user
hurt.
Nothing
has
changed.
C
C
F
A
A
The
last
time
when
I've
shown
like
the
integration
test,
that
they're
running
their
own
keys
and
stuff,
like
that,
so
yeah
we've
also
updated
the
docs
to
have
some
information
about
what
to
do
when
installing
captain
on
keys,
it's
it's
more
about
like
having
an
experience
of
downloading
and
installing
keys
and
then
immediately
installing
captain,
and
it
just
works
quite
nicely
and
on
that
subject.
I
also
just
want
to
note
that
there
is
like
I,
think,
there's
a
youtube
video
now
available
about
installing
captain
on
keys
with
a
single
command.
So.
B
D
F
A
F
D
F
F
B
F
F
A
F
F
F
The
problem
is
that
in
the
remediation
llamó
that
we
specify
in
the
spec,
we
say
version
o
dot
too.
But
when
we
take
a
look
at
Kuni
this
manifests,
then
they
have
the
naming
of
API
version,
which
makes
which
is
semantically
stronger,
and
we,
as
a
team,
agreed
on
that
that
we
also
want
to
to
name
our
manifests
or
to
specify
the
version
of
our
manifest
by
using
the
property
API
version,
and
then
the
value
should
be
spected,
captain
dot
s
age
and
at
the
end,
diversion
or
the
released
spec
version.
F
F
F
Okay,
I
think
there
is
already
a
comment
on
that
issue.
Let
me
just
scroll
down
yep
Christian
is
asking
for
that
one.
What
can
you
can
I?
Take
it
yeah
thanks
great
yeah.
The
idea
is
that
the
API,
the
captain
API,
provides
an
endpoint
and
when
sending
a
request
to
the
endpoint,
you
get
then
made
the
information
about
your
captain
deployment.
This
is
the
API
ul,
the
bridge
URL,
in
which
namespace
its
installed
and
also
which
version
is
installed
for
captain
itself
and
the
bridge
just.
A
E
B
F
E
B
A
A
The
the
problem
is
that
and
Adam
has
commented
that
below.
If
you
install
captain
on
a
mini,
cube
virtual
machine
and
you
shut
down
that
virtual
machine
instant.
If
again,
there
seems
to
be
some
problem
with
the
permissions
for
the
MongoDB
data
folder
and
as
a
first
step,
it
would
be
nice
to
reproduce
the
issue.
A
So
basically,
the
entrance
area
here
or
a
drip
area
here
is:
can
you
run
mini
cube
in
a
virtual
machine?
If
you
can,
then
this
is
you
can
try
out
to
install
captain
and
then
add
some
data
and
reboot
the
virtual
machine
and
see
if
things
still
work
or
if
the
behavior
that
Adam
described
is
happening.
I
have.
G
A
So,
in
my
opinion,
it's
not
that
important
to
support
mini
cube,
but
I
know
many
people
or
many
developers
use
mini
cube
as
their
preferred
options.
So
I
don't
know
if
that's
a
good
idea
to
just
dismiss
mini
cube,
but
if
we
can
collect
a
couple
of
issues
and
we
can
see
that
these
are
related
to
mini
cube
and
not
captain,
then
sure
I
mean
so.
B
G
And
we
also
had
other
people
like
Alex
was
reporting
today
that
he
had
issues
on
mini
cube,
I
mean
he
I.
Think
here's
some
other
things
as
well
going
on
on
this
machine,
but
also
instability,
issues
of
mini
cube
and
the
resource
consumption
is
higher
right,
just
just
pointing
it
out
there
I
have
it
feels
for
me
that
we
have
better
alternatives.
That's
what
I
wanted
to
say.
A
F
B
B
C
F
Okay,
then
now
we
are
going
or
coming
to
preach
related
issues.
The
first
one
is
when
you
are
installing
cap
in
the
first
time,
and
you
have
no
service
on
boarded
or
deployed,
then
it's
kind
of
surprising
or
you
don't
get
any
information.
What's
going
on
in
your
environment
and
I,
also
kind
of
yeah,
all
right
kind
of
is
surprising.
F
A
F
E
A
A
E
A
F
A
I'm
against
that,
because
that
would
mean
that
we
have
captain
the
captain
repository
and
we
reference
something
that's
in
captain
contrib,
so
I
would
like
to
repository
to
be
self
contain
as
much
as
possible.
So
if
we
install
a
meter
extended
service
with
the
captain
installer
automatically,
it
should
be
in
a
captain
repository.
A
F
All
right,
then,
let's
continue
with
the
next
one.
It's
about
captain
an
install
on
an
open
shift
environment.
They
are
it's
the
problem
that
we
recommend
to
delete
open,
so
open
shift
namespaces
and
that's
not
what
we
should
recommend
and
the
inst
in
the
uninstall
command,
and
the
idea
is
that
we
we
simply
skip
namespaces
or
don't
you
name
spaces
that
start
with
an
always
open
shift.
I.