►
From YouTube: Meshery Development Meeting (June 1st, 2022)
Description
Agenda-
[Ashish] Demo of multi cluster and remaining required considerations.
Small chip issue to point out.
Extra modal
[Abhi/Ashish] Refactoring multi-context features. UI changes needed on #5528
Action Items:
Send query params with required API Calls
Refractor and regenerate all grapqhQL endpoint with send Variables of context details/clusterIDs [In Progress]
Add a global redux variable to store available context and active context [Done]
Make the context switcher from navbar work [Done]
[Nithish] Replacing kubeopenapi-jsonschema with cuelang for component generation.
[Srinivas] Integration Test Details: Wrong color and missing pass/fail icons. #5540.
[Tathagatha]Added multiple k8s version for adapter tests #5548
[Abhi] Establish connection between RJSF schema and kubernetes special fields
[Pranav] Updates on user profiles
[Alpha] Blog on mesheryctl reference docs evolution
[Uzair] Working on redesigning settings page.
[Krish Aryan] Completed dark/light readme logos #5550
Join the community at https://layer5.io/community
Find Meshery on:
GitHub: https://github.com/meshery
Twitter: https://twitter.com/mesheryio
LinkedIn: https://www.linkedin.com/showcase/meshery/
Docker Hub: https://hub.docker.com/u/layer5/
C
C
A
E
B
Good,
so
so,
by
the
way
for
it's
always
it's,
I
always
it's
always
pleasant
for
me
to
sit
on
quiet
silently
over
here
and
let
other
people
have
to
figure
out
how
to
enunciate
other
people's
names
and
if
they
have
a
nickname
or
a
short
name,
or
I
pretty
much
go
by
anything.
So
it's
really
easy
to
get
my
attention
also.
B
My
my
name
only
has
three
letters
which
is
makes
it
super
easy,
but
for
durian
woo
thanks
for
reintroducing
or
thanks
for
like
introducing
again
today,
it's
nice
nice
to
get
acquainted,
yeah
go,
go,
go,
go,
find
your
spot,
so
to
speak
on
the
project,
whether
it's
this
one
or
any
of
the
related
projects.
There's
a
ton
of
things
to
get
into
don't
hesitate
to
ask
a
bunch
of
questions
as
you
go
to
get
engaged.
That's
probably
the
best.
B
The
best
way
to
get
engaged
make
some
friends
make
a
mess
clean.
It
up
break
something,
go
fix
it,
but
yeah,
and
so
leonard,
is
on
mr
well
so
leonard,
occasionally,
you'll
see
his
other
first
name
akane
and
then
occasionally
he'll
confuse
you
with
a
bit
of
a
kc,
and
I
I
think
I
think
I
prefer
the
kc,
but
anyway
so
leonard
is
here.
That's
great
leonard's
super
active
in
the
monday's
websites
call
and
so
and
then
other
folks
that
might
be
new
today.
B
Have
you
been
on
this
call
before
two
things,
one?
If
you
haven't
please
say
hi
and
introduce
and
whether
you
have
or
haven't
you're
gonna
you'll
have
to
add
your
last
name
in
zoom,
so
we
know
which
type
on
you
are
right
now,
you're
the
only
one,
but
that's
not
always
the
case
tap
on.
Do
you
have
your
working
audio,
if
you
do
say,
hi
heck?
If
you
get
working,
video
come
off
and
say
hi
in
a
video,
it's
even
better.
B
B
B
B
If
you
have
topics
just
drop,
your
drop,
your
name
and
the
topic
at
the
bottom
of
the
meeting
minutes
everybody's
welcome
to
drop
anything
they
want
to,
hopefully
we'll
make
through
the
whole
list
bobby
will
make
sure
that
we
do
he's
got
a
big
stick
behind
him.
He
pulls
out
sometimes
so
ashish
first
up
demo
of
multi-cluster
and
remaining
considerations
around
support
for
many
kubernetes
clusters.
Okay,.
B
So
context
here
is
like
a
late
coming
feature
in
the
dot.
Six
release
has
been
mesher's
ability
to
simultaneously
or
like
concurrently
manage
any
number
of
kubernetes
clusters
today.
The
way
that
people
connect
largely
the
way
they
connect
clusters
to
measuring
is
either
by
low
by
loading
their
cube,
config,
multiple
cube,
configs
or
by
simply
deploying
measuring
inside
of
the
cluster
and
then
basically
measure
yourself
configures
from
there.
So.
A
Basically,
it
is
being
faced
using
graphql
queries
which
are
working
at
the
backend.
But
you
know
there
is
some.
There
are
some
considerations
around
it
in
the
front
end
which
would
be
done
by
today.
So
let
me
get
back
to
the
things
that
I
can
demo
today,
which
is
so
we
here
we
have
our
context
switcher,
so
we
have
multiple
context
right
now,
I'm
connected
to.
A
I
have
my
two
two
of
my
clusters,
loaded
into
my
my
mesh
has
detected
two
of
my
clusters,
which
were
in
my
cube,
config,
which
I
loaded
so
I
have
mini
cube
and
mini
cube
2,
and
I
can
ping
each
one
of
them
to
make
sure
that
I'm
connected
to.
Basically,
there
is
no
connectivity
issues
and
then
I
have
two
of
my
adapters
running
here.
One
is
my
ht
adapter
and
one
is
my
linkedin
adapter.
A
So
for
demo,
what
I'll
be
doing
is
that
I'll
use
this
context
feature
to
first
deploy
istio
service
mesh
in
my
mini
cube,
cluster
link
id
service
mesh
in
my
mini
cube,
2
cluster,
and
then
this
select
I'll
use
the
select
all
to
deploy
a
sample
app
in
both
of
my
clusters
at
once.
So
let's
start
with
the
so
I
basically
I
can
perform
any
sort
of
sort
of
operation.
So
what
you
seeing
right
here
is
what
we
call
mesh
ops
v1,
because
this
is
very
static.
A
Stuff
that
you
see,
for
example,
you
click
on
buttons
and
stuff
gets
deployed.
We
also
have
a
design
configurator,
which
gives
you
a
lot
more
flexibility
and
lot
more,
basically
a
handle
on
the
things
that
you
can
do
with
your
infra,
but
just
to
avoid
you
know
any
kind
of
complexity.
Clicking
buttons
is
very
simpler
when
it
comes
to
demo,
because
there
is
chances
that
things
wouldn't
break
because
I'm
just
clicking
buttons
so
I'll
first
select
my
and
to
showcase
right
now,
I'll
I'm
doing
cube
curl
to
my
mini
cube.
A
2-
and
this
is
my
mini
cube
after
the
graphql
thing
is
done.
We
would
be
able
to
able.
We
would
have
been
able
to
see
this
thing
on
the
dashboard
itself,
but
you
know
pardon
that
so
I
have
selected
my
mini
cube
cluster
and
if
I
click
on
deploy
my
ht
service
mesh-
and
I
come
back
on
my
mini
cube.
So
I
can
see
two
of
my
ports
coming
up
right
away
and
nothing
happened
in
my
mini
cube
too.
A
If
I
go
back
in
my
link
and
in
the
linker
d,
adapter
dash
the
adapter
life
cycle
and
if
I
click
on
mini
cube,
2
now
mini
q2
is
selected.
So
if
I
deploy
my
linkedin
service
mesh,
I
come
back
and
it's
on
my
mini
cube
to
status
and
yep
in
a
second.
I
should
see
linker
d
ports
coming
up
and
it
comes
up
so
my
mini.
So
right
now
I
am
inside
of
my
mini
q.
I
have
my
steel
service
mesh
deployed
in
my
mini
cube
2.
A
I
have
my
link
rd
and
now,
let's
deploy
a
sample
app
in
both
of
those
at
once.
So
if
I
come
back,
I
select
all
and
I
click
on.
We
have
a
bunch
of
applications
from
which
we
can
select.
So
let's
say
I
go
with
book
info,
and
so
one
of
the
pods
have
come
up
in
my
mini
cube
too,
and
in
my
mini
cube.
Also
these
details
and
ratings
pods
have
started
to
come
up.
A
So
I
just
so,
if
you
have,
let's
say
10
clusters,
you
just
click
on
this
select
all
and
in
all
of
your
clusters.
The
same
operation
would
be
applied
at
once,
and
this
whole
thing
is
concurrent.
When
I
say
concurrent,
I
mean
in
the
terms
of
go
routines,
so,
for
example,
if
so,
because
we
are
not
doing
it
sequentially
if
one
of
the
cluster
there
is
some
issue
with
one
of
the
clusters.
A
You
still
have
stuff
deployed
in
the
rest
of
the
clusters,
so
yup,
that's
pretty
much
it
around
what
I
I
could
deploy
designs,
but
so
that
that's
pretty
much
it
around
what
this
multi-cluster
thing
did
and
now
let
me
get
back
to
the
things
that
are
left
right
now.
So,
for
example,
here
we
should
be
seeing
the
style
so,
for
example,
I
have
selected
now
select
all
so.
A
A
So,
for
example,
if
I
click
on
these
chips
here,
I'm
able
to
do
this
connectivity
test
and
the
way
it
happens
is
that
when,
when
this
request
goes
to
the
server,
it
also
carries
the
context
id
of
the
cluster
in
which
I'm
performing
my
connectivity
test.
But
I
think
the
same
thing
is
not
implemented
here,
because
if
I
click
here,
I
get
an
error
saying
empty
context
id
so
I
think
that's
just
a
small
little
thing
to
point
out
this
same
logic
can
be
just
as
directly
and
easily
transferred
over
here.
A
So
that
was
one
small
little
nitpick
to
point
out.
The
other
one
is
the
extra
modal
so
yeah.
So
let's
say
that
a
user
has
selected
four
out
of
these
five
clusters
and
then
they
click
back
on
this
kubernetes
logo,
and
then
they
forget
about
what
they
had
selected
and
they
come
on
the
systeo
lifecycle
page
and
they
click
on
this.
They
click
this
button,
but
it
is.
A
It
can
be
the
case
that
they
they
deploy
the
service
mesh
on
the
cluster
which
which
they
didn't
mean
to
deploy
the
cluster
on,
so
they
should
be
when
they
click
on
this
thing
or
when
they
perform
any
operation,
whether
it's
deploying
a
service
mesh,
whether
it's
deploying
a
sample
app,
whether
it's
you
going
inside
of
configuration
and
deploying
one
of
those
designs.
Any
of
these
operations,
which
are
concerned
with
you
know,
which
are
concerned
with
the
with
the
cluster
ids
and
the
whole
multicluster
thing.
Should
these
operations
should
have
a
modal.
A
So
when
someone
clicks
on
this
this,
instead
of
directly
deploying
we
show
them,
we
are
going
to
deploy
this
thing
inside
of
these
this
cluster,
and
this
this,
my
basically
some
extra
information
about
what
what
we
are
about
to
do,
so
that
there
is
context
to
that
and
if
they
and
dynamically
they
can
just,
they
don't
have
to
go
back
and
reselect
those
things
on
the
mobile
page
itself.
They
can
select
and
deselect
clusters
and
then
apply
operation
on
there
so
yeah.
These
were
the
two
little
things
to
point
out.
A
So
if
you
have
selected
two
clusters,
maybe
we
have
a
visualizer
in
mesh
map,
so
you
would
be
able
to
see
data
from
both
these
clusters
on
the
visualizer,
although
we'll
have
to
do
a
lot
of
cleaning
up,
because
if
you
have
selected
10
clusters-
and
you
see
direct
data
from
10
clusters
at
once
on
the
visualizer,
this
is
going
to
be
a
little
cluttered,
but
that
will
handle
there
and
coming
back
to
the
only
the
last
thing
that
I'm
concerned
about.
Is
this
operator
configuration
page?
So
we
would
need
some
kind
of.
A
A
It's
completely
a
single
context,
aware
thing
so,
basically
earlier
we
had
current
stuff
something
known
as
a
current
context,
so
I
think
this
also
needs
to
go
context
name,
and
this
was
previously
useful
because
of
the
fact
that
we
had
a
construct
of
current
context
and
because
things
were
pretty
much
single
cluster,
but
this
will
go,
and
since
this
will
go,
this
operation
page
has
to
exist
in
the
context
of
a
given
context.
So
when
user
clicks
on,
let's
say
this,
this
button
basically
means
to
deploy
the
machinery
operator.
A
Mystery
operator
further
deploys
mesh
sync
in
a
nats
broker,
whose
entire
job
is
to
keep
pumping
data
from
your
cluster
to
a
database,
which
we
can
further
use
to.
Do.
You
know
messy
stuff.
So,
basically,
when
someone
clicks
right
now
here,
the
one
one
thing
that
we
can
do
is
that
if
we
go
completely
with
multi-context,
if
they
have
select,
if
they
have,
you
know
clicked
on
select
all
and
if
they
click
on
this.
A
We
deploy
mesh
the
operator
on
all
of
these,
but
it
becomes
hard
because
it's
not
a
operation
that
is
specific
to
cluster.
It's
an
operational
thing,
which
is
completely
our
thing
and
when
one
of
the
clusters
give
error
while
deploying
operator
and
the
other
ones
don't
we'll
have
to
you
know,
go
fine
grain,
those
error
messages
and
also
it
would
be
nice
to
do
this.
A
One
thing,
one
cluster
at
a
time
to
configure
this
messaging
operator,
there
might
be
some
use
in
selecting
all
at
once,
but
four
four
operators,
three
operators
at
once
becomes
problematic
after
a
point.
So
that's
the
only
place
where
I
was
considering
to
have
one
context
at
a
time
other
than
this
operator
configuration
thing.
Everything
can
be
multiple
context
at
a
time
just
as
easily
and
after
we
redesigned
this
thing,
users
would
be
able
to
view
a
operator
configuration
model
for
each
of
the
clusters
that
they
are
connected
to.
A
So,
for
example,
if
I'm
I'm,
I
have
my
mystery
operator
deployed
in
mini
cube,
but
not
in
mini
cube
2.
I
would
some.
There
would
be
some
way
here
to
go:
switch
between
mini
cube
and
mini
cube,
2,
and
I
would
see
inside
of
mini
cube.
This
thing
is
off
in
mini
cube.
This
thing
is
on
so
each
context
would
have
a
different
opera.
A
Most
probably
today,
we'll
do
a
maybe
after
the
call
we'll
we'll
do
a
core
debugging
session
to
speed
things
up
and
then,
most
probably
by
tomorrow,
we'll
all
we'll
also
be
seeing
data
over
here
from
multiple
clusters
and
also
inside
of
meshmap
visualizer
so
and
I'll
hand.
Over
this
now
to
avi
to
point
out
the
his
progress
on
the
ui
side
of
the
things.
I've
showed
it
on
the
back
inside
of
the
things.
A
This
operation
will
be
applied
to
these
many
contexts,
how
they
can
switch
the
context,
so
the
pr
for
that
model
is
already
up,
and
that
will
be
that
will
be
available.
As
with
watch
and
the
second
thing
that
is
the
settings
page,
it
should
show
all
the
contacts
and
all
the
operations
the
user
can
be
able
to
perform
on
these
contacts.
So
I
only
have
have
final.
A
B
Thanks
and
so,
but
by
the
way
to
add
to
that,
it's
it's
not
a
it's,
not
a
small
feature
or
not
a
small
set
of
considerations
to
make
inside
of
measuring
about
the
like.
You
know
about
actively
managing
multiple
clusters.
At
one
time
any
number
of
things
could
be
changing
in
one
cluster
or
the
next
and
making
sure
that
the
user
is
seeing.
B
Those
updates
as
quickly
as
possible
inside
of
mesh
for
ui
is
is
an
important
thing,
but
also
like,
hopefully
intuitively
providing
them
the
right
level
or
easy
control
over
how
to
split
up
their
view.
How
to
let
them
know
that
yes,
they're
looking
at
five
of
the
clusters,
not
ten
of
them,
that
they
have
connected.
B
Maybe
they
have
two
groups.
You
know
five
for
dev
five
for
prod
something
like
that
right
now
we
don't
have
our
meshery
doesn't
have
the
con
concept
of
groups
of
clusters,
and
maybe
in
the
future
it
will.
Maybe
one
of
you
will
implement
that
for
some
people,
that's
not
very
important,
because
you
don't
because
you're
not
running
around
with
10
or
50
or
100
clusters,
so
groups
doesn't
really
help
you
for
others
who
are
running
around
with
200
clusters,
300
clusters.
B
B
It's
so
great
just
I
I
kind
of
paused
there
and
mentioned
mention
some
of
this
to
say
that
it's
not
necessarily
obvious
the
impact
that
more
than
one
active
cluster
has
on
how
people,
how
a
user
is,
viewing
things,
how
you
deploy
mesherie,
how
its
components
stay
in
sync,
when
someone
wants
to
perform
an
operation
against
the
cluster,
how
do
they?
Maybe
they
have
five
clusters?
You
know
10
clusters,
like
I
said
they
only
want
to
apply
it
across
five
who's.
B
There
is
going
to
talk
more
about
that,
but
maybe
they
have
a
particular
sequence
by
which
they
want
it
to
occur.
They
want
it
to
occur
on
the
third
cluster
first,
then,
the
second
you
know
they
want
to
so
so.
There's
a
level
of
there's
more
levels
of
sophistication
to
kind
of
potentially
layer
on
the
community
has
talked
about
a
workflow
engine
as
a
roadmap
item
and
workflow
engine
would
really
help
facilitate
dependencies.
A
A
So
all
the
changes
need
to
be
done
on
the
front
end
as
well,
but
there
were
some
minor
ui
books
that
was
coming
across
the
changes
and
there
were
some
different
challenges,
while
you
know
passing
the
context
as
well
as
cluster
ids
at
some
or
the
different
filters.
So
as
written
here,
there
were
three
changes.
You
know
made
three
major
domain
where
the
ui
changes
need
to
be
done
for
the
multi-cluster
thing
to
work
and
to
get
in
sync
with
the
backend.
A
So
this
these
two
things
are
context
feature
as
well
as
a
redux
variable
are
to
store
the
active
select
clusters
and
you
know
active
context
as
well
as
not
acute
context,
etcetera.
I
mean
yeah,
so
those
things
are
done.
It's
just
about
refractoring
and
regenerating
all
graphql
queries
and
the
and
the
endpoints
that
is
need
to
be
completed.
Yet
it
is
in
progress
and
almost
50
percent
of
the
work
is
done.
A
A
A
A
They
yeah
they
are
responsible
for
handling
the
operations
and
things
that
you
can
do
with
the
service
which
so
yeah,
although
they
are
not
like,
although,
although
currently
we
only
have
routers
for
service
messages
like
the
future,
you
know
goal
is
to
have
something
I
mean
those
would
not
be
limited
to
service
measures
but
to
cloud
native
infrastructure
stuff.
So
you
know
something
to
keep
in
mind,
but
so
essentially
we
have
something
called
as
a
capabilities
registry
or
a
component
registry.
A
A
Yeah,
so
I
was
yeah,
so
there's
a
registry
where
we
actually
store
those
capabilities,
so
the
capabilities.
What
I
mean
is
that
like
and
each
adapter
like
whenever
they
boot
up,
they
actually
come
and
register
like
what
are
the
things
that
they're
capable
of
doing
and
stuff
so
and
right
now
like
each
and
every
adapter
that
we
have.
Let's.
If,
if
we
take
istio
for
example,
then
hdr
comes
again
and
registers
the
components,
so
those
are
kind
of
like
a
representation
of
like
what
are
the
things
that
that
you
can.
A
One
can
actually
do
with
the
measuring
steel
data
or
sort
of
like
what
it
supports
at
this
point.
So
to
see
it
visually
like
when
you,
when
we
open
mesh
map,
which
is
a
plugin
of
measuring
so
and
there
are
two
parts
to
mesh
map,
we
have
a
designer
and
we
have
visualizer
and
right
now,
I'm
in
designer
right
now
and
like
you,
can
actually
see
that
there
are
a
list
of
components
that
you
can
actually
use
to
design
our
you
know
infrastructure.
A
So
right
now
like
we
have
kubernetes
components
and
core
components
which
are
actually
registered
by
measuring
itself,
so
these
kubernetes
components
are
registered
by
machine
server.
So
in
this
case
actually
measure
receiver
also
acts
as
an
adapter,
not
acts
as
an
adapter
in
the
sense
like
it
actually
registers
the
communities
related
to
components.
So
each
of
these
components
are
actually
like
yeah
capabilities
like
that,
are
the
register
with
kubernetes.
So
two
measuring
communities
is
sort
of
like
a
client
and
it
actually
registers
all
these
components.
A
So
with
this
we
can
actually
do
stuff,
and
you
know
design
our
you
know
infrastructure.
So
this
is
not
only
limited
to
mesh
map.
We
also
use
the
same
thing
in
the
design
configurator
as
well.
If
you
have
seen
it
yeah
so
yeah
like
we
have
a
design
configurator
that
we
actually
use
the
same
stuff
so
yeah.
A
This
is
to
give
a
bit
of
a
context
about
like
what
these
components
are
and
what
what
the,
if
I
say,
capabilities
then
now
you
might
actually
get
no,
no
have
an
idea
about
what
I'm
talking
about
so
now
previously,
like
we
used
to
have
a
node
like
a
nodejs
binary
to
you
know,
extract
these
definitions
of
the
schema
definitions
of
the
components
from
you
know
different
places.
So,
for
example,
if
you
take
humanities,
then
we
actually,
what
we
used
to
do
was
like
yeah.
A
There
is
a
open
api
specification
for
kubernetes
and
we
actually
used
that
that
particular
specification
and
we
extracted
the
definitions
of
each
and
every
component
that
we
needed
so
basically
like
those
are
the
custom
resource
definitions
but
yeah.
So
this
is
for
communities,
but
then
for
me,
but
then
for
different
adapters
like
there
are
some
different
ways
of
actually
you
know
getting
that
definitions
and
schemas,
so
yeah
so
to
unify
all
those
like.
We
actually
had
node.js
binary
over
here,
which
allowed
us
to
do
things
like
you
know.
A
A
What
you
ask
so
more
to
be
yeah
so
essentially
like
on
one
use
case,
would
be
that
let's
say
you
actually
give
it
a
open,
fps
schema
and
then,
like
you
say,
you
want
all
the
crts
so
yeah.
This
is
something
that
we
have
been
using
this
particular
library
for
and
yeah,
and
also
for
machines
to
let's
say
if
you,
okay,
I'll
get
to
that
later.
A
So
this
is
how
we
have
been
doing
it
till
now,
but
there
have
been
some
issues
since
like
we
are
like,
whenever
measuring
server
is
a
go
binary
and
it
inside
a
go
binary.
If
you
want
to
actually,
you
know,
create
the
node
runtime.
If
you
want
to
run
this
binary,
then
you
actually
have
to
do
some
do
some
stuff
before
you
actually
can't
run
this
binary,
such
as
you
know,
loading
the
runtime
and
stuff
so
that
actually
used
to
take
some
time,
and
that
was
yeah.
A
I
don't
know
about
you,
but
like
the
previous
mission
that
I
had
like
it
was
very
slow
and
on
top
of
it
like
when
I
actually
used
to
generate
these
components,
it
used
to
take
a
lot
of
time
so
yeah
I
was
like
we
were
actually
looking
for
other
alternatives
as
well,
and
that
is
when
we
actually
found
that
there's
something
called
cube
so
yeah
as
you
can
see
like
it.
What
it
means
like
q
means
like
it.
I
I
don't.
E
A
Learn
more
about
queue
by
going
to
the
website
or
the
documentation,
but
yeah
this
is
sound
of
like
like
it
actually
allows
us
to
do
mainly
to
you
know,
manage
configurations
easier,
and
it
also
helps
in
querying
scripting
and
a
lot
of
bunch
of
other
stuff
which,
which
you
know
align
with
our
use
cases
so
yeah.
So
that
is
what
we
did
like.
I
actually
made
a
prototype
by
you
know
replacing
this
cube,
this
node.js
binary
with
q
lang
and
it
it
was
pretty
successful.
A
E
A
Yeah
apologies
so
yeah,
as
I
was
saying,
like
yeah.
These
are
the
this
is
kind
of
like
the
main
pr
which
actually
replaces
this
thing,
so
you
guys
can
look
into
it.
I've
shared
the
link
as
well,
and
if
you
have
any
questions,
feel
free
to
you
know,
if
you
think,
if
you
think
something
doesn't
make
sense,
then
yeah
you're
welcome
to
share
your
views
or
suggestions
if
you're
aware
so
yeah.
A
We
also
have
the
same
thing
for
for
each
and
every
adapter,
which
so
I'll
just
I'll
just
show
an
example
of
what
the
change
means
in
my
store
right
now.
So
previously,
as
you
can
see
like
we
had
this
particular
field
over
here
so
essentially
like
app,
is
the
one
is
the
place
where
you
actually
store
the
information
about.
A
You
know
what
manifest
you're
providing
and
what
information
you
want
to
like
what
information
you
want
to
extract
from
it
sort
of
thing.
So,
in
this
case
like
if
you
actually
looked
into
this
particular
example,
then
the
manifest
that
you
are
providing
would
actually
be
the
that
is
also
discussing.
A
B
I
figured
that
there's
there's
a
number
of
what
I
consider
pretty
decent
resources
for
anyone
who
has
filled
in
a
community
member
form.
You
end
up
with
access
to
well
a
shared
drive
that
has
a
bunch
of
resources
and
one
of
those
resources.
Is
this
a
slide
deck
called
mastery
architecture
and
there's
a
fair
bit
of
time?
That's
been
put
into
this
particular
deck
in
each
of
the
slides
and
trying
to
keep
them
up
to
date
to
date.
B
One
way
to
consider
what
natish
was
saying
is
that,
to
the
extent
that
you're
able
to
go
into
measuring
as
a
user
and
create
designs,
whether
you're,
using
whether
you're,
using
that
visual
designer
that
the
dish
showed
or
you're
using
the
design
configurator
it's
a
couple.
There's
a
or
whether
you're
just
dealing
with
the
ammo
and
you're
importing.
B
And
so
yeah
he's
a
way
of
gosh.
I
wanted
to
say
it
a
different
way,
but
that's
about
as
concise
as
it
gets.
It
needs
to
be
able
to
model
your
desired
state
right
and
help
interact
with
kubernetes
interact
with
other
infrastructure
running
on
top
of
kubernetes
other
apps
things
running
on
top
of
kubernetes
to
con.
You
know
provide
the
right
configuration
the
specific
configuration
that
you
desire.
B
Maybe
that
model
that
you
wanted
was
to
configure
some
retries
or
to
just
deploy
a
docker
compose
app
or
something
like
that
as
meschery
ingests,
your
model,
it
needs
to
persist
that
to
its
database,
persist
that
on
disk
model
that
in
a
consistent
way.
So
that's
what
the
dish
has
been
talking
about
is
the
speed
by
which
mescheri
server
when
it
spins
up
today
when
mesh
reserver,
you
turn
it
on,
and
you
point
it.
You
connect
it
to
one
of
your
kubernetes
clusters.
B
B
If
you've
been
around
kubernetes
very
long
you're
aware
of
the
fact,
there
are
custom
objects
or
custom
resources,
crds
custom
resource
definitions,
which
means
that
any
given
kubernetes
deployment
might
might
not
look
quite
like
another
kubernetes
deployment
they're
still
compatible,
but
they
might
have
a
bunch
of
different
capabilities
that
they're
running.
So
that's
why
mesh
reserver?
Does
this
real-time
interrogation
to
figure
out
what's
going
on?
It
runs
discovery
as
it's
running
discovery.
It
generates
these
models
and
persists
them
so
that
you
can
then
describe
how
you
want
your
infrastructure.
A
F
F
A
Yeah,
I
think
we
can
make
a
mesquite
release
by
tonight,
because
I
also
have
made.
I
also
have
made
a
change
which
I
can
talk
about
at
the
end,
if
we
get
time
which
is
about
improving
white
spacing
around
components,
so
I
think
that
change
in
your
change
can
get
messed
into
a
new
release,
and
that
is
yeah,
and
I
think
that
that
is
more
a
reason
to
make
a
release
than
we
had
previously.
E
A
A
A
B
G
B
D
G
G
G
A
So
both
of
these
approaches
have
their
own
merits
and
one
merit
of
the
hard-coding
approaches.
What
the
hacker
just
said
is
that
we
wouldn't
need
to
make
any
change
in
the
adapters
and
pretty
much.
This
is
a
easy
way
to
do
this
without
breaking
anything
the
but
yeah,
and
I
I
think
both
of
these
approaches
have
there.
If
someone
has
a
better
alternative
and
merits
or
demands
to
add
in
both
of
these
approaches,
taken.
D
D
G
B
G
D
G
G
A
Yeah,
so
so
moving
on.
The
next
item
is
by
me,
which
is
establishing
connection
between
scheme
and
our
kubernetes
specific.
So
as
a
lot
of
people
like
a
lot
of
you
may
know
that
we
are
using
schema
to
generate
the
you
know,
forms
you
are
seeing
here.
So
these
forms
are
generated
by
the
artists
schema
and
you
can
generate
yours
by
you
know
the
playground
that
rj17
provides.
So
this
is
the
way
you
are
generating
schema.
A
So
what
you
are
doing
is
you
are
providing
the
title,
description,
type,
etc.
Just
to
you
know,
transpile
it
to
the
the
actual
ui
the
form
right,
so
the
ui
form
yeah.
So
we
are
using
it.
But
you
know:
kubernetes
also
generates
its
own
schema
and
it
has
some
special
values
for
it,
which
is
like
x,
kubernetes
list
type
or
map
types,
or
there
are
many
more
like
this.
A
So
what
we
have
you
know
the
only
community
kubernetes
understands
it
and
the
artist
of
schema
itself
doesn't
understand
it,
but
since
we
are
completely
relying
on
the
schema
for
generating
the
form
or
and
the
ui,
so
the
fields
are,
you
know
not
properly
handled
by
the
ui,
and
it
shows
some.
You
know
non-interactivity
or
something
weird
happens
when
one
of
these
types
are,
you
know
inferred
by
the
forms.
A
So
we
have
already
done
for
some
of
the
fields
and
if
some
of
you
are
interested
in
are
doing
it,
I
will
be
very
happy
to
provide
you
the
context
in
the
slack
like
or
if
you
want,
if
you
want
to
discuss
more
so
we
have
to
just
provide
a
list
of
these
values
and
the
corresponding
mapping
to
the
schema
so
yeah
that
was
update
and
if
any
one
of
you
just
want
to
get
started
with
it.
Yeah
please
ping
in
the
public,
channel
or
rtm.
F
Yeah,
I
will
be
sharing
my
screen
and
showing
the
updates
so
first
of
all,
I'd
like
to
give
a
little
bit
of
extra
knowledge
about
what
I'm
doing
and
why
it's
necessary.
So,
for
example,
whenever
you
are
logging
into
mystery,
no
matter
how
you
are
running
and
when
you're
running
in
locally
or
to
docker
extension
or
to
dockerized
or
communities.
F
So
you
always
see
this
screen
so
the
when
it,
and
then
you
select
your
provider,
why
a
provider
is
necessary
because
it
will
help
you
to
like
save
your
changes
in
the
cloud
so
that
whenever,
whenever
next
time
you
log
into
the
machine,
you
have
your
changes
there.
You
can
see
again
your
application.
You
can
again
see
your
pattern
so
that
all
the
changes
are
persisted
with
the
with
the
facilities
with
the
infrastructure
we
have
so
like.
I
usually
use
github
so
I'll
log
in
with
a
dummy
account.
F
So
when
I
log
in
it
gets
authenticated
through
my
account-
and
it
takes
all
the
information
from
the
third
party
provider
which
I
just
clicked
on,
that
was
github
and
github
provides
my
email,
user,
id
and
other
stuff
and
also
the
my
profile
picture.
So
the
problem
is
that
we
cannot
edit
any
of
this,
like
whatever
was
provided
by
github
or
linkedin
linkedin
or
google
was.
F
We
cannot
edit
it
right
over
here
in
messaging
and
that's
the
thing
what
I'm
moving
forward
with
like
so
to
facilitate
a
profile
page
where
we
can
do
all
these
necessary
changes
to
a
user
profile,
and
one
more
thing
to
add
on
is
like
the
whenever
you're
logging
in
you
are
always
redirected
to
this
link
for
authentication.
So
after
my
changes,
you
can
directly
log
into
mysticloud
and
see
your
profile
page
for
editing
or
all
the
in
all
the
things
you
have
in
account.
F
F
A
number
one
rank
it's
still
in
progress,
but
I
know
the
ui
is
not
good,
but
the
thing
is
that
now
what
you
can
do
is
that
you
can
see
the
username.
You
can
see
your
first
name
last
name
your
email
id
and
a
bit
of
bio,
like,
of
course,
we
know
what
it's
not
provided
by
the
third
party
provider,
but
you
can
add
it,
and
the
thing
is
that
now
you
can
edit
it
as
well.
F
If
I
don't
want
to
say
this,
I
can
say
something
like
this
and
then
you
can
save
the
changes,
though
this
save
changes.
Query
is
not
in
place,
but
that
would
be
done
soon,
so
other
than
that.
The
fetch
query
is
done,
and
the
same
thing
then
would
be
shown
in
the
measuring
ui
through
an
extension
point,
which
I
would
be
making
one
minute.
F
Which
would
be
right
over
here
right
over
here?
There
would
be
new
extension
point
that
would
be
profile
and
that
would
load
up
the
same
thing,
which
I
just
showed
you
and
then
we
can
do
all
the
profile
change
related
changes.
And
if
you
want
to
know
more
about
the
design,
then
you
can
go
to
this
link
in
the
sigma
which
you
might
have
got
access
to,
after
filling
the
form
member
community
form.
And
then
these
are
the
changes.
This
is
how
it
will
look
like
after
my
changes.
F
A
Had
any
addition,
yes,
I
was
like
now
the
only
the
admins
web
admin
admin
role
can
generate
infinite
tokens.
So,
with
my
changes,
any
user
who
logs
in
will
be
able
to
generate
infinite
tokens
and
all
the
tokens
here
he
or
she
has
generated-
will
be
visible
like
in
the
in
the
user
profile.
There
is
a
tab
like
api
tokens.
I
can
show
you
the
demo,
but
it
will
take
time.
So
I
will
move
with
my
agent
item.
That
is
settings
page.
A
Yes,
yes,
so
this
is
the
new
design
which
incorporates
a
multi-cluster
thing
that
demo
does
so
now
our
ui
doesn't
doesn't
show
all
details
about
all
the
custom
we
have
to
switch
to.
We
have
to
switch
with
the
context
feature
and
then
then
we
are
able
to
perform
our
operations
on
the
context.
So
this
with
this
new
design,
all
the
context,
the
user
has
will
be
displayed.
All
the
details
like
whether
it
is
whether
measure
is.
F
Deployed
within
the
within
the
humanities,
cluster
or
outside
the
cluster,
then
this
last
discovery
like
when
it
was
last
discovered
or
when
it
last
the
when
last
was
the
machete
server
was
successfully
able
to
connect
to
the
of
this
kubernetes
cluster,
and
this
individual
row
will
be
expandable.
So
when
the
user
clicks
here,
the
row
will
expand
and
this
table
kind.
F
F
A
F
Contacts
in
the
cube
config
and
this
this
model
will
further
expand
to
enable
user,
whether
to
enable
user
to
select
which
contacts
or
which,
which
contacts
he
want.
He
or
she
wants
to
add,
and
then
the
user,
when
user
clicks
on
register,
that
context
will
be
added
and
displayed
in
this
table,
and
there
is
one
more
consideration
like
this:
is
this
delete
database?
So
this
database
is
a
system-wide
operation,
so
this
button?
Where
should
this
button
be
kept?
F
A
A
A
Is
this
table
displayed
all
the
details
like
or
more
detail
system
added,
just
on
the
first
site
yeah,
it
looks
pretty
complete
to
me
if
there
is
yep
yeah,
it
looks
pretty
complete
to
me.
There
is
nothing
on
the
off
the
top
of
my
head
that
I
can
point
out
that
it's
lacking
and
if
I
find
out
something
then
I'll
tell
you
about
it.
But
right
now
I
think
it's
complete.
It's
pretty
cool.
A
Yeah
so
I
think
yeah
we
can
conclude
this
meeting,
so
we
have
a
few
items
that
is
left,
but
since
we
are
out
of
the
time
we
can
cover
these
in
the
as
a
future
item
in
the
next
development
call,
by
giving
the
priority
as
the
first
member
to
speak
up
on
their
items,
so
yeah
thanks
well,
thank
you.
Everyone
once
again
that
you
joined
the
machine
development
meeting
and.