►
Description
[SIG-Network] Ingress NGINX Bi-Weekly Meeting for 20220623
A
Hello,
everyone-
this
is
james
strong.
This
is
the
sub
project
for
sig
networking
ingress
engine
x.
It
is
june
23rd
and
as
always,
this
is
a
cncf
meeting.
So
that
means
it
is
under
the
coc
guidelines,
which
essentially
means
be
kind
to
each
other.
If
you
have
any
issues,
please
report
those
to
myself
or
ricardo
and
if
you
have
problems
with
us,
make
sure
to
report
those
to
the
cncf.
So
thank
you
everyone
for
joining
today
and
I
see
that
we've
got
one
new
folks,
folk
folk,
singular
joining
us
today.
A
Deshawn
did
I
pronounce
that
correctly.
Do
you
want
to
introduce
yourself
for
the
group.
A
Awesome
well,
like
I
said
previously,
thank
you
for
the
help
on
that
and
we'll
definitely
make
sure
we
discuss
that
today.
While
we
have
you
on
the
call,
anyone
else
wants
to
introduce
themselves.
D
A
I'm
gonna
go
ahead
and
pull
up
the
the
dock
and
we
can
go
ahead
and
get
started
discussing.
I
think
it's
fair
that
we
that
we
do
spend
the
15
minutes
on
triaging
issues,
since
we
didn't
yesterday
or
yesterday.
D
A
Meeting
before
we
go
into
the
topics
we
want
to
discuss,
or
do
you
think
we
should
just
go
right
into
the?
I
know,
we've
got
two
big
things
that
we
want
to
discuss
the
survey
and
the
stabilization
project.
A
Okay,
well,
as
we
talked
about
last
week,
I
wanted
to
make
sure
that
we
discuss
the
stabilization
project
and
the
document
that
we
put
together.
Hopefully,
everyone
had
a
chance
to
read
it.
If
not,
we've
got
it
here
on
the
screen.
The
big
thing
that
I
wanted
to
talk
about
was
the
timeline.
I
think
we
probably
should
put
a
timeline
on
this.
We
do
discuss
that.
We
don't
have
a
timeline
yet,
but
as
a
as
a
helper
for
folks
to
understand
where
we're
at
what
we're
trying
to
accomplish
as
well.
A
One
of
the
things
I
want
to
do
is
make
sure
we
have
ticket
items
for
each
one
of
these.
I've
created
three
new
labels,
stabilization
release
and
security,
and
I've
opened
up
a
new
project
to
track
all
of
these.
So
if
you
have
things
that
you
know
that
you're
working
on
that
we're
working
towards
on
the
things
that
we
discuss
here
in
the
stabilization
bits,
please
add
them,
add
those
three
labels
and
add
them
to
the
project.
So
right
now,
we've
got
a
few
things
right.
A
So
I
know
one
of
the
first
things
right
is:
we've
put
together
the
survey
that
we
shared
and
discussed
in
the
channel
I've
added
a
couple
of
the
I've
added
the
open
telemetry
bit,
because
I
know
that's
part
of
the
stabilization
stuff
we've
talked
about,
but
I
went
through
and
just
started,
adding
today,
some
of
the
other
ones.
So
again
you
all
should
have
access
to
the
project
and
be
able
to
assign
issues
and
prs
to
the
project
and
the
labels.
So
again
it's
just.
A
We
want
to
make
sure
that
if
we're
telling
folks
that
we're
going
to
put
a
pause
on
accepting
feature
requests,
we
should
show
them
the
work
that
we're
doing
and
just
making
it
available
to
the
community.
Was
there
any
questions
about
the
document?
The
only
thing
like
I
said
is
the
timeline
that
I'd
like
to
you
know
if
we
want
to
say
six
months
and
hold
ourselves
to
that
timeline,
or
is
there
anything
else
in
the
document
that
we
should
call
out
before
we
send
this
out
to
the
dev
mailing
list.
D
Yeah
and
to
to
just
to
be
clear,
I
will
show
this
as
well
on
sig
network
meeting,
which
happens
just
after
hours
here.
I
already
spoke
with
stick
network
chairs
and
some
other
folks
that
are
that,
aren't
tired
with
this
project
like
rob,
scott
and
even
alejandro,
which
was
the
previous
maintainer
to
see
what
they
think
about
that
and-
and
it
was
well
accepted,
the
idea
of
us
actually
freezing
the
features
and
working
on
on
the
bug
fixes.
D
Okay,
so
it's
something
that
at
least
the
the
maintainers
of
kubernetes
and
the
and
other
folks
that
they
support
the
only
thing
right
now
is
we
we
we
need
to
be
strict
with
our
decision.
D
So
if
we
say
let's
go
to
this,
we
cannot
open
exception
to
any
feature
any
other
thing
and
really
try
to
use
that
time
in
our
favor
to
make
this
stabilization
cool
right,
but
yeah,
and
I
think
it's
actually
fine
too,
to
announce
that
I'm
just
not
sure
about
the
timeline.
When
we
want
to
announce
that
james.
Do
we
wanna
announce
with
the
survey
after
later.
A
A
Yeah,
it's
difficult
to
say:
hey
we're,
gonna,
stop
doing
prs
or
feature
request
prs,
but
not
give
a
timeline
and
when
we're
going
to
start
doing
that
again,
that's
that's
the
thing
I'm
struggling
with.
D
A
E
I'm
just
going
to
say
tentatively
four
months
and
then
extensible
with
a
note
saying.
If,
if
we
are
not
done,
then
we
exchange,
I
mean
october.
A
Is
yeah
october
is
about
five
months
and
it's
towards
the
end
of
the
year.
So
I
I
think
if
we
say
six
months
that
might
we'll
have
something
to
talk
about
on
the
maintainer
track
about
where
we're
at
so
we
say
in
june,
we
did.
We
said
we
were
going
to
stop
this,
and
this
is
where
we're
at
with
the
project
the
stabilization
bits.
So
I
think
six
months
now
that
I'm
talking
out
loud
about
it
and
understanding
what
october
is.
E
Six
months
works
because
anyway,
activity
kind
of
slows
down
around
christmas
right
so
november
december
and
new
year's,
so
six
months,
seems
fine.
The
thing
is
there:
are
there
so
record
you're,
saying
no
exceptions
but
think
that
things
like
open
telemetry
and
the
other
modules
sidecar
thing?
So
we
have
to
make
a
note
in
this
in
this
day
in
this
announcement
that
those
kind
of
things,
those
kind
of
components
are
not
actually
a
new
feature,
but
they
are
like.
D
Yeah,
so
anything
that
we
can
consider
cleanup
can
actually
be
a
a
a
a
stabilization
path
right.
So
when
we
say
we
are
doing
the
open,
telemetry
thing,
I'm
actually
looking
into
doing
the
opportunity
thing
to
deprecate
the
zipkin
and
the
jagger,
and
all
of
the
model
is
in
favor
of
the
open,
telemetry
thing
being
the
couple
from
the
car
in
ginax
container
as
an
example
right.
So
so
I
think
yeah.
D
Let
me
let
me
rephrase
that
I
think
that
it's
not
an
exception
in
this
case,
but
we
need
to
discuss
instead
of
just
accept,
prs
and
say
yeah.
This
is
this
is
doable
or
not.
D
So
I
would
rather
prefer
like
giving
bringing
this
to
the
discussion
and
and
figuring
out
why
it's
important
to
have
the
open,
telemetry
thing
as
part
of
this
stabilization
code,
instead
of
just
saying
no,
we
are
not
going
to
do
that
because
we
are
in
the
middle
of
the
stabilization
time
period
right
so
so
so
so
I
think
I
I
what
what
I
don't
want
to
do
is
say
like
hey.
D
We
are
in
the
middle
of
this
feature,
something
that
we've
been
implementing
and
we've
been
waiting
for
someone
to
some
to
review,
and
now
you
are
saying
that
you
are
putting
a
feature
free.
So
cannot
you
just
message
this
before
you
put
the
feature
freeze
and
yeah,
I
don't
want
to
merge
anything
on
a
rush
just
because
we
are
gonna.
Add
some
future
freeze
right.
So
I
think
that,
as
an
example,
the
open
telemetry
thing
can
be
added
to
this
stable
release.
D
We
can
call
it
like
a
stable
release
in
six
months
that
we
are
gonna
have
with
a
bunch
of
cleanups,
and
I
expect
that
that
open,
telemetry
thing
to
be
part
of
of
the
cleanup.
On
the
other
hand,
I
was
a
bit
worried
when
I
was
working
as
an
example
on
the
open,
telemetry
thing.
I've
been
trying
by
myself
and
I've
seen
that,
even
like
the
compilation,
time
of
the
open,
telemetry
theme,
it's
like
bigger
than
the
the
jagger
one
as
an
example.
D
So
I
don't
want
to
stop
that,
but
I
think
we
we
need
to
have
some
be
really
diligent
on
that
right.
So
look
into
what
we
are
doing.
What's
the
value
of
doing
that,
then,
if
any
of
the
prs
they
bring
value
to
the
stabilization
that
we
want
right.
A
B
A
I
wanted
to
make
sure
that
folks
think
that
it
needs
to
be
there.
They
can
add
it
to
the
board
and
we
can
discuss
it
during
these
meetings,
so
yeah
so
okay,
so
we
we
agree
on
the
six
months.
We
agree
on.
If
anyone
from
the
community
thinks
there's
something
a
pr
that
needs
to
be
there,
they
can
add
these
labels.
A
The
other
thing
that
I
was
going
to
add,
too,
is,
on
the
feature,
request
template
I'm
going
to
add
a
link
to
this
discussion
so
that
they
can
see
this
and
just
add
a
note
saying:
hey
we're
doing
the
feature.
Freeze,
here's
our
justification,
so
please
consider
that
when
you're
adding
a
feature
to
it,
so
that
should
help
as
well.
A
E
A
Yeah,
so
that
was
going
to
be
one
of
the
things
I
wanted
to
discuss
and
figure
out
how
we,
how
we
track
that
out
and
ones
that
we
know
that
are
waiting
on
us
that
are
almost
at
the
finish
line.
So.
E
A
Yeah,
I
think
I
mean
we'll
we'll
keep
the
triaging
and
looking
through
the
the
issues
and,
as
we
see
fit,
we'll
just
add
them
so
that
that's
fine,
okay,
okay,
so
ricardo's
going
to
talk
about
this
sig
networking,
we
don't
have
the
survey
out
yet,
which
is
fine,
we'll
add
that
to
the
dev
mailing
list
once
we
have
that
out,
so
we'll
probably
send
this
out
today.
You
think
ricotta.
D
Yeah,
I
think
that
we
can,
we
can
announce
insignet
and
then
I
will
and
and
like
I
will
make
sure
that
they
understand
the
value
of
this
and
saying
that
we
wanna
announce
that
probably
today
and
unless
someone
wants
to
to
discuss
something
more
about
that
during
sign
network
meeting.
But
I
don't.
I
don't
want
to
spend
more
than
five
minutes
discussing
that.
A
Gotcha
also,
I
found
out
that
there
is,
I
don't
know
if
anyone
else
has
been
paying
attention.
I
found
out
yesterday
talking
with
eddie
from
six
cli
that
there
is
a
new
dev
mailing
list.
So
it's
not
kubernetes
dev
anymore,
that's
been
archived,
so
that
was
we
can
send
to
all
of.
D
A
D
A
Yeah
I'll
I've
got
time
today
too,
so
I'll
join
the
sig
networking
meeting
as
well
anyway,
we've
discussed.
That's,
I
think
enough.
So
here's
the
board
if
you've
got
anything
I've
added
several
things,
anything
that
has
cve
stuff.
That's
still
open.
I've
added
to
the
security
bits,
the
data
plane,
control
splits.
A
Some
of
the
other
issues
that
I
found
from
our
our
dependency
management
things.
So
I've
got
the
jaeger
open
tracing.
A
I've
also
opened
up
a
an
issue
to
get
dev
stats
for
us
to
try
to
understand
where
we're
at
from
a
community
perspective
any
of
the
other
stuff
that
had
cvs
and
attackers
and
bugs
that,
I
think,
were
there,
here's
the
124
issue,
so
this
is
probably
would
you
say
this
is
in
progress.
Gentile.
A
Yeah
I'm
working
on
it.
Okay,
awesome!
So
I
think
that's
the
ask
we
I
don't
know
if
we
should
spend
time
on
going
through
issues
now.
Do
you
think
that
would
be
helpful
folks
to
just
go
through
and
start
labeling
issues
yeah?
I
think.
A
E
Close
on
the
open,
telemetry
plan,
then,
if
time
is
left,
then
we
do
try.
Energy.
A
Gotcha,
that's
fair,
so
we've
discussed
that
we've
discussed
the
draft
I'll
go
through
and
make
sure
I
don't
think
we
have
something
to
track
this
one.
We
need
an
issue
to
track
these
I'll
go
through
these,
so
I'll
go
through
and
make
sure
that
we've
got
issues
on
the
project
to
track
this.
So
I'll
put
those.
A
Okay,
okay,
cool
that
one
still
needs
one:
okay,
all
right,
yeah,
let's,
let's
go
ahead
and
discuss
the
open
telemetry
bit,
because
maybe
we
can
help
with
my
confusion
on
it
and
we
can
just
work
through
that.
So
let's
go
ahead
and
do
we
have
do
we
have
that
up
or
is
it
just?
You
just
go
to
the
open
prs.
E
So
there
is
two
of
them.
This
one
is
to
fix
the
mesh
that
I
created
by
missing
by
changing
stuff
in
the
base
base
image
we
messed
with
the
entry
point,
and
we
also
put
a
variable
there
and
delivery
path.
So
reverting
that
this
one
is
just
to
revert
that,
but
the
bulk
of
the
work
is
actually
in
8622.
E
So
months
ago
it
wasn't
there,
then
we
put
it
in
working
with
asan
thinking
that
that
will
help
it
does
help,
but
in
a
different
way.
But
now
we
had
a
meeting
with
the
creator
of
this
pr
and
son
and
we
figured
out
that
if
we
mess
with
the
base
image,
then
we
can't
keep
it
same
like
for
every
kind
of
new
module
that
we'll
add
new
side
cut.
We
have
to
again
come
back
and
change
here,
so
completely
go
back
to
the
way
the
base
image
was
before
we
started
messing
with
open
telemetry.
A
D
Okay,
and
and
to
be
really
honest,
one
thing
that
I
was
expecting
from
these
telemetry
stuff
is
that
we
can
reuse
it
in
in
other
modules
as
well
right.
So
at
least
like
before
dropping
what
security.
At
least
we
can
migrate
mod
security
to
something
to
the
same
approach,
so
we
don't
spend
too
much
time
recompiling
the
base
image
every
time
we
want
to
change
something
and
right
and
we
can
keep
them
separated,
even
even
the
size
of
the
images
yeah.
E
Time
and
reducing
the
size,
it's
not
been
kind
of
completely
reviewed,
but
there
is
a
process
very
well
discussed
with
azan
and
with
this,
the
guy
who
put
this
pr
daniel.
So
now
we
know
exactly
if
we
add
a
new
model
where
we
need
to
work
with
it.
We
just
need
to
add
the
library
path
for
that
module
in
the
container
image.
This
is
sorry
the
controller
image
and
because
we
don't
have
to
in
future
change
anything
in
the
base
image
for
for
that
kind
of
work.
E
E
E
Right
but
just
fi,
this
8622
is
a
problem
because
the
the
the
contributor
daniel
dobrik
username
he
worked
on
this
on
his
fork,
but
in
the
main
branch.
So
he
had
issues
like
you
know
having
two,
so
he
created
now.
This
change
to
the
base
image
and
all
that,
so
he
had
that
problem
of
you
know
working
with
this
main
branch
right
now,
it's
there.
But
this
will.
He
will
close
this
and
move
the
changes
that
are
proposed
here
into
a
new
pr.
E
So
that
will
happen
later,
but
for
our
practical
purpose
we
can.
We
can
look
at
what
what's
happening
here,
because
it's
a
I
mean.
The
the
action
item
here
is
that
there
is
some
stuff
that
he
knows
and
is
certain
about,
and
hassan
also
talked
about
it
because
assign
is
a
contributor
to
open
telemetry.
So
the
compile
thing
and
the
enabling
component
is
now
working.
So
we
got
we
got.
E
We
tested
that
and
all
that,
but
then
daniel
or
username
dobrick
here
among
the
13
files
he's
changing
here,
he's
also
changing
a
bunch
of
go
files,
so
he
explained
that
he
copied
all
of
this.
E
The
changes
to
go
files
from
the
open,
tracing
open
tracing
module
and
he
doesn't
have
any
idea
about
how
to
what
what
these
go
files
do.
D
Okay,
so
let's,
let's,
let's
separate
this
in
in
in
two
steps:
okay,
so
the
first
one
is
to
get
the
open,
telemetry
bits
compiling
and-
and
we
can
say
as
an
example.
D
How
can
I
inject
the
open
telemetry
in
in
the
enginex
car
container
right
so
that
that's
how
I
would
set
this
as
a
goal
right
so
having
the
open,
telemetry
sidecar
as
part
of
the
compilation
and
like
let's
say
some
changes
on
the
helm,
chart
that
when
I
enable
open
telemetry
it
will
download
the
open,
telemetry,
sidecar
and
inject
and
say:
okay,
the
enginex
ingress
controller
container
does
have
in
china
open
telemetry.
D
So
I
would
say
this
is
the
first,
the
first
delivery,
okay,
okay
and
then
the
second
one
would
be.
Let's
say
now:
we
have
an
open,
telemetry
ready
container,
but
that's
a
no
op.
We
don't
have
any
operation
that
can
be
deal
so
my
second
step
would
be.
D
How
can
we
migrate
all
of
the
directives
that
already
exist
for
zipkin
and
jagger
to
open
telemetry?
So,
instead
of
creating
new
annotations
and
creating
new
things,
we
just
use
what
we
have
right
now,
but
using
the
open,
telemetry
model
right.
So
this
then
this
will
be
some
go
effort
awesome,
because
this
way
this
way
we
want.
Let's
say
we
are
not
kind
of
deprecating
the
feature
itself.
D
We
are
just
saying
your
annotations
will
keep
working,
but
we
are
now
using
open,
telemetry
module.
We
don't
have
zipkin
and
jagger
mod
and
zipkin
and
open
tracing.
I
just
can't
remember
all
of
those
but
on
on
the
audinginax
container
anymore
right
and
then
we
can
establish
a
path
of
like
deprecating
these
annotations
later
and
saying.
Okay,
everything
now
is
open,
trace,
open
telemetry,
but
but
but
right
now
I
will
just
split
in
two
right.
D
The
first
one
is
making
sure
that
the
open
telemetry,
the
open
telemetry
model
can
be
injected
into
a
an
ingress
controller
image
and
not
be
used,
but
we
know
that
it's
there
right
and
then
the
second
one
would
be
like.
How
can
we
establish
a
process
of
like
is
open
elementary
enable
is
the
mod?
Could
the
model
be
be
found
or
not
before?
Just
configuring
the
template
and
then
are
you
using
an
annotation
of
jagger
of
jaeger.
So,
let's,
let's
configure
open
telemetry
using
those
themes.
Are
you
using
zipkin,
whatever
okay.
E
D
I'm
I'm
all
about
merging
if,
if
you
folks
can
make
it
like
open,
telemetry,
sidecar
container
work
and
even
have
some
readme
on
how
can
you
inject
the
open,
telemetry
side
car
into
the
cor
ingress
in
genetics
even
not
being
used?
I
think
it's
fine
to
merge
that,
and
it's
going
to
be
a
no
up.
We
are
just
going
to
compile
every
time
you
compile
in
gen
x.
We
are
going
to
compile
open
telemetry
as
well,
and
then
we
can.
D
We
can
add
into
some
some
effort
just
to
use
that,
and
I'm
really
looking
into
that,
because
I
spent
too
much
time
trying
to
make
open
telemetry
working
in
gynex,
and
I
couldn't
so.
If
someone
just
brings
me
this
ready,
I
will
just
start
testing
whatever
the
way
I
can.
E
So
the
beautiful
thing
that
has
happened
with
asan
coming
in
is
that
the
compilation
work
it
works
perfectly
now.
Imagine
we
compiled
the
module
also
and
the
libraries
and
the
daniel,
the
other
guy
who
put
the
br
on
his
laptop.
I
saw
it
working
working
for
him,
so
it's
a
complete
end-to-end
working
as
in
he.
It
compiles
the
modules
load
and
he
can
actually
does
that
work
in
cloud
build.
E
E
You
know
beautiful
work
about
two
weeks
ago,
so
compilation
is
not
a
problem
at
all,
so
daniel
used
that
compilation
also-
and
he
did
his
own
comparison
and
he
actually
did
the
integration
work
as
in
loading
it
so
it
loads,
and
he
actually
pointed
his
grafana
at
the
at
the
end
point,
but
he
did
in
a
very
very
you
know
non-standard
way,
I
think
he
used
his
company's
grafana
and
then
the
data
source
was
all
crazy.
So
I'm
working
on
that
part.
So,
okay,.
D
E
The
limited
time
we
have
this
was
the
beautiful
part
that
he
said,
we'll
split
the
goal
and
all
the
annotation
parts
so
that
I'll
get
I'll
start
working
on
with
daniel
on
that
part.
E
But
if
you
want
to
so
just
the
the
takeaway
is
that
compilation
working
enabling
and
enabling
the
module
these
two
things
are
working.
So
if
you
want
to
dive
into
it,
ricardo
now
asan
is
on
on
the
chat.
He
can
explain
some
things,
especially
not
about
just
compilation
but
compilation
with,
and
the
integration
and
the
decision
or
design
you
want
to
make
for
jager
and
zipking.
D
D
So
I
will
try
to
make
some
time
on
on
next
next
week
on
sorry
next
week
to
to
to
take
a
look
into
that
and
and
and
make
sure
that
at
least
I
can
in
some
of
my
spare
time
test
it
as
well
right
so
based
on
what
you
did
just
test
it
and
say:
okay,
I
can
I
can
make
it.
I
can
work
from
here
right
now,
so
just.
E
The
question
the
question
you
are
asked
a
question:
another
question
is
an
answer
that
zipkin
nager
zipkinheager
modules.
Are
there
already
already
included?
So
if
we
deprecate
from
the
current
code
base
the
pin
and
jager
when
we
that
is
fine,
and
when
we
compile
and
open
telemetry
the
way
it's
being
compiled
now
we
can
use
the
jager
and
zipping
that's
included
there.
Sam,
please
correct
me.
If
I'm
yeah,
I
just
wanted.
C
D
Okay,
but
there
is
no
big
worries
on
that
folks,
because
I
expect,
with
the
survey
as
well,
that
someone
raises
the
hand
saying
hey,
I
use
jager
a
lot,
so
don't
don't
deprecate
it
or
like
hey?
No
one
actually
cares
about
jagger,
so
just
go
to
open,
telemetry
and
deprecate
everything
right.
D
So
we
can
work
based
on
that
right
now
and
and
and
see
how
the
survey
goes
so
make
sure,
actually
that
you
have
a
lot
of
people
answering
that
survey
as
well,
because
we
are
going
to
start
deprecating
stuff
based
on
that
and
if
we
can
just
go
directly
to
open
telemetry
without
compiling
I've.
Seen
that
one
of
the
problems
was
like
compiling
all
of
the
grpc
stuff
to
make
the
jaeger
stuff
work
and
was
like
yeah.
D
So
if
you,
if
you
can
just
go
with
the
pure
approach
of
open
telemetry
for
me,
would
be
better
right.
I
just
I
just
need
to
know
if
there
are
a
lot
of
people
around
there
using
the
jager
back
end
okay,
but
I
will
try
to
sync
with
you
folks
asynchronous
as
soon
as
I
get
some
some
some
time
next
week.
It's
going
to
be
easier
for
me.
E
A
Awesome
is
there
anything
major
that
we
need
to
discuss?
Should
we
discuss
the
election
id
for
124,
or
do
we
just
go
to
the
action
items
and
open
topics.
A
D
I
want
to
make
sure
that
this
is
part
of
the
stabilization
process
loan.
I
think
that
one
of
the
things
that
we
need
on
the
stabilization
is
to
have
some
metrics
on
what
we
change
if
improves
or
decreases
the
performance
right.
So
so
I
will
I
wanna,
I
wanna
look
into
that.
D
If
you
can
make
some,
I'm
not
sure
if
you
are
comfortable
with
that,
but
making
some
presentation
about
that
on
our
next
meeting
and
how
it
looks
like
like
you,
you
told
me
that
you
already
have
some
some
some
market
data
on
that
and
some
github
actions
that
run
so
if
you
have
some
space
to
do
some
10
or
15
minutes
presentation
on
that,
I
think
that
other
people
taking
a
look
into
that
not
only
me,
but
everybody
in
this
meeting
will
see
the
value
on
that
and
they
may.
D
D
D
D
A
E
E
This,
if
you
can
just
go
to
github.com
and.
D
A
Open,
I'm
I'm
not
sure
yeah
chrome's,
my
default
browser.
Sorry,
let
me
just
share
my
screen.
My
desktop.
E
D
Probably
just
you
can
see
long
because
it's
your
ripple,
probably
there
is
something
that
just
you
can
see
right.
E
Oh
damn,
okay!
Sorry,
then,.
D
D
E
E
A
Come,
let's
run
the
workflow
on
main?
What's
the
k6
load
test,
what
variable
do
we
need,
then,.
E
You
can
share
your
screen.
I
start
sharing
mine.
E
E
So
the
k6
website,
so
this
is,
if
you
go
to
an
old
run,
this
is
current
run.
If
you
go
to
an
old
run,
you
see
and
go
to
k6
dot
yeah.
I
o,
I
think,
maybe.
A
Okay,
we'll
let
it
run
and
we
can
look
at
it.
Does
it
not
show,
does
not
show
the
results
in
the
github
action
it
does.
E
It
does
so,
if
you
look
at,
you
can
open
a
tab
for
for
a
old
run
and
then
in
any
case,
at
the
end
of
this
run,
you
will
see.
E
A
E
In
them
you
can
open
up
under
under
in
the
pr.
There
is
a
test
file.
Javascript
you
can
get
and
put
the
issue
right
now
is
that
this
runs
on
github
actions
right,
so
the
so
the
vm
that's
created
for
for
github
actions.
Events
is
2
core
7,
gb
and
right
now,
I'm
not
using
the
whole
thing.
So
I
I
can't
start
this
stock
right
now,
because
if
this
is
approved,
then
I
can.
We
have
to
start
writing.
E
Godzilla
has
to
help
and
to
tune
these
tests
to
to
use
the
you
know
entire
two
core
and
7gb,
and
and
for
our
for
our
for
the
english
english
use
case.
That
is
so
right
now
just
get
and
put
just
to
a
simple
http
bin
backend.
E
E
E
E
E
A
Yeah,
so
this
is
a
good
first
step
of
just
understanding
where
we're
at
yeah.
No,
that's
good
it
it.
It
moves
the
needle.
That's
that's
the
main
thing
we
didn't
have
the
data
before
now.
We
can
have
a
little
bit
more
data
and
we
can
start,
like
you
said,
fine-tuning
the
the
testing,
okay,
and
so
this.