►
From YouTube: Argo Contributor Experience Office Hour 28th Jan 2020
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
A
Okay
and
we
had
a
lot
of
topics
today,
first
was
proposed
by
shobik,
but
I
think
sharma
will
have
to
speak
about
it,
so
that
the
question
was:
how
did
your
first
week
of
github
discussion,
moderator
well
and
I
think
yeah.
The
question
is
like:
what
can
we
improve,
or
should
we
just
keep
doing
that.
B
So,
for
me
it
was
a
good
learning
like
I
had
to
go
through
the
code
and
the
slack
channels
and
ask
few
people
to
understand
like
to
get
the
answer
and
it
it's
not
that
difficult
like.
Sometimes
you
can
just
google
what
the
person
is
asking
and
the
first
link
is
the
answer
so
yeah.
It
was
a
good
experience,
but
I
think
so
we
I
think
we
should
decide
some
kind
of
goal.
So
there
are
few
questions
which
are
already
answered,
so
it's
like
whether
to
whether
to
like
go
in.
A
That's
my
understanding.
I
guess
you
won't
ask
me
open
questions
as
possible,
but
this
is
how
I
thought
about
it.
B
A
Awesome,
and
did
you
like,
did
you
notice
how
many
new
questions
did
you
get
on
average.
B
A
All
right-
and
I
noticed
we
used
to
convert
some
github
issues
to
discussions,
because
some
github
issues
are
basically
questions
and
then
that
feature
disappeared
from
github.
Now
it's
back
and
I
think
we're
going
to
it
will
flow
a
little
bit
more
questions
into
github
discussions.
C
D
Once
in
a
while,
so
I
think,
okay,
thank
you
genre.
A
D
Yeah
but
devon,
just
noted
in
the
chat
before
you're
moving
sorry
to
interrupt
you
before
moving
to
the
next
topic.
There's
there's
one
new
person
in
the
call.
Oh
I'm
sorry,
yeah
and
devon,
just
noted
it
and
maybe
ishita
can
introduce
him
or.
E
E
F
G
E
D
E
Yeah
so.
G
H
She
actually
was
she
joined
us
at
the
beginning,
like
she
was
an
intern.
Now
she
is
she's
a
full-time
she
actually
been
introduced
when
we
were
first,
you
know
get
together
at
this
group
and
and
then
her
internet
was
finished
and
then
went
back
to
finish
school
and
announced
she's.
Just
to
tell
john
has
to
full
time
now
in
my
head
ever
had
so
yeah
welcome.
E
A
Awesome
right,
okay,
so
next
topic
is
status
of
application.
Sets
it's
true
because
that
you
jonathan
yep
yep.
F
Can
you
hear
me?
Okay,
yes,
cool
yeah,
so
over
in
the
application
sets
repository.
I've
created
a
milestone
for
all
the
issues
that
we
want
to
hit
as
part
of
the
argo
cd
integration.
So
that's
things
like
infrastructure
tasks,
tests
docs.
We
want
to
write
bugs.
We
want
to
fix
as
part
of
the
process,
and
I
thought
I'd
just
briefly
give
you
an
update
over
the
kind
of
stuff
that's
gone
in
over
the
last
few
weeks.
F
F
This
is
another
feature
from
the
design
proposal
where
you
can
actually
override
the
contents
of
a
template
with
a
template.
That's
specified
as
part
of
the
generator,
which
is
very
useful,
and
we've
also
got
support
for
arbitrary
key
value
pairs
on
the
cluster
generator
that
was
from
michael.
So
that
was
also
awesome.
F
So
those
are
the
new
features
that
have
gone
in
over
the
past
few
weeks.
We've
got
a
bunch
of
tests
and
infrastructure
prs
that
went
in
as
well.
I
added
a
new
end-to-end
test
framework
which
runs
application,
set
ede
tests
against
kubernetes
and
against
argo
cd
on
every
commit
as
part
of
a
github
action.
F
F
New
tests
and
infrastructure
in
place
new
documentation,
in
addition
to
a
few
new
features
from
a
bunch
of
different
folks.
A
G
A
Question
about
how
key
generator
works,
I
basically
we
had
the
discussion
before
like
trying
to
reuse
a
repository
server
versus
you.
You
know,
do
git
operations
in
the
same
port,
where
our
cd
application
set
runs.
Do
which
way?
Did
you
go
at
the
end.
F
F
The
problem
is
that
that
will
miss
some
directories
in
the
git
repository,
so
that
will
correctly
identify
customize
and
helm,
and
I
think
jsonet
applications
within
a
repository,
but
we'll
miss
just
directories
that
contain
plain
yamls,
which
is
not
what
we
want.
I
I
have
a
pr
or
not
a
pr.
I
have
a
branch
where
I've
done
some
work
on
that
I've
not
raised
it
against
argo,
but
there
will
be
more.
You
should
see
more
from
me
in
that
area
in
the
future.
F
The
other
thing
that
we're
doing
is
we
are
actually
calling
git
clone
ourselves
as
part
of
the
it's.
The
files
part
of
the
the
files
field
of
the
git
generator
requires
us
to
have
full
access
to
the
repository
and
again,
if
we
wanted
to
have
repo
server
be
just
like
the
single
point
of
connecting
to
a
git
repository,
we
would
need
to
replace
our
use
of
the
git
cli
with
a
corresponding
grpc
method
in
the
repo
server.
That
would
allow
us
to
get
the
contents
of
a
git
repository.
F
That
is
a
bit
lower
priority
because
we
have
a
solution.
That's
working
for
us
right
now,.
F
Yeah,
so
the
short
version
is,
we
are
calling
list
apps
on
the
repo
server,
but
that's
an
imperfect
way
of
getting
a
list
of
directories
from
the
repo
server
and
we're
calling
the
git
cli,
which
works,
but
there
there's
a
more
elegant
way
to
do
it.
Yes,.
A
And-
and
I
I
wanted
to
mention
that
I
think
we
had
same-
you-
know
problem
with
argo
cd
image
updater.
It
needs
to
have
access
to
git
repository
as
well
and
jan
decided
to
just
kind
of
copy
paste,
a
part
of
argo
cd
first
and
then
make
necessary
changes
and
hopefully
contribute
it
back
and
that
we
tried
we
were
discussing
whether
we
should
just
have
api
instead
of
you
know,
sharing
the
library
library
and
it's
not
clear
what
kind
of
api
is
it
and
that
api
is
going
to
be
and
used
by
argo
cd.
A
So
maybe
it's
good
if
we
both
kind
of
doing
that,
we're
both
trying
to
you
know,
reuse,
parts
of
argo
cd
as
a
you
know,
part
of
code,
fargo
cd
to
make
to
interact
with
git
and
then
finally,
we
will
get.
You
know
requirements
of
two
projects,
and
hopefully
it
will
be
enough
to
create
api.
Finally
or
just
maybe
just
just
move
git
client
from
argo
cd
into
separate
library,
for
example,
into
argo
pkg.
So
this
is
where
we
share
code.
A
D
Yeah-
maybe
maybe
it's
I
think
so
alex
and
me
we.
We
already
had
the
discussion
on
slack
and
so
the
the
current
state
of
the
of
the
repository
server
api
is
like
it's.
It's
a
private
api.
It's
not
well
defined.
It's
changed
on
will
and
stuff
like
that
yeah,
but
maybe
maybe,
if
both
application
set
and
the
image
updater
with
their
use
cases
or
if
they
have
enough
use
cases,
we
can
maybe
sit
together
and
formalize
a
ripple
server.
Api.
A
Yeah
and
so
jan
convinced
me
that
it's
bad
to
have
api,
which
is
not
used
by
you
know
by
this
by
argo,
cd
and
honestly,
I
was
thinking
since
image
of
data
already
import
argo
cd
as
library
kind
of.
Why
don't?
We
just
contribute
couple
more
private
methods
to
git
client
of
api
it
it's.
It
gives
more
flexibility,
and
at
least
in
case
of
image
updater.
There
is
just
no
need
to
have
all
functionality
of
repo
server
image.
A
A
F
D
No,
probably
probably
we
are,
we
both
do
very
different
things:
okay,
but
but
we
have
basically
a
requirement
to
access
repositories
that
are
connected
by
argo
city
yeah.
D
D
So
it
will
read
the
file
and
check
the
contents
of
the
file,
but
mostly
it
was
for
for
committing
back
the
changes,
but
yeah
it's
the
base
requirement
access,
a
repository,
that's
connected
by
august
cd
is,
is
the
same
so,
but
maybe
we
can
discuss
this
together
separately
and
align
our
requirements
and
then
we'll
see.
A
And
my
thank
you,
some
question
about
application
set
jonathan.
How
do
how
do
you
think
how
close
it
is
to
you
know
to
version
one
I
would
say
yeah
to
the
release.
F
Good
question:
I've
got
the
milestone,
that's
set
up.
That
includes
the
list
of
issues
that
I'd
like
to
see.
Not
all
of
them
are
required.
It
is
an
ordered
list.
G
A
F
Next
up
is
the
install
yaml
that
allows
to
update
doc
work,
so
people
know
how
to
use
the
application
set
controller
and
how
to
install
it.
Some
bugs
once
we've
finished
the
dock
work
the
install
work
and
the
bugs
which
is
about
halfway
through
your
screen.
I
think
we'll
be
a
lot
closer
to
being
able
to
put
out
some
form
of
release,
after
that,
it's
just
writing
more
tests,
whether
it
be
more
unit
tests
or
more
ede
tests,
which
is
always
good.
F
A
A
C
A
So
I
already
have
blog
for
argus
identifications,
I'm
trying
to
convince
jan
to
work
on
image
updater
and
I'm
writing
the
blog.
Basically,
it's
my
way
to
test
that
image.
Updater
works
as
well.
You
know,
if
you're
able
to
come
up
with
a
simple
tutorial,
which
is
you
know,
someone
can
run
someone
can
execute
like
in
10
minutes.
That
means
yeah.
It's
kind
of
that's
a
great
sign
and
typically
a
lot
of
bugs
been
found
during
the
process
and
I
suggest
to
do
same
for
application
set.
F
Sounds
good
yeah,
I'm
currently
writing
a
bunch
of
docs
for
application
sets
repo
itself,
so
that
would
be
totally
consistent
with
what
I'm
already
doing.
A
A
A
H
Yeah
yeah,
I
just
wonder
if
everyone,
what
was
your
thoughts
like?
We
can
move
the
time
up
an
hour
or
two,
because
we
have
a
few
foes
from
from
india.
They
would
like
to
join,
but
you
know.
H
H
So
I
don't
know
that's
a
one
hour,
one
hour
two
hours
when
any
possibility.
A
We
want
what
the
the
best
time,
which
is
you
know,
quest
for
majority
of
who
joins
that
meeting.
I
personally
prefer
earlier.
I
would
move
it.
You
know
to
think
basically,
in
our
time
zone
in
my
time
zone,
it's
10
am,
I
would
prefer
it
to
be.
Even
8
am
I
don't
know,
and
then
someone
else
I
think,
would
be
for
9
a.m.
Okay.
Anyone
have
strong
objections
to
move
it
to
nine
two,
basically
to
one
hour,
yeah.
D
It's
not
midnight
here,
but
it's
it's
it's
already
way
in
my
leisure
time,.
A
I
A
A
Yeah
and
I
think
he
started
discussion,
okay,
I
don't
know
if
we
were
supposed
to
discuss
it
again
or
not,
but
I
think
for
now
we'll
have
to
skip
it
and
then.
A
Yeah,
so
maybe
we
can
just
remove
it
and
yeah
agree.
You
can
edit
again,
if
you
need
it
right.
H
I
will
do
it
sometime
not
not
next
week,
still
busy,
so
yeah,
okay.
B
D
B
J
Yeah,
so
I,
and
so
for
colleagues
who
have
been
discussing
on
this
just
trying
to
get
the
idea
of
expected
behavior
and
the
actual
behavior.
So
you
know
in
under
auto
sync:
you
can
have
both
flags
checked,
so
you
could
have
auto
prone
and
you
could
have
self
heal
so
we'd
like
to
understand
that
if
we
uncheck
self
heal
but
still
check,
auto
prone
without
expecting
any
kind
of
resources
that
is
not
in
our
gate
repository
to
be
deleted.
J
If
we
create
it
on
the
cluster,
so
the
behavior
we
are
seeing
like
the
actual
behavior
we're
seeing
is,
let's
say
we
create
a
non-kts
resource,
let's
say
openshift
route.
If
we
create
that,
while
self
healing
is
not
checked,
only
auto
prone
is
checked.
We
are
expecting
this
to
get
deleted,
but
it
doesn't
get
deleted.
If
self
healing
is
checked
as
well,
then
yes,
it
does
get
delayed,
because
self-healing
is
working
as
a
shield
that
I'm
not
gonna.
Let
anything
change
to
your
cluster,
so
we
have
like
few
scenarios
in
our
head.
J
One
is
completely
auto
sync,
unchecked
and
then
operating
checked
and
the
four
four
combinations
of
self-healing
auto
prone
and
for
each
of
these
combination,
what
kind
of
resources
does
get
deleted
and
does
not
get
deleted?
J
A
I
can't
at
least
partially
answer
that
question
so
first,
maybe
I
want
to
talk
about
meaning
of
these
two
flags
so
and
they
are
kind
of
not
you
know
so.
Okay,
so
self
healing
this
decides
when
the
sync
process
should
start.
So
if
self
healing
is
disabled,
then
auto
start
sync
process
only
if
new
commits
got
pushed
into
git.
A
A
So
if
between
these
two
commits
something
changed
in
the
cluster,
argo
cd
will
notice
the
diff,
but
it
will
not
attempt
to
sync
the
change,
because
there
will
not
no
changes
in
git
and
okay
and
if
self
hearing
is
enabled,
then
auto
sync
will
try
to
synchronize
the
change
every
time.
It's
seeing
the
diff
okay
yeah
and
that's
why
it
explains
why
and
auto
prone
is
kind
of
it's
completely
different.
Auto
prone
means
is
argo
cd,
going
to
delete
resources
during
outer
syncing
process
or
not.
Actually,
I
think
it's
not
even
auto
prone.
J
Yeah
like,
for
example,
when
I'm
thinking
when
I'm
seeing
this
from
a
lens
of
let's
say
a
new
user
who's
just
following
the
argos
into
documentation
and
see,
what's
going
on
so
what
I'm
reading
is.
It
says
that
by
default,
so
under
automatic
pruning,
it
says
by
default.
Argo
cd
does
not
delete
the
resources
based
on
the
mismatch
of
your
git
to
your
cluster.
In
order
to
do
that,
yeah
you
should
have
auto
printing
enabled.
So
I
was
asking
that
okay.
J
So
if
I
do
auto
tuning
enabled-
and
I
have
auto
sync
enabled
that
means
as
soon
as
I
create
a
new
resource
that
is
not
in
my
gate
that
would
be
deleted
and
and
then
then
the
other
thing
in
the
back
of
my
mind
was
now:
does
argo
cd
care
about
non-cadence
resources
works
versus
cages,
resources
also
for
the
example
of
a
non-cadence
resource
when
I
could,
because
I
think
kevin
was
pointing
out
that
for
for
core
kubernetes
resources,
still
those
resources
don't
get
deleted,
but
at
least
the
the
test
was
okay.
J
So
let
me
create
a
non-kubernetes
resource,
so
I'm
sure
that
is
expected
to
get
deleted
and
then,
when
it
didn't
get
deleted
then
I
was
thinking.
Maybe
am
I
understanding
correctly.
How
auto
prone
would
work.
A
I
think
there
is
kind
of
I
think
there
is.
I
don't
know
if
there
is
in
ui
auto
prone,
but
I
think
it's
called
just
room
and
basically
the
idea
is
it
doesn't
matter.
How
sync
was
triggered
manually
or
automatically
proven
is
the
flag
that
decides
if
resources
should
be
deleted
during
the
thinking
process
or
not
yeah,
and
I
know
that
there
is
open
issue.
It's
a
not
issue,
it's
a
feature
request,
so
we
have
outer
sinking,
we
have
self
healing
and
they
kind
of
tied
together.
A
J
Okay,
so
if
we,
if
we
think
about
one
test
case,
so
if
we
forget
same
thing
for
now
cell
phone
is
unchecked,
auto
sync
is
enabled
autophone
is
enabled.
As
a
user
I
haven't
done
a
git
commit.
But
what
I
did
is
on
my
cluster.
I
created
a
new
resource
because
it's
auto
sync
I'm
expecting
it's
periodically
doing
a
poll
to
see
if
diff
is
there
and
since
it
sees
a
new
resource
on
my
rvo
city
cluster,
does
it
or
does
a
ldd
delete
this
resource
or
not,
and
the
self
healing
is
disabled?
Is
it.
J
A
D
But
I
think
there's
there's
a
slight
misunderstanding,
because
argo
cd
won't
touch
any
resources
that
it
has
not
created
by
itself.
Oh.
J
So
the
test
I
did
was
argo
cd
immediately
deleted
the
resource
I
created
when
self-healing
was
checked.
D
But
only
so,
if,
from
my
understanding,
this
should
only
happen
if
you
create
a
resource
that
has
the
the
label
on
it
that
argo
cd
uses
to
identify
to
which
application
the
resource
belongs.
D
J
So
I
think
I
I
have
one
proposition
if
the
team
feels
it's
okay,
so
let's
say
if
I
create
a
table
with
all
five
different
settings
and
then
I
identify
some
kubernetes
resources
and
some
common
non-combination
resources
and
I
observe
exactly
what
I
did
and
which
resources
got
deleted
or
not.
And
then,
if
I
share
that
finding
with
the
team
to
see
if
this,
if
this
actual
behavior
is
the
expected
behavior
and
then
maybe
we
can
take
it
from
there.
D
Oh,
it's
app.kubernetes.I,
o
slash
instance
by
default,
so
I
I
know
that
if
you
use
the
hand
chart
it
will
it
will
use
another
label.
If
you
install
iocd
using
the
argo
cd
hunt
chart
the
community
maintained
one.
I.
J
Was
using
like
the
the
regular
cd
operator
and
I
think.
J
A
Oh
yeah,
if
you
want
to
you,
know,
play
with
some
new
rxc
cd
ui
features.
I
suggest
to
take
a
look
at
a
new
logs
viewer,
so
argo
cd
team
at
intuit
recently
got
a
new
engineer,
he's
very
patient
about
user
interface
remington.
So
he
worked
on
pod's
view
and
now
he
focused
on
logs
viewer
and
yeah.
A
Please
give
your
feedback
about
it,
because
it's
getting.
I
think
it's
now
getting
kind
of
feature
parity
with
cube
ctl
logs
recently,
I
remember
I
kind
of
I
would
use
argo
cd
user
interface
to
see
logs
of
a
very
simple
application,
but
it
was
not
as
useful
as
useful
as
cube
ctl
and
I
guess
goal
of
you
know
this
iteration
is
to
really
make
it.
You
know
100
useful.
A
Yeah,
so
I'm
just
going
to
open
it
really
quick
and
show
that
it's
hopefully
working
yeah.
So
the
idea
is
that
it
has
pagination
and
it
even
has
like
light
mode
and
night
mode
and
awesome
follow
unfollow,
and
I
know
that
we
plan
to
add
more
things
like
there
is
already
a
filtering
master
and
ability
to
open
it
in
the
full
screen,
and
I
guess
the
next
thing
is
to
add
previous
port,
and
maybe
that's
it.
I
don't
even
know
what
else
keep
ctl
has
that
this
ui
don't
have
yeah.
J
Since
we
do
have
some
time,
I
want
to
bring
one
of
the
other
issues
to
light.
I
added
in
the
chat
in
the
docs
page
on
the
e2e
there's
a
scale
warning
banner
that
says
this
documentation
is
out
of
date,
but
I
think
many
of
our
colleagues
say
that,
like
the
documentation
is
actually
updated,
it's
just
the
banner
hasn't
been
taken
out.
A
D
A
Okay-
and
I
wanted
it's
a
nice
segue
into
another
question,
so
regina
she
was
working
on
two
things.
Basically
trying
to
she
was
trying
to
add
a
version
banner
for
argo
cd
documentation
when
it's
hosted
on
read
the
docs,
and
the
next
kind
of
part
of
the
same
effort
was
to
create
a
warning
message
which
is
shown
to
user.
If
user
landed
on
all
documentation-
and
we,
I
recently
found
that
actually,
we
already
have
documentation
for
argo
cd,
so
she
already
gets
like
most
of
of
it
ready.
A
Yeah,
so
that
documentation
is
already
live
only
the
docs,
but
basically
just
no
one
knows
it
exists.
It
has
banner
selector,
so
it
has
a
version
selector.
It
doesn't
have
the
banner
yet
and
yesterday
I
realized
that
banner.
I
don't
think
it's
a
you
know,
it
must
have.
Maybe
we
can
go
live
is
what
we
have
like.
What
do
you
think
I
keep
and
the
reason
I'm
asking
is
that
I
keep
seeing
questions
again
and
again
and
people
get
confused
that
they
see
a
description
of
documentation
that
describes
feature
which
is
not
yet
available.
A
A
Switch,
so
if
honestly,
I
don't
see
any
reason.
Why
don't
we
switch
like
now
to
I
mean
not
now
like
today,
for
example,
to
to
that
new
website.
All
we
have
to
do
we
just.
We
would
need
to
create
a
redirect
from
existing
documentation
to
to
do
that,
documentation
to
argo
cd
read
the
docs,
but
it's
not
a
big
kind
of
technically
it's
not
that
difficult.
We
just
need
to
have
one.
You
know.
D
A
So
you
think
maybe
you
want
to
suggest
a
little
kind
of
gradual
approach.
So
first
user
would
open
all
documentation
and
we
would
show
banner
somewhere
at
the
top.
That
says,
a
new
documentation
is
available
here
and
maybe
a
quick.
D
No,
no,
I
think
I
I
was
just
expressing
myself
in
a
complicated
way,
so
we
update
the
url
on
on
the
github
page
and-
and
I
don't
know
anything
in
the
readme
there's
also
to
point
to
to
this
new
url
and
maybe
not
to
latest
but
too
stable,
oh
yeah
yeah.
D
We
can
configure
right,
but
so
many
so
many
people
probably
have
bookmarks
to
to
the
documentation
hosted
on
github
pages.
Yes,
and
so
my
proposal
was
to
to
put
a
banner
on
the
github
pages
version
that
says
this
is
this:
is
an
archive
and
the
new
all
the
new
versions
of
documentation?
All
the
new
stuff
will
come
at
read
the
docs
so
that
the
the
bookmarks
won't
break
for
the
users
and
it's
clear
that
they
are
currently
watching
an
archive
and
not
stable
or
latest
or
whatever
version
yeah.
D
It
would
make
sense,
but
I
I
think
I've
mentioned
it
earlier
in
one
one
earlier
called
it.
I
have
a
complete
restructuring
of
the
documentation
coming
up,
so
basically
this
would
break
all
bookmarks
anyway,
okay,
because
I've
sorted,
I've
resorted
many
things
and
moved
things
around
and
stuff
like
that.
So.
A
I
think
yeah,
that
kind
of
I
think
it's
a
good
compromise.
I
would
in
that
banner
I
still
at
the
convenience.
I
would
put
kind
of
a
quick
link.
You
know
see
that
same
page
in
the
new
documentation
and
then
so
in
the
beginning.
It's
it's
going
to
work
and
then
later
you
know
there
will
be
discrepancy
between
dogs,
but
it's
okay.
So.
A
With
the
banner
so-
and
it's
really
easy
to
to
do
it's
just
it's
small
improvement,
anyone
has
objections
to
move
to.
You
know
we
did
the
dog's
version.
I
mean
we
spoke
about
it
before,
and
I
think
anyone
have
objections
to
kind
of
execute.
That
plan,
which
jan
proposed
to
have
a
banner
here
and
run
github
pages
at
the
same
time
with
read.
The
docs
and
banner
will
basically
explain
to
users
that
there
is
new
version.
A
Sounds
good,
oh
awesome,
yeah
and
I
think
it's
it's
important.
I
we
have
google
analytics
for
august
documentation.
It
keep
amazing
amaze
me
every
time
I
open
it.
There
is
at
least
20
25
people
looking
at
the
documentation
like
in
real
in
in
right
time,
at
the
time
when
I
open
it
and
yeah.
So
it's
like
a
popular
website.
You
know
the
amount.