►
From YouTube: Keptn Community & Developer Meeting - Jun 28, 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
A
A
Nothing
much
from
the
very
first
item:
klt
updates.
We
recently
released
version
zero
point
eight
and
we
are
working
towards
0.9.
You
can
check
the
Milestones.
Actually,
let
me
link
them.
A
Learning
for
next
release,
move
away
from
the
scheduler
for
environments
that
have
the
Readiness
Gates
feature
flag,
enabled
at
the
cubelet
level.
A
A
And
then
I
would
like
to
talk
a
bit
about
this
Captain
announcement
proposal.
Cap95,
you
can
read
the
link
following
the
link.
You
can
read
the
cap
where
the
goal
is
to
move
the
face
of
Captain
from
Captain
B1
to
klt,
and
for
that
we
start
discussing
the
migration
strategy
and
the
plan
for
that
is
before
we
can
do
the
official
switch.
A
We
need
to
have
feature
parity
and
if
you
look
at
the
use
cases
of
Captain
B1,
we
identified
three
major
use
cases
that
Captain
P1
is
used
for
qualiticate
continuous
delivery
and
bring
your
own
integration,
or
these
two
points
klt
already
covers
99
of
the
scenarios
of
Captain
V1.
So
we
can
say
everything
is
teacher
parity.
A
The
only
part
which
is
greatly
missing
is
quality
gate,
because
Captain
V1
has
a
much
more
powerful
SLO
engine,
but
you
can
provide
multiple,
slides
or
average
among
them
check
previous
data
and
compare
against
them
against
that
and
klt
at
the
moment
has
not
this
big
feature
set
for
having
SLO
definitions?
Therefore,
we
want
to
increase
the
support
of
this
in
klt
and
after
that
we
can
really
do
the
switch,
but
don't
be
worried.
It's
not
just
enough
from
one
day
to
another.
A
How
you
can
run
your
use
case
in
Captain,
V1
and
now
how
you
can
do
that
in
klt,
how
you
can
migrate
from
the
what
you
already
already
have
and
do
that
in
klt
and
Mac
started
a
very
nice
handy,
dandy,
epic,
that
describes
all
the
different
scenarios,
how
we
plan
to
migrate
them
and
if
you
want
to
contribute
on
the
documentation
side
play
with
Captain,
V1
and
klt.
Please
feel
free
to
ask
I
want
to
work
on
that
issue.
B
So
yeah,
hey
everyone,
I
am
currently
working
on
a
gsoc
project
in
which
we'll
introduce
a
new
time
frame
field
in
the
captain
metric.
So
we
have,
we
I
am
done
with
introducing
the
field
in
the
captain
metric.
If
you
want
to
have
a
look
at
the
pr
here
is
the
pr
now
for
this
time
range
field
to
work,
we'll
have
to
update
the
apis
for
our
metric
providers.
Promise
is
data
dog
and
dynatories.
I
am
almost
done
with
the
like.
B
The
basic
functionality
is
working,
just
need
to
upgrade
the
test
cases
and
all
yeah,
so
I
have
a
demo
ready,
so
I
have
deployed
The
Matrix
operator
and
the
certificate
operator
in
my
cluster
and
I
have
parameters
already
deployed
in
the
cluster
too.
B
So
we
have
introduced
this
new
field
in
the
captain
metric,
but
it
will
what
it
will
do
is
it
will
query
for
metrics
in
the
time
five
in
the
like
five
minutes
behind
the
current
time.
So
the
start
time
would
be
five
minutes
before
till
the
current
time,
and
here
is
the
metric
provider
which
will
set
promises
as
the
provider
I
can
apply.
This.
B
So
here's
the
value
of
our
captain
metric
right
now
we
have
the
value
as
1.69.
That
means
the
value
for
the
metric.
In
the
past,
five
minutes
was
1.69
and
it
has
upgraded
the
last
amplitude
and
the
raw
value,
so
that
was
all
delete
we'll
now,
once
we
are
done
with
this
API
thing,
then
we'll
move
on
to
aggregation
functions
so
that
you
will
be
able
to
query
for
different
time,
usually
able
to
query
for
a
Time
range.
But
you
will.
B
You
can
also
mention
a
step
field
like
for
different
seconds
so
that
it
queries
for
different
seconds
in
that
time
frame
and
you
will
get
different
metric
values
and
then
you
can
apply.
Aggregation
function,
functions
to
that
metric
value,
to
get
a
single
value
in
your
metric
status,
so
yeah.
That
was
all.
If
you
have
any
questions.
A
Thank
you
very
much
for
the
demo.
I
really
like
the
work.
I
have
only
one
question
more
towards
the
general
public
here.
Would
you
like
to
have
the
five
minutes
interval
as
part
of
the
get
metric
command,
because
in
the
cube,
City
I'll
get
captain
metric?
You
have
the
query
and
the
results
does
it
make
sense
also
to
show
in
the
column
the
time
frame?
So
you
know
that
this
1.69
was
the
aggregation
of
that
specific
query
in
the
last
five
minutes.
A
C
A
B
C
B
Very
great
to
hear
actually
I
was
like
I
almost
completed
the
half
of
the
project
before
the
time
like
I
was
behind
before
10
to
12
days,
but
due
to
kcd
Mumbai
I
got
left
behind,
so
yeah
I
am
almost
on
the
track.
Right
now,
with
the
timeline.
A
Okie
dokie,
then
a
small
announcement.
Let
me
go.
A
So
currently
we
have
to
help
if
I,
don't
recall,
bronc
meetings
every
month,
and
this
might
be
too
many.
It's
also
hard
for
a
new
contributor
to
join
all
of
these
12
meetings
to
understand.
What's
going
on
in
each
Library
meeting,
so
we
funding,
we
are
looking
for
different
ways
how
we
can
reduce
this
amount
of
meetings
that
we
have.
A
Currently,
there
are
two
strategies:
one
is
to
aggregate
multiple
meetings
into
a
single
one,
for
instance
having
the
docs
community
and
refinement
meetings
as
a
single
one,
make
it
longer
and
time
box
each
topic
to
30
minutes
or
another
option
is
to
reduce
the
Cadence
of
the
meeting.
Instead
of
having
the
committee
meeting
every
week
having
that
every
two
weeks,
one
per
month
in
a
European,
Amer,
friendly
time
zone
and
another
one
for
these
North
America
friendly
time
zone,
we
will
give
you
an
update
as
soon
as
we
know
exactly
how
we
will
proceed.