►
From YouTube: Keptn Community & Developer Meeting - Mar 29, 2023
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,
so
today,
Giovanni
is
not
here
so
I'm
trying
to
give
my
best
giving
the
news
he
wrote
down
here
and
then
I
see
in
the
agenda.
We
have
something
from
Simon,
so
I
will
try
to
be
quick.
First
thing
in
the
agenda
is
the
public
roadmap.
We
have
updated
this,
as
we
have
mentioned
before.
What
we
are
concentrating
right
now
for
the
life
cycle.
Toolkit
is
the
automatic
application
discovery,
but
we
also
started
enhancement
proposal
for
the
context
propagation
for
git,
Ops
I
believe
both
we
already
mentioned
in
previous
meetings.
A
B
Yes,
these
are
both
anticipated
to
be
series
season
of
docs
projects.
A
And
then
we
have
also
two
new
tickets,
but
I
believe
this.
We
will
refine
next
public
refinement,
but
it's
just
a
short
description.
One
of
them
is
about
giving
the
possibility
of
having
multiple
providers
of
the
same
type,
and
this
is
a
pretty
simple
task
that
would
be
just
done
by
adding
a
pipe
value
in
the
CRT,
and
then
there
was
also
a
request
for
a
summary
of
the
project
from
the
cncf
that
we
have
to
work
on
for
this
period.
A
Anybody
has
anything
to
see
about
that.
We
haven't
planned
for
the
roadmap.
A
C
Sure
we
actually
mentioned
it
last
meeting
already
as
well,
but
I'm
gonna
talk
about
it
a
little
bit
again.
Basically,
we
started
this
issue
that
you
can
see
here:
sunsetting
the
usage
of
Docker
Hub
in
Captain.
This
was
a
result
of
Docker,
actually
basically
sunsetting
one
of
the
building
models
that
they
have,
which
is
the
free
team
subscription
with
three
major
team
members.
C
There
was
a
big
Community
backlash
and
they
are
actually
not
going
to
do
it
in
the
end
now,
so
they
fully
reverted
everything
and
everything
is
packed
before,
but
maybe
we
can
take
this
opportunity
to
still
do
this,
so
I
would
still
go
through
with
this.
In
the
end,
it
does
there's
not
much
to
do
for
us
anyways,
because
most
things
are
on
GitHub
container
registry
already
anyways,
except
for
the
captain
main
repository
and
maybe
two
or
three
other
things
that
need
to
be
fixed.
C
So
there's
not
that
much
to
do
for
us
I
prepared
a
pull
request
which
fixes
the
cap
and
Captain
repository
it's
right
now,
I
haven't
watched
it
yet.
So
if
anybody
wants
to
comment
on
this,
it's
actually
yes
yeah
exactly.
B
C
Cool
Giovanni
already
approved
nice
yeah,
so
we
are
taking
this
opportunity
and
still
move
away
from
talking
hub,
even
if
it's
to
not
keep
up
with
their
Shenanigans,
basically,
which
is
also
win,
I,
would
say
yeah.
Our
images
will
still
be
on
key.o
and
ozone
ghcr.
A
Okay,
then
I
have
here
some
news
about
Captain
and
klt
for
klt
I.
Think
we
already
announced
it
that
there
was
a
release
0.7
ready
now
the
helm
chart
for
this
release
is
working.
Fine.
There
has
been
some
pickup.
We
have
0.2.1
version
that
has
fixed
it.
You
can
check
the
release,
notes
as
usual
and
in
the
documentation
on
getting
started.
You
can
see
that
we
added
instruction
on
how
to
do
and
how
Rebel
upgrade
and
then
install
Captain
with
PLT
return
or
1.3.0
for
Captain.
A
A
C
D
I
do
not
need
the
screen;
actually,
okay,
sharing
the
thing
is
I
just
wanted
to
inform
you
that
we
merged
our
first
part
of
peribolos,
so
our
git
Ops
user
management
as
a
GitHub
space
user
management.
So
if
you
want
to
be
a
member,
you
just
can
create
a
pull
request
within
the
community
repository
now
we
decided
to
do
it
in
two
iterations
now.
The
first
iteration
is
just
creating
repositories
and
assigning
members
to
the
organization.
D
In
our
next
step,
we
will
do
creating
the
teams
and
creating
the
repositories
where
we,
where
we
will
most
likely
testing
it
on
Monday.
So
if
you
get
emails
or
something
like
that,
normally
you
should
not
have
any
degree
equity,
any
reduced
rights.
Sorry
yeah,
but
if
you
experience
something
just
let
us
know
it
was
not.
It
was
not
intentional
and
most
likely
an
accident,
so
we
will
fix
it
as
soon
as
possible.
E
Yep
yeah,
so
actually
I
am
interested
to
participate
in
gsoc
for
the
query
time
frame
in
Matrix
project.
So
I
just
had
this
one
question
that
right
now
we
are
having
two
dependencies
for
this
project.
One
is
the
addition
of
time
frame
field
and
another
is
the
modification
of
SLI
providers.
F
So,
from
my
perspective,
if
you
want
to
include
the
partner
she's
a
project-
and
it
is
not
too
much
effort
for
you-
then
simply
go
for
it
totally
fine
right
to
keep
the
to
keep
the
scope
of
the
cheeser
projects
small,
to
not
overload
something
someone.
F
E
A
F
Is
there
anything
else
and
in
fact
you
would
also
you
would
have
to
implement
one
provider
in
any
way
to
test
it?
So
I
think
you
would
have
touched
the
promises
providing
anyway.
A
A
G
Today,
yeah
I
just
wanted
to
ask
Motors
if
he
can
remain
in
the
meeting
for
just
two
minutes.
I
just
wanted
to
have
some
chat
regarding
life
cycle
scenario,
just
two
minutes.
If
you
can
stay
absolutely.
G
G
It's
just
the
I
I
was,
you
know,
syncing
up
with
Adam
regarding
scenario
for
lifecycle
toolkit
but
I'm
facing
some
issues
in
installing
that
and
since
Adam
is
not
in
the
time
zone
which
I
am
in
mortez's
IC
is
a
reluctant
with
killer
codia,
color
code
I
think
so.
I
just
wanted
to
have
some
chat
regarding
that.
C
B
C
Okay,
this
is
the
issue
right
on
a
demo
for
life
cycle
controller.
G
G
So
the
the
update
on
this
is
that
most
of
the
part
of
the
demo
is
prepared,
but
while
let's
say
while
installing
the
demo
application
in
the
scenario,
so
how
the
GitHub
repo
is
like
you,
you
install
that
repo
you
CD
into
it,
and
then
there
is
a
sample
app
repo
to
work
for
the
demo
application
version,
one
two
and
three.
G
E
G
If
you
just-
and
we
also
add
a
chat
about
removing
the
cert
manager
thing,
because
that
installation
was
failing
so
I
updated
it
to
Helen
yeah
now,.
B
G
It's
working
but
after
when
you
go
to
the
second
step,
so
it's
I'm
just
like
structuring
it.
It's
like
not
completely
prepared,
just
you
know,
running
through
the
command
so
that,
if
I
not
run
into
any
error.
G
So
when,
when
you
hit
these
commands,
make
install
observability
and
make
restart
lifecycle,
toolkit
so
I
think
install
observability
is
going
through
various
commands
like
it's
installing
Jagger
I
promise,
yes
and
all,
but
it's
not
able
to
pick
few
of
the
resources
which
I
had
a
chat
with
Adam
and
they
said
that
it's
okay,
maybe
it's
searching
for
some
resources
and
not
able
to
find,
but
that
not
that's,
not
a
very
big
issue.
But
when
you
restart
the
lifecycle
toolkit,
it
throws
error.
B
G
B
G
C
C
C
Yeah,
you
could
use
the
tag
here.
Oh
actually,
I
thought
there's
a
release
here:
okay,
never
mind
yeah,
but
the
latest
version
is
released
here.
So
that
should
be
fine.
Let's
see.
Okay,
it's
still
installing.
C
C
B
C
G
C
It
offline
or
if
you
want,
we
can
also
I,
don't
know,
do
this
like
tomorrow
or
something
and
sit
together
us
too.
That.
G
Only
reason
I
wanted
to
do
it
today
is
Adam
told
that
if
it
is
possible,
we
can
make
it
if
we
can
complete
this
demo
within
this
week,
because
he
mainly
wants
me
to
complete
the
demo
before
kubecon.