►
From YouTube: Meshery Development Meeting (Sept 8th, 2021)
Description
Meshery Development Meeting - September 8th, 2021
Agenda:
- [Utkarsh/Bariq] Urgent performance test results bug (#4102).
- [Lee] Recap of Meshery v0.5.53
- [Sayantan/Debopriya] Send release announcement?
- [Meghana/Zain] Preparations for the Meshery v0.6.0 Release Announcement.
- [Nithish] Review of progress toward UI architecture overhaul with introduction of Redux.
- [Gaurav] Discussion - Centralizing MesheryPatternserviceform (adding patterns/filters/apps in configuration in code(separating out files) + PR discuss
- [Abhi] Talk out the future work aspects of Patterns and the work needed, etc
- [Tanuj] Preview of Meshery marketing video. CLI splash asset
- [Jared] RBAC and Kubernetes v1.22 support (#issue)
- [Rudraksh] GetNighthawk as a Meshery component (spec)
- [Piyush] Mesheryctl roadmap update.
- [Aditi] Review schedule for caching design spec.
- [Soham] Meshmap node actions.
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
A
Oh
wow,
some
bad
jokes
this
morning.
Okay,
all
right,
so
brief,
roll
call
brief
to
check
on
folks
that
are
on
the
call
if
you're
on
the
call.
Please
do
drop
your
name
in
into
the
meeting
minutes
nice
to
see
everyone.
I'm
gonna
do
a
quick
scan
of
those
that
are
on
the
call
and
look
for
any
unrecognized
names.
A
A
A
A
B
A
The
well
yeah
a
couple,
two
reasons:
smaller
code
base
like
smaller
set
of
concerns
in
measuring
ctl,
and
then
also
it's
really
nice-
that
each
of
the
commands,
like
they're
they're,
somewhat
procedural
in
nature,
the
way
that
they
execute
and
also
like,
there's
one
file
for
one
command
like
like
it's
constrained
like
the
you,
don't
have
to
wrap
your
head
around
too
many
things
to
be
able
to
absorb
it
and
make
a
contribution
so
yeah
kudos.
My
compliments
on
your
choice,
sir.
A
Oh
yes,
very
good.
By
the
way
not
I
mean
this
is
maybe
an
old
joke
for
some
people,
it's
not
really
a
joke.
It's
like
it's
nice
to
have
someone
from
uganda
on
bami
will
have
to
close
her
ears.
I
think
I
think
she's
from
nigeria
there's
just
so
many
nigerians
running
around
here.
It's
just
you
know
it's
nice
to
have
some
representation
from.
A
A
C
A
A
A
E
E
Actually,
there
was
a
bug
initially
where,
if
where
you
would,
if
you
would
try
to
retrieve
the
performance
results,
it
will
actually
show
you
an
error
that
bug
was
coming
from
coming
to
you
multiple
reasons.
Actually,
a
few
things
were
failing.
First
was
that
the
tokens
were
not
being
propagated
properly,
so
the
request
was
fading
and
that
the
request
was
not
being
pre-checked,
so
there
are
a
few
things
which
were
actually
paying.
This
has
been
fixed.
I
mean
api
has
been
raised
to
fix
this
particular
issue.
E
I
have
I've
linked
to
the
pr
in
meeting
minutes
yeah.
So
this
all
what
this
pr
does
is
basically
fixes
the
propagation
of
tokens
which
was
causing
the
request
to
fail.
The
request
was
provided
and
obviously
has
added
some
error
checks,
which
were
not
there,
which
was
actually
causing
the
panic
of
which
you
would
have
seen
in
the
logs.
That
was
dashed
in
the
vr
in
the
issue
so
yeah.
E
This
is
a
pretty
short
upgrade,
a
secondary
issue,
which
was
also
uncovered
due
to
this
particular
like
while
we
were
fixing.
This
was
that
refresh
tokens
were
basically
refreshing
of
tokens
was
not
quite
working,
and
that
has
also
been
rpi
has
been
raised
to
fix
that
that
particular
issue
also
so
now
we
should
be
long-lived
as
they
were
in
mystery
cloud,
so
yeah.
F
A
A
A
A
G
A
Yeah,
if
you
can
or
yeah
there's,
I'm
hoping
that
we'll
get
into
this
process
of,
even
in
an
automated
way,
beginning
to
send
out
just
minor
release,
announcements
that
are,
you
know,
fairly
wrote
in
nature
and
and
it'd
be
good
to
some.
Some,
I
think,
on
the
call
have
seen
the
last
couple
of
release
announcements
but
they're
still
being
hand
curated
and
so
yeah.
I
guess
my
question:
if
you
have
a
copy
of
that
template
or
if
you
have
a
copy
of
it,
does
anyone
have
a
copy
of
the
old
email?
A
G
So
I
think
this
was
the
basic
one
which
we
created
like
we
have.
We
have
this
template
now.
What
what
we
do
is
that
we
just
change
the
version
of
this
meshery
and
the
highlights
we
changed.
What
are
the
new
features?
We
are?
We
have
attached
with
the
new
release
and
then
we
jot
down
all
the
release,
notes
that
are
auto
generated,
like
I,
I
think
everyone
has
seen
about
this
general
maintenance
and
the
documentation
part.
G
So
we
just
attach
this
thing
and
then
we
attach
this
command
for
upgrading
the
machinery
deployment,
but
this
footer
and
this
header
is
always
there
so
yeah.
This
was
the
mail
template.
I
think
we
are
using
right
now
for
release
announcements
for
the
latest.
I
think
there
was
a
latest
announcement
for
the
I
think
yeah
this
one
so
for
eight,
I
think
yeah.
So
this
was
the
new
release
measures
version.
So
this
is
how
we
just
change
the
format
and
send
it
to
our
users.
A
Yeah,
thank
you,
yeah.
It's
a
poorly
phrased
question
on
my
part,
and
this
is
perfect,
if
you
don't
mind
just
for
open
reflection
for
everyone,
that's
on
the
call,
if
you
scroll
toward
the
bottom
about
halfway
through
there's,
there's
two
sections
that
are
or
three
sections
I
think
that
are
probably
common
and
static
common
and
that
we
can
automate
this
section
here,
release
notes.
A
A
A
A
A
Wow,
thank
you
much,
the
the
other
two
sections.
I
think
those
are
static
as
well
like.
I
think
that
we
can
that
that
what
we
have
here
is
a
little
more
helpful
than
what
you'll
commonly
get
from
other
projects.
Other
projects
they'll
send
out
our
release,
notes,
and
it's
just
you
know
it's
just
very
brief.
It's
just
a
lot
of
times,
they're
hand
curated.
It's
just
highlights
very
quickly.
A
A
A
A
A
A
A
F
F
A
As
we're
organizing,
this
sounds
like
we'll
have
in
the
announcement
there
will
be
a
number
of
new
features
to
explain,
and
some
of
the
features
are
quite
deep,
and
many
of
you
know
that,
because
many
of
you
created
these
and
so
either
in
a
collaborative
way
or
as
an
individual,
writing
up
a
description
of
that
feature
or
that
collection
of
features
a
lot
of
times.
You
know
for
any
given
significant
feature.
A
There's
often
things
to
talk
about
in
measuring
ctl
in
measuring
server.
I
can
measure
ui,
maybe
in
the
adapters,
maybe
in
mesh
sync,
maybe
in
the
operator
like
there's
a
lot
of
components
here
and
so
that
sort
of
a
cross-sectional
description
of
the
functionality
and
how
that
pert.
You
know
how
that
might
be
exposed
in
the
ui
or
in
the
ctl.
A
A
I
don't
think
we
have
a
link
to
the
final
announcement
for
the
last
release,
but
it's
a
good
reference
like
hey.
What
are
we
trying
to
achieve
here?
We're
trying
to
organize
the
upcoming
release
and
let
people
know
about
all
the
things
that
went
on.
One
of
those
that,
like
I
think
we're
going
to
have
a
re-release
of
in
some
respects,
is
the
nginx,
the
adapter
for
nginx,
but
but
so
here
was
last
last
releases.
D
A
A
H
H
H
A
A
A
A
All
right
so
on
the
topic
of
releasing
as
we
go
to
get
ready
to
do
this,
that
we
are
by
the
way
yeah
we're
in
need
of
well
hosting
a
couple
of
bug.
Smashing
sessions,
we're
in
need
of
making
sure
that
things
are
fairly
well
hardened,
that
we
can
confidently
point
people
to
the
release
and
suggest
that
they
upgrade
so
by
the
way.
This
document
here
talks
about
our
different
announcements
and
and
how
they
might
work
just
as
as
a
reference.
A
A
A
If
you
go
to
the
issues
area
for
the
mesherie
repo,
there's
a
collection
of
milestones-
and
so
you
know,
in
accordance
with
these
milestones,
we're
like
88
we're
almost
there
she's
got
168
items
closed
and
21
open,
so
part
of
the
release
management
would
be
like
hey.
Are
we
driving
driving
the
remainder
of
that
12
to
completion,
so
it
might
be
following
up
on
open
issues,
helping
connect
the
dots
between
someone,
who's
stuck
and
someone
who
can
help
that
activity
by
the
way
is
kind
of?
A
A
A
A
Do
something
else
or
whatever
happened,
but
following
up
and
and
checking
in
is
nice.
It
shows
that
we
care
about
the
work
that
they're
doing
that's
important
work
for
all
of
you
that
have
been
around
for
a
little.
While
does
this
it's
not
usually
doesn't
take
very
long.
Most
of
you
will
have
gotten
an
invite
to
join
the
github
organization
here
and
part
of
affiliating.
A
Your
username
to
the
organization
is
that
you
then
have
triage
permission
over
the
issues
and
so
any
any
one
of
you,
the
vast
majority
of
you,
are
able
to
come
in
and
we'll
drop
in
a
label
like
this
remind
issue
progress
check.
So
if
we
label
this
with
remind
momentarily,
there
should
be
a
bot
that
comes
around
and
says:
hey,
it's
been
a.
While
are
you?
A
So,
oh
there's,
probably
some
snark
in
there,
I'm
sure
no
okay,
thank
goodness,
but
feel
free
to
use
that
on
occasion
to
help
to
help
make
sure
that
folks
are
you
know
that
things
are
moving
along
a
lot
of
times.
People
newcomers
will
drop
in
and
they'll
say,
hey
I'd,
love
to
contribute,
but
I
don't
seem
to
find
any
open
issues.
It's
like
well,
there's
a
lot
out
there.
You
know,
and
that
just
happens
to
be
that
there
are
stale
assignments
sometimes
so
so.
Release
management
has
is
in
part
about
herding.
A
A
Also,
let's
get
some
names
filled
in
if
we
can
on
the
sections
for
those
that
are
interested
in
writing
it
up
and
then
probably
some
issues
created
to
track
that,
like
that,
would
be
part
of
the
release.
Manager's
job
potentially
create
the
issues
follow
up
help.
People
make
sure
that
the
draft
is
being
reviewed.
I
So
if
you
look
at
like
something
that,
like
I
have
been
working
on
it
and
I've
checked
out
some
of
the
things
and
still
there
are
a
lot
left
and
I'll
be
reviewing
those
things
which
I
have
completed
right
now,
so
yeah.
The
first
one
is
that
I
have
set
up
a
new
structure
so
actually
before
that.
If
you
guys
want
to
take
a
look
at
the
code
and
where
it
is
actually
the
work
is
being
happened.
I
It's
so
it's
in
a
new
branch
called
machine
way
restructuring
in
reports.
If
I
have
shared,
I
mean
you
have
the
link
over
here.
If
you
want
to
go
and
check
what
and
all
the
things
are
being
made
and
yeah
so
now
coming
to
the
tasks,
so
we
have
that,
like
the
news
texture
to
the
code
base
has
been
set
up
to
give
you
a
idea.
So
this
is
what
the
structure
of
our
ui
that
we
have
right
now.
I
I
A
look
at
the
output
in
the
branch
here
and
yeah
also,
I
have
set
up
a
unit,
testing
and
integration
testing
frameworks.
I've
used
react,
testing,
library
and
then
just
for
that,
and
after
that,
I
have
initialized
3dx
yeah
and
I've
also
used
toolkit
along
with
whether
to
reduce
the
border
plate
and
yeah.
I
After
that,
I
have
initialized
relay,
which
is
a
graphical
client
that
we're
using
for
us
to
communicate
with
the
back-end
server
so
yeah
and
yeah,
and
I
have
a
set
of
prettier
and
es
link
which
are
for
formatting
and
linking
respectively
and
yeah
and
like
these
are
the
just
set
up
things
and
after
that,
the
one
of
the
huge
tasks
is
to
create
actions
and
the
thumbs
and
reduce
the
logics
for
all
the
functionalities
that
has
to
be
implemented
with
measuring
server.
So
these
are
a
list
of
those
things.
I
So
basically,
what
this
means
is
that,
if
any
of
any
one
of
these
things
was
complete,
then
it
basically
means
that
the
only
thing
that
is
left
for
that
particular
feature
to
be
functional
is
to
write
the
ui
components
so
yeah.
In
this
case,
you
can
see
that
the
dashboard
page
for
like
in
all
the
functionalities
that
are
required
for
and
all
the
actions
and
thumbs
and
the
reducer
logics
that
are
required
for
the
dashboard
page
to
be
fully
functional,
is
written.
I
B
I
And
yes,
still,
these
are
left
which
we
have
to
complete
and
after
that
we'll
have
to
write
the
ui
components
for
each
and
every
one
of
them,
and
this,
I
don't
think,
is
a
huge
task
because
we
would
essentially
be
doing.
I
mean
we
already
have
the
ui
structure
in
our
current
code
as
well,
so
we
just
have
to
refactor
it
a
little
bit
and
then
make
it
more
readable
and
stuff
and
also
yeah.
So
this
won't
be
a
huge
task.
A
I
Actually,
I'm
thinking
that,
like
once
this
particular
tasks,
are
complete.
I
think
that
we
can
actually
invite
other
people
who
are
interested
in
working
as
well
to
collaborate
with
this
thing,
so
that
yeah
after
this,
we
would
have
a
convention
and
then
like
that
would
be
structured.
So
it
would
be
easy
for
people
to
contribute
to
it
as
well.
I
So
these
are
the
list
of
tasks
that
we
have
to
accomplish
in
order
for
like
to,
in
order
for
us
to
say
that
this
thing
is
totally
complete,
so
yeah-
and
this
is
where
we
are
now
so
by
september-
15-
I'm.
I
believe
that
I'll
be
able
to
complete
this
thing,
and
then
we
can
other
folks
who
are
interested
can
come
and
take
up
different
issues.
I
mean
take
up
each
one
of
these
starts
and
start
working
on
them,
so
yeah.
K
A
A
This
set
of
changes
is
sweeping
there's
a
design
spec,
that's
linked
in
the
meeting
minutes
that
you
know
a
number
of
you
have
reviewed
and
approved,
and
so
this
is
less
of
a
design,
spec
and
more
of
a
decision
making
framework
like,
and
so
the
implementation
and
restructuring
is
happening.
Inside
of
the
this
branch
is
carrying
the
torch
so
to
speak,
but
certainly
not
the
only
one.
So
he's
calling
this
out
just
to
say
this
work
is
in
flight.
A
He
thinks
that
a
significant
the
first
iteration
is
probably
ready
to
in
a
little
over
a
week
or
about
a
week
or
exactly
a
week
and
he's
soliciting
input
and
feedback
and
engagement,
and
so
please
go
and
engage
it's
good
to
be
on
the
ground
floor
of
how
redux
is
being
incorporated,
and
it's
really
necessary
for
the
type
of
intelligent
and
kind
of
real-time
application.
Experience
that
we're
looking
for
measuring
to
provide.
So
this
is
pretty
neat
okay
based
on
time.
Gara.
Do
you
want
to
go
next?
L
L
So,
as
you
can
see
that
we
are
using
a
similar
kind
of
a
configuration
form
for
the
patterns
as
well
as
for
the
applications,
so
this
thing
we
can
keep
it
as
a
central
component.
So,
as
this
thing
also
discuss
the
comments
on
the
issue,
but
the
main
issue
we
will
face
and
on
centralizing,
this
particular
pattern
from
component
is
that
we
are
passing
each
and
particular
id
or
name
as,
for
example
over
here
we
are
passing
applications
and
application
file
or
application
data
with
all
the
apis
selected
to
the
applications
or
the
patterns.
L
I
I
think
that
will
not
create
an
issue
for
now,
since
the
main
reason
that
we
are
providing
the
function
include
as
a
prop
is
to
reduce
the
amount
of
redundant
code.
So
that
is
something
that
is
reducing
it.
So
that's
why
it
is
here,
and
secondly,
as
you
said
like
a
very
well
said
that
pattern
from
connectors
are
one
component
and
the
applications
are
patterns
as
well
as
filters
in
some
way.
K
L
I
really
yeah,
I
think
I
may
not
be
able
to
explain
it
properly,
so
I
was
saying
that
in
the
pattern
form
over
here
function,
we
are
having
this
application.
Similarly,
we
are
having
it
for
the
patterns
right
yeah.
So
how
can
we
then
use
this
as
a
common
component?
So,
but
we
are
declaring
it
separately.
I
Okay,
okay,
okay,
so
I
believe
applications
patterns
and
maybe
filters.
I
don't
really
know
less
about
filters,
so
applications
and
pattern
has
a
common
pattern
and
for
the
timing
they
can
be
used
and,
of
course,
we
will
be
needing
some
minor
changes
according
to
the
schema
that
is
coming
for
applications
and
patterns
and
how
they
are
behaving
internally
for
the
ui.
We
need
some
change
minor
change
inside
the
usable
component,
and
that
should
be
done.
L
About
the
this
delete
date,
confirmation
model
that
we
are
using
across
the
patterns,
filters,
application
and
the
in
the
performance.
So
we
are
regarding
this.
Yesterday
I
had
a
talk
with
so
the
current
best
approach.
We
got
on
a
solution
that
the
whole
model
that
we
are
using
the
perf
model
we
are
using
over
here.
That
needs
to
be
refracted
from
the
scratch,
so
we
can
implement
all
these
features
so
implementing
so
changing
the
whole
model
would
be
a
good
idea
for
this
thing.
I
So,
to
give
you
like
yeah
so
basically
like
we
are
using,
we
have
a
common
component.
We
have
a
component
called
a
prompt
model
which
is,
which
is
what
we
are
using
for,
which
is
what
we
are
using
across
the
material
for
displaying
these
kind
of
electrons,
whether
you
want
to
accept
it
or
decline,
those
kind
of
stuff.
I
So
basically,
right
now
we
are
only
allowing
like
it
just
has
three
components
written,
it
has
a
title:
it
accepts
a
title
and
a
subtitle,
and
then
yes
or
no
so
with
that,
if
you
want
to
display
the
number
of
I
mean,
like
the
total
number
of
you
know
the
items
that
you
have
selected,
then
we
won't
like.
If
we
want
to
add
one
more
field
to
that
particular
component,
then
it
actually
breaks
the
it
does
it.
I
I
Otherwise,
like
other
thing
that
we
can
do
is
like
we
can
take
the
whole
prompt
component
model
and
then
build
up
on
it
like
create
a
new
model
out
of
it,
and
then
basically,
we
would
just
add
one
more
field
to
that
model
and
yeah
that
would
that
would
be
a
different
model.
So
that
is
also
a
different
approach.
We
can
follow
yeah.
I
So
we
need
some
help
over
the
patterns
component,
since
we
have
a
lot
of
item
to
do
for
the
pattern
itself
pattern
page.
So
let's
do
it
and
finish
it
up.
So
I
have
created
an
issue
discussing
all
the
action
items
that
we
are
needing
to.
You
know
make
this
pattern
speech
success
and
then,
whatever
the
team
are
thinking.
So
that's
why
I
have
created
this
issue,
so
this
small
issue
can
be
broken
down
into
several
other
issues
like
the
smaller
ones
that
is
checked
items.
I
I
So,
wherever
there
is
importance
of
combining
the
components
we
need
to
combine
it
and
whenever
there
is
not
so
we
have
to
extract
them,
so
so
small
things
have
been
done
by
me
in
into
my
recent
year,
so
yeah.
That
is
also
great
if
you
can
watch
it
and
for
now,
if
you
can
see
this
page,
so
the
pattern
forms
the
the
whole
code
for
the
pattern
from
our
pattern
component
is
written
just
below
the
machine
pattern,
so
we
have
to
extract
it
out.
I
So
since
we
are
using
our
next
js
and
I
have
very
less
information
like
knowledge
about
the
next-
yes,
so
I
I
just
don't,
I
wanted
to
you-
know,
mess
up
with
the
how
routing,
once
that's
why
I
had
put
that
beside
the
actual
our
top
level
component.
So
we
can
just
create
a
new
pattern
form
sorry,
we
can
just
extract
out
the
code
into
its
own
file
and
then
make
this
file
make
this
component
as
a
reasonable
component
as
we
as
just
what
have
discussed
about.
I
So
you
can
do
that
and
there
are
other
action
items
we
can
also
think
of
so
multiple
applications.
Here,
of
course,
that
is
something
that
is
really
very
important
for
for
the
success
of
the
pattern,
vision
that
we
are
thinking
of.
So
if
you
see
the
book
info
so
that
has
multiple
applications
that
is
running
concurrently
or
multiple
applications
are
communicating
with
each
other.
I
So
in
the
current
implementation
there
is
not
a
feature
for
multiple
applications,
so
there
is
only
you
can
only
provide
one
application
from
this
step,
so
you
can
provide
one
application
and
that
it
will
be
reflected
up
here.
So
that's
the
only
thing
right
now,
since
we
are
using
object,
start
find
so
what
it
does
is
it
just
finds
the
first
application
that
we
are
from
the
yaml
file,
then
just
returns
it.
So
that's
why
we
are
using
only
one.
So
what
we
are
thinking.
I
What
we
can
do
here
is,
since
we
are
using
multiple
applications
here,
so
we
can
give
some
ways
in
the
rj
form
itself
to
to
list
multiple
applications,
actually
right
so
same
for
the
kubernetes
services
same
for
configure
add-ons
and
same
for
the
other
rescue
messages
or
traffic
message.
Whatever
we
are
gonna
just
add
it
yeah
right.
I
So
that
was
the
one
thing
that
we
have
to
do,
and
that
is
something
that
is
on
priority,
so
ad
reverse
change
operation
for
the
yaml
editing,
so
that
is
nothing
but
actually
whatever
we
are
doing
here,
so
it
just
change
the
yaml
right.
So
it's
just
change
the
yaml
in
real
time.
So,
but
whenever
we
change
the
yaml,
it
is
not
reflected
into
the
rjsf.
I
I
That
is
the
expectation,
so
that
is
happening
good,
but
actually,
whenever
we
change
the
amount,
so
it
should
reflect
the
changed
thing
into
this
form
also.
So
that
is
the
actual
expectation,
so
that
is
something
can
be
pronounced
as
the
reverse
of
something
yeah,
so,
okay,
so
actually
I
had.
I
was
using
the
machine
mesh
interface,
a
pattern
service
form,
since
most
of
the
thing
that
we
are
doing
here
is
actually
already
written
in
the
machine
service
form
itself.
I
So
I
was
just
using
using
that
component
itself.
So,
but
recently
we
just
get
into
a
lot
of
troubles
where
someone's
changing
the
code
in
the
machine
center
in
the
mesh
map
and
then
the
side
effect
is
just
visible
in
the
patterns
file
and
same
applies
for
whenever
we
change
something
in
the
patterns
file,
then
there
is
some
problem
with
the
measure
right.
I
So
that's
why
just
try
to
extract
out
the
code,
so
so
we
can,
just
you
know,
replace
the
code
in
the
the
changes
in
the
max
map
that
we
did
for
for
recently
to
the
previous
one
right.
So
we
can
do
it
since
we
are
not
using
that
component
for
the
patterns.
Fine,
so
we
can
just
add
it
invert,
it
yeah,
so
that
was
it
and
yeah.
Of
course,
that
is
the
applied
custom
scaling
styling
towards
the
phone.
I
J
I
A
So
the
issue
that
avi
was
describing
each
of
those
check
boxes.
The
issue
that
he's
describing
is
really
an
epic
like
it's
a
it's,
a
large
set
of
changes
that
need
to
go
through
and
those
changes
can
be
done.
A
lot
of
them
can
be
done
a
la
carte.
So
so,
if
you
pick
off
one
of
those
check
boxes,
you
can
anyone.
A
A
I
Actually
it
is
about,
since
we
are
just
providing
a
complete
way
to
change,
auto
config
or
to
configure
the
application.
So
our
namespace
is
something
that
is
really
important.
So
we
are
just
providing
a
new
text
field
for
them
to
change
their
namespace
accordingly,
or
that
the
text
will
also
would
auto,
detect
the
namespace.
If
they
have
already
provided
one
into
the
previous
build
configuration
file
so
yeah,
I
think
it
would
come
with
the
yaml
itself,
the
value
of
the
namespace.
We
have
to
just
look.
A
A
A
Good
good,
I
don't
for
anyone
that
didn't
notice,
I
mean
patterns,
are
a
big
thing
to
the
project.
Abby
just
called
our
baby.
Ugly,
I
think,
is
what
he
did
so
and
it
looks
like
he
got
away
with
it
as
well,
so,
apparently
that
our
new
newborn
needs
some
help
anyway,
I'm
getting
into
theirs.
It
will
be
good
for
all
of
you.
Rjsf
is
a
library
that
we're
going
to
be
using
quite
a
bit.
I
Yeah,
actually,
a
lot
of
the
techniques
are
really
very
beginner
friendly
and
they
just
have
very
small
changes
to
work
around,
and
actually
it
will
help
a
lot
in
understanding
the
messaging
patterns
for
itself.
So
if
someone
is
new
on
the
call
and
they
want
to
work
on
it,
so
they
can
definitely
work
on
it
and
it's
really
very
easy
and
a
great
starting
issue
like
for
someone
and
you
can
connect
on
connect
with
me
on
slack.
A
Cool
okay,
yeah!
Thank
you.
Thank
you.
Hobby!
Well,
great!
Well,
we're
right!
At
the
top
of
the
hour,
there's
a
couple
of
items
to
chat
through
extremely
briefly.
One
was,
with
with
respect
jared,
had
called
out
a
couple
of
issues,
or
at
least
one
and
maybe
two
but
but
basically
led
to
a
couple.
So
one
was
lack
of
compatibility
with
kubernetes
1.22
jared.
I
I
think
we're
past
that
now
or
the
edge
release
is
past
that
I
think
so.
Thanks
to
your
thanks
to
you.
A
E
A
A
E
Yeah
so
yeah,
what
happens
is
in
the
mini
cube
environment
when
we
try
to
install
basically
provision
steel,
because
at
that
point
we
because
we
internally
use
him
installation
it
tries
to
escalate
the
privileges
which
is
not
something
that
service
account.
The
current
cluster
rule
that
we
have,
it
doesn't
have
the
privilege
for
the
same,
so
the
operation
currently
fails
in
mini
cube.
E
So
what
we
need
to
do
is
basically
add
so
right
now
we
have
access
to
a
few
works
like
get
get
list
and
delete,
and
those
kind
of
things
whatever
we
don't
ask
access
for
is
a
proof.
That's
another
thing
that
we
need
or
again
aztec,
would
also
this
stuff.
This
is
something
that
I've
tested
so
yeah
it
works.
This
is
this
is
something
that
we
need
to
do
actually
do
fixation.