►
From YouTube: The Argo Ecosystem: Tailoring Your Installation Through Comm... Jesse Suen & Alexander Matyushentsev
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
The Argo Ecosystem: Tailoring Your Installation Through Community Add-ons - Jesse Suen, Akuity & Alexander Matyushentsev, Intuit
You are probably already familiar with the core set of Argo projects such as Workflows, CD, Rollouts, and Events. But did you know there is also an entire suite of ecosystem projects which complement these core offerings? These operators unlock support for additional features including notifications, docker registry integration, git writeback, cluster bootstrapping/add-on management, all in a composable way. In this talk, we showcase many of the Argo community projects which will supercharge your Argo installation by providing features outside of the base functionality. Discover ways to custom tailor your setup according to your organization’s needs. Learn about new and upcoming enhancements to make Argo CD even more extensible, including a redesigned config management plugin system, UI component library, and UI/API extensions. Finally, learn how you can even leverage Argo engines and building blocks in your own operators to gain new capabilities, completely independent of Argo!
A
A
First
few
words
about
company,
I'm
working
for
so
I
work
for
intuit,
which
is
a
us-based
tech,
fintech
company
founded
in
1983,
and
we
are
proud
builders
of
products
like
turbotax,
quickbooks
and
mint,
and
so
we
serve
10
000
million
customers
from
all
the
segments
and
into
it
is
a
cncf
gold.
Member
next
jc
continue.
B
So
you
might
be
wondering
like
how
did
we
end
up
with
for
like
loosely
coupled
projects
and
then
a
collection
of
ecosystem
projects,
and
it
all
comes
down
to
some
design
philosophies
that
we
share
about
the
project,
and
so
we
believe
that
all
each
project
should
stay
focused
on
a
specific
use
case
and
and
solving
that
use
case.
Very
well.
For
example,
argo
cd
is
all
about
delivering
manifest
from
a
git
repo
to
kubernetes
clusters
and
a
few
years
back,
we
had
this
need
to
do.
B
B
B
So
it
turns
out
that
kubernetes
has
this
pretty
good
mechanism
for
adding
features
to
resources
in
an
indirect
way,
which
is
annotations
and
annotations.
Allow
us
to
effectively
expand
the
spec
of
a
resource,
but
without
implementing
the
functionality
into
the
core
controller
logic.
The
whole
idea
is
that
you
can
write
your
own
controller,
which
monitors
those
same
resources
and
then
adds
functionality
based
on
those
annotations
and
but
we
think
one
of
the
biggest
benefits
of
adding
features.
B
Well,
the
first
is
you
get
a
much
higher
development
velocity
by
having
a
separate
project?
You
can
iterate
faster
on
that
idea.
You
can
have
a
completely
set
a
separate
set
of
maintainers
you're,
freer
to
experiment
and
make
braking
changes
without
you
know
impacting
the
the
core
users
you
can
give
earlier
access
to
those
features
since
you're
not
tied
to
the
release
cadence
of
the
main
projects,
and
if
the
idea
doesn't
pan
out,
then
it's
it's
okay
to
abandon
it
like
compare
that
to.
B
This
all
helps
to
keep
the
main
projects
lightweight
as
a
separate
project.
The
component
is
optional
and
so
users
who
don't
need
or
want
that
feature
they
don't
have
to
install
it
and
finally,
as
these
projects
mature
and
become
more
stable
and
gather
momentum,
there's
always
that
option
we
can.
We
can
always
formalize
that
and
bring
it
into
the
main
project
down
the
road,
so
we
form
this
sister
organization.
It's
called
argo
proj
labs,
and
this
is
a
place
where
we
can
host
ecosystem
projects
from
the
community
that
complement
the
core
projects.
B
Some
didn't
pan
out,
but
others
are
quite
popular
and
we're
now
at
a
point
where
we're
considering,
including
some
of
these
popular
ones
as
part
of
the
core
projects,
and
today
we'll
be
going
over
a
handful
of
some
of
these
projects
that
enhance
the
argo
cd
experience.
Alex
will
be
giving
a
demo
of
how
you
can
get
more
out
of
argo
cd
with
these
add-ons.
B
Next
we
have
application
sets,
and
the
use
case
here
is,
if
you've
been
using
argo
cd
for
some
time,
you
might
have
felt
the
need
to
automate
the
creation
of
many
applications.
For
example,
maybe
you
run
hundreds
of
clusters
and
you
need
that
same
application
installed
in
each
of
those
clusters
or
another
reason
could
be.
B
Notifications,
this
is
a
project
that
allows
you
to
become
notified
about
state
changes
of
your
applications.
For
example
with
notifications,
you
can
get
a
slack
email,
page
or
duty
notification.
Anytime,
say
one
of
your
application.
Degrades
has
configuration
drift
or
maybe
every
time
just
someone
clicks
the
sync
button
and
we
also
have
a
deep
dive
on
this
service
tomorrow.
B
So
the
back
story
around
this
feature
is
that
as
heavy
rollout
users,
we
wanted
a
way
to
bring
the
role
roll
out
specific
visualizations
into
the
argo
cd
interface,
because,
if
end
users,
if
they're
just
looking
at
the
spec,
it's
really
hard
to
understand.
You
know
what's
going
on:
it's
not
really
user
friendly,
and
originally
we
were
going
to
give
special
treatment
for
argo,
rollout
and
and
bake
that
directly
into
the
argo
cd
code
base.
But
the
more
we
thought
about
it.
B
So
we
came
up
with
this
new
architecture
where
that
allows
users
to
build
and
package
their
own
ui
components
for
any
kubernetes
resource
and
for
that
visualization
to
be
presented
into
the
argos,
cd,
ui
and
so
now
alex
will
be
demoing.
All
these
add-ons
and
you'll
be
able
to
see
these
things
in
combination
in
action.
Awesome.
A
Cool
and
I
want
to
validate
you
see
what
I
see
all
right
and
a
little
preparation
before
the
demo.
Okay.
So,
as
jesse
mentioned,
we
are
going
to
go
through
argo
cd,
specific
add-ons,
and
so
we
thought
that
one
demo
worth
a
thousand
words
and
instead
of
explaining
your
details
and
showing
you
slides,
we
can
just
show
you
all
these
addons
in
action.
A
So
before
I
start
the
demo,
I
just
wanted
to
highlight
that
this
url
is
a
public
github
repository
url.
That
has
all
the
materials
you
need
to
do
the
demo
yourself.
So
if
you're
interested
just
clone
it
and
use
the
readme
file,
it
has
all
the
descriptions
of
all
the
steps,
and
one
thing
you
would
have
to
do
is
to
go
through
some
preparations.
A
A
And
finally,
you
will
need
argo
cd
because
it's
kind
of
a
tool
to
drive
the
demo,
and
so
it's
just
easier
to
do
the
demo
and
see
what's
happening
using
argo
cd
and
just
for
the
sake
of
time.
I
did
it.
I
already
have
it
running
on
my
mini
cube,
and
so
we
are
here
right
now,
so
we
are
ready
to
take
a
look
at
argo,
cdui
and
start
you
know
using
it.
A
Let
me
go
ahead,
open
the
url,
and
so,
if
you
don't
know,
this
is
how
argo
cd
user
interface
looks
like
as
soon
as
you
install
argo
cd.
So
there
is
an
empty
page,
no
applications
and
we
are
about
to
create
few
and
before
I
create
I
kind
of
want
to
explain
like
what
am
I
trying
to
achieve,
and
so
my
goal
is
to
use
this
github
repository
to
represent
the
target
state
of
my
cluster
and
manage
it,
and
there
are
different
ways
you
can
do
it.
A
I
chose
to
just
create
a
folder
for
a
namespace
and
each
folder
here,
so
it
represents
a
namespace
in
the
target
cluster
and
it
has
some
manifests,
and
so
this
is
one
example.
So
we
have
argo
cd
folder,
which
represents
argo
cdnm
space
and,
as
you
can
guess,
it
has
argo
cd
yamas.
I
didn't
want
to
copy
a
bunch
of
yaml
files,
so
I
just
use
customize
config
management
tool
to
pull
a
lot
of
manifest
together,
and
this
is
it.
This
is
the
customize
yaml
file.
It
includes
argo
cd,
stable
manifests.
A
D
A
Ready
to
start
using
cargo
cd
and
create
applications
and
start,
you
know,
pull
this
manifest
into
the
target
cluster.
If
you're
a
user
of
argo
cd,
you
kind
of
know,
one
way
to
do
it
already.
Typically,
you
can
switch
to
argo
cd
user
interface
and
create
new
application
by
clicking
new
application
button,
you
would
have
to
fill
some
information
here,
specify
the
repo
url
and
so
on,
and
this
is
maybe
not
the
best
possible
way.
A
And
so,
if
you
remember,
I
had
four
four
such
folders
and
it's
supposed
to
create
those
applications.
The
folder
name
goes
into
the
application
name
as
well
as
into
the
target
namespace
and
plus
I
configured
these
apps
to
self-think
like
as
soon
as
applications
created.
They
should
just
create
resources.
A
If
name
space
is
missing,
the
namespace
will
be
created
and
hopefully,
if
all
went
well,
yeah
we've
got
four
applications
as
expected,
so
applications
had
created
these
apps
for
us,
and
so
we
have
one
for
argo
cd.
We
have
argo
reloads.
We
have
ingress
because
I
needed
it
for
my
demo
and
we
have
one
application
that
I
want
to
focus
on.
It's
a
demo
up.
It's
still
syncing.
A
I
know
the
reason
is
basically
minecraft's
not
yet
up
and
argo
cd
keep
basically
retrying
to
create
ingresses
so
that
eventually,
basically
as
soon
as
ingress
controller
mutating
hook
is
up,
ingresses
will
be
created
done
so
basically
here
I
should
step
back.
I
think
and
explain
what
you
are
seeing.
A
If
you
are
not
a
user
of
argo
cd,
you
might
not
know,
but
this
is
a
argo
cd
application
details
page
and
the
goal
of
this
page
is
to
explain
to
you
which
resources
are
part
of
your
application,
and
so
you
might
find
see
you
might
see
here
that
we
have
two
kubernetes
services.
We
have
couple
ingresses,
nothing
fancy
one
object
is
interesting.
It's
a
argo,
rollout
object
that
manages
one
replica
set
and
few
pods
in
in
the
in
the
cluster
so
and
you
can
use
argo
cd
ui
to
learn
more
about
these
resources.
A
Much
enough
for
you
to
understand
what's
happening
with
the
reload,
except
there
is
a
caveat.
You
must
know
that
yaml
structure
you
have
to
you,
know
scroll
down
and
and
maybe
find
status
of
this
rollout
and
understand
what
it's
doing
now.
You
will
have
to
go
through
the
spec
to
understand
what
will
happen
when
update.
D
A
And
so
that
requires
it's
not
the
best
possible
user
experience
and
we
can
definitely
do
better
and
thanks
to
argo
cd
extension
addon,
we
have
this
new
tab
called
more.
If
you
click
on
it,
you
will
get
a
rollout
dashboard
that
visualizes
the
state
of
our
load,
and
I
guess
I.
I
really
think
this
is
like
way
better,
because
without
looking
at
yaml,
I
immediately
know
that
this
rollout
is
supposed
to
use
canary
deployment
in
case
of
a
change.
A
It
has
eight
steps
defined
in
the
canary
strategy
right
now
we
have
just
a
single
revision
with
five
pods
and
I
have
all
of
them
all
these
ports
uses
this
particular
image.
Argo
approach,
rollout
demo
and
tag,
is
blue
and
it's
important
to
remember
it,
because
we
will
be
changing
it
soon,
and
so
we
also
have
visualization
of
steps.
A
It's
kind
of
not
very
interesting
now,
because
rollout
is
not
running
any
canary
and
to
demonstrate
your
real
power
of
that
ui.
I
want
to
change
this
reload
and
start
the
canary
upgrade,
and
you
will
see
how
how
it's
really
useful
to
use
this
ui
to
understand,
what's
happening
with
reload
and
of
course
there
is
a
simple
way
to
make.
This
change
maybe
use
cube
ctl
edit.
A
The
github's
way
is
to
go
into
the
git
repository,
make
a
change
in
a
yaml
file,
but
we
are
here
to
see
the
power
of
addons
and
that's
why
I
will
be
using
argo,
cd
image,
updater
and
just
as
a
reminder.
The
goal
of
the
project
is
to
automatically
make
the
changes
in
git
for
you,
and
I
will
have
to
run
couple
more
cele
commands
to
do
it.
A
A
It's
another
patch
to
the
application
set
that
inject
a
set
of
annotations
and
as
jc
mentioned,
we
use
annotations
to
to
enable
the
features
provided
by
by
the
add-ons
and
let's
take
a
look
at
the
annotations
annotations
are
here,
so
I
have
a
json
patch
that
was
used
in
the
cube,
ctl
patch
command,
and
so
we
have
not
so
much
stuff.
Here
we
have
two
groups
of
annotations:
one
explain
image
updater,
how
exactly
images.
A
I
also
specified
a
pretty
simple
update
strategy
called
name
and
what
it
does
is
just
list
all
the
tags,
compare
them
as
strings
and
pick
the
latest.
So
it's
not
real
life,
and
basically
I
would
encourage
you
to
use
something
else,
for
example
semdor.
Yes,
so
you
can.
If
you
take
the
following
same
your
notation,
I
would
use
that
and
finally
notifications,
it's
even
simpler
than
image
updater.
So
what
I'm
that
annotation
is
saying
is
that
we
want
to
get
notified
about
this
thinking.
A
A
A
If
I
click
create
pull
request
button,
you
can
preview
what
is
about
to
be
changed
and
you
will
see
a
argo
cd
application,
specific
file
that
has
a
set
of
settings
that
explain
to
customize
that
image
should
be.
The
image
text
should
be
changed
to
yellow
and
I'm
just
going.
I
like
it.
Basically,
this
is
what
I
expected
to
see.
So
I'm
going
to
approve
and
merge
this
pr.
A
A
A
There
is
canary
upgrade
happening,
live,
and
so
this
panel
now
make
more
sense,
so
you
can
see
that
we
are
at
the
step.
Two
actually
first
is
already
completed,
and
so
the
first
step
was
supposed
to
roll
out.
It
was
supposed
to
create
a
new
version
of
application,
but
it
should
have
only
20
percent
of
all
the
posts
we
have,
and
you
can
see
that
we
did
get
second
revision,
which
has
only
one
port.
A
A
C
A
Is
done
and
I
wanted
to
share
with
you
some
information
about
what
it
takes
to
create
an
extension
and
how
you
can
work
on
it
to
add
visualization
of
custom
resources
you
care
about
in
argo
cd,
so
of
course
you
will
have
to
install
the
add-on
itself,
and
this
is
the
first
url.
It's
just
a
you
know,
pointer
to
readme
file,
which
has
installation
instructions.
A
A
If
you
want
really
fancy
extension,
we
can
help
you
as
well.
So
the
last
url
is
a
github
repository
that
has
a
set
of
reusable
react
components
that
we
already
use
to
build.
Argo,
workflows,
argor
loud
and
argo
cdoi,
as
well
as
argo,
rollout
extension,
ui
uses
the
same
library,
and
so
what
that
library
is
is.
As
I
said,
it's
a
set
of
react
components
and
all
of
them.
Look
like
argo.
That's
why
you
don't
have
to
repeat
the
same.
A
You
know
same
css
styles,
if
you
want
your
extension
to
be
kind
of
fit
nicely
into
argo
ui,
and
this
is
not
the
end
we
we
are
like
really
excited
about
the
feature
and
we
plan
to
keep
working
on
it.
We
are
hoping
to
get
more
extension
types,
the
ones
that
you
can
embed
into
sidebar
application
level
extensions
and
we
are
already
working
on
another
way
to
extend
our
ocd.
A
We
call
this
feature:
config
management,
plugins,
v2
and
idea
that
we
want
end
users
to
be
able
to
add
support
for
config
management
tools
such
as
cdk
otanka
by
grafana
in
argosy
dui,
and
get
kind
of
almost
first
class
user
experience,
and
this
is
it.
This
is
end
of
the
demo
and
the
presentations.
Thank
you
for
listening.
D
A
Events
actually
argo
events
are
to
consume
events
and
do
and
create
a
kubernetes
resource.
That's
how
I
understand
it
so
idea
that
it
can
connect
to
a
lot
of
sources
and
eventually
create
resource,
and
I
guess
the
most
frequently
created
resource
is
argo,
overflow
and
so
argo
notification,
notifications,
kind
of
only
support
one
source,
which
is
a
crd
that
it
watches
and
you
know,
react
on
changes,
but
it
kind
of
it.
So
you
cannot
select
the
source,
but
you
have
a
variety
of
destinations
where
the
notification
can
be
delivered,
it
could
be
slack
telegram.
F
B
Yeah,
so
it's
this
is
actually
powered
by
argo
rollouts,
which
you
don't
need
argo
cd
to
do
it,
but
the
way
rollouts
works
is
it
does
integrate
with
like
ingress
controllers
or
service
meshes,
but
for
what
I
call
the
the
basic
canary
you
don't
need
that
in
the
way
it
works
is,
if
you
want
a
certain
percentage
of
traffic
to
reach
the
new
version
you
can
think
about.
Is
we
just
deploy
the
percentage
of
overall
pods
of
that
new
version?
F
A
D
A
A
A
Yeah,
so
argo
cd
already
supports
at
least
two
type
of
sources.
One
is
git
and
second
helm
chart
and
the
criteria
like
we
wanted
in
order
to
import
important
source.
We
need
to
make
sure
this
source
has
some
notion
of
versioning,
basically
an
s3.
I
guess
it's
like
it's
a
hard
requirement
for
s3.
I
think
like
in
your
case,
I
would
recommend
to
run
a
sidecar
in
argo
cd,
repo
server.
A
That
sidecar
can
you
know
continuously
download
s3
can
bucket
content
and
if
it
is,
let's
say
a
terrible
of
the
git
repository,
you
can
unzip
it
into.
You
know
local
file
system
and
point
argo
cd
to
that
file
system,
and
I
just
know
that
trick
because
I
think
I
spoke
with
one
of
the
users
and
they
did
that
so
argo
city.
Can
it
doesn't
care
where
your
repo
is?
It
can
be
just
on
a
local
file
system
and
yeah.
F
C
B
Yeah
yeah
secrets
is
a
common
issue.
I
think
I
would
say
overall
with
just
git
ops,
not
necessarily
argo
cd
and
because
every
organization
has
their
different
postures
and
tools
and
stuff
that
they
prefer
to
use
for
managing
secrets,
and
it's
it's
possibly
easy
to
get
down
on,
like
a
rabbit
hole
of
adding
integrations
right
to
like
fault
or
either
a
secret
manager.
All
these
things,
and
thus
far
we
wanted
to
avoid
that
integration.
Rabbit
hall.
B
That's
all
the
reason
why
notifications
spun
out
as
a
separate
project
too,
because
you
know
there's
no
end
to
notification
services
that
that
you
could
end
up
supporting.
So
I
do
think
there's
there's
a
future
where
you
know
there
is
something
like
a
argo
notifications,
but
for
secrets
right,
like
a
extensible
way
where
organizations
should
can
bring
in
what
they
want
to
use
for
their
secret
management
and
and
plug
it
into
argo
cd.
B
We
just
didn't
want
to
build
that
direct
integration
into
argo
city
core,
because
we
actually
learned
our
lesson
with
config
management,
where
we
first
support
the
case
on
it
and
then
json,
and
then
we
can
start
getting
requests
for
tonka
and
all
these
things.
So
the
idea
is
that
we
want
to
do
this
in
an
extensible
way
where
we
don't
have
a
strong
built-in
vendor
support
like
for
specific
vendors.
E
There's
also
a
session
yesterday
called
it's
a
secret
managing
your
secrets.
The
github's
way
talking
about
nargo
cd
vault
plug-in.
So
if
you
missed
that
that
might
be
worth
looking
into
as
well,
and
with
that,
I
think
we're
we're
out
of
time.
So
if
you
have
any
more
questions,
please
take
them
outside
and
clear
the
room
and
we'll
continue
the
discussion
outside.
Thank
you.
Everyone.