►
From YouTube: Meshery Development Meeting (Jan 19th, 2022)
Description
Meshery Development Meeting - January 19th 2022
Agenda:
- Feedback on v0.6.0-rc-4 - Fixes working? Bugs found?
- Progress update: Refactoring Meshery UI in v0.7.0 (design proposal)
- Branch | Meshery v0.7.0 Implementation Tracker | Contributor’s Guide
- Refining GraphQL subscriptions in Meshery and changes to Meshsync
- progress bar component. #4830
- style changes to the navigator. #4926
- Configurator feature + style enhancements. #4954
- Added flag to control browser behaviour. #4959
- Fix capture and handle expired token in performance page. #4956
- Cypress e2e tests updates
- Search issue in Performance profiles. #4915
- Service Mesh Labs [Errors]
Join the community at https://layer5.io/community
Find Layer5 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/
A
Okay,
all
right
and
we're
live,
and
it's
time
to
start
the
meeting.
It's
the
19th
of
january
welcome
to
the
mystery
development
call.
We
have
this
call
once
a
week.
We
do
a
couple
of
things
every
week.
We
welcome
newcomers
if
we
have
any
looking
through
the
list,
there's
just
shy
of
20
of
you
and
you're
all
old
timers,
crotchety,
old-timers,
okay,
good
nice
to
see
everybody
back,
I
think
everyone
or
for
sure
everyone
has
introduced
before
everyone's
been
here
any
number
of
times.
So
that's
great!
A
A
Actually,
in
addition,
let
me
preempt
this
real
quick
before
we
talk
about
mesheri
v07,
the
upcoming
the
upcoming
release,
the
upcoming
version
to
work
on.
I
want
to
ask
all
those
on
the
call
now
about
the
current
version
of
meshary.
There
was
a
release
made
release
candidate
4
for
the
v060
version,
tons
of
things
packed
in
there
from
the
dot
5
release,
2.6
tons
of
things
so
plenty
of
opportunity
for
bugs
has.
I
know
I
got
a
chance
to
run
release
candidate
for
has
anyone
else.
A
A
A
A
So
if
any
of
you
are
interested
in
so
we
talked
for
quite
a
bit
of
in
the
past
about
writing
up
the
feature
sets
either
small
blogs.
That
kind
of
describe
the
features
that
that
you've
worked
on
or
that
you're
aware
of,
even
if
you
didn't
work
on
them,
that's
fine
or
small
recordings
about
how
to
use
a
particular
thing,
or
maybe
just
a
small
recording
that
explains
the
behavior
behind
the
scenes.
A
So
certainly
recordings
of
like
of
use
of
mesh
free,
ctl
recordings
of
use
of
measure
ui,
those
are
all
very
helpful
to
people
understanding
how
the
system
works.
What
the
new
features
do
so,
if,
if
anyone's
up
for
those
things,
there's
a
perpetual
call
for
that
and
there
was
a
whole
set
of
organized
issues
and
blog
posts
to
be
written
for
dot.
Six.
Some
of
those
have
been
written
already.
A
And
I
know
that
that
doesn't
always
isn't
always
exciting
work
for
some
or
people
just
don't
know
where
to
start
or
how
to
do
it,
and
so,
but
for
my
part,
I'll
fill
in
the
blanks
where
we
have
blanks
but
yeah.
But
if
you
want
to
write
anything
about
dot
six
record,
something
about
that
six,
let's
do
it
or
do
it
and
we'll
get
it
posted
we'll
include
it
as
part
of
the
release
announcement.
So.
B
B
Okay,
so
we
are
about
to
bring
in
some
huge
architectural
changes
to
measure
ui
in
terms
of
mostly
like
these
changes
would
not
be
you
know,
user
facing
in
the
sensor.
They
wouldn't
be
able
to
see
those
things,
but
these
actually
impact
the
way
our
our
ui
is
going
to.
You
know,
work
and
function
so
yep,
so
some
of
the
things
that
we're
actually
introducing
are
you
can
actually
look
at
this
proposal
to
understand
like
what
things
are.
Why
are
we
doing
this
and
what
are
the?
B
What's
the
reason
behind
all
this
stuff
and
an
explanation
about
why
we
chose
certain
things,
so
all
those
stuff
can
be
found
here.
The
link
is
also
there
in
the
meeting
minutes
so
yeah
so
like
as
a
part
of
that
we
will
be
introducing
redux,
observables
and
a
bunch
of
other
stuff
as
well,
which
which
actually
would
impact
my
http
in
a
positive
way,
and
we
are
we
are
also
going
to
achieve.
I
mean
yeah
change
a
little
bit
of
designs
in
the
ui
as
well,
and
that
would
be
for
p0.7.
B
Next
year's,
mostly
so,
if
you
want
to
get
familiar
with
it
or
you
know,
work
on
that,
then
it's
probably
a
great
place
to
start
out
and
you
can
actually
look
at
the
links
are
provided
over
here.
So
I
don't
have
to
explain
all
these
things
like
yeah,
you
can
go
to
the
contributors
guide
and
there
would
actually
be
a
detailed
explanation
as
to
how
you
can
start
out
and
how
you
can
start
contributing.
B
So
yeah,
that's
the
first
topic
and
yep
just
jump
in
and
start
contributing
to
it.
It's
it's
going
to
be
exciting
because,
like
yeah,
there
are
a
lot
of
new
things
happening,
so
you
should
be
excited
all
right.
So
the
next
thing
is
okay.
We
have
been
having
some
problems
with
the
with
the
way
we
have.
B
But
then
the
way
we
are
implementing
subscriptions
right
now,
those
are
not
how
we
are
implementing
it
in
the
sense
that
they,
whenever
you,
you
actually
listen
to
any
of
the
changes
in
the
database
and
then
like
you,
actually
hold
the
database
and
then
send
it
over
to
measure
ui
or
any
other
client
for
that
matter.
So
this
this
is
something
that
we
have
to
fix
soon
and
yeah
yeah.
This
is
actually
one
of
the
many
problems
that
I
wouldn't
say
like
the
problems
that
I'm
talking
about
this.
B
Those
are
not
you
know
very
evident,
and
people
who
are
using
the
ui
or
measuring
server
would
not
be
able
to
recognize
this
because,
like
it's
yeah,
it's
it's
not
that
evident
so,
but
it
is
actually
impacting
in
a
negative
way
a
little
bit
here
and
over.
So
still,
those
things
have
to
be
taken
care
of.
B
So
as
a
so
that's
a
step.
I've
taken
a
step
towards
that
by
changing
some
things
and
how
much
sync
actually
works.
So
if
you
don't
know
what
my
sync
is,
it's
it's
kind
of
like
the
it
is
responsible
for
syncing
the
cluster
state
and
sending
out
to
measuring
components.
So
basically,
that's
over
it
in
a
simple
way.
So
its
job
is
to
send
the
events
like
whenever
some.
Whenever
something
in
the
cluster
changes,
it
will
actually
send
events
to
the
all
the
other
components.
B
Basically,
it
would
publish
those
events
to
the
not
subscribe.
I
mean
that's
not
just
basically
a
pops
up
messaging
component,
so
it
would
actually
send
send
that
over
to
an
ad
something
like
mystery,
ui
or
messaging,
whatever
the
client
is,
they
can
actually
use
that
and
do
whatever
they
want
to
do
with
it
so
yeah.
So
right
now,
like
the
some
of
the
changes
that
I've
made,
I
would
like
to
demo
those
right
now
and
see
if
see
where
we
can
take
it
from
here.
B
Okay,
I'll
just
explain,
what's
the
setup
that
I
have
here
so
I've
just
started
so
this
this
measuring
server.
It's
actually
I've
made
some
changes
to
it.
So
this
is
not
the
one
that
you
would
find
in
the
master
right
now,
and
this
is
amazing
that
I've
run
locally,
and
this
is
I've
made
some
changes
to
this
as
well
so
yep
and
I
have
a
nat
server
running
locally
so
that
like
missing,
could
publish
to
it
and
then
mystery
server
could
subscribe
to
it
and
receive
the
updates.
B
So
basically,
like
the
some
of
the,
I
will
just
talk
about
the
changes
that
I
have
made
right
now
and
how
it
impacts
mesheri.
So
one
thing
you
could
notice
is
that
so
after
it
starts
like
you,
can
see
these
three
messages
over
here.
So
these
are
the
basically
the
changes
that
I've
made.
One
is
that
first,
so
I
would
before
that.
B
In
the
sense,
it
would
actually
ask
all
the
informers
that
they
have
to
you
know,
set
up
watch
connections
with
the
cube,
kubernetes
api
and
then
like
get
the
events,
and
you
know
pass
it
pass
it
down
to
the
machinery
server.
So
right
now
like,
if
you
think
about
it,
like
messy
ui,
is
kind
of
controlling
the
behavior
of
memory
server.
B
Those
informers
have
a
store
within
them
and
those
stores
actually
capture
all
the
events
and
they
actually
kind
of
reflect
the
state
of
the
cluster.
So
instead
of
you
know
sending,
instead
of
whenever
a
page
refreshes,
you
ask
mesh
thing
to
resync
and
get
those
date
I
mean
subscribe
to,
I
mean
dispose
all
the
connections
that
it
has
and
then,
like
re-establish
those
connections.
B
You
can
just
use
this
to
ask
it
to
send
the
data
that
is
in
the
store
instead
of
resyncing,
and
even
this
can
only
be
done
whenever
measuring
server
is
initializing.
So
basically,
that's
what
I've
done
now.
So,
whenever
right
now
measures
over
initializes,
it
would
actually
dispose
the
data
that
missing
objects
that
it
has
in
the
database
right
now
and
then
it
would
subscribe
to
the
store,
updates
and
messaging
so
basically
like
after
the
subscript.
B
After
that,
it
would
actually
ask
me,
I
mean
the
yeah,
my
sync,
to
send
the
data
in
the
store
and
then
it
would
get
that
data
and
store
it
in
the
database.
So
this
is
a
one
thing
like
that's.
That's
changed
right
now
that
is
like,
so
how
it
would
impact
is
that
yeah,
it
would
actually
reduce
a
lot
of
those
network
calls
between
kubernetes
ap,
although,
like,
although
you
might
think
that
it's
not
actually
a
huge
deal
but
then
yeah
still
we
can,
we
can
reduce
it.
B
So
it's
actually
good
and
yeah.
The
other
thing
is
that,
right
now
we
actually
have
the
ability
to
because
of
the
changes
that
has
been
made
into
a
machine
kind
of
server.
We
now
have
the
ability
to
create
subscriptions
that
send
just
deltas
rather
than
you
know,
fetching
the
whole
database
and
then
sending
stuff.
So,
to
give
you
an
example,
let's
say
I
I
open
the
ui
right
now.
A
It
actually
doesn't
take
too
large
of
an
environment
for
those
repetitive
messages
that
are
being
sent
from
mesh
sync,
to
start
to
have
a
performance
impact
not
only
on
mesheriy
itself,
but
on
cube
api
kubernetes
as
well
like.
We
want
to
be
a
good,
a
good
citizen
in
terms
of
managing
the
environment
and
not
what
is
what
is
the
oath?
A
Oh
geez,
I
forget
the
oath,
I
don't
know
if
it's
like
do
you
know,
I
don't
know.
Don't
anyway,
we
don't
want
to
harm
the
things
that
we're
managing,
and
so
we
want
to
be
efficient.
The
other
thing
that
is
part
and
parcel
to
this
enhancement
is
that
there
are
other
behaviors
that
manifest
as
part
of
receiving
updates,
repetitive
updates
about
the
same
objects
over
and
over
and
over
again,
it's
unnecessary
and
can
be
confusing
to
different
aspects
of
the
system.
A
A
So
yeah,
that's
part
of
what
nitish
is
talking
about.
I
think
he's
if
I
got
it
right,
he's
also
alluding
to
the
efficiency
by
which,
so
I
think,
we've
been
using
some
graphql
subscriptions.
We've
been
using
some
graphql
fetches
desire
to
be
using
subscriptions
largely
using
subscriptions
in
most
places.
A
D
B
B
So
we
can
see
that,
like
these
deltas
are
getting
added
to
the
so
basically
like
this
is
rather
than
querying
the
database
and
sending
the
data
over.
We
now
have
this.
You
know.
Delta
is
basically
like
whether
it's
an
ad
event
or
a
delete
event.
So
because
we
have
some
seo
installed
like
it
would
actually
add
some
other
stuff
as
well,
while
creating
the
name
space.
So
that's
why
we
are
seeing
a
bunch
of
other
stuff
as
well,
but
yep.
B
So
this
is
basically
the
stuff
that
I
wanted
to
show
and
from
here
like
so
we
can
actually,
we
should
actually
think
about
not.
We
should
actually
work
on
changing
the
subscriptions
that
we
have
right
now
which
are
not
based
on
delta's.
Two,
you
know
same
delta
rather
than
fetching
the
queries,
and
there
are
a
bunch
of
subscriptions
where
we
are
doing
that
as
well.
So
probably
the
next
step
would
be
to
change
those
subscriptions
as
well
and.
A
B
So
actually
like
yeah,
one
more
thing
that
I
wanted
to
talk
about,
and
I
missed
out
was
so
right
now,
like
one
more
change.
That's
made
is
that
this
does
impact
like
what
are
the
changes
that
we
have
to
make
to
our
graphical
subscriptions
that
we
currently
have,
and
the
thing
is
that
so
essentially
like
the
architecture
that
we
are
going
to
follow
right
now
I
mean
like
that
is
being
implemented
right
now
by
the
changes
that
I've
made.
It
actually
ensures
that
so
a
message
server
has
a
component.
B
It
actually
establishes
a
connection
with
the
broker
whenever
it
initializes
and
that
particular
connection
is
unique
to
it,
so
that
that
that's
connection,
that's
the
connection
where
we
can
actually
attribute
that
particular
connection
to
measuring
server
and
when
a
subscription
like
right
now
as
it
is
implemented,
you
can
think
of
it.
As
a
okay,
like
let's
say
we
have
a
subscription
and
measure
ui
as
a
client,
and
let's
call
that
subscription,
listen
to
mesync
events
and
that's
what
it's
called
right
now.
B
So
basically,
what
the
logic
of
the
subscription
subscription
would
do
is
that
so,
whenever
a
client
is
connected,
it
would
actually
establish
a
new
connection
to
the
you
know,
not
subject
where
my
sync
would
actually
send
those
events
and
then
it
would
directly
proxy.
It
would
act
as
a
proxy
and
send
those
event
directly
to
the
client.
So
that
is
how
yeah.
So
that's,
actually
the
current
architecture
that's
being
implemented
right
now.
B
A
B
So
yep,
and
also
like
one
more
thing
that
it
would
so
previously
like.
If
you
had
noticed,
you
would
see
that
sometimes
in
a
database
objects
that
are
not
there
in
the
cluster
would
actually
show
up
would
still
be
there
and
the
this
would
actually
address
that
as
well.
That
is
like
you
wouldn't
have
like
whenever
you
start
measuring
server
the
or
data
that's
in
the
database.
It's
it's!
It's
a
complete
reflection
of.
B
What's
in
the
cluster
yeah,
it
ensures
that
so
the
way
we
are
able
to
achieve
it
is
that
in
the
informals
like
we
have
stores
and
stores
provide
us
the
guarantee
that
eventually
it
would
be
consistent
with
what
the
state,
what
is
the
state
of
the
cluster
so
essentially
like?
Because
since
we
are
just
taking
the
data
in
the
state
and
storing
it
to
measuring
server,
then
we
can
also
say
that
have
that
guarantee
saying
that
okay,
this
would
actually
reflect
the
state
of
cluster.
Eventually.
A
E
A
A
And
so
the
connectivity,
wizard
or
the
connection
wizard
isn't
is
something
that
will
be
refactored,
something
that
was
released
kind
of
in
dot.
Six
had
some
trouble,
we
pulled
it
back,
but
the
point
of
that
wizard
is
just
to
help.
People
get
be
successful,
deploying
measuring
so
that's
where
a
stepper
like
that
they
would
be
stepping
them
through
getting
meshers,
set
up
and
connected
to
their
infrastructure
and
josh
you're,
saying
so
you're
working
on
a
refactoring
of
the
navigation
component,
and
so
within
these
screenshots.
A
A
Yeah
yeah
there's
one
thing
that
was
well
then
I
don't
I
don't
want
to.
You
know
necessarily
call
out
man
of
as
having
done
incomplete
work,
but,
but
I
guess
I
just
did
mono-
did
a
great
job
of
that
transition
and
that
the
expansion
from
a
single
button
to
four
you
know
buttons
and
it
works
pretty
great,
like
all
of
it
works
really.
Well,
there's
one
there's
one
final
aspect,
and
it's
that
chevron,
that's
sitting.
A
You
know
like
conceptually
it's
supposed
to
be
sitting
about
halfway
across
the
line
of
the
navigation,
you
know,
pain
and
and
the
rest
of
the
main
screen
view
and
we're
slightly
off.
It's
actually.
Okay
and
the
thing
is,
is
like
we
use
chevrons
to
open
and
close
drawers
and
pains
and
things
none
of
them
other
than
this
one.
Had
we
tried
to
have
it
split
across
the
you
know
what
the
collapsible
entity
and
so
josh
for
my
part,
just
as
if
no
one
else
is
giving
feedback.
A
One
thing
that
I'd
love
to
see
is
actually
not
hovering
over.
You
know
halfway
over
the
line,
but
is
but
rather
like
not
actually,
maybe
not
actually
using
the
exact
same
chevron
having
a
little
bit
of
a
different
style
to
it.
Josh.
Let
me
can
I
share
this
with
you,
real,
quick
and
with
everyone
else.
Maybe
everyone
else
can
give
an
opinion.
So
if
you
go,
I
can't
see
the
zoom
start.
A
What
do
you
think
you
want?
Can
we
try
something
like
that?
It
seems
you
know
instead
of
hovering
on
the
center
and
actually,
in
this
case
see
you
see
the
chevron
here.
This
is
basically
the
same
exact
arrow
that
we're
using
today
and
it's
fine
that
we're
using
it
to
expand
and
collapse
different
panels.
G
Yep,
so
it's
visible
so
on
our
latest
release
that
we
have
on
mystery.
We
had
made
changes
to
some
of
the
enhancement
in
the
patent
configurator,
so
it's
a
good
job
to
make
announcement
in
every
release
that
we
have
so
in
the
current
this
pr.
I
have
added
some
of
the
features
to
the
pattern:
configurator
and
some
of
the
styling
announcements.
So
let's
first
look
at
some
of
the
visual
selling
announcement
that
you
can
see
over
here.
G
So
previously,
what
we
were
having
that
there
was
a
lot
of
space
white
space
wastage
that
we
were
seeing
in
this
pattern
configurator.
So
I
removed
that
thing
and
made
it
a
bit
clear
and
next
thing
you
might
have
noticed
that
this
was
also
getting
like
spaced
out
and
also
I
also
had
refined
it
a
bit
with
some
stylings
next
is.
It
is
covering
two
issues.
The
second
one
is
still
in
progress.
G
The
first
one
is
setting
integer
as
a
num
with
the
first
one
is
sitting
in
decision
with
a
range
of
0
to
10
having
in
this.
So
we
can
set
the
range
over
here
and
I
guess
it
should
update
over
here
yep.
It
is
updating,
plus
that
was
all,
and
in
the
second
issue
I
have
a
query.
Let
me
also
ask
so
could
you
just
brief
me
with
this
issue
once
more?
A
G
A
You
know,
replicas
to
being
the
the
up
down
arrows,
the
other
one
which
is
great,
which
is
nice
to
have
some
diversity.
One
thing
on
there:
garv
is
a
I
don't
know.
Maybe
this
is
taking
it
too
far,
but
probably
the
numbers
that
people
are
gonna
put
in.
They
probably
wouldn't
go
past
a
thousand
like
those
three
three
places.
So
if
we
reduce
that
width,
maybe
that
sort
of
throws
off
the
symmetry
of
what's
being
presented,
and
so
maybe
that's
not
a
good
suggestion.
I
don't
know.
D
A
But
something
to
think
about
so
so
the
other
one
is
when
we're
trying
to
represent
configuration
of
different
service
mesh
components,
one
of
the
descriptors
for
an
input
value,
it's
called
additional
properties.
So
if
you
go
so
additional
properties,
the
type
of
input
field
that
it's
referred
to
is
called
string.
A
The
thing
is,
is
so,
I
think
to
date,
we've
been
mostly
there's
some
funky
business,
where
we've
been
doing
like
a
key
value
pair
of
like
having
people
identify
key
and
then
a
value
for
the
and
so
what's
desired.
Here
is
just
if,
if
we're
being
presented,
json
to
represent
as
input
and
if
that
element
is
if
it
matches
the
string
additional
properties
and
it's
of
type
string,
let's
go
ahead
and
display
it
as
a
single
just
just
a
regular
text.
Input
field.
G
B
There
is
a
a
key
called
additional
properties
in
the
schema
if
you
check
it
out
right
now.
What
happens
is
in
the
rjsf
form
in
the
pattern
configurator.
It
comes
as
a
new
key
key,
which
makes
no
sense
so
because
we
don't
have
any.
You
know
we
don't
have
an
exceptional
rule
for
the
additional
properties
field,
so
that
is
basically
what
you
have
to
do.
There
is
this:
there
is
I'll.
Send
I
send
the
docs
in
the
chat.
B
F
G
A
A
A
A
From
a
user
experience,
perspective
provide
comment,
probably
so
so
so
here
he
is,
there's
there's
a
user
that
has
an
expired
token
expired
session.
They
go
to
click
navigate
and
in
order
for
information
to
be
presented,
they
have
to
have
an
actual
session,
so
they
just
get
redirected
to
log
back
in
feels
pretty
natural.
A
I
think
there
was
a
design
given
in
terms
of
the
modal
which
should
be
kind
of
the
standard
modal
and
it's
slightly
off
slightly,
not
within
the
design
that
was
given,
but
has
anyone
looked
into
this
pull
request
and
understood
how
it
is
that
session
tokens
are
being
validated?
How
it
is
that
tokens
are
expired.
Sessions
are
being
redirected.
A
E
I
don't
think
there
is
any
code
needed
to
be
changed
in
the
server
because
we
can
just
if,
if
we
just
have
to
validate
the
user,
then
we
can
just
make
a
request
to
the
server
like
asking
for
the
user
information
like
we
do
when
we
are
showing
the
image
of
of
some
user
on
on
the
network.
So
if,
if
there
is
like
no
login
credentials,
then
it
will
automatically
push
400
500
and
we
will
just.
B
See
like
the
the
implementation
of
the
fetch,
our
custom,
you
know
apa
that
we
have
implemented
right
now.
We
can
actually
put
the
logic
inside
there
as
well.
That
is
like,
if
you
actually
receive
anything
from
arranging
500
5x6,
you
can
actually
it's
basically
because
it's
unauthorized
and
you
can
use
that
to
send
the
user
back
to
the
login
page.
E
Yeah
another
thing
just
to
just
one
more
consideration
is
like
we
want,
so
so
we
are
sending
cookies.
So
if
the
token
cookie
is
absent,
like
the
token
cookie
is
absent,
then
there
is
no
way
you
can
authorize
to
the
server.
So
we
can
just
check
the
cookie
if
token
cookie
is
present
in
like
here
and
inside
the
front
end
just
push
it
because,
because
those
token
cookies,
like
those
tokens
are,
I
think,
lasted
for
one
day.
A
Anybody
else
have
comments
on
that
yeah.
There's
a
single
point
of
enforcement
that
we
want
to
do
you
can
do
it
client
side
great.
There
is
middleware
in
each
of
the
rest.
Api
calls
the
golang
calls
that
could
also
perform
the
redirect
on
the
back
end
like
avi
was
saying
and
that
that
validation
of
whether
or
not
their
token
is
active
or
not
is
already
being
performed
so
that
it
could.
That
could
be
enhanced
to
also
redirect,
to
the
extent
that
the
ui
you
know
some
some
area
of
the
ui
wasn't
doing
it.
I
Yeah
so
recently
I
shared
with
team
that
I
was
a
bit.
There
was
some
something
blocking
the
progress.
I
was
some
integration
test,
failing
some
differences
between
github,
ci
and
local,
but
they're
solved.
It
was
just
a
matter
of
making
sure
that
the
server
was
not
running
during
running
the
integration
test
locally,
and
so
now
that
looks
fine
and
I'm
trying
to
get
the
latest
changes
to
rerun.
I
The
the
end-to-end
tests
finish
the
a
the
script
there's
there
might
be
some
differences
in
the
the
expected
payload
that
is
sent,
but
hopefully
not
now
it's
you
know
the
upload
for
the
pattern
can
proceed
and
so
I'll
share
updates.
As
soon
as
I
get
that
working,
I
don't
know
why,
but
I
keep
getting
issues
whenever
I
follow
the
the
contributing
git
flow.
A
Well,
yeah
yeah,
that's
actually
everybody.
I
bumped
my
head
on
that
on
occasion
as
well.
There
is
this
is
absolutely
worth
talking
about
for
a
moment,
because
everybody
is
this
yeah
there's
the
the
main
contributing
guide
and
you
might
have
seen
it
already,
but
it's
still
worth
highlighting,
is
there's
a
secondary
one.
That
kind
of
that's
fairly
generic,
it's
not
really
specific
to,
but
the
the
trick
here
problem
for
the
most
part
is
yeah.
It
would.
I
I
And
if
you
go
to
the
submitting
your
changes
and
like
it's
in
the
bottom,
and
so
I
follow
all
of
these
steps
literally,
I
look
at
them
and
then
can
you
go
down
like
the
part
where
it
says
submitting
your
changes.
So
even
though
I
rebased
the
master
a
like
the
one,
a
new
commit
rebates,
your
development
branch.
I
E
I
E
Probably
you
may
not
require
device,
just
just
do
git
pull
up
stream
master
a
while,
while
pres,
while
you
are
in
your
branch,
just
to
get
full
upstream
and
then
space
master
master.
So
all
the
upstream
changes
will
be
merged
to
your
branch
as
well
as
there
will
not
be
like
a
too
many
comments
will
be
added.
No,
it
won't
be.
It
won't
happen
like
that.
So
just
then
push
the
regular
push
will
work.
Then
uh-huh.
I
I
A
C
I
A
A
I
A
I
I
E
I
B
C
I
J
A
Following
one,
the
one
that
you
were,
that
read
me
that
you
were
pointing
to
like
to
either
include
like
get
fetch
to
maybe
include
a
more
clear
statement
on
like
when
you
would
need
to
continue
with
the
rest
of
the
steps.
If
okay
and
so
yeah,
I
think,
for
the
most
part
that
was
copied
from
a
different
git
flow
that
some
other
project
had
had
or
something.
A
I
A
E
Okay,
so
yeah,
I
figured
out
that
the
patent
search
table
uses
that
to
fall
back
that
if
the
search
is,
if
there
is
nothing
no
patterns
there,
the
default
thing
is
that
a
message
saying
that
sorry,
we
could
not
find
any
match,
but
for
the
performance
profile,
it's
a
new
page
with
create
performance
profile.
So
maybe
that
was
the
issue.
So
what
I
was
thinking
like
if
we
are
in
table
view,
we
need
to
create
different
error
message,
kind
of
thing
that
replicates
the
pattern
pattern
way
of.
E
C
J
E
Am
I
am
I
audible
hello?
You
are
now
yep
yeah
all
right,
so
I've
been
working
on
the
up.
Updating
the
labs
lab
seems
not
to
be
working
for
different
adapters,
so
the
current
image
id
the
category
provided
image
id
we
are
running.
Is
this
kubernetes
cluster
running
this?
Had
some
issues
like
I
have
discussed
here,
that
is
your
service
mesh
and
the
console
console
labs.
E
So
these
were
some
issues
where
we
were
running
in
the
current
kubernetes
cluster
id
now
I
was
trying
different
combination
of
the
ids
that
were
provided
by
kubernetes,
and
so
this
in
this
talk,
I've
discussed
all
the
errors
that
I
have
faced
and
I
just
wanted
to
like
everyone
to
elite
go
through
it
and
maybe
some
maybe
I
ran
a
wrong
code
or
missed
something
that
might
have
gone.
That.
A
Thank
you
jared,
so
aditya
yeah.
So
this
is
so
so
you
so
you're
trying
out
different
base
images
and
then
different
approaches
on
those
base
images.
The
problem
it
seems
with
this
particular
image
is
a
lack
of
permissions
to
be
able
to
mount
to
volume
and
that's
probably
not
something
we
can
circumvent.
That's
something
that
catacota
isn't
forcing.
A
Okay,
that's
that's
a
shame,
because
that
would
be
the
most
convenient.
There
would
be
a
pre-existing
kubernetes
cluster
to
interact
with
fine,
so
you're
trying
a
different
base
image
of
ubuntu
214.
It
doesn't
seem
to
have
enough
ram
to
or
not
as
much
ram
as
cube.
Adm
wants
it
to
have,
and
so
then
yeah.
E
D
E
A
E
E
So
I
did
it
with
the
fresh
install
that,
after
q,
a
cube
adm
in
it.
It
came
with
one
cluster
only
like
horse
01
cluster
and
I
didn't
know
how
to
add
another
one.
So
in
the
dock
it
said
that
we
cannot
create
pods
in
the
control
plane
cluster.
So
there
was
a
code
for
this
to
make
parts
in
the
control
pin
itself.
So
I'm
ran
this
code,
so
is
it
like
correct
or.
A
A
Yeah,
I
think
you're
gonna
run
it.
You
probably
run
to
the
same
issue
right
if
it's
got
only
two
gigs
of
ram
like
if
the
environment
is
basically
the
same
you're
gonna,
it
doesn't
really
matter
if
you
figure
that
out
so
good,
so
we're
a
little
bit
over
time,
a
number
of
people
are
having
a
drop
off
reach
did
you
have?
I
know
I
just
called
you
out
to
demo
this,
so
I
don't
know
that
you're
necessarily
ready.
It
might
be
a
good
one,
just
to
drop
into
on
the
chat
or
and
point.