►
From YouTube: Argo Contributor Experience Office Hour 11th Feb 2021
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).
B
A
Right
so
this
meeting
is
ui
ux
focused,
so
that
we
can
get
some
more
discussion
on
ways
to
improve
the
argo
ui,
and
so
we
have
serena
and
beau
here
from
red
hat,
to
help
us
and
provide
their
expertise
on
the
subject.
A
Right,
hi
bridget,
so
yeah
we
are,
we
have
a
list
of
topics
to
go
over
today
that
I've
kind
of
prepared.
We
have
some
people
that
added
other
topics
as
well.
A
I
kind
of
went
through
the
argo
cd
backlog
of
issues
and
tried
to
find
some
overarching
themes
of
issues,
so
I
can
share
some
of
those.
Let
me
just
share
my
screen
yeah,
and
you
can
see
the
agenda
right
now.
A
Yes,
okay,
so
the
first
one
that
I
kind
of
wanted
to
go
over
is
general
accessibility
in
argo
cdui.
A
Some
of
these
topics
include
this
all
kind
of
started
stemming
from
this
issue,
which
was
the
badge
of
the
status
badge
component,
and
so
the
main
problem
with
this
was
that
it's
kind
of
small
when
you
look
at
it
here
and
that's
really
hard
to
see
unless
you
like,
really
enlarge
it,
there's
bad
contrast
ratios
with
it
and
particularly
with
the
yellow
on
the
white,
and
so
one
way
that
we
were
thinking
about
going
about.
This
was
to
fix.
A
It
was
possibly
changing
the
argo
cd
color
palette
in
a
couple
places,
maybe
maybe
the
whole
thing
it
depends
on
like
what
the
community
thinks.
Argo
cd
currently
has
this
color
palette
for
that
relates
to
all
of
the
statuses
and
like
sync
status,
health
status,
and
I
let
me
zoom
in
here.
A
We
kind
of
wanted
to
get
some
more
feedback
on
what
the
community
thinks
about
this.
So
I
talked
to
serena
a
couple
days
ago
and
she
had
suggested
that
we
use
the
color,
let's
just
like
borrow
them
from
pattern
fly,
which
is
something
that
red
hat
open
shift
uses.
C
Yeah,
I
was
just
going
to
say-
and
I
think
bo
and
bridget
can
attest
to
this
as
well
like
there's
a
lot
of
accessibility
testing
with
the
pattern
fly
color
palette
that
we
use-
and
I
don't
know
if
everybody
knows
but
pattern
flies
like
an
open,
open
source
design
system.
C
A
D
A
D
A
Fly
colors,
we
weren't
sure
how
tied
argo
cd
is
to
these
colors.
If
there
was
any
particular
reason
for
choosing
these
colors
or
if
it
was
just
kind
of
like
it,
looks
pretty.
D
Randomly
chose
colors,
plus
we
and
some
common
sense,
but
no
particular
strong
attachment
to
any
colors.
A
D
I
mean
definitely
no
objections
plus.
I
think
we
should
maybe
talk
quickly
with
argo
workflows
team,
because
we
have
a
shared
code,
library
and
the
simplest
way
to
change.
These
colors
would
be
to
just
go
ahead
and
just
update
existing
library,
so
it
will
affect
workflows.
They
would
inherit
new
color
palette,
okay,
yeah
and
instead
of
trying
to
duplicate
it
in
argo
cd.
Maybe
we
can
just
ask
them.
If
they
don't
mind,
you
know,
if
they
open
to
do
the
same,
then
we
can
just
change.
D
A
D
B
If
I
may
quickly
play
the
devil's
advocate
a
bit
and,
to
probably
add
a
little
more
details
to
what
serena
mentioned,
so
I
think
it
would
be
good
to
find
out
how
pattern
flight
fits
in
all
this.
My
question
would
be:
is
pattern
fly
your
red
hat
thing
or
it's.
A
community
thing
can
recommendations
from
patent
fly
with
the
use
of
the
research
that
has
been
done
to
get
all
those
records
get
to
those
recommendations
be
taken
into
the
argo
cd
color
palette
yeah.
B
So
I
think
if,
if
we
could
highlight
how
pattern
fly
as
a
project
is
being
run
generally
for
the
community,
that
would
be
good
just
so
that
it
doesn't
feel
like
it's
a
red
hat
thing.
That's
going
in
throughout
the
city.
I
don't
know
serena
if
you
could
give
an
overview
of
patent
funding
in
general.
E
I
mean
we
could
even
have
a
pattern,
fly
team
member
available
to
answer
any
concerns
or
questions.
I
mean
the
nice
thing
that
serena
and
you
you
shubik
have
both
said
is-
is
we're
kind
of
getting?
The
research
has
already
been
done
and
and
there's
a
there's,
a
very
large
palette
that
we
can
draw
from.
E
So
I
think
this
idea
of
how
that
works
with
the
argo,
ui
and
kind
of
figuring
that
out
is
is
a
next
step
and
then,
but
we
can
definitely,
we
can
definitely
get
a
little
more
information
about
your
pattern,
fly
question
and
even
have
someone
available
to
support
this.
You
know
on
a
call
or
something.
F
You
can
also,
oh
sorry,
you
can
also
join
the
pattern,
fly
slack
channel,
it's
open
source,
so
anyone
can
join.
C
We
can
get
that
length
too,
for
you.
The
other
thing
I
was
just
going
to
mention
too,
is
I
mean
it
it?
I
think
it
could
be
a
possibility
that
you
just
use
like
the
the
colors
that
are
indicating
status
without
necessarily
having
to
take
of
all
of
the
pattern,
fly
visuals
right.
So
that's
also,
I
think
another
thing
you
could
consider.
A
A
D
C
A
Okay,
other
accessibility
issues
is,
I
guess,
keyboard
navigation
and
we
had
remington
who
wanted
to
discuss
this.
G
Yeah,
this
should
be
pretty
brief.
I
opened
an
issue.
Would
you
mind
opening
that
up?
Actually
yeah?
Thank
you
yeah.
I
just.
I
think
it
would
be
really
useful,
not
just
for
the
sake
of
accessibility
but
for
the
sake
of
productivity,
to
be
able
to
navigate
the
entire
ui
with
keyboard
shortcuts.
G
So
I
included
a
few
of
my
thoughts
there.
Any
suggestions
would
be
appreciated,
but
they're
pretty
similar
to.
I
took
a
lot
of
inspiration
from
the
github
keyboard
shortcuts,
so
slash
to
search.
Obviously,
arrow
keys
are
pretty
straightforward,
but
yeah.
A
Yeah
and
then
this
was
also
another
issue,
basically
like
if
you
have
enter
as
like
a
default
like
you,
should
be
able
to
click
enter
and
like
have
it
actually
work.
So
like
there's
a
couple
places
in
argosy
dui,
where
it
really
doesn't
do
that,
and
you
would
kind
of
expect
it
to
it's
generally,
a
behavior
that
you
would
see
across
the
internet.
So.
D
Yeah
I
can
because
I've
worked
on
a
lot
of
ui.
I
can
tell
that
it's
not
even
we
didn't
even
try
yet
if
it
works
somewhere,
it
works
by
accident
yeah
and
it's
definitely
good
to
go
for
all
pages
and
try
to
fix
these
basic
things.
D
And
yeah:
do
you
think
it
makes
sense
to
kind
of
create
ticket?
For
that?
I
honestly,
I
don't
know
what's
included
it
could
be.
You
know
good
to
learn
from
you.
What
is
usually
must
have
things
like
tab
navigation.
As
I
understand
that
means,
user
should
be
able
to
navigate
through
input
elements
right
using
tabs.
D
C
Or
even
ctas
right,
like
even
just
any
button
or
any
anything
in
navigation,
nothing
that
remington,
I
think,
was
just
mentioning.
It
feels
to
me,
like
that's,
definitely
really
important,
but
you'd
want
to
be
able
to
navigate
from
each
element
to
the
next
first
and
then
be
able
to
make
your
selections
as
a
secondary
requirement.
G
I
think
they
could
both
go
into
the
same
pr.
To
be
honest,
I
think
that
the
tab
navigation
is
as
simple
as
adding
maybe
a
couple
lines
to
each
form
and
since
they're
components
it
should
be
pretty
easy
and
then
the
keyboard
navigation
is
a
little
bit
more
involved,
but
I
think
if
you
put
them
in
the
same
pr,
that
would
make
sense.
C
And
I
don't
know
a
ton
about
accessibility
and
I
don't
know
bridget
or
foe
if
you
guys
do,
but
something
with
the
area
tag
and
like
for
screen
readers.
I
don't
know
if
you
guys
are
doing
any
of
that.
That's
again
not
an
area
of
my
expertise,
but
if
you're
going
to
start
going
down
that
road,
you
might
want
to
consider
that
as
well.
G
E
A
H
There
was
a
lighthouse
that
was
used
for
checking
local
stuff
yeah
by.
C
H
I'm
josh,
I
am
the
troublemaker
who
has
filed
mostly
and
past
history.
For
me,
I
worked
on
the
mozilla
web
browser.
I've
worked
in
accessibility,
I've
worked
in
baidai,
I
worked
with
vocalization.
I've
worked
in
pretty
much
everything,
which
is
why
you'll
see
me
following
bugs
about
everything,
including
screen
readers,
so
yeah.
I
have
a
friend
who
I
one
of
my
people.
H
I
work
with
talk
with
regular
early
is
blind
and
so
every
now
and
then
I
will
post
things
on
the
screen
reader,
I'm
currently
listening
to
podcasts
at
2.8
times,
which
is
around
where
people
using
screen
readers
do
stuff.
I
definitely
use
keyboard
strokes
and
I
have
feedback
about
pretty
much
everything
I
have
not
used
arguing
with
a
screen
reader.
Yet
there
are
too
many
things
that
are
before
that
in
my
list
of
things,
but
I
imagine
about
six
months
I'll
probably
beat
it
up
and
file.
Another
20
bucks.
A
A
Okay,
so
I
think
that's
all!
I
have
for
accessibility
right
now,
I'm
sure
there's
more
to
talk
about
with
it,
but
we
should
continue
to
go
through
the
issues
that
I
have
here
so
next.
One
that
I
saw
a
lot
of
issues
about
is
filtering
abilities,
for
instance,
this
is
when
operations
should
offer
filtering.
H
I
mean
it's
basically
I
at
some
point.
I
spend
a
lot
of
time
in
spelt
in
in
spreadsheets
and
anytime.
You
have
headings
especially
when
you
have
lots
of
rows,
being
able
to
quick
filter
on
rows
or
on
on
columns,
so
basically,
for
instance,
mostly
here
the
status
field
or
potentially
the
kind
just
being
able
to
say.
Oh,
I
only
care
about
certain
statuses,
or
I
only
fear
about
certain.
I
mean
yes,
it's
certainly
name,
but
basically
anything
that
you
have
anytime.
H
You
have
a
column
header
that
represents
a
thing,
especially
there's
likely
to
be
repeats
or
you're
likely
to
be
interested
in
some
subset
of
those
things.
It's
really
quite
valuable,
and
ideally
we
would
do
this
as
a
instead
of
doing
it
as
a
one-off.
For
this
page
it
would
be
a
general
thing
that
would
be
in
the
framework,
so
we
fix
it
here
and
then
I
can
use
it
everywhere
else,
and
I'm
noting
that
the
word
results
is
has
a
call
on.
D
Yeah
I
wanted
to
mention
that
I
know
what
stops
us
from
doing
that
is
yeah.
We
need
some
kind
of
pattern
that
we
want
to
reuse
and
we
added
filters
to
applications
because
it
would
be
totally
unusable
and
I
was
so
we
were
forced
to
do
it,
but
this
page
and
a
list
of
repositories,
list
or
clusters
needs
filters
too.
D
H
To
be
honest,
my
general
favor,
so
this
thing
works,
but
as
people
will
know
or
see,
I
filed
a
whole
bunch
of
bugs
about
this
thing.
Yes,
it's
getting
better,
but
I
actually
spend
a
lot
of
time
in
either
google
sheets
or
microsoft
excel
and
the
quick
filter
model
is
closer.
Can
you
do
you
have
any
google
sheets?
If
not
I
can.
I
can
share
a
spell
checking
thing.
Maybe
I
might
even
be
able
to
pull
it
up
from
argo,
but
quick
filter
is
sort
of
a
much
more.
H
I've
shared
a
thing.
I
believe
that
anyone
can
touch
it
if
it
screams
only
people
with
link,
you
can
open.
So
since
you
have
a
link,
you
should
be
able
to
open
it.
H
Right,
so
if
you
I.
F
H
Hold
on
I,
no,
if
you
do
tools,
I
maybe
have
to
actually
make
you
sorry
data.
H
Oh
shoot:
okay,
fine!
Make
me
make
me
a
person
yeah
make
me.
D
A
F
H
Oh
yeah,
because
I
need
to
give
permission
to
the
app,
which
means
I'm
gonna
probably
have
to
rejoin
I'll,
be
back
in
a
moment.
A
Okay,
so
in
the
meantime,
we
can
continue
with
like
a
couple
other
little
issues,
so
another
one
is
filtering
by
date,
and
I
know
from
the
discussion
on
this
that
this
was
a
little
bit
hard
because
it
was
only
by
creation.
Timestamp
is
this
still
kind
of
in
the
same
status
area,
though,
like.
A
H
The
first
thing
for
me
is
a
status
like
for
messages,
for
instance,
there'll
be
a
whole
bunch
of
things
we're
seeing
successfully
and
there'll
be
some
that
are
out
of
sync.
I
only
care
about
things
that
are
out
of
sync,
but
things
are
in
error
state,
maybe
there's
something:
that's
there's
a
thing,
there's
an
application
which
has
multiple
name
spaces,
and
I
currently
only
care
about
one
of
the
data
spaces.
H
The
thing
that
has-
or
I
mean
it,
depends
on
how
complicated
your
chart
is
or
sorry
chart
is,
I
think,
a
helm
term.
Excuse
me,
but
basically
anytime,
you
have
something
that
has
some
amount
of
content.
This
one
doesn't
have
a.
I
mean
this
one
was
specifically
states,
although
there's
also
filtering
by
date,
some
of
the
other
bugs
I
filed.
You
have
these
huge
trees
where
they're
like
a
whole
bunch
of
different
kinds
of
resources,
and
so
I
only
care
about
maybe
replica
stats
or
only
hear
certificates.
H
I
only
care
about
secrets,
but
really
essentially
anytime
you're
doing
things
that
with
something
has
more
than
if
it
doesn't
fit
on
the
screen.
There's
a
likelihood
that
there's
some
way
to
categorize
it
and
the
user
only
cares
about
that.
Categorization
plus.
D
H
100,
but
yes
like
that,
that
was
specifically
why
this
was
filed
about
sync
status
is
like
we
have
huge
number
of
items
in
our
thing
and
almost
all
of
them
are
perfectly
happy,
but
somewhere
down
there
don't
know.
Where
is
one
that's
knocked.
C
Yeah
I
mean
from
a
usability
perspective,
I
think
filtering
by
name
and
status
are
always
really
helpful.
I
think
the
question
is:
do
you
have
to
have
a
filter
capability
for
every
single
thing?
That's
on
the
page,
and
that
would
go
back
to
use
cases
to
me
and
then
I
think
what
you
were
just
mentioning
around
different
resource
types
or
whatever
that
to
me
is
a
little
bit
different
than
filtering.
I
don't
know,
I
guess
you
could
think
about
it
as
filter
or
like
shutting
the
display
on
or
off.
H
Well,
his
kind
is
the
first
column
in
this
thing
and
that's
the
resource
kind.
So
you
can't
see
well
because
in
this
case
I
think
they're
all
probably
the
same
kind
in
my
picture,
but
they
yeah
it's
it's
a
pretty
common
thing
and
in
fact,
given
that
it's
literally
the
first
thing
at
the
table
it
somebody
thought
it
was.
D
Important
and
I
feel
like
we're
kind
of
saying
that
we
basically
we
want
to
improve,
we
want
to
have
a
reusable
table
component
that
has
filtering,
and
I
I
know
for
sure
we
also
had
ticket
open
to
support
sorting.
So
maybe
this
is
the
way
I
mean.
Maybe
this
is
simpler
solution,
so
applications
list
page
is
different.
D
A
Yeah,
okay,
so
just
like
in
general,
we
should
have
more
filtering
abilities.
Is
there
currently,
like
any
limitations
on
filtering
abilities,
like
reasons
why
it
hasn't
really
been
fully
implemented
yet
good
thing
about.
D
Like
cargo
cd
case
is
that
pretty
image
it
just?
Naturally,
all
the
information
fits
into
memory
in
browser,
so
basically
filter
filtering
could
be
done
on
client
side.
There's.
Just
no
reason
to
you
know
make
it
server-side
right
now,
because
it's
you
know
we
would
have
to
filter
things
like
number
of,
for
example
clusters,
and
if
you
have
more
than
1000
clusters,
then
it's
a
whole
different
problem
and
I
think
it's
same
for
everything.
J
Yeah,
I
think
there
are
some
open
source
components
available,
such
as
data
tables,
something
like
that
that
would
easily
enable
it,
but
still,
I
think
it's
it's
quite
an
effort
right
to
implement
that
yeah.
D
I
feel
like
if
we
go
for
it,
it
definitely
should
be
done
not,
for
you
know
one
table
yeah.
We
should
try
to
at
least
validate
it
with
one
such
table
and
have
intent
to
use
it
everywhere,
and
then
the
next
question
is
going
to
be.
What
do
we
do
with
applications
list
page
which
has
filters
right
now?
Would
we
keep
it
as
this
and
kind
of
make
an
exception.
H
J
But
I
I
think
it
would
be
really
useful
so
to
to
have
some
filtering,
because
I
I
know
from
my
experience
as
well.
So
if
you
have
some
some
very
large
applications
and
yeah,
just
like
your
use
case,
josh
if
swim
fails,
have
fun
finding
the
the
course
it's.
It
is
like
that.
So
it
would
be
a
really
a
really
valuable
addition
for
people
managing
applications.
Large
applications.
A
Some
of
them
are
not
really
all
that
consistent.
Some
of
them
don't
have
a
great
validation,
auto
complete,
not
positioned
correctly,
so
I
guess
it.
There
is
like
a
general
component
for
forms
right.
This.
D
D
D
I
think
it
inherits
line
hate
from
the
page
and
that's
why
sometimes
it
looks
wide
some
I
mean
too
high
like
yeah.
Sometimes
it
looks
too
wide.
Sometimes
it's
a
little
bit
narrow,
so
maybe
we
could
just
there
is
possibility.
We
can
just
improve
the
reusable
components
and
it
will
fix
things
in
all
pages
for
gracie.
A
G
D
Thing
so
and
again,
if
I'm
hoping
that
we
can
so
we
use
a,
I
think
it's
called
just
react
form
which
was
deprecated
and
then
we
built
on
top
of
it
our
own
kind
of
layer
and
maybe
if
we
try
to
get
rid
of
react,
form
and
replace
it
with
something
else.
I
would
see
if
we
can
keep.
You
know
just
replace
the
direct
form
and
then
keep
this
layer
on
top
attached
or
you
know,
try
not
to
change
it
much
and
this
way
we
can
save,
I
mean
we
don't.
G
D
G
I
also
opened
a
pr
a
while
ago,
like
a
few
months
back,
that
did
implement
a
new
version
of
this.
I'd
have
to
look
to
get.
It
was
never
merged,
so
I'd
have
to
look
and
update
it,
but
I
think
that
I
did
make
a
replacement
for
this.
D
I
I
just
my
biggest
care
would
be
to
you
know,
replace
forms
on
one
page
and
it
will
look
a
little
bit
different
and
then
we
never
have
energy
to
continue
and
then
and
now
we
ended
up
having
two
frameworks
and
it's
in
a
bigger
problem
I
feel
like.
I
would
commit
to.
You
know,
work
on
it
and
try
to
commit
to
replace
forms
everywhere
in
the
whole
application
within
one's
paint
and
what
makes
it
more
difficult
is
we
have
workflows
and
they
use
the
same
forms,
and
they
have
you
know
same
number
of
pages.
D
A
Okay,
if
there's
nothing
else
to
say
about
that,
we'll
move
on
to
visual
representations,
so
this
is
one
of
the
issues
provide
a
node
view
that
includes
child
applications.
H
We
have
a
lot
of
applications
which
have
related
pieces,
but
they're
kind
of
componentized,
but
often
like,
because
you
basically
make
each
application
fairly
small.
The
nodes
end
up
running
a
whole
bunch
of
pods
from
a
whole
bunch
of
unrelated
applications,
and
then
you
don't
actually
get
much
visibility
from
looking
at
the
node
view.
In
the
current
way,
it's
done
so
being
able
to
see
all
the
pods
from
all
the
applications
on
the
individual
nodes
is
helpful,
as
opposed
to
just
seeing
the
pods
for
the
application
you're.
Currently
looking
at.
D
Jesse,
I
think
we
talked
about
it
right.
I
think
so.
Like
a
long
time
ago,
we
had
we
filed
a
ticket
to
support
cluster
view
and
ability
to
kind
of
just
view
your
whole
cluster,
and
the
reason
was
because
we
have
the
data
and
it
it
felt
like
it's
cheap
to.
You
know,
implement
visualization.
K
L
H
I
mean
it's
sort
of
the
same
thing,
but
it
ace
for
soon
further
out.
If
you
gave
me
cluster
view,
it
would
make
me
happy
for
probably
six
months
until
my
project
grows
and
then
I'd
really
want
a
version.
That's
further
down
the
line
because,
right
now
we
don't.
I
don't
know
how
many
pods
we
have
maybe
around
100.
But
if
we
get
closer
to
500,
then
the
cluster
view
is
not
going
to
make
us
particularly
happy
and
we're
trying
to
grow
as
we're
putting
stuff
into
kubernetes.
L
Yeah,
so
a
cluster
when
I
think
for
cluster
review,
I
don't
think
we
ever
intended
to
show
all
pods
of
the
entire
cluster
it
would
have
to
be.
I
think
we
were
thinking
about
just
navigating
at
a
name
space
level,
because
a
lot
of
times
an
operator
or
someone
wants
to
see
the
other
stuff
that
is
happening
in
the
namespace.
Maybe
there's
two
like
three
applications
in
that
namespace
and
they
want
to
kind
of
overall
view
of
stuff
going
on
there.
That
was
the
idea
behind
browsing
the
cluster
yeah.
D
H
L
Yeah,
oh.
L
There
is
there's
kind
of
one
reason
we
haven't
been
kind
of
pursuing.
This
is
because
there's
there's
a
lot
of
other
observability
modeling
tools
that
are
are
doing
that,
I
think,
with
argosy
does
offer
a
little
bit
of
its
own
perspective.
I
guess
because
it
has
things
like
health
checks,
right
and
and
yeah.
I
think
we're
trying
to
figure
out
what
is
the
right
balance
to
leave.
L
I
mean
let
those
other
tools,
observability
tools
like
do
their
thing.
I
don't
feel
like
we
need
to
try
to
solve
the
problems
that
they're
solving,
but
still
provide
like
a
useful
view
that
we
know
that
you
know
application,
maintainers
or
or
maybe
even
cluster
operators
would
want.
L
So
at
least
for
our
teams
like
the
cluster
operators,
they
might
not
care
about
applications,
and
so
they
they
use
their
own
stuff
to
monitor
the
platform
team
uses
their
own
self-demanded
nodes,
whereas
our
users,
the
developer
service
teams,
they
care
about
their
application
that
they
also
care
about
like
a
name
sp,
because
their
tenancy
is
like
the
name
space
and
that's
kind
of
what
we
were
thinking
for
for
this.
L
I
think
cluster
view
is
maybe
I
would
I
would
call
it
cluster
browser
instead
of
the
name
customer
view,
cluster
view
kind
of
indicates,
it's
viewing
the
whole
cluster.
J
Yeah,
I
think
it's
also,
I
mean
so
we
have.
We
have
the
arbuck
stuff
in
our
city
right
and
I
mean
it's
it's
there
for
a
reason.
So
the
application
controller
basically
has
super
super
user
privileges
for
the
cluster.
But
it's
it's
not
inherited
to
the
users
right.
So.
L
Oh
yeah,
that
that
was
the
other
issues
that
we
would
have
to
figure
out,
whether
it's
the
right,
our
back.
So
so
that's
another
challenge
for
providing
a
view
like
this.
That
was
another
thing
that
kept
us.
J
I
mean,
I
think
it's
so
if
you,
if
you're
looking
at
it
from
from
the
application-centric
view
right,
so
it's
it's
valuable
to
see
when
you
look
at
your
application
through
the
ui
to
see
how
much
pressure
actually
is
on
the
nodes
that
your
application
is
running
in
so,
but
I
I
think
it
would
not
be
a
good
idea
to
to
show
in
that
view
who's
the
the
I
miss
the
word
the
delinquent
there.
J
L
L
J
A
Okay,
so
moving
on
from
that
remington,
our
next
issue
is
our
go
cd,
ui
integration
with
argo,
rollout.
G
Yeah
so
jesse
opened
an
issue
I
think
last
week
targeting
disintegration
for
1.10,
so
it's
coming
up.
Would
it
be
okay?
If
I
shared
my
screen
real
quick.
G
So
I
mocked
up
something
for
how
I
think
it
could
look
so
on
the
left.
We
have
the
current
argo
rollout
cubes
ttl
plugin,
so
that
has
you
know,
data
about
the
rollout
and
then
on
the
right.
I
have
what
I
think
it
could
look
like
so
yeah.
G
Any
thoughts
would
be
appreciated
on
the
left
is
just
a
really
small
update
to
the
node
view,
so
just
adding
a
new
tag
that
indicates
what
type
of
rollout
it
is,
but
then
on
the
right
would
be
the
info
panel
that
pops
up
when
you
dive
into
that
rollout.
So.
H
H
G
L
I'm
actually
I'm
trying
to
absorb
the
panel
right
now.
D
That's
just
if
we
kind
of
for
powers,
I
think
we
transitioned,
so
we
went
I'm
just
trying
to
figure
out
like
how
music
is
going
so
first.
I
think
we
transitioned
through
these
general
issues,
and
then
I
saw
origin.
You
took
notes
so
and
now
I
think
we
we're
going
to
talk
about
kind
of
two.
We
basically
basically
moved
into
a
big
feature,
cluster
review
and
and
then
concluded.
A
D
Or
I
mean
I'm
not,
maybe
let's
not
try
to
come
up
with
this
reflection
right
now,
but
I
just
maybe
that
is.
We
should
post
this,
you
know
notes
and
into
a
document
and
try
to
convert
them
into
issues
yeah.
I
have
a
feeling
this
is
actionable
and
what
we're
discussing
now
I
mean
at
least
last
review.
It's
like
a
long
discussion.
We
won't
be
able
to
come
up
this
conclusion
in
that
meeting
for
sure,
yeah
and
and
enroll
out.
D
L
I
think
for
the
rollout
thing,
I
think
we
should
actually
get
first
get
everyone
on
the
same
page
on
the
the
desire
for
the
the
feature
and
then
what
it's
trying
to
solve
and
then
I
I
want
to
make
sure,
there's
no
kind
of
objections
and
introducing
this
type
of
integration
into
argo,
cd,
but
I'll.
Let's
step
back
and
I'll
describe
the
you
know
what
is
the
purpose.
L
So,
basically,
we
have
a
lot
of
users
who
are
using
both
argo
cd
and
argo
rollouts,
and
a
popular
request
is
some
type
of
better
visualization
of
what's
going
on
with
the
rollout
and
the
cli
actually
is
more
powerful.
In
that
regard,
like
you
can
tell
a
lot
more
information
using
the
argo
rollouts,
keep
steel
plug-in
that
then
you
can
by
looking
at
an
application
that
has
a
roll-up
in
argo
cd,
and
so
the
integration
that
we
or
I
like
is
that
in
the
argo
cd.
L
If
you
click
on
the
rollout,
we
would
have
a
additional
tab
or
a
pane
that
had
rollout
specific
information
so,
and
I
think
remington
is
showing
kind
of
like
his
interpretation
of
of
what
the
cli
is
able
to
show,
but
in
in
the
argo
cd
ui.
So
it's
kind
of
like
getting
parody
of
what
the
cli
is
showing.
L
So
that's
what
this
feature
is
about.
It's
it's!
It's
for
the
the
rollout
users
who
are
also
using
argo
roles
in
argo,
cd.
H
Can
I
ask
some
questions
about
this
visualization
yeah,
of
course,
so
having
not
too
recently
or
actually
fairly
recently
read
on
the
way
jenkins's
ui
works.
The
nesting
here
is
really
weird.
Am
I
right
and
understanding
that
you
have
a
revision
for
and
then
you
have
a
canary
demo,
which
in
turn
has
two
children,
the
success
rate
and
then
success
rate
dot,
one
which
in
turn
has
the
children
that
we're
seeing.
G
H
H
Yeah,
so
on
the
bright
side,
they're
visual
level.
From
my
perspective,
because
I
don't
I'm
not
familiar
with
the
features
yet
we're
looking
to
use
rollouts,
probably
in
the
summer,
it's
kind
of
weird,
because,
yes,
the
icons
are
sort
of
different,
but
they
are
sort
of
similar.
Like
you
have
some
check
marks
under
canary
demo,
which
are
presumably
pods,
and
then
you
have
an
x1
and
a
check
11..
L
I
can
probably
shed
some
some
white
so
with
a
rollout.
Every
update
results
in
a
new
revision,
and
so
the
what
this
is
trying
to
do
is
is,
I
guess,
group,
all
of
the
related
stuff
that
is
related
to
that
revision,
so
that
a
revision
will
have
a
replica
set
and
replica
has
parts.
Obviously,
and
revision
will
also
may
have
like
a
analysis
that
happens
with
it.
Actually,
maybe
this
is
more
than
one.
L
This
is
showing
two
attempts,
which
might
be
also
confusing
right
now,
because
this
is
a
bit
of
a
more,
I
guess,
advanced
or
example,
and
then
at
the
bottom
we
have
the
the
amount
of
successful
measurements
that
have
been
taken
versus
the
failed
measurements.
L
So
it's
this
is
actually
showing.
Now
that
I
I
am
seeing
it.
I
understand
that,
but
it
did
take
me
some
time
to
translate,
and
I
have
also
have
context
too
so.
L
Yeah,
I
think,
there's
there's
some
things
that
I
I
for
analysis
specifically
that
I
couldn't
do
in
the
cli
when
I
was
doing
the
cli
version,
but
I
had
envisioned
that
what
would
be
cool
to
do
in
the
ui,
for
example,
we
have
measurements
and
we
also
have
timestamps
of
when
those
measurements
were
taken
and
so
actually
the
ui.
L
Could
you
know
plot
along
things
like
okay,
like
green
dots
and
red
dots,
when
measurements
were
taken
along
a
dotted
line,
and
I
think
there's
some
more
powerful
things
we
can
do
in
the
ui
for
for
rollouts,
then
this
what
the
cli
was
able
to
do
so
I
like.
L
I
think
this
is
a
good
start,
but
I
think
there's
some
more
interesting
widgets.
I
think
we
can
do.
D
Yeah,
I
think
we
never
discussed
it,
but
I
feel
like
it's
rollouts
and
argo
cj
getting
closer
and
closer
and
it
was
like
the
inevitable
one
day.
We
would
add.
D
You
know
knowledge
of
fallouts
into
our
city
ui
at
least,
and
I
think
maybe
this
way
we
never
discuss
it.
I
want
to
know
you
know
what
others
think
about
it
like.
I
think
schrodinger
might
have
opinion.
D
You
know
in
general,
like
argo
cd
is
going
to
become
kind
of
our
goal
out
somewhere
and
if
we
add
ui
it
will.
I
think
there
will
be
even
dependencies
between
versions
like
cargo.
You
know,
basically,
cd
at
this
ui
would
work
only
with
some
version
of
rollout
and
and
maybe
won't
support.
Another
older
version.
B
I
think
that
is
okay
in
general,
I
would
say
I
think,
as
long
as
we're
defining
what
those
comp,
what
the
compatibility
metrics
is.
That's
fine,
because
it's
a
well-known
fact
that
there
is
a
lot
of
there
are
a
lot
of
users
of
argo
cd
who
use
argo
rollouts
as
well
and
with
application
cells.
We
are
potentially
saying
that,
and
with
some
other
ecosystem
projects
that
we
can
we
see
coming
up,
we
will
see
a
lot
of
dependencies
on
dargo
city
ui
for
argo
rollouts
to
function
properly.
D
B
L
I
would
say:
it'd
be
it'd,
be
good
if
we
could
design
this
in
such
a
way
that
it
was,
you
know
in
the
future,
more
extensible
right.
So
if,
if
some
crd,
you
know
not
an
argo
project,
crd
were
to
have
a
need
like
a
a
popular
one
that
needed
some
special
visualization
that
we
could
do.
Then
if
it
was
extensible,
maybe
people
could
drop
in
their
own.
L
A
Okay,
so
if
there's
no
other,
if
there's
nothing
else
to
talk
about
on
that
topic,
we
have
about
four
more
minutes
left.
So
I
guess
the
last
thing
that
I
think
we
should
discuss
is
adding
ability
for
users
to
update
passwords
through
the
ui.
A
So
this
is
discussed
in
this
issue
a
little
bit.
I'd
ask
jared
to
be
on
this
call.
I
don't
think
he
is
though,
but
this
was
we
were
talking
about
this
the
other
day.
I
believe
I
think
dewan
was
asking
about
it,
but
is
there
any
intention
to
do
this
feature.
G
A
pr
has
actually
been
opened
already.
I
think
jared
opened
it.
I
have
been
meaning
to
look.
He
made
some
changes
and
I've
been
meaning
to
look
at
it,
but
I'll
get
that
done
today.
A
Okay,
I
didn't
see
that
it's
not
linked
so
okay,
but
thank
you.
Okay,
so
should
we
try
to
do
another
one,
or
is
this
good.
L
The
next
one:
what's
the
next
request.
A
The
next
one
is
pod
web
shell
and
argo
ui.
This
issue
was
opened
in
december,
so
it's
a
little
bit
old,
but
basically
it
would
be
like
a
terminal
in
the
for
the
positive.
Oh.
A
I
L
It's
it's
like.
It's
definitely
possible.
In
fact,
we
actually
did
it
in
a
v1
version
of
fargo
and
then
we
intended
it
to
do
it
in
in
argos
cd.
But
then
we,
I
don't
think
we
ever.
You
know
I
mean
we,
we
just
never
prioritized
it.
There's
there's
definitely
a
rbac
a
new
or
back.
That
would
need
it
for
this,
because
exacting
into
containers
is
the
big
deal.
L
B
B
D
K
I
know
I
just
added
it
yeah
I
was
looking
at
this
recently.
The
current
layout
of
nodes
could
definitely
be
improved.
I
attached
two
screen
shots
to
that
issue.
If
you
want
to
take
a
look
at
that
before
and
after
so
yeah
fixing,
this
would
definitely
make
the
audio
cd
views
more
polished
and
will
add
to
the
overall
fit
and
finish
of
argo
cd
yeah.
I
need
the
ux
design
feedback.
K
Should
we
put
them
all
in
one
column
and
how
about
colors
of
notes
should
we
color,
like
pods,
depicted
in
the
second
screenshot
there?
Should
we
color
them
differently.
L
Oh,
I
actually
have
a
related
issue
to
this
can
so
so.
Actually
I
I
I
was
proposing
to
the
into
folks
yes
or
this
week
that
we
shouldn't
even
show
individual
pods
at
this
level,
because
most
of
the
time,
people
don't
the
pods
are
all
part
of
something
higher.
That
is,
is
grouping
them
somehow.
So
it's
not
very
useful
in
a
screenshot
that
I
posted
in
the
the
other.
L
One
is
an
example
of
an
app
that
just
had
like
a
couple
dozen
parts,
and
then
it
was
as
bad
as
a
a
large
tree
view
for
application.
We
were
just
scrolling
and
scrolling
and
scrolling,
so
it
looks
like
we
have
a
lot
of
plus
ones
on
yeah
that
don't
show
pods.
So
the
improvement
that
I'd
like
to
see
is
we.
We
just
show
something
like
what
like
a
workload.
This
is
actually
something
that
kiali
the
the
the
ui
for
isio.
L
Does
they
they
show
something
called
a
workload
for
us
for
the
the
easiest
thing
we
could
do
is
just
take
the
parent
of
the
pod
and
then
and
that's
the
thing
that
the
lines
are
are
ultimately
reaching
in
this
view,
and
that
would
be
much
more
useful
than
it's
the
the
current
form
which
is
like
fanning
out
to
to
dozens,
if
not
dozens,
little
of
pods.
L
So,
okay
with
that
said,
the
I
still
think
the
right
justification
is
needed,
so
both
I
think
the
combination
of
right
justifying
the
like
the
termination,
node
and
grouping
of
pods
into
whatever
its
parent
is.
The
combination
of
those
things
would
make
this
much
more
usable.
K
Yeah,
I'm
also
talking
about
the
the
tree
too.
D
Yeah,
I
think
it's.
This
is
because
we
don't
even
we're
not
trying
to
lay
out
them
manually.
We
just
you
know
the
layout
is
provided
by
just
a
library,
so
it
has
no
information
about
what
the
nodes
mean.
It
just
try
to.
I
think
layout
them
as
compact
as
possible.
Yeah,
so
yeah.
D
We,
the
only
thing
we
could
do.
We
can,
I
mean
we
control
how
nodes
are
rendered
and
we
can
influence.
Basically,
how
layout
is
happening.
We
could
we
could
inject
nodes
and
just
do
not
render
them
so
the
dagger,
the
framework,
it
would
think
that
node
exists,
and
this
way
you
can
force
you
know
to
move
like
basically
to
force
services
to
be
on
the
same
level
and
ingress
at
the
higher
level
yeah,
and
this
is
the
possibility,
so
I
think
it's
doable
for
me.
D
H
Having
recently
run
into
this,
where
pods
were
like
five
different
columns
in
the
review,
it's
definitely
frustrating.
It
came
up
from
one
of
the
other
issues.
I
filed
people
like
oh,
but
you
can
just
do
this
like.
Actually,
no,
you
can
see
that
it
doesn't
always
work
that
way.
So
yeah
I'd
be
thumbs
up
for
forcing
things
into
columns
by
with
dummy
nodes,
invisible
yeah.
L
Yeah
alex,
I
think
we
better
wrap
up.
We
have
another,
this
review
meeting
for
the
august
city
security,
stuff
happening.
A
That's
okay
and
any
issues
that
we
didn't
cover
this
time.
This
ux
meeting
or
ui
ux
meeting
focus
will
happen
every
third
week
during
this
time.