►
From YouTube: Argo’s Vibrant Ecosystem and Community - Alex Collins, Alexander Matyushentsev & Dan Garfield
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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.
Argo’s Vibrant Ecosystem and Community - Alex Collins, Intuit; Alexander Matyushentsev, Akuity; Dan Garfield, Codefresh
Argo CD is the most popular Kubernetes GitOps application delivery tool. Argo Workflows is the most popular Kubernetes workflow execution platform. I bet you know about the core Argo projects, but what about the massive rapidly growing ecosystem of projects around them? Have you heard of Argo Events, Argo Rollouts, ApplicationSet, Argo CD Image Updater, Argo CD Vault Plugin, Argo CD Autopilot, Hera Workflows? What about tools such as Kubeflow Pipelines, Katib, SQL Flow, Couler, and Ploomber?. In this session, you’ll learn not just about the core Argo projects, but also get the highlights from several ecosystem projects with demos and best practices. You can address many more use cases by teaming them up with each other.
A
All
right
welcome
everybody.
Thank
you
so
much
for
coming
to
our
session.
We're
gonna
be
talking
about
argo
and
this
incredible
community
that
has
sprung
up
over
the
last
few
years.
My
name
is
dan
garfield,
I'm
a
co-founder
chief,
open
source
officer
of
code,
fresh
we're,
an
enterprise
cargo
company,
and
this
is
alexander.
B
C
A
Yeah,
I'm
I'm
absolutely
feel
privileged
to
share
the
stage
with
these
two
who
are
lead,
maintainers
and
absolute
legends
and
contributed
more
code.
I
think
between
them
than
anybody
else.
So
we're
going
to
be
running
through
this
ecosystem,
which
is
incredible
again,
if
you
can
invite
neighbors
raise
your
hand
if
there's
a
seat
open
next
to
you,
because
there
are
a
whole
host
of
people
who
are
looking
for
seats.
A
So
those
in
the
back,
if
you
see
someone
with
a
hand
raised,
go
sit
next
to
them,
they're
asking
you
to
be
their
buddy,
so
buddy
up
so,
like
I
said
we're
going
to
be
talking
about
this
amazing
vibrant
ecosystem.
That
has
been
growing
dramatically
and
there
are
a
lot
of
opportunities
for
you
as
community
members
to
join
in
and
take
advantage
of
these
things.
A
We
already
introduced
ourselves
for
those
of
you
that
are
familiar
with,
maybe
just
part
of
the
project
there
are.
There
are
four
main
tools:
there's
argo
workflows,
which
is
this
incredibly
powerful,
general
purpose,
workflow
engine
for
kubernetes,
argo
events,
which
is
typically
used
for
triggering
workflows,
and
things
like
that.
Argo
cd
is
the
world's
most
popular
and
fastest
growing
get
ops
engine
today,
and
it's
far
and
away.
A
It's
really
amazing
how
that
community
has
grown
and
argo
rollouts
is
one
of
the
easiest
quickest
ways
to
get
started
with
doing
progressive
delivery,
canary
releases
blue
green
deployments.
How
many
are
go?
Workflows,
users
first,
like
a
really
good
quarter
of
the
audience:
argo
cd
users?
Okay,
all
right!
That's
awesome!
A
So,
like
we
said
it
is
one
of
the
fastest
growing,
most
popular
cncf
projects.
Today
we
recently
ran
a
survey
of
users
and
asked
them
how
likely
they
were
to
recommend
argo
to
a
friend
and
argos
cd
scored
an
incredible
72..
This
is
a.
This
is
a
scale
that
goes
from
negative
100
to
positive
100
and
72
is
like
some
of
the
most
beloved.
You
know.
Companies
in
the
world
can
reach
that
level,
and
48
is
very.
Very
strong.
Like
starbucks
is
like
a
48..
You
know
people
love
their
starbucks.
A
It's
a
big
deal
there.
It's
maintained
in
a
partnership
between
acuity
blackrock
code,
fresh
intuit,
red
hat
and,
of
course,
an
amazing
community
of
individual
contributors
that
that
help
out
with
that,
it's
used
by
google
adobe
nvidia
tesla
paypal,
ea,
the
the
list
goes
on
and
if
you're
using
argo,
please
go
add
yourself
to
the
users
list,
we'd
love
to
see
how
that
grows,
and
it's
in
a
very
long
list
already,
and
everyone
counts.
A
A
So
another
part
of
the
argo
project
that
you
may
not
be
aware
of
is
argo
project,
labs
and
argo
project.
Labs
is
really
this
growing
ecosystem
of
tools
that
are
designed
to
work
with
argo
and
there's
already
a
lot
of
ecosystem
projects
and
some
of
those
ecosystem
projects
end
up
getting
merged
into
these
main
argo
tools
that
you're
already
familiar
with
so,
for
example,
argo,
cd
notifications
and
application
set
started
off
as
argo
labs
projects
that
people
contributed.
They
had
this
idea.
They
said
hey
when
I'm
adding
applications.
A
Wouldn't
it
be
amazing
if
I
could
templatize
that
and
just
add
them
at
scale
application
set
when
we
surveyed
users
who
are
using
argo
cd,
we
found
that
everybody
that
had
over
a
thousand
applications,
so
the
people
that
were
really
scaling
every
single
one
of
them
used
application
sets.
So
the
fact
that
that's
merged
into
the
main
project
started
in
the
community.
A
I
mean
it's
all
community,
but
it
started
as
kind
of
an
individual
contribution
and
idea
that
was
then
merged
into
the
project,
and
now
everybody
benefits
from
it,
and
there
are
so
many
more
amazing
projects
in
there.
So
if
you
have
an
idea,
if
you
have
something
you've
been
working
on
at
a
lot
of
companies,
they
build
little
tools.
You
know
around
argo
to
help
them
do
this
project
or
that
project
we'd
love
for
you
to
bring
those
and
so
contact
us
reach
out,
hit
us
up
on
slack.
A
A
One
project
that
I
want
to
highlight
that
was
added
in
the
last
six
months.
Seven
months
was
argo,
cd,
autopilot
and
argo
cd.
Autopilot
is
a
git
ops,
compliant
interface
that
allows
you
to
bootstrap
argo
cd
and
have
it
create
your
directory
structures
and
all
these
things
for
you-
and
I
have
a
very
quick
demo
for
you.
A
So
here
you
can
see
basically,
first,
I
need
to
set
a
git
token,
because
this
is
a
git
ops,
operated
interface,
and
so
it's
going
to
write
all
the
changes
to
get.
We
set
the
git
repo,
where
we
want
to
store
our
files.
So
this
is
where
all
the
configuration
for
argo
cd,
as
well
of
all,
of
the
applications
that
are
installed
and
managed
and
all
the
projects
that
are
managed
there
are
going
to
be
set.
A
A
Okay,
so
this
is
a
pattern,
that's
getting
more
and
more
popular
and
one
that
I
personally
love
to
see.
That's
the
way
I
like
to
do
it
we're
going
to
add
a
project
here
for
the
local
cluster,
and
you
could
add,
you
know
many
clusters.
You
could
be
managing
a
thousand
clusters
with
a
single.
You
know
argo
cd
instance
and
then
we're
gonna
do
an
app
create
demo
app
and
we're
gonna
specify
where
the
manifests
for
those
come
from,
and
it's
going
to
create
a
customized
overlay
in
our
repo
that
we're
working
on
that
references.
A
The
base
as
that
application.
So
now
that
it's
been
pushed
we'll
pull
this
from
git,
you
can
see
it's
created,
apps,
bootstrap
and
projects
and
we'll
run
a
tree
on
this
really
quick.
So
we
can
see
how
it
is
designed
this
structure.
So
you
can
see
argo
cd
is
managing
itself.
If
you
want
to
update
argo
cd,
you
just
change
the
the
version
reference
that
it's
referencing
and
it'll
pull
in
an
update,
update
itself
and
then,
if
you
want
to
add
applications,
you
just
add
a
file
under
application
and
there's
an
application
set.
A
That's
set
up
that
automatically
will
take
all
of
the
files
under
those
folders
and
automatically
create
applications
from
them
and
deploy
them
to
your
cluster.
So
this
is
a
a
very
opinionated
way
to
use
argo
cd,
argo
cd
is
generally
very,
very
flexible,
and
so
this
that's
why
this
is
a
labs
project.
So
if
you
want
to
try
out
argo
cd,
autopilot
we'll
have
a
link
for
you
at
the
end.
A
B
So,
for
example,
argo
city
don't
force
engineers
to
write
yaml.
Instead,
you
can
use
your
favorite
config
management
tool
such
as
customize
or
helm,
in
order
to
be
truly
useful.
Dashboard
argo
cd
has
to
have
a
deep
understanding
of
various
kubernetes
resources
such
as
deployment
boards
and
even
popular
custom
resources
of
projects
like
search
manager
or
istio,
and
so
ui
have
to
understand
how
those
you
know
the
structure
of
those
resources
and
provide
useful
visualizations,
and
we
have
plans
to
even
integrate
with
some
third-party
metrics
providers,
meaning
third-party
to
argo.
B
We
try
to
group
the
ways
of
how
we
want
to
extend
our
gosiidin
and
we
come
up
with
those
three
major
extension
points.
One
of
them
is
manifest
generation,
as
I
said.
Second
is
resource
customization
and
third-party
ipa
integrations
and
first
I
want
to
talk
about
manifest
generation
and
how
we
want
to
approach
it.
So,
basically,
we
come
up
with
a
feature
that
we
call
config
management
plugin
and
we
decided
to
split
implementation
into
several
steps,
and
so
we
basically
plan
to
deliver
it
in
three
steps
and
step.
B
One
is
complete,
which
is
a
basic
functionality.
So,
as
of
version
2.3,
you
can
take
any
cli
and
as
long
as
it
produces
yaml,
you
can
use
it
as
a
config
management
plugin
for
argo,
cd
so
and
the
snippet
on
the
right
side
kind
of
oh.
Is
it
left
side
for
you,
so
it
demonstrates
that
the
configuration
that
argo
cd
administrator
have
to
provide.
B
B
Basically,
every
pretty
much
every
config
management
tool
has
a
way
to
apply
some
last
mile
changes
and
kind
of
influence.
How
your
final
yammer
looks
like,
for
example,
in
customize.
You
might
say:
oh,
if
you
see
this
particular
image,
then
I
want
to
use
latest
tech,
for
example,
for
dev
environment,
or
you
can
choose
to
apply
name
prefix.
B
We
plan
to
allow
admins,
who
configure
the
plugins
to
provide
the
mapping
between
the
cli
and
basically
and
and
provide
declarative
definitions
of
the
supported
parameters
and
that
parameterization
support
is
supposed
to
be
delivered.
Hopefully,
in
upcoming
2.5
release.
As
soon
as
it's
there,
you
will
be
able
to
leverage
that
feature
by
making
changes
in
argo,
cd,
application,
crt,
spec
and
that's
a
big
step
forward.
It
will
cover
most
of
them
pretty
much.
B
Currently
we
have,
I
would
say,
maybe
a
dozen
requests
to
support
different
content
management
tools,
and
hopefully
we
can
execute
those
requests
very
quickly
because
we
can
start
building
those
plugins
in
parallel
and
it
doesn't
have
to
be
in
the
core
team
of
argosyd
right.
We
have
not
so
much
time,
so
I
want
to
keep
moving.
So
the
next
area
of
customization
that
I
want
to
cover
is
resource
customizations.
B
So,
as
you
probably
know,
argo
cd
understands
the
health
of
a
resource
and
it
it
provides
a
way
to
execute
some
actions
on
the
resource
and
currently,
all
those
integrations
for
customer
resources
kind
of
built
in
into
argo
cd.
All
of
them
contributed
by
the
community,
but
we
realized
that
it
really
takes
kind
of
every
every
little
bug
contributed
in
such
integration
affect
a
lot
of
users,
and
users
have
to
wait
like
three
months
before
the
next
targo
cd
release,
which
is
not
great,
and
we
wanted
to
kind
of
make
it
a
move.
B
Those
integrations
outside
of
a
project
and
then
in
other
requirements
that
we
had.
We
wanted
to
let
end
users
kind
of
configure
custom
visualizations
for
all
custom
resources
in
in
kubernetes
and
to
achieve
that,
we've
created
a
lapse
project
called
argo
cd
extensions
and
we
built
one
extension
which
is
available
already
for
argo
rollouts
and
the
screenshot
on
the
slide
demonstrates
your
argo
cd
user
interface
that
renders
the
rollout
object
and
rollout.
B
And
there
is
a
little
bit
of
help
for
you.
So
there
is
a
library
called
that's
available
under
argo
approach
in
the
argo
ui
repository
and
that's
just
a
it's,
a
library
of
react
components,
that's
already
used
by
argo,
cd
ui
by
workflows,
ui
and
rollout
ui.
So
if
you
want
to
build
an
extensions,
you
are
welcome
to
use
that
library,
because
this
way
you
will
get
the
same,
look
and
feel,
and
basically
your
extensions
will
look
naturally
in
in
argo,
cd
ui.
B
This
is
really
passionate
about
that
feature.
It's
still
in
the
plans
and
it's
it.
I
expect
that
it
won't
be
delivered
in
in
other
2
3
releases,
but
we
thinking
about
making
cargo
city
even
more
extensible,
and
so
we
want
to
be
able
to
visualize
data,
that's
outside
of
kubernetes
and
to
do
so
we're
planning
we're
hoping
to
introduce
a
way
for
administrators
to
register
additional
api
endpoints
that
would
proxy
requests
to
system
to
like
apis
such
as
data.
A
So
argo
rollouts,
as
many
of
you
know,
relies
on
gateways
to
manage
traffic
and
currently
anytime,
we
add
support
for
an
additional
gateway.
We
have
to
write
a
new
controller
specifically
for
that
gateway
and
figure
out
that
logic
and
it's
fairly
time
consuming.
But
there's
an
amazing
project
called
gateway
api
coming
from
the
kubernetes
community
and
it
provides
a
standardized
interface
for
working
with
different
gateway
providers
and
coming
soon.
A
This
is
currently
in
pr
and
we're
just
working
through
the
changes
we're
going
to
be
able
to
vastly
extend
how
many
gateways
we
can
support
with
argo
rollouts
through
gateway
api.
So
currently,
today
we
natively
support
ambassador
aws,
albs,
istio,
nginx
and
then
smi,
which
provides
the
the
interface
for
not
sto
for
service.
B
A
And
then-
and
now
of
course,
we
can
add
support
for
all
of
these
other
ones,
like
google,
kubernetes,
engine,
aha,
proxy
console,
kongs,
and
so
from
now
on,
once
this
is
merged,
if
you
want
to
add
support
for
your
gateway
into
argo,
argo
rollouts,
you
only
need
to
add
support
for
gateway
api,
so
this
is
a
really
exciting
development.
Most
of
those
gateway
apis
are
currently
in
an
alpha
something
they're
moving
into
a
beta
stage.
C
Cool
thanks
dan.
Do
you
fist
bump,
or
do
you
elbow?
I
can't
really
tell
what
people
prefer
cool.
So
argo
workflows
is
kind
of
the
de
facto
workflow
engine
on
kubernetes.
So
if
you're
running
kind
of
batch
processing,
machine
learning
things
like
infrastructure,
automation
and
I've
talked
a
lot
of
people
about
doing
ci.
C
The
reason
we've
done
this
is
it
just
takes
a
really
long
time
to
introduce
new
features
into
argo,
workflows,
I'll
release
cycles
about
every
three
or
four
months.
But
what
with
a
plug-in
what
you
can
do
as
a
user
is
you
can
install
a
plug-in
today?
You
can
write
it
today.
You
don't
need
to
learn
golang,
you
don't
need
to
commit
to
the
tree
and
you
don't
need
to
really
wait
for
a
release.
C
So
a
plug-in
is
really
just
if
people
have
gone
to
any
talks
about
how
to
extend
controllers.
It's
a
very
standard
pattern.
Basically,
when
we
want
to
invoke
your
plugin,
we
just
make
an
api
request,
and
this
is
basically
the
api
contract
where
we
send
you
the
details
of
the
workflow
and
the
template,
and
you
just
tell
us
what
the
outcome
of
that
is
to
implement
it.
It's
what
30
lines
of
python
codes.
C
C
Now
we
have
a
little
video.
Oh
it's
playing
brilliant
okay.
So
let
me
see
if
I
can
narrate
the
video
as
it
comes
up
here.
So
a
plugin
is
just
installed
as
a
typically
as
a
config
map
that
describes
the
plugin,
and
you
can
just
install
this
at
runtime.
You
don't
need
to
restart
the
controller
and
your
plugin
will
appear
now.
If
you
can
install
this
as
a
user
as
or
as
an
administrator.
C
So
it's
self-service
and
the
plug-in
is
just,
as
I
said,
a
python
script
and
this
example
is
just
going
to
run
some
python
code,
a
python
expression,
and
I
can
pass
parameters
to
this
script
as
well.
Just
like
I
would
do
with
a
normal
pod
template
in
this
example,
I'm
going
to
get
it
to
print
out
a
message
I
just
create
this
workflow
and
I'll
appear
in
the
user
interface.
C
I
know
most
people
are
probably
more
familiar
with
the
argo
cd
interface,
but
there
you
go
and
now
the
message
has
appeared
in
the
user
interface
for
users
to
see.
So
that's
that
and
how
do
I
get
out
of
this
stand
and
wait
for
the
ends
so
we've
got
about.
Eight
people
have
already
opened
source
plugins.
Several
of
these
people
open
source
that
before
the
plugins
are
even
available
in
release,
so
things
like
syncing
are
going
to
see
the
applications
sending
slack
or
other
kind
of
notifications
running
volcano
jobs.
C
I
missed
the
volcano
presentation
today.
I
was
looking
forward
to
that.
I'm
actually
I'm
running
web
assembly,
so
you
can
write
your
own
plugin
and
webassembly.
If
that
tickles
your
fancy,
the
other
thing
that
people
use
argo
workflows
for
is
building
platforms.
On
top
of
this,
so
at
intuit,
our
machine
learning
platform
is
based
on
our
go
workflows
internally,
as
is
our
batch
processing
platform
and
they
basically
typically
the
pattern
is
that
you'll
write
your
workflow
in
the
language
you're
most
comfortable
with.
C
C
Okay
got
a
little
short
video
for
you
here,
so
this
is
great.
I
don't
have
to
write
a
yaml.
I
can
write
this
in
python.
I
don't
have
to
build
an
image.
I
can
just
write
a
python
script
and
it'll
run
that
that
gets
turned
into
a
workflow
template,
so
I
can
run
the
workflow
template
multiple
times
with
inside
argo
workflows
and
in
this
example
it's
parametrized.
C
C
C
This
is
the
kubeflow
dsl
that
you
write
your
workflow
in
it
now
that
gets
transpiled
to,
of
course,
a
directed
acyclic
graph,
because
we
love
those
in
the
in
the
community,
and
if
you
notice
that
this
is
the
this
is
the
graph
shown
in
the
kubeflow
pipelines
interface,
and
this
is
actually
the
same
graph
that
executes
in
argo
workflows.
Just
the
layout
of
that
graph
is
a
little
bit
different.
One
of
the
things
I
really
like
about
kube
flow
pipeline
is
actually
also
about.
Metaflow
is
the
way
they
make.
C
A
First
of
all,
there
are
some
additional
great
talks
coming
up
around
argo,
so
tomorrow,
alexander,
your
your
partner,
jesse
is
going
to
be
speaking
with
tiktok
about
how
they're,
using
argo
cd
successfully
there's
going
to
be
a
great
get
ops
get
opposifying
with
cross
plane
talk
from
some
folks
at
ibm
on
friday.
So
don't
don't
miss
those
talks
and
there
have
already
been
actually
quite
a
few
great
argo
talks
at
kubecon.
A
I'm
sure
you've
all
been
chasing
them
down
some
other
community
resources
to
mention
there
is
a
get
off
certification
available,
focused
on
argo
cd
that
somebody
on
my
team
coast
has
put
together.
So
you
can
get
the
bitly,
slash,
argo
dash
training,
and
then
there
is
this
awesome.
Argo
list
that
the
folks
at
acuity,
sponsor
and
put
together
and
has
getting
started
guides
best
practices.
A
How
should
you,
you
know,
make
your
directory
structures?
How
should
you
handle
permissions?
All
these
house,
united
secrets
and,
of
course,
join
us
on
slack
we're
on
the
cncf
slack,
there's
tons
of
channels?
There's
argo
workflows,
channel
or
a
cd
channel
more
channels.
You
can
throw
a
stick
at.
I
know,
that's
a
lot!
A
It
seems
overwhelming,
but
you
know
start
with
the
area
that
you're
interested
in,
and
you
can
branch
out
and
see
these
other
ones,
so
really
amazing
resources
coming
from
the
community
and
if
you
have
a
blog
post,
if
you
have
a
great
best
practice
guide
a
presentation
send
it
on
to
that
awesome.
Argo
list
which
has
been
a
huge
resource
for
us,
and
I
know
that
everybody
relies
on
it.
We
also
have
a
subreddit.
A
We
have
an
argo
project,
subreddit,
there's
a
get
off
subreddit,
so
join
those
forgot
to
put
that
on
the
slide
and
even
more
exciting,
coming
up
at
the
end
of
the
year
is
going
to
be
argo
con.
This
will
be
the
second
time
we've
done
it.
How
many
people
attended
argo
con
virtually
last
year?
A
handful?
Okay,
that's
amazing,
because
we
had
like
over
6
000
people
attend
that
conference.
A
So
it's
really
this
like
tour
de
force,
that's
arriving
with
argo
con
and
so
go
and
register
for
that,
and
you
have
until
the
31st
to
submit
a
cfp
so
about
a
week
and
a
half
left
go
get
those
cfps
in
we'd
love
to
have
them
and,
of
course,
get
ops.
Con
just
happened
on
tuesday
and
there
were
a
ton
of
talks.
There
were
probably
nine
ten
talks
that
focused
on
argo
cd,
auto
rollouts.
Those
recordings
are
all
available
now.
So
if
you
missed
get
off
con,
you
can
go
and
watch
those
and
that's
it.
A
A
A
B
B
Some
time
ago
we
just
made
a
decision
to
release
no
matter
what
so
we're
kind
of
releasing
every
three
months,
and
there
was
you
know
the
feature
didn't
make
it
now,
but
it's
actively
being
developed
right
now.
The
proposal
is
finalized,
so
it
definitely
makes
it
in
the
next
release.
2.5
yeah,
that's
it.
E
B
Do
you
think
I
don't?
Actually?
I
don't
think
so.
There
is
a
I
feel
like
it's.
I
would
call
it
a
pattern,
but
not
so
many
people
uses
it
because
it
requires
you
to
be
like
100
githubs.
If
you
like,
really
able
to
disconnect
your
ci
completely
from
your
deployment
and
you're,
confident
that
every
time
you
push
anything
into
git,
it's
100
tested.
So,
but
I
agree,
it's
kind
of
it's
opinionated
feature.
Not
everyone
uses
it
and
like
before
we
joined
acuity.
I
was
working
cut
into
it.