►
From YouTube: Keptn Community & Developer Meeting - Mar 03, 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
Hello
thanks
for
joining
the
captain
community
meeting,
so
today
is
march
3rd
and
we
have
several
items
in
our
agenda.
I'll
just
share
my
screen.
A
Okay,
then,
I
could
probably
just
do
a
quick
update
for
clipcon
for
the
record,
and
then
we
discuss
community,
so
yeah
coupon
will
take
place
in
may
in
valencia.
It
will
be
in
first
event,
hopefully,
by
this
time
we
will
have
captain
officially
joining
the
creating
stage,
and
we
have
a
few
captain
related
applications
to
keep
on
and
we
also
applied
for
various
kinds
of
community
events,
including
office
hours.
A
The
screen,
so
it
would
be
based
because
we
focused
on
capturing
users,
so
we
could
leverage
keep
on
attendance,
ballpark
estimation
that
we
could
get
from
50
to
100
basic
participants.
Obviously,
profit
restrictions
and
other
events
in
the
world
allow
that
and
yeah.
The
idea
is
to
have
multiple
presenters,
including
captain
developers.
A
A
So
initially
we
got
feedback
that
yeah.
It
would
be
technically
possible
to
have
a
half
day
event
on
may
17th
right
at
the
cube,
convenient
up
to
50
people.
So
it
was
something
fitting
our
needs
and
we
agreed
and
started
planning
for
that,
but
now
yeah.
So
it
seems
that
it's
no
longer
possible.
So
basically
there
were
some
ideas
how
we
could
actually
replace
that
by
using
other
possibilities
that
keep
on.
And
if
you
put
your.
B
B
So
we
received
your
requests
for
both
a
in-person
meeting
at
the
event
which
is
initially
set
up
for
us
to
allow
a
project
to
meet
with
their
maintainers
or
specific
contributors
contributors
in
their
community
and
to
discuss
things
like
roadmap
or
discuss
things
like
specific
challenges.
It's
kind
of
a
working
session
that
we
had
set
up
that
working
session
would
be
typically
about
two
hours
of
time
and
it's
up
to
30
people.
B
What
I
can
offer
you
at
this
time
on
tuesday
may
17
is
extending
it
to
four
hours
and
we
can
allow
up
to
45
people
in
that
room,
and
you
can
use
that
essentially
to
do
a
hybrid
of
either
your
in-person
event
or
the
community
contributor
user
summit
that
you
were
hoping
to
host
so
or
if
you
want
to
go
ahead
and
use
it
just
for
the
contributor
user
summit.
That's
totally
fine,
too.
B
We
are
providing
a
projector
and
screen
in
that
room.
We
would
have
the
room
set
up
in
a
theater
style
with
chairs
that
have
individual
desks.
That
kind
of
pop
up
that
allows
for
those
who
are
in
your
sessions
to
be
able
to
work
on
their
laptops
or
tablets
or
take
notes.
It
can
be
more
of
a
working
session
as
opposed
to
having
a
traditional
classroom
set
up.
It
just
allows
for
us
to
get
more
people
into
the
space.
B
B
A
A
So
for
us.
I
think
it
would
be
great
one
question
about
the
vineyard.
So
if
you
want
to
broadcast
the
event
or
if
we
want
to
record
that
other
any
partners
that
provides
that
already
yeah.
B
So
yeah
we
do
have
a
partner
that
we
can
provide
you
costs
for
them
to
record
they're
our
preferred
provider
that
we
use
for
all
of
our
kubecon
events.
We
bring
them
specifically
to
eu
events
as
well
as
north
america
and
china
events,
so
they're
very
well
versed
in
what
the
community
is
looking
for,
they've
been
recording
all
of
our
events
dating
back
to
the
start
of
kubecon
in
2016
in
seattle.
B
B
A
B
A
Nice
so
that
yeah,
we
are
currently
working
with
potential
sponsors,
so
we
want
to
have
two
or
three
sponsors
at
the
event
and
just
to
set
the
budgeting
expectations.
So
we
scat
rank
as
because,
when
you
handle
being
handled
basically
recording
could
be
the
biggest
cost.
B
Additionally,
I
do
want
to
note
that,
because
you
aren't
incubating
yet
typically
we
provide.
This
is
a
opportunity
that
we're
providing
for
incubating
graduated
and
tag
projects
that
in-person
meeting
and
it's
a
special
exception
for
us
to
extend
it
for
you.
I
know
that
you're
really
looking
to
get
the
community
involved,
and
we
want
to
support
that.
Of
course,
we
want
to
support
all
of
our
projects
in
order
for
us
to
make
this
move
forward.
A
Yeah,
it's
technically
possible,
so
it
fits
the
timeline
we
discussed
with
the
cncftvc.
So
basically
our
current
status.
We
have
pending
application
due
diligence.
We
finished
user
interviews
by
now,
so
assuming
that
the
due
diligence
is
accepted
by
the
cncf,
we
should
be
able
to
start
voting
in
two
weeks.
Perfect.
C
A
So
to
have
this
captain
community
by
april
13th,
we
need
to
have
basically
binding
approval
for
incubation.
B
C
B
B
Spoken
to
amy
about
this,
she
is
well
aware
that
that's
the
contingency
and
she
is
going
to
be
helping
your
project
with
this
process
as
well.
She
does
know
that
that
you
have
had
this
in
a
ticketing
backlog
since
july
of
2021,
so
she
is
well
aware
of
this
and
she
is
going
to
be
working
to
help
you.
So
that's.
A
No
thanks,
it's
much
appreciated,
so
we
will
work
with
our
cncftc
sponsor
and
yeah.
We
are
really
working
on
the
community.
So
it's
great!
Thank
you.
So
if
you
have
this
project
meeting
or
captain
community,
how
does
it
happen
in
terms
of
logistics?
So
you
would
still
need
to
have
a
kind
of
program,
team,
etc
to
drop
the
event
agenda
and
put
into
the
support
of
kid
phone.
Or
would
you
expect
it
to
happen
as
a
separate
event.
B
It
would,
it
would
happen
as
a
separate
event.
We
would
host
it
on
the
project
benefits
site
for
you.
You.
B
Your
own
schedule
within
our
scheduling
tool
called
sketch.
We
would
help
with
those
logistics.
You
would
need
to
have
a
program
committee.
We
typically
request
that
a
program
committee
doesn't
have
more
than
two
people
from
one
company
on
it.
So
to
have
a
diverse
program.
Committee
of
you
know
three
to
four
people
from
different
companies
looking
at
applications.
B
We
can
help
you
with
the
cfp
process.
If
that's
something
you
needed,
we,
we
would
kind
of,
allow
you
to
run
that
portion
of
it
on
your
own
as
well
as
kind
of
running
your
what
you
would
be
giving
your
sponsors
at
this
time
since
we
are
going
to
be.
B
You
know,
slotting
this
in
under
project
meetings,
our
team
would
take
kind
of
a
secondary
step
back
in
more
of
a
logistics
role,
but
guiding
you
with.
You
know
best
practices
and
you
know,
recommendations
as
needed
and
again,
like
I
said
we
would
have
that
highlighted
on
our
project
benefits
page
our
participation
page.
So
people
would
be
aware
of
it.
We
would
have
a
schedule
posted.
C
B
That
we
send
out
to
the
registrants
of
cubecon
about
project
participation
and
then
one
requirement
we
would
have
for
anyone
who's
attending
your
event,
and
this
is
happening
with
all
events
across
coupon.
You
know,
co-located
events
and
project
meetings
is
that
all
attendees
would
have
to
be
a
registered.
Keep
con
participate
participant
to
be
on
the
premises.
B
At
the
event,
we
we
request
that
they
are
a
full
coupon
registrant.
We
can
help
in
terms
of
speakers
if
that's
something
that
needs
to
have
an
exception,
but
not
for
general
attendees.
A
Yeah,
that's
totally
understandable
and
yeah
thanks
for
summarizing
that
one
question
about
logistics,
so
does
it
get
posted
as
a
separate
event
on
events.linuxfoundation.com.
A
A
A
Okay,
that's
perfectly
fine,
so
yeah
thanks
for
summarizing,
so
basically
from
outside.
You
need
us
to
finalize
the
program
coming
here.
We
go
to
the
input
regarding
the
company,
so
we
will
talk
between
each
other,
how
we
can
organize
that
and
I
guess
abstract,
etc.
For
the
event,
I
can
take
care
of
that,
and
so
the
event
would
be
published
before
april
13th,
or
would
you
just
publish
it
only
after
we
have
a
confirmation.
B
C
A
Yeah,
I
think
it's
perfectly
fine
for
us.
We
can
start
socializing
to
the
event
internally
in
the
community,
which
would
contribute
to
the
agenda
etc,
and
I
guess
taking
the
timing,
then,
if
you
wouldn't
do
public
chp
on
the
event
side.
Instead
of
that,
we
can
just
ask
around
in
the
community
so
so
that
by
april
12th
or
when
the
decision
is
made,
we
can
have
a
more
complete
agenda.
B
We
have,
we
have
all
the
logos
on
our
end,
so
we're
fine
with
that.
What
I
can
do
is
follow
up
with
a
post
call
email
about
everything.
We've
discussed
on
this
call.
C
B
Just
you
know
what
we're
looking
for,
what
we're
able
to
offer
and
what
it's
all
contingent
on
and
then
you
can
go
ahead
and
respond
to
that,
and
let
me
know
if
you
have
any
additional
questions
or
if
you
need
any
further
clarifications,
I'm
happy
to
do
that
as
well,
and
then
we
can
also
plan
to
have
another
call
after
you've
kind
of
talked
more
with
the
community
and
more
with
the
toc
about
your
application
process,
and
we
can
go
from
there.
Okay,.
A
Great
yeah
one
last
question,
so
we
basically,
we
will
need
to
add
cncf
as
the
sponsor
for
the
event.
I
guess
anything
else
that
would
be
expected
from
us
in
terms
of
additional
promotions
that
we
will
do
it
through
the
community
channels,
but
if
there
are
any
other
expectations,
please
let
us
know.
B
Yeah
I'll,
let
you
know
at
this
time
there
aren't
any
other
expectations
but
I'll
confirm
and
let
you
know.
A
I
guess
we
will
focus
on
incubation.
Then.
A
Okay,
then
yeah
thanks
a
lot
for
all
the
inputs,
et
cetera
anything
else.
We
need
to
discuss
about
coupon
in
general,.
B
I
don't
think
so
from
my
end,
one
recommendation
that
I
would
make
to
you
that,
if
you're
interested
in
hosting
anything
at
kucon
north
america,
this
would
be
the
time
to
be
filling
out
that
information.
It
is
on
the
kubecon
north
america
website.
B
We
are
starting
to
look
at
what
interest
is
for
co-located
events
there
and
what
our
space
is.
So,
if
you're
interested
in
hosting
a
larger
event
than
what
we're
able
to
give
you
at
this
time
for
europe
at
north
america,
this
is
the
time
to
submit
that
process
and
that
application
for
it.
A
A
B
A
Okay,
so
yeah
thanks
thomas
thanks
johannes,
for
stepping
up
as
potential
program
committee
members.
So
I
guess
we
will
need
to
discuss
the
gender
potential
topics
but
yeah
one
of
the
things
I
would
actually
appreciate
feedback
right
now
is
our
due
diligence
document,
because
it
seems
to
be
on
the
critical
path
right
now
and
actually
well.
It
was
actually
the
next
topic
in
the
agenda.
A
Just
a
quick
update
for
that,
so
we
got
just
trying
to
feedback
from
carnegie
davis,
who
is
the
qc
sponsor.
Also
yesterday
I
had
a
quick
presentation
at
the
up
delivery
talk,
so
they
will
also
get
some
feedback
and,
based
on
that
yesterday-
and
today
I
updated
this
document
quite
a
lot
in
terms
of
basically
everything
we
were
advised
to
move
for
architectural
review,
etc.
Right
inside
the
application.
A
Also,
we
had
to
actualize
everything.
There
is
a
lot
of
discussion
about
proper
wording
with
andy
et
cetera
and,
and
then
current
status
was
updated,
including
major
deliverables.
I
split
out
captain
security
hardening
in
this
separate
section.
With
all
these
topics
it's
ecosystem
growth
community
grows.
All
of
that
is
new.
I
still
need
to
add
some
statistics.
A
I
may
ask
for
help,
but
yeah
right
now.
I
know
where
to
find
all
the
data
and
yeah
future
plans.
We
are
basically
updated
based
on
our
roadmap,
so
if
anyone
could
just
go
through
and
see
what's
missing
or
what
is
wrong
outdated,
for
example,
for
me,
it's
the
open
question
about
remote
management
of
execution
planes.
A
D
No,
no,
it's
not
done.
Definitely
not.
There
are
a
couple
of
items
left,
securing
the
communication
and
and
also
making
the
life
cycle
management
of
the
execution
service
possible.
There
are
definitely
a
couple
of
items
left,
but
I
can
I
can
take
an
action
item
here
to
update
this
section.
A
Yeah,
so
any
updates
or
just
reviews
feedback
would
be
appreciated
and
what
else
do
we
have
here?
So
there
is
quite
a
lot
of
sections
in
integrations
value,
et
cetera.
It
was
slightly
updated
because
captain
got
one
use
cases
like
auto
remediation.
A
Then
we
have
cloud
native
assistant
mapping.
It
was
again
updated
to
reference
all
new
integrations
the
events
project
which
is
now
officially
live
but
yeah
again.
If
something
is
missing,
if
you
have
documented
examples
through
the
webhooks,
it
would
be
really
nice.
Actually,
you
may
have
seen
that
adam
garner.
A
Well,
he
seems
to
be
planning
to
double
the
number
of
integrations
soon.
So
again,
if
you
see
something
missing,
it's
definitely.
This
comment
and
no
need
to
suggest
text
just
point
to
me
to
something
this
is
wrong
and
it's
updated.
I
will
be
happy
to
follow
up
on
that.
A
What
else
do
we
have
here?
Some
plant
integrations
so
here
I
still
have
cross
plane,
open,
telemetry
flux,
falca,
wolf
sneak.
So
this
is
what
we
had
an
initial
one.
Then
I
added
p6,
because
there
is
interest
and
potential
project
idea.
Maybe
github
integrations,
maybe
jenkins
file,
runner
executor.
Here.
I'm
not
sure
right
because
we
have
it
in
json
project
ids,
but
nobody
is
working
on
them
right
now,
particularly
plans.
A
And
then
well
again,
there
is
a
bunch
of
text.
So
what
changed
here
that
added
license
and
dependencies?
One
question
my
understanding
that
currently
we
do
not
produce
as
bombs.
E
A
Yeah,
so
it's
basically
in
this
case
it
would
be
rather
providing
a
standard
format
so
that
other
tools
could
consume
that,
for
example,
for
scanning
purposes,
so
it
could
be
spdex
to
something
different
like
well.
We
will
unlikely
use
maybelline
foam,
but
you
get
the
idea
and
another
topic
which
is
closely
related
to
this
bomb
is
actually
signing
called
the
artifacts.
So
there
is
also
project
seek
store,
so
maybe
I
will
also
create
a
ticket
for
that
so
that
we
ensure
that
everything
is
designed.
A
A
A
A
The
statistics
also
probably
need
to
be
updated.
Do
we
still
have.
D
A
A
A
So
again,
there
is
a
lot
of
discussion
how
we
try
to
ensure
energy
depending
governance,
project
infrastructure
and
also
based
on
the
feedback,
the
special
section
about
dyna
trees,
because
it's
a
finding
funding
company,
but
it's
important
to
show
that
we
basically
do
not
intend
to
have
rendered
lock
in
the
project.
A
D
A
Was
some
additional
feedback,
but
not
much?
I
was
planning
to
do
the
presentation
from
captain
advisor
report,
but
finally
based
on
timing.
I
just
glanced
through
this
document
and
a
few
other
items.
So
no
offenses,
like
yesterday.
A
A
A
A
Is
basically
sets
expectation
that
we
limit
number
representative
from
a
single
company
of
organization
and
basically
that's
it.
So
it's
a
really
simple
document,
but
I
wanted
to
do
sanity
check
so
that
you
see
whether
it's
how
we
would
see
it.
A
And
these
are
all
topics
from
you,
so
just
wanted
to
show
where
we
stand,
if
you're
interested
in
kevin
contributed
pipelines.
Take
a
look
at
yesterday's
meeting
recording,
because
today
we
had
a
really
nice
discussion
with
adam
garner
about
issues
problems
with
discussions,
because
we
have
a
discussion
with
everywhere.
So
we
came
to
some
more
alignment.
How
we
would
like
to
do
that
so,
for
example,
limited
example
before
using
github
discussions
using
github
issues
where
possible,
not
using
apps
for
proposals
that
are
not
substantial
and
that
are
not
specifications.