►
Description
Delivering software with Argo is so effective many organizations find the proliferation of services, configurations, clusters, and repositories rapidly become difficult to manage. In this keynote, we’ll review the state of the community and explore new tools, technologies, and trainings to help organizations tackle software delivery at scale using Argo Workflows, Argo CD, Argo Rollouts, and Argo Events.
A
Up
next
are
two
people.
I
have
the
pleasure
of
working
alongside
almost
every
day
dan
and
hannah
dan
is
the
co-founder
and
chief
open
source
officer
of
code
fresh,
a
continuous
delivery
and
get
ops
platform
as
a
full
stack
engineer
and
kubernete
google
developer
expert
and
a
member
of
the
forbes
technology
council
dan
has
built
open
source
tools
for
advanced
deployment
methodologies
with
kubernetes,
argo,
helm
and
istio.
He's
also
helped.
Companies,
large
and
small,
adopt
kubernetes
and
modern
devops
practices
and
hannah
is
a
prior.net
developer.
Who
is
now
a
developer
evangelist
for
code
fresh?
A
B
B
It's
mostly
memes
and
nonsense.
So
if
that's
the
kind
of
stuff
you
want
were
the
two
people
to
follow
for
it,
we
are
going
to
be
talking
about
scaling
software
delivery
on
argo,
and
our
goal
here
is
to
give
you
a
lot
of
tools
that
you
can
use
most
of
them
open
source
and
most
of
them,
part
of
the
community
and
most
of
them
provided
for
free.
B
So
if
you
don't
make,
if
you
get
bored
with
our
talk-
and
I
wouldn't
blame
you-
because
sometimes
I
can
be
a
little
bit
boring
hannah-
is
always
engaging
but
stay
tuned
till
the
end,
because
we
do
have
an
announcement
and
I
think
you're
going
to
really
like
it
so
stay
tuned
for
that
at
the
end
and
we'll
get
through
it.
If
you
don't
know
who
code
fresh
is
just
a
quick
introduction.
B
B
We
do
a
lot
of
work
in
the
cloud
and
a
lot
of
surprisingly,
in
this
last
year,
we've
seen
a
lot
more
edge
usage
going
on
some
really
cool
companies
and
what
we're
sharing
with
you
today
is
really
a
lot
of
insights
that
we've
taken
from
working
with
these
enterprise
companies
working
with
people
who
are
doing
thousands
of
services,
thousands
of
instances
of
argo
thousands
of
applications,
so
we
actually
code
fresh
as
as
pratik
kind
of
mentioned
in
the
pro
at
the
top
of
the
day.
B
We
came
to
this
project
about
a
year
and
a
half
two
years
ago,
and
we
were
looking
at
technology
that
we
could
build
into
our
core
offering,
and
we
were
looking
at
ways
that
we
could
do
our
workflows.
We
could
do
workflows
better
pipelines
better.
B
We
were
looking
for
ways
that
we
could
do
get
ops
better
and
if
we
look
at
the
argo
project,
wow
just
phenomenal
growth
and
and
pratik
spoke
to
this-
about
the
nps
being
the
net
promoter
score
most
engineers,
don't
know
what
a
net
promoter
score
is
to
give
you
an
idea.
70
is
like
kind
of
unheard
of
it's.
Basically,
almost
as
high
as
you
can
as
it's
basically,
the
best
products
in
the
world
hope
to
achieve
like
50s,
so
to
get
be
up
in
that
60
70
range
is
really
amazing.
B
So
argo
workflows,
argo
cd
has
outpaced
growth
of
a
lot
of
other
projects
and
that's
been
amazing
to
see
we
maintain
argo
along
with
intuit
blackrock,
red
hat
and
recently
welcomed
acuity
plus
hundreds
of
engineers,
obviously
from
the
community,
which
is
which
is
fantastic
and
to
the
project.
We
currently
have
11
active
contributors
that
have
been
doing
hundreds
of
commits.
Many
of
you
have
been
been
lucky
enough
to
have
your
issues
fixed
by
some
code.
B
Fresh
people,
you
probably
met
pasha
anastasia's,
been
doing
a
ton
of
work
on
uis
and
the
areas
that
we've
been
really
focused
on.
Security
is
a
big
one.
We
have
a
lot
of
enterprise
customers.
We
have
a
lot
of
regulated
industries
that
are
using
code
fresh
and
using
argo
and
so
making
sure
that
things
are
up
to
snuff,
and
this
goes
to
what
pratik
was
talking
about
us
going
towards
graduation.
This
is
super.
Important
conformance
is
another
area
that
we
think
is
really
important.
We
think
that
argo
is
similar
to
kubernetes.
B
You
want
to
be
able
to
take
a
configuration
in
one
place
and
use
it
in
another
place.
You
want
to
know
that
if
somebody's
providing
argo
they're
giving
you
the
real
deal,
so
this
is
another
area
that
we're
working
on,
obviously
lots
of
ui
stuff
lots
of
extensibility
lots
of
bug
fixes
and
we
are
planning
to
more
than
double
our
contributions
in
2022.
So
this
is
only
getting
more
important
for
us
and
we're
going
to
bring
that
to
everybody.
B
So
what
are
some
of
the
common
challenges
of
scaling
software
delivery
on
argo
and
how
can
we
solve
them
and
we're
going
to
start
getting
hannah
into
the
mix
here
soon,
thanks
hannah
for
hanging
out
yeah,
so
the
the
answer
is
is
really
good.
Ops
and
git
ops
is
everybody
here
we
actually
did
a
talk
recently
where
kostas
gave
a
talk
in
the
beginning.
He
said
how
many
people
are
doing
git
ups
and
so
put
it
in
the
chat.
B
Are
you
doing
git
ops
right
now
and
then
he
explained
get
offs
and
then
he
asked
again
how
many
people
are
doing
get
offs
and
suddenly
all
the
hands
went
down.
So,
let's
see,
let's
see
if
we
quickly
reviewed
it
up,
let's
make
sure
we're
on
the
same
page
about
what
this
thing
is.
So
we
actually
launched
an
initiative
a
little
over
a
year
ago,
with
amazon,
azure
github,
red
hat,
we've
worked
to
make
sure
that
we
had
a
clear
standard
for
git
ops,
so
we
actually
had
96
different
interested
parties.
B
C
Yeah,
so
as
as
dan
mentioned,
you
might
be
familiar
already
with
some
of
these
principles,
but
there's
so
much
more
there's
so
much
more
to
them
than
just
a
list
or
just
a
high-level
guide
when
it
comes
to
your
workflow
and
your
infrastructure,
so
first
just
starting
with
declaration.
This
is
the
number
one
best
practice.
It's.
You
essentially
want
to
describe
your
entire
system
declaratively.
B
And
then
you
know
actually
minor
minor
interruption
before
we
get
into
get
ups.
People
were
asking
about
these
t-shirts
and
where
to
get
them,
oh
yeah,
everything
to
me
and
she
said,
make
sure
that
people
check
their
email
after
the
event
because
she's
like
she's,
like
we
have
like
a
thousand
of
these
in
a
box.
B
And
this
is
this
is
actually
one.
That's
a
lot
of
people
surprisingly
get
wrong
because
they're
like
well
I'm
using
git.
So
it's
versioned
and
it's
immutable
right
like
what
else
do
I
need
to
do,
and
then
you
look
in
their
configuration
and
their
image
is
like
using
the
latest
tag
and
you're
like
okay.
So,
like
what
happens,
if
you
want
to
do
a
rollback,
can
you
go
check
out
an
old
commit?
It's
not
going
to
work
because
you
actually
unversioned
your
configuration,
so
you
have
to
look
for
things
like
that.
B
Images
are
the
most
common
places
where
we
see
people
make
this
mistake,
but
you
do
need
to
be
using
git
in
a
virgin
and
immutable
way.
You
can't
be
going
around
it
and,
of
course
you
could
actually
be
using
something
other
than
get.
You
could
use
perforce
we
actually
when
we
were
building
this
standard
we
were
like.
Can
you
do
this
with
google
sheets
and
we
kind
of
found
like
yeah?
You
probably
could
not
that.
I
would
recommend
that,
but
going
to
number
three.
B
Yeah
and
we
didn't-
we
didn't
use
the
word
push
here,
because
if
you
have
a
software
agent,
this
is
what
it
implies.
A
software
agent
is
checking
and
always
aware
of
the
configuration,
and
so
some
people
will
say
well,
I
have
a
trigger
that
triggers
a
deployment
right,
but
if
that
trigger
failed,
you
want
that
software
agent
actually
checking
in
and
being
aware
of
the
desired
state
always-
and
this
goes
to
number
four
which
is
continuously
reconciled.
B
We
really
believe
that
gitops
goes
beyond
that,
that
we
could
actually
apply
these
principles
to
our
entire
software
delivery
stack
and
so
we're
gonna
actually
get
into
that
in
a
second.
So
if
you're,
this
just
gives
you
like
a
clear
picture
of
of
get
ops
in
operation.
So
now
I'm
curious
in
the
chat.
How
many
of
you
still
feel
like
you
do
get
ups.
You
have
all
of
those
components
how
many
of
you
were
surprised
like?
Oh,
actually,
we
kind
of
don't
do
each
of
those
things.
B
So
the
next
is
like
how
can
we
make
sure
we're
getting
the
most
out
of
our
go
using
git
ops,
and
this
goes
to
a
tool
that
we've
released
called
argo
cd
autopilot?
This
is
an
open
source
tool.
It's
part
of
argo
labs,
and
this
is
actually
the
most
common
way
that
I
use
argo,
because
when
I'm
using
argo
and
I've
found
a
lot
of
people
do
this,
they
install
it
manually
on
a
cluster.
B
That's
great.
It
gets
you
up
and
running,
but
it
actually
means
that
you're
using
argo
in
a
non-gitops
friendly
way.
So
if
you
want
to
update
argo,
suddenly
it's
like
oh
wait.
This
isn't
checked
into
git,
wait.
How
do
I
keep
this
updated
and
then
the
other
problems
that
we
see
a
lot
are
people.
Argo
is
very
flexible,
which
is
great
when
you're
getting
started,
but
as
you
start
to
scale
this,
that
flexibility
can
bite,
you
are
going
to
say
hannah.
B
Yeah,
so
argo
cd
autopilot
will
also
create
a
directory
structure
for
you,
and
it's
built
off
of
customized
that
you
can
follow
to
not
only
handle
multiple
environments
and
promotion
of
changes
from
one
environment
to
another,
but
also
enables
disaster
recovery,
helps
you
handle
secrets
all
these
kinds
of
things,
so
you
can
check
it
out
at
codefresh.org
autopilot
we're
not
going
to
get
a
demo
of
it
today,
but
code
fred.
You
can
just
see
how
it
works.
B
Argo,
cd,
autopilot,
repo
bootstrap,
will
actually
install
argo
cd,
write
all
of
the
configuration
onto
a
git
repo
and
create
that
directory
structure
for
you.
So
it
actually
solves
a
lot
of
problems
and
a
lot
of
people
that
use
argos
cd
find
that
this
actually
helps
them
move
a
lot
faster.
So,
okay,
get
ops
is
about
more
than
technology,
so
we've
got
argo
cd
autopilot
to
help
us
be
effective
in
creating
our
repositories.
B
But
it's
not
just
technology,
because
we
all
know
that
if
we
just
throw
all
this
technology
at
our
teams,
they're
not
necessarily
going
to
know
how
to
use
it
and
they're
not
necessarily
going
to
bring
the
discipline
to
actually
follow
the
principles
as
they've
been
laid
out.
So
obviously,
we've
got
argo
khan
today
tons
of
best
practices,
aya's
talk
was
like
just
her
q.
A
on
on
secrets.
I
was
like
this
is
better
than
most
talks
on
secrets
and
how
to
handle
get
off.
B
So
if
you've
missed
that
go
watch
that
session
again,
preferably
after
our
session
yeah
also
get
ops.
Con
at
kubecon
in
back
in
october,
was
the
largest
day.
Zero
event
at
kubecon
is
the
most
popular
one
and
we
have
get
ops
con
eu
happening
may
16th,
so
you
can
join
us
virtually
or
on
site.
For
that
really
excited
to
be
a
part
of
that,
and
the
planning
is
happening
right
now.
The
call
for
papers
is
about
to
go
out.
C
So
this
I'm
really
excited
to
talk
to
you
guys
about
this
and,
if
you're
familiar
with
code
fresh-
and
you
already
interact
with
us-
you've-
probably
gotten
some
sort
of
email
or
something
just
letting.
You
know
that
we're
going
to
be
launching
a
certification
program
and
we've
had
at
least
over
a
thousand
people
already
sign
up.
C
This
program
is
going
to
include
three
courses
that
focus
on
get
ops
that
we
want
to
share
with
all
of
you,
the
community
and
those
of
you
who
are
already
in
kind
of
ingrained
within
the
get
ups
process
and
just
want
to
know
how
to
improve.
So
our
courses
and
our
program
include
includes
three
courses.
It's
going
to
be
get
ups,
fundamentals
get
opposite
scale
and
get
opposite
edge.
Currently
we're
offering
our
first
course,
which
is
get
ops
fundamentals
and
essentially
within
this
course
course
curriculum.
C
B
Yeah
and
I've
really
loved
this
we've.
The
team
hannah
and
costas
really
built
this
thing
and
going
through
using
argo
cd
using
argo,
rollout
setting
it
all
up
in
a
github
friendly
way,
because
again
you
can
use
these
tools
and
not
follow
github's
principles
and
you'll
rapidly
find
yourself
in
trouble.
If
you
don't.
C
Yeah,
so
right
now
the
course
experience
when
you
enroll
in
the
certification
program.
It's
going
to
be
pretty
sophisticated.
We're
excited
about
this
so
that
all
of
the
content
was
created
by
code,
fresh's,
evangelism
team,
there's
going
to
be
a
hands-on
cli
editor
you'll
even
be
able
to
access
the
argo
cd
ui
component
and
then
we're
going
to
guide
you
through
the
get
ops
workflow
step
by
step,
we'll
even
be
allowing
you
to
use
a
real
live,
kubernetes
cluster
and
there
won't
be
any
setup
on
your
end.
C
So
we're
taking
care
of
pretty
much
all
the
heavy
lifting
your
environment
and
just
allowing
you
to
have
an
easy
learning
experience
so
that
you
can
even
use
on
a
mobile
device.
So
we're
really
excited-
and
we
also
have
some
other
news-
is
that
you
can
get
started
with
the
get
ops
fundamentals
course
today.
C
B
At
least
for
the
next
two
months,
so
definitely
getting
that
certification
early
and
also
send
your
feedback
to
hannah
hit
her
up
on
twitter.
Tell
her
everything
you
don't
like
about
it.
She'll
be
thrilled.
B
Yeah,
you
can
say
what
you
love
about
it
too
awesome.
Thank
you
hannah.
So
now
that
we've
we've
got
you
certified,
you
know
how
to
do.
Git
ops,
you
know
you're
using
some
cool
tools
like
argo
cd
autopilot.
The
next
question
really
comes
in.
How
do
I
keep
track
of
this
at
scale,
and
so
this
is
something
that
we've
seen
happen
with
people
where
they
have,
and
actually
I
saw
this
a
lot
in
the
chat
during
the
other
sessions.
B
People
were
saying:
I've
got
500
instances
of
argo
cd
should
I
keep
them
all
slaved
to
essentially
a
single
instance
where
what?
If
what
happens,
if
that
goes
down
and
there's
a
loss
of
network
connectivity,
how
do
I
manage
all
these
and
then
just
keeping
track
of
everything?
That's
happening.
B
Git
ops
principles
are
so
effective
that
people
rapidly
see
a
sprawl
where
there's
they're
doing
thousands
of
services
they're
doing
thousands
of
releases,
and
suddenly
people
start
to
feel
a
little
bit
uncomfortable
because
it's
like
okay.
How
do
I
keep
track
of
what's
going
on,
so
this
is
actually
a
tool,
there's
actually
a
tool
we
released
for
this
last
year,
called
code
fresh,
get
offs.
C
Yeah
and
so
codex
so
code,
fresh
gitops
is
a
dashboard
that
already
exists
within
the
code
fresh
platform,
and
it
also
has
an
easy
integration
with
argo
cd.
This
this
dashboard
provides
amazing
visualization
of
your
current
deployment,
utilizing
a
get
ops
controller
and
it
utilizes
an
existing
argo
cd
installation,
but
it
can
help
you
install
configure
an
argo
cd
instance,
so
this
dashboard
in
this
step
really
was.
This
really
did
create
a
path
for
us
to
integrate
with
argo
and
offer
its
capabilities
on
an
enterprise
level.
B
C
B
We
really
wanted
to
extend
that
so,
ultimately,
with
all
of
this
stuff,
the
goal
is
to
deliver
software.
We
want
to
use
git
ops
for
thousands
of
developers
for
thousands
of
environments
for
thousands
of
pipelines,
while
also
keeping
this
easy
enough
that
small
teams
can
use
it.
I
want.
I
want
teams
of
five
people
to
be
able
to
come
in
and
use
all
these
tools
and
be
really
effective,
just
like
the
same
way
that
a
team
of
5000
would
so.
B
That's,
that's
really
the
goal
here
and
so
we've
extended,
and
we
announced
this
at
kubecon,
but
we've
actually
extended
what
we've
done
with
code
fresh,
get
ops,
what
we've
done
with
that
enterprise
distribution
of
argo
cd
into
a
new
platform
that
is
called
the
code
fresh
software
delivery
platform-
and
this
is
an
enterprise
distribution
of
argo,
where
we
bring
all
of
the
components
together.
Argo
workflows,
argue
events,
argo
cd,
argo
rollouts,
and
this
is
something
I
saw
in
the
chat
today
too.
B
C
B
Yeah
and
this
this
goes,
this
goes
directly
back
to
the
scale.
Now
this
we
announced
at
kubecon
and
it's
currently
in
early
access
and
people
are
starting
to
use
it.
I
wanted
to
show
you
just
a
little
bit
of
a
sneak
peek
of
some
of
the
stuff
that
is
going
to
be
available
starting
in
january.
B
So
first
off
when
you
you
have
to
understand
about
this
platform,
is
that
we're
managing
a
lot
of
runtimes?
So
here
you
can
see
a
view
where
we've
got
a
ton
of
runtimes
in
scranton
in
orlando
across
the
world.
These
could
be
at
edge.
These
could
be
behind
the
firewall.
These
could
be
on-prem,
but
I'm
getting
a
roll-up
view
of
the
status
of
all
these
environments.
B
B
What
what
we're
really
doing
with
this
enterprise
distribution
of
argo
is
we've
taken
the
core
of
the
current
open
source
offering
and
we've
built
some
additional
enterprise
tooling
around
it,
to
handle
permissions
to
handle
our
back
to
enable
sso.
So
you
basically
can
just
create
these
instances,
and
I
can
navigate
to
an
instance.
I've
never
been
to
and
my
permission's
already
set
up.
B
So
I
can
log
in
with
my
user
and
I
can
get
directly
into
the
argo
cd
ui,
for
example,
the
argo
workflows
ui
if
I
need
to,
but
also
provide
versioning
on
all
these
things,
so
you
can
keep
them
all
up
to
date.
Now
what
happens
if
there's
a
connection
issue
with
one
of
these,
and
let's
say
my
instance
in
scranton
no
longer
can
reach
and
report
back
the
information
to
the
centralized
dashboard.
Well,
it's
going
to
continue
to
operate,
based
on
the
configuration
that
I
gave
it.
B
B
Now,
if
we
go
into
the
overall
dashboard,
we're
going
to
see
the
beginnings
of
how
this
starts
to
bring
all
this
information
together.
Now
when
we
talk
about
workflows
commonly
with
code
fresh,
these
are
ci
pipelines.
These
are
cd
pipelines.
We
do
have
a
number
of
people,
doing
machine
learning,
pipelines
or
data
pipelines,
and
I
can
see
somebody's
asking
already
like
wait.
Is
this
sas?
Is
this
on-prem?
This
is
actually
something
that
we
can
support
both
of
those
things,
and
so,
if
you
need
to
use
it,
we
actually
had.
B
This
is
a
whole
another
talk
conversation,
but
we
actually
have
people
doing
some
air
gap
stuff
with
github,
really
cool
and
I'm
going
to.
I
want
to
get
a
talk
out
on
that
soon
and
share
what
what
the
teams
built,
because
that's
a
really
interesting
use
case,
but
let's
get
into
actually
the
github's
dashboards-
and
this
is
this-
is
something
that
was
coming
from
code
fresh,
get
ops
again
ever
bringing
everything
together
is
the
goal
here.
B
So
if
we
pull
up
the
the
get
ups
dashboard
in
the
code,
fresh
argo
platform,
you're
going
to
see
it's
a
lot
of
information
going
on,
but
really
the
goal
is
to
bring
everything
together.
C
B
Here
you
can
see,
we've
got
argo
workflows
and
events
all
that
information
brought
into
a
place,
we're
actually
looking
at
an
application
level
here.
So
I
can
see
for
this
deployment
here
all
the
workflows
that
are
associated
with
that
and
that
could
be
that
could
be
ci
pipelines,
cd
pipelines.
That
could
be
some
machine
learning
pipelines,
models
that
were
being
built
or
things
like
that,
in
addition
to
the
pull
requests
associated
with
it
all
of
the
events
associated
with
it.
So
that's
all
that's
all
exposed
on
this
single
view.
B
So
I'm
not
jumping
between
tools
to
understand.
What's
going
on,
argo
rollouts
also
exposed.
C
And
with
and
with
argo,
it's
with
argo
rollouts
as
part
of
the
runtime,
you
can
actually
be
able
to
perform
advanced
deployment
using
your
canary
or
your
blue
green
deployments,
and
you
can
view
the
deployment
progress
in
the
application
dashboard.
So
it's
going
to
allow
you
to
promote
or
roll
back
your
deployments
according
to
any
sort
of
metrics
that
you're
able
to
view
right
here,
which
is
super
nice.
B
Yeah
absolutely-
and
I
I
can
see
somebody's
asking
does
it
have
integrations
with
any
vault
like
hashicorp,
absolutely
also
works
with
mozilla
sops
and
some
other
secret
providers
kind
of
right
out
of
the
box.
Someone
is
also
asking
if
the
certification
is
free.
I
just
want
to
reiterate
it
is
today
so.
C
B
In
this
view,
we
also
have
argo
cd
information
exposed,
so
we
can
see
all
the
services
and
a
timeline
view
now.
This
is
this
is
something
that's
really
important
to
me
when
you're
shipping
microservices
at
scale,
one
of
the
issues
that
can
happen
is
that
a
regression
in
service
b
can
actually
cause
failures
in
service.
Why
and
the
relationship
between
those
can
be
difficult
to
understand.
B
So
within
this
timeline
view,
I
can
actually
say
show
me
all
the
deployments
all
the
releases
that
happen
during
this
time
period,
and
then
I
can
look
and
just
see.
Oh
well,
these
are
the
jira
tickets
associated
with
those
releases.
I
can
see
that
how
that
would
cause
a
potential
failure
over
here,
so
it
really
helps
you
identify
regressions,
much
much
faster.
B
So
this
is
the
complete
platform
right.
We're
bringing
argo
workflows,
we're
bringing
argo
cd,
we're
bringing
our
go
events,
we're
bringing
argo
rollouts
all
into
a
single
platform
where
you
can
access
them
all,
and
these
are
configurations
that
you
can
just
bring
from
if
you're,
just
using
open
source
argo
workflows.
Today
you
can
just
bring
that
workflow
in
code
fresh
and
rock
and
roll.
A
B
So
next
up
wanted
to
show
you
the
image
view.
So,
if
I'm
looking
in
here,
I
can
actually
see
the
instances
of
the
services
and
I
could
drill
down
onto
a
view
of
just
those
images.
So
this
image
report
is
really
powerful.
It
can
show
you
where
an
image
is
deployed.
So
it's
aware
of
all
your
instances
right,
so
you
can
say.
Oh
I
have
this
older
version
of
this
image.
Is
anybody
still
using
this?
B
Oh,
my
gosh,
I
can
actually
see
it's
deployed
in
15
locations
still
right
now
you
can
jump
over
to
those
applications
and
figure
out
who's
using
it
figure
out
why
they're
using
it
so
that
there's
a
lot
of
like
headspace
management
stuff
that
this
is
helping
solve
and
bringing
all
the
information
together.
Obviously,
security
information,
pull
request,
information,
all
those
kinds
of
things
really
powerful
stuff.
B
Now
we
want
to
go
back
and
look
at
argo
workflows,
but
before
we
do
one
of
the
really
cool
features
that
we're
bringing
is
the
ability
to
review
and
look
at
pull
requests
at
the
application
level.
C
C
B
Yeah,
if
you're,
if
you're
looking
at
the
application
level,
you
could
be
dealing
with
pull
requests
for
many
different
repositories.
We
didn't
really
talk
a
lot
about
the
repository
model,
but
what
we
really
advocate,
what
we've
seen
a
lot
of
success
with
our
customers
with
is
using
a
two
repo
model
where
you
have
an
application,
repo
and
sort
of
an
infrastructure
repo.
You
make
changes
to
your
application.
B
So
these
pull
requests
could
actually
be
dealing
with
many
different
applications
that
are
part
of
an
app
of
apps
or
part
of
an
application
set
so
being
able
to
view
how
these
relate
to
each
other
within
the
context
of
a
pull
request,
that's
really
powerful
and
it
means
I
don't
have
to
jump
around
between
tools
to
figure
out.
What's
going
on
and
somebody's
asking
in
the
chat
does
code
fresh,
provide
the
clusters
or
does
it
sit
on
top
of
other
clusters
sits
on
top
of
other
clusters.
B
B
Ci
cd
pipelines
is
is
where
we've
we're
bringing
argo
workflows
really
to
bear,
and
we
have
a
lot
of
experience,
building
performance,
ci,
cd
pipelines.
So
one
of
the
things
you'll
see
that
I
wanted
to
highlight
is
this
view
of
a
pipeline
execution
of
a
workflow
execution.
You
can
actually
see
which
event
sources
which
sensors
were
used
to
trigger
this
pipeline,
and
it
gives
you
debugging
information
and
we
found
that
a
lot
of
people
when
they're
using
argo
events
and
argo
workflows
together.
B
Sometimes
the
linkage
between
those
things
gets
confusing
and
it's
difficult
to
debug
so
presenting
all
this
together
makes
it
more
powerful
and
when
it
comes
to
adding
a
pipeline,
maybe
hannah
is
this
something
you
want
to
talk
to.
B
No,
so
when
adding
a
pipeline,
we've
made
this
really
easy.
So
when
you
create
a
pipeline
and
you
need
to
configure
sensors,
you
need
to
configure
workflows,
we
actually
created
a
wizard,
so
you
can
start
with
a
baseline
template
and
yes,
this
does
work
with
multiple
clusters,
like
I
was
saying
at
the
top.
People
have
thousands
of
clusters,
basically
under
management
here,
but
when
I
go
to
create
this
you
can
see.
I
can
actually
configure
everything
about
my
event
in
a
single
screen
and
when
I'm
ready
to
apply
it.
B
This
is
not
some
configuration
that
just
sits
on
codefresh.
This
is
actually
going
to
make
a
commit
into
git
the
product
that
I'm
showing
right
now
is
called
code
fresh
software
delivery
platform.
I'm
glad
somebody
asked
that,
but
I
can
commit
this
into
git,
and
so
everything
that
you've
seen
is
not
just
some
ui.
Everything
you've
seen
is
actually
a
front
end
for
what
is
stored
in
git,
so
this
is
all
being
done
in
a
git
ops
friendly
way.
B
B
B
So
we
have
a
lot
of
experience
with
this,
with
our
with
steps
that
we've
built
where
people
are
using
these
hundreds
of
millions
of
times,
essentially
over
100
million
times
between
all
the
steps,
and
so
today
we
are
announcing
code
fresh
hub
for
argo.
C
Yeah-
and
this
is
essentially
we're
providing
you
reusable
templates
for
argo
workflows,
and
this
is
available
today,
so
if
you
want,
you
can
definitely
check
it
out
on
our
website.
We
already
have
some
certified
templates
that
are
available
for
you,
and
I
think
dan
can
speak
to
the
security
aspect
in
regards
to
that.
B
Yeah
one
of
the
things
that
we're
doing
is
everybody
that
contributes
or
our
argo
workflow
templates
to
this
hub.
Each
one
is
always
gets
a
security
scan
and
we
also
have
a
certification
process
that
you
can
go
through.
This
is
for
the
community.
You
can
use
this
in
our
workflows
on
your
own
instances.
It's
going
to
work
everywhere,
so
really
exciting.
Go
check
it
out
code,
fresh
dot,
io,
slash,
argo,
slash
hub
it's
available
today,
and
this
announcement.
We're
really
excited
to
offer
this
to
the
community
and
we're
committing
to
maintain
it.