►
From YouTube: Argo Contributor Experience Office Hour 12th Aug 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,
I
I'm
assuming
harry
you,
you
edit
this
right
so
yeah.
B
Large
experience,
yes,
I
I
provided
a
document,
but
I
think
once
I
think
only
this
weekend,
I
will
transfer
that
to
git
talks
as
part
of
that,
but
yeah,
that's
right.
When
you
get
a
chance
to
transfer
but
yeah,
we
can
just
review
and
then
transfer
it,
but
either.
A
Way,
it
sounds
like
first,
we
can
just
talk
about.
You
know
continue
talking
about
the
process
of
treasing
and
then
that,
and
we
were
planning
to
talk
about
my
next
release
issues
and
and
then
one
more
question
from
john
deep
about
a
feature.
I
guess
we
can
start
from
sharing.
Experience
is
passion.
A
Yes
here
yeah,
yes,
thank
you.
I
can
share
my
experience
and
I
cannot
please
and
if
you
basically,
I
feel
like
we
realized
that
it's
not
so.
This
time
we
were
trying
to,
we
were
supposed
to
do
treasuring
together,
but
basically
doesn't
have
yet
permissions
to
modify
so
it
was
challenging
for
him.
It
was.
A
C
Yeah
from
my
side,
I
think
I
did
a
bit
of
in
this
area,
so
I
tried
go
over
all
items.
I
actually
saw
this
wave
of
bug
fixes
from
last
days,
like
small
ui
box
and
so
on
during
that
latest
release
yeah.
So
I
identify
them.
But
yes,
because
I
have
permission
to
market
as
buck
or
something
else
it's.
It
was
difficult
to
me
to
help
somehow
in
this
in
in
this
area.
So
would
you
say:
was
it
next
time?
Was
it
at
least
useful
for
you
like?
C
Did
you
have
a
chance
to
learn
anything
at
all
or
it
was
like?
I,
I
think
it's
my
strategy
from
first
time
that
I
start
to
work
as
a
contributor
that
I
go
over
almost
all
issues
that
we
have
in
in
our
issues
list
and
try
to
answer
on
some
of
them
try
to
reproduce
and
so
on.
So
yes,
it's
one
of
the
strategies
that
I
decide
to
use
for
understands
argo
city,
better,
okay,
so
at
least
it
yeah
at
least.
A
D
B
It
once
we
get
on
it,
so
do
we
actually
discuss
about
tricycles
of
one
week
or
two
weeks
actually.
B
B
Experience
from
pasha
and
alex
with
our
like
primary
should
be
at
least
a
member
so
that
they
have
access
to
ad
labels
or
maybe
move
in
close
it.
So
all
those
kind
of
permissions
primary
needs
to
have
so
we
need
at
least
a
member
to
be
primary
and
secondary
can
be
everyone
who
are
interested
and
wants
to
learn
and
contribute.
So
they
can
be
anyone.
B
So
that's
what
I
have
created
and
again,
like
the
topics
discussed,
we
can
again
we
have
the
contributor
meeting
where
you
can
post
in
there
and
issues
to
try
us.
So
we
have
like
three
github
issue
links
again.
We
can
discuss
on
how,
to
I
mean,
like
correctly,
label
image,
updated
notifications,
but
these
are
the
three
git
repos
which
are
relevant
for
arbo
cd,
which
needs
to
be
looked
at,
and
we
have
already
have
proposal
for
how
to
try
as
a
bugs.
B
A
I
just
wanted
to.
We
had
short
discussion
about
this
documentaries
hurry
and
basically,
I
think
we
just
wanted
to
add
some
clarity
like
if
we
have
primary
and
secondary
and
secondary,
doesn't
really
doesn't
really
have
permission
to
change
label
or
admit
milestone,
but
still
wants
to
participate.
A
We
just
wanted
to
propose
to
use
comments,
basically
just
give
a
hint
to
primary
that
you
would
add.
You
would
add
this
issue
to
milestone,
or
you
might
just
say
it's
a
bug,
but
it's
not
critical.
That's
why
let
it
be.
You
know
we'll
pick
it
up
when
time
comes,
and
then
you
can
attach
labels
and
basically,
when
we
spoke
about
it,
I
remember
that
we
already
had
a
document
that
describes
all
the
labels.
A
Basically,
a
quick
summary
that
during
triaging
the
result
is
a
label
and
milestone
either
edit,
like
I
guess,
yeah,
we
need
to
add
labels,
no
matter
what
and
then
basically
prioritize
it
by
adding
two
milestone
or
not.
And,
secondly,
you
can
just
use
comments
and
primary
actually
will
perform.
You
know
the
mechanical
thing
moved
to
the
level
yeah
okay
and
then
we
didn't
talk
about
it,
but
basically
we
so
far.
We
completely
ignore
two
other
projects
that
exist
like
we
have
fargo
notifications
and
image.
A
Updater
we've
advertised
them
as
argo
cd
features,
but
kind
of
it's
like
young
handle
100
of
issues
in
argo,
cd
image,
updater
project,
and
we
have
like
a
hidden
member,
ryota
sakamoto
who
works
on
argos
identifications
and
he's
a
solo
supporter
of
that
project
and
I've
yeah.
I
guess
we're
proposing
that
we
should
start
looking
into
these
projects
too,
and
they
both
projects
are
supposed
to
eventually
make
it
into
argo
cd,
at
least
with.
A
I
know
that
there
was
already
a
proposal
to
do
it
for
image
updater
and
we
basically
image
argus
identifications
kind
of
already
have
they
are
there.
We
already
merged
notifications
into
rollout,
so
it's
algorithms
basically
has
that
functionality
built
in,
and
I
guess
we're
going
to
do
same
for
adverse
identifications
that
just
to
highlight
the
importance.
It's
like
it's
a
it's
part
of
project
already
and
we
should
be
looking
at
issues.
A
B
What
about
gitop's
engine
should
we
be
watching
that
as
well.
A
It's
just
github
symptom
typically
gets
very
technical
issues.
It's
like
requires
less
discussions,
because
engine
is
a
library
and
typically
from
use
case
perspective.
It
starts
in
argo,
cd,
repo
and
then
once
we
realize
that
something
is
missing
in
engine,
but
I
guess
you're
right.
I
just
know
it
will
be
more
difficult
to
make
meaningful
decisions
about
gitob's
engine
proposals
because,
like
it
requires
you
to
have
context,
but
yes,.
A
A
Do
you
mind
if
I
edit
and
then
we
can
decide
if,
like
we
can
collect
feedback
and
people
can
say?
Okay,
it
was
meaningless.
It's
like
or
yeah
git
ops
engine.
Typically,
it
doesn't
get
issue
issues
it
get
prs
because
we
we
will
find
something
that
it's
not
working
in
cd
and
then
we
would
create
a
pull
request.
B
Do
do
we
do
we
want
to
link
that
like
do
you
yeah,
so
I
think
once
everyone
agrees,
we
can
just
transfer
this
to
github
dogs
like
a
proposal,
and
europe
can
start
to
need
it.
I
don't
think
another
document
will
make
sense.
Just.
B
All
right,
so
the
tricycle
starts
from
friday
to
thursday.
A
We
should
discuss
about
that
as
well.
I
think
we
should
yeah
discuss
like
well.
We
still
on
the
topic.
Basically,
we
still
don't
have.
I
think
we
were
hoping
to
get
list
of
volunteers
offline.
We
still
have
abhishek
and
then
it
will
be
again
pushing
me.
A
We
need
more
people,
I
guess
maybe
like
call
to
everyone
in
the.
A
Guess
that
means
you,
okay
and
I
thought
you
have
access.
A
F
A
A
A
Yes,
I
was
assuming
that
members
can
do
it
and
I
I
guess
we
will
need
to
change
github
settings
to
enable
it.
H
A
A
H
The
other
better
problem
we
had
earlier
was
that
we
agreed
that
members
should
be
able
to
moderate
just
github
discussions,
but
they
also
don't
have
that
privilege
right
now.
So
I
think
we
should
create
like
a
member,
a
default
member.
Well
such
that
any
member
of
the
argo
or
can
do
these
activities.
D
Yeah
yawn
was
asking
the
same
question
on
the
argo
maintainers
slack
channel
on
cncf.
It
does
seem
to
be
a
general
issue
and
hopefully
it
can
be
fixed
with
triage
permissions.
A
B
B
A
A
B
I
A
A
Who
feel
confident
how
about
william
like
do
you
want
to
help
chetan
or
abhishek?
J
J
B
So
before
going
to
milestones-
and
all
I
just
want
to
ask
all
the
contributors
like
if
we
get
a
chance
to
review
or
think
about
what
could
be
the
next
feature
that
you
know
wants
to
be
like
what
are
the
important
items
from
the
controller
side
or
from
the
red
hat
or
code
fresh?
Do
you
get
a
chance
to
review
that
or
get
a
list
before
alex
actually
present?
Some
of
the
milestones
that
that
we
thought,
like
the
report
for
arco
city.
C
A
C
D
For
I
can't
speak
to
argo
cd
specifically,
but
for
application
sets,
we
have
our
own
milestone
and
I've
got
a
kind
of
a
list
of
things
that
I'm
tracking
for
that
which
we
don't
need
to
go
through
here,
but
yeah
just
fyi.
There
are
some
items
that
I'd
like
to
get
to
that
the
community
is
definitely
requesting,
and
but
those
would
live
on
a
we
wouldn't
need
to
go
through
those
here.
Those
would
live
in.
K
D
Repository
under
its
own
milestone,
but
from
the
red
hot
side
of
things,
that
would
be
one
thing
that
we're
looking
at
okay.
William,
do
you
happen
to
know
if
yourself
or
yawn
had
a
chance
to
look
at
the
rcd
side
of
things.
A
A
A
A
Basically
long
story
short
is
that
users
will
be
able
to
click
on
any
resource
in
argo,
cd
application
detail
stage,
and
then
we
would
show
the
familiar
sliding
panel
that
has
bunch
of
tabs,
and
there
will
be
one
more
tab
that
has
resource
specific
ui
and
we're
going
to
start
from
rollouts.
Basically,
you
user
will
be
able
to
click
on
rollout
and
then
see
reach
visualization
of
rollout.
That
includes
steps
and
current
current.
A
Rollouts
state
and
yeah
everything
that
is
available
in
in
real
life,
dashboard
yeah,
and
I
think
that
kind
of
the
end
goal
is
to
you
know,
make
it
popular,
and
hopefully
we
will
get
a
lot
of
support
for
many
custom
resources
in
argos
cdi
yeah.
So
this
is
already
work
in
progress
and
it's
hopefully
will
finally
be
done
into
the
term.
So
next
item
is
the
same
kind
of
story.
A
We
started
working
already
in
2.1
on
improving
config
management
plugins
in
argo,
cd
and
final
goal
is
that
basically
argo
cd
has
first
class
support,
for
I
think
four
tools
and
it's
realized
it's
a
pain
to
maintain,
not
a
pain.
A
It's
just
a
lot
of
work
to
maintain
each
tool
and
it's
kind
of
difficult
to
do
it
if
it's
part
of
core
and
that's
why
we
decided
to
take
existing
config
management,
plug-in
functionality
in
rbcd
and
try
to
enhance
it
to
the
point
where
plugins
would
provide
exact,
same
user
experience
as
built-in
tool
support
and
hopefully,
at
the
end
of
this
story,
we
will
be
able
to
even
replace
one
of
the
existing
tools
like
customize
and
replace
it
with
a
plugin.
And
so
we
have
a
proposal
already.
A
We
have
pull
request
in
progress
ready
and
we
just
need
to
finish
that
work
so,
and
I
guess
that's
only
part
one
and
we're
going
to
we
want
to
finish
this
part.
One
work
get
some
feedback
from
users
and
then
continue
in
next
releases
on
part
two.
Basically,
we
know
it's
not
in
2.2
we're
not
going
to
complete
it
like
100.
A
We
still
will
need
to
work
on
some
ui
improvements,
but
yeah.
So
and
that's
why?
So
it's
this
too,
at
the
top,
because
we
have
a
lot
of
requests
to
to
to
get.
A
An
improvement
of
repo
self
we're
trying
to
make
it
easier
for
end
users
to
help
themselves
and
start
and
let
them
configure
cluster,
connect
more
clusters
and
repositories
to
argo
cd
without
asking
admin,
and
that
was
pretty
much
just
observation
from
us
like
we
noticed
that
can
uni.
Basically,
we've
got
several
similar
bug.
Reports
from
the
community
and
people
were
asking
about
the
same.
They
were
just
staring.
A
Everyone
was
describing
the
same
use
case
that
we
have
team
of
admins
who
simply
run
argo
cd,
but
these
administrators
don't
have
access
to
clusters
and
repositories
themselves.
They
basically
only
admin
of
argor
and
users.
They
own
the
infrastructure
around
and
users
just
wants
to
connect
that
infrastructure
to
an
instance
and
then
use
it
to
manage
that
infrastructure
and
right
now,
it's
impossible
to
do
without
help
of
an
admin.
Users
must
reach
out
to
admin.
Ask
admin
to
basically
share
permissions
with
the
admin.
A
A
So
argo
cd
uses
label
to
remember
kind
of
which
resources
it
deployed
so
that
in
the
future
it
can
maybe
delete
proven
old
resources
or
notice
that
like
yeah,
basically,
there
are
bunch
use
cases
solved
by
tracking
which
resource
was
deployed
by
which
cd
application,
but
label
using
label
causes
some
issues
and
we
have
we
identified
four
gaps.
A
One
of
them
label
has
fixed,
like
cannot
be
longer
than
three
four
characters,
so
64
characters,
and
there
are
there
are
more
so
basically,
we
ended
up
writing
a
proposal.
Then
we
finally
we
kind
of
agreed
on.
We
have
a
bunch
of
comments
that
describe
how
eventually
we
want
to
improve
that
functionality.
We
still
need
to
update
proposal,
but
basically
we
know
how
we
want
to
build
that
feature.
A
We
just
need
to
document
it
finalize
one
more
time
and
it's
still
possible
that
we
can
implement
it
in
2.2,
because
it's
mostly
about
just
brainstorming
about
how
to
do
it.
The
code
changes
are
not
going
to
be
very
heavy
yeah
and
okay,
so
and
just
to
step
back.
I
guess
we
like
team
from
intuit,
committing
to
work
on
on
this
too.
A
We've
got
commitment
from
from
pasha
to
help
us
with
this
fun
and
resource
tracking.
Looking
for
for
help,
and
it's
there,
I
guess
to
because
it's
important,
we
already
know
what
to
do:
it's
not
so
difficult
to
do
and
we're
looking
for
someone
who
can
help
to
execute
it
and
then
refresh
documentation.
A
A
Jan
did
the
first
good
step
he
created
reaper.
He
gave
us
like
high
level
proposal
of
new
how
to
call
it
table
of
content.
Basically,
it
restructured
the
structural
documentation
and
we
just
need
to
execute
it,
and
so
it's
important
we
do
it
one
day,
but
jan
won't
be
do
it
alone
and
he
needs
help
and
I
basically,
I
don't
think
one
team
has
to
commit
to
do
it.
We
need
to
find
several
volunteers
who
eventually
wants
to
work
on
documentation
if
we
don't
find
it
in
202,
we'll
move
it
again
to
next
release.
A
B
Yeah,
I
think
the
idea
is,
let's
review
these
things,
probably
in
next
quarter.
We
can
see
like
this.
B
Any
other
items
to
be
added,
but
again
like
from
the
water
like
that
right,
so
a
couple
of
them
are,
I
think,
con
from
the
intuit
one
from
code.
Flash
and
remaining,
I
think,
let's
discuss
like
who
can
contribute
and
for
the
bugs
as
well.
We
can
start
tracking,
like
maybe
every
once
every
two
weeks
to
see
like
like
help
wanted
or
who
wants
to
be
contributed.
D
B
I
think
we
can
start
looking
at
the
progress
as
well,
and
I
think
that
is
my
proposal,
but
we
can
discuss
on
how
we
can
actually
track
the
milestones
and
how
we
can
track
the
progress
going
forward.
But.
B
B
We
can
discuss
more
on
it,
but
please
come
forward
and
pick
up
the
tasks
and
even
if
it
is,
if
you
are
new,
that's
fine.
I
think
you
can
start
landing.
L
Yeah
I'll,
let
you
know
I
mean:
we've
got
six
to
ten
people
ramping
up
right
now.
Most
of
them
are
gonna,
be
focused
on
the
code
side.
So,
on
the
documentation
side
for
argo
rollouts,
I
think
we
actually
have.
We
have
one
person
costas.
That's
doing
a
lot
of
documentation
work
there.
So
if
there's,
if
there's
stuff
that
comes
up
around
documentation,
I'd
be
thrilled.
L
If
people
want
to
sign
it
to
costas
and
and
tag
me
on
it,
and
we
can
see
about
trying
to
get
those
things
figured
out,
yeah.
A
I
I
that
would
be
awesome.
I
I
know
that
my
feeling
is
that
everyone
recognized
that
this
is
important
task,
but
engineers
find
it
very
boring
and
like
not
no
one
excited
to.
Actually.
We
just
need
a
little
bit
more
energy,
someone
who
can
lead
it-
and
I
I
guess,
like
jan,
like
did
a
good
kickstart.
He
I
need
to
find
the
ticket
that
has
already
some
description
of
the
end
goal
yeah
in
the
ticket.
We
have
more
details
about
basically,
what's
not
working
currently
and
what
we
should
improve.
L
You
know
yeah
tag
coast,
just
an
eye
on
any
documentation,
issues
and
we'll
see
if
we
can
get
it
get
them
resolved.
L
A
A
H
Yes,
a
few
months
back,
we
had
jonathan
presented
the
integration
plan
for
the
app
sets
to
get
into
argo
cd.
It's
recorded.
I
hope
we
I'm
not
sure
if
we
can
upload
it,
but
there's
email
loosely
focused
on
the
back
end
integration
and
not
the
ui,
but
I
there's
some
details
in
that
meeting
that
discussed
like
how
we
should
integrate
the
backend
for
episodes
yeah.
H
I
think
it
basically
involved
like
a
pass
through
api
call
that
reached
the
the
app
set
server
api
server
to
perform
some
of
the
things
like
previewing
the
generated
apps
that
would
be
created
without
actually
creating
it,
and
then
somehow
you
know
presenting
that
back
to.
A
D
Yeah,
so
there's
that
recording,
there's
also
an
application
set
issue
in
the
upset
repo
containing
a
link
to
the
google
doc,
which
is
what
I
presented
at
that
meeting.
So
folks
are
looking
for
a
quick
overview.
That's
a
good
place
to
start.
A
Right,
I
guess
we're
not
talking
about
milestone,
that's
pretty
much.
At
least
I
didn't
have
any
more
information,
so
we
can
move
yeah.
We
can
move
to
the
questions
about
tickets.
So,
let's
start
from
the
first
one.
I
had
a
chance
to
look
at
it
here.
So
basically,
the
request
here
is
to
start
so.
Argo
cd
has
a
feature
that
allows
creating
namespace.
A
If
you
have
an
application
that
points
to
a
namespace
but
namespace
doesn't
exist,
you
can
click
a
checkbox
and
obviously
you
will
auto
create
namespace
and
then
people
now
requesting
ability
to
add
labels
to
auto
created
namespace,
and
I
guess
we
need
to
honestly.
We
did
not
talk
about
that
feature,
but
it
feels
like
we
need
to
make
a
decision.
If
we
want
to
support
it
or
not.
The
downside
is
that
today
we
want
to
create
labels
tomorrow,
people
will
ask
for
annotations
and
then
day
after
tomorrow.
A
Maybe
we'll
need
to
ask
like
someone
will
ask
for
some
additional
fields
in
a
spec,
so
it's
kind
of
a
slippery
slope,
but
at
the
same
time
maybe
it's
not
so
slippery,
because
namespaces
doesn't
have
a
lot
of
like
details.
It's
basically
just
metadata
if
I'm
not
mistaken
labels
and
annotations.
So
there's.
H
Some
security
concerns
with
this
feature:
the
ability
to
annotate
their
label
name
spaces
come
because
a
lot
of
controllers
will
do
like
issue
injection,
for
example,
and
that's
typically
a
operator
concern.
H
So
so,
if
end
user,
can
I
guess,
if
they
get
this
feature,
create
all
the
crea
if
they
can
create
name
spaces
anyways.
This.
A
D
A
H
So
let
me
take
back
that
concern
because
it's
no
worse
than
right
now,
like
I
mean,
if,
basically,
if
they
can
create
namespaces,
they
can
create
namespaces
and
they
can
always
label
it
and
get
okay.
So
let
me
take
that
back,
but
I
do
think
it
does
sound
like
a.
H
A
J
Oh
yeah,
so
sorry
I
haven't
contributed
in
a
while,
so
I'm
kind
of
refamiliarizing
myself
for
the
code
to
get
back
into
it,
but
I
figured
if
we
have
time.
I
would
just
raise
this
essentially
yeah.
So
when
I
looked
at
this,
I
figured
I'd
take
a
crack
at
it
because
it
seemed
at
first
it
seemed
it
might
be
straightforward
to
me
like.
J
So
I
kind
of
wanted
to
see
what
would
be
a
better
approach
for
that
like
I
guess
it
doesn't
make
sense
to
make
any
changes
in
the
get
ops
engine
for
that,
so
it
would
need
to
be
labeled
separately
later
on.
I
just
want
to
get
some
thoughts
on
what
you
think,
a
good
approach
for
that
would
be
yeah,
and
then
I
realized
while
alex
was
talking.
I
guess
this
might
fall
under
the
resource
tracking
area
that
you
mentioned
anyway.
A
A
H
So
if
I
recall
we
created,
we
actually
created
the
auto,
create
name
space
feature
to
support
helm
style,
use
cases
right
like
home.
H
Like
create
namespace
file,
I
think,
and
so
so
helm
can
create
an
increase
as
part
of
the
insult
without
having
to
define
that
namespace
as
part
of
the
southern
manifest.
So
I
think
that
was
the
the
motivation
for
actually
creating
the
the
whole
the
create
all
the
great
namesakes.
In
the
first
place,
I
don't
think
they
have
the
ability
to
annotate
or
label
those
other
created
namespaces.
H
I
could
be
wrong,
but
because
it's
controlled
by
flags
I
might.
I
suspect,
that
you
can't.
J
But
the
other
thing
I
think,
is
whoever
created
this
issue.
I
think
what
they
mentioned.
The
proposal
is
just
that
the
label
would
just
have
the
name
space
like
the
name
of
the
namespace
in
the
label,
like,
I
don't
think,
they've
thought
about
it
being
on
like
an
application
level
or
whether
it
needs
to
have
app
metadata
and
stuff.
Maybe
that's
like
an
extension
of
this
proposal,
I'm
just
going
to
fund
based
off
of
what
they
mentioned
in
yeah.
Like
the
proposal
section,
they
just
said.
G
Do
we
have
any
example
right
now
using
label
to
create
resources
like
do
we
is?
This
is
the
first
time
we
have
a
proposal.
First
time
we
use
labor
to
create
anything
or
do
we
have
an
exam
or
are
we?
Are
we
already
doing
some
these
sort
of
things.
G
A
I
mean
there
is
the
user
provided
some
motivation?
It's
mostly
discoverability,
like
you
know,
if
how
do
you
find
which
team
spaces
were
auto
created,
quickly,
yeah
and
then
you
can
use
it
to
clean
up,
for
example,.
G
And
later
on,
we
might
be
looking
at
people
asking
use
label
degrees,
something
it's
a
lot
of
resources.
Okay.
So
this
is
a
pattern
that
we
like
to
use
then
maybe
open
on
door
for
future.
J
A
One
thing
about
namespace,
auto
created
name
space:
it
doesn't
even
have
typical,
you
know,
so
all
other
resources
are
labeled
and
namespace
is
enabled
so
that
we
don't
delete
it
mistakenly
when
we
delete
application.
So
basically
you
can
create
application,
it
will
auto,
create
namespace.
Then
you
delete
application,
but
namespace
stays
and
we
did
it
kind
of
intentionally
because
it's
not
safe
to
auto
delete
namespace.
H
I
honestly
don't
think
the
reasons
listed
here
are
motivation
enough
to
for
the
future.
I,
but
I
do
think
the
use
case
for
the
injection
labels.
That's
actually
a
stronger
use
case
in
my
mind,
to
to
support
a
feature
like
this,
but
I
think,
there's
also
a
kind
of
a
gray
area
or
a
line
that
we
would
have
to
cross
like
at
that
point.
If
you
want
all
these
labels
and
annotations
on
your
name
space,
it
goes
beyond
just
the
convenience
function
of
creating
any
space
you.
H
It
seems
like
something
you
want
to
get
ups
and
kind
of
declaratively
think,
rather
than
a
checkbox
that
you
create
application
create
time.
So,
philosophically
I
think
there's
maybe
a
reason
not
to
do
it.
A
A
A
You
know
it's
there,
and
users
can
assume
that
label
will
be
added
to
all
auto,
created
namespace
and
the
they
can
use
it
for
discoverability
if
they
want
more.
That
means.
So,
basically,
we
will
not
support
any
annotations
or
any
custom
labels.
We
can
only
offer
one
single
label
that
our
procedure
will
auto,
create
how
to
auto
apply
to
each
name
space,
and
then
people
can
use
that
label
to
discover
name
spaces.
H
Well,
I'm
actually
saying:
if
we
do
do
this,
I
would
rather
the
the
mechanism
be
generic
so
that
they
can't
choose
it
for
this
specific
use
case
for
for
the
tracking
and
as
well
as
the
seo
use
case,
so
just
a
more
generic
mechanism
to
allow
them
to
label
or
annotate
anything
they
want.
H
And,
and
also,
I
think
that
I
agree
with
the
templating
thing-
is
it's
way
kind
of
too
far
like
it's?
You
know
a
system
level
like.
Oh,
I
want
all
the
sdo
ones
to
like.
Have
this
label
and
then
another
one
with
all
the
alb
ingress
controller
labels
that
want
to
do
injection
for
ab
ingress
and
then
that
that
seems
like
a
step
too
far,
but
just
having
like
a
feel
like
just
like
a
metadata
namespace
metadata
where
they
can
put
labels
and
annotations,
and
then
they
can
do
whatever
they
want
in
there.
H
I
think
I'm,
I
think,
I'm
open
to
that.
It's
just
it's!
It's
additional
stuffing
configuration
management
into
the
rollouts
in
the
the
application,
spec,
okay,.
H
A
A
How
about
we,
let
you
specify
which
labels
annotations
namespace
has,
but
on
application
level,
so
it's
kind
of
it's
a
little
bit
of
burden
on
user
user
will
need
to
specify
it
every
time
you
know
right
now,
it's
just
checkbox.
We
will
we're
saying
in
addition
to
checkbooks,
you
will
need
to
fill
labels
and.
J
I
have
a
quick,
related
question
so
like
right
now,
if,
like
a
user,
has
a
namespace
that
they
want
created
like
in
their
git,
which
can
just
be
deployed,
so
could
they
just
add
this
label?
Do
they
have
the
ability
to
just
add
this
label
in
their
name
space
and
get
and
have
it
deployed
as
it's
right
now?
Is
that
it's
it's
a
lot?
The
only
problem
is
it's
like
you.
A
Want
to
make
it
it
makes
application
not
known
portable
like
right
now
you
can
install
the
same
set
of
manifests
into
any
namespace.
If
your
hardcode
name
space
name
in
the
in
this
manifests,
then
you
kind
of
the
name.
Space
name
is
predefined
and
then,
if
you
want
to
make
it
more
flexible,
maybe
you
can
use
helm
inside
of
helm.
You
have
access
to.
A
A
It's
mostly
about
convenience,
yeah,
it's
it's
like
namespace
altercation
is
useful.
The
the
main
benefit
it
provides
is
that
you
don't
need
to
create
name
space
template
in
name
space,
manifesting
you'll,
get
people
okay,.
J
Got
it
yes,
I
mean
for
now
I
think,
there's
a
lot
that
needs
to
be
discussed
on
the
silence
track.
The
discussion
before
trying
to
work
on
it
and
I
think
jessica,
has
a
good
proposal.
It's.
A
Like
kind
of
you
know,
we
that
that
feature
stays
just
a
convenience
feature
and
it
it's
not
like
we're
introducing
the
whole
big
templating
mechanism,
but
but
we
need
information
from
user
that
what
gc
is
proposing
is
going
to
work
yeah.
Okay,
thanks.
D
A
K
A
K
Yes,
the
thing
is,
I
I
tested
without
that
line
and
still
drop
down
will
work
with
no
issues,
so
I
just
I
couldn't
check
back
which
who
wrote
this
down
and
asked
him
about
why
we
need
that
line.
So
I.
A
K
A
A
And
I
guess
the
problem
here:
oh
sorry,
the
ticket
that
you
mentioned-
okay
yeah,
so
this
functionality
is
broken
here
because
we
have
a
drop
down
which
should
stay
open.
If
you
open
another
drop
down,
you
see
the
problem
here.
Basically
it
in
all
the
cases
you
want
to
close
all
other
drop
downs,
except
this
particular
case.
Oh
okay,.
A
K
A
I
will,
if
you
remove
this
line,
what
will
happen
if
you
know
we
will
stop?
After
closing,
after
all,
other
drop
downs
on
the
page,
yeah
and
user
will
be
able
to.
You
know,
click
this
little
dot
button
button
here
the
drop
down,
stays
open
and
then
click
another
three
dot
button,
and
there
are
kind
of
two
open
drill,
downs
which
is
not
good,
so
yeah,
no.
K
Okay,
I
see,
I
think
when
I
tested
it,
it
wasn't
an
issue
to
me.
You
can
simply
confirm
to
comment
out
that
line
on
your
end.
You
can
just
confirm
when
you
have
time.
I
don't
think
that
happened
to
me,
but
I
can
confirm
again
yeah.
K
I
don't
see
a
issue,
an
issue
when
I
test
it.
It
looks
naturally
when
I
click
that
arrow
and
it
opens
the
refresh
menu
and
the
drop
down
stay
there
before
I
click
the
hard
refresh
button.
A
K
I
think,
if
that
that's
that's
the
reason
you
edit
it,
I
think
we're
fine
to
remove
it.
Just
maybe
you
can
help
me
to
confirm
and
I
will
make
a
vr
thank
you.
A
That
was
to
that
one
all
right,
yeah,
basically
2.1.
A
I
just
deployed
it
so
it
we
kind
of
delayed,
so
we
didn't
even
deploy
it
into
it
that
we
use
for
testing
until
yesterday.
I
deployed
it
yesterday
because
we
had
bugs,
but
now
we
still
have
one
open
bug,
not
critical
one,
the
ui
and
we
started
testing
internally
and
we'll,
but
we
already
had
extensive
external
testing,
so
I
guess
we're
going
to
get
it
and
we
will
get
some
user
feedback
into
it.
H
For
I
have
one
fix
that
needs
to
be
and
2.1
I
submitted
a
pr
for
it.
The
rollout
health
check
was
has
one,
so
I
would
make
sure
that
is
in
before
deploying
it
into
any
rollout
clusters.
H
I
it's
the
pr
series,
basically,
the
suspended
the
sorry,
the
pause
status
and
the
rollout
doesn't
matter
wasn't
being
mapped
to
the
suspended
argo
cd
status.
I
had
to
map
it
correctly
and
the
the
error
was
that
any
pause
rollouts
would
have
the
invalid
health.
A
We
yeah
we
need
to,
I
think
two,
two
in
progress
fixes
so
yeah.
It's
kind
of.
I
think
I
basically
saying
it
every
day
that
we're
almost
done-
and
hopefully
this
time
we're
really
almost
almost
done
so
to
like
your
health
check,
fix
and
ui
fix
needs
to
make
it
in
yeah
and
the
good
thing
that
so
we
had
a
bug
that
we
found
it's
just
to
highlight
that
testing
from
external
users
is
super
helpful,
so
we
had
a
bug
during.
A
I
still
don't
know
how,
but
because
we
know
that
we
had
the
stack
trace,
but
we
just
fixed
it.
We
had
that
kind
of
graceful
handling.
Confederated
data
so
yeah,
basically
that
this
is
that
explains
my
confidence
in
the
release,
because
it's
already
used
by
multiple
people
and
they
even
reproduced
kind
of
a
bug
that
is
not
so
straightforward,
yeah
and
cannot
be
easily
reproduced
yeah.
So
hopefully
I
think
next
thursday
we
will
have
a
just.
A
O
A
O
To
rotate
the
exactly
moderator.
D
Discussion,
thank
you.
So
should
I-
and
I
looked
at,
I
think
four
or
five
issues
over
the
past
week
so
pretty
late.
Actually,
I
think
most
of
them
within
the
past
couple
days
should
anything
you
wanted
to
add.
E
No
nothing
much.
I
gotta
learn
a
lot
exactly
how
we
need
to
answer
to
the
users,
so
it
was
quite
helpful
like
having
a
primary
discussion
moderator.
It
just
helps
to
understand
exactly
like
next
time.
If
I
am
like,
I
think
I'll
need
to
have
again
one
I
need
to
shadow
once
more,
but
yeah.
I
just
feel
a
little
more
confident
about
how
I
could
go
ahead
in
future.
E
A
Great
feedback,
all
right
so
jc
your
name
is
next
on
the
list.
Do
you
want
to
do
that?
Do
you
have
time
to
do
it
next
week
or
you're
going
to
be
on
vacation.