►
From YouTube: Meshery Dev Meeting (Sept. 28th, 2022)
Description
Meshery Development Meeting (September 28th, 2022)
Agenda:
[Debopriya] Community Meeting on Friday - Hacktoberfest Prep: Easing into Cloud Native Open Source Projects.
KubeCon talks to be posted. Meshery and Service Mesh Performance Project Office Hours. Details and opportunity to participate forthcoming.
Volunteers: Deepesha
[Ruturaj] [Server] Backend for catalog for local provider #6258
[Harkirat] Improvement in mesheryctl #6174.
[Yash] Run through of progress on Meshery UI overhaul
[Pranav] Updates on Adapter versions not being displayed #issue6245
[Harshit] Configuration Page Suggestion.
[Pankaj/Gaurav] Meshery v0.7.0 Planning
Refactoring Meshery UI: meshery-ui-restructuring | How to contribute
Volunteer Needed: v0.7.0 Roadmap feature champion assignment refresh
[Subedy] Discussion on Integration test failing
[Divine] UX: New Compatibility Matrix design
[Harshit] meshery and meshery.io dark Theme discussion.
Breaking this big feature request into smaller milestones.
Hacktoberfest
[Ashish] Adding E2E tests in Meshery #6264
[Ashish] Fixed failing tests
[Ashish] Pointing urgent bugs on RJSF form
Adding unnecessary fields onto the design.
Missing labels and annotations
For the Design Configurator, even Name and Namespace are missing.
Add search feature
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/
B
A
Hello,
everyone
welcome
to
today's
mystery
development
meeting
and
we'll
be
starting
off
with
a
new
Commerce
introduction,
so
hectober
Festival,
coaching
and
yeah
we'll
have
a
lot
of
newcomers
in
coming
weeks
and
in
October
months,
especially
so,
starting
with
today
we
have
the
pesha
I
think
deepesha.
You
have
joined
the
call
for
the
first
time
right
if
I'm
not
wrong,
like
I,
always
I.
C
A
I
think
shubham
has
some
problems
with
his
audio.
So
probably,
if
you
have
joined
this
call
for
the
first
time,
then
it's,
it
will
be
great
if
you
can
put
in
the
chat
and
give
us
a
brief.
This
I
mean
brief
of
yours
so
that
we
know
about
you
a
bit
more
and
looking
at
the
list
again.
I,
don't
think
there
is
anyone
new
here.
So
let's
get
rolling
with
our
first
item,
which
is
about
the
hack,
Tower,
Fest,
preparation
and.
B
D
D
D
If
your
audio
is
working
feel
free
to
say
hi
for
a
moment
and
just
introduce
yourself,
it's
always
nice
to
get
to
know
everybody
give
everybody
a
chance
to
get
to
know
you
and
shubham.
If
your
audio
isn't
working
feel
free
to
just
say,
hi
and
chat
too
that'll
work.
I
did
catch
your
high
in
the
slack
chat,
which
was
great.
C
C
It's
fine,
you
can
continue
so
be
back
with
the
community
meeting
once
more,
we'll
be
having
an
event
on
Friday.
So
the
main
focus
of
this
event
is
to
conduct
a
sort
of
a
workshop
for
first-time
contributors
who
are
relatively
new
to
open
source
it'll,
be
like
the
timing
is
just
perfect
because
we
are
just
starting
off
with
Oktoberfest,
and
the
main
purpose
of
this
event
will
be
to
guide
newcomers
guide
first
time
contributors
through
their
entire
process.
C
We
are
planning
to
conduct
demonstrations
of
how
to
use
gate,
how
to
use
GitHub
how
to
make
your
first
PR
and
mostly
surrounding
our
projects.
So
talking
about
that,
we
have
a
couple
of
volunteers
who
have
who
will
be
speaking
at
this
event,
but
I
know
on
this
call,
particularly
we
have
had
contributors
who
have
been
contributing
to
our
projects
from
a
long
time.
So,
if
any
one
of
you
is
interested
to
speak
for
some
time.
C
In
this
event,
maybe
in
the
form
of
a
demonstration,
maybe
show
something
on
next
to
the
UI
or
anything
you'd
like,
or
just
talk
about
your
experience
regarding
open
source,
something
that
will
be
helpful
for
first-time
contributors.
You
can
volunteer
right
now
as
well.
We
can
give
you
a
slot
in
the
meeting
and
you
can
take
it
forward
from
there
and,
apart
from
that,
I've
also
prepared
a
doc
for
brainstorming
issues
for
hacktoberfest.
So
it
is
categorized
into
the
different
organizations
we
have
and
further
into
the
different
repositories.
C
So
if
you
guys
have
any
free
feature,
requests
or
any
bugs
that
you
have
noticed
which
are
simple
to
solve,
which
we
can
create
issues
for
them
and
we
can
assign
them
to
all
the
in,
like
contributors
will
be
coming
in
the
next
month.
So
add
your
list
over
here.
Any
one
of
the
call
is
like
your
anyone
is
feel
free
to
add
that
please
so
yeah,
that's
all
from
me
about
Oktoberfest
and
if
any
one
of
you
do
want
to
speak
at
the
event,
please
reach
out
right
now.
C
C
B
E
A
A
B
Yeah
I'm
there
actually
so
I
have
fixed
the
image
residual
Behavior.
So
the
current
behavior
was,
like
the
user,
wasn't
able
to
view
and
delete
the
configurations
on
the
base
of
the
ID,
so
I
fixed
that
and
now
the
user
can
view
the
view
and
delete
the
configuration.
I
call
pattern,
design
and
whatsoever
like
application
filters
on
the
base
of
the
ID
that
we
provide
them.
That's
a
small
update
from
my
head
foreign.
D
B
B
A
D
Then
we
we
probably
need
to-
we
probably
do
need
to
follow
up
on
this,
then,
because
the
ux
needs
I
think
we
talked
last
time.
We
brought
this
up.
The
ux
needs
to
be
consistent
with
Mastery,
CTL,
perf
and
perf
profile,
because
you
can,
the
user
can
search
for
specific
performance
profiles.
They
can
enter
it
by
name
or
ID
and
then
they
can
get
performance
test
results
based
on
that
and
there's
a
particular
style.
That's
style
of
user
experience.
D
B
A
A
A
A
D
It's
possible
we're
here
by
the
way
as
root
Raj
works.
It
looks
over
this
and
shares
I'll
just
share
some
context
for
everyone.
There's
an
emergent
Mastery
catalog
that
we've
spoken
about
a
number
of
times
on
this
call
it's
at
meshery.io,
catalog
and
well.
There's
a
number
of
yeah
so
anyway,
we're
hoping
that
that
catalog
is
full
of
content,
that's
useful
to
people
and
helps
them
get
value
from
the
project
out
of
the
box.
D
We're
also
hopeful
that
it
serves
as
a
venue
for
anyone
to
share
their
content
content,
meaning
like
a
well
an
infrastructure
design
like
a
kubernetes
configuration
a
service
mesh
deployment,
an
application
deployment.
Maybe
someone
has
imported
a
Helm
chart
and
they've
modified
it.
They
want
to
export
and
share
that
that's
another
example,
so
it
could
just
be
an
app
a
sample
app
and
so
as
people
as
users
go
to
create
that
content,
create
those
designs
or
create
a
web
assembly
filter.
D
A
E
D
It's
it's
probably
worth
looking
at
it
for
a
moment
just
to
ensure
that
everybody
is
on
the
same
page.
Also
to
let
people
know
that
you
know
one
of
the
things
that
root
Raj
is
giving
thought
to
is
like.
So
this
is
just
an
instance
of
Mastery
that
I'm
that
I'm
sharing
with
with
you
all
he's
giving
thought
to.
D
How
do
we
help
them
sort
of
forego
that
step
and
just
make
those
public
designs
readily
available
here
that
that's
kind
of
his
current
I
think
challenge,
but
he's
also
looking
at
it
from
I
think
I
have
an
old
session
yeah
or
I'm,
not
oops
I'm,
not
even
running
my
server
so
but
the
other
challenge
is
to
look
at
it
from
the
other
perspective.
So
if
someone
has
been
using
meshery
they've
been
working
on
creating
an
application
or
a
design
if
they
want
to
share
it
with
the
world.
D
What
mechanism
can
they
use
to
do
that
today?
That
looks
like
that
they
can.
They
can
download
it
from
measury
and
go
over
and
share
it
in
the
catalog
root.
Raj
is
giving
consideration
to
making
that
a
little
easier
with
like
a
click
of
the
button
so
anyway,
if,
if
any
of
that
topic
interests,
you
you
know
root
Raj
is
someone
to
go,
have
a
chat
with
he's
actively
soliciting
help,
as
you
can
see
so.
A
D
E
So,
as
we
can
see,
only
couple
of
them
are
only
two
of
them
are
currently
showing
the
version
that
is
this
and
recognize
the
other
ones
are
not
showing
so
why
this
is
because
there
can.
There
is
an
API,
slash,
API
system,
slash
adapters,
which
returns
this
information,
which
was
stored
in
the
message
which
shows
when
taken
from
each
other,
was
stored
in
in
machine
server,
and
then
it's
returned
back
to
the
UI
through
this
we
wanting
to
this
API
now.
E
The
problem
is
that
that
information
is
itself
not
sent
by
the
adapters
through
the
grpc
messages
which
we
do
between
the
doctor
and
the
Mystery
server.
Now
what
the
problem
is
it's
in
the
workflow
like.
Let
me
first
tell
you
what
happens
so
whenever
we
are
building
any
of
the
adapters,
so
we
are
using
this
new
workflow
that
is
multi-platform.
What
it
does
is
that
it
uses
our
Docker
file,
which
is
this
and
builds.
E
The
platform,
builds
the
each
of
the
adapter
and
what
it
requires
is
this
version
and
commit
Shah
as
an
argument,
and
then
it
uses
that
to
update
the
value
in
the
member
profile
over
here
and
then
it
will
send
to
the
mystery
server.
So
this
update
is
not
happening
because
these
arguments
are
not
passed
in
this
workflow,
which
is
over
here,
like
as
you
can
see,
the
argument
which
we
are
passing.
E
It
script
version
good
version
and
release
panel
when
actually,
but
in
reality
we
require
version
and
grid
comments,
and
since
we
are
not
passing
it,
so
it's
not
getting
updated
and
hence
we're
seeing
that
problem.
So
I'll
just
update
this.
It
just
require
a
little
bit
of
tweaking
in
this
each
of
this
workflow
for
each
of
the
adapter.
So
once
we
do
that
over
here
and
then
start
working,
this
is
the
first
issue
which
I
wanted
to
tell
like
I.
E
We
can
also
see
like
we
can
see
the
same
thing
over
here
that
the
version
is
not
being
sent.
So
that
is
the
first
thing.
The
second
thing
which
I
discovered
that
like,
even
though
we
are
able
to
see
the
version
of
this
application
traffic
match,
but
this
is
incorrect,
because
if
you
see
the
latest
version
of
traffic
mesh,
it
is
0.6.1,
but
we
are
seeing
something
else
like
0.5,
which
is
not
great.
It's
basically
due
to
that
work.
Only
so
once
you
update
that,
then
it
will
be
fixed.
E
The
third
thing
which
I
wanted
to
discuss,
which
I
discovered
while
working
on
this
was
the
console
adapter
is
not
working.
It
is
because
its
container
is
not
starting,
and
that
is
because
it
image
was
not
built
properly
and
that
that
was
because
this
Docker
file
is
incorrect
because,
like
this
Docker
pie
is
quite
outdated.
As
it
hasn't
got
any
updates
for
the
past
few
months,
so
we
basically
need
to
update
it
with
the
other
other
profile
which
we
are
using
across
other
adapters.
E
E
Actually,
they
are
not
importing
a
package
and
because
of
that,
it's
failing.
We
need
to
update
this
article.
So
actually
there
were
a
couple
of
things,
so
I'll
just
update
one
by
one.
The
first
thing
I'll
do
is
just
fix
that
that
workflow
for
all
their
actors-
and
then
we
can
tackle
each
of
these.
So
any
feedback
on
this.
A
Yeah,
so
I
I
was
also
having
this
issue
with
the
console
adapter
in
my
Docker
extensions,
maybe
because
I
was
using
a
previous
image,
but
when
I
was
on
call
with
Lee
and
he
pulled
the
latest
image
for
Docker
extension
and
I,
think
it
pulled
latest
everything
and
at
that
time,
to
the
console
adapter
work
so
like
is,
is
the
it
is
breaking
for
a
specific
version
or
after
some
particular
version
for
everything
for
every
other
version.
It's
breaking.
E
D
Well,
just
a
quick
clarification
of
what
you'd
said
about
the
adapter
versions,
not
displaying
the
core.
Well
you're,
not
displaying
the
correct
version
in
measure.
Ui
you'd
point
it
to
a
workflow.
You
know
an
update
needed
in
the
workflow
is
that
that
build
number
or
that
release
number
is
baked
in.
Is
it
that
we're
not
baking
that
into
the
build
Arguments
for
yeah
yeah?
We.
E
D
There's
also
this
we're
probably
if
Divine
yeah
Divine
is
here,
so
we
might
I'll
he's
going
to
talk
about
compatibility,
Matrix,
I,
think
and
there's
some
interesting
things
to
note
about
the
adapters.
Specifically,
oh
I'll
wait
until
he
brings
up
that
topic,
but
pranava.
No,
no,
no
naysayers,
here
as
to
what
you
presented.
So
it
sounds
like
you're
on
the
right
path.
A
B
Okay,
so
yeah
next
is
mine,
so
basically
it's
a
suggestion
for
the
have
for
having
a
configuration
page,
because
it
is
not
following
the
project
standards.
We
have
that
whenever
we
press
any
tab,
we
have
a
page
here
and
but
for
we
have
no
page
for
a
configuration
so
yeah.
This
is
a
suggestion.
I
want
to
give
that
you
would
have
something
for
us
configuration
page,
so
yeah
I
want
to
suggest
this
and
Lee
avian
even
want
to
say
about
this.
D
B
Yeah
I
want
to
say
that
we
have
something
for
every
page
we
have.
We
have
something
for
configuration.
We
have
something
for
performance,
but
when
we
press
the
configuration
we
have
nothing
so
because
so
that
breaks
the
kind
of
consistency,
I
think
so
because
I
mean
we
should
have
and
for
a
tab.
Page
I
think
we
should
have
something
that
defines
the
actual
page
that
what
this
page
wants
to
say
what
configuration
means.
A
Yeah
I
think
that's
a
great
suggestion
by
the
way
to
the
some
items
to
be
displayed
on
the
configuration
itemically
at
least
what
is
configuration.
What
do
we
support?
We
can
provide
the
list
of.
We
can
provide
the
categories,
as
we
said,
like
applications
patterns
and
filters
are
very
brief
of
what
they
do
and
what
we
have,
and
some
I
mean
Edge
steps
or
short
links
to
that
I'm.
Going
to
this
individual
configuration
items
so.
D
Yeah
yeah,
one
of
the
things
that
pranav
had
recently
worked
on,
is
a
summary
of
well
it's
a
summary
of
account
of
different
elements.
Different
things,
that's
another!
That's
another
thought!
So
if
you
were
to
click
on
you'd
said
life
cycle
like
it
might
be
that
actually
there's
a
well
it
might
so
so
right
now
are,
do
you
have
all
the
adapters,
loaded
or
or
no
adapters
loaded.
D
Having
said
that,
we
might
want
to
look
at
oh
man,
yeah
I,
don't
know
I,
don't
know,
we've
gone
back
and
forth
on
this
a
little
bit
like
like
one
nice
thing,
there's
an
open
issue,
there's
a
feature
request
that
was
opened
this
week.
It's
part
of
the
docker
hacktoberfest
on
the
meshery
extension,
which
is
to
allow
users
to
click
a
button
and
measure
UI
to
then
deploy
a
meshery
adapter,
and
in
this
case
so
her
on
his
machine
in
his
mesh
redeployment.
D
He
doesn't
have
any
adapters
deployed,
but
he
might
want
to,
and
he
can
click
on,
configure
settings
and
then
try
to
connect
to
an
adapter
if
he
has
deployed
one.
He
hasn't,
though,
so
he'd
have
to
leave
measure
UI,
go
somewhere
else
and
then
do
do
his
deployment
in
whatever
style
he
wants
to
do
it
yeah
our
that
might
be
that
open
recently,
open
feature
request
might
dovetail
into
what
you're
saying
here
about.
Oh,
you
know
just
getting
the
user
one
further
step
along
like
oh,
you
don't
have
any
adapters.
D
B
Think
if
I
don't
have
a
adapter
loaded,
so
it
should
say
something
like
that:
I
had
no
adapter
around
a
in
a
life
cycle,
page
itself,
it's
showing
in
the
if
I'm
here
it's
showing
the
adapter
is
not
available,
but
in
a
life
cycle
page,
it's
not
showing
it's
just
showing
the
configure
button
in
the
center
and
that's
looking
odd
to
me.
I
think
gesture
configuration
settings
be
in
a
center,
so
we
should
have
something
for
this.
E
So,
currently,
we
are
at
dot
6.9
for
mystery
and
4.7
meshie
version,
so
the
whole
machine
UI
is
being
refactored
using
some
set
of
new
principles
using
State
Management
Redux
have
a
state
management
tool
and
material
UI
as
well
as
react
17.
for
this
whole
machine.
Ui
reflection,
so
I
wanted
to
have
a
demo
of
the.
What
is
the
current
state
of
Machinery
UI,
but
I
am
getting
this
some
kind
of
capabilities
on
the
machine
wire
restricting
branch.
So
since
Yash
is
not
on
the
call,
I
grab
one
of
his
video
from
slack.
B
B
B
Then
most
of
the
components
are
done.
Work
working
on
some
other
company.
Other
things
we
need
to
work
on
is
the
connecting
the
life
life
cycle
to
the
back
end.
It's
it
is
static
right
now.
We
need
to
connect
it
to
the
server
for
to
show
different
different
page
for
everything
for
every
adapter
and
I've
also
made
graphql
graphical
subscriptions
for
adapters
for
all
the
configurations.
B
B
Show
the
filters
page
I've
also
made
the
profiles
page.
You
can't
see
you
can
see
all
the
data,
because
I
don't
have
the
server
running
right
now.
Sorry
for
that
and
the
performance
dashboard
page
I
have
also
asked
for
the
for
changes
for
Leonard
I.
Guess
not
that
active
right
now.
He
might.
He
might
come
back
again
for
that
and
all
the
okay
forms
issues
right
now
and
I've
also
made
the
settings
page
it
is
connected
to.
It
is
I
connected
the
whole.
B
We
made
the
whole
part
for
all
the
components,
but
if,
if
we
have
this
server
running,
we
can
we
would
be
able
to
show,
but
we
most
of
the
states,
the
global
States
like
the
a8s
configs
and
the
adapters
I.
We
have
not
made
them
as
of
now.
We
have
to
make
the
work
on
the
detox
part.
It's
it
needs
a
lot
of
work
as
of
now.
The
notification
center
also
needs
a
lot
of
work.
B
D
Wants
to
work
so
yeah
yeah.
So
yes,
there's
a
bunch
of
there's
a
number
of
people
who
should
to
garve
and
harshit
and
harkarat
and
pranav
and
there's
a
long
list
of
folks
who
contribute
here.
I,
wonder
if
they
might
be
digesting
at
the
moment.
I've
got
a
question
or
two:
the
did
we
end
up
getting.
We
have
something
of
a
theme.
An
mui
theme
in
this
branch
is
that
right,
yeah.
B
D
B
Excuse
me
so
18
years
we
can't
support
the
act
18.
because
right
now,
because
it's
not
mui
data
table
is
not
compatible
with
that
right
now
we
use
it
at
number
of
places.
We
can
shift
from
that
to
use
Simple
mui,
but
that
would
be
like
to
decrease
a
lot
of
work,
but
but
we
can
we,
it
is
compatible
with
react
17
right
now,
but
there
are
some
other
libraries
that
are
not
compatible
with
redacted.
B
D
E
E
So
yeah
yes,
demoed
the
machine
UI
refactoring
seven,
so
we
need
more
volunteers
on
this
particular
UI
refactoring
area.
So
if
you
are
into
react
or
wants
to
contribute
to
machine
UI,
so
this
is
a
very
good
item
to
contribute,
and
this
will
help
also
help
you
to
understand
machine
UI
code
base
more
efficiently.
E
A
C
B
B
Compatibility
Matrix
to
be
more
easier
for
disaster
access,
so
this
is
what
the
whole
hold
on
was
like.
So
the
composition,
Matrix
had
some
platform
and
different
versions
listed
out
and
there
were
lots
of
spaces
beside
them.
So
we
moved
out
the
main
compartment
this
Matrix
and
we
have
access
to
take
out
these
versions.
D
Yeah,
do
people
have
feedback
that
there's
a
link
to
the
current
compatibility
Matrix
inside
of
Mastery
docs
in
the
zoom
chat?
So
you
can,
you
can
see
the
compatibility
Matrix
that
we
have
today
is
a
bit
split
across
two
pages,
the
the
two
pages
that
there's
one
page
called
compatibility
Matrix
and
you
can
see
the
resemblance
of
the
current
implementation
to
what
divine
was
just
showing
part
of
what
he's.
D
Well,
what
he's
trying
to
do
is
distill
a
lot
of
details
into
a
high
level
summary
like
this,
but
acknowledge
that
it
isn't
just
kubernetes
compatibility
that
is
being
tracked
or
tested
and
and
it's
a
little
yeah.
It
certainly
is
a
matrix.
It's
a
matrix
of
Matrix
says
matrices
if
you
really
get
into
it,
which
has
to
deal
with
the
fact
that
Mastery
has
a
stable
release,
Channel
an
edge
release
Channel,
which
I
don't
know
if
these
are
working
at
okay,
they're,
kinda,
I,
guess
they
are
working.
D
There's
an
open
issue
about
this.
We
also
it
would
be
great
if
this
was
sortable
too
we're
missing
the
console
item.
There's
a
few
there's
a
number
of
things
that
contributors
can
jump
into
and
assist
on,
and
that's
actually
what
divine
is
calling
out
is:
there's
a
design.
That's
going
to
take
this
page
and
the
contents
of
this
page
there's
a
supported
platforms
page.
So
this
supported
platforms
and
the
compatibility
Matrix
of
the
design
that
Divine
has
just
shown.
D
B
B
It's
so,
basically,
honestly,
it's
basically
a
coloring
Workshop
where,
where
the
colors
of
these
I
will
just
we'll
discuss
the
colors
of
these
components
and
after
discussing
the
components
we
have
to
just
fill
it
in
all
the
other
pages,
so
yeah
and
it
will
be-
will
then
complete.
This
Dark
theme,
so
yeah
I
have
to
decide
the
colors
and
of
the
each
component
how
we
will
switch
it
I'm
planning
to
switch
it
with
the
global
Styles.
B
You
have
to
think
about
that
yeah
Mei
team.
That's
what
we
are
going
to
use.
If
we
don't
have
a
mui
theme
for
each
and
every
component.
We
cannot
proceed
forward
and
select
a
theme
on
the
just
a
base
of
the
switcher,
so
yeah.
We
should
have
to
implement
the
mui
theme
first
in
our
project.
If
it
is
not
there.
A
B
Okay,
so
here's
a
layer,
five,
so
here's
a
basically
switcher
in
which
we
can
switch
yeah,
sorry
switch
on
the
click
and
we
are
using
the
mui
theme
Here.
We
have
decided
the
colors
over
each
component
in
our
single
repository
style
load.
Yes,
and
we
are
fetching
each
color
from
here
and
that's
what
I
think
we
should
also
Implement
here
to
give
fetch
of
each
colors
from
a
single
page
that
will
be
complicated.
B
A
Yeah,
okay,
by
the
way
harshit
will
be
breaking
this
big
task
into
smaller
itemized
Milestones
so
that
anyone
working
on
it
will,
you
know,
get
through
those
smaller,
smaller
Milestone.
To
achieve
that
bigger
feature
request-
and
he
may
put
some
initial
work
to
you
know
kick
start
the
journey
towards
the
aim
of
having
a
dark
theme
in
the
message.
A
E
B
B
If
you
are
defining
the
each
color
from
the
for
each
component,
I
think
this
is
not
should
be
done
in
project
I
was
in
our
general
project
also,
and
we
have
to
implement
the
single
style
sheet
for
a
dark
theme.
Also
so
yeah
I
mean
I
will
kick
start.
This
journey
I
will
need
a
volunteers
for
that
and
then
we
will
proceed
further.
B
A
A
E
D
A
Yeah,
so
so
this
was
about
adding
e2b
testing
machine,
so
we
have
a
core
workflow
which
runs
across,
which
is
a
callable
workflow,
which
runs
across
all
the
adapters.
The
results
from
which
are
then
sourced
for
the
compatibility
Matrix
that
you
just
saw
so
I
won't
go
over
the
compatibility
Matrix
because
we
just
discussed
about
it.
So
I
made
some
changes
in
that
core
workflow.
A
So
a
while
back,
we
had
a
discussion
about
the
utility
of
this
kind
of
test
is
that
we
can
right
now.
I
have
added
so
Horus
has
had
just
has
just
commented
about.
Why
have
we
have?
Why
have
I
added
a
new
Emoji
dot
yaml
here,
instead
of
sourcing
it
from
one
single
Source?
Actually,
the
idea
is
to
have
those
things
sourced
from
one
single
Source,
the
same
source.
A
That
would
be
the
news
for
measuring
catalog
as
well,
and
the
idea
here
is
that
not
only
the
single
Source
would
be
used
to
Source
those
things
into
catalog,
but
the
test
results
of
here
as
you
can
see
that
that
design
successfully
passed
for
all
the
from
communities,
versions
from
20,
21,
22
and
23
I
just
need
to
add
24
and
25
as
well
but
anyway.
So
these
test
results
can
then
be
also
sent
back
to
the
catalog
so
that
we're
on
the
catalog.
A
Those
things
can
be
so
if
you
have
posted
that
thing
in
a
public
place
in
design,
those
things
can
be
caught
by
our
running
tests,
which
can
run
which
actually
run
on
a
nightly
basis
and
also
on
a
bullet
request
basis
on
a
bunch
of
a
bunch
of
things
trigger
those
tests.
So
these
so
yeah.
The
point
is
that
there
is
a
utility
to
these
tests
and
this
kind
of
we
can
move
forward
by
adding
more
test
in
adapter
assessment.
So
in
adapters
right
now
we
only
test
a
bunch
of
control
plane.
A
So
that,
like
let's
say
that
one
PR
makes
a
change
onto
so.
We
internally
delegate
requests
to
kubernetes
by
changing
few
Fields
here
and
there.
Let's
say
that
we
mess
up
and
we
add
some
label
or
maybe
we
did
something.
We
manipulated
the
field
in
a
way
that
might
break
something
so
that
can
be
caught
in
the
pull
request.
Only
so
that's
the
usage
of
it.
If
anyone
has
any
doubts
regarding
it,
I
can
go
answering
that
or
I
can
move
on
to
the.
A
A
So
while
we
go
on
to
having
these
public
facing
catalog
items
and
internet
is
going
to
be
using
design,
configurator
and
mesh
map
to
create
these
new
designs,
there
is
a
bunch
of
things
that
is
stopping
us
from
moving
to
a
completely
functional
design
which
you
can
deploy
and
you
with
which
you
can
be
more
comfortable
and
more.
Basically,
you
can
be
more
relax
that
this
is
going
to
deploy.
A
So
one
of
the
things
that
I've
been
pointing
out
for
a
while
is
which
is
the
fact
that
I
just
clicked
on
the
application
and
these
extra
things
got
added
for
no
reason,
and
this
actually
fails
the
deployment
in
a
lot
of
cases
because
a
lot
of
times
like
here
this
is,
let's
say:
I,
go
to
kubernetes
thing
and,
let's
say:
I'll:
go
and
open
a
service.
So
if
I
click
on
a
service,
it
automatically
says
allocate
load,
balancer
note
code
as
false.
A
Now
this
shouldn't
be
set
unless
you
and
until
you
are
using
a
load
balancer.
So
if
you
try
to
deploy,
things
will
fail.
Although
I
didn't
manually
check
or
uncheck
this
thing
so
yeah,
we
shouldn't
add
any
field
which
the
user
hasn't
touched
and
I
think
Avi
and
nitish
are
having
a
discussion
around
how
to
circumvent
this
thing.
If
you
guys
reach
to
a
conclusion,
then
just
just
the
the
core
idea
is
that
don't
touch
field
that
the
user
hasn't
does
also
I,
don't
think
we
should
add
the
faults
by
default.
A
If
user
hasn't
ticked
it,
so
we
kind
of
need
I,
don't
know
if
we
would
need
to
to
I,
don't
know
how
the
ux
should
be
here,
whether
we
need
two
different
kind
of
States
here.
One
is
the
true
State
and
one
is
the
fall
State
and
one
is
the
user
doesn't
want
to
touch
its
state
I'm,
not
good
at
QX?
So
if
anyone.
B
E
A
A
A
Get
added
like
if
I
click
on
IEP
families,
the
null
got
added,
I
didn't
like
or
I
I
mean
technically,
yes,
this
form
got
open,
but
unless
and
until
I
click
on
this
and
I
manually
do
this.
This
shouldn't
be
filled
automatically.
So
there
is
a
bunch
of
things
regarding
this
which
make
the
make
things
a
little
dysfunctional.
If,
if
you,
if
a,
if
someone
is
not
a
power
user,
basically
they
might
turn
into
these
ux
problems.
A
That's
the
first
problem
and
I
think
this
is
a
noted
Problem
by
Avi,
and
he
has
he
has
been
working
on
it.
The
second
problem
is
that
I
still
don't
have
a
way
to
specify
name
and
name
space
on
from
the
left
side.
I
still
have
to
go
back
to
the
yam
and
the
channel
repeats
the
purpose.
So
just
like
we
have
on
mesh
map
name
and
namespace.
We
can
just
add
it
over
the
settings
field
over
here,
I
mean
I.
A
Think
this
is
a
quick
thing,
but
I've
been
saying
this
for
like
a
month
now
anyone
it
says
it
can
be
a
good
first
issue,
because
to
me
it
looks
pretty
straightforward.
Just
add
those
things
and
I:
don't
know
how
complicated
things
are
at
the
front
end,
but
anyways
that's
the
thing
and
also
while
you
are
adding
name
and
namespace
there.
A
We
also
need
labels
and
annotations
because,
like
say
that
I
would
want
to
deploy
a
service
and
instead
of
Select
Drive,
pass
some
labels
and
now,
if
I
want
to
deploy
a
pod
with
those
labels,
I
cannot
because
I
don't
see
the
labels
and
annotations
field
here
so
name
name,
space
labels
and
annotations.
Those
four
Fields
should
be
present
on
top
of
each
workload
that
we
have
here.
These
are
the
two
and
once
we
have
these
two
things
plus
the
initial
thing
that
I've
talked
about
that.
A
Don't
include
a
field
which
the
user
hasn't
touched,
I
think
I.
Think
I'm,
like
I,
have
worked.
I
have
made
a
lot
of
designs
and
I
think
that
once
we
have
that,
I
can
be
more
confident
in
in
the
fact
that
this
design
won't
break
and
there
would
be
a
better
ux
and
there's
a
bunch
of
validation
errors
that
we
get
we'll
get
rid
of
those
and
so
on
and
so
forth.
So
that's
kind
of
some
feedback
for
UI
people
and
I
have
added
these
three
as
bullet
pointers
and
I.
A
A
D
Yeah,
no
just
Mario's
last
question
there
about
like
a
feature
request,
have
a
search
field
is
I
think
resonates
another
request
from
Ashish
to
like
try
to
parse
through.
What's
there
so
that's
yeah,
we
should
probably
open
up
an
issue
to
maybe
to
have
people
weigh
in
on
that
kind
of
kind
of
describe
how
it
might
work
and
things
yeah,
but
that's
it
then
other
than
that
yeah
there's.
So
we've
got
an
event
on
Friday
that
will
is
just
a
I'm
introduced.