►
From YouTube: Keptn Community & Developer Meeting - Jan 20, 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
a
lot
for
coming
to
the
meeting
today
is
january
20th
and
we
have
a
regular
community
meeting.
So
if
you
would
like
to
add
some
topics
to
the
agenda,
just
update
the
google
doc
and
yeah,
let's
start
from
some
news.
So
can
you
say
that
now
we
actually
try
doing
two
meetings.
So
yesterday
we
had
a
meeting
in
the
asian
and
pacific
region,
time
zone,
which
was
also
comfortable
for
me
and
yeah.
This
meeting
we
had
seven
participants.
A
For
everyone
who
cannot
attend
this
meeting
on
yeah
communities
in
cfio,
we
publish
links
to
the
meeting
to
meeting
notes
the
presentations
if
needed.
Everything
is
basically
on
youtube
same
as
before.
So
if
you
straight
to
youtube,
you
will
see
this
information
and
we
agreed
during
the
meeting
that
we
will
try
to
keep
as
detailed
meeting
notes
as
possible,
so
that
whomever
is
unable
to
join
one
session.
A
But
it's
this
time
slot
or
one
we
had
yesterday,
then
you
can
basically
take
a
look
what's
going
on
and
comment
and
discuss
as
a
follow-up,
so
yeah.
This
is
what
we
discussed
yesterday.
Also
we
talked
about
doing
more
things
synchronously,
so
that
these
meetings
are
rather
for
runtimes
in
cup,
but
not
for
decision
making
yeah
anything
in
screen.
A
So
this
basically
a
key
follow-up
from
there
and,
as
you
can
see,
we
discussed
a
few
topics
like
captain
012
fosdem
participation.
Just
in
a
few
weeks,
then
we
discussed
captain
community
in
the
park
region.
All
again,
we
talked
about
cap65
required
configuration
and
githubs
quite
a
lot-
also
google
summer,
of
course,
an
lfx
mentorship
and
cap
64
buck
and
potentially
user
authorization
in
the
future.
A
A
So
just
referring
to
the
previous
meeting
and
discussing
the
topics
we
would
like
to
discuss,
especially
the
question
for
the
v3,
because
thomas
and
johannes
participated
yesterday.
B
A
Yeah
so,
firstly,
our
option
to
glance
through
news
so
that
we
have
quick
update
and
post
meetings
and
then
for
the
specific
discussions.
We
can
just
pick
topics
which
are
interested
to
the
audience
so,
for
example,
thomas
put
kept
65
discussion
for
today,
so
yeah.
This
is
definitely
important
enough
to
do
a
recap,
but,
for
example,
for
this
particular
meeting
capital
community
in
the
park
region
is
probably
not
that
important.
I
mean
it's
probably
not
the
subject
for
the
today's
meeting,
yeah
right
great.
A
B
So,
let's
start
according
to
your
initial
plan
and
no
specific
updates
from
my
site,
I
can
just
inform
what
I
am
working
on
additional
connector
to
adx
it's
a
it's.
A
azure
data
explorer
also
called
the
kusto,
and
once
it's
ready,
I'm
happy
to
contribute
back
to
community
azure
data
explorer
right.
It's
also
called
the
custo
database.
B
Because
all
metrics
are
going
directly
there
and
in
future
we
will
be
able
to
use
both
prometheus
from
ql
and
a
kql
language.
What
is
used
for
for
adx,
but
for
now
the
kql
is
the
only
option
to
integrate
with
with
the
system.
A
Understood
have
you
already
talked
to
yurkin
nope
yeah
because
he
just
joined
microsoft.
I
believe
for
asia
advocacy
in
austria
and.
C
A
A
A
Okay,
so
the
next
quick
topic
is
about
maintaining
a
replication
by
thomas,
so
well,
it
was
submitted
this
morning
and
yep.
There
was
so
there
were
already
many
responses
from
maintainers,
including
me,
including
jurgen,
johannes
chris,
and
so
I
guess
we
have
the
majority
of
maintainers
commenting
here
so
yeah.
The
question
is
whether
we
could
just
proceed
and
at
thomas
to
all
the
groups
and
github
organizations,
so.
D
Yeah
definitely
we
have
strong
support
of
this
request
and
I
think,
or
I
think
I'm
sure
we
can
go
on.
A
Johannes,
would
you
be
able
to
grant
the
permissions
because
it
looks
like
I
still
don't
have
all
of
them.
So,
for
example,
I'm
still
not
a
member
of
captain
country
etc,
and
maybe
we
will
need
to
do
a
maintenance
onboarding
checklist
later
to
ensure
that
all
permissions
said.
A
And
later
I
will
add
thomas
to
the
linux
foundation
database,
because
there
is
a
separate
database
for
the
linux
foundation
and
separate
database
for
the
cncf
and
there
are
requests
to
be
submitted.
I
can
take
care
of
that
because
yeah
I
could
just
edit
myself
last
friday,
but
I
need
to
add
the
rest
of
the
team.
There.
A
A
While
we're
talking
about
governance-
maybe
one
topic
to
mention
and
that
there
are
changes
in
the
continuous
delivery
foundation,
so
the
executive
director
of
this
foundation-
three
similar
under
stepped
down
and
what
it
means
that
there
will
be
some
changes
in
the
organization
and
some
projects
might
be
delayed.
What
is
important
for
us
cd
events?
A
So
there
will
be
some
delay,
but
ultimately
it
doesn't
impact
the
working
group
so
allowing
specifications
doing
reference
implementation
for
captain
everything
can
be
done.
It's
just
a
matter
of
marketing
and
official
governance
changes
for
the
project
and
yeah.
A
A
So
maybe
this
particular
topic
we
can
put
on
hold
for
now,
because
we
need
to
understand
what
is
actually
the
future
for
the
continuous
delivery
foundation
in
terms
of
resource
investment,
program
management,
etc.
A
A
Well,
you
are
the
champion
of
this
story,
so
it
would
be
a
very
if
you
take
care
of
that.
But
if
you
want
to
understand.
E
Yes,
yesterday,
we
talked
another
time
about
the
cape
65
so
about
the
captaincytops
and
declarative
configuration
in
our
enhancement
proposal,
and
we
found
out
that
the
cap
by
itself
is
a
bit
too
too
large,
so
that
we
will
split
this
in
two
in
in
two
caps.
So
they
will.
E
Currently,
the
the
whole.
The
whole
cap
is
based
on
our
prototype,
which
we
created
in
a
in
an
innovation
thing
at
the
banana
trees
and
currently
I'm
about
to
be
about
to
finish
this
prototype.
So
I
hope
this
will
be
will
be
done
until
the
next
until
next
week,
when
we
will
present
some
kind
of
key
tops
and
key
tops
in
cape
met
the
defense
knight
in
here.
E
So
please
it
would
also
be
nice
if
someone
joins
in
this
presentation
and,
yes,
I
think,
on
monday
we
had
a
twitter
space
regarding
this.
This
was
also
brought
also
some
kind
of
insights.
Regarding
this,
we
found
some
nice
people
who
will
join
our
efforts
in
in
terms
of
defining
this
and
talking
about
this.
A
So
generally,
we
got
quite
a
lot
of
feedback
and
I
guess
there
will
be
another
iteration,
and
one
of
the
milestones
thomas
you
mentioned
is
releasing
the
next
preview
ready
version
in
a
few
weeks.
A
A
And
to
look
on
the
call:
did
you
have
a
chance
to
take
a
look
at
this
story,
and
maybe
you
have
some
additional
feedback
to
share
about
the
githubs
for
captain
or
captain
operator.
D
A
So
they
will,
if
you
follow
follow-ups,
so
we
discussed
how
we
actually
manage
sli
slos.
They
should
be
exposed
to
crds,
so
there
was
quite
a
long
discussion
and
he
also
participated
the
synchronously.
A
So
I
think
we
will
need
to
revisit
this
topic,
but
I
think
this
so
why
we
actually
have
caps
so
we're
having
open
discussion
and
the
pull
request
or
at
one
of
the
meetings
on
the
chat.
This
is
how
we
could
approach
to
address
this
topic
and
well.
I
guess.
A
Maybe
one
quick
update
yeah
yesterday
I
tried
reaching
out
to
cardinalia
davis
again
to
check
the
status
of
the
graduation.
There
was
a
kind
of
misconnect
because
I
asked
in
the
cncf
talk
and
I
got
a
response
that
currently
they
are
focusing
on
sandbox
projects
for
the
next
two
months.
I
mean
first
box
applications
but
yeah
then
I
had
a
discussion,
gazemy
program
manager,
project
manager,
working
on
cncftoc,
and
actually
it
meant
that
they
won't
be
considering
any
other
sandbox
projects,
but
for
incubation
requests.
A
A
So
I'm
currently
trying
to
reach
out
to
carnegie
through
different
channels.
If
it
doesn't
work
yeah,
let's
see,
I
have
plan
b
already
but
yeah.
I
hope
that
planning
a
works
because
for
us
we
still
have
one
on
clear
topic,
this
security
review.
B
A
It's
not
about
captain.
It's
just
about
operators
in
cap,
65.
B
Okay,
so
it
still
will
be
the
single
helm
deployment
to
install
different
sets
of
operators.
So
it's
based
on
what
so,
how
a
as
a
user.
I
can
choose
the
right
set
of
operators
to
install
all
my
clusters.
E
E
This
additions
consist
of
two
parts,
so
there
is
a
keytops
part
which,
which
talks
to
the
git
repository
itself,
and
there
is
a
captain
part
which,
which
is
able,
which
is
maintaining
the
captain
custom
resources,
but
you
can
also
use
captain
without
all
of
this
github's
approach
and
without
all
of
these
custom
resources.
Therefore,
if
you
don't
want
to
use
a
github's
approach,
nothing
will
change
for
you.
B
Okay,
so
it's
just
for
using
crds
for
all
types
of
resources.
So
it's.
D
D
B
Okay,
because
my
additional
thought
on
that,
it's
like
a
feature
feature
proposal.
Captain
comes
with
multiple
integrations
already,
so
captain
could
be
integrated
with
the
slack.
I
don't
know
it's
dozens
of
different
types
of
integrations,
so
each
of
them
are
additional
services
which
should
be
installed.
B
B
E
B
D
C
C
D
The
idea
that
you
currently
described
is
the
situation
that
I,
as
a
devops
engineer,
I'm
in
charge
of
setting
up
a
captain,
and
I
also
want
to
describe
which
services
captain
services
should
be
installed
and
rolled
out
and
yeah.
Here
it
was
a
first
idea
how
this
could
look
like
by
having
here
a
uniform
and
this
in
this
uniform.
I
specify
I
want
to
have
a
deployment
service
which
then
is
implemented
in
this
image.
D
B
Here:
okay,
exactly
so,
it
could
be
inception
what
you
you
have
installed:
a
single
cluster
and
you're
trying
to
install
additional
clusters
using
this
approach,
it's
known
as
inception
pattern.
Okay,.
D
Thanks
for
the
hint
yeah,
that's
an
old
captain
enhancement
proposal,
but
if
you
have
further
ideas,
please
post
them
on
on
the
on
the
proposal,
and
then
we
can
elaborate
on
that
and
drive
it
forward.
Okay,
thank
you.
A
D
A
Here
sorry,
I'm
still
dealing
with
my
screen
because
apparently
baby
doesn't
automatically
align
the
layout.
If
you
split
the
screen
to
two
parts.
A
D
I
mean
the
idea
of
having
tooling
that
subscribes
to
event
is
implemented
in
captain,
that's
for
sure,
but
the
way
of
having
a
mechanism
to
declare
my
environment
and
to
define
also
in
a
git
tops
way
what
I
would
like
to
have
on
my
cluster.
This
is
a
missing
piece.
B
Okay
may
have
a
if
they
have
a
a
bit
more
time.
One
more
question:
I
have
we
heard.
F
Workflow
engine
argus
workflow
is
just
an
example,
so
you.
B
A
In
this
case,
I
would
recommend
to
duplicate
this
question
in
the
channel,
for
example,
in
captain
integrations
because
andy
grubner,
he
has
probably
a
lot
of
additional
expertise
and
knowledge
about
use
cases
because
he
travels
the
world.
Also.
Does
a
lot
of
workshops
talks
to
many
end
users,
so
he
might
have
more
information
about
the
use
cases
with
his
captain
and
other
by
captain
users.
A
A
A
A
So
if
no
other
questions
or
topics
we
can
close
down
the
meeting
again
I'll
handle
the
recording
will
be
published
tomorrow,
I
will
follow
up
regarding
eating.
A
Thomas
to
the
cncf
database,
johannes,
can
tackle
permissions,
so
we
can
just
sync
up
a
smaller
synchronously
to
ensure
that
everything
is
done,
and
then
we
updated
the
checklist
because
yeah,
for
example,
for
the
cncf
database.
It's
definitely
not
in
the
checklist,
as
we
discovered
hardly
so
yeah.
We
can
get
it
fixed
and
yeah
for
the
rest.
A
I
will
send
jurgen's
conflict
to
the
v3.
In
slack
and
dmitry.
You
can
create
a
threat
about
cd
use
cases
so
that
you
can
see
whether
we
can
get
some
participants.
A
A
Write
about
hierarchical
presentation
of
various
cases,
so
the
vision
for
captain
so
that
we
could
try
approaching
from
this
side,
or
maybe
we
could
do
it
through
the
user
group.
Let's
see,
okay,
cool
thanks
all.