►
Description
Who doesn't love a good end user story? In this episode we are joined by Jaime Magiera from the University of Michigan where he will talk about how they are using Argo CD and OKD in their environment. Grab some popcorn, and get your questions ready!
Want to learn more?
https://www.youtube.com/watch?v=dnUhWmednQs
Try Red Hat OpenShift: https://red.ht/3sMaW7O
Follow us:
Christian Hernandez https://twitter.com/christianh814
Hilliary Lipsig https://twitter.com/Int2Caffeinate
Jamie Magiera https://twitter.com/jaime4a2
OpenShift https://twitter.com/openshift
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
What is GitOps Guide to the Galaxy?
Every other Thursday at 3pm ET host Christian Hernandez and guests dig in to discuss everything in the GitOps universe, from end-to-end CICD pipelines to creating Git workflows.
Learn GitOps https://red.ht/3saqlzS
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 on redhat.com https://red.ht/3LGCIeD
OpenShift on GitHub https://github.com/openshift/
#RedHat #GitOps #Kubernetes
A
A
A
B
A
A
Love
this
should
be,
you
know,
there's
there's
always
a
everyone
says:
there's
like
an
uber
for
x
right.
We
should
do
like
a
like
an
uber
for
dogs
right,
so
that
would
be
cool.
So
we
are
joined
here,
special
guest
here,
jamie
from
the
university
of
michigan,
and
so
why
don't
you
introduce
yourself
real
quick
to
to
those
to
those
who
are
who
aren't
familiar
with
you,
who
haven't
gone
to
the
okd
meetings?
Who
haven't
gone
to
the
open,
get
ups
meetings.
C
A
That's
a
busy
busy
busy
man
here,
so
it's
I'm
excited
to
have
to
have
jamie
out.
So
what
the
reason
I
had
him
on
he!
Actually
he
did
a
presentation
at
the
okd,
sorry
openshift
commons
day
of
get
ops,
and
I
he
did
a
fantastic
presentation
about.
You
know
what
he's
doing
over
there
at
university
of
michigan,
and
you
know
all
the
stuff
he's
doing
with
the
open
source
aspect
of
it.
A
What's
really
cool
what
I
really
like
about
like
education
and
what
about
jamie's
doing
is
like
like
open
source
kind
of
has
its
roots
in
the
education
system
right
like
if
you
have
ever.
If
you're
like
a
nerd
like
me
and
read
history
about
like
like
like
bsd
and
unix
and
like
hall,
you
know
in
linux,
and
I
call
all
that
stuff
happens
in
universities,
so
all
that
stuff
still,
you
know
open
source
software
still
is
being
used
in
university.
A
So
I
like,
I
always
like
people
who
are
you
know
using
okd
right
using
the
the
open
source
version
right
of
openshift
that
we're
using
you
know,
argo
cd
directly.
You
know
which
is
the
core
of
openshift
getup.
So
that's
always
really
cool
we're
always
really
exciting.
He
did
a
great
presentation
there.
I
thought
you
know
what
like,
let's
bring
him
on.
Have
him
explain
kind
of
what
he's
doing
there?
Two
quick
notes,
though,
before
I
kind
of
just
you
know
hand
it
off
to
jamie
there
have
have
it
be.
A
The
jamie
show
one
get
up
con
is
on
so
get
up
con.
It's
happening
right.
So
that's
on
schedule.
The
schedule
is
out
right,
I'll,
be
there.
Hillary
will
be
there,
so
hillary
will
be
there
so
we'll
both
be
there.
So
at
get
ups
con
and
kubecon
so
stop
by
and
say,
hi
and
hopefully
we'll
see
walid
there
right
so
walid.
I
know
I
think
you're
going
so
one
of
our
longest
viewers
here.
A
So
I
hope
to
see
you
there
also
cfps
are
open
for
argo
khan,
so
argo
con
will
take
place
in
in
the
bay
area
right
we're,
gonna,
it'll
it'll
be
actually
at
the.
I
don't
think
it's
announced
yet
wait
hold
on.
Let
me
see
here,
it's
not
officially
announced,
so
I
won't
tell
you
exactly
where
it
is.
I
might
get
in
trouble.
A
If
I
tell
you
what
we
decided
on
and
it
doesn't
go
through,
but
it'll
be
in
the
bay
area
mountain
view,
area
of
san
francisco
right,
if
you're
in
the
san
francisco
california,
the
bay
area
it'll,
be
a
three-day
event,
so
cfps
are
open.
So
if
you,
if
you
have
a
cfp,
please
you
know,
let
us
know
if
you're
doing
anything
cool
with
argo
jamie.
You
can
maybe
I'll
call
you
out
here.
Maybe
you
can
do
a
cfp.
There
will
be
a
virtual
component.
A
It'll
be
a
hybrid
event
right
there'll,
be
a
virtual
component,
it'll,
be
on
on-site
components,
so
check
that
out.
I
put
that
link
in
the
chat
for
argo
con,
so
I
think
with
that.
I
will
pass
it
over
to
you,
jamie
and
yeah
kind
of
just
go
over
like
what
are
you
guys
doing
over
there?
The
university
of
michigan,
with
with
everything,
right,
okd
tech.
D
A
C
Yeah
so
you're
right,
there's
a
long
history
at
the
university
of
michigan
in
terms
of
open
source
and
standards
and
sort
of
the
technologies
that
underlie
the
internet
and
software
development
and
whatnot
so
ldap
in
part,
designed
here
at
the
use
of
michigan.
The
initial
sketches
for
how
the
internet
would
be
how
the
nodes
would
work
out
and
the
the
network
architecture
star
network
was
on
a
napkin
at
a
hotel
here
in
ann
arbor.
C
This
is
the
inter
university
consortium
for
political
and
social
research
and
we
provide
leadership
and
training
in
data
access,
curation
and
methods
of
analysis
for
social
science,
research
community,
and
we
provide
data
for
research.
So
it's
like
a
clearinghouse
basically
of
research
data
that
other
entities
can
use
to
to
fill
out.
C
Their
research
and
researchers
can
then
submit
their
research
into
these
repositories,
so
we
write
software
that
allows
folks
to
submit
research
data
and
also
to
pull
research
data
out
and
and
also
to
to
do
the
sort
of
the
paperwork
of
it.
Signing
off
disclosures
and
stuff
like
that,
and
so
this
is
something
that
is
very
web
application.
Heavy
and
kubernetes
fits
right
in
with
that
process
and
then
git
ops
is
almost
essential.
C
Some
of
the
problems
that
we
had
at
icpsr
are:
you
know
we
originally
started
out
with
just
a
handful
of
developers
and
engineers.
Literally,
just
you
know,
under
six
engineers
and
a
handful
of
developers,
and
then
those
respective
groups
have
grown
to
dozens
just
in
the
past
couple
of
years.
As
you
know,
data
becomes
more
and
more
important
in
political
and
social
research
right
in
in
terms
of
access
to
large
amounts
of
data.
C
I
should
say,
and
so,
although
development
was
being
done
in
the
changes
were
not
accurately
synchronized
to
the
clusters
continuously,
the
deployments
were
not
accurately,
they
were
being
modified
and
synchronized
in
real
time
like
you
really
need
to
do
to
get
that
ci
cd,
going
and
and
really
realize,
the
benefits
of
ci
cd
and
microservices
were
not
deployed
in
unison
for
applications,
so
some
applications
work.
Some
microservices
work
really
well
as
a
globally
available
microservice.
C
C
Another
issue
that
we
had
that
we
needed
to
resolve
is
configuring
external
resources.
So
if
you
have
a
microservice,
that's
going
to
might
have
a
database
in
aws.
It
may
be
relying
on
traditional
apache
solar,
which
is
a
basically
a
data,
indexing
type
of
service
right
or
elasticsearch
things
of
that
nature.
You
might
have
those
running
outside
of
the
cluster.
You
need
to
interact
with
those,
so
we
said.
D
C
We
can
we
can
automate
the
process
of
updating
the
configurations
for
the
solar
and
whatnot,
but
how
do
we
make
sure
that
the
developers
and
the
devops
engineers
can
make
those
changes
and
get
and
have
the
pipelines
synchronized
properly
into
the
cluster
and
pipeline
runs
properly
synchronized
into
the
cluster?
To
then
launch
those
pipelines
to
affect
those
external
resources
and
you'll
see
what
I'm
talking
about
in
a
second
and
then,
of
course,
the
underlying
infrastructure
of
the
clusters
getting
those
synchronized
very
quickly.
C
C
So
a
couple
of
the
solutions
that
we
came
up
with
to
to
really
work
with
the
get
ops
model
and
and
and
with
argo
cd,
is
we
separated
out
the
application
code
from
the
deployment
code.
It
used
to
be
that
git
sort
of
had
one
each
project,
meech
microservice,
had
sort
of
everything
all
in
one.
The
helm
charts
were
all
in
in
with
the
code
and
christian.
C
I
know,
you've
got
a
opinion
on
on
that
as
well,
and
I
share
that
opinion
that
I
think
that
those
two
should
be
separated
out.
So
we
separated
those
out.
We
simply
separated
out
the
application
code
from
the
deployment
code
and
we
created
an
external
dependency
configuration
so
that
basically,
these
external
resources
that
was
talking
about
dependent
resources
in
aws
or
vms
that
are
running.
C
So
I
created
helm,
charts
for
various
parts
of
infrastructure
that
argo
can
then
synchronize
and
we
can,
for
example,
version
our
pipelines
and
then
argo
synchronizes,
those
helm
charts
for
the
pipelines
out
there
and
those
are
versioned
and
we
can
keep
track
of
them
really
well,
and
you
know
we
use
argo
in
all
steps
of
this
to
provide
that
synchronization.
There's
a
lot
of
tools
out
there.
C
C
There
you
go
okay
great,
so
we
have
a
variety
of
clusters.
As
I
said,
we
have
development
clusters
that
are
okd
and
ocp,
and
these
are
used
for
dividend,
quality
assurance
stages
or,
as
I
said,
we're
changing
to
sit,
and
then
we
have
production
clusters
that
are
ocp,
and
these
are
used
for
our
user
acceptance,
testing
and
production
stages.
So
in
essence,
we
have
four
stages.
We
actually
have
a
fifth
sort
of
tangential
stage,
which
is
a
or
a
side
stage.
C
C
A
C
We're
able
to
duplicate
those
configurations
across
all
of
the
clusters
for
things
that
need
to
be
the
same
across
all
of
them
and
then
also
individualize
them
for
clusters.
So
this
is
our
our
our
use
of
argo
cd
for
sort
of
that
day,
two
or
hour
two,
so
I
call
it
configuration
and
here's
our
our
overall
process
here
you
can
see
you
know
cute
little
icons.
Basically,
that
lay
out
everything
is
working.
C
You
know:
we've
got
helm,
git
lab
argo,
cd,
aws
and
open
shift,
and
its
various
flavors
here
and
they're
all
talking
to
each
other
and
argo
cd
is
providing
that
that
you
know
that
crucial
step
of
communication
between
git
lab
and
the
cluster
and
and
there's
a
lot
of
web
hooks
in
there
that
you
don't
see.
I
simplified
this
down
quite
a
bit.
Otherwise
arrows
and
lines
like
going
all
over
the
place.
A
What
I'd
like
to
call
out
here
is,
is,
I
guess
this
is
a
question
statement.
Is
that
I
think
it's
pretty
cool
that
you're
running
okd
in
dev
and
qa
and
then
ocp
in
production
right
and
so
which,
which
I
think
a
lot
of
people
do
like
not
a
lot
of
people
say
that
they're
doing
that,
which
I
I
just
by
the
way.
I
think
it's
great
right,
it's
kind
of
like
the
nature
of
red
hat's,
open
source
right.
It's
like
we
just
use
upstream
bits.
It's
not
like
it's!
A
C
You
know
exactly
so
one
of
the
reasons
we're
using
ocp
is
because
fedora
core
os
the
operating
system
underneath
okd
is
not
fips
compliant
right
it.
There
isn't
a
switch
that
you
can
turn
on
to
use
the
the
fips
approved
encryption
and
that's
something
that
they're
aware
of
there's
a
there's.
An
issue
opened
up
with
the
fedora
coreos
folks
on
it.
C
Whether
that
will
get
addressed
in
the
future
is
unknown,
but
our
work
requires
the
majority
of
it
requires
fips
compliant
encryption,
and
so
that's
one
of
the
reasons,
and
the
other
reasons
is
it
allows
us
to.
It
allows
us
to
allow
the
developers
to
really
bang
around
in
things
at
a
lower
price
point
than
licensing
and
openshift
right
right.
C
Exactly
and
and
there's
a
couple
of
operators,
quite
frankly
that
are
not
available
that
are,
for
example,
some
of
the
operators
like
logging,
I
think,
are
not
available
in
okd.
They
haven't
been
created
and
provided
in
a
community
repo.
Yet
because
there's
some
specific
red
hat
bits
that
are
in
some
of
those
operators,
okd
working
group,
is
in
communication,
with
red
hat
on
resolving
that
situation
and
making
more
of
the
operators
more
parity.
I
guess
between
between
the
operators.
A
I
don't
know
if
you're
gonna
go
over
it,
but
I'm
curious
and
by
the
way,
for
those
hillary
as
well
and
who
are
wherever
don't
let
me
bogart
all
the
questions
right.
If
you
have
questions,
please
drop
them
in
the
chat
I'll
I'll
push
them
on
over.
But
I
have
questions
because
I'm
geeking
out
here
too
so.
B
A
Like
it
like
put
their
entire,
you
know
stack
as
an
application
right
like
so.
If
I
have
a
three-tiered,
you
know
dumb
three-tier
application,
some
people
just
stuff
it
all.
In
one
application,
some
people
break
those
up
into
three
individual
applications,
and
so
they
can
manage
those
individually.
So
I
know
you
have
some
government
stuff
that
you
need
to
keep
protected,
but
like
what
can
you
tell
us
about
how
you
know
what
you
guys
do
and
how
you
came
about
that
decision.
C
Sure
so
one
of
the
things
that
we
found
is
that
some
some
some
stuff
works
really
well
in
a
single
application
like
multiple
helm,
charts
all
in
one.
So
the
way
that
we,
let
me
just
talk
about
how
we
do
it
so
how
we
do.
It
is
you'll
notice
that
we
have
here
destinations
that
are
in
a
single
cluster
here.
Some
things
that
we
know
will
be
across
multiple
clusters
and
stay
the
same.
C
C
Database
pipeline
and
then
we'll
have
deployment
resources
and
those
are
all
separate
because
they
will
have
different
uses.
Some
of
them
are
going
to
be
using
deployed
as
customized.
Some
of
them
are
going
to
be
deployed
as
straight
helm,
charts.
Some
of
them
are
going
to
be
deployed
as
the
the
directory
style
as
as
they
call
it
inargo.
C
A
Sort
yeah
and
that's
another
thing
like
like
with
with
customize.
I
know,
there's
like
you
know,
a
few
ways
to
skin
that
cat
right
and
then
it's
you
know
what
works
for
me
may
not
necessarily
work
for
you,
because
your
production
is
going
to
look
way
different
than
mine.
You
know
what
I'm
doing
so.
I'd
definitely
be
curious
to
see
to
see
that
like
now
now,
I'm
geeking
out
harder
so
so.
C
D
C
A
A
D
A
C
C
These
are
tecton
pipelines
in
case
that
wasn't
clear
and
so
titan
pipelines
have
like
four
different
components.
They
have
an
interceptor
which
is
like
your
web
hook.
Basically,
and
then
they
have
a
bind
that
connects
a
pipeline
template
to
listener
and
then
you've
got
the
pipeline
template
and
so
there's
like
four
different
components
that
are
involved
in
a
webhook
triggered
tecton
pipeline,
and
so
we
have
all
of
those
resources
in
a
helm
chart
and
then
we
deploy
that,
and
so
these
are
the
builds.
C
C
We
just
update
the
git
repository.
Argo
picks
that
up
picks
up
all
the
changes
and
all
of
the
individual
cluster
project
name
spaces
for
each
microservice,
then
get
that
updated
pipeline
and
then
all
of
the
updated
tests.
So
this
is
an
example
of
really
just
you
know
not
just
the
the
build
itself,
but
the
build
resources,
the
pipelines
etc.
Taking
advantage
of
that
synchronization
via
argo
cd
and
so
here's
an
example
of
that
of
that
pipelines
for
a
build.
C
I
have
a
what
I
call
a
gate
emerge
request
gate
so
for
folks
that
know
git
lab
who
don't
know
git
lab.
When
you
do
a
merger,
it
will
trigger
the
web
hook
with
one
of
like
four
different
actions.
So
it's
like
open
or
create,
approve,
close
and
delete,
or
something
like
that.
There's
like
four
different
actions
and
the
web
hook
gets
called
regardless
of
which
of
those
four
actions,
and
you
have
to
actually
read
the
payload
to
do
that.
C
So
our
pipeline
has
a
gate,
basically
that
I
wrote
that
looks
for
a
particular
action
before
it
runs,
and
then
we
clone
the
repository
get
some
meta
information
about
the
repository
generate
a
location
for
the
image.
Then
we
do
an
s2i
java
build
a
source
to
image
java
build
and
then
we
tag
it
christian.
This
is
sort
of
similar
to.
I
think
you
did
a
show.
What
was
it
last
fall?
I
think
you
did
a
show
where
you
sort
of
showed
this
sort
of
a
process.
A
Yeah
yeah
yeah,
I
was
going
to
comment
and
like
this
is
kind
of
like
similar
to
the,
because
tecton
doesn't
currently
have
like
a
gate,
a
gating
picture.
It's
it's
essentially
what
what
you
need
to
do
is
kind
of
like
write
in
a
pr
in
the
pipeline
in
order
to
get
gating
right
so
yeah.
So
this
is,
I
was
going
to
say
this
is
like
like
I'm
like,
I'm
glad
that
I'm
not
crazy
and
so.
A
B
C
Yes,
yeah,
it's
it's
very
cool
because
so
get
ops.
You
know,
you've
got
the
one
component
if
you're
constantly
syncing
with
what's
in
your
repository,
but
there
are
times
when
you
need
to
have
commands
issued
to
get
something
and-
and
you
want
those
commands
stored
in
the
git-
basically
so
that
it's
it's
there
that
someone
issued
this
command
at
this
time.
So
there's
there's
two
benefits
right
to
to
doing
sort
of
git
bots.
A
Yeah
stuff
well,
and
also
it
it
kind
of
bridges,
the
like
the
imperative
tasks
right
and
the
declarative
rights
like
there's
like
there's,
there's
gonna,
be
some
imperative
steps
that
you're
going
to
need
to
do
right,
and
so
I
think
you
know
this.
You
know
having
that
those
those
bots
right
in
those
those
integration
points
are
extremely
helpful
right,
especially
when
you
know
you
need
to
run
like
you
know,
a
few
commands
just
some
things
you
just
can't
do
declaratively
right,
you
just
have
just
some
imperative
tests
to
do.
D
B
B
C
And
so
here's
just
a
quick
look,
so
you
know
deployment
resources.
We
have
separate
repositories
for
each
microservice.
Each
repository
is
a
helm
chart
for
the
code.
The
helm,
charts
are
published
and
packaged
and
published
to
a
registry,
and
then
the
application
level
repos
and
helm
charts
allow
for
quickly
collecting
microservices
into
an
application
christian.
I
know
you've
talked
about
this
before
on
the
show.
It's
so
essentially
we're
talking
about
helm,
charts
that
are
sort
of
parent
helm,
charts
that
reference
sort
of
child,
helm,
charts,
sub
and
charts
right
and.
A
Yeah,
like
they
call
I
actually
starting
trump,
I
actually
found
out
what
they're
actually
called
they're,
actually
called
umbrella
charts.
So
for
those
who
are
curious,
the
technical
name
for
it
is
because
they're
called
umbrella
charts
so
like
if
you're
like
it'll
help
in
your
googling.
So
just
a
little
tip.
D
D
B
A
C
Yeah,
so
we
have
a
helm
chart
library
that
I
created
that
allows
us
to
create
helm,
charts
really
easy.
It's
like
even
easier
templating,
because
you
can
just
drag
and
drop
basically
a
template
from
this
library
that
I
created
and
then
add
some
values
and
you
don't
even
have
to
mess
with
helm
templates
very
much
as
well,
and
all
the
deployment
repositories
have
pipelines
and
pipeline
runs.
Like
I
mentioned
that
get
synchronized.
C
Here's
an
example
of
the
deployment
repositories.
With
my
ubiquitous
taco
deployment
for
testing
purposes,
you
always
have
to
have
a
taco
repository
for
testing,
and
these
are
so.
These
are
the
umbrella,
helm,
charts
right,
and
so
this
is
you'll
see
on
the
right
hand,
side
different
micro
services
with
different
versions
that
are
all
helm
packages,
and
so
we
this
allows
that
umbrella
chart
right
to
pull
in
dependencies
of
different
versions
for
a
particular
application
and
so
and
you'll
see
some.
C
These
are
all
the
external
types
of
resources
that
we
want
to
manage
via
pipeline
and
and
use
argo
to
synchronize,
the
pipelines
and
the
pipeline
runs
actually
for
that
and
here's
customize.
This
goes
a
little
bit
to
what
we
were
talking
about
christian.
So
you
know,
customize
we
found
is
best
suited
for
singular
resources
on
that
are
not
part
of
like
a
collection,
and
you
can
modify
a
pipeline
run
existing
in
the
deployment
configuration
repositories
and
you
can
modify
smiles
which
require
only
very
small
changes.
C
So
we
would
break
out
to
a
separate
application
in
argo,
something
that,
under
these
circumstances,
you
would
use
customize
because
of
what
you
see
sort
of
listed
here
and
you
know,
helm
charts
for
managing
managing
pipeline
resources.
Here's
an
example,
sort
of
at
a
clearer
level
there,
those
those
four
files
that
I
remember
was
mentioning
there
and
argo
cd
can
reconcile
against
the
chart
for
full,
get
ops
right
and
syncing
the
pipeline
resources.
C
This
is
an
example
of
a
of
a
pipeline
file
here
and
so
here's
you
know,
argo
just
copies
these
over
within
the
helm
chart
some
of
them.
We
actually
just
do
as
individual
pipeline
runs
separately
that
are
in
the
rivas,
and
I
understand,
there's
some
new
stuff
coming
from
tecton
that
actually
is
pipeline
runs
in
the
repos
themselves.
Christian
you
may
know
about.
A
Yeah
yeah,
so
actually
I
was
thinking
about
maybe
having
a
show
on
that
called
pipeline
as
code
right,
and
so
you,
it's
essentially
pipelines
as
code
and
techdon,
is
what
you
know
kind
of
what
it
sounds
like
is
that
techton
reads
these
configurations
from
a
git
repo
right,
so
you
just
provided
a
git
repo
and
it
can
interact
with
your
with
your
repo
to
be
able
to
do
these
things.
What's.
D
A
Interesting
is
that
you're
actually
storing
the
pipeline
runs
or
because,
like
what?
What
I
end
up
doing
is
I
always
end
up
like
like
I
do
like
a
trigger
template
or
I
do
a
you
know
the
I
forget
what
they
call
it
now:
the
object
but
anyways
the
trigger
template.
What
it
does
is
you
basically
templatize
and
it
takes
a
payload
from
the
the
git
repo
and
just
takes
that
payload,
and
then
you
know
it
kind
of
parses
that
out
and
then
runs
that
pipeline
for
you.
C
Some
cases
yes,
so
it
depends,
it
depends
on
the
underlying
storage
needs.
It's
it's
because
of
this
thing
with
customize
that
it's
it's
a
bug
or
a
feature
depending
on
how
you
look
at
it.
So
customize
uses
the
name
metadata
for
its
modifications
and
if
you
want
to
do
generated
name
if
your
pipeline
run
needs
to
do
generated,
name
like
like
it
won't
be
like
that
run,
won't
be
delete.
C
So
here's
the
issue
if
you
are
going
by
name
and
you're
using
customize,
if
you
give
it
a
name
such
as
you
see
here,
it
won't
run
properly
in
open
shift.
If
you
run
customize,
if
you
sorry,
if
you
run
customize
and
pull
this
in
again,
if
the
run
has
previous
run
hasn't
been
deleted,
it
won't
run
again
because
it's
it's
the
same
name
and
so
because
there's
a
little
hack
that
you
can
do
of
using
said.
C
So
you
run
your
customize,
you
pipe
it
to
said
to
pull
out
the
name
metadata
and
turn
it
into
a
general
name,
metadata
item
and
then
feed
that
in,
but
obviously
that
wouldn't
be
something
that
we
would
be
doing
through
argo.
So
that's!
That's
a
case
where
we
wouldn't
be
using
argo.
If
we
need
to
have
unique
names,
because
we
don't
expect
that
that
pipeline
run
will
be
deleted
before
the
next
time
that
it
needs
to
run
yeah.
A
D
A
So
so
in
generated,
so
if
you,
if
you
supply
both-
and
this
is
kind
of
like
a
hack-
maybe
maybe
they
took
it
out
so
if
you
provide
both
when
you
apply,
the
manifest
generated,
name
takes
precedence,
but
if
you
have,
if
you
have
name
you
can
reference
that
name
in
a
customized
file
so
like.
If
so,
you
know
when
you're
you're,
patching
and
customize
you
have
to
reference
the
name.
So
it
knows
what
it's
patching
yeah.
A
C
D
A
Yeah
because,
ideally,
ideally
in
customize,
you
should
be
able
to
reference
a
generated
name
right,
because
all
it
is
is
a
prefix
like
it's
like.
Who
cares
what
the
suffix
is,
because
that's
going
to
be
applied
at
runtime
like
it's,
never
going
to
know
that
so
anyway,
so
yeah
test
that
out
I'll
see
so
we'll
we'll
see.
I
may
I
know.
A
C
You
know-
and
so
here's
you
know
syncing
pipeline
resources
the
via
customize.
So
if
I
need
to
update
all
of
the,
if
I
update
that
template
library
and
then
all
of
the
micro
services
that
use
that
template
library
need
to
be
updated
as
well,
I
can
use
customize
to
to
run
and
change
from
argo
customized
from
argo
to
change
the
references
in
all
of
those
and
so
here's
pipeline
for
x
resources,
and
so
this
is
deploying
it
based
in
aws.
C
Speeding
up
the
creation
of
the
web
applications,
configuration
for
external
dependencies
is
deployed
consistently
developer
new
applications
without
server
and
intervention.
Without
devops
intervention,
including
sort
of
one-off
instances
to
functionality
right
because
argo
can
be
running
in
the
background
and
synchronize
their
changes
from
the
git
reporter,
and
they
don't
even
necessarily
even
know-
need
to
know
how
to
modify
things
within
the
cluster
itself.
Right
and
the
process
of
promoting
applications
through
the
different
stages
is
efficient
and
way
less
prone
to
errors.
C
And
you
know,
resource
usage
can
be
tracked
at
a
higher
level
of
resolution
and
even
for
those
commands
we're
talking
about
you
know.
So,
if
you're
issuing
commands
to
trigger
things
or
modify
things,
those
are
stored
in
the
repo
which
in
turn
can
be
synchronized
to
the
cluster
in
various
ways
and
clusters
themselves
can
be
scaled
up
really
quickly
by
using
get
ops
principles
in
argo
cd
for
that
day,
two
stuff
or
hour.
C
Two,
as
I
call
it,
and
some
next
steps
separate
out
deployments
code
create
more
top
level
applications.
These
are
things
that
devops
and
developers
can
do
to
to
embrace
git
ops,
and
you
know
utilize
argo
cd
to
its
fullest.
I
think
you
know
create
top
level
applications
the
umbrella
application,
helm
charts.
You
know
clarify
that
delineation
between
software
for
an
application
and
software
for
multiple
applications
right,
so
some
microservices
might
be
used
for
only
one
application.
They
might
be
used
for
multiple
health
checks.
C
You
know
and
sort
of
that
mental
shift
to
thinking
about
the
microservices
that
you're
creating
are
you're
being
con.
It's
being
consumed
by
users,
but
also
other
development
teams,
are
consuming
your
software
as
well
and
think
communicate
in
terms
of
git
commit
hashes.
This
is
a
great
thing
for
synchronization,
with
argo
cd
and
with
techton,
because
you
that
when
you
start
thinking
and
and
and
coding
and
synchronizing
in
terms
of
git
hashes,
things
become
very
clear.
What
is
where
and
what
has
been
copied
over
to
the
cluster?
D
C
A
A
D
B
I
I
send
some
of
it.
I
don't
know
if
you
could
even
answer.
You
know
some
of
the
the
logistical
splits
behind
applications
that
need
to
run
more
monolithically
versus
applications
that
can
be
made
up
of
a
series
of
microservices,
and
I
I
don't
even
know
if
you
can
answer
that.
Most
of
my
questions
are
going
to
be
around
stuff
like
that,
because
it's
super
fascinating.
C
Sure
so
some
applications
are
monolithic
just
out
of
the
sheer
fact
that
they
were
written
years
ago
and
haven't
been
ported
over
yet,
and
so
they
are
monolithic
because
they
were
written.
Monolithic
and
breaking
them
off
into
microservices
is
a
task
that
would
take
many
development
teams,
many
hours
and-
and
we
just
haven't
gotten
there.
Yet
we
are
in
a
process
of
moving
over
a
lot
of
the
old
monolithic
service
applications,
monolithic
applications,
breaking
them
where
appropriate,
into
microservices
and
moving
them
into
the
into
the
cluster.
C
C
C
Books
and
sam
newman,
I
think,
does
a
good
job
of
pointing
this
out
is
not
everything
is
a
microservice
or
not.
Everything
should
be
a
microservice,
and
you
want
to
ask
yourself
like
what
are
the
benefits
and
you
want
to
do
a
cost-benefit
analysis
right.
What
are
the
benefits
and
what
are
the
downsides
of
doing
this
as
a
microservice,
and
so
we
have
a
whole
criteria
for
that.
That
would
probably
take
us
right
through
another
show
to
go
through,
but.
C
A
That
would
definitely
be.
I
was
just
thinking
that
yeah
first
of
all,
that
that
would
just
be
a
series
right.
It's
not
even
a
show,
just
one
episode
right.
That
could
be
like
a
series
of
talks
and
I
think
also
sometimes
you
just
have
tech
debt
and
so,
like
you
said,
like
it's
a
cost
analysis.
It's
like
do
we
you
know:
do
we
spend
the
time
and
money
to
break
this
up
into
a
microservice
and
like
you're,
not
gonna,
really
see
much
benefit
from
it?
I
think
a
lot.
A
That's
has
a
lot
to
do
with
where
the
benefits
of
something
like-
and
this
is
a
shout
out
to
andrew
who's,
watching
of
openshift
virtualization
right,
where
you
can
maybe,
instead
of
like
run
so
because
me
and
hillary,
had
this
conversation
on
slack
about
something
completely
separate
about
like.
Why
are
you
shoveling
shoving
your
monolith
in
a
container?
That's
you
know,
may
not
be
the
best
move
that
you
want
to
do
so,
which
is
something
like
kubert
right
and
I
guess
jamie
you
would
use.
C
A
C
Yeah
yeah!
Well
because
some
things
you
do
need
to
get
off
of
the
old
infrastructure,
and
maybe
you
maybe
you
can't
break
that
application
just
yet,
but
you
need
to
get
it
off
of
the
old
infrastructure,
and
so
in
that
case,
maybe
one
of
the
you
know
doing
it.
That
way
in
a
vm
is,
is
the
way
to
go.
Yeah.
B
Yeah,
I
think
my
favorite
thing
about
what
you
just
took
us
through,
and
this
is
something
that
is
always
my
favorite
thing
is
that
there's
several
different
technologies
that
you
have
orchestrated
so
that
you're
applying
the
best
tool
for
the
job,
so
you
didn't
go
over
it
in
your
slides.
I
know
you
mentioned
you
use
operators,
I
see
you're
using
helm,
charts
and
christian.
I
have
done
a
talk
about
these
two
topics
before
these
are
things
I
work
with
every
day.
B
This
tour,
you
gave
us
had
the
best
tools
for
the
best
job,
even
if
there's
technically
some
like
a
venn
diagram
of
overlap
of
functionality-
and
I
really
appreciated
that
and
that's
orchestrated
so
cleanly
and
also
shout
out
to
rick
hi
rick.
We
used
to
work
together
and
then
he
left
red
hat,
but
hi
rick.
A
A
It's
like
it's
a
yes
and
conversation,
not
a
butt
right,
like
you're
gonna
use,
you
know
using
the
best
tool
for
the
job
is
is
always
you
know,
is
always
the
way
to
go,
and
I
think
yeah
taking
you
know
taking
us
on
that
journey
that
that's
something
that
stood
out
to
me
as
well.
I
was
gonna
comment
like
you
know.
I
noticed
you're
using
a
little
bit
of
both
and
you're
kind
of
just
playing
to
the
strengths
of
what
you're
trying
to
do
and
using
that
that
tool.
C
Excellent
yeah,
I
mean
that's
something
that
you
know
it.
It
does
take
a
little
bit
of
work
because
you
have
to
familiarize
yourself
with
all
those
tools
and
you
have
to
get
your
teams,
your
devops
teams
and
your
developers
sort
of
familiar
with
these
different
ways
in
which
things
are
going
to
be
done.
C
A
And,
of
course,
I
miss
my
mute
button,
sorry
so
so
yeah.
So
if
anyone
has
has
any
questions,
please
drop
the
drop
that
in
we
are
almost
about
at
time
again.
Thank
you,
jamie
for
joining
us.
I
always
enjoy
end
user
talks.
People
always
enjoy
end
user
talk,
they
love
seeing
how
these
things
are
working
in
production.
I
personally
like
seeing
some
of
my
suggestions
being
used,
so
I
mean
that's
me,
that's
a
that's
the
leo
in
me.
A
Seeing
my
stuff
actually
being
used,
and
so
oh
yes,
someone
has
an
interesting
question
about
in
terms
of
security.
I
don't
know
if
I
know
we've
had
that
that
acquisition
of
stack
rocks
right.
That
has
been
open
source.
I
don't
know
if
you
guys
have
been
looking
into
that
or
have
you
been
using
other
tools
like
like
sync
or
I
forget
what
the
other
one
is
black
duck
something
black
something
duck
something
with
a
duck,
but
yeah
anyways
is.
C
D
A
Yeah
yeah,
I
had
foster
on
michael
foster,
who's
part
of
the
stackrock's.
One
sacrifice
community,
and
you
know
he's
the
acs
guy
here
at
at
red
hat
talking
about
supply
chain.
I
think
maybe
that'd
be
cool
to
maybe
revisit
that
the
supply
chain
and
kind
of
just
having
that
the
factory
of
of
trying
to
deliver
applications
and
constantly
scanning.
I
think
that's
that's
an
important
thing
to
be
a
little
blacked
up
is
what
okay
yeah
black
duck.
A
A
A
C
C
If
you
want
to
reach
out,
you
can
find
me
in
the
openshift
slack
channel
in
the
kubernetes
slack,
and
you
can
also
find
me
in
the
the
get
ops
channel
there
and
then
the
open
get
ops
channel
on
the
cncf
slack
and
you
know
check
out
any
of
the
working
groups.
I'm
involved
with
you
know:
okd
working
group
open,
get
ops,
working
group
and
you
know
fedora
core
os
working
group.
A
lot
of
great
stuff
happening
there
in
all
those
places
for
sure.
A
Awesome
awesome.
Thank
you.
Thank
you
for
sharing
that,
thank
you.
So
we
are
out
of
time
again.
I
appreciate
everyone
coming
on
jamie
appreciate
it.
Hillary
appreciate
it
I'll
appreciate
you
all
joining
and
geeking
out
with
us
for
the
hour
and
yeah,
so
everyone
stay
safe
out
there.
Hopefully
I'll
see
you
at
cubecon.
I
think
we
have
one
more
episode
before
kubecon
break
and
so
remember
to
like
subscribe
share,
especially
share.
I
appreciate
the
shares
right.
A
So
if
you,
if
you
go
to
our
youtube
channel
and
you
find
an
episode
and
you
think
it's
cool-
please
re-share
it-
you
can
find
that
I'll
actually
drop
it
in
the
chat
just
while
I'm
talking
about
it,
red.html
ups.
So
if
you
like,
the
video,
please
feel
free
to
share.
I
appreciate
every
share
and
yeah
and
with
that,
as
I
always
say,
unless
it's
in
git,
it's
only
a
rumor.
Thank
you.
Everyone
cheers.