►
From YouTube: Design Pair Session - 04-06-2023
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everyone:
this
is
the
design
pair
session
on
April,
6th
and
I've
added
two
things
to
the
agenda.
Today,
though,
the
first
one
based
on
some
adjustments
to
the
16-0
plan,
might
not
be
as
relevant.
A
Just
for
those
of
you
who
don't
who
haven't
followed
along,
it
looks
like
Andrew
might
be
going
forward
with
looking
at
the
deployment
Details
page,
which
is
a
very
easy
way
to
solve
for
this
top
issue
here.
So
I
might
pivot
kind
of
like
the
work
I'm
doing
here
to
revolve
around
the
deployment
Details
page
instead,
but
Andrew
I,
don't
know
if
you
wanted
to
talk
to
that
at
all.
B
B
There's
no,
no
changes
to
like
data
models
or
anything
crazy
like
that,
but
kind
of,
like
I,
did
starting
off
point
for
some
of
these
other
features
that
we
want
to.
We
want
to
tackle
going
forward.
A
So
basically,
the
problem
with
this
one
right
now
is
when
users
are
going
to
approve
a
deployment
or
they
have
a
deployment
that
they
need
approved.
We
don't
currently
show
anyone
with
developer
access
or
below
who
can
approve
their
deployment
so
you've
given
you're
kind
of
given
this
modal.
Let
me
just
move
this
out
of
the
way
with
this
current
approvals
zero
out
of
one,
but
we
don't
actually
tell
you
who
can
approve.
So
you
are
waiting
on
your
approvals.
A
A
A
What
we
have
on
the
settings
page
to
read
only
view
either
on
settings
which
I
don't
now
that
I've
kind
of
looked
at
it
I,
don't
think
that'll
work
or
on
like
the
edit
environment
page
just
somewhere,
where
we
have
that
table
of
rules
that
everyone
can
kind
of
go
view
who
can
approve
or
not.
And
then
we
just
link
that
from
this
modal
or
now
from
that
page,
so
that
they
can
go
in
and
kind
of
see
who
the
approvers
are.
A
B
So
I
think
we
already
show
the
table
if
you're,
using
multiple
approval
rules,
even
if
you
haven't
approved
yet,
does
that
sound
right,
Andre
I
know
you've
been
in
the
area
a
lot.
D
C
Any
of
you
have
a
an
exam
plus
hand
so
that
we
can
I'm
gonna
leave
it
that
quickly
like
how.
How.
A
Does
it
look
like
today,
I
think
I
actually
do
have
that,
but
I
think
it's
just
shown
who
has
approved
or
not
who
has
to
approve,
but
let
me
you're
going
to
watch
me
trying
to
figure
out
where
this
is
now
showing
in
figma.
Is
it
this
design
with
the
table.
B
A
Yeah
so
I
still
I
think
this
now
is
giving
Clarity
of
who
has
approved
so
far.
But
we
don't
show
who
is
left
to
approve
on.
C
A
B
Them
too,
just
the
access
levels
can't
be
links,
yeah
yeah,
the
groups
can
be
groups
and
users
can
be.
A
Okay,
that
actually
might
solve
for
this
to
start
with,
then,
is
as
long
as
we
can
link
for
groups
and
users.
This
issue
might
actually
be
solved
by
this
adjustment.
B
C
A
Yeah,
because
in
this
table,
when
they
do
approve,
we
have
the
little
bubbles.
It's
just
at
the
role
axis
they're
only
given
that
like
maintainers
can
approve,
but
they're,
not
really
given
a
list
of
people,
but
if
we're
showing
groups
and
users
do
we
think
that's
like
enough
information
to
start
with
this
is
more
than
we
currently
give
them.
So
I
think
this
is
getting
there
to
solve.
For
this.
A
B
Yeah
yeah,
so
this
is
this-
is
live
on.com
right
now
for
multiple
approval
rules
yeah.
We
just
need
to
come
up
with
a
similar
design
for
unified
rules.
A
C
I
think
it
would
be
nice
to
to
have
the
the
guide
on
how
to
move
from
unified
to
multiple
approval
rules
is
that
that
would
be
nice
to
have
this.
But
I
don't
want
to
spend
like
in
these
times
engineering
time
on
building
our
DUI.
A
A
The
second
thing
I
just
wanted
to
ask,
is-
and
Victor
and
I
have
already
been
chatting
about
this,
but
it's
for
the
filtering
concept
for
the
kubernetes
dashboard,
so
I'm
still
fairly
new
into
this
area,
so
I
just
wanted
to
review
kind
of
what
I've
mocked
up
so
far,
but
basically
for
the
MVC.
A
For
this
we're
expecting
users
to
enter
the
dashboard
through
an
environment
block
on
the
environment
index
page
and
when
they
enter
in
we'll
pre-fill
kind
of
the
filters
through
what
the
environment
has
so
I've
chatted
with
Victor
a
little
bit
about
this.
But
let
me
share
my
screen
here.
A
So
I
think
this
is
fairly
similar
to
what
Ellie
had
earlier
I.
Think
the
only
thing
we've
adjusted
is.
We
want
to
filter
by
namespace,
name
and
label
type
we've
split
out
name:
space
name
into
a
drop
down
and
label
type
into
a
search.
Filter
I
haven't
actually
mocked
up
how
this
would
work,
but
I
did
have
it
when
it
was
the
bigger
one.
So
this
works
very
similar
to
like
the
issue.
A
One
where
you
choose
the
filter
is
or
is
not
and
then
choose
your
label
and
that
kind
of
shows
up
at
the
top
I.
C
Have
the
feedback
here?
This
is
not
what
I
meant,
because
basically,
labels
just
change
and
the
whole
idea
is
that
labors
are
are
like
a
key
value.
A
Okay,
that
makes
more
sense.
So
then
the
first
one
you're
choosing
is
the
label
and
then
you're
choosing
it
is
or
it
isn't
and
then
you're
choosing
the
label
value
that
goes
into
possible.
Yeah.
A
E
Lot
more
quick,
quick
question:
does
it
mean,
like
user,
have
to
type
the
label
name
and
the
label
value
every
time
visiting
this
page.
C
E
C
E
Yeah
I
think
so.
I
just
need
to
wrap
up
rub
my
head
around
about
like
the
resolution
relationship
between
this
kubernetes
dashboard
and
the
environment,
kubernetes
dispute
I
think
these
are
two
different
features
right,
so
yeah
I
I
still
don't
understand
that
the
whole
concept
of
like
how
these
are
connected
and
like
user,
how
move
move
around
so
yeah.
C
Yeah,
let
me
try
to
give
a
bit
more
details
why
we
have
a
separate
combatus
dashboard,
because
it's
a
very,
very
valid
question
actually
like.
Why
can't
we
just
show
all
the
related
stuff
within
the
environment
page
and
the
answer
to
that
is
actually
very
simple,
which
is
we
don't
have
enough
space
there,
like
you
had
this
topic
that
you
reached.
You
know
I
think
last
week
or
two
weeks
ago
when
it
was
like,
but
how
can
the
user
specify
the
different
kinds
that
we
will
list
on
the
environments
page
and
monetary?
C
Was
that
that's
preset
redefine
is
they
can
choose,
and
the
reason
for
that
is
that
it
might
change
from
company
to
company
from
Team
to
team
what
they
want
on
the
environments
page,
which
is
really
important
like
some,
but
like
very
likely
country
map
secrets
are
important
to
see,
but,
like
some
might
use
volume,
some
might
not.
Some
might
even
know
some
custom
resources,
some
might
not
and
so
on
and
so
forth.
So
that's
why
we're
like?
Okay,
that's
that's
not
overwhelm
the
environments
page.
C
There
are
already
too
many
accordions
and
and
too
much
information
there
anyway,
and
that's
why
I
decided
and-
and
we
want
to
add,
even
more
features
there.
So
it's
not
just
a
view
of
the
resources,
but
for
the
workload
type
like
pods.
We
would
like
to
provide
reports
terminal
for
many
things,
we'd
like
to
show
related
events
when
possibly
would
like
to
show
log
tailing
and
all
of
that
it
doesn't
fit
into
the
environment
page.
So
that's
why
we
have
a
commanded
dashboard.
E
Yeah
so
like,
if
user
needs
to
investigate
something
very
minor
things,
and
they
can
go
to
kubernetes
dashboard
to
dig
into
the
resources
because
yeah
it
can
show
everything.
Basically,
yes,
but
in
general,
like
a
user,
sees
the
resource
overview
in
environment
based.
C
A
C
Need
to
pre-select
the
agent
and
it's
it's
it's
hard.
If
you
don't
know
which
agent
we
want
to
select,
that's,
we
had
a
discussion
with
tiger
and
that,
like
figuring
out
from
a
project
that
inherits
an
agent
from
a
group
that
actually
has
access
to
an
agent
contribution,
totally
different
project,
that's
like
very
difficult
from
a
database
perspective,
and
that's
why,
like?
Okay,
let's
not
do
that.
E
A
I
I
just
had
one
more
question.
I
did
see
in
the
design
issue
for
this
that
we
might
need
a
page
when
they
haven't
had
an
agent
selected.
A
Is
that
still
something
that
we're
going
to
encounter
with
the
environment's
entry
point?
And
if
so,
what
are
we
kind
of
expecting
to
show
on
that
page?
Just
like
a
hey,
go
to
the
environments
page
and
select
an
agent
from
there
or
I.
C
I
I
think
something
like
this
that
yeah
what
I
was
thinking
about
this,
so
how
we
came
up
with
the
dashboard.
What
the
idea
was
the
the
old
web
ID,
which
is
basically
its
own
app
within
gitlab.
A
C
The
dashboard
is
something
similar:
it's
it
takes
over
the
main
navigation
as
well
as
you
can
see
and
and
everything,
and
so
what
I
would
say
is
like
basically
kind
of
like
a
404
page,
just
perhaps
a
bit
more
informative
that
you
should
open
this
page
from
a
project,
environment,
page
or
group
environment
page.
We
see
and
that's
how
go
and
go
there.
Basically.
A
C
A
Well
and
then
the
last
question
I
had
is
I
noticed
we
have
kind
of
like
this
breadcrumb
Trail
up
here
with
agent
name
and
when
they're
on
this,
like
agent
overview
page,
it
kind
of
shows
everything
related
to
that
agent
when
you
click
on
this,
like
kubernetes,
dashboard,
breadcrumb
and
you're,
brought
to
like
a
top
level.
What
is.
C
A
Okay,
well,
that
makes
sense.
I
think
that
was
all
my
questions
about
this
I
just
wanted
to
make
sure
I
was
on
the
right
track,
with
kind
of
how
this
filtering
worked.
If
separating
out
that
namespace
and
then
having
agent
ideas,
just
static
content
at
the
top
is
what
we
were
looking
for
with
this
filtering,
but
if
so
I
can
clean
this
up
and
get
this
done
by
the
end
of
the
milestone
for
sure,
so
we
can
get
working
on
it
soon.
A
A
C
I
think
you
can,
because
you
can
go
to
the
choose,
a
specific
kind
like
ports,
and
then
we
could
add
that
to
the
deployment,
because,
basically
the
decide
Bar
menu
is
not
just
one
level
but
like
under
the
workloads.
We
want
to
show
all
the
workload
types
which
is
deployments:
pods
demon,
set
jobs,
Chrome
jobs
and
I
think
I
left
out
something,
but
there
is
anyway,
there
are
a
few
workload
types
that
are
under
the
workloads.
I
think
there
is
somewhere
designed
that
actually
shows
the
some
of
these
open
or
or
the
issue
describe
them.
A
I
have
all
of
Ellie's
designs
here:
I'm
just
yeah.
A
Yeah
because
I
think,
if
there
are
levels
deeper,
we
might
wanna
kind
of
keep
that
agent
as
the
top
level
one
and
then
have
them
be
able
to
go
down.
So
I
could
see
value
in
that.
A
So
I've
just
switched
over
to
this
yesterday.
How
do
you
get
to
like
the
environment
dashboard
with
this
new
navigation.
A
How
do
you
get
to
the
top
level
like
those
Dash
used
to
be
at
the
top,
because
I
was
like
okay,
we
could
probably
work
something
in
there
where,
when
you
click
on
it,
you
have
that
whole
new
nav,
like
this
kubernetes
nav
under
the
new
now
but
I,
haven't
been
able
to
find
how
to
get
to
the
environment
dashboard
with.
B
A
A
B
A
A
A
So
I
think
we
could
probably
do
something
around
this
in
your
work,
but
yeah
we'll
probably
have
to
rethink
the
side
navigation
for
the
kubernetes
dashboard.
Now
that
this
is
all
new
and
I
also
think
has
there
is
there
some
lock
on
navigation
changes
for
the
next
few
months?.
D
C
E
Just
quick
question
is
any
page
to
show
list
of
agents
that
the
user
can
access
to.
For
example,
like
we
recently
introduced
the
user
access
keyword
so
like
each
agent
config
file
contains
that
like
hey.
This
is
the
agent
a
is
allowed
to
yeah
access
by
the
user,
a
and
then
probably
like,
but
with
this
keyword
is
again
have
multiple
agents
like
we
can
show
a
list.
I
was
just
wondering
that
when
we
talking
about
this
overview,
things
it
seems
like
this
page
belongs
to
our
specific
user.
E
C
This
is
this
is
what
I
I
said
a
couple
of
minutes
ago,
that
it's
very
difficult
to
get
the
desktop
agent,
that
the
user
has
access
to
I
won't
be
able
to
quickly
find
the
discussion
I,
don't
even
remember
where
it
was
with
order
or
tiger,
but
basically
they
one
of
them
told
me
that
it's
it's
almost
impossible
and
then
the
the
best
idea
we
had
to
make
it
basically
eventually
consistent
in
a
way
that
build
a
separate
index.
Whenever
access
level
change,
then
we
update
the
index,
but
it's
like
that's.
E
Okay,
so
I
think
yeah
I
need
to
talk
with
tiger
about
this
thing,
I'm,
not
sure
what
the
technical
challenge
here,
because,
like
we
are
prevailing,
like
purchasing
data
of
config
file
into
database,
so
that,
like
we,
can,
if
gently
search
this
type
of
information,
I'm,
not
sure
if
that
can
resolve
the
this
technical
change
or
is
any
like
as
a
concerns.
But
yeah
I'll
talk.
B
B
A
E
Or
I
just
one
question:
I.
Think:
okay,
we're
gonna
emerge
grocery
today,
right,
Victor
I
posted
a
bunch
of
comments,
but
yeah.
If
we
feel
free
to
go
forward,
it's
not
blocker
comments
anyway,
so
yeah.
Thank
you
for
creating
a
major
request.
C
Yeah,
thanks
for
the
comments,
I
I
would
love
to
hear
your
opinion.
Whether
we
are
good
to
merge
or
not,
I
haven't
seen
comments
from
Mikhail
and
tiger
and
Pam
I
mean
day
week
is
all
over
already.
I
know
that
I
mean
mikai
might
not
have
comments
because
we
wrote
it
together,
but
I
would
love
to
I.
Would
love
to
ask
all
of
you
to
to
have
a
look
at
least
upload
the
Mr?
C
If
you,
if
you
don't,
have
any
comments
so
that
we
know
that
you,
you
have
read
the
glossary
and
you
understand
the
terms
there
and
then,
if,
if
I
see
a
large
number
of
upwards,
at
least
in
the
in
the
Mr
I
will
I
will
merge
it
tomorrow
morning,
the
good
chance
for
Hunter
as
well
too
getting
there.
A
No,
it
looks
it
looks
good
so
far,
I
just
had
a
small
like
I
adjusted
some
of
the
formatting
to
fit
more
of
a
glossary,
but
overall
I
think
it
looks
really
good.
A
No
thanks
for
all
the
feedback,
I
really
appreciate
these
sessions
to
kind
of
go
over
these
things,
so.