►
From YouTube: Keptn and k6 integrations project sync-up, June 30, 2022
B
Yeah,
good
okay,
so
I
will
just
I'll
just
share
my
screen
so
yeah,
so
I
have
adam
created
one
issue
which
will
track
all
the
I
mean.
I
will
keep
a
list
of
all
the
issues
and
steps
that
are
needed
over
here
and
just
link
the
corresponding
issues
to
it.
And,
apart
from
that,
so
for
this
the
documentation
documenting
the
tutorial
for
running
k6
has
been
done.
So
probably
you
can
review
the
pr
and
yeah.
B
Let
me
know
if
any
changes
are
required,
but
I
made
the
changes
that
you
told
regarding
keep
one
micro
service
and
based
on
that
trigger
the
sequences
yeah.
Okay
and
for
this
does
job
executed,
always
support
multiple
command.
So
I
tried
using
different,
different
commands
and
trying
to
see
if
it's
running
or
not,
but
it
was
failing.
I
was
getting
this
error,
but
this
error
was
of
k6
and
not
captain
so
yeah.
Basically,
I
ran
this
command
and
I
also
ran
and
echo
genome
log
with
yeah,
so
echo,
china
lock.
A
B
Taking
the
all
the
arguments
as
a
single,
so
it
won't
consider
ampersand
ampersand
so
the
same
way
we
are
getting
this
error
over
here.
This
error
is
also
corresponding
to
only
one
argument
is
given
should
be
given
to
k6,
but
over
here
it
takes
ampersand
and
following
command
also
so
it
which
is
fine.
So
that's
the
issue,
so
we
won't
be
able
to
do
that.
Yeah.
A
A
So
what
we
want
to
do
is
basically,
as
this
task
runs
inside,
that
container
build
a
version
of
k6
with
any
extension
that
you
choose
and
then
run
it.
So
what
I
suggest
you
look
at
john
for
next
time
is
the
job
executor
cons
service
can
copy
files
into
the
container
when
it
starts
up.
So
maybe
you
use
that
mechanism
in
some.
I
don't
I
don't
want
to
give
it
away.
I
want
you
to
kind
of
discover
and
find.
B
A
B
A
B
A
B
A
B
We
need
this,
I
mean
we
need
to
run
multiple
this
right
so,
but
I
mean
for
for
building
the
so
for
building
a
k6
extension
using
xk6.
We
will
have
to
use,
for
I
mean
follow
these
steps,
have
a
golang
image
and
then
install
case
xk6
first
and
then
use
xk6
to
build
some
extension,
and
then
you
use
that
text
cases.
So
we
will
have
to
use
this
ampersand
and
if
it's
taking
the
arguments
as
a
whole,
then
probably
you
won't
be
able
to
do
that.
B
A
Yeah,
I
don't
think
by
the
way,
if
you
flick
back
to
that,
I
don't
think
you're
a
million
miles
away.
I
think
we
just
obviously
as
you've
seen
what
it's
doing
is.
It's
it's
running,
go
and
then
it's
just
sticking
all
the
args.
On
the
end,
I
I
think
that's
very
close
using
that
golang
image
and
then
a
slightly
different
command.
A
B
B
A
My
thought
there
is:
we
take
that
pre-built.
If
there
is
one
we
take
that
pre-built
binary
and
we
store
it
in
our
git
repo
and
copy
it
into
the
container,
and
then
you
don't
have
to
do
all
of
that
golang
building.
All
you
do.
Is
you
run
x
because,
because
x,
k
6,
the
binary
is
already
in
your
job.
Execute
service
container
and
you
just
run
x,
casing
build
yeah.
Oh,
I
see
what
you
still
need.
Yeah.
B
Image
but
I
mean
for
most
of
the
k6
extensions
they
are
not.
I
mean
they
don't
have
this
image
published
from
there
and
also
that
they
don't
have
any
official
image
of
that
extension
so
that
we
will
be
yeah.
I
mean
that
the
problem
with
our
lives,
but
still
so
I
mean
if
we
are
anywhere
if
we
are
having
that
then
this
will
then
we
don't
have
to
worry
about
running
multiple
commands
directly
use
that
k60
yeah.
B
So
I
mean
I
was
just
thinking
of
some
other
ways
that
we
can
do
this
so
so.
Last
time
we
discussed
regarding
keeping
this
into
a
so
user.
What
user
will
do
user
will?
Keep
this
into
the
file
structure?
Keep
this
binary
into
file
structure
and
directly
use
that
from
that
location
right,
but
so
basically
provide
everything
into
the
config
of
kasich
service
itself.
But
could
we
do
anything
like
building
this
on
our
side
itself?
B
I
mean
whenever
we
are
deploying
this
service,
we
can,
if
you
can,
pass
any
parameters
or
something
or
ask
user
itself
to
keep
a
file
and
basically
install
this
and
set
up
this
service
itself
and
instead
of
using
the
default
k6,
we
will
switch
to
this
k6
yeah.
So
I
mean
yeah.
I
am
not
completely.
You
know
I
I
was
just
looking
into
the
I
mean
how
helm
box
and
all
that.
B
So
I
was
I'm
I'm
a
little
new
to
this,
but
so
I
thought
that
the
first
step
would
be
spinning
up
the
service
in
when
it
is
clustered
using,
but
I
guess
this
that
will
be
the
last
step
and
the
first
step
should
be
this.
Instead
right,
listen
to
captains,
this
cloud
event
right
and
print
some
logs
on
the
console
talking
about
the
kasich
service
as
a
separate
service.
B
So
probably
I
mean
yeah
this
we
could
do,
and
so
I
I
mean
I'm
even
I'm
not
completely
sure
how
we
will
be
building
this
image
when
we
are
deploying
and
how
basically
enabling
user
to
use
an
extension
doing
this.
So
even
I
will
have
to
take
a
look
into
this,
but
yeah
I
mean
this
is
a
thought
that
I
came
across.
So
I
mean
the
issue
of
the
the
issue
of
use.
Asking
user
to
put
binary
into
a
particular
location
will
be
and
that
binary
won't
become.
B
A
I
I
agree,
I
think,
wherever
possible.
I
think
we
should
follow
k6
as
best
practice
guidelines,
because
if
we
go
rogue
and
kind
of
go
off
on
our
own
little
way
of
doing
things,
we've
got
to
maintain
that.
So
if
we
can
follow
their
their
bet,
you
know
they're
the
experts
on
k-6,
so
let's,
let's
trust
them
and
follow
their
their
guidance
and-
and
that
certainly
seems
like
xk6.
So
let's,
let's
forge
ahead
with
that
path.
A
B
Yeah,
okay
cool,
so
I
mean
I
even
I
will
have
to
start.
I
mean
for
the
first
step
will
be.
This
won't
be
like
just
use
a
normal
k6
binary
and
execute
execute
test
using
that
so
in
in
the
service.
So
the
first
step
for
that
new
service
will
be
just
listening
to
this
captain
event
and
then
send
a
finished
event
and
then
start
running.
A
Now,
brad's
mccoy
who's,
another
g
sock
man.
I
had
a
very
good
idea
because
he's
mentoring,
the
flux
project
and
he
suggested
what
we
do
when
when
each
of
the
projects
are
at
a
certain
maturity
and
they're
ready
to
go,
we
actually
link
them,
because
if
you
think
flux
can
do
the
deployment
or
argo
can
do
the
deployment
or
whatever
tool.
A
But
in
this
case
flux
because
they're
working
on
it
and
as
soon
as
the
deployment
is
done,
we
can
then
trigger
our
k6
to
do
a
load
test,
and
then
we
can
use
captain
to
do
the
quality
evaluation.
So
it's
kind
of
kind
of
a
nice
story
that
he's
he's
come
up
with.
So
I'm
looking
forward
to
seeing
that
progress.
That
sounds
good.
B
B
B
Cool,
I
guess
I
don't
have
anything
more
to
add
right
now,
but
yeah.
I
will
start
working
on
this
and
yeah
if
you
have
any
any
initial
setup
kind
of
thing
for
me
for
for
basically
adding
it
into
the
git
wrap
of
the
k6
service
itself
like
there
are
some
checks
and
some
lending,
and
all
this
that
we
are
doing,
I
mean
that
captain
is
also
following
and
checking
that
the
committee's
commit
has
been
signed
off
and
all
that.
B
A
No,
I
think
the
important
thing
apart
from
the
technical
stuff,
the
important
thing
is
the
documentation,
as
we've
seen
with
the
captain
project
itself
and
any
project.
To
be
honest:
if
we
don't
get
good
documentation,
then
you
no
matter
how
good
this
is.
Users
won't
be
able
to
figure
it
out
and
use
it.
So,
as
I
say,
I
had
a
look
at
the
other
pr
and
suggest
some
changes
and
and
but
yeah
the
content.
A
There
look
really
really
good,
except
that
that
feedback
so
I'll
review
that
other
pr,
I'm
pretty
sure
it's
going
to
be
absolutely
perfect,
but
I'm
really
really,
I
hope,
you're
happy
with
progress
as
well,
because
I
think
we've
we've
come
a
long
way.
I
think
I
heard
we're
at
about
the
halfway
point
of
the
project.
I
believe.
A
Yeah,
okay,
okay,
cool!
I
don't
know
where
I
heard
that
from
them,
that's
nice.
We've
got
a
bit
more
time,
awesome
well
respectful
of
people's
times.
If
there's
nothing
else,
then
yeah
we'll
we'll
wrap
up
there
and
yeah
nice
job
nice,
job
and
mija.
If
you
have
any
thoughts
or
you
want
to
get
involved,
please
reach
out
to
jana
as
the
lead
on
this.