►
Description
Special guest Dan Garfield from Codefresh joins us to talk about the things that Codefresh is working on, the CNCF OpenGitOps, and how Codefresh is providing GitOps functionality with their SaaS offering.
Dan Garfield is a co-founder and co-chair of the GitOps Working Group. As the Chief Open Source Officer of Codefresh he leads OSS contributions and strategy. He is also a member of the Forbes Technology Council and a Google Developer Expert. He focuses on helping teams adopt GitOps to deploy more often and with greater confidence.
About OpenGitOps
CNCF Sandbox project for lasting programs, documents and code from the GitOps Working Group.
https://github.com/open-gitops
Follow us:
Dan Garfield Twitter https://twitter.com/todaywasawesome
Dan Garfield GitHub https://github.com/todaywasawesome
Christian Hernandez https://twitter.com/christianh814
Chris Short https://twitter.com/ChrisShort
What is GitOps Guide to the Galaxy?
Every other Thursday at 3am ET hosts Christian Hernandez and Chris Short sit down to discuss everything in the GitOps universe, from end-to-end CICD pipelines to creating Git workflows.
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_c...
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
Openshift.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #GitOps #Kubernetes
A
A
B
B
So
cool
yeah,
so
we
do
have
a
special
guest.
I've
been
lining
him
up
a
lot
of
a
lot
of
cool
special
guests.
We
have
another
one
here:
dan
garfield
from
from
code,
fresh
dan
I'll.
Let
you
let
you
introduce
yourself
and
then
we'll
we'll
get
to
talking
about
a
lot
of
cool
stuff.
That's
happening
in
the
get
ups
world.
Sure.
C
C
Right,
yeah,
that's
right
and
my
background.
You
know
I
was
a
full-stack
engineer
for
a
number
of
years
and
then
spent
a
lot
of
time
on
the
the
comm
side
of
things
and
done
a
lot
of
evangelism
work.
Google,
developer
expert
and
member
of
the
forbes
technology
council
and
basically
just
want
an
excuse
to
talk
about
get
offs
talk
about
devops
talk
about
delivering
software.
B
B
B
B
A
rough
a
rough
outline,
but
I
I
never
mind
deviating
so
dan-
is
actually
also
a
part
of
the
get
ops
working
group
right
and
so
dan
you're
a
co-chair.
I
believe
you're
one
of
the
one
of
the
co-founders
as
well
for
the
get
ups
working
group
you
know
kind
of.
Can
you
talk
to
us
a
little
bit
about
like
the?
B
C
Yeah,
so
a
lot
of
people
know
that
the
that
git
ops
is
a
concept
came
out
of
weaveworks
a
few
years
ago,
and
the
idea
was
really
simple.
You
know
we
just
you
wanted
to
have
some
it.
You
wanted
to
build
on
the
ideas
of
infrastructure
as
code
and
kind
of
codify
where
to
go
with
it
and
what
we
saw
happening
over
the
last
few
years
is
this
term
github's
people
were
like.
Oh,
I
really
like
that.
C
I
really
like
this
idea
of,
like
I'm
doing,
operations
like
pull,
requests,
I'm
doing
operations
through
git,
and
that
feels
like
a
good
pattern.
I'm
embracing
the
infrastructure
as
code
stuff
and
what
we
found
really
quickly
is
that
get
offs
was
like
spreading
out
suddenly
and
people
were
like
talking
about
like
oh
I'm
doing
get
up
so,
oh
like
I'm
doing
it
up,
so
I'm
not
doing
git
ups
and
and
then
people
were
like
well,
you
know
I
do
a
git
commit
and
then
and
then
something
gets
deployed.
B
C
B
A
C
C
B
B
C
Yeah,
so
so
to
have
this
standard
that
is
like
no.
These
are
these
are.
This
is
what
it
means
if
you're
doing
get
ups.
These
are
the
things
that
you're
doing.
It's
not
meant
to
be
gatekeeping
and
say:
oh
you're
not
really
doing
get
ups,
but
it
is
meant
to
set
like
you
know.
This
is
this
is
where
you
want
to
get
to.
This
should
be
where
you
where
you
go,
and
so,
if
you
come
into
the
room
and
you're
saying
hey,
we've
fully
adopted
githubs
and
you're.
C
Looking
at
the
standards
and
you're
saying
oh
there's
some
stuff
in
here
that
we
haven't
been
doing
well,
it's
food
for
thought.
You
know
I
mean
it's
not
like
you
have
to
adopt
it,
but
to
get
a
bunch
of
companies
in
the
room,
and
at
this
point
I
think
we've
had
over,
like
70
different
companies
participate
in
the
principal's
formation
and
sign
on
as
interested
parties,
and
things
like
that.
C
They
want
to
make
sure
that
their
infrastructure
is
complying
and
can
be
managed
in
a
git
ops
kind
of
way
so
to
give
them
like
the
template
of
like
this
is
what
it
is
that
helps
them
do
that,
so
it's
not
just
for
that.
It's
also
to
create
patterns.
It's
also
create
standardized
ways
of
approaches
to
things
so
that,
ultimately,
all
of
us
should
spend
a
lot
less
time
reinventing
the
wheel.
We
should
be
able
to
kind
of
just
pick
up
patterns
and
move
forward
and
save
a
lot
of
time.
Ideally.
B
B
It's
it's
more
of
a
goal
right
like
if
I
want
to
do
get
ups
like
okay.
What
what
do
I
do?
What
standards
do
I
follow
now?
There's
like,
like
you
know,
industry
standard
or
a
a
vendor-neutral
way
of
meeting
that
right
and
less
of
a
like
you're
out
of
the
club?
It's
like!
No,
if
you
want
to
be
in
the
club,
you
know
here's
here's
what
you
do
right
and
it's
not
like
you
said
dan,
it's
not
for
everyone,
people,
I've
talked
to
people,
it's
like!
C
B
B
Yeah
yeah,
exactly
exactly
exactly
and
which
is
which
I
think
I
think
is-
is
really
great-
that
we
that
the
working
group
has
all
these
all
these
minds
coming
together.
It's
really
like
a
think
tank
right.
It's
less
of
a
of
you
know
a
club
and
more
like
hey,
let's
bring
all
of
our
best
practices
and
kind
of
just
distill
that
so
it's
really
exciting
to
see.
Definitely.
C
C
Know
yeah
and
he
was
like
he's
like
you-
get
up
people
with
your
your
hipsters
and
your
we
were
doing
this
stuff
in
the
90s
he's
like
we.
We
had
like
components
that
were
on
the
infrastructure
that
we're
pulling
and
deploying,
and
I
was
like
actually
like
pretty
excited
to
hear
about
what,
like
they
had
been
doing.
You
know
20
years
ago
and
and
how
advanced
it
was
and-
and
I
kind
of
thought
about
it-
I
said
you
know,
I
think
what
we're
really
trying
to
do
is
what
henry
ford
did.
C
Yeah
henry
ford
didn't
invent
the
car,
but
he
made
it
so
everybody
could
drive
one
so
we're
really
trying
to
take
the
stuff
that
you
guys
were
doing,
which
is
awesome
and
distill
it
and
make
it
simple
and
easy
to
adopt,
and
this
is
where
we're
going
with
argo
right
and
red
hat's,
like
a
big
part
of
that.
This
is
where,
where
weave
is
going
with
flux,
it's
about
making
all
those
components
just
like
turnkey
and
accessible,
and
it's
like,
let's
just
get
it
out
to
the
masses.
B
B
B
A
B
Assembly
line
sort
of
thing
right,
it's
like
hey.
I
want
to
deliver
my
application,
let's
send
it
along
the
assembly
line.
This
is
how
you
kind
of
do
it,
and-
and
it's
really
like
you
know
chris,
like
what
you
said
I
always
mentioned
your
your
quote.
Right
is
like
get.
Ops
is
like
the
the
holy
grail
of
devops.
B
Yeah
right,
it's
like
it's.
What
devops
has
been
trying
to
do
and
like
now
we're
in
that
place
right
with,
with
kubernetes
and
and
and
software
like
argo,
cd
and
things
like
that
that
we're
actually
getting
to
that
point
where
it's
like
yeah,
we
can
actually
do
a
lot
of
the
stuff.
We've
been
trying
to
do
all
these
years,
final,
yeah,
yeah,
finally,
yeah
so
dan.
B
I
I
know
that
you
guys,
you
know,
I
I've
interacted
with
you
guys
with
you
specifically,
but
with
code
fresh
right
like
not
even
in
the
get-ups
working
group,
but
also
like
with
our
go
cd
community.
Can
you
tell
us
a
little
bit
about
what
you
guys
are
doing
over
at
code
fresh?
What
would
you
know
what
what
you're
doing
with
argo,
what
you
know
all
the
you
know
what
what
is
it
well?
What's
that
saying
like?
What
is
what
would
you
say
you
do
here
right?
B
C
C
A
A
C
Of
different
stuff
going
on,
but
we
know
that
like
containerization,
this
is
the
future
and
we
want
to
make
a
big
bet
here
and
within
a
few,
like
you
know,
within
a
few
months,
we
we
got
really
deep
into
the
fundamentals
of
all
the
different
technologies
and
we're,
like
you
know.
We
really
think
kubernetes
is
going
to
be
the
future.
We
think
this
is
where
it's
going
to
go
right,
and
so
our
whole
platform
that
we
built
in
code
fresh
is
really
built
around
the
idea
of
building
and
deploying
software
in
a
cloud-native
way.
C
Now
that
doesn't
mean
that
we
don't
have
customers
who
are
deploying
to
vms
or
building
android
apps
or
whatever
we
do
we.
You
know
those
people
are
there
and
they
can
run
the
stuff,
but
the
big
advantage
comes
when
you're,
when
you're
using
stuff
like
kubernetes,
if
you're
using
serverless,
if
you're
using
those
cloud
native
technologies,
and
so
we
would
kind
of
talk
about
ourselves
in
terms
of
ci
cd
when
we
started,
but
it's
really
become
apparent
that
ci
cd
is
just
like
a
it's
a
term.
That's
been
completely
destroyed
when.
A
C
C
You
know
to
production
in
some
kind
of
way
or
have
some
kind
of
feedback
loop
coming
from
production,
and
it's
like
well
a
lot
of
ci
cd
tools.
Don't
really
have
that
they're
just
you
have
scripts
that
maybe
connect
into
a
deployment
or
something
like
that
and
it's
like
well,
it
should
be
done
in
a
declarative
way
and
you
should
have
monitoring
and
you
should
be
able
to
do
rollbacks
and
you
should
be
able
to
link
up
information
because,
ultimately,
the
push
and
pull
of
what
keeps
people
from
deploying
more
often
is
usually
about
fear.
C
It's
usually
like
I
want
to
deploy
more
often
except
I
don't
want
to
have
down
time
right
right
and
why
don't?
I
want
to
have
downtime
it's
expensive
and
it's
hard
to
figure
out.
What's
going
on
and
by
the
way
at
1500
micro
services,
I
could
have
a
regression
in
one
that
causes
a
bunch
of
errors
in
other
ones.
C
How
do
you
know
what's
going
on?
And
philosophically
you
know,
instead
of
being
an
all-in-one
platform
right-
and
I
think
openshift
is
a
great
example
of
like
a
kind
of
an
all-in-one
platform
right
that
does
a
specific
job.
That's
like
encompassing
really
well,
you
know,
gitlab
has
a
very
all-in-one
approach
where
it's
like.
You
store
your
source
code
here
and
your
appointments
here,
we
kind
of
said
we
want
to
be.
C
We
want
to
connect
with
whatever
git
provider
you're
using
and
we
want
to
connect
with
whatever
deployment
environment
you're
using
and
then
we
want
to
be
completely
inclusive
about
that.
But
then
we
just
want
to
let
you
integrate
with
the
best
and
breed
tools
across
the
board.
You
like
sneak
for
security
scanning
great
plug
it
in
it's,
going
to
work
great.
It's
going
to
be
like
a
first
class
citizen.
You
know
you
want
to
use.
You
know,
aqua
security,
great!
You
want
to
use
git
lab.
C
You
want
to
use
github,
you
want
to
use
bitbucket,
you
want
to
use
vs
code
great,
you
want
to
use
gcp,
you
want
to
use
openshift,
you
want
to
do
some
vm
deployments,
whatever
that's
great
we're
going
to
be
agnostic
about
those
things,
because
we're
going
to
be
really
really
good
at
that
deployment.
You
know
loop
and
process.
C
C
C
What
if
you
want
to
do
it
at
scale
right?
What
if
you
want
to
do
it
with
with
extra
security
and,
like
you
know,
identity,
management
and
all
those
kinds
of
things?
And
what,
if
you
want
to
do
it
with
support?
That's
where
code
fresh
is
going
to
come
in
and
we're
going
to
provide
a
lot
of
value?
On
top
of
that,
so
we
have
customers
like
we
have
a
healthcare
customer
that
basically
has
a.
They
actually
have
a
kubernetes
cluster.
C
Basically
in
every
hospital
really
cool
use
case,
they
used
to
update
these
things.
They
didn't
have
a
cluster
before
right,
but
they
used
to
have
services
that
they
would
run
in
these
hospitals
and
to
update
them.
Somebody
would
have
to
walk
in
with
a
usb
drive.
You
can
imagine
it's
like
it's
healthcare
right,
so
it's
high
security.
C
C
So
what
we've
done
is
we've
depl
is
they've
deployed
the
code
fresh,
get
ops
agent,
which
is
built
on
top
of
argo
and
has
some
additional
like
tooling,
on
top
of
it
into
all
of
those
clusters,
and
then
they
manage
it
from
a
single
control
plane,
and
so
now
they
can
get
updates
out.
You
know
right
away
immediately
and
and
when
you
think
about
that
with
healthcare,
it's
like
that's
pretty
cutting
edge.
B
C
B
C
So
today
the
production
we've
had
three
deployments
that
have
happened.
You
can
see
how
many
deployments
were
happening.
You
know
over
any
given
time
period
and
one
of
the
things
you
can
do
is
like.
If
you
were
looking
at
a
regression,
you
could
actually
drill
down
and
be
like.
I
want
to
see
all
the
deployments
that
happen
during
this
time
frame,
because
this
is
when
my
regression
started
and
you
can,
you
can
see
all
those
and
once
you
do,
you
can
see
like
okay.
C
Not
only
do
I
see
like
the
commits
and
the
pull
requests
and
what
what
services
were
actually
updated,
but
I
can
actually
jump
straight
into
the
the
the
the
jira
issue
and
like
see
what
issue
was
being
solved
with
this
deployment,
and
so
when
you're
trying
to
track
down
like
okay,
I've
got
1500
micro
services.
I
have
regression,
something
is
happening.
Okay,
it
started
during
this
time
period.
Okay,
I
can
see
three
deployments
happen
during
that
time
period.
One
of
these
jared
tickets
is
very
much
related
to
the
thing.
C
That's
currently
not
working
well,
okay.
Now
I
can
just
I
can
kick
in
and
do
a
rollback
or
or
or
narrow
down
the
issue
very
quickly.
So
this
gives
people
a
lot
more
confidence
to
be
able
to
like
drill
down
into
like
you
know
what
the
potential
issue
might
be
and
then
for
our
for
other,
like.
I
would
think
that
the
you
know
for
other
customers
and
things
like
that,
where
they
have
lots
of
deployments,
lots
of
environments.
C
You
think
about
somebody
that
has
you
know
1500
clusters
that
are
maybe
in
edge
locations,
maybe
they're
in
vpcs
or
whatever,
to
be
able
to
basically
get
the
roll-up
view
all
at
once
of
what's
happening
and
drill
down
into
that.
That
just
brings
a
ton
of
confidence
and
you
could
take
like
argo
cd
as
an
open
source
product
right.
So
you
could
go
take
that
open
source
and
then
just
install
it
on
1500
clusters.
But
then
it
gets
really
hairy
trying
to
manage
it
and
try.
B
Call
what
they
call
them.
That's
that's
pretty
cool
I've
seen
also
some
some
of
the
projects
that
you
guys
are
so
are
argo,
for
those
of
you
don't
know,
is
actually
a
a
whole
project
right.
It's
not
just
argo
cd,
there's
other
things
in
it
code
fresh
has
been
heavily
involved.
Actually
you
guys
created
the
the
autopilot
right.
Can
you
talk
a
little
bit
about
the
autopilot.
A
A
C
So
this
this
is
really
about
the
push
and
pull
between
opinionated
and
unopinionated
right,
and
so,
if
you
use
argo
cd,
it's
actually
pretty
flexible,
there's
kind
of
some
default
pathing.
But
if
you
go
out-
and
you
did
a
survey
right
now-
of
people
who
are
using
argo
cd,
very
few
of
them
actually
have
argo
cd
sitting
in
git.
C
C
Yeah,
it's
always
what
crunchy
strategy
should
I
use
yeah
you've
given
me
an
amazing
hammer
right,
but
like
what's
the
blueprint
for
the
thing
that
I
should
actually
be
building
right,
so
yeah.
So
argo
cd
is
like
this
great
great
tool
that
you
have,
but
it
doesn't
necessarily
tell
you
exactly
how
you
should
do
all
that
stuff.
So
argo
cd
autopilot
is
an
attempt
to
do
that
and
I'll
share
I'll
just
show
like
I
won't
give.
C
C
Yeah,
it
might
be
in
my
brain,
but
it's
definitely
syntax
yeah,
so
yeah.
So
you
run,
you
run
basically
repo
bootstrap
and-
and
you
only
need
to
be
connected
to
your
cluster
once
for
this,
and
what
this
will
do
is
it
will
bootstrap
a
git
repo
with
all
of
the
files
and
and
configuration
that
is
for
the
cluster,
and
then
it
will
connect
to
the
cluster
and
then
apply
all
those
changes
and
then
from
there
on
out,
every
change
to
your
repo
will
be
automatically
reflected
back
into
your
cluster.
C
So
this
allows
you
to
manage
argo
cd
using
get
ops
and
also
sets
up
a
bunch
of
patterns
that
you
can
just
follow.
So
if
I
look
at
this
repo,
you
can
see
it's
been
a
little
while,
since
I
did
anything
with
it,
but
in
the
bootstrap
you
can
see
argo
cd
is
defined
in
here
and
then
we
this
is
actually
using
customize.
C
We
are
going
to
be
adding
support
for
helm
soon.
It's
like
the
most
requested
feature,
but
all
the
configuration
is
in
there
and
if
I
went
into
like
my
projects,
you
can
see
I've
got
a
prod
project
and
a
staging
project,
and
then
what
I
can
do
is
under
my
customize
I'll,
have
my
application
and
my
application
will
have
an
overlay
for
each
environment,
so
I
can
make
my
commit
to
staging
and
I'll
have
some
customization
there.
C
That's
you
know
specifying
whatever
image
is
gonna
be
deployed,
and
I
can
have
you
know,
changes
made
there
and
so
to
make
a
change.
I
make
a
change
to
this
file
which
will
push
it
to
staging
and
then
once
I'm
ready,
I
basically
push
the
same
change
into
production
and
then
I'll
have
you
know
whatever
changes
that
whatever
customizations
I
put
under
production.
This
allows
me
to
move
things
from
staging
to
production,
and
so
this
pattern
is
just
it's
dead,
simple.
C
It's
really
hard
to
mess
up
and
I
think
if
you're
just
getting
started
started
with
with
doing
get
ops
with
doing
argo
cd,
I
would
highly
advise
just
starting
with
argo
cd
autopilot
because
you
get
all
that
stuff
for
free
it.
Just
bootstraps
it
for
you,
it
sets
up
the
repo
and
then
you're
just
making
tweaks
and
changes
there.
And
then,
if
your
cluster
is
destroyed,
you
connect
your
new
cluster.
You
rerun
the
bootstrap
with
a
new
environment
and
it'll,
set
it
up
and
and
be
running.
B
Yeah
what
what
I
really
liked
about?
What
about
autopilot
is,
I
always
take
elements
of
what
everyone's
doing
right.
People
always
ask
me
like.
How
do
you
do
your
directory
structure
and
I'm
like
honestly,
it
changes
week
from
week
because
I
see
other
people's
repos
and
I
go
that's
a
great
idea.
So
some
of
the
things
like
you
guys,
you
had
you
had
the
bootstrap
right
concept
and
I'm
like.
Oh
that's,
pretty
cool.
B
I
like
that
directory
structure
of
like
the
bootstrap
and
then
like
components
and
overlays,
and
I've
actually,
instead
of
using
autopilot.
Traditionally,
I've
done
it
with
hell
right,
which
is
basically,
it
was
just
a
wrapper
around
from
applying
all
of
these
into
the,
but
it's
really
just
like
a
a
an
ignition
more
like.
This
is
my
point
of
entry
of
deploying
this
way
I
like
how
autopilot
does
just
all
that
for
you,
it
removes
me
from
having
to
write
a
helm
chart
right.
B
C
Well,
and
even
like
a
nice
component
here,
so
you
can
see
like
if
you're
creating
an
application
you
specify
the
source
of
that
application
as
a
git
repo.
So
what
do
we
have
here?
You
have
basically
a
git
repo
for
each
application,
and
then
you
have
a
git
repo
for
your
infrastructure,
where
maybe
all
of
those
applications
come
in
and
all
the
configuration
is
all
in
one
infrastructure
repo.
So
that
makes
it
very
simple.
It's
like
it's
like
a
two
repo
approach.
So
I'm
doing
my
I'm
doing
my
changes.
C
My
application-
and
this
is
basically
triggering
you-
would
want
to
maybe
introduce
an
additional
process
here
where
you,
where
you
trigger,
like
pull,
requests
off
of
application
repos
to
your
infrastructure,
repo,
but
your
infrastructure,
repo
is
all
set
up.
You've
got
you
know,
you're
good
to
go,
but
that's
what
we
advise
most
of
our
customers
to
do,
and
most
of
our
customers
are
doing-
is
like
a
two-stage
process,
where
they
have
their
application,
repos
separate
from
their
infrastructure
repos,
and
that
solves
a
lot
of
problems
that
just
simplifies
things
and
conceptually.
B
B
That's
always
a
point
of
contention
that
I
find,
and
it's
it's
not
until
you
do
it
that
you
understand
why
we
give
the
suggestion
of
separating
your
code
repo
from
your
application
repo,
because
intuitively
you
want
to
have
it
all
in
one
right
intuitively
you
want
my
application,
has
a
life
cycle
and
the
configuration
for
that
application
should
move
with
the
application,
and
actually
your
infra
has
a
completely
different
life
cycle
than
your
code
base.
It's
like
a
completely
different
and
most
and
most
people
use
trunk
based
development.
B
When,
when
using
configuration,
right
infrastructure
repos
that
you
they
basically,
you
know
do
a.
What
do
you
call
it
a
feature,
branch
they'll
test
on
it
and
then
they'll
just
merge
it
into
the
trunk
right,
which
is
usually
main
and
then
they'll
just
delete
that
and
it
most
people
are
like,
are
hesitant
to
do
that
because
they
intuitively
want
to
put
everything
together,
but
actually
those
are
two
completely
different.
Life
cycles,
your
application
and
your
infra
completely
different
life
cycles.
Well,.
B
Yeah
yeah,
exactly
exactly
all
you
know
you
talking
about
floating
tags,
I'm
completely
against
floating
tanks
as
well.
For
that
same
reason,
right,
like
having
a
prod
tag
versus
the
like
an
actual
versioned
tag
is
that
goes
against.
Like
the
get
ups
principles,
I
guess
right
the
fact
that
that
you
can't
version
the
the
the
image
because
it's
always
pointed
to
a
floating
tag
right,
because
I
can
make
a
push
to
prod
and
everything
changes
all
of
a
sudden
so
see
here,
see
if
there's
any
questions.
B
C
Zoom
in
for
any
future
stuff,
that's
a
good
comment,
and
then,
but
by
the
way,
the
point
of
hey
lots
of
plus
ones
for
separation
makes
the
icd
and
testing
easier,
that's
100,
true
and-
and
this
this
also
makes
it
a
little
bit
easier.
So,
like
you
know,
ideally
what
you've
defined
and
get
is
what's
getting
deployed
right
and
if
you,
if
you're,
pushing
a
change
in
an
application
repo,
you
know
ideally
you're
able
to
test
it
before
it's
merged
and
all
that
stuff,
you
know,
gets,
gets
easier
for
sure.
B
Yeah,
I
know
for
for
sure
see
here:
where
are
we
on
time?
Well
we're
doing
pretty
well
on
time.
Let's
so
you
know,
you
know
dan
and
I
were
part
of
the
the
the
working
group.
Oh
by
the
way
our
our
website
just
went
live.
I
forgot
about
that
yeah
I'll
put
in
the
chat
opengetops.dev
here,
some
of
the
stuff
we've
been
working
on,
if
you
guys
want
to
get
involved
in
open,
get
ups
open,
get
ups
working
group,
I
put
the
link
in
the
chat
there.
It's
live.
C
The
thing
that
we
need
to
do
now
is
we
actually
had
like
70
people.
I
think
it
was.
Maybe
I
can't
remember
how
many,
but
a
lot
of
people
were
involved
in
the
creation
of
git
ops
as
a
standard
and
have
said
that
they're
interested
parties,
but
we
haven't
stuck
their
logos
on
the
website
because
when
they
put
their
names
there
we
didn't
say
and
we're
gonna
put
these
all
on
the
website.
So
if
somebody's
out
there
listening
you're
thinking,
hey
we've
been
involved
in
this
we've
we've
been
an
interested
party.
C
We
want
to
be
part
of
this
open,
get
off
standard,
go
open,
a
pr,
and
just
add
yourself
as
a
member
that
that's
like
the
quickest
thing
you
can
do
is
add
yourself,
add
your
company
as
a
member
and
and
we
can
just
plug
it
right
in
and
merge
it
and
guess
what
if
it
gets
merged,
it's
gonna
be
on
the
site.
So
there.
A
C
C
B
Yeah,
you
can
see
all
of
our
repos
there.
The
website
is
the
one
for
the
website,
intuitively
so
cool,
so
yeah.
So
we're
you
know.
So
we
were
part
of
the
working
group
that
is
driving
open,
get
ops.
We
actually
have
an
event
coming
up,
so
we
actually
have
a
get
ops
con
right.
The
the
the
cfp's
just
closed.
We
actually
got
a
lot
of
submissions,
so
I
need
to
block
off
my
calendar
to
review
those.
So
those
of
you
who
submitted
them.
Thank
you
very
much
right.
B
B
What
what
is
if,
if
you'd
like
to
share,
if
you
can
share
just
some
of
the
things
that
you're
thinking
around
building
really
building
this
community,
really
building
get
ops
in
terms
of
like
get
ops
con?
What?
What
is
your
vision?
I
I've
always
during
our
meetings.
We
we
actually
me
dan
and
I
we
talk
fairly
often-
and
I
you
know,
I
always
see
him
passionately
talk
about
his
plans
for
get
ops
guns.
So
I
like
to
give
you
this
platform
to
you
know.
C
C
So
several
additional
companies
have
done
buy-in
for
open,
get
up
for
keep
on
saying
open
ghost
con
for
just
get
ops
con.
So
this
is
actually
opening
up
to
additional
sponsors
and
some
of
the
community
might
be
thinking
like.
Why
do
I
care
if
there
are
additional
sponsors
there
like?
What
do
I
care
if
mcdonald's
shows
up
well?
C
You
know,
implementations
of
git,
ops
and
what
we
think
is
git
ops
as
a
standard
is
valuable
and
to
the
extent
that
we
can
make
it
an
open
standard
that
everybody
takes
part
in
we're,
going
to
make
that
pie
much
larger
for
everybody
and
everybody
can
adopt
it
faster
and
everybody
get
more
value
out
of
it.
And
it's
going
to
be
great
right.
So
it's
not
we
don't.
C
We
don't
want
to
have
like
this
centrally
controlled
thing,
and
this
was
like,
like
kubernetes,
the
biggest
value
of
kubernetes,
and
everybody
will
say
this
over
and
over
again
has
been
the
api,
and
people
have
said,
like
maybe
kubernetes
won't
be
a
thing
in
five
years,
but
the
api
will
like
it'll,
be
it'll,
be
plugged
into
something
else.
Maybe,
but
you
know
who
knows
if
that
will
happen,
but
that
api
is
is
really
valuable
and
we
want
githubs
to
be
the
same
way.
C
C
You
know
all
of
these
principles
that
we've
been
when
we've
been
working
on
and
talking
about
those
things
can
be
long
lasting,
so
to
have
get
ops
con
potentially
become
its
own
standalone
event,
not
just
a
co-located
event,
but
like
three
days
talking
about
how
to
do
git,
ops
and
like
pushing
the
envelope
okay,
how
do
we
bring
it
to
vms?
How
do
we
bring
it
to
these
other
services?
C
How
do
we
bring
it
to
stateful
services
and
and
there's
so
much
to
talk
about
in
deployment
and
life
cycle
management
here
that
I
think
it
could
easily
be
its
own
standalone
conference
that
could
be
really
big,
so
that
all
depends
on
how
many
people
register
and
the
sponsorship
levels
and
all
that
stuff.
So
if
you're
thinking
about
it,
we'd
love
to
have
you-
and
I
will
tell
you
that
the
cfp's
and
you've
seen
this
christian
and
chris
you're
on
the
committee
as
well
cfp's
been
really
good.
C
At
some
point,
we
we
we.
Basically,
we
were
looking
at
like
five,
we'll
we'll
see
if
this
you
know
goes
in.
Maybe
I
shouldn't
speak
about
it
too
much,
but
we've
got
like
a
bunch
of
really
big
name
companies
that
are
doing
git,
ops
at
scale,
and
it's
like
geez
like
maybe
we
can
at
least
get
a
panel
with
all
these
people,
because
there's
so
much
to
talk
about
there's
plenty
enough
for
a
full
conference
next
year.
So
the
the
day,
zero
event
at
kubecon,
I
think,
will
be
really
cool.
B
Yeah,
no
definitely,
and
I
think
I
think
that
I
think
you
you
hit
an
interesting
point
that
I
wanted
to
make
is.
Is
that,
like
we
have
just
so
much
content
that
it
literally
can't
fit
in
one
day
so
sponsorship's
important,
so
we
can
make
it
a
three
day
event.
So
that
way
we
can
have
multiple
tracks
right.
We
can
have
multiple
speakers.
We
can
include
more
people,
we
can
have
lightning
talks.
B
C
C
A
B
A
B
B
Like
I
want
to
attend
the
spinnaker
one,
but
that's
at
the
same
time
as
this
other
one
and
it's
like
well,
which
one
do
I
attend,
there's
only
one
one
day:
zero
right,
so
even
the
the
you
know,
cloud
native
con
kubecon,
even
the
day,
zero
stuff
is
starting
to
get
crowded
right.
So
you
know
the
more
the
more
stuff
we
got.
You
know
more
attendees.
We
got
the
more
sponsorship.
B
We
got
the
more
we
can
make
the
case
for
actually
having
a
full
event
right
and
speaking
of
events
right
then
I
know
you
want
to
talk
about
argo
con
right
like
we're
busy
guys
by
the
way.
So
I
want
to
talk
a
little
bit
about
about
about
argo
con
that
we're
supposed
to
be
having.
I
think,
I
believe,
at
the
end
of
this
year,
right.
Yes,.
C
B
C
But
but
argo
khan,
this
is
really
exciting.
We're
doing
the
first
argo
con
ever
there's
never
been
a
conference
for
argo,
and
if
you
look
at
argo
and
like
we're,
we've
been
kind
of
a
competition
between
argo
workflows
and
argo
cd
to
see
which
one
gets
to
10k.
First
and
argo
workflows
is
now
at
like
9600
and
argo
city's
fallen
to
like
6
800.
C
Know
definitely
go
star.
Those
repos
if
you
get
a
chance,
but
there's
a
lot
of
interest
in
that
community.
There's
a
lot
of
experts
in
that
community.
There's
a
lot
of
excitement
there
and
it's
growing
faster
than
almost
any
other
project
out
there.
It's
growing
faster
than
any
other
cd
related
project.
That's
that's
out!
There
certainly
is
popular
at
all,
so
it's
it's
been
growing
very
quickly,
so
for
us
to
be
able
to
host
argo
con
and
we're
doing
in
partnership
with
red
hat.
So
it's
code,
fresh
and
red
hat
are
hosting
it.
C
Sponsorship
is
open
too.
You
know
if
other
people
want
to
come
and
sponsor,
we
want
to
make
it
open.
It's
possible
we're
going
to
do
it
in
sf
and
we'll
also
broadcast
it.
So
we'll
have
an
online
component
as
well.
Currently,
tickets
are
99,
but
early
bird
pricing
is
available.
You
get
tickets
for
20
bucks
for
the
in
person
and
online
is
free.
So
that's
if
you
haven't,
registered,
go
and
do
it
right
now.
It's
just
just
search
argo
con,
throw
it
throw
the
link
in
the
chat,
but
yeah.
C
This
will
be
really
cool.
We'll
have
the
maintainers
there
you'll
have
a
chance
to
talk
with
maintainers
we'll
have
some
some
fishbowl
sessions
and
we'll
also
have
a
lot
of
people
are
submitting
talks
right
now.
We
already
have
a
lot
of
cfps
they've
been
really
really
good
for
that
one
as
well,
and
lots
of
people
who
are
doing
argo
at
scale.
You
wanna
you
wanna,
hear
from
somebody
who's
got.
You
know
a
few
thousand
clusters
under
management
with
argo
cd.
You
want
to
talk
to
somebody
who's
doing.
C
You
know
millions
of
argo
workflows
and
even
to
plug
in
with
like
argo,
rollouts
and
and
to
hear
about
like
argo
events,
which
is
like
a
whole
nother.
You
know
ball
game,
there's,
there's
so
much
going
on
with
argo
and
then
we
also
have
argo
labs.
A
lot
of
people
don't
know
about
argo
labs,
but
argo
cd
autopilot
is
in
argo,
labs
and
there's
some
really
cool
data
pipeline
stuff.
Coming
up
in
argo
labs,
so
like
to
be
able
to
feature
all
that
content.
C
We
really
needed
our
own
standalone
conference
to
do
it
so
very
excited.
So
far
the
registrations
have
been
like
beyond
expectation.
So
I
actually
thought
when
we
put
up
git
ops
con,
I
was
like
get
ops.
Con
will
be
really
really
big
and
argo
khan,
you
know
be
a
little
bit
smaller
and
it's
like
argo
khan
might
outpace
get.
C
B
I'm
actually
actually
registering
right
now,
yeah,
I
have
people
pinging
me
actually
excited
now
about
like,
like
you
know
here,
on
slack
and
the
red
hat
slack
about
argo
khan,
so
nice
yeah,
that's
gonna,
be
that's
gonna,
be
really
cool!
Argo
con
san
francisco
I'll,
be
there
get
the
twenty
dollar
one
because,
like
even
even
if
you're,
not
sure,
because
it's
like
for
twenty
dollars
right
like
it's.
Oh
my
god,
you're.
A
B
C
B
C
And
as
the
project
grows
like
guaranteed
you
like
next
year,
you
know
in
two
years,
like
it'll,
be
a
little
bit,
you
know,
there'll
be
a
lot
more
people
there
and
it'll
be
more
challenging
to
connect
with
with
people
in
a
significant
way.
So
those
are
always
my
favorite,
like
kubecon,
is
almost
getting
a
little
too
big.
For
me
now.
C
B
A
B
B
C
So
our
sas,
offering
is
certainly
popular,
but
our
most
popular
is
our
hybrid,
offering
where,
like
we'll,
we'll
manage
the
control
plane
for
you,
but
all
of
your
components,
your
build
components,
your
deploy
components,
although
it's
on
your
infrastructure,
yeah
that
hybrid
model
has
become
really
really
popular.
So
that's
like
the
the
the
majority
of
our
customers,
are
doing
that
hybrid
model
where
they
have
all
their
secrets.
C
All
their
stuff
is
on
their
own
infrastructure,
but
they
have
a
control
plan
that
they
manage,
that
we
manage
and
that
way
you
like,
updates,
are
automatic
and
all
those
kinds
of
things
that's
really
helpful.
But
we
do
have
people
and
banking
customers
and
finance
comp
customers
come
to
mind
that
are
doing
full
on
prem,
where
they
manage
the
control
plan
themselves,
but
we've
actually
had
customers
who
said
we're
gonna.
Do
the
full
managed
control
plan?
You
know
our
security
people
won't.
C
B
C
B
C
C
Yeah,
I
think
I
mentioned
a
couple
like
sneak-
is
good
aqua's
good
twist,
lock
is
good.
I
don't
know
if
I
have
a
really
strong
opinion.
If
you're,
if
you're
doing
open
source
clear
scanning,
is
pretty
darn
good
and
has
basically
has
most
of
the
same
database
stuff
that
exists
in
the
premium
offerings,
so
I
would
like
start
with
that,
but
then
I,
like
any
of
those
yeah.
A
C
Yeah,
we
definitely
I
mean,
and-
and
I
think
both
of
you
are
probably
on
the
are
on
the
talk
I
think
you're
both
on
the
talk
committee
yep
for
that
as
well
definitely
end
user
talks.
You
know
we
want
to
see
people
that
are
doing
really
interesting
things
with
argo.
There
was
a
great
talk
if,
if
you're,
not
in
the
argo
community
meetings
that
happen
once
a
month,
there's
usually
a
talk,
that's
given
once
a
month
or
so
by
a
different.
C
You
know,
end
user
of
argo
and,
like
we
had
somebody
give
a
talk
one
time
about
doing
argo,
cd,
air
gapped
really
interesting
possible,
oh
yeah
yeah,
and
it
was
really
cool
how
they
set
that
up.
So
that
was
really
interesting
to
hear
about
so
interesting
use.
Cases
interesting,
end,
user,
stuff
and
interesting
doesn't
always
mean
you're
doing
something
like
weird
like
like
I'm
not
like.
Oh
I'm,
not
I'm,
not
air,
gapping,
argo
cd
and
dropping
it
out
of
the
c130
so
like.
Is
it
really
weird?
You
know?
Is
it
really
interesting
enough?
C
The
truth
is
that
even
just
even
just
a
story
about
like
how
you
got
your
organization
to
buy
in
that's
something
that
people
deal
with
as
a
challenge,
so
just
think
about
the
unique
things
about
your
use
case,
and
maybe
it's
maybe
it's
a
lot
of
scale.
Maybe
it's
just
how
simple
you've
made
it.
Maybe
it's
how
you
got
people
to
adopt
it
end
user
talks.
Definitely,
you
know,
take
the
cake,
that's
what
we're
looking
for
the
most.
C
If
you
have
interesting
projects
you
built
on
top
of,
if
you're,
if
you're
doing
some
stuff
in
argos
and
argo
labs-
and
you
want
to
talk
about
like
a
project
you
want
to
get
going
there,
we
we
one
time
at
a
helm
conference.
Have
somebody
come
in
and
give
a
talk.
That
was
like
here's
everything
wrong
with
helm
and
I
think.
A
C
B
B
Like
those
are
also
interesting,
don't
think
like
it
has
to
be
a
success
story
either
like
if,
if
you
have
you
know
this
is
what
I
tried.
This
is
how
it
messed
up.
This
is
what
I
would
do
different
is
always
always
welcome.
I
I
think
those
are
those
are
also
insanely
popular
as
well,
so
it
doesn't
have
to
be
a
feel-good
story
either.
A
C
We
have
a
bunch
of
ebooks
right
then,
and
things
that
are
like
oh,
how
to
do
kubernetes
at
scale
how
to
do
microservices
scaled.
The
most
popular
ones
are
the
ones
that
are
like
kubernetes
anti-patterns
like
these
are
all
the
things
that
people
do
wrong
with
kubernetes
and
those
are
like
way
more
popular
people
love
to
read
about
that
a
lot
more
and
they
like
to
read
about
how
to
do
something
right.
B
Yeah
exactly
which
is
always
always
fun,
it's
also
there's
an
old
old
adage.
What
is
it
if
you
want
like
with
it?
People
too,
like
if
you
want,
if
you
want
the
answer,
if
you
want
an
answer,
don't
ask
a
question
post
the
wrong
answer,
post,
the
wrong
answer
and,
and
then
someone
will
they
will
come
and
like
okay,
thank
you.
You
know
it's
like
yeah
people
like
bad
bad
stories,
for
whatever
reason,
so
here.
A
B
That's
that's
kind
of
an
interesting
use.
Well,
there's
also
an
interesting
use
case.
We
we've
here
at
red
hat.
We
have
the
concept
of
namespace
argo
versus
a
cluster
argo
right
where
a
lot
of
people
use
openshift
as
a
multi-tenant
system,
and
so
we
have
this
concept
of
having
okay.
You
have
an
argo
cd
that
manages
this
name
space
and
only
this
name
space.
You
know
this,
you
know
argo
cd,
the
name
cd
is
is
is
what
it
does
right
for
application
delivery.
A
B
B
A
A
C
C
C
A
C
If
you
don't
want
to
go
to
the
the
contributor
experience
is
more
about
like
project
management,
a
few
like
discussion
around
some
big
issues
and
things
like
that,
and
then
we
have
like
a
ux
ui
meeting.
That's
that's
twice
twice
a
month,
but
the
the
monthly
community
meeting
for
the
individual
projects
are
often
the
most
interesting
you'll.
Have
somebody
give
a
talk,
or
somebody
share
an
interesting
use
case
or
they'll,
be
discussion
about
the
roadmap
or
you
know
those
kinds
of
things.
B
B
A
A
B
C
C
Actually
that
that
reminds
me
of
maybe
another
point
of
get
ops
here,
while
we're
while
we're
talking
about
it,
is
the
whole
value
of
deploying
more
often
isn't
just
that
you
get.
The
value
of
you
know
faster
releases
and
more
features
and
you're
more
competitive,
but
it's
also
from
a
risk
perspective,
you're
able
to
just
patch
things
more
quickly
and
almost
every
hack
that
happens
is
because
of
unpatched
software.
That's
not
only
just
been
unpatched,
but
it's
been
unpatched
for
a
while,
because
their
soft
delivery
process
isn't
good.
C
B
A
A
B
C
C
Where
we're
going
is,
I
would
say
that
we're
building
on
git
ops
in
a
kind
of
interesting
way,
where
a
we're
thinking
about
git
ups-
and
I
I
just
talked
about
the
importance
of
standards-
a
whole
bunch
at
the
top
of
the
hour
and
I'm
kind
of
now
saying
like
and
where
do
we
want
to
go
on
top
of
that?
So
extending
the
standard
maybe
get
ops?
C
I
I'd
like
to
get
to
the
point
where
we
think
of
git
ops,
not
just
as
encompassing
you've
defined
all
of
your
deployment
environments
using
git,
ops
and
they're
managed
in
a
way,
but
also
in
a
way
of
all
of
your
tooling,
is
defined
in
a
git
oriented
way.
So,
like
all
of
the
policies
around
pipeline,
all
the
policies
around
security
and
where
we're
going
and
building
is,
is
also
instead
of
thinking
about.
C
You
know:
testing
pipelines
in
terms
of
scripting
thinking
about
them.
In
terms
of
policy,
that's
defined
in
git,
and
so
maybe
I
don't
write
you
know,
maybe
I
don't
have
a
step
that
says:
do
the
security
scan
and
here's
all
the
instructions
of
how
to
do
it?
Maybe
I
just
say
this
security
scan
needs
to
be
completed
right
right,
and
this
is
what.
C
Yeah
and
so
so
now
continuously
yeah.
Now
I'm
doing
my
build
processes,
my
test
processes,
my
deployment
processes,
all
in
a
declarative
way,
that's
and
all
of
that's
defined
in
git.
So
I
think
of
that
as
kind
of
an
extension
of
git
ops,
but
it's
also
a
change
in
the
way
that
you
think
about
how
you
build
and
deploy
and
and
we've
we've
built
a
lot
of
abstractions
on
top
of
scripting
and
if
you
think,
even
like
a
make
file
is
like
well
I'm
using
a
make
file.
C
B
C
So
so
I'd
like
us
to
to
go
beyond
that
and
think
of
like
no.
I
have
a
policy
that
describes
what
is
needed
and
I
don't
worry
about
it
after
that,
and
and
that's
that's
true
from
a
security
perspective
and
again
we're
not
we're
not
a
security
company,
we're
going
to
integrate
with
every
security
company,
but
to
allow
you
to
give
the
definition
in
such
a
way.
I
think
that'll
be
really
interesting.
What
we're
doing
with
progressive
delivery
is
really
exciting,
where
we're
going
with
what
we're
building
on
top
of
our
go.
C
Rollouts
is
really
interesting
how
we're
looping,
together
and
combining
all
the
argo
projects
so
that
it's
almost
like
it's.
It's
really
its
own
distribution
of
argo
and
it's
kind
of
hardened
for
enterprise,
and
it's
you
know,
got
some
extensions
for
scale
and
things
like
that
and
then
just
tying
it
all
together,
so
that
you
have
all
the
information.