►
From YouTube: Argo Contributor Experience Office Hour 25th 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).
A
Right
good
morning,
everyone
one
more
time.
Okay,
I
don't
see
any
new
faces,
so
no
need
to
do
any
introductions
and
let
me
start
from
sharing
my
screen.
A
And
yeah
here
is
the
list
of
topics
we
had
and
all
of
them
from
previous
meetings
from
regina's
ux
review
meeting,
and
I
also
wanted
to
add
one
topic
to
discuss
1.9
release-
and
I
know
that
shobik
has
not
joined
today
and
I
don't
see
so
usually
they
have
things
they
want
to
discuss.
If
they're
not
here,.
A
A
Yes,
okay
yeah
in
this
case
maybe
you're
gonna
take
over
and
maybe
you
know,
walk
us
through
remaining
u.s
ux
issues.
B
Sure
one
second,
so
this
the
first
one
is
just
redesigning
the
action
buttons
in
the
application
list
view.
B
This
was
opened
in
october,
but
it's
just
you
know
I
I
don't
think
we
have
like
serena
or
beau
in
this
meeting,
but
it's
just
kind
of
trying
to
get
more
ideas
for
better
ways
that
we
could
display
this.
B
B
I
think
this
one
is
probably
specific
for
this
page
really
like
these
two
pages,
especially
this.
This
list
view
it
hides
them
in
an
overflow
menu,
and
I
don't
think
that
that's
very
good
ui.
A
A
B
So
I
haven't
updated
this
one
before
I
think
shibama
has
been
working
on
it.
The
past
couple
days.
A
A
A
B
If
we,
if
we
could
talk
about
one
more
quick
ux
thing
I
have,
can
I
share
for
a
second.
B
Okay,
so
can
you
see
this
okay?
So
these
are.
This
is
the
status
badge
and
I
was
redesigning
this
to
fit.
Pattern
fly
colors
because
they're
the
issue
with
it
was
that
it
doesn't
fit.
The
web
aim
standards
for
contrast,
so
this
would
be
what
it
would
look
like
if
we
went
with
the
pattern
fly
colors
for,
like
the
words
in
the
background,
so
does
this
work
with
like
our
go
cd
like
design
pattern
like?
B
Is
this
too
out
of
place
with,
like
the
colors,
just
wanted
to
get
some
feedback
on
it
really
quick?
This
would
be
like
a
pretty
simple
change.
It
would
only
be
for
the
colors
really.
A
I
personally,
I
would
not
have
any
objections
it
feels
like
you
know
much
similar
to
what
we
had
before,
but
better
readability.
So,
but
I'm
I
want
to
hear
someone
else's
opinion
as
well.
I'm
not
the
strongest
ux
ui
focus
person.
C
A
D
B
E
Yeah
hi,
it
looks
different
here.
This
is
the
current
one,
because
the
type
looks
funky.
Is
that
I'm
not
like
the
the
well?
I
call
it
the
like
tracking,
it's.
It
seems
like
the
are
they
like
stretching
to
like
the
size
of
the.
B
B
The
shortest
word
that
would
be
here
is
synced,
so
that
would
be
like
the
biggest.
A
A
B
B
Yeah,
I
was
also
the
last
thing
I
was
like.
Is
it
okay,
if
they're
both
the
same
color,
because
there
there
must
be
like
instances
where
this
is
also
the
same
color,
because
I'm
not
changing
any
of
the
colors
based
on
like
their
their
color?
I
don't
know
how
to
explain
that,
like
there
are
certain
cases
where,
like
these
would
be
the
same
color
as
this.
B
E
A
Yeah,
this
thing
is
an
image
that
people
embed
into
readme
files
or
some
websites.
Okay,.
D
On
another
thought,
so
sorry
for
completely
switching
the
context.
Do
we
have
a
bug
in
the
patch
because
you
specify
in
the
ui
the
revision
is
equal
is
true,
but
there's
no
revision
displayed.
A
A
D
A
B
That's
okay.
I
was
pretty
much
done.
A
B
A
F
A
Okay-
okay,
I
want
to.
I
will
share
my
screen
again,
so
I
think
that
was
last
ux.
I
think
we
wanted
to
discuss
right.
Okay
and
I
I
wanted
to
just
talk
about
1.9
milestone
and
the
reason
is,
I
think,
we're
basically
approaching
the
end
of
it
and
just
wanted
to
do
this
typical
exercise.
I
wanted
to
just
quickly
talk
about
things
that
looks
very
important
and
we
need
some
kind
of
status
update
and
then
maybe
you
just
agreed
on
things
that
could
sleep
and
we
we
can
move
them
to
the
next
milestone.
A
Yeah.
So
and
to
be
honest,
this
list
is
kind
of
it's
it's
long,
but
there
are
no
extremely
difficult
things
and
then
some
of
them
kind
of
hard
to
do,
but
they
are
not
really
blockers
for
release
yeah
and
I
I
but
there
was
one
thing
which
I
wanted
to
talk.
I
think
with
vizion,
because
I
think
can
you
worked
on
it
before
so
it
was
related
to
argo,
cd,
repo
server
tls
issue,
I'm
trying
to
find
the
ticket
in
list
right
now.
A
It's
it's
just
there,
one
below
this
one,
this
one,
oh
yeah,
okay,
yeah!
So
never
mind
this,
not
this
one
right.
This
is
to
disable
tls
and
there
was
one
more
two
I
just
saw
it.
A
Yeah
there's
this
okay,
this
one
authentication
help
show
this
one
yeah.
D
A
Tls
authentication,
so
basically
we
never
found
the
real
real
reason,
but
we
implemented
health
check,
which
is
kind
of
a
good
workaround
and
a
health
check,
catches
that
situation
and
simply
restarts
repo
server
and
and
that's
it.
But
we
never
learned
why
this
is
happening,
and
I
know
janu
worked
on.
We
just
the
next
attempt
to
fix.
It
was
to
upgrade
all
dependencies
and
it
appears
to
be
difficult
to
do
because
we
we
use
jrpc
and
go
and
protobuf
and
go
go
protobuf
generator
and
to
move
all
of
that
to
next
version.
A
I
think
we
were
supposed
to
get
rid
of
go,
go,
protobuf,
right,
yeah
and-
and
I
think
it's
kind
of
it's
open
discussion
right
right
now.
This
ticket
is
not
extremely.
It's
not
like
everything
is
broken.
Health
check
does
its
work
and
I
think
we
just
need
to
make
a
decision
if
we
want
to
try
to
upgrade
everything
get
rid
of
google
protobufs.
So
it's
quite
of
good
changes,
but
I
think
it
could
be.
D
Not
so
yeah,
I
think
the
the
problem
with
this
issue
is
so
I
was
never
able
to
reproduce
it
on
one
of
my
systems
so
and
for
some
people
it
happens
and
for
some
people
it
doesn't
happen.
A
D
That
makes
this
issue
really
yeah.
It's
it's
mind-blowing
right,
yeah,
so
because,
unless
we
have
a
way
to
to
reliably
reproduce
it,
I
think,
even
if
we
go
ahead
and
and
upgrade
the
the
dependencies
we
think
might
be
the
reason
for
this
to
happen.
A
Yeah
I
feel
like
we
can
and
into
it
get
help
can
help
a
little
bit
because
we
run
a
lot
of
argo
cds.
So
we
still
see
that
issue
in
logs
only
like
maybe
once
every
two
three
days.
A
So
if
we
make
changes
and
then
we
will
have
some
way
to
say
if
it
helped
or
not,
it
won't,
but
we
will
have
to
wait
longer
than
two
two
days.
Basically,
if
we
make
this
change
and
then
if
we
release
that
change
to
all
instances
on
into
it,
and
then
we
wait
for
like
a
week,
then
we
will
be
able
to
see
so
it's
kind
of
yeah.
We
won't
get
immediate
answer,
yes
or
no,
but
there
is
a
way
to
test
it.
Yeah,
okay,
understood,
but
at
the
same
time,.
D
D
The
thing
is
getting
rid
of
global
proto.
That's
that's!
Quite
a
bummer
right.
It's
it's
really
a
lot
of
effort,
so
I
don't
know.
I
don't
know
about
the
release
timeline
for
v1.9.
D
D
So
I
mean
I,
I
talked
with
jesse
and
we
I
think
we
agreed
that
we
should
get
rid
of
google
product
anyway,
because
yeah
they're
they're
not
really
they're,
not
maintained
anymore
and
yeah.
So
it's
it's
something
we
should
do.
I
agree.
Okay,
but.
A
A
D
Cool
great
okay,
thank
you.
What,
but
what
we
can
also
try
is
that's,
that's
far
quicker
to
to
upgrade
golem,
because
I
will
yeah,
as
I
said,
I'm
not
sure
where,
where
the
bug
is
right,
so
no
one
is,
but
we
can
just
maybe
we
can.
We
can
do
a
build
for
intuit
using
golan
1.5
dot.
I
don't
know
what
the
latest
patch
is.
A
D
A
Okay,
nice
and
thank
you,
and
so
the
next
ticket
was
I
I
wanted
to
discuss-
was
about
customized.
Basically,
so
we
we
have
this
one.
It's
like
an
umbrella
ticket
to
update
tools
versions,
but
I
think
helm
is
straightforward.
A
We
already
upgraded
to
latest
helm
and
I
think
we
will
maybe
send
one
more
pr
before
releasing
to
upgrade
to
latest
latest
helm,
but
customize
is
different,
so
recently
customize.4
got
released
and
it
has
a
breaking
change
and
even
customize.t
latest
batch
release
has
breaking
change
budget
breaking
changes
comparing
to
previous
version
of
most
recent
version
of
customize
available
in
current
argo
cd
release.
A
So,
basically,
that's
why
it's
unclear,
which
version
we
should
upgrade
to
so
if
we
upgrade
to
customize
1.4
a
lot
of
fargo
cd
users
will
be
in
trouble
because
customize.4
laws
lose
a
feature
that
allows
people
to
reference
files
using
gogetter.
A
I
think
library
is
called
go
getter
if
we
upgrade
to
most
recent
3.9
push
release
in
this
case.
We
will
think
it's
better
to
me,
but
in
this
case
we're
going
to
know
that
argo
cd
goes
out
with
not
most
recent
version
of
customize
and
yeah.
I
wanted
to
hear
your
thoughts,
so
basically
I'm
I'm
thinking
that
upgrading
to
customized
to
latest
customized
4.0
version
is
bad
idea,
because
I
think
it
really.
A
I
mean
this
breaking
change
will
make
really
difficult
to
use
argo
cd,
vs
customize
for
a
lot
of
users
and
and
I'm
kind
of
proposing
to
just
upgrade
to
most
recent
3.9
patch
version,
and
maybe
maybe
just
put
an
explanation
into
upgrade
notes
and
explain
why
it's
not
4.0
and
explanation
would
sounds
like
sorry,
4.0,
don't
have
a
feature
that
allows
you
to
reference
remote
files
and
that's
why
we
won't
use
it.
D
I
think
I
think
so
so
if
you,
if
you
look
at
the
failing
ci
tests
of
this
pr,
this
is
customized.
Iso
has
introduced
another
breaking
change
in
the
command
line.
Interface
right
so
I
mean
we
have
we
have
the
mechanisms
for
users
to
specify
the
customized
version
to
use
right?
Yes,
but
moving
up
to
I'm
not
sure
which
version
it
was.
I
think
it's
mentioned
in
the
in
dpr
yeah,
it's
3.99
yeah,
and
so
this
will.
This
will
basically.
D
A
Oh
yeah,
I
I
kind
of
I
didn't
talk
about
this.
So
it's
it's
like
it's
a
separate
problem
and
I
was
thinking
even
if
we
upgrade
to
3.9
we
should
make.
We
should
do
it
in
a
backward
compatible
way.
So
I
guess
we
will
have
to
hard
code.
The
version
that
introduce
you
know
behavior
change
and
still
support
old
versions,
and
I
think,
and
the
next
even
bigger
problem
is:
what
do
we
do
with
customized?
Four,
because
it's
it's
a
completely.
D
A
It's
what
do
you
think
if,
if
like
for
1.9
release,
we
simply,
I
guess
hard
code
backwards
and
compressibility
introduced
in
3.9
version,
do
not
upgrade
four
and
that's
it
and
then
yeah
and
I
think
we'll
need
to
come
up
with
a
plan
for
with
a
better
way
to
support
customizing
next
delays.
Yeah.
D
A
G
A
4.0
of
customers-
I
might
I
don't
know
if
that's
true
or
not,
but
my
impression
was
that
it
feels
like
customize
kind
of
you
can
assume
that
customized
version
is
stable
if
it's
used
in
cube
ctl
because
the
you
know
require
is
really
high
to
get
into
cube
ctl,
and
I
guess
all
the
versions
between
this.
You
know
the
version
that
goes
into
keep
ctl
are
kind
of
considered
unstable.
A
Before
that
happens,
it's
not
really
safe.
Okay-
and
I
think-
and
this
is
these
are
two
big
issues
I
found
in
in
the
list
of
1.9
release
and
another-
not
issue.
But
you
know,
the
big
thing
which
we
must
do
is
kind
of
is
to
include
the
application
set
into
rcd
installation,
and
we
already
spoke
about
it.
I
think
yeah.
There
is
no
need
to
repeat
the
same
conversation
and
the
rest
of
it.
A
I've
maybe
I'm
wrong,
but
I
kind
of
went
for
all
these
tickets
and
none
of
them
is
there
are
things
we
must
do
like
upgrades
and
some
bug
fixes,
but
I'm
pretty
sure
they
will
be
done
using
the
week
or
two
and
okay,
sorry,
my
bad,
and
there
was
one
thing
which
we
targeted
for
1.8
release
and
I
think
it
won't
be
done.
So
there
is
a
feature
to
optionally
change.
How
argo
cd
track
resources
that
were
deployed
by
rbcd,
basically
to
switch
from
label
to
annotation?
A
A
F
A
A
G
I'll
take
the
first
opportunity
so
just
in
in
in
general
question,
so
when
we
think
about
like
continuous
deployment
right
in
general,
we
think
about
like
the
blueprint
deployment
model
or
canary.
G
I
see
that
for
argo
cd,
that
is
part
of
our
roll-ups,
I'm
sorry
if
it
has
been
discussed
previously
or
not.
So
let's
say:
if
I'm
doing
a
talk,
cargo,
cd
and
then
the
question
comes
out.
How
do
we
do
blue,
green
or
canary
deployment
with
argo
cd?
I
think
one
of
the
way
of
thinking
is
because
blueprint
or
canary
deployment
is
imperative,
there's
no
building
with
from
kubernetes
to
to
use
the
declarative
approach.
G
But
if
we
like
to
break
it
down
simply
how
customer
could
achieve
the
blue
mean
deployment
or
different
rollout
models,
maybe
with
argo
cd
or
in
conjunction
with
argo
rollouts.
What
would
be
a
nice
answer.
A
I
feel
like
our
position
was
that
blue
green
is
kind
of
is
no
different
from
our
link
update.
It's
also
imperative.
A
rolling
update
consists
of
bunch
of
steps
because
you
need
to
progress.
You
know
from
one
port
and
two
to
ten
ports.
Basically,
you
need
to
do
10
steps
and
create
templates,
but
blue
green
just
have
more
features.
A
It
requires
more
features
like
manual
approval
when
you
have
to
do
the
switch
and
and
that's
why,
if
you
have
this
type
of
situation,
you
need
to
you
need
to
stop
using
deployment
and
switch
to
something
which
support
blue
green,
and
we
have
basically
two
options
right
now:
either
argo
loud
or
flagger,
I
guess
that's
the
answer.
So
it's
like
argo
cd
is
not
going
to
orchestrate
step
by
step
deployment,
because
that's
not
what
it's
supposed
to
do.
G
And
so
I'll
ask
one
more
question,
so
another
question
I
I
received
was:
how
does
argo
ct
handle
multi-tenancy?
So
I
have
clusters
and
different
zones,
and
then
I
want
to
make
sure
that
I'm
not
accidentally
making
change
to
a
cluster
where
I
shouldn't
have
access
to
what
would
be
the
right
place
where
I
could
read
more
about
this.
A
D
I
mean:
do
you
agree
with
it,
but
that
reminds
me
that
I
wanted
to
push
the
the
new
documentation
yeah,
but
I
think
I
there's
in
the
in
the
in
the
new
in
the
new
layout
or
in
the
new
content.
There's
something
about
that
explained
I
think,
and
if
not
it
will,
it
will
have
a
structure
where
people
can
actually
contribute
this
knowledge.
A
A
D
D
A
I'm
pretty
sure
I
will
be
able
to
share
my
blog
this
weekend
yeah,
so
it
will
improve
a
little
bit.
I've
seen
even
more
I've
seen
that
someone
offered
money
for
like
a
consultancy
work.
If
and
he
was
asking
about
projects,
he
was
asking
okay.
How
do
I
configure
multi-tenancy
in
argo
cd?
If
you,
if
you
know
how
to
do
it,
let
me
know,
and
he
was
proposing
to
pay
for
ours.
Of
course,
have
you
seen?
Have
you
seen.
A
H
Cool,
I
have
something
to
bring
up
real,
quick
sorry.
I
was
a
little
bit
late
to
the
meeting.
I
don't
know
if
people
saw
the
issue
that
I've
filed
against
argo
cdn
workflows,
I
think
it
was
two
days
ago,
but
just
discussing
a
browser
support
policy
for
the
ui
right.
So
what
browsers
do
we
officially
want
to
support
and
what
versions
of
said
browsers
do
we
want
support,
so
just
wanted
to
bring
it
up.
So
if
you
could
like
take
a
look
at
it
and
chime
in
with
your
opinion,
I
think
it'd
be.
H
I
I
I
have
a
question
about
this.
I
mean
I
I
have
not
seen.
People
have
issues
with
browser
incompatibility
using
our
products.
I
wondered
if
anybody
else
had
had
that
issue.
D
Yeah,
as
a
firefox
user
myself,
I
sometimes
notice
that
there
is
a
very
high
cpu
consumption
when
I
have
an
rcd
application
opened,
but
I
I
was,
I
have
not
fired
the
bug
yet
and
it's
higher
than
chrome.
Is
it
being
no
chrome
being
no
chrome
user?
I
have
no
comparison,
okay,
but
it
it.
It
eats
up
a
complete
cpu.
H
Yep
I
mean
I
can
give
you
a
concrete
example.
I
would
be
surprised
if
it
even
works
but,
for
example,
internet
explorer
11..
We
don't
have
an
efficient
advance
there
so
say
if
we
wanted
to
start
using
css
grid
specifically
for
workflows,
there's
some
alignment
issues.
I
noticed,
then
I
was
going
to
try
using
css
grid
to
fix
those,
but
it's
not
supported
in
ie11.
So
the
question
was:
can
I
actually.
H
A
A
J
G
J
Adding
adding
a
new
feature,
that's
using
a
new
capability
that
might
not
work
on
an
older
browser.
I'm
I'm
less
concerned
about
the
latter.
I
mean
adding
a
new
feature.
We
shouldn't
we
shouldn't
slow
down
velocity
because
someone
might
be
in
an
older
browser.
I
mean
they.
Eventually
they
will
upgrade
if
they,
if
they
need
a
new
feature
they
can,
they
can
upgrade.
I
don't
think
that's
a
big
problem.
J
J
I
I
don't
want
to
add
more
process
and
testing.
If
we
don't
have
to
do
do
we
need
to
come
up
with
some
recommendations
on
just
something
written
on
that
we
can
use
new
features
when
they
come
out
or
are
we
it
seems
like
it
kind
of
works
as
it
is,
I'm
not
sure
what
if
it
is
a
big
problem
that
that
we
need
to
to
write
something
down
if
we
can
just
discuss
it
here,.
A
I
guess
maybe
the
simplest
thing
we
could
do.
If
we
just
say
we
assume
you
use
latest
chrome
or
safari,
you
know
latest
stable
version
of
romance
and
sorry
and
firefox,
and
then
everyone,
like
all
developers,
will
be
happy
because
that
would
mean
go
ahead.
Use
most
recent
features,
but
maybe
what?
If
we
simply
add
one
more
question
about
browser
in
a
next
user
survey
and
get
some
data
about?
You
know
some
answers
from
users
and
if,
if
everyone
replies
we
don't
use
old
browser,
we
upgrade
often
questions
will
be
answered.
J
Yeah
or
there
can
be
a
caveat
when
we,
when
you
do
a
new
release,
if
there
are
new
features,
would
be
a
caveat
that
you
know.
New
features
might
only
work
with
the
latest
versions
of
the
of
the
browser.
If
we
say
that
we
we
assume,
we
use
the
latest
browser,
then
then
that
could
potentially
be
the
you
know.
The
breakage
part
included
in
that,
but
I
think
maybe
just
a
small
caveat
that
new
features
might.
B
A
Okay,
yeah
and
basically
I
I
take
it
as
yeah
unless
you're
changing
something
existing,
don't
even
think
assume
you
can
use
latest
feature.
But
if,
let's
say
if
you're
trying
to
redesign
in
arbor
city
case,
if
we
redesigning
application
details
page
something
which
everyone
uses,
then
we
should
be
a
little
more
careful.
But
the
good
thing
is
we
don't
redesign
it
very
often
and
it's
kind
of.
A
A
A
Great
anything
else.
C
So
I
want
to
see
who
wants
to
volunteer
for
the
next
week's
moderator.
A
C
So
it
could
get
go,
it
went
pretty
well,
so
last
couple
day
actually
was
there's
a
few
questions.
I
I
actually
haven't
got
a
chance
to
do
research
on,
and
I
I
did
ask
someone
to
the
chairman,
john.
Maybe
you
can,
you
know
probably
take
me
a
significant
longer
to
to
come
up
with.
You
know
the
research.
Yes,
but
overall
there
have
been
a
few
questions.
You
know
most
of
them.
C
You
know
straightforward,
I
think
I
would
say
most
and
then
and
then
there's
one
I
you
know
I
think
someone's
looking
for
an
example
for
the
the
vaults
integration
I
think
yeah.
I
definitely
got
a
chance
to
to
take
your
take
up
and
I
deposed
for
the
question
to
the
deaf,
but
I
guess
I
guess
I
still
on
me
trying
to
I.
You
know
it
happened
to
to
to
me
that
it
will.
C
We
also
have
to
do
something
similar
so
similar
research
in
red
hat,
so
so
I'll
follow
up
with
that.
But
overall
it
was
a.
It
was
a
few
questions,
quite
a
few
questions
and
yeah
yeah.
I
think
you
know
it's.