►
From YouTube: Keptn Community & Developer Meeting - Dec 23, 2021
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
First,
what
happened
this
week
is
that
we
released
captain
odot
eleven
four.
This
was
needed
yeah,
because
the
look
for
j
issue
and
vulnerability
hit
us
as
well,
but
not
to
a
heavy
extent
more
on
our
slightly
because
we
are
using
a
geometer
in
version
or
we
used
version
5.4.1
and
yeah.
India
was
look
for
j,
which
was
vulnerable
and
we
did
an
upgrade
of
gmeter
and
then
also
released
captain
odot4
and
it's
basically
really
just
the
bug
fix
for
the
meter
service.
A
Actually,
we
also
filed
an
security
or
vulnerability
bulletin,
which
summarizes
the
incident
or
the
situation
just
go
to
captain.sh
and
in
the
news
section
which
is
here
on
the
bottom.
You
find
a
list
of
release,
notes
as
well
as
vulnerability
bulletins
and
the
last
one
yeah
is
related
to
the
geometer
issue,
and
here
you'll
find
all
the
details
affected
are
to
meet
the
versions
below
0.11.4.
A
And
here
you
get
a
link
to
the
upgrade
path,
and
please
do
so
so
that
your
environment
is
safe
and
you're,
not
yeah
a
target
to
the
meter
out
to
the
jail
jlog
issue.
A
That
is
the
first
announcement
that
I
have
to
make
then
today,
captain
user
also
informed
us
that
the
upgrade
did
not
work,
and
the
issue
was
because
the
user
didn't
or
because
the
cube
con,
that
the
captain
context
was
not
set
correctly
and
therefore
I
filed
a
pr
on
the
documentation
of
the
captain
upgrade
and
what
was
missing
on
on
the
user's
end.
Was
the
command
captain
set
config,
cube
context
check
to
true
and
by
setting
this
or
by
executing
this
command?
The
upgrade
then
worked
as
we
could
justify
and
test.
A
A
If
this
pops
up,
then
please
execute
captain
set
config
yeah
to
get
your
captain
upgrade
command
working,
and
if
this
also
doesn't
work,
then
there's
always
the
chance
that
you
upgrade
your
cap
manually
in
the
sense
that
you
do
a
helm
upgrade
of
your
captain
release,
and
this
must
work
anyways.
A
Then
the
third
announcement-
the
third
topic
that
I
would
like
to
talk
about
is
the
situation
that
we
shut
down.
The
captain
dot.
B
A
Dot
demo
cluster
it
is,
it
is
on
christmas
holidays
for
a
little
bit
and
will
come
back
in
2022,
but
for
for
now
yeah
we
we
shut
it
down
in
order
also
to
get
the
g-meter
situation
fixed
and
we
want
to
bring
it
back
and
also
roll
based
access
control
is
in
place
so
that
we
can
then
restrict
the
the
surface
of
the
public
demo
cluster,
so
that
not
everybody
can
then
execute
something.
Just
those
who
are
allowed
to
do.
C
Yeah,
so
for
this
cluster
there
were
multiple
issues
and
yeah.
Look
for
jay
was
just
a
final
call
to
action,
so
we
currently
have
it
hosted
and
sponsored
by
dana
frase.
So
we
got
in
the
conflict
with
some
security
policies
because
of
the
lack
of
urban
captain
and
yeah.
Well,
it's
not
great
for
captain
adoption
at
all,
so
we'll
be
working
on
a
new
setup
which
will
be
first
and
fully
managed
as
infrastructure
is
called
so
maybe
with
some
utop,
separators,
etc.
C
Let's
see
and
yeah,
it
will
be
fully
only
and
it
will
be
a
good
case
study
once
rolled
out
but
yeah
for
now
you
have
to
shut
down
it.
I
will
update
tutorials
this
night,
so
yeah
it's
unfortunate,
but
we
have
to
bring
that
down
and
next
week,
we'll
also
spend
some
time
to
properly
create
a
github
project
for
this
demo
so
that
we
actually
start
building
documentation
and
configurations
code
around
the
existing
setup,
because
now
it's
semi-manual
and
with
the
fact
that
everyone
can
actually
access
it
through
captain
cli.
It's
not
fun.
A
C
Okay,
oleg,
you
also
added
two
points
yeah.
I
did
a
point
about
captain
user
dope.
We
had
on
december
21st.
So
I
would
like
to
thank
diego
and
maura
from
kirotec
for
presenting
him
integration
with
krater
platform,
ops,
so
the
recording
is
now
live.
I
will
update
the
meetup
page
so
that
there
are
youtube
links.
Currently
you
can
find
them
on
twitter
and
but
yeah.
We
have
it
out
of
the
door
and
just
a
reminder.
We
are
still
looking
for
presenters
for
january
21st.
C
So
if
somebody
wants
to
join
and
share
their
key
studies
around
captain,
it
doesn't
have
to
be
kept
himself.
Maybe
dmitry
wants
to
talk
about
the
captain
and
backstage
if
you
had
a
chance
to
try
it
out,
but.
D
C
So
with
something
we
can
take
a
look
and
we
are
looking
for
speakers.
I
have
plan
b
but
yeah
on
my
list
yeah.
C
So
another
important
thing
is
that
a
google
summer,
of
course,
so
I
next
meeting
january
13th-
I
proposed
that
we
start
regular,
sync
ups.
So
currently
we
have
four
potential
project
ideas
listed
on
githubisha.
I
will
add
a
link,
so
it's
potential
enough
to
be
selected
for
google
summer
of
code,
but
we
need
to
coordinate
with
regards
to
mentorship
with
regards
to
student
guidelines,
etc.
If
you
want
to
participate,
I
will
be
organ
in
the
junkies
project
next
year
anyway.
C
So
jenkins
project
is
probably
a
bit
too
heavy
for
captain,
but
yeah.
I
can
apply
some
best
practices.
So
if
there
are
people
who
want
to
participate
as
mentors,
then
it
would
be
nice,
and
maybe
it's
also
something
we
could
discuss
because
yeah
johannes,
you
were
a
mentor
for
lfx
membership
last
year
I
also
put
a
jenkins
and
backstage
plugin,
so
the
caption
and
backstage
plugin
as
potential
gsoc
idea
for
the
next
year.
C
So
we
can
talk
about
it,
but
I
think
it
would
be
important
for
us
to
apply,
because
even
if
we
do
not
get
elected
so,
which
is
totally
possible,
it's
a
very
competitive
program.
We
can
reuse
the
same
materials
to
just
run,
lfx
mentorship
now
on
next
year.
Right,
so
we
do
have
potential
run
it.
There
are
people
who
are
interested
to
do
some
mentorship.
C
C
C
A
I
would
be
great
oleg
if
you
can
share
the
ideas
you
already
collected
yeah.
C
C
So
if
you
go
there,
there
are
four
ideas,
but
these
are
not
the
ideas
in
the
list
that
we
can
use
for
application
because
there
are
strict
restrictions
about
google
summer.
Of
course
how
ideas
should
look
like.
C
So
the
only
idea
which
is
let's
say
somewhat
aligned
with
what
is
needed,
is
captain
plugging
for
backstage,
but
I
will
spend
some
time
over
the
christmas
break
which
will
get
a
work
thermal
qd's,
so
I
will
probably
sort
these
ideas
out,
create
maybe
some
newcomer
friendly
issues
etc
and
maybe
even
some
contributing
guidelines
so
that
we
can
actually
get
it
off
the
ground
but
yeah.
My
plan
is
to
keep
expanding
it.
C
C
Yeah
also
a
gentle
reminder.
We
have
seven
days
until
fosdem
application
deadline
for
the
most
of
their
firms,
so
I
will
be
applying
for
ci
cd
rom
with
a
caption
talk
and
yeah.
I
still
have
no
idea
what
will
happen.
These
developer
stands,
but
if
they
will
be
developers
stand
opportunity
this
year,
then
I
will
also
submit
one
for
captain
a
full
disclaimer.
C
If
you
have
ever
been
to
foster
in
person
online
fosdem
experience
is
significantly
different.
I'm
missing
any
person
for
them
a
lot,
but
still
is
something
we
could
try
out
as
additional
dania.
A
Okay,
yeah,
thanks
for
your
updates,
brings
us
to
the
last
point,
but
before
discussing
that
or
announcing
that
dimitri,
do
you
have
any
thoughts
ideas
you
want
to
share
with
us.
D
I
probably
you're
less
familiar
with
microsoft
and
the
azure
tools,
but
the
microsoft
has
a
a
huge
offering
is
around
the
built
infrastructure.
It's
called
azure
devops
that
has
been
more
and
more
connected
to
different
github
tools
like
argo
cd
flux
and
even
we
have
our
own
microsoft
internal
open
source,
which
is
called
the
porter
porter
sh.
You
can
take
a
look
if
you
are
interested.
D
So
observability
is
one
of
the
major
pain
points
in
a
github's
infrastructure
and
I
think
a
captain
provides
a
one
of
the
best
abilities
to
collect
the
event-driven
information
from
different
stages
of
githubs,
and
it
really
depends
how
a
big
organization.
D
Is
using
such
tools
like
azure,
devops,
jenkins
and
or
any
other
well-known
tools
and
as
an
orchestrator.
D
So
a
captain
is,
it
could
be
a
great
addition
to
what
we
have
today.
But
integration
with
multiple
tools
is
painful.
D
That's
why
we
have
decided
to
go
with
a
single
tool
which
will
provide
an
a
necessary
level
of
observability
for
the
system
and
this
tool
will
be
fully
integrated
with
azure,
devops
and
github
provided
by
microsoft,
and
that
will
be
the
backstage.
D
So
backstage
is
a
dashboard
for
for
for
developers,
developer
and
internal
dashboards
could
be
very
interesting
busy
integration
to
event
driven
a
collector
like
captain,
but
it's
all
ideas.
What
should
be
a
glued
together
and
they
represent
a
much
more
complete
solution.
D
They
have
a
huge
opportunity
to
collaborate
here,
but
I
I
don't
have
currently
anything
concrete
to
suggest
right
away,
but
we
can
work
together
and
to
create
a
roadmap
and
a
it.
It
could
be
a
huge,
a
win
for
an
entire
community,
not
only
captain
community,
but
the
github's
community,
with
the
endless
list
of
of
tools
that
is
part
of
it.
A
Yeah
really
cool,
first
of
all
to
have
you
on
the
call,
welcome
and
also
the
ideas
that
you
you
shared
right
now.
I
just
want
to
give
you
an
idea,
also
from
from
our
side
from
the
captain
side
that
we
actually
do
have
an
integration
into
assured
devops,
because
on
the
captain
sandbox
organization,
this
is
where
extensions
are
living
that
are
more
in
a
sandbox
mode,
but
already
used
also
by
the
community.
A
A
If
you
have
some
time-
and
I,
as
you
are
also
an
expert
on
that
topic-
would
be
also
very
appreciated.
If
you
can
take
a
look
here
to
give
us
your
ideas
and
thoughts
on
on
the
extension
on
the
integration,
so
that
we
can
also
then
build
a
integration
that
really
fits
both
worlds
and
and
helps
merging
all
together.
D
It
will
be
great,
I
I
will
happy
to
take
a
look
in
the.
I
think
I
was
not
aware
of
this
repo,
so
I
will
learn
it
and
get
back
one
of
the
best
options
would.
D
What
could
happen
now
is
a
to
get
the
a
hand,
a
hands
from
azure
ado
team
that
will
actually
work
with
the
with
the
captain
community
and
to
make
additional
efforts
to
make
it
more
complete.
So.
A
D
Feel
a
communicate
with
with
the
idiot
team
and
will
suggest
the
to
take
a
look
on
this
project.
And-
and
I
will
try
to
create
a
microsoft
community
for
for
that
and
to
get
more
hands-on
developers
to
extend
the
system
really.
A
Cool
really
cool
thanks.
C
Yeah,
please
feel
free
to
include
me
into
the
loop
because
we
used
to
work
with
asia
team
when
they
were
doing
jenkins
integrations
like
azure,
devops,
artifact,
storage
and
other
beats.
So
I
do
have
some
contacts,
though
I'm
not
sure
who's
currently
leading
this
integration
effort.
D
C
I
can
say
that
we
use
teams
yeah,
so
many
of
captain
developers-
I
don't
know
this
teams
too
well,
at
least
to
some
extent
so
yeah,
if
needed.
Some
of
us
could
join
this
meeting.
A
Okay,
then
suraj,
do
you
have
any
updates
from
your
side?
Am
I
audible.
B
Yes,
you
are
okay,
thank
god.
The
quality
sound
quality
won't
be
that
good,
but
I'm
still
working
on
the
data
rock
service
actually-
and
I
am
actually
facing
some
problems
with
the
dev
setup,
I'm
using
to
represent
version
2
when
it
connects
to
a
remote
cluster.
But
the
problem
is,
I
think
our
distributor
is
somehow
messing
up
the
telepresence,
so
I'm
just
looking
into
that.
Basically.
A
Okay,
okay
yep,
if
you
need
help,
feel
free
to
reach
out
my
slack,
but
I
wanna.
Let
you
know
that
the
next
at
least
the
next
week
the
captain
team
is,
is
more
on
vacation
than
online.
So
please
be
patient
in
case
feedback
is
not
available
so
quickly.
A
A
Okay,
well
because
this
brings
me
to
the
last
point
yeah,
the
next
two
weeks
are:
there
are
a
couple
of
people
on
vacation
and
not
available,
and
this
means
that
we
will
also
skip
the
next
two
meetings
and
we'll
continue
on
january
13th
same
time,
same
link
or
same
channel,
where
we
will
then
kick
on
kick
off
the
new
year
and
yeah
drive
captain
into
into
a
great
year.
So
to
say.
C
And
yeah
our
slot
channels
remain
open,
so
I
will
be
doing
one
meeting
next
week
to
help
one
of
captain
users.
There
are
other
issues
with
gmeter
service,
so
there
is
suspect
back
there
and
if
you
experience
anything,
please
reach
out
to
the
people
in
captain
slack
channels,
some
responses
may
be
delayed
because
many
people
will
be
off.
I
will
try
tomorrow
to
be
also
for
some
days.