►
From YouTube: Meshery Development Meeting (June 16th, 2021)
Description
Meshery Development Meeting - June 16th, 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
Welcome
we
have
19
people
and
we
are
four
after
so.
Let's
get
started
with
the
meeting
today
is
today
is
16th
june,
and
this
is
the
measuring
development
call,
and
we
have
a
tight
agenda
here
and
mainly
we'll
be
focusing
on
the
next
release.
The
measure
ev,
six,
zero
dot,
six
release
and
how
measure
is
ready
to
be
released.
So
do
we
have
any
newcomers
on
the
call
today,
like.
B
C
Okay,
wait.
Do
we
so
I
don't
know.
D
A
A
E
Yeah,
hello,
yeah,
I'm
a
newcomer,
I'm
shum
singh.
Currently
I'm
doing
my
undergraduation
and
I
have
joined
machinery
just
a
few
days
ago.
I
think
two
or
three
days
ago,
okay
and
right
now
I'm
learning
golang
and
I
I
have
just
a
few
little
bit
of
knowledge
of
docker
and
rest.
A
Awesome
awesome:
you
are
the
right
place
to
learn
all
this
and
I
guess
we.
We
will
talk
about
some
of
the
imagery
projects
under
memory
which
use
golang
underneath
so
you
can
like
yeah.
You
can
probably
jump
into
some
of
that
nitish.
Do
you
want
to
introduce
yourself?
Are
you.
C
A
Okay,
so
let's,
let's
get
started
with
today's
topics.
First
up
we
have
drew.
G
Yeah
sure,
hey,
hey
guys,
so
people
who
are
not
new
here
would
have
been
seen
in
few
of
the
development
calls
that
we
show
off
what
we
are
working
in
mesh
map
right,
it's
pretty
exciting
stuff,
but
it
is
usually
under
construction
and
there
are
a
lot
of
bugs
over
there.
So
we
usually
keep
it
to
ourselves
to
people
who
don't
know
what
mesh
map
is.
It
is
basically
a
visual
topology
which
we
are
working
on,
which
would
be
our
extension
of
machines
in
which
there
are
basically
two
side
to
it.
G
One
side
is
visualizer
where
you
will
be
able
to
visualize
what
is
going
on
in
your
cluster.
You
will
be
able
to
interact
with
a
particular
pod
which
you
have
in
your
cluster
and
see
the
logs
and
execute
commands
if
you
like,
and
you
can
run
a
performance
test
and
stuff
like
that
and
there's
another
component
called
designer
which
helps
you
create
paddles,
while
which
you
can
apply
to
your
cluster.
So
like
this
is
a
gist
of
what
mesh
map
is.
We
have
achieved
some
of
the
functionalities.
G
We
think
we
might
be
ready
to
have
a
alpha
release
to
have
don't
take
very
excited.
This
would
be
very
small
number
of
people
who
we
might
give
mesh
map
for
them
to
use
and
tell
us
the
bugs
which
we
which
they
see
and
for
us
to
improve
upon,
like
this
is
air
of
the
people
who
are
participating
in
this,
except
that
they
will
be
bugs,
and
you
will
see
them
like,
don't
be
surprised
about
that,
but
we
want
to
resolve
them
as
quickly
as
possible
and
move
to
have
a
better
uxn.
G
So
because
of
that,
we
are
planning
on
releasing
like
the
alpha
state
in
the
next
week.
So
that's
the
gist
of
what
we
are
planning
over
here.
This
is
just
a
trailer
or
a
spoiler,
or
this
is
going
to
happen
and
friday.
We
will
probably
have
a
signup
form
or
something
like
that
for
people
to
sign
up
for
the
program.
C
So,
to
add,
add
to
that,
if
I
could,
the
there's
a
collection
of
individuals
that
have
been
working
on
on
meshmap
and
and
it's
one
of
the
and
you're
all
welcome
to
it's
one
of
the
very
few
areas
of
the
the
projects
that
go
on
here
between
get
nighthawk
and
meshery
and
service
mesh
performance
and
what
other
projects
am
I
in
and
all
the
projects
that
runs
a
bit
quick
or
is
the
only
project
in
which
people
don't
slow
down
to
explain
things
everywhere
else
things
get
explained
or
people
get
slapped
on
the
wrist
for
not
explaining
so
very
warm
community.
C
In
that
way,
also,
sometimes
we
go
a
bit
slow
because
we
are
trying
to
make
sure
everybody's
along
comes
along
for
the
ride
anyway,
so
that
functionality
mesh
map,
the
link
that
was
shared
in
the
chat,
is,
as
driven
said,
we're
ready
for
people
to
poke
at
it
shortly.
It
is
an
alpha
state
if
you
do
sign
up,
which
you
know
you
can
do
right
now
by
putting
your
name
under
the
in
the
bullet
points,
there
dhruv
will
probably
make
a
call
again
for
people
that
want
to
take
a
look
on
friday.
C
There
will
be
an
ask
of
those
that
participate
in
the
the
quote-unquote
program.
Very
light
thing,
but
there
are
mesh
map
was
designed
to
facilitate
any
number
of
tasks
that
people
might
want
to
do
with
a
service
mesh
like
like
almost
all
the
tasks,
a
lot
of
tasks
I
mean
it
doesn't
do
even
a
quarter
of
all
of
what
we
think
that
it
might
do,
but
of
the
quarter
of
things
that
it
does
do.
C
The
ask
would
be
that
if
you
sign
up
that
you'll
you'll
provide
some
feedback
that
you'll
you'll
execute
a
couple
of
user
tasks
to
verify
that
the
software
does
what
it's
supposed
to
do
and
just
provide
some
feedback.
So
it's
a
fairly
light.
Ask,
but
just
know
that
if
you
put
your
name
there,
there'll
be
a
few
questions
and
a
couple
of
tasks
pushed
your.
A
Way,
yeah
thanks
lee
thanks,
drew
yeah,
go
ahead:
oh
no
I'll!
Just
I'm
gonna,
mark
samir's
name
down
so
yeah
and
I
guess
drew
will
send
out
these
iron
forms
on
the
community
meeting
on
friday.
A
Okay,
so
let's
move
on
to
the
main
item
for
today's
call,
so
we
are,
we
are
moving
towards
the
next
release.
The
0.6
release
and
mesherie
has
different
components,
and
each
component
needs
to
be
ready
for
the
release,
so
we
we
are
used
to
using
this
time
to
track
the
progress
of
all
these
components.
A
A
C
We
lost
we
lost
november
for
just
a
moment,
but
devon
singh
did
you
want
to
say
hi
just
introduce
yourself
briefly.
It'd
be
nice
to.
I
Okay,
my
name
is
devon
singh
and
I'm
a
student
of
second
year
csc
computer
science
engineering
and
I
read
about
the
mystery
over
the
internet
and
I
love
it,
and
I've
also
read
about
the
container
d
and
I'm
very
much
excited
to
work
in
this
and
I'm
very
excited
to
get
merged
into
the
this
community.
This,
the
lovely
community-
and
I
need
a
help
for
these
with
you
all
guys,.
J
C
All
right,
and
if
a
d
yeah,
do
you
mind
sending
devbond
a
link
to
the
meshmates
page
that
way
he
can
pick
out
his
favorite
mesh
mate,
yep
cool.
So
if
navendu
can
hear
me,
he
will
interrupt
me
as
we
go
so
so
we're
about
ready
for
our
next
measuring
release,
we're
on
what
the
current
version
of
estuary
is
v05.23.
C
At
least
I
think
it
is,
and
well
there's
a
couple
of
things
to
reflect
on
here.
We
haven't
the
project,
has
not
re
achieved
a
1.0,
so
so
we're
not
signaling
to
everyone
that
it's
production,
ready
that
it's
there
are
aspects
of
measuring
that
that
really
are
production
ready
and
have
been
for
a
while,
and
people
have
been
using
it
for
a
while
and
and
some
of
those
people
are
on
the
call.
The
performance
management
area
of
maestro
is
probably
the
oldest
and
deepest
most
capable
area
of
meshri.
C
So
there's
work
around
service
mesh
patterns
and
that's
in
part
what
I'm
referring
to
about
this
significant
uplift
of
how
it
is
that
mescheri
does
life
cycle
management
of
a
service
mesh
anytime
that
there's
a
new
feature
brought
forth
in
a
project
like
measuri
there
that
new
feature
needs
implemented
in
a
few
different
areas,
so
mesherie,
if
you've
seen
its
architecture,
is
comprised
of
any
number
of
components.
It
kind
of
depends
on
your
deployment
like
what
what
all
you're
trying
to
manage.
C
Some
of
those
components
include
a
couple
of
clients,
a
user
interface,
the
measuring
ui
web-based
and
the
ctl
the
command
line,
client
and
so
as
new
constructs
as
new
features
are
brought
forth.
Those
things
sometimes
they
go
into
mastery
adapters,
measuring
server,
mastery
command
line,
client
measure,
ui,
mesh,
reoperator,
kubernetes
controllers.
C
C
This
is
extraordinarily
succinct
in
terms
of
how
it's
described
here
it
just
it
groups
things
into
measuring
and
measuring
ctl.
It
yet
has
yet
to
kind
of
break
out
measury,
ui
or
mastery
operator,
but
we've
done
that
here
in
today's
meeting
minutes.
C
So
what
we
want
to
do,
as
an
exercise
today
is
to
take
a
temperature
check,
take
an
assessment
as
to
the
status
of
individual
features
that
are
in
flight
and
you
get
in
some
cases
a
quantifiable
assessment
of
where
those
features
are
and
their
readiness
for
release
and,
in
other
cases,
more
like
a
gut
feeling
of
where
they
are,
as
the
project
evolves.
C
The
more
well
rigidity
is
maybe
the
wrong
word
that
that
has
a
negative
connotation
attached,
but
the
more
process-
and
that
will
be
wrapped
around
how
releases
are
done,
the
more
consistency
by
which
they're
run
the
more
consistency
by
which
they
were
released.
C
What
we're
doing
today
is
a
reflection
of
the
point
in
time
of
the
maturity
of
the
project,
so
at
some
point,
the
way
that
we
just
discuss
and
review
kind
of
release
status
will
probably
change,
but,
but
this
is,
I
think,
appropriate
for
now.
So
first
on
the
list
is
back
to
utkarsh
on
performance
profiles.
C
If
each
of
you
will
characterize
where
you
feel
you
know
where
the
what
the
status
of
these
areas
is
well
we'll
capture
it
here
and
follow
up.
Ultimately,
the
goal
of
this
exercise
is
to
try
to
identify
where
we'll
land
the
plane
when
we'll
make
the
release,
is
that
tomorrow,
or
is
that
four
months
from
now?
H
Yeah,
so
for
just
a
quick
update
on
performance
replies,
performance
files
has
a
revamped
ui
in
this
version.
Like
the
version
that's
running,
the
new
thing
is
that
we
have
calendar
view
and
those
flip
card
card
flips
and
those
kind
of
things.
The
thing
that
still
needs
to
be
done
here
is
right.
Now
there
is
a
nice
calendar
view
you
get
to
see
a
summary
of
all
of
the
states
that
you
have
already
run.
Something
like
scheduling
still
needs
vr,
but
not
right.
Now.
H
The
thing
that
needs
to
be
added
in
this
version
is
basically
when
so
right
now
the
calendar
is.
The
calendar
can
show
you
that
hey
you
run
these
lists,
but
you
cannot
get
more
details
just
on
the
calendar.
Probably
what
you
would
like
to
have
is
that
you
can
click
on
the
click
on
the
test
result
and
as
soon
as
you
click
you
get
a
nice
summary
of
the
days
that
you
run
probably
the
same
one
that
we
show
in
other
views.
H
So
that's
something
that
we
still
have
missing
in
calendar,
at
least
in
this
version.
In
future,
we
will
again
have
like
in
next
versions.
We
have
that
you
will
get
to
see
that
what
is
your
schedule
and
at
what
days
and
or
on
what
week
they
are
supposed
to
be
run,
but
probably
something
for
next
releases,
that's
pretty
much
it.
That's
that
is
left
in
this
particular
version
needs
to
be
done
in
this
particular
version.
H
Did
I
I
hope
I
didn't
miss
any
particular
feature.
Anyhow.
C
No,
I
don't
think
so.
There's
there's
a
minor
touch-up
to
the
way
that
the
details
are
shown.
There's
two
minor
touch-ups
some.
So
one
is
the
the
way
in
which
the
ui
will
swivel.
So
I
should
prob.
I
should
probably
have
up
measures
so
that
everybody
can
see
what
I'm
talking
about,
but
there's
a
slight
refinement
of
user
experience
there
and
the
other
one
is
there's
a
collection
of
there's
a
read.
Look
at
how
many
performance
test
results.
C
Administrators
can
see
so
I'll.
Take
those
two
notes,
but
I
think
you
hit
it
on
the
head.
Otherwise,
gosh.
H
H
I'll
I'll
probably
move
on
to
the
patents
one
if
performance
file
is
done
so
in
patents,
we
already
have
credit.
Now
the
credit
is
complete.
That
is,
you
can't,
create,
read
and
update
and
delete
all
of
the
buttons
from
the
from
from
mystery
api
point
of
view.
You
can
you
also
have
a
lot
of
functionalities
now
available
in
mystery,
adapter
for
istio,
so
he
can
basically
control
the
virtual
services
on
web
filters
and
provisioning.
H
A
lot
of
operations
on
mystery,
adapter
he's
basically
using
machine
learning
wire
patterns.
There
are
a
few
things:
three
operations
that
are
still
lived
in
machine
learning.
That
needs
to
be
done
in
this
release,
and
that
is
basically
adding
basically
adding
support
for
support
for
other
crds
like
destination
rule,
maybe
authorization
policy,
basically
all
of
the
crds,
that
that
still
comes
with
gateways
like
interest
gateway
and
across
gateways.
So
this
is
something
that
still
needs
to
be
done.
Probably
this
will
be
all
automated.
H
That
is,
you
should
be
able
to
run
a
few
scripts
or
something
like
that,
and
it
will
automatically
generate
json
schemas
and
those
kind
of
things
that
are
required
to
make
a
pattern
file
work.
So
this
is
something
that
still
has
to
be
done
in
this
particular
release.
Other
than
that
mystery
adapter
for
istio
is
completely
ready.
H
If
you
talk
about
capabilities
registry,
this
is
another
construct
that
was
created
in
this
particular
release,
and
that
is
now
the
now
mystery
has
a
capabilities
registry
which
is
basically
used
by
adapters
to
register
its
capabilities
like
workloads
and
trades,
and
those
kind
of
things
we
have
concepts
like
we
have
constructs
of
of
a
dag,
that
is
a
mystery,
is
capable
of
orchestrating
a
lot
of
tasks
for
you,
which
is
which
you
can
provide
to
it
via
virus.
H
So
you
can
write
a
pattern
and
what
measure
will
do
internally
is
basically
it
will
create
a
dag
and
will
execute
all
of
the
operation
for
you.
It
will
also
handle
parallel
execution
of
them,
basically,
dependency
management
in
the
in
some
sense.
So
this
is
also
an
addition
in
this
particular
release.
This
this
is
this
is
capabilities.
Registry
is
almost
a
complete
feature
right
now.
One
thing
that
needs
to
be
added
there
is
that
right
now,
capabilities
registry
only
supports
one
adapter,
so
you
can
have.
H
You
can
have
in
other
number
of
adapters
just
for
seo,
but
capabilities
register
will
only
register
the
one
adapter's
capabilities
and
not
every
one
of
them.
So
probably
that
is
something
that
needs
to
be
added
there
and
it
will
be
added
in
this
particular
release.
So
I'll
add
a
no.
That
is
support,
multiple.
D
H
D
C
Nice
so
adidi
and
rudraksh
not
nothing
like
getting
put
on
the
spot,
but
do
you
guys
want
to
reflect
on
these
areas.
J
Yeah,
so
a
little
bit
about
the
vr
I'd,
say
I'll,
just
post
the
link
in
the
chat
for
reference.
So
little
recap
on
that
pr.
It
was
about
adding
the
filter,
specific
config
to
the
onward
filter
resource
whenever
the
apply
image
of
filter
operation
was
called,
and
this
was
not
generic
enough
I'd
say,
and
I
don't
know
if
we
can
extend
it
to
everything
so
yeah.
I
guess
we'll
be
handling
this
using
patterns.
Now
am
I
right.
K
Hi,
so
I'm
sorry,
I've
been
a
little
busy.
I
I'll
have
to
look
into
this
link
or
d
support
for.
K
C
Makes
sense,
and
so
just
for
context,
I
think
for
everyone
else,
that
the
no
the
concept
of
service
mesh
patterns
is
actually
a
is
what
utkarsh
is
kind
of
talking
about
and
was
we
gave
a
lot
of,
I
think,
to
the
team.
Like
you
know,
you
all
gave
a
lot
of
demos
last
time
we
met
some
of
those
were
on
patterns
and
and
so
go
back
and
watch
last
meeting's.
Recording.
C
C
It
will
be
by
the
time
that
it's
done
in
the
mesh
reistio
adapter,
which
is
mandatory
for
the
this
release
it.
It
should
be
a
cookie
cutter,
I'm
trying
to
think
of
a
word
other
than
pattern
to
kind
of
stamp
out
across
the
rest,
so
so
good
timing
there
in
terms
of
your
focus,
I
mean
and
rude
rocks.
Actually,
it's
sort
of
the
same
thing
I
think
is
it
sounds
like
red
rock.
We
would
highlight
this
in
green
that
essentially
the
at
least
for
this
particular
issue.
C
This
item
is
closed
in
terms
of
filter
support,
yep,
that's
good,
okay,
by
the
way
for
most
of
you
that
are
on
the
call,
usually
there's
a
lot
more
demos
and
graphs
and
charts
and
like
diagrams
to
look
at
today.
We
just
so
happen
to
be
trying
to
assess
where
we're
at
with
this
next
release.
So,
but
it's
a
good
way
to
begin
to
digest
some
things.
If
you
haven't
seen
the
architecture
diagrams,
rather,
if
you
haven't
seen
them
lately,
as
a
matter
of
fact,
I've
never
seen
this
slide
right
here.
C
C
It's
a
curious
thing
if
you're
still
learning
mesherie,
that
meshri
has
a
component
called
meshsync
that
will
that
will
discover
and
keep
track
of
the
infrastructure.
The
service
meshes
the
applications,
the
kubernetes
infrastructure,
that's
under
management.
It
interacts
with
service
mesh
patterns,
as
as
individuals
as
people
might
load
up.
Those
patterns
have
them
deployed.
Mesh
sync
will
actually
rediscover
those
the
infrastructure
provisioned
by
the
patterns
so
kind
of
an
interesting
life
cycle
that
goes
on
so
a
lot
to
parse.
In
these
slides,
I
recommend
digesting
them
hanging
out.
We
should
is
anita
on.
C
We
might
want
to
do.
Is
you
had
some
great
ideas
about
some
things
that
we
should
be
doing
in
the
community
that
we
can
do
more
of
one
of
those
might
be.
C
It
might
be
like
a
session
that
you
know
everyone's
invited
to
that.
We
record
and
post
on
sort
of
like
a
deep
dive
into
mysteries
architecture,
potentially
so
there's
kind
of
a
lot
to
so
food
for
thought
like
it
and
and
that
doesn't
have
to
come
from
me
like
there's
a
lot
of
other
smart
people
on
the
call
that
have
like
created
this
stuff.
C
F
Sure
so,
basically,
let
me
just
show
this
one
so
I'll
be
talking
about
how
to
use
the
record
utility
that
was
recently
been
published
by
michael
one
of
our
community.
L
F
I've
added
a
make
command,
which
would
you
know,
make
sure
that
the
error
utility
is
basically
updated
before
you
push
the
changes.
This
same
make
command
can
be
integrated
with
a
currency.
I
to
do
some
specific
checks
before
the
pr
is
getting
merged
and
also
while
publishing
a
publishing
build
of
michelin.
F
So
so
that's
yeah,
that's
more
or
less
what
the
instruction
is
for.
Anyone
who
wants
to
contribute
or
anyone
who
is
contributing
in
a
in
a
project,
a
golan
project
of
f5
they
can,
they
will
be
able
to
use
this
make
command
if
they
don't
see
this
make
command.
It
means
that
it
has
not
been
integrated
in
that
project
yet
and
basically,
we
are
trying
to
push
it
to
most
of
other.
It's
a
new
feature,
so
we
are
just
trying
to
push
it
to
other
projects,
to
integrate
it
and
yeah.
F
That's
that's
pretty
much.
What
the
update
is.
C
F
You
mean
the
error
code.
The
new
error
coding
structure
that
we
follow
needs
to
be
integrated
in
other
products
right.
C
Right,
well,
actually
so
yeah.
So
if
you,
if
you
go
back
to
the
meeting
minutes,
I
think
we
can.
We
can
break
down
this
particular
area
into
three
deliverables,
and
that
is
that
and
that's
the
kind
of
the
focus
of
today's
call
is
like
hey:
what's
this,
what's
the
status
of
these
things
and
how
far
out
are
we
from
being
ready
to
release
so
the
first
one
is
like
at
the
air
code,
utility
itself
is
complete
merged,
ready
to
use
available
to
all
the
components,
and
is
that
true
or
no.
F
So
we
don't
need
a
utility
published
anywhere
or
we
don't
need
a
binary
out
of
it.
We
can
directly
run
a
go
command
using
that
package.
It
will.
C
Yep
yeah,
I
understand
no,
no,
I
mean
okay,
good,
so
I'll
answer
the
question
which
is
yes,
it's
completed
and
it's
available
for
use
that
use
can
be
as
integrated
like
as
like.
You
were
like
you
were
just
articulating
or
it
can
be
and
or
it
can
be
integrated
into
workflows,
and
so
so
that's
good,
so
status
is
what
we're
looking
for
and
so
status
of
the
utility
is
utility
itself
is
ready.
C
C
Now
that
might
be
covered
here
under
the
pervasive
workflow
of
pervasive
integration
into
workflows
for
each
measuring
component,
but
that
would
be
the
other
thing
to
follow
up
on
sort
of
okay
to
samir's
point
one
of
the
things
that
we
should
be
tracking
here
and-
and
I
mentioned
it
because
I
don't
know
that
we
have
one-
I
think
we
do
actually
there
can
you
grab
the
issue
number
that
tracks
this.
I
want
to
make
sure
that
rodolfo,
if
he's
taking
it
on
and
that
he
fully
understands
what
to
do.
C
G
A
F
No,
I
guess
I
had
marked
it
as
an.
There
is
no
update
on
that.
Currently,
you
can
move
to
next
level.
C
So
abhishek
the
goal
today
is
to
provide
status.
So
it's
like
the
the
status
is
it's
currently
not
ready,
and
then
you
have
a
an
estimate
like
less
than
a
week
is,
is
really
safe
for
it
being
ready.
A
F
There's
not
too
much
that
we
could
have
right
now,
so
this
is
the
pr
that
has
been
merged
now
this.
So
we
have
this
screen
for
the
dynamic
ui
and
what
we
have
to
do
is
have
it
look
better,
so
so
something
via
I
and
other
they
would
be
having
contact,
chat
with
and
chat
with
each
other.
I
have
planned
out
to
how
to
go
through
all
the
things.
F
F
And
just
one
thing
so,
apart
from,
like
you
know
the
part
of
this
dynamic
ui
will
the
left
side
pan
will
be
also
changed,
depending
upon
which
service
mesh
I'm
using
instead
of
showing
all
the
services?
Yes,
it
will
show
also
that
we
can
navigate
to
each
and
every
one
thing,
but
one
organization
may
not
use
multiple.
C
Yep
and
so
there's
an
open
issue
for
that.
That's
a
good
ask
and
and
something
that
something
that
we
should
we
should
do.
It
is
it's
a
great
you're
right
that
the
two
efforts
are
highly
related
and
that
and
that
the
that
ask
is
quite
achievable,
like
within
this
time
frame.
Samir,
if
you
happen
to
have
that
shoe
number
handy.
Please
do
you
know
drop
it
in
here
and-
and
I
don't
know
that,
like
ayush
in
particular,
has
visibility
to
or
is
aware
of
it.
A
Perfect
is
this
on
for
the
next
release
or.
C
C
Well,
yeah:
this
is
a
really
good
question.
It
might
be
a
soft
land.
It
might
be
that
so
I
use
right
now
so
so
to
answer
that
question.
C
It
might
be
the
case
that,
depending
upon
how
much
more
time
we
have
left
before
the
release,
it
might
be
that
we
softly
include
a
new
version
of
the
management
ui,
the
one
that
ayush
was
just
showing,
but
that
that's
available
at
a
separate
endpoint
and
that
users
are
made.
You
know
users
are
made
aware
that
they
can
try
out
the
new
new
ui
and
get
feedback
and
while
leaving
the
existing
one,
it
might
be
a
way
of
softly
releasing,
and
so
you
know,
speaking
of
which
I
believe
that
is
it.
C
So
I
use
if
people
use
the
car,
should
people
use
the
edge
channel,
what
what's
the
url
that
they
can
use
to?
Try
out
this
upcoming
new
management.
H
Ui
slash
management
issue,
that's
where
you
would
be
able
to
see
the
sd
management
page,
so
slash
management.
Slash
machining
is
where
the
dynamic
ui
is
it's
not
linked
on
the
navigator
yet,
but
definitely
should
be
accessible
in
this
release.
H
C
Okay
and
so
first
time
that
people
can
touch
that
so
if
anyone's
using
the,
if
you
switch
to
the
edge
release,
you
can
try
it
right
now
right
so,
okay,
good,
I
mean
not
that
there's
a
lot
to
try
it's
kind
of
what
ayush
was
just
showing,
so
it's
pretty
raw
but
but
the
earlier
the
feedback,
the
better.
C
C
Here:
here's
a
pop
quiz
forever
for
everybody,
hey,
there's
a
new
feature:
ayusha
was
just
saying:
there's
a
new
ui
being
worked
on
od
cars
just
said
it's
available
here
at
this
url
when
you're
running
mesheri,
which
I
am
right
now
and
I'm
running
this
stable
release
of
measuring,
at
least
as
much
as
I
remember
so,
I'm
running
yeah.
So
right
here.
What
channel
am
I?
What
release
channel
am
I
subscribed
to
the
stable
one
and
I'm
running
the
latest
version?
C
Okay,
good,
and
that
is
the
latest
version,
because
it
tells
me
that
okay,
so
if
I
try
to
go
to
that
url,
it's
not
going
to
work,
I
need
to
switch
to
the
edge
channel.
How
do
I
do
that?
Because
I
can't
click
here
and
it's
that's
not
available
here,
so
all
right.
If
anyone
can
tell
me,
I'm
not
sure
what
we
will
do,
but
we
will
do
something
and
it
can't
be
an
inside
has
to
be
someone
who.
C
Learned
it
for
the
first
time.
Okay,
so
you'll
tell
me
in
the
chat
but
great
so
who's
next
navindy.
Do
you
wanna
you're?
Given
the
time
do
you
want
to
knock
out
a
lot
of
the
mess
for
ctl
discussion
with
sharing
the
command
tracker.
A
Yeah,
I
guess
I
will
also
give
an
update
on
the
the
filter,
crud
and
application
thread
for
the
uip.
So
we
have
gaurav
has
been
working
on
the
filter,
credit
and
the
application
correct.
So
we
we
have
both
ready.
The
filter
card
is
already
merged
into
onto
master
and
the
application
credit
is
an
open
pr.
I
have
recently
added
support
on
the
measuring
server
for
it
so
yeah.
Now,
let's
move
on
to
the
machinery
ctf
stuff,
you
can
see
my
screen
right.
C
A
C
A
So
this
is
the
recital
command
tracker,
so
this
is
where
we
track
the
progress
of
all
the
measuring
ctl
commands
and
it
can
look
like
a
lot,
but
this
is.
This
is
really
helpful
in
deciding
what
features
to
be
worked
on
and
what
and
how
far
we
are
along
to
make
the
next
release
and
all
those
other
stuff,
and
we
also
use
it
to
track
bugs
and
track
the
progress
of
the
bugs
and
all
the
other
stuff.
A
So
for
the
the
version
6
release,
we
have
the
one
of
the
main
features
that
is
coming
up
is
the
kubernetes
support.
So
till
now
we
only
had
we.
We
only
had
measuring
ctl
only
had
the
support
for
deploying
measuring
on
the
docker
platform,
and
now
we
have
the
support
for
deploying
on
kubernetes
platform,
and
these
orange
cells,
you
can
see
are
issues
that
needs
to
be
fixed
prior
to
release
and
it
may
it
may
be
that
some
of
this
needs
to
be
updated.
A
But
generally
I
updated
this
today,
and
some
of
these
are
bugs
that
needs
to
be
fixed,
but
we
do
have
a
working
end-to-end
working
kubernetes
support
only.
We
need
to
fix
only
some
ux
bugs
and
yeah
and
moving
on
to
yeah
moving
on
to
the
performance
profiles.
A
Okay,
so
the
ctl
perf
commands,
which
is
being
tracked
here.
All
these
commands
are
working
and
we
are
also-
I
don't
know
if
jubilee
is
on
the
call,
but
jubril
is
working
on
adding
a
github
action
which
basically
wraps
around
this
machinery
ctl
command,
so
that
the
like
a
service
mesh
provider,
a
service
mesh
project
can
use
it
in
their
ci
cd
pipeline
to
test
the
performance
of
their
service
mesh
and
a
few
other
new
commands
that
were
added
was
pattern
and
filter.
A
So,
like
the
measuring
ui,
we
we
do
have
the
crude
support
for
both
the
filters
and
patterns
and
yeah
push
has
been
working
on
it
and
I
guess
I
think,
that's
that
it's
complete
and
the
only
missing
part
is
that
we
need
to
add
a
deployment
point
on
the
measuring
server.
So
everything
is
completed
in
the
measuring
sector
part
and
we
used
to
want
to
talk
about
the
status
of
the
check
command.
G
A
That
we
are
missing
from
from
pervasive
group
community
support
that
we
originally
intended
to
have
was
supporting
multiple
kubernetes
platforms
or
providers
like
gks.
B
Spend
much
time
last
night,
so
I
had
looked
at
the
articles
available
and
the
libraries
available
gold,
golang
libraries.
So
the
thing
is
there
is
a
way
to
list
the
kubernetes
config
based
on
a
project
ready.
So
far
we
were
using
some
service
account
name
and
the
region
name
as
input
when
we
try
to
conflict
so
that
that's
like
very
narrowed
down
thing
and
whatever
specific
thing
we
want
to
do
right
and
whatever
articles
I
found
they
do
it
at
project
level.
B
B
C
Yeah,
that's
essentially
what
we're
trying
to
assess
like
and
on
this
one.
It
might.
I
mean,
like
first
of
all,
just
not
to
share
personal
things
for
hussein,
but
but
kovit
has
touched
many
people's
lives,
and
so
you
know-
and
so
I,
which
wanted
to
say
like
who's,
saying
that,
like
it's
completely
understandable
that
that
you've
only
been
able
to
put
in
so
much
time
on
this.
So
this
is
one
of
those
things
that
we
probably
should.
C
We
shouldn't
stop
work
on,
but
we
should
probably
plan
that
it
that
it
lands
next
release
such
that
you
we're
not
adding
any
additional
pressure
to
to
things
that
you're
already
pressured
by
one
thing
we
might
want
to
do.
C
Well,
I
don't
know
it's
hard
to
tell
what's
more
popular,
like
people
deploying
mesherie
on
gke
or
in
samir's
case,
like
aks
or
like
mini
cube,
there's,
definitely
a
lot
of
people
who
get
their
hands
on
meshrey
for
the
first
time
using
minikube,
and
my
word
have
we
had
just
so
many
issues
with
certificate
data
missing
and
and
network
connectivity,
and
so
I
wonder
if
minicube,
maybe
if
we
shouldn't
try
to
change
priorities,
that
I
guess
a
good
question,
there
is
avishak
on
the
integration
of
mesh
kit
into
measuring
server.
C
Oh
because
I'm
sorry
thanks,
I'm
just
thinking
a
lot
of
measuring
ctl
itself
tries
to
communicate
both
directly
with
mescheri,
but
also
to
the
kubernetes
cluster,
to
provision
measuring
and
provision
the
operator.
So,
okay
do
as
you
work
on
some
of
those
your
mesh
kit
in
mesh
reservoir.
F
Ctl
not
in
every
functionality,
but
yeah
like
there
will
be
some
benefit.
C
So
it's
this
is
measuring
ctl
system
config.
C
So
last,
maybe
so,
there's
a
couple
of
other
items,
probably
the
push,
the
prof,
the
ability
for
the
perf
command,
the
perf
apply
to
work
along
with
perf
list
and
things
that's
imperative.
Otherwise,
we're
gonna
have
a
regression
issue,
and
so
we
do
need
to
focus
fairly
tightly
on
getting
the
perf
command
going.
C
C
C
G
G
L
A
Okay,
yeah
appears
like
we
can
give
you
access
to
some
some
of
the
other,
the
other
performance.
Just
so
you
can.
A
A
And
I
guess
like
we
are
at
the
we
are
almost
three
over
our
time.
I
guess
we
are
able
to
cover
all
the
topics
for
today's
call
with
that.
Let's,
let's
come
to
an
end
and
thank
you,
everyone
for
joining
and
sharing
the
progress
we'll
see
you
friday
on
the
community
call
bye.