►
From YouTube: Argo Contributor Experience Office Hour 15th Apr 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).
A
Okay,
hi
everyone
again
good
morning
good
evening,
I'm
going
to
start
from
sharing
my
screen
and
I
will
show
agenda.
But
today,
if
I'm
not
mistaken,
we're
supposed
to
focus
on
ui
ux
topics-
and
I
see
I
saw
one.
B
From
red
hat,
they
looked
at
the
feedback
that
we
had
received
and
they
came
back
with
some
questions
that
they
had
regarding
them.
I
can
take
them
here,
one
second
I'll
post
them
right
here.
Maybe
we
can
discuss
them
here,
okay,
so
this
is
what
they
kind
of
came
up
with
as
stuff
that
they
saw
happening.
So
they
saw
that
our
back
came
up
a
lot
so
who's.
Who
are
we
trying
to
keep
out
of
certain
areas
and
for
what
purposes
yeah?
A
And
I
I
can
take
first
one
I
can
answer
erbach
and
I
also
recall
that
it
was
mentioned
multiple
times
in
you
know
in
feedback.
So
there
is
a
reason
to
have
our
bike.
We
want
to
protect,
so
argo
cd
is
supposed
to
be
multi-tenant,
so
we
have
users
not
supposed
to.
A
You,
know
be
admins
and
should
be
restricted
in
what
they
can
do
and
so
far
we
make
zero
effort
to
reflect
our
back
instinctions
in
ui.
So
basically,
every
possible
button
is
shown
to
everyone
and
that's
a
known
known
issue
and
I
feel
like
we
just
never
prioritized
it
and
now
next
blocker
is
we
don't
really
know
what
is
the
best
way
to
implement
it,
and
I
you
know
one
common
mistake
is
to
just
hide
buttons
for
people
who
are
not
supposed
to
see
them.
A
I
know
it's
maybe
a
bad
idea.
So
basically
you
know
it
might
confuse
users
even
more,
and
I
guess
we
need
some
some
guidance
on
what
it
can,
how
it
can
be
done.
B
Better,
okay,
sarah
jane
arbo,
do
you
have
clarification
on
that?
Do
you
have
any
more
questions
regarding
this
point.
A
I
guess
the
question
is:
is
there
any?
Is
there
a
guideline
about
how
you
know
how
how
users
should
be
informed
that
action
is
forbidden
for
him
or
not
forbidden
or
is
it?
You
know
like
case
by
case,
and
there
is
no
single
firm.
C
I
don't
think
there's
a
one-size-fits-all
rule.
Unfortunately,
it's
not
it's
not
quite
that
simple,
and
sometimes
you
want
them
to
see
the
button,
maybe
with
a
tool
tip
or
something
so
they
understand
or
learn
about
what
it
is
they're
not
seeing.
Maybe
it's
something
they
can
graduate
into
or
get
you
know,
get
access
eventually.
Sometimes
you
really
do
not
want
them
to
see
the
button
or
see
the
link
or
whatever,
because
they
really
have
no
business
ever
in
the
life
cycle
of
their
usage
ever
using
that
link
or
that
button
or
whatever.
C
So
I
think
you
know
you
kind
of
have
to
think
through
your
goals
for
all
the
things
that
might
be
shown
or
hidden
and
think
through
what
they
might
do
with
that
now
and
in
the
future.
A
Okay-
and
I
have
a
feeling-
we
kind
of
we
have
cases
where
we
might
want
to
hide
a
button,
for
example,
no
not
means
not
supposed
to
even
know
there
is.
You
know
there
is
way
to
customize
arc
ocd,
and
you
know
we
can
kind
of
just
hide
links
that
navigates
to
section
two
for
non-admins
and
at
the
same
time
you
know
what
about
other
users
who
so
the
the
most
not
problematic
the
most
the
piece
of
ui
that
needs
this
polishing.
The
most
is
rbc
application
details
page.
A
This
is
where
most
of
your
elements
are
located,
and
in
this
case
I
feel,
like
you
know,
the
same
same
type
of
users,
use
that
page
and
either
any
kind
of
rule
of
thumb.
Like
do
you
think
it's
okay
to
just
maybe
disable
the
button.
If
users
don't
have
access
to
to
the
action
of
that
button
and
just
have
a
tooltip.
That
explains
that
sorry,
you
you
need
to
you
need
this,
and
these
permissions.
C
That
could
work
it.
It
might
put
some
some
burden
on
the
admin
or
whoever
controls
it,
because
if
they
see
that
they
might
say
oh
well,
this
is
just
something
excuse
me.
I
could
ask
for
excuse
me.
I
could
just
request
permission
for
it.
Maybe
that
is
the
case
or
maybe
not
so
that
could
work
in
in
that.
If
that
is
the
case,
if
it's
something
that
they
really
truly
are
not
likely
to
ever
have
access
to.
D
C
A
I
I
understood
yeah,
so
basically
we
should
look
out
for
you
know
for
buttons.
It's
yeah.
I
might
be
wrong,
but
my
feeling
is
that
most
of
the
buttons
on
the
application
details
page
are
going
to
be.
You
know,
user
may
or
may
not
have
access
or
may
get
access,
eventually,
maybe
one
of
two
buttons
that
are
strictly
related
to
admins,
but
I
doubt
it
but
yeah.
So
it
will
simplify
implementation.
A
lot.
A
If
we
just
have
this
rule
of
thumb
and
basically
you
know,
go
for
disabling
plaster
tooltip
for
most
of
them,
and
if
there
is
a
question
then
we
can
just
you
know.
C
You
know
the
other
thing
too,
is.
If
somebody
really
is
interested
in
whatever
functionality
would
be
provided
by
that
button,
if
even
if
they
don't
see
the
button
they're
likely
to
google
for
it
right,
they're
going
to
see,
does
argo
cd,
do
this
thing
and
they'll
find
documentation
and
realize
that
it
is
possible?
So
it's
not
like
you
know
if
they're
really
really
interested
in
doing
whatever
that
thing
is
they'll
find
out,
you
know
whether
it
exists
and
try
to
work
around
it.
A
A
E
A
Kind
of
it's,
not
okay,
it's
realizing
turbuc,
so
in
most
cases
user
needs
to
know
needs
to
be
a
part
of
some
group
and
that
user.
This
is
what
user
needs
wants
to
know
like,
for
example,
user
is
trying
to
sync
application
and
realize
he
doesn't
have
permission
the
next
question
he
has
he
or
she
has
okay,
which
group
should
I
be
in
to
get
their
permission
and
yeah?
So
I
guess
maybe,
if
you
taking
notes,
maybe
I
feel
like
we
should
do
something
about
that
too.
A
Yes,
if
you
navigate
so
we
have
user
profile,
page
and
user
can
patron
see
list
of
groups
he
belongs
to,
and
we
basically
created
that
page.
For
that
reason,
so
every
time
we
get
a
question
from
a
user,
we
ask
him
to
go
to
that
page
and
send
us
a
list
of
groups,
and
then
we
tell
them.
Okay,
see
you
have
to
be
in
that
group
and
you
and
this
these
are
your
groups.
Talk
to
your
admin
to
ask.
You
know,
ask
you
ask
him
to
add
you
to
a
required
group.
A
A
It,
as
part
of
you
know
several:
it
will
help.
E
A
C
A
Programmatically
you
know
like
so
the
thing
is:
cargo
city
admin
doesn't
really
know
how
to
I
mean
rtc
admin
knows,
but
he
cannot
give
permission
so
argent,
arrogancy,
admins,
typically
configure
our
back
rules
and
they're.
Just
saying
users
of
that
group
can
do
that,
but
they
don't
control
who
belongs
to
that
group
and
that
information
is
somewhere
in.
You
know
in
like
maybe
github
settings
or
lab
settings,
and
so
you
can
admin
can
just
tell
go
talk
to.
A
And
that
it's
really
easy
to
get
information
about
which
group
you
have
to
be
in
to
get
access
to
that
to
the
action,
but
it's
this
is
that
support
burden
users
keep
asking
what
do
I
do?
We
try
to
document
it,
but
we
still
get
this
question
all
the
time.
B
Are
we
good
on
this
question?
Should
we
move
on
okay.
G
G
Sometimes,
maybe
the
resources
are
either
not
available
or
they
they're
only
available
to
certain
or
they're
only
editable,
so
we
even
have
like
would
recommend.
Maybe
like
boilerplate
like
when
there's
nothing
there
or
I
mean
it's
just
stuff.
We
run
again
run
up
against
where
we
call
it
like.
It
would
be
like
an
empty,
an
empty
message,
or
so
you
may
start
to
run
into
those
things
as
well
or
that
may
come
up.
It
happened.
A
I
spoke
with
several
users.
I
think
it
happened
less
frequently
desirable
cd
because
I
feel,
like
typically
people
tend
to
open
read-only
access
to
everyone,
because
it's
okay
to
let
your
team
members
to
view
infrastructure
and
usually
argo
cd
is
behind
firewall.
But
in
some
cases
I
spoke
with
few
users
and
they
complained
that
they
navigate
to
rbc
ui
and
then
see
nothing
and
it's
due
to
our
back.
So
our
back
is
right.
Now.
C
A
Works
this
way
it
kind
of
it's
like
a
hidden
filter
when
every
time
you
open
list
page
and
then
list
api
will
filter
out
everything
you
don't
have
access
to
yeah.
So.
A
And
we
do
have
generic
kind
of
empty
state
widgets,
which
shows
you
a
little
icon,
an
explanation
that
hey
you
don't
see
anything
and
it
may
be
because
of
filter,
so
try
to
either
reset
filter.
It
doesn't
talk
about
our
bug.
Maybe
we
can
simply
add
this.
You
know
one
more
hint
and
explain
that
do
a
part
of
groups,
and
probably
none
of
those
groups
has
access
to
an
application.
A
G
I
mean
the
only
thing
is
if,
if
it's
like,
if
it's
like
an
edge
case,
our
back
this
is
nice
and
clean
and
simple.
So
you
don't
want
to
turn
it.
You
know
you
want
to
make
sure
that,
like
the
you
know,
the
most
the
most
likely
one
is
what's
what
we're
instructing
them
to
kind
of
look
for
is
to
to
fix
the
the
empty
state
that
that's
my
only
concern
about
lumping
any
everything
in.
A
Yeah,
so
we
will
need
to
think
about
how
to
distinguish
our
bug
versus
just
normal
applications
available
right
now.
This
filter
is
kind
of
trying
to
be
smart.
If
you,
so
we
won't
show
clear
filters
unless
you
specify
a
filter,
yeah
and
then
for
arbuck
at
least
we
I
mean.
I
would
just
take
a
note
that
it's
good
to
think
about
the
solution.
Maybe
we
could
have
an
api
that
explicitly
says
we
hide
something
from
you
because
of
our
bug
and
then
you,
I
will
have
a
clear.
A
B
A
I
I
can't
tell
what
I
know
about
that,
so
I
I
suspect
that
people
are
talking
about
cluster
observability
kind
of
it's
a
feature
that
we
talked
about
for
a
long
time.
Basically,
arco
cd,
watches
the
whole
cluster,
no
matter
how
you
know
how
many
namespaces
in
the
cluster
you
manage
organic.
You
have
to
get
all
the
information
about
the
cluster
and
that's
why
we
kind
of
keep
hearing
that
user.
Saying.
A
A
It
should
be
almost
the
same
as
application
list
page,
but
except
instead
of
applications
you
would
see
namespaces
and
then
you
can
click
on
the
namespace
and
basically
see
all
the
resources
in
in
that
namespace
and
so
on
and
so
forth.
So
and
I
feel
like
I'm
not
sure
if
it's
purely
a
ux
question.
Basically
we
don't,
we
have
not
done
it
yet,
because
it's
it's
like
really
diverging.
A
Basically,
it's
argosy
was
focused
on
is
focused
on
github's
use
case
100,
plus
we're
trying
to
show
kind
of
useful
information
just
along
the
way.
You
know,
because
we
monitor
all
application
resources.
It
makes
sense
to
show
everything
related
to
to
the
application
resources,
like
you
know,
the
div
state
and
so
on
and
so
forth,
so
and
namespaces,
even
though
we
collected
information,
but
it's
really
like
it's.
Basically,
it
would
transform
argo
cd
into
mostly
monitoring
tool,
plus
github's
features
and
yeah.
A
C
Yeah,
I
mean,
I
think
there
was
only
one
person
I
saw
who
mentioned
it
specifically
in
that
thread
on
github
about
the
the
feedback.
But
that
is
something
that
I
have
heard
from
some
folks.
I've
talked
to
in
the
context
of
doing
open
shift
research
is
that
they
don't
necessarily
think
in
the
cluster
view.
They
are
much
more
focused
on
on
the
nodes
and
the
pods
like
that's
where
the
majority
of
their
their
focus
is
so
they're
kind
of
looking
more
at.
C
How
can
I
see
across
everything,
but
at
that
level,
not
like
you
know,
at
a
cluster
level,
but
more
down
in
the
weeds
at
the
kind
of
the
node
level?
So
I
guess
I
was
just
curious
if
that's
something
that
you
guys
have
heard
too
or
if
this
was
just
kind
of
a
unique.
H
A
Yeah,
I
feel
like
I'm
kind
of
describing
my
experience
mostly,
but
I'm
not
sure
if
others
do
the
same,
but
I
because
I
use
argo
cd
ui
often
I
kind
of
get
used
to
it
and
that's
why
sometimes,
if
I
just
do
something
in
kubernetes,
I
want
to
see
it
in
argo,
cdui
and
right
now.
Only
way
to
see
it
in
ui
is
to
try
to
put
it
into
git
repo,
and
then
you
know
you
I
will
visualize
it.
A
So
it's
kind
of
I
see
why
people
might
want
to
just
use
argo
cd
guide
just
to
see
what's
in
the
cluster,
not
necessarily
managed
by
argo
cd
and
my
suspicious.
Is
that
what
you
know?
That's
what
people
are
talking
about
here
and
you
know
if
they,
if
someone
is
and
then
you
might
have
different
users
like
cluster
admins,
they
would
be
interested
to
group
it
by
node
and
then
just
see.
A
What's
in
my
know,
like
what
exactly
is
running
on
the
node
and
here
and
then
they
might
be
interested
in
kind
of
finding
resources
that
created
port
for
that
node
and
so
on.
C
A
But
we
I
feel,
like
we've,
already
slept,
we
already
collected
to
show
that
so
it's
a
matter
of
can
I
feel
like
it's
a
matter
of
commitment
like
if
have
interest
from
contributors,
and
you
know
people
kind
of
already
so
ready
to
invest
time.
I
I
just
know
that
it's
like
never
in
this.
If
we
go
for
it,
it
will
never
stop.
We
will
first,
we
will
get.
A
B
Okay,
so
should
we
move
on
to
the
next
question.
B
Okay,
so
scale,
only
one
person
mentions
how
many
apps
they're
dealing
with,
which
is
a
hundred
plus,
and
I
I
know
that
many
vario
cd
users
have
large
amounts
of
applications.
Would
it
be
good
to
get
a
sense
of
the
scale
that
the
ui
has
to
handle
for
everything
number
of
name
spaces
pods
clusters?
How
long
names
are
generally.
C
A
Yeah
yeah,
maybe
I
will
I'm
not
sure
if
I
catch.
You
know
the
question
right,
so
I
so
some
numbers
that
we
know
it's.
I
know
that
people
have
thousands
of
applications.
It
could
be
up
to
like
the
highest
number
I
heard
is
6000
plus
arbor
city
and
ui
is
kind
of
still
alive.
I
think
it's
challenging,
but
yeah
and
application
name
can
be,
can
be
extremely
long
and
the
reason
is
rbc
application.
Names
have
to
be
unique
and
that's
why
people
come
up
with
conventions.
So
basically
it's
typically
every
name.
A
A
C
A
Accommodating
the
tool
yeah
and
the
same
story
in
application.
Okay,
I
cannot
speak
for
everyone,
intuit
users.
They
have
long
resource
names
as
well,
so
within
the.
A
Resources,
resources,
don't
have
to
be
you
know,
named,
don't
have
to
have
extremely
long
names,
but
sometimes
they
do,
and
I
I
just
observed
it
and-
and
I
feel
like
this
is
the
this
is
area
where
we
really
need
help
so
application
details
page
is
not
designed
to
visualize
large
applications,
they
have
to
be
improved
nodes,
view
or
ports
view.
The
most
recent
ports
view
was
that
an
attempt
to
kind
of
handle
one
aspect
so
pods
view
simplify
showing
application
that
have
a
lot
of
pots.
A
G
A
A
And
I
I
know
that
this
view
it's
not
just
a
flat.
You
know
the
list
of
these
resources
is
not
flipped,
it
has
grouping
internal
grouping
and
I'm
kind
of
trying
to
give
you
a
hint
in
case.
You
will,
you
know,
think
about
the
problem
later
but,
for
example,
every
resource
has
here
has
a
label
and
let
me
show
that
label
yeah,
so
you
know
it.
It
can.
C
A
A
B
A
Yes,
and
do
you
want
to
take
over
jenna,
so
you
don't
ask
me,
you
know,
I'm
like
oh
you're,
fine.
B
A
My
okay,
it's
it's
mostly
feeling
I
would
not
so
basically
most
of
users,
I
believe,
use
ui
and
you
know
most
of
humans
use
ui,
but
cli
is
still
in
it
because
cli
is
used
to.
You
know:
integrate
argo
cd
with
ci
systems,
yeah
yeah,
so
it's
kind
of
you
know
cli
is
needed,
but
it's
not
to
view
results.
A
C
A
A
My
bet
is
that
more
users
use
ui,
but
I
cannot
just
like.
I
cannot
prove
it.
C
Okay,
yeah,
I
think,
there's
plenty
of
room
for
both.
I
think
there's
gonna
be
people
who
prefer
one
to
the
other
and
that's
just
natural,
but
I
I
think
what
I'm
most
curious
about
is
what
about
it.
What
about
their
preference
makes
it
their
preference?
Is
it
speed?
Is
it
muscle
memory?
Is
it
they
can
see
things
more
clearly
in
the
ui
like
I,
you
know,
I'm
just
always
curious
about
that.
A
I
suspect
ui
is
more
popular
because
it's
kind
of
it
lets
you
reach
as
more
users,
and
so
you
know
like
hardcore
users
who
really
manage
deployments
they
already,
they
use
cli
as
well,
so
they
learn
to
install
it,
configure
connect
to
argo
cd
and
so
they
benefit
from
both,
but
with
ui
you
can
kind
of
involve
even
more
users.
You
know
in
their
organizations.
Maybe
you
know,
managers
use
ocd
as
a
dashboard.
They
don't
care
about
voice.
They
just
you
know,
click
the
link
and.
G
One
thing
that
sometimes
we
you
know,
if
you
don't
have
parity
between
the
two
interfaces
and
the
ui
can't
have
all
the
features
you
can.
Maybe
you
cherry-pick
the
ones
that
maybe
this
more
beginner
or
less
sophisticated
user
would
need.
F
G
Really
more
the
more
complex
ones,
if
you
can't
replicate
in
the
ui
you
you
have
to
pick
so
that's
the
thing
we
think
about
yeah.
I
Okay,
yeah,
I
think
developer
type
of
user
use
cli
more.
It
gets
a
lot
quicker,
sometimes
especially
like
people
coming
from
kubernetes.
They
do
have
gmos
stuff
like
that
they
probably
prefer
ui,
but
therefore
but
most
user
ui.
On
this
thing,
it's
more
comfortable
almost
does.
J
A
Reason
is,
cli
has
access
to
local
files
and
it
can
kind
of
you
can
replicate
it
in
ui,
but
it's
just
simpler
to
download,
cli
and
run
it
because
cli
will
you
know
it
will
figure
out
what
file
should
be
used
and
uploads
it
for
you,
yeah.
A
Think
that
cli
maybe
slows
down
them
so
like
it,
algo
workflows,
started
as
cli,
only
and
then
ui
kind
of
ui
for
a
long
time
was
simply
read-only,
dashboard
and
recently
ui
kind
of
catch
up,
and
now
it
has,
I
think,
more
features
than
cla,
but
for
historical
reasons.
Basically
team
now
helps
to
maintain
this
feature.
Parity
in
cli
and
ui,
maybe
rbcd,
will
kind
of
be
in
the
same
situation.
A
B
Helpful,
okay,
I
think
that's
it
then.
A
Awesome
I
feel
like
it
was
mostly
you
know
a
questionnaire,
but
one
thing
I
think
some
of
your
notes
are
kind
of
answers
already.
I
I
like
that.
A
A
So
you
know
impact
kind
of
potentially
pick
if
we
just
hide
so
not
quite
like
disable
buttons
and
give
user
a
hint
what
he
should
do,
he
would
you
should
do
to
get
access
instead
of
right
now
these
users
have
to
go
and
ask
argo
city
administrator
just
to
get
answer
that
hey
go
to
someone
else
and
talk
to
him.
C
Yep
yep
clarity
is,
is
always
the
best
way
and
then
they
can
decide.
Maybe
they,
you
know,
read
the
you
know
the
explanation
of
why
they
don't
have
it
they're
like
oh,
I
get
that
I
get.
I
get
why
I
don't
have
that
and
then
you
know
that's
the
end
of
it,
which
saves
a
little
time
too
so
yeah.
I
think
you're
right
though
I
think
there
is
some
time
savings
here
which
should
be
cool
to
see
happen.
J
Right
so
so,
this
issue
talks
about
the
it's
bit
of
user
experience.
How
the
user
is
waiting
for
the
app
to
sync,
while
all
they
want
to
do
is
just
delete
the
app.
So
I
added
a
video
recording
as
well,
where
you
can
see
that
the
sync
is
going
on
for
a
good
three
year,
four
minutes
and
you
can't
even
abort
the
process.
A
I
have
a
simple
answer.
I
fixed
it
recently
into
the
euro,
but
maybe
if
you
can
validate
it,
but
I
run
into
the
same
situation,
I
had
an
application.
I
clicked
delete
button,
but
it
was
syncing
and
basically
I
stuck
because
ui
didn't
give
you
a
chance
to
do
anything.
In
this
case.
You
must
wait
for
sync
to
complete
and
then
delete.
A
So
I
I
made
a
change
on
on
this
page,
so
I'll
take
advantage
that
I'm
sharing
screen
right
now
so
right
now,
if
you
click
delete,
so
if
you
click
sync
and
then
maybe
delete
application
using
cli
and
in
1.8
version,
you
would
see
deleting
here
and
I
just
changed
priority
so
that
if
you're
deleting
and
thinking
at
the
same
time,
sync
will
show
up,
you
know
it
will
take
priority.
A
Like
is
does
it?
Are
we
talking
about
the
same
problem
or.
J
Yeah,
I
think,
as
long
as
the
user
can
delete
the
app
or
when
the
sync
is
taking
like
three
or
four
minutes,
if
you
have
an
option,
whether
to
terminate
or
even
if
they
could
wait
like
if
the
user
is
acknowledging.
Yes,
I'd
like
to
wait
for
the
sync
to
finish,
that
could
be
an
option
as
well,
but
yeah
I
can.
I
can
validate
it
using
2.1.
Then
comment
on
this
group
awesome.
Thank
you.
J
A
A
Okay
and
we
have
one
more
proposal:
let's
see:
okay,
sorry,
there
was
one
more
ux
topic,
the
user
input
form
enhancements
and.
K
Yeah,
so
I
am
working
in
a
ui
path
right
now
and
we
have
a
we
use,
argo
cd
to
deploy
it
onto
the
customer
premixes.
We
we
actually
deploy
ui
path,
application
suits
onto
a
customer
premises
and
we
use
argo
cd
widely
for
accepting
some
of
the
user
customers
input
in
a
form
of
parameters
and
those
are
fed
to
our
health
charts,
which
can
further
go
ahead
and
configure
ui
path,
application
onto
the
premises
right.
K
So
for
that
we
are
facing
some
of
the
challenges
and
we
want
to
see
whether
it's
possible
to
enhance
those
user
inputs,
so
right
so
a
few
of
them,
which
I
have
already
made
a
note
of
it.
K
The
first
one
is
a
tree
view
or
where
I
can
or
a
way
to
group
the
related
parameters
together
right
so
right
now
we
we
deploy
around
40
to
50
application
right
now,
once
we
have
one
and
there's
a
lot
of
fields
which
requires
parameters
so,
instead
of
showing
all
the
parameters
together
in
one
single
long
form,
we
wanted
to
see
if
the
user
can
collapse,
form
and
can
group
it
accordingly.
K
It's
specifically
it's
kind
of
yeah.
It's
a
helm
specific,
so
so
maybe
the
the
logical
grouping
that
we
could
think
of
it's
based
on
the
parameter
that
path:
that
user.
We
are
expecting
user
to
input.
K
I'm
just
giving
an
example
like
global.userinput.xyz,
then
global.userinput.abc
so
xyz
and
abc
is
a
way
to
I
can
collapse
it
under
the
same
name
like
global.
user
input,
something
like
that
right,
so
that
that
would
be
help.
That
would
be
a
great
help
for
us
to
actually
show
all
the
related
fields
in
a
proper
way.
Yeah.
I
feel
like
it's
a.
A
K
Yeah,
so,
okay,
so
other
enhancement
that
we
could
think
of.
It's
associate
a
display
name,
maybe
with
some
of
the
fields.
So
the
field
that
we
expose
it
to
the
customers
might
not
be
very
much
intuitive
for
them
to
understand,
what's
actual
meaning
behind
this
field
is
and
what
this?
What
is
the
meaning
of
this
particular
field?
K
So
we
want
to
see
if
we
can
associate
some
display
name
or
the
some
logical
name
to
that
input
field
which
can
convey
some
meaningful
yeah,
some
meaningful
thing
to
the
user,
so
that
can
be
very
easier
for
them
to
identify.
K
So
just
to
give
you
an
example,
maybe
I
want
to
accept
a
certificate,
let's
say,
let's
say
the
certificate
field,
I'm
just
giving
an
example.
So,
instead
of
saying
that
giving
the
whole
variable
name
in
which
I
am
accepting
a
certificate,
I
can
ask
user
that
this
is
a
domain
certificate
that
I
I'm
accepting
from
you.
So
just
the
display
name
would
be
like
domain
certifications
instead
of
whole
parameter.
Something
like
some
way
to
identify
that
yeah
yeah.
A
Sorry
go
ahead.
Sorry
right,
yeah,
oh
you're,
swimming
too
yeah.
I
just
wanted
to
say
that
the
challenge
here
is
that
we
don't
like
algo
has
no
database.
So
it's
hard
to
have
maintain
any
mapping,
but
we
have
we
don't
have
info
like
we
already
have
some
information
within
the
home
chart
itself.
It's
not
this
name.
It's
like
we
can
use
comments
next
to
that
field,
as
a
tooltip.
K
Okay,
so
yeah,
so
the
next
thing
I
was
coming
on
to
the
dual
depth,
so
I
can
use
comments
to
show
a
tooltip
right,
so
yeah.
A
A
We
cannot
expect
like
who
is
going
to
configure
that
mapping
between
this
display
name
or
maybe
I
can
ask
you
like
do.
K
Does
it
work
so
what
we
were
thinking
of,
maybe
in
a
hand
chart
we
will
provide
the
mapping
of
the
actual
variable
and
the
name
that
I
wanted
to
show
it
to
the
customers
or
the
user
and
whatever
the
mapping
I
provide
that
can
be
rendered
instead
of
the
actual
variable
name
over
there.
So,
for
example,
you.
A
Know
like
if
we
have,
if
we
just
keep
use
comments,
but
we
just
maybe
you
know,
use
some
convention
that
if
comment
looks
like
field
name,
comma
column,
some
value,
then
it's
a
this.
Then
it's
a
display
name
yeah.
So
I
I'm
just
curious,
like
how
many
other
users
wants
it
and
like
how
many,
how
important
that
feature?
Is
it?
A
K
We
are
fair
enough,
so
for
us,
if
we
can
show
the
tooltip
with
the
help
of
the
comments
I
think
for
now,
we
should
be
but
yeah,
because
we
are
able
to
communicate
clearly
to
the
customer
why?
What
this
field
is
for
and
for
what
users
yeah.
A
I
feel
like
yeah,
I
agree
with
both
cases
and
kind
of
tooltip.
Using
comments
is
easier
because
it's
you
know
it's
that
data
is
just
there
and
someone
just
have
to
write
a
code
and
for
display
names.
I
would
start
from
research
and
see
if
helm
community
has
something
and
then
last
resort
is
try
to
invent
something
our
own
and
introduce
like
some
way
to
some
way
to
record
this
mapping
between
names
and
destroy
names.
K
Thank
you.
The
third
thing,
the
third
topic
that
I
have
is
is
there
any
way
that
I
can
mask
a
password,
so
we
may
want
to
accept
a
connection
string
as
for
connecting
to
a
particular
database
as
a
parameter
from
a
customer,
and
we
have
a
fee.
We
got
a
feedback
from
very
from
a
customer
that
they
are
not
very
comfortable,
providing
the
connection
string
in
a
form
of
a
plain
text,
and
they
wanted
to
somehow
mask
that
input
right.
So.
A
Yeah
I
can
answer.
I
know
that
this
is
so
to
do
that
we
except
so
right
now,
argo
cd
does
know
secret
management
and
basically
it's
not
hiding
any
secrets
except
a
view
that
we
must
hide.
Basically,
we
hide
cluster
credentials
ripple
credentials
and
we
support
kubernetes
secret.
So
if
we
opt
in
and
start.
A
A
You
know:
user
management
secrets
from
the
logs
from
api
responses
from
ui.
So
what
I'm
trying
to
say?
It's
not
just
ui,
it's
a
you
know
it's
like.
If
we
do
it,
then
we
have
to
build
kind
of
full-fledged
secret
management
and
it's,
I
think,
it's
in
scope
of
argo
cd,
but
it's
a
big
commitment.
That's
why
and
it's
I
feel,
like
we
kind
of
I
have
never
seen
heard
anyone
arguing
if
it's
a
good
thing
or
not.
Everyone
thinks
it's
a
good
thing,
but
we
need
you
know.
A
So
yeah,
that's
that's
the
current
state
and
people
ask
for
imagine.
If
you
have
ability
in
argo
city
to
mark
a
helm
field
as
a
secret,
then
you
know
that
that
that
value
that
you
marked
as
a
secret,
you
can
view
it
in
logs.
You
can
view
it
in
generated.
Manifests
you
can
view
it
in
argo,
cd,
details,
page
and
yeah,
so
to
hide
that
you
kind
of
a
lot
of
work
needed.
A
Yeah,
so
it's
just,
I
think
we
know
how
to
do
it.
We
just
need
people
to
do
it
and
I
believe
we
already
have
a
ticket,
and
maybe
you
know
I
was
hoping
that
either
this
meeting
okay
next
meeting,
we
were
going
to
go
through
priorities
for
next
milestone.
I
encourage
you
to
maybe
mention
that
it's
one
more
time
and
the
goal
of
I
guess
next
meeting
will
be
to
figure
out
which
tickets
maintainers
are
going
to
work
on
during
next.
K
Thank
you,
okay,
yeah
sure.
The
next
item
that
I
have
is
we
were
thinking
of
some
way
to
provide
a
validation
for
each
and
every
field.
So
if
I
am
expect
it
means,
can
there
be
any
way
that
any
any
of
the
input
provided
by
the
customer?
We
can
validate
it
with
the
help
of.
Maybe
I'm
not
I'm
just
thinking
of
louder,
maybe
with
the
help
of
callback
functions,
or
maybe
some
regex,
I'm
I'm
not
sure
so
yeah,
but
some
way
to
provide
a
validation
to
each
field.
K
Yeah
so
again
it
will
be.
We
will
be
taking
input
from
a
user
on
the
parameters
page
so
yeah,
that's
again
the
helm
specifically.
I
feel
like
it's
almost
same
as.
K
A
A
K
A
To
make
it
easy,
can
you
maybe
create
ticket
for
that
and
explain
your
use
case,
because
I
never
thought
about
it
this
way.
So,
as
I
understand
you
think
you
have
a
home
chat
and
you
kind
of,
and
then
you
ask
use
end
users
to
fill
in
values
in
that
handshake
and
argo
cd
is
kind
of
user
interface
is
the
way
to
enter
values.
Is
it
is
right.
K
Yes,
yes,
so,
okay,
so,
okay,
just
to
give
you
a
small
idea,
what
we
do
is
we
publish
a
health
chart
to
deploy
our
various
application
on
customer
premises.
So
we
want
a
customer
to
provide
input
to
configure
those
applications,
so
maybe
like
provide
a
domain
name.
So
if
I'm,
I'm
configuring
a
cluster
kubernetes
cluster
onto
their
machine
and
I
want
to
access
it
via
the
external
domain
name.
K
So
maybe
I'll
I'll
accept
I'll
provide
a
field
where
user
can
enter
a
domain
name
associated
on
which
they
wanted
to
access
their
application
right,
the
application
that
we
are
deploying
and
that
domain
name
will
be
used
in
internally
in
our
microservices
to
do
various
jobs
right.
So
maybe
that
is
one
of
the
places
I
want.
I
might
want
to
have
a
proper
validation
check,
so
maybe
that
kind
of
thing
I
was
thinking
yeah.
A
K
Sure
yeah
I
I'll
create
a
ticket
for
that,
and
maybe
the
last
topic
that
I
have
right
now
here
is:
is
there
a
way
that
I
can
disable
a
few
of
the
buttons
that
I
want?
I
don't
want
the
customer
to
use
it.
So
if
I
I'm
just
giving
an
example
like
maybe
I
I
don't
want
the
user
to
delete
an
application,
so
maybe
a
delete
button.
This
is
now
again
outside
of
help.
If
there's
no
moderate
well,
maybe
a
delete
button
that
says
the
delete
app.
K
A
You
can
configure
you
can
use
our
bug
to
to
disable,
don't
give
them
permission
to
delete,
and
I
think,
okay
user,
as
of
now
delete
button,
still
will
be
there,
but
at
least
it
won't
work
and
we
just
discuss
a
way
to
improve
it.
So
I
guess
we
will.
You
know
in
next
version,
we'll
either
hide
delete
or
disable
delete.
A
Yeah-
and
I
guess
another
is
just
for
you,
so
you
can
help
us
right
now-
we're
working
on
better
config
management,
plugins
support,
and
I
feel,
like
the
perfect
state,
would
be
that
we
will
migrate
native
home
support
to
this
enhanced
config
management
plug-in
support,
an
idea
that
we,
you
know
users
should
be
able
to
configure
login
parameters,
and
I
I
know
that
we
didn't
mention
validation
and
display
names
in
that
plugin
support.
Yet,
and
you
know.
A
If
so,
if
you
open,
let
me
just
do
it
right
now.
A
A
Back-End
changes
and
kind
of
looking
for
and
ui
is
a
next
step,
and
I
think
I
really
appreciate
if
you
mentioned
that
for
ui
we
will
need
display
name
for
parameters.
A
A
And
any
other
topics:
people
do
you
want
to
discuss
something,
or
I
guess,
okay,
we
run
out
of
time.
So
please
add
the
topics
that
you
want
to
discuss
to
the
next
meeting.
F
A
Yes,
I
migrate.
I
know
that
we
did
it
two
weeks
ago
and
since
then
I
think
jan
was
supposed
to
be
a
moderator,
and
I
guess
he
just
stopped
doing
it
for
you
know
after
one
week
so
and
jonathan,
do
you
mind
to
be
the
next
one,
because
you
are
next
in
the
list?
I
don't
know
if
you
already
did
it
this
way.
F
A
A
I
will
double
check
this
here,
but
I
think
for
now
she
is
the
moderator
for
next
week,
thanks
for
inviting
I
everything.