►
From YouTube: Argo Contributors Office Hours Feb 17th 2022
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
B
A
To
the
contributors
meeting,
I'm
going
to
be
your
host
today.
My
name
is
leo
and
let
me
start
sharing
my
screen.
A
So
going
with
the
agenda
for
today,
starting
with
the
triage
and
discussions
for
the
next
week
schedule.
So,
let's
starting,
let's
start
from
the
last
week
primary
and
secondary.
So
we
have
jesse
and
john
jesse.
C
We
actually
went
pretty
smoothly,
there's
no.
No,
I
I
tried
to
close
some
enhancement
requests
that
it
was
like
very
little
chances
that
we
would
end
up
doing
a
yeah.
No,
nothing
big
to
report.
A
Okay,
thank
you.
So,
let's
decide
for
next
week
it's
been
a
while
I'm
not
helping
with
the
triage.
So
I
volunteer
myself
to
be
maybe
primary
for
next
week.
A
All
right-
and
that
covers
the
planned
topics,
so
if
somebody
has
some
some
topic
to
add,
feel
free,
the
rise
is
going
to
be
a
really
really
short
meeting
today.
B
I
can
give
a
just
quick
update
about
2.3
release,
it's
delayed
as
usual,
but
right
now
we
have
just
two
things
to
worry
about
one:
we
have
security
enhancements
that
we
want
to
include
in
to
the
three
and
right
now
all
pls
are
open
and
basically
soon
will
be
merged,
and
we
have
two
again
open
pis
for
application
set.
We
just
need
to
merge.
B
As
I
understand
we
just
need
to
merge
one
pr
that
introduces
arm
64
image
and
second,
we
need
to,
I
guess,
have
another
release
of
application
set
which
has
image
changes
and
we
need
to
update
our
cd
make
our
qcd
pull
in
the
latest
application
set
version,
and
we
should
be
done.
I
think
that's.
D
C
D
D
One
thing
we're
talking
about
and
if
you
want
to
do
is
bring
in
more
data
into
the
argo
cd
user
interface
and
by
the
way
I
mean
you
know
my
my
team,
and
particularly
we
want
to
bring
in
kind
of
application
telemetry
in
there
as
well
and
a
way
to
get
into
whatever
the
telemetry
system
is
is
surfaced,
and
I
actually
think
this
might
be
quite
useful
for
roll
outs
as
well.
D
Currently,
you
can
kind
of
build
a
user
interface
plug-in
that
allows
you
to
render
a
particular
resource,
which
is
which
is
great,
but
it's
kind
of
limited
to
resource
orientated
data
in
kubernetes
and
actually
there's
quite
a
few
other
kinds
of
data
that
might
be
interesting
to
bring
into
the
user
interface.
D
So
I've
raised
this
issue
here,
but
I'm
kind
of
inspired
by
this
feature
in
backstage
called
plugins.
So
I'll
just
give
you
a
quick
overview
of
that,
because
I
think
it
might
explain
my
thinking
better
than
I
would
myself.
So
I'm
just
going
to
choose
a
plugin
at
random
from
the
selection.
D
It
wasn't
random
as
a
joke,
so
in
backstage
you
can
basically
add
new
routes
to
your
api
server
that
back
proxy
through
to
another
system.
So
the
argo
cd
server
sits
in
the
front,
providing
authentication
for
users
and
slr
ssl,
that
kind
of
business
tls
and
then
requests
a
particular
endpoint
effectively
get
proxied
through
to
another
application.
D
So
you
basically
provide
this
proxy
configuration.
Obviously,
you've
got
to
write
your
back-end
application
as
well,
and
then
you
provide
some
kind
of
plug-in
components
to
it.
Much
like
the
system
we
already
have
for
rollouts,
which
then
appears
in
the
user
interface
and
then
there's
some
additional
configuration.
And
then
you
go
in
this
example,
and
it
shows
us
at
random
I'll
go
cd.
You
have
a
now
argo
cd
in
your
user
interface,
so
that's
kind
of
where
I'm
coming
from
from
in
my
solution.
D
Sorry
I
closed
it
and
went
back
so
I
think
there's
a
few
kind
of
interesting
use
cases
where
you
can
bring
in
additional
data
into
the
application
about
the
application,
I'm
not
kind
of
proposing
we
step
into
the
space
of
backstage
actually
in
terms
of
turning
argo
cd
into
a
developer
portal.
I
don't
think
that's
probably
the
right
direction
for
it,
but
bring
that
additional
information
in
there
is
quite
good.
There
are
some
stuff
around.
D
I
won't
go
into
the
security
aspect
of
like
preventing
dos
attacks
on
those
and
how
to
do
r
back
for
those
endpoints.
Just
a
few
notes
here.
I
just
wanted
to
bounce
this
idea
off
people
and
see
if
anybody
else
had
thought
about
something
like
this
recently
and
what
they
think
about
this
and
what
ideas
they
might
have.
C
Actually,
the
proxy
approach
is
the
original
proposal
we
had
for
argo
cd
extensions
when
we
wanted
to
extend
it
to
show
the
rollout
ui,
because
we
wanted
we.
The
plan
was
to
bake
all
the
functionality
and
endpoints
in
the
rollout
dashboard
somehow
and
then
for
the
proxy
to
actually
proxy
requests
to
show
the
the
rollout
info
and
inside
the
argo
cd
ui.
But
I
think
we
were
concerned
with
the.
C
I
guess
the
complexity
to
get
that
to
work,
and
then
luckily
we
figured
out
a
way
to
do
it
all
with
like
just
static
front-end
front-end
snippets.
D
That
said,
yeah,
I
don't
think
I'm
suggesting
changing
how
the
front
end
extension
mechanism
works
at
all.
Actually,
I'm
going
to
keep
that
the
same,
but
extend
the
extensions
to
allow
you
to
add
back
end
routes.
Maybe
roots
is
not
the
right
word.
Maybe
api
endpoint
is
a
better
word.
B
I
think
it's
at
least
I
think
I
understood
what
you're
talking
about,
and
I
guess
I'm
so
we
we
were
considering
to
it
custom,
ipis
kind
of
fix.
You
know
the
way
to
extend
argo,
cd,
api
and
argo
would
just
proceed
to
something
else,
and
then
we
landed
on
current
design
because
we
were
just
looking
for
this
simplest
possible
implementation
and
so
guessing.
If
we
have
a
use
case
that
is
not
covered
by
current
design,
then
we
can
consider
ips
right
now.
B
We
kind
of
just
we're
just
saying
if
you
want
to
show
something,
make
sure
that
data
is
in
in
the
resource
that
you
want
to
visualize,
and
then
you
don't
need
api.
It's
kind
of
you
get
this
cheap
account,
which
is
kubernetes.
D
Yeah
yeah,
I
I
get.
I
get
that
and
I
I
wouldn't
be
proposing
this.
If
I
didn't
think
that
was
that
would
work
and
the
reason
that
doesn't
work
but
well
is
well
fundamentally,
you
know
we
don't
want
a
lot
of
throughput
on
any
resources
within
the
system
and
something
like
a
time
series
data.
You
know
like
a
graph
of
data
points
of
something.
That's
you
know
500
areas
of
my
application.
D
That's
an
awful
lot
of
data,
and
that's
I
mean
if
you
put
that
throughout
set
d,
you
can
imagine
everything
will
start
working
properly,
whereas
if
it
comes
through
like
an
a
it
basically,
I
want
to
go
to
not
just
kubernetes
to
get
my
data.
I
want
to
go
to
another
system
to
get
the.
D
I
want
to
enrich
that
data
with
data
from
another
system
and
rather
than
just
making
it
very
specific
about
application,
telemetry
endpoints,
I
thought
maybe
it
would
be
better
to
have
a
general
solution
that
does
that
that
allows
I
I
actually
not
sure
how
many
things
people
would
want
to
do
with
it.
D
If
you
look
at
the
backstage
plugins,
there
are
a
lot
of
things
around
ci
in
there.
I
don't
know
if
you
want
to
bring
ci
system
ci
information
into
marco
cd.
C
I've
actually
yeah
I've
had
some
thoughts
about
this
for
a
while
now
so
I
think
so.
It's
for
the
ones
that
you
highlighted,
like
splunk
page
of
the
prometheus
wavefront
open
telemetry
for
those
type
of
things.
I
actually
felt
like
we're,
never
going
to
be
as
good
as
the
original
ui
and
anything
we
we
attempt
on
the
argo
city
extension
front.
C
C
On
the
other
hand,
there
are
extensions
that
I
feel
we
need
to
bake
into
the
argos
of
the
ui
for
us
for
a
lot
of
these
optional
ecosystem,
add-ons
things
like
set
and
notifications
and
image
updater.
I
I
don't
want
all
of
these
to
be
actually
first
class
out
of
the
box
like,
like
always
on
features,
because
I
think
we
always
need
to
have
a
lightweight
version
of
vargo
cd
for
people
who
just
want
to
run
it
at
the
edge
or
in
a
more
lightweight
mode.
C
So
I
do
think
that
ui
and
has
to
have
some
extension
mechanism
to
kind
of
like
okay.
I
need
an
easy
way
to
you
know
play
around
with
notifications
or
app
sets
or
image
updater
or
all
those
things,
and
I
think
that's
actually
where
we
can
extend
the
ui
for
not
just
the
ecosystem
stuff,
but
for
probably
maybe
the
things
that
you're
thinking
about
in
this
proposal.
D
I
I
I
struggle.
I
don't
know
if
anybody's
had
any
thoughts
on
this
with
kind
of
knowing
where
to
put
extension
points
into
the
user
interface,
because
it's
hard
to
know
where
people
will
want
them
until
people
want
them,
and
so
you
have
kind
of
a
catch-22
situation.
It's
like
okay.
Somebody
wants
an
extension
point
when
you
click
the
sync
button,
something
else
pops
up
between
the
sync
button
and
the
next
page,
but
you
can't
know
until
somebody
asks
that,
so
you
can't
provide
it.
D
C
Less
about
that,
but
like
to
things
like
just
like
configuring
notifications
right
like
the
experience
for
that,
is
that
you
have
to
set
an
annotation
on
it
and
understand
the
you
know
the
format
for
that
and
then
some
right
now
we're
going
in
a
direction
where
they
might
have
to
write
yeah
I'll
snip
it
inside
the
annotation
itself.
And
you
know
that
experience
could
be
made
simpler
through,
like
a
simple
ui
pane
that
understands
that
format
and
just
presents
form
fields
to
let
them
manage
their
notifications.
B
B
Yeah,
so
even
notifications
might
benefit
from
it,
but
I
think
it's
a
it's
kind
of
a
big
commitment
if
you
want
to
support
exchanging
apis.
That
means
you
also.
There
is
a
lot
of
security
questions
plus
like
you
want
to
when
we
thought
about
it
for
allowance.
We
also
kind
of
we
realized
that
we
would
have
to
build
an
api,
and
then
you
need
to
run
that
api
in
a
reliable
manner.
So
it
should
be.
You
need
at
least
few
replicas,
and
so
I
think
it's
just
like.
B
If
you
really
really
have
strong
use
case,
then,
where,
like
in
case
of
notifications,
I
would
still
say:
okay,
I
I
better
not
have
auto
completion,
because
it's
maybe
not
the
most
important
features
of
argosy,
because
api
is
just
so
much
work,
and
so,
like
so
much
complexity,.
D
Yeah
yeah
yeah,
when
you
said
it
to
me,
I
thought
well,
there's
a
lot
of
lifting
to
be
done
to
just
do
a
small
feature:
yeah,
that's
fine!
Okay,
that's
cool!
That's
interesting
and
feedback
that
that
kind
of
chimes
a
bit
with
what
I
was
thinking
about
in
terms
of
the
experience
you
can
provide
and
I'll
go
see
it's
hard
to
provide
a
good
experience
to
somebody
else.
D
Are
people
asking
for
anything
like
this?
I
mean
there
is
the
other
benefit
of
doing
stuff
like
this.
Is
it
allows
you
to
grow,
but
that
doesn't
feel
like
an
issue
for
argo
cd.
C
I
mean
that
was
the
other
point
I
was
going
to
make
so
when
we,
when
we
first
did
the
the
ui
extensions,
the
resource,
extensions,
I'll
call
it.
I
was
expecting
a
lot
more.
You
know
community
excitement
and
I
guess,
like
oh
wow,
yeah,
look
at
what,
like,
with
the
rollout
being
the
poster
child
like
or
the
reference
examples
like.
Okay,
look,
what's
possible
with
rollouts
now,
and
I
thought
the
community
would
take
off
with
their
own
extensions
and,
like
nothing's,
really
happening
with
that.
C
C
This
is
small
that
we
would
use,
but
I
do
think
once
again,
if
you
want
to
keep
make,
I
I
do
like
the
idea
if
it
helps
keep
the
the
core
of
argosy,
be
lightweight
and
like
not
having
forcing
us
to
like
bake
in
all
this
functionality.
C
D
That
yeah,
because
the
value
of
an
extension
system
is
really
like
the
ecosystem
around
it
and
if
the
ecosystem
doesn't
grow.
You've
kind
of
told
yourself
you've
shown
to
yourself
that
it's
it's
not
maybe
a
very
good
idea,
or
it's
not
going
to
do
what
you
want.
Not
not
that
it's
not
a
very
good
idea,
but
rather
it's
not
going
to
build
the
eco.
The
ecosystem
didn't
appear,
so
it
won't
improve
the
community
in
the
ecosystem.
I
think
you're
saying
that
or
I
would
that's
how
I
didn't
talk
about
that.
C
Yeah,
but
it
it
maybe
just
takes
time.
You
know
that
it
took
some
time
for
plugins
to
take
off
it's
going
to
take
some
more
time
for
plugins
v2
to
take
off
so
I
mean
I
was.
B
C
Like
surprised
about
all
the
plugins
v1
plugins
that
like
popped
up,
but
it
just
took
like
a
year
before
you
know,
people
started
creating
coupon
sessions
about
the
vault
plugin,
and
you
know
those
type
of
things
so.
D
C
But
yeah
now
this
is,
and
I
always
mention
like
the
direction
I
saw
the
extension
mechanism
going
with,
for
you
know
not
just
the
resource,
the
but
sidebar
extensions
and
application
view
extensions,
and
I
think
the
only
thing
that
I
think
we
need
to
tread
lightly
on
is
if
we
need
a
proxying
backend
component
to
this
versus,
if
we
can
do
things
in
purely
from
just
form,
edits
and
front-end
stuff
that
modified.
D
Yeah,
that's
interesting.
I
was
thinking
about
this,
but
maybe
like
a
telemetry
button
would
appear
in
the
toolbar.
When
you
click
on
that
a
drawer,
a
drawer,
a
drawer
drawer,
would
appear
from
the
right
hand
side.
I
think
drawer
is
a
real
work.
A
drawer
would
appear
from
the
right
hand,
side,
and
that
will
contain
your
component.
That
will
make
your
apical
requests
and
that
your
extension
points
would
be.
You
know,
extension
give
me
give
me
new
application
buttons.
An
extension
give
me
new,
you
know
what
what
goes
behind
that
button.
Yeah.
Would
I
frames.
C
This
would
be
things
you
know
being
configured
in
the
that
we,
in
our
extension,
make
sense
to
permit
from.
C
I
mean
if
similarly,
we
like,
we
would
have
to
like
to
say
yes,
it's
safe
to
visit
this
other
url
embedded
in
this
iframe,
and
then
I
don't
know
if
you
know
you
find
that
one,
but
I'm
assuming
that
it's
possible
for
the
user
to
not
have
a
broken
experience,
but
still
using
iframes.
I
I.
D
I
think
there's
I
mean,
from
the
security
point
of
view,
embedding
third-party
code
into
your
web
pages.
I
think
people
do
quite
commonly
things
like
trackers
and
so
forth,
but
you
know
you
always
install
those
from
a
representative.
All
sorts,
don't
you,
but
with
an
ecosystem
of
plugins
you've
got
this
kind
of
interesting
tension
between
you
know.
How
do
I
trust
this
plugin?
How
has
it
been
validated
who's
who's?
What's
his
provenance
versus,
I
want
lots
of
plugins
to
grow
the
ecosystem.
D
You
need
to
get
the
right
balance
between
that,
because
you
don't
want
people
to
be
storing
an
argo
cd
plug-in
really
nearly
and
finding
out
it's
exfiltrating.
All
your
kind
of
secrets
from
it
so
may
need
a
way
to
sandbox
those
user
interface
plugins
to
say.
Well,
you
know
you
only
know
about
you
know
we'll
instantiate
the
plug-in
with
a
series
of
parameters,
but
you
shouldn't
be
able
to
escape
that
sandbox.
D
E
E
That's
to
me
is
more
key
at
this
moment,
since
we
are
being
more
not
criticized,
maybe
more
blocked
by
more
about
security,
posture
and
those
things.
So
this
maybe
open
up
more
attack
surface
there
yeah.
D
E
I
know
it's,
I
know
it's
it's
a
little
bit
sad
to
using
that
reason,
but
it's
kind
of
like
the
reality
we
are
facing
so
but
there's
I
mean.
D
E
D
A
Okay,
thanks
alex
anything
else,
any
other
topic
someone
someone
would
like
to
to
bring
up
for
this
question.