►
From YouTube: Keptn Community & Developer Meeting - August 23, 2023
Description
Meeting notes: https://docs.google.com/document/d/1y...
Learn more: https://keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/lifecycle-to...
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
D
B
A
A
We
announced
in
the
announcement
channel
that
we
are
basically
going
away
from
supporting
Captain
B1
with
the
end
of
life
by
four
teenth
of
December
11th
of
December.
Sorry,
and
therefore,
please
reach
out
for
any
feedback
according
to
this
thing,
and
also
for
helping
you
to
migrate
towards
the
new
captain,
everyone
things
just
try
out
the
lifecycle
toolkit
and
if
you
need
any
help,
we
are
there
to
support
you
with
the
migration
process.
A
B
Yep,
oh
please,
either
way
just
heads
up,
Adam
and
more
to
put
together
a
wonderful
new,
getting
started
guide,
which
I
personally
think
is
orders
of
magnitude
better
than
what
we
had
more
work
to
still
do.
B
But
it
actually
is
step
by
step
all
the
way
and
tells
you
what
you're
going
to
do
so
I'm
hoping
if
there's
any
new
community
members
out
there
who
are
looking
for
something
to
do
running
through
this
and
letting
us
know
what
happens,
would
be
wonderful.
A
E
Cool
we'll
do
so,
while
we're
discussing
waiting
for
that
kept.
Is
there
another
way
to
do
what
I'm
trying
to
do,
which
is
basically
integrate
with
git
I
guess,
because
at
the
moment
we've
got
a
post
task
that
fails.
E
E
A
E
Yes,
I
can
do
that
kind
of
not
statically,
but
but,
as
you
know,
with
the
the
get
off
details,
I
can
do
that
with
a
secret
or
something
because
that's
not
going
to
change
the
thing.
That's
really
Dynamic
is
that
the
previous
commit,
and
we
can't
even
assume
that
it's
the
last
commit.
Obviously
we
need
the
hash.
A
D
A
E
C
G
J
A
G
E
Yeah,
oh
yeah,
I
think
so
I
think
so
just
sorry,
I,
don't
I
don't
mean
to
Sidetrack
this,
but
the
contacts
propagation.
Another
thing
that
came
up
is
the
ability
to
have
something
generate
a
spanner.
An
open
Telemetry
span
ID
when
the
pull
request
is
opened,
for
example,
and
we
then
pass
that
span
ID
to
Captain,
because
then
we
can
then,
when
Captain
finishes
its
Trace,
we
can
say
well,
you
know
end
to
end
that
took
three
weeks
to
get
into
production.
A
G
G
A
Be
part
of
this
one.
G
Would
possibly
like
a
CD
event,
make
sense
there
or.
A
For
that
we
have
even
yet
a
different
ticket.
If
you
want
to
track
that
specific
part.
G
G
Yeah
pipelines
that
builds
the
artifact
produced
Etc.
I
A
G
F
G
A
Just
you
know
we
can
talk
Cloud
events,
but
the
events
have
a
specific
semantics
of
those
Cloud
events
and
we
need
to
not
just
use
our
own
semantics
but
then
adapt
our
own
fields
to
fit
into
that
specific
specification.
A
No
worries,
okay,.
E
It
might
be
a
simple
yes
or
no,
but
like
a
read-only
captain
mode.
What
I
mean
by
that
is
the
is
the
the
fear
is
that
we
can
install
captain
and
have
it
break
something
in
particular
the
pre
tasks
post
tasks.
You
know
your
pods
are
running
the
worst
case
scenarios
you
get
some
red
on
a
dashboard
somewhere,
but
pre-tasks
are
really
could
be
bad.
E
So
if
we
could
have
a
flat
like
it
might
help
have
those
conversations
about
adoption
in
companies,
if
we
can
go,
we
can
start
with
the
flag,
so
it
can't
actually
break
anything.
We
can.
We
can
play
around
with
this
safely
and
then
you
know
as
a
company
when
we
get
comfortable
with
this,
we
can
enable
the
pre-tasks
if
we,
if
we
want
to.
B
E
Fundamentally,
what
I
want
is
a
way
if
I
was
trying
to
adopt
captain
is
to
say
it,
my
boss,
nothing
bad
can
happen.
We
can
roll
this
out
and
the
worst
that
would
happen
is
we'd
get
a
couple
of
alerts
that
don't
block
deployments.
E
A
A
Know
yeah
I
think
it
makes
sense
to
have
like
don't
fail
like
some
something
like
that.
I
A
D
A
What
I
mean
is
the
trace
will
report
that
something
failed,
so
you
will
have
all
of
that.
Deluxe
will
say
that
task
failed,
but
but
but
the
scheduler
won't
block
the
port
to
be
bound
to
another
and
be
deployed.
E
The
implementation
to
the
to
the
brains,
but
that's
basically
the
the
use
case.
There
is
just
foreign.
B
Migration
is
yours,
another
new
piece
that
we
have,
which
is
we'll
see
if
it's
useful,
we
wanted
a
migration
guide
and
it
really
don't.
But
this
we
tried
to
put
together
if
you've
got
a
captain
V1
app,
and
you
want
to
migrate
it
here's
sort
of
what
you
might
do
with
you
know.
What
do
you
do
with
the
project
or
service
or
something
thanks
everybody?
We
got
a
lot
of
good
comments
on
this
and
it's
you
know.
A
I
C
B
A
B
I
I
think
you
I,
think
I
heard
that
and
I
didn't
I
was
just
happy.
The
pr
was
merged,
oh
we're,
continuing
contributing.
This
is
mostly
so
far.
What
we've
done
is
just
moved
stuff
from
the
old
contributing.md
file
into
the
contributing
guide
that
is
accessed
from
the
top
tab.
B
So
we
have
a
couple
more
these
that
are
almost
almost
done
at
least
for
what
they
are,
and
this
is
kind
of.
Basically
it's
your
cheat
sheet.
If
you're,
not
a
super,
get
Guru.
B
There
are
several
links
to
some
stuff
and
it
was
one
that
I
wanted.
I
wanted
one
that
something
about
how
how
big
your
PR
should
be
and
I
couldn't
I
found
a
whole
bunch
of
links
from
various
places,
but,
like
I,
didn't
find
anything
from
GitHub
itself
or
something
they
were
doing,
250
to
300
lines
or
something
yeah
I
would
definitely
add
it.
Yeah
there's
a
lot
of
things
here
that
I
and
I've
also
asked
a
couple
and
will
anybody.
This
is
another
one
for
new
contributors.
B
A
B
I
just
wanted
everybody
to
know
if
we
get
one
and
then
the
contributing
guidelines,
and
actually
they
told
that
for
a
second
Yash
did
I
see
that
you're
here?
C
B
And
then
the
dto,
that's
pretty
that's
just
what
was
there?
Who
cares,
but
it
does
have
the
information
in
it
and
then
comes
between
contributing
guide
and
git
and
Anna
our
definition
of
done
for
software
for
the
actually,
if
you've,
only
click
on
contributing
guidelines
real
fast
here
up
under
right
after
migration
strategy,
you
mean,
oh,
the
guidelines
here.
B
B
D
Here,
I
think
it
would
be
useful
to
have
a
simple
list
of
to-do
lists
for
especially
for
new
contributors
of
what
should
be
done
before
putting
your
PRS
ready,
so,
for
instance,
for
documentation.
This
could
be
okay.
All
the
markdown
and
linter
checks
are
passed.
You
don't
write
your
own
yaml
files,
but
you
embed
a
documentation
so
that
this
is
corrected
by
our
yamlink
lint
tool
or
stuff
like
that
or
like
you
do
exactly
what's
in
the
ticket,
no
more
than
that.
B
B
I
B
B
E
Do
do
we
have
any
docs
around
what
actually
happens
in
a
PR
like
because,
if
I'm
raising
a
PR
as
a
first
contributor,
if
I
know
what
GitHub
actions
are
going
to
trigger
and
what
to
expect
I
know
then
like
if
I
know
a
markdown
lint
or
is
going
to
run,
I
then
know
I
need
to
run.
I
can
preemptively
run
a
check.
B
B
Making
room
because
well
the
the
get
doc
does
list
the
semantic
Pete
colon
dot,
colon
Etc,
the
titles
of
that.
So
that's
one
piece
of
it
so
yeah.
If
somebody
makes
the
template
I'll,
just
I
can
use
that
to
source
to
fill
out
the
contributing
guidelines
and
that's
good
I.
Would
how
would
we
feel
about
going
ahead
and
merging
what
we've
got
for
contributing
guidelines?
B
B
A
Well,
I
guess
you're
volunteering
yourself
sure
as
well
for
good
manner
since
Rises
the
topic.
Thank
you.
E
B
And
we
discussed
that
last
week
and
somebody
who
did
somebody
volunteered
they
were
going
to
actually
write
up
a
doc
for
the
contributing
guides
about
how
docs
are
published.
It's.
H
A
I
I
found
the
issue
18
novet
1863.
A
A
H
E
So
how
do
we
kind
of
trigger
that
manual
process?
How
do
we
request
it?
I
guess
is
the
quest.
Is
the
question
if
it,
if
I've,
if
we've
got
docs
on
Main,
how
do
we
kind
of
put
our
hand
up
and
say,
let's:
let's:
let's
do
it.
A
A
A
A
Nice
okey
dokey,
then
we
can
jump
to
the
next
block,
which
is
for
technical
discussions,
although
we
speak
already
a
bit
about
technical
stuff.
But
if
you
have
any
other
technical
topic,
please
add
it
to
the
agenda
otherwise,
for
today,
I
have
a
single
ticket
that
I'd
like
to
discuss
with
the
group,
which
is
this
one
to
improve
the
analogy,
feature
validation
web
hook
and
now,
since
it's
your
ticket,
do
you
like
to
go
over
it?
Yeah.
D
Premises,
we
don't
have
to
do
it,
but
it
would
be
nice
to
have
it.
The
thing
is
while
I
was
developing
the
controller
I
realized
that
you
can
create
the
analysis,
crd
in
two
direction.
Right
and
One.
Direction
is
obvious
and
the
other
direction,
because
we
are
having
a
reference
from
the
other
crd,
and
this
reference
is
not
validated.
You
may
come
up
with
a
name
which
is
not
valid
for
the
kubernetes
resources,
and
this
could
be
a
little
bit
frustrating
like
you
put
something
that
then
you
go
and
try
to
create
a
resource.
D
D
K
H
F
B
That
again
so.
E
A
A
To
me
this
sounds
good.
Whatever
we
can
prevent
earlier
enough
is
good.
D
Yeah,
so
basically,
if
I
create
first
my
template,
then
my
definition
then
my
analysis.
There
is
no
problem
because
Definition
reverse
template
and
Analysis
referral
definition,
so
I
will
be
blocked
by
the
Kuba
CTL.
If
I
try
to
create
a
resource.
That
has
a
bad
name
right,
but
if
I
do
on
the
opposite
way,
then
the
reference
name
for
us
is
just
a
field
inside
the
resource.
So
this
check
won't
be
done.
So
if
I
create
first,
the
analysis
I
will
refer
to
something
that
then
I
cannot
create.
C
K
Yeah,
but
the
ordering
shouldn't
make
that
much
of
a
difference
here,
the
analysis,
value
template
or
analysis
definition
until
the
user
basically
does
not
create.
Nonetheless,
crd,
then
it
shouldn't
bother
us
the
order
of
the
value,
template
or
definition
yeah.
D
K
I
Shouldn't
it
right
also
thinking,
we
could
also
check
that
the
object,
as
reference
is
actually
there,
but
that
then
order
is
important.
H
H
I
I
D
H
A
I
E
K
F
J
Yeah,
it
would
fail
with
a
config
error,
probably
or
a
probably,
you
know
a.
H
D
F
A
C
B
I
have
one
question:
I
think
I
see
somebody
who
might
be
a
first
timer
here.
Harian.
Are
you
still
here?
How
are
you
Michelle
Gary
did
I
pronounce
that
correctly.
H
E
Was
all
done
again,
this
one
might
have
already
been
discussed
and
solved,
but
it's
it's
the
whole
anything
other
than
deployments.
Can
we
annotate
things
other
than
it?
Is
it
on
the
road
map?
Will
it
be
possible?
Should
we
discuss
whether
we
want
it
Etc.
A
A
However,
yesterday
also
I
was
speaking
with
another
member
from
the
community
and
they
would
like
to
integrate
with
Argo
as
well
monitor
Argo
workflows
in
particular.
There
are
also
people
I,
don't
remember
that
specific
person,
but
they
suggested
to
monitor
infrastructure
deployment
through
cross
plane
because
I'm
deploying
my
infrastructure
through
cross
plane.
A
So
it's
nothing
else
than
a
special
type
of
deployment
in
kubernetes,
so
captain
could
also
Monitor
and
do
pre-tasking
Post
task
for
that,
like
verifying
that
my
node
is
big
enough
to
support
all
the
or
have
enough
resources
for
my
application.
I,
don't
know
whatever
security
text
and
then
text
that
the
infrastructure.
C
A
A
A
Oh
Florian
just
checked
about
containing
a
reference.
A
secret
with
an
invalid
name
can
be
applied
so
Dynamic
restrictions
are
not
checked
here
as
well.
So
that's
good
that
we
marked
it
as
a
ignored
ticket
okie
dokie.
Then,
if
there
are
no
further
topics
to
discuss,
we
already
two
minutes
over
time.
I
guess
so!
Thank
you.
Everyone
have
a
great
rest
of
your
day
and
see
you
next
time.
Bye,
bye,
bye,.