►
From YouTube: Keptn Community Meeting, APAC/EMEA - Feb 02, 2022
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 newsletter: https://bit.ly/KeptnNews
A
Okay,
we're
being
recorded
now
yeah,
so
today
is
february
2nd
and
the
first
topic
we
have
in
the
agenda
is
captain
developer
meeting.
So
currently,
what
we
have
for
votes
is
that
there
is
a
preference
for
having
meetings
at
8
a.m.
Utc,
so
9
a.m,
utc
either
on
wednesday.
So
basically
it's
current
time
slot
for
epac
community
meeting
or
on
thursday,
and
the
question
is
actually
how
we
organize
that,
because
historically
we
had
two
types
of
meetings.
A
B
Actually,
I
would
vote
for
continue
the
way
it
was
meaning
that
every
second
week
we
have
a
more
engineering
or
development
focused
meeting
and
the
other
week.
We
are
open
to
the
community,
I
mean
also
in
the
other
meeting,
but
it's
then
more
driven
by
topics
that
are
currently
ongoing
in
a
broader
scope
and
not
sprint
related.
B
I
think
the
only
thing
which
will
date
and
the
time
will,
as
it
looks
currently
will
move
to
thursday
from
10
to
11
pm
am
so.
We
combine
those.
A
Yeah,
so
what
we
could
do,
then
so
yeah,
we
can
say
that
we
start
coming
developer
meetings,
I'm
not
sure
starting
from
tomorrow
or
maybe
starting
from
the
next
week,
maybe
next
week,
and
we
start
them
on
thursdays.
A
Then
we
have
meetings
for
community
in
apec
region.
We
can
keep
them
as
is
on
wednesday,
or
we
could
also
move
them
to
thursday,
and
we
will
still
have
captain
community
meeting
every
other
week
at
5
pm
4
pm
utc,
which
is
usual
time.
C
I
think
if
I
could,
if
I
could
just
put
my
opinion
here,
that
the
the
individuals
in
apac
are
heavily
developer
focused
anyway,
so
I
don't
think
they
would
necessarily
mind
listening
into
the
development
topics.
I
don't
think
that
would
knowing
the
people.
I
think
it
would
fit
quite
well.
A
So
well,
the
developer
meeting
remains
open
to
everyone,
so
it
will
be
just
become
a
pack
friendly.
So
everyone
is
welcome
to
join
then
well.
We
can
see
what
they
we
need:
a
separate
community
painting
so
for
today
we
had
actually
two
items
so
for
brett,
marco
and
famika
present
today,
captain
experiences
but
they're
not
on
the
course.
So
I
guess
it's
going
to
be
moved
and
yeah.
If
it
gets
moved,
then
again,
then
we
might
have
a
question
whether
we
keep
doing
separate
meetings.
A
But
let's
see
so
I
suggest
that
for
the
next
week
we
meet
on
thursday,
and
then
we
see
whether
we
have
enough
attendance
for
the
community
meeting
in
two
weeks.
A
Let's
work
for
everyone,
then
we'll
keep
it
as
this
and
then
yeah
adjust
as
we
go.
A
Okay,
so
another
important
news,
so
we
have
mike
on
the
call
so
mike,
joins
to
contribute
to
captain
documentation,
tutorials
and
other
topics
so
mac.
Would
you
like
to
introduce
yourself
sure.
D
Hi
everybody-
I
am
so
happy
to
be
here-
I'm
excited
it's
my
day,
two
and
a
half,
so
we've
still
funding
some
of
my
thoughts
going
in
we'll
get
more
details
and
actions
soon,
but
in
general
we
want
to
make
the
documentation
a
comprehensive
collect
of
the
information
that
all
users
need
to
be
successful
with
captain,
and
we
want
to
get
it
structured,
easily,
locate
the
information
they
need
easier
said
than
done.
It
will
be
an
ongoing
project,
but
we'll
work
on
it.
D
What
this
means
potential
users
who
are
just
curious,
can
quickly
set
up
an
evaluation
copy
of
captain
to
explore
its
features.
D
I
know
for
years
I
personally
was
a
big
fan
of
open
source,
but
I
think
I
knew
enough
to
contribute
anything
really,
and
then
I
discovered
that
even
just
coming
in
and
editing
other
documentation
or
commenting
on
it
or
testing
it
was
invaluable
to
the
community.
So
we
want
to
get
more
people
involved
in
the
contribution.
D
We
also
want
to
ensure
that
people
who
contribute
software
to
the
kept
in
project
have
support
if
they
need
some
help
getting
the
documentation
done.
Their
new
software
will
become
part
of
captain
and
we
want
the
new
documentation
to
be
excellent,
but
my
experience
over
the
years
there
have
been
a
few
sterling
exceptions,
but
most
people
who
write
great
software
are
either
not
great
writers
or
I've
met
some
that
were
fabulous
writers,
but
they
hated
every
minute
of
it.
D
So
we
want
to
make
this
a
pleasant
thing
and
be
there
to
support
them,
so
those
are
sort
of
my
goals
that
I'm
thinking
of
as
we
get
started
here.
I
look
forward
to
hearing
from
people.
I
am
on
channels
and
feel
free
to
ping
me.
If
you
have
opinions
I
will
respond.
I
will
note,
and
eventually
hopefully
we
will
respond,
we'll
be
able
to
fulfill
what
you're
hoping
for.
B
Related
to
the
documentation,
please
feel
free
to
reach
out
to
me
as
yeah
I
was
one
of
the
people
who
started
everything
and
yeah
wrote
the
first
pieces
of
the
documentation
and
since
then
it
grew
step
by
step.
So
whenever
you
have
questions,
don't
hesitate.
D
Thank
you,
yeah,
I'm
just
starting
to
read.
I'm
making
all
my
notes
and
things
so
that'll
be
very
useful
to
get
there's
history
and
I
would
say
it's
a
very
nice
start.
D
C
Hey
meg
yeah
I've
actually
been
having
a
a
similar
discussion
with
brad
brad
can't
make
it
on
the
call,
unfortunately
tonight,
but
he
I
know,
he's
introduced.
Captain
co
to
a
couple
of
his
colleagues
and
they've
they've
had
some
feedback
so
yeah.
Let's,
let's
have
that
discussion
as
well.
I
think
brad
was
even
talking
about
kind
of
a
focus
group
or
you
know
just
getting
a
few
captain
beginners
and
and
getting
it
because
everyone
on
this
call
has
been
involved
for
quite
some
time.
C
D
Wonderful
because
my
experience
with
this
is
it's
going
to
have
to
be
iterative,
you
know
we
keep,
we
make
an
improvement
and
then
we
look
at
that
again
and
we
make
more
improvements
and
because
it's
always
a
fine
line
to
you,
don't
want
to
overwhelm
people
when
they're,
just
starting
with
too
much
information
and
yet
I'm
as
guilty
as
the
next
person.
I
start
looking
and
I'm
like
well
what,
if
I
wanted
to
do,
such
and
such
here
and
what,
if
I
wanted
to
do,
such
and
so
to
try
to
get
that
balance.
D
A
Welcome
back
yeah,
first
documentation
is
quite
important
topic
for
sure,
and
we
have
a
few
items
on
the
roadmap
already,
so
I'll
probably
show
how
it's
currently
organized,
and
so
we
have
captain
roadmap,
it's
a
github
project
and
on
this
project
we
start
putting
some
topics
beyond
captain
core
development.
So
we
have
captain
enhancement
proposals.
We
will
talk
about
them
a
bit
later,
but
also
there
are
some
items
focused
on
documentation
and,
for
example,
currently
we
have
a
new
lightweight
tutorial
which
made
some
progress
and
we
can
get
it
together
over
the
line.
A
I
mean
not
how
it's
implemented
now,
when
we
have
a
separate
repository
for
the
documentation
but
integrating
the
docs
right
inside
the
projects
and
indicating
them.
Let's
say
this
enter
also
improving
the
website
improving
contributing
guidelines,
as
you
mentioned
mac,
and
also
get
restructuring
tutorials.
A
A
A
So,
what's
next
for
us,
do
we
have
anything
else
to
discuss
about
the
documentation
while
we're
there,
or
would
you
like
to
move
on
to
other
topics.
A
So
maybe
you
would
like
to
quickly
speak
about
it.
How
you
see
its
landing.
E
C
B
B
And
unfortunately,
as
you
can
see
here,
we
have
a
copy
of
200
files
and
it's
copy
paste
from
from
the
old,
and
then
the
team
is
working
or
doing
here,
yeah
the
improvements
and
the
the
new
features,
and
once
the
release
is
ready
and
we
just
enable
this
documentation
and
and
render
it
and
disable
old
ones,
so
that
the
list
does
not
get
longer.
D
A
So
yeah
basically
he's
the
least
yeah
the
problem
right
now
that
all
this
documentation
is
basically
indexed
by
google
and
if
you
look
for
something,
it's
not
necessary
that
you
will
get
to
latest
version.
Well,
it's
almost
guaranteed
that
it's
not.
I
usually
get
the
oldest
version
and
yeah.
There
is
a
lot
of
other
experience
issues
we
could
address
over
time.
A
D
A
A
So
there
is
change
lock
on
github
releases
that
basically
integrates
all
the
represented
toria.
You
can
see
that
it's
not
just
the
core,
but
also
some
services
integrate
like
cvs,
security
service
reserve
resource
service,
also
geometer
service,
which
should
be
probably
detached
because
it's
execution
plane,
but
all
of
that
is,
has
integrated
change,
lock.
Here's,
for
example,
change
lock
for
0.12,
with
all
the
features
etc
aggregated.
So
it's
automated
change.
Log
and.
A
D
A
A
D
D
A
So
yeah
there
are
some
items.
Well,
generally,
all
the
information
is
available
to
users,
how
we
represent
that,
how
we
collect
that
something
we
could
improve.
Also,
a
change
looks
so
this
automated
part,
which
is
just
generated
from
community
history.
A
E
E
A
B
A
slightly
what's
actually
the
difference
between
those
and
not
that
many
end
user
facing
changes
no
more
on
the
course
side,
meaning
behind
the
scenes,
but
not
really
much.
That
is
usually
impacting.
C
If
there
was
a
policy
there,
because
in
the
future
there
might
be
breaking
changes,
so
if
the
policy
is
to
always
use
the
bleeding
edge,
you
could
run
into
a
situation
where
you're
now
running
tutorials
that
you've,
specifically
written
that
aren't
going
to
work
with
the
currently
ga
version.
So
my
first
thought
there
is
always
go
with
the
one,
that's
kind
of
ga
at
the
moment
and
then
then
you're
giving
you're
giving
yourself
that
flexibility
to
change
it
in
the
future.
That's
just
my
thought.
A
So,
yes,
I
think
thanks
a
lot
for
the
information
inside.
So
definitely
look
into
that
and
yes,
so
we
tend
to
be
plant
discussions
with
bread
and
mica
about
captain
experiences
and
my
superman
integration
so
they're
not
on
the
call
I
will
reach
out
to
them
separately
and
see
how
we
actually
get
it
scheduled.
A
B
B
Well,
what
I
did
yeah
this
week
was
filing
a
new
enhancement
proposal,
which
is
a
use
case
or
a
user-facing
one.
It's
the
capability
of
capability
of
re-triggering,
a
sequence
that
was
already
executed,
but
probably
failed.
Yet
this
request
is
coming
in
almost
every
second
week.
B
Someone
is
asking
for
this
feature,
and
I
now
sat
down
and
yeah
created
this
enhancement
proposal
where
I
describe
the
persona,
because
I
as
a
side,
reliability,
engineer
or
devops
engineer
who
is
using
captain
wants
to
retrigger
failed
sequence,
meaning
in
the
same
stage,
or
there
can
also
be
the
situation
that
I
would
like
to
retrigger
a
sequence
really
starting
from
the
first
stage.
These
are
the
two
use
cases.
B
B
From
my
point
of
view,
there
are
two
levels
where
I
can
re-trigger
a
sequence.
As
I
said
the
first
one
is
here.
Let
me
just
open
that
one
where
I
get
this
re
run
or
retrigger
functionality
directly
at
the
sequence
level,
and
when
I
click
that
one
this
sequence
will
get
executed
a
second
time,
meaning
that
it
will
show
up
here
again
and
yeah,
we'll
get
executed.
Then
by
captain
and
the
second
level
where
I
see
a
rerun
functionality
is
here
on
the
on
the
top.
B
The
content
of
the
sequence
is
identical
to
that
one,
and
the
outcome
would
be
that
a
new
sequence
pops
up
here
in
the
left
menu
because
it's
a
new
one
and
then
it
starts
from
the
first
stage
and
then
it
goes
through
all
the
other
stages.
This
is
the
second
entry.
A
Point
maybe
user
experience
feedback,
so
text
is
short,
but
in
some
cases
it
might
be
essential
for
users
to
know
what
they're
triggering,
because,
if
you
let's
say,
re-trigger
the
stage
when
it's
not
intended,
you
can
actually
impact
your
deployment
right.
So
maybe,
in
this
case
it
makes
sense
to
be
more
explicit
about
what
is
it
on
the
web
interface
so
rerun
stage
around
sequence
text
and
maybe
other
option
is
to
have
confirmation
window.
So
are
you
sure
you
want
to
run
that
these
details?
What
exactly
you're
going
to
rerun.
B
C
Sorry
this
is
probably
one
for
the
developer
meeting
or
even
the
thread
but
another
cloud
event:
spec
are
the
id's
going
to
be
regenerated
or
is
the
expectation
that
you're
literally
sending
this
thing
identical,
payload.
B
Very
good
question:
in
the
first
use
case:
it's
really
the
identical
payload
from
from
the
sequence,
it's
a
one
to
one
and
when
I'm
here
on
that
level,
then
the
ids
will
be
new
ones,
because
I
will
get
a
new
context
id
as
well
as
a
new
yeah
sequence
id,
and
this
is
also
the
reason
why
a
new
sequence
will
pop
up
here.
C
B
No
no
this
here,
it's
popping
up
correct,
it's
where
the
new
sequence
will
be
shown
here.
It's
on
the
on
yeah
continuing
this
list,
and
here
it's
on
the
top
have
a
new
one.
There.
B
And
on
the
other
side
we
have
the
captain
operator,
which
is
taking
those
entities
and
then
yeah
talking
to
the
captain
api
for
creating
a
service,
creating
a
stage
project
and
so
on
and
my
proposal.
The
last
time
was
to
do
a
split
of
this
cap
and
the
split
would
be
right
here
having
the
left
part,
which
is
the
upper
the
kit,
git
ops
operator
and
the
right
part.
Where
we
talk
about
the
captain
operator.
E
B
C
B
B
A
Yeah
but
on
the
other
hand,
the
captain
operator
can
operate
separately
because
you
can
submit
crds
to
that,
and
it
cannot
manage
your
instance
so
well
in
some
regards.
Captain
operator
independently
might
be
useful,
especially
for
example,
for
tools
that
integrate
captain
kratero
ops,
for
example,
which
was
presented
months
ago,
because
they
can
just
use
crds
to
configure
the
instance.
A
Yeah,
so
the
prototype
is
basically
available
for
evaluation,
thomas
matched
other
recent
changes.
So
if
somebody
wants
to
try
it
out,
it
would
be
nice.
You
might
edit
this
g-shock
project
idea,
because
we
had
some
ideas,
how
we
could
actually
leverage
that
but
yeah,
it's,
let's
see
to
be
discussed.
A
A
Well,
it
was
a
quick
one.
So
currently
we
wait
for
review
by
the
toc.
So
yesterday
there
was
a
election
cycle
of
cncf2c
ending.
So
hopefully
we
will
have
some
attraction
after
that
some
projects
already
get
follow-ups.
So,
for
example,
litmus
cows
went
through
voting
process.
There
is
a
key
native
process
started,
so
they
are
handling
the
queue
and
the
cabinet
is
on
this
queue
as
well
as
backstage,
using
which
we're
integrating
currently
so
no
eta
at
the
moment,
but
hopefully
we'll
get
the
final
decision
in
one
or
two
months.
A
So
these
are
two
items
happening
there.
One
thing
for
us:
we
might
need
to
revise
the
due
diligence
document,
because
the
current
due
diligence
document
was
created
by
jurgen
in
june
and
since
that
it
got
updated
a
lot
well
outdated.
A
lot.
First
of
all,
we
delivered
a
lot
of
features
from
the
roadmap
declaration.
These
due
diligence.
There
are
new
roadmap
changes
which
I
need
to
be
reflected.
There
are
new
adopters
new
integrations,
and
all
of
that
is
actually
important
for
evaluation
by
the
queues
here.
A
So
there
is
a
new
delusions
document
referenced
by
you
can
below.
I
believe,
yeah,
here's
one
and
this
one
is
quite
updated.
So
yeah
all
summary
are
all
relevant
but
future
plans.
So
you
can
see
zeroed
out
time
upgrades
it's
not
future
plans.
It's
currently
a
work
in
progress
on
the
roadmap.
A
Captain
uniform
first
part
was
delivered
yearly.
Access
control
is
basically
cap.
60,
which
is
planned
for
future
eventing
standards
is
something
we
have
in
progress:
remote
management
of
execution,
plane,
yeah,
it's
cap,
65
and
67
we
discussed
recently.
A
So
we
definitely
need
to
do
some
updates
here
and
also
mentioning
new
integrations,
because
it's
super
important
to
have
all
possible
integrations
here
and
currently
we
have
more
operators.
Yeah
you
have
a
prototype
for
crossplane
is
currently
shipped.
We
have
baxter
integration
work
in
progress
and
we
have
more
moderators.
A
And
yeah,
maybe
I
will
build
looking
at
core
infrastructure
initiative
checklist
which
is
currently
being
transferred
to
open
ssf,
because
there
is
a
lot
of
quality
gates,
including
community
health
security
project
structure.
A
We
currently
have
99
for
100
percent
checklist,
and
I
will
get
this
one
percent
done,
but
after
that
we
also
have
200
for
silver
and
gold
status
with
a
lot
of
best
practices.
We
actually
already
address
and
some
way
which
would
be
nice
to
address.
A
A
Well,
it's
a
lot
of
bureaucratic
purpose
with
a
valiant
gold
to
have
us
incubating
project
in
the
cncf,
with
assumption
that
it
would
help
us
to
drive
contributions.
It
would
unlock
help
from
the
cncf
marketing
team.
It
would
unlock
lfx
tool
success
because,
for
example,
even
easy
cla
we
discussed
for
improving
documentation,
contribution
flow
or
basic
okay,
getting
creative
dco.
You
have
to
be
in
an
incubating
project
to
get
access
to
that
or
to
get
an
exception.
A
A
Also
same
for
kubecon,
if
we
are
incubating,
we
will
be
able
to
reserve
some
time
in
the
agenda
and
make
it
worse
and
other
things.
A
A
Yeah,
so
for
me,
either
option
works.
I
just
wanted
to
understand
and
adjust
accordingly,
but
yeah.
It
would
be
really
nice
to
have
this
presentation.
I
watched
it
with
subtitles.
It
was
really
nice
so
well,
it
was
half
english
after
all,
but
if
you
could
do
a
full
english
version,
I
think
it
would
be
nice.
A
A
I
think
that
in
two
weeks
we
can
target
having
the
same
meeting
and
then
we
see
how
the
developer
meeting
and
community
meeting
interact
together,
because
personally,
I
would
like
to
have
more
developers
at
the
community
meeting
and
to
not
create
this
sealers.