►
Description
Scott Rigby and Cornelia Davis from Weaveworks return to dig a little deeper into the components of Flux on OpenShift. In the previous episode, Scott and Cornelia introduced Flux, and in this episode, we'll talk about some of the features of Flux a little more in-depth and reveal some OpenShift specific enhancements.
About FluxCD:
FluxCD is an open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
https://fluxcd.io/
Cornelia Davis is the CTO at WeaveWorks. She is responsible for the company’s technology strategy, inclusive of open source projects, commercial products, and services offerings.
Scott Rigby is a Developer Experience Engineer at Weaveworks. He co-founded the Basekamp art and research group in 1998 and the massively collaborative Plausible Artworlds international network. In technology, he enjoys helping develop open source software that anyone can use, most recently projects in the cloud native landscape including co-maintaining Helm and Flux.
Follow us:
Scott Rigby https://twitter.com/r6by
Cornelia Davis https://twitter.com/cdavisafc
Weaveworks https://twitter.com/weaveworks
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_confirmation=1
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
Yeah
yeah,
so
we've
had
so
much
fun.
Last
time
we
decided
to
invite
cornelia
and
scott
again
to
talk
about
to
kind
of
dig
a
little
bit
deeper
about
flux
and
and
how
it
relates
to
openshift
and
kind
of
just
pick
apart
the
pieces
just
a
quick
kind
of
quick,
a
funny
note,
I'm
actually
wearing
the
cuttlefish
t-shirt
today.
So
I
kind
of
want
to
say
there
was
a
there's
a
little.
You
know
funny
story,
I
guess
I
don't
know
just
small
antidote
about.
D
B
Yeah
yeah,
so
I
was
supposed
to
so
the
last
episode.
I
was
supposed
to
wear
it
and
but
it
didn't
come
in
time
and
then
I
checked
the
mail
that
that
day
after
we
finished
streaming
and
it
was
there
yeah.
Of
course
it
was
there.
Of
course
it
was
so
so
yeah,
so
I'm
I'm
I'm
ready
for
for
today.
I
got
my
t-shirt
on
and
and
yeah,
so
I
guess
I'll
hand
it
over
to
to
scott
and
cornelia.
I
guess
scott's
gonna
be
driving
today
talking
about
getting
getting
deeper.
E
E
You
don't
mind
I'll
I'll
I'll
chime
in
really
quickly
just
to
set
some
context
for
those
of
you
who
don't
know
us
who
didn't
come
last
week,
I'm
cornelia
davis,
cto
at
weaver
scott
will
introduce
himself
as
well,
but
for
those
of
you
who
didn't
make
it
last
week,
I'll
and
even
those
who
did
two
weeks
ago,
I
should
say,
is
that
two
weeks
ago
I
did
some
demos.
I
showed
you,
for
example,
the
operator
for
flux.
E
So
I
showed
you
how
you
can
go
to
the
operator
hub
and
you
can
download
and
you
can
install
flux,
but
I
really
focused
on
once
flux
is
in
there.
Let
me
show
you
what
you
can
do
with
it.
Let
me
show
you
these
different
get
ops
flows
that
you
can
build,
whether
you
are
doing
it
in
production
or
you're
doing
it
in
development.
You
might
want
different
flows,
and
I
showed
you
a
little
bit
of
observability
on
that.
So
it
was
more
from
the
the
perspective
of
what
you
can
do
with
it.
E
A
C
D
D
I'm
super
interested
in
open
source
communities
and
and
different
kinds
of
structures,
including
you
know,
the
rules
of
how
we
do
things,
governance
and
decision
making
and
just
I
think,
it's
a
really
interesting
way
to
help
think
about
our
future
as
a
species.
You
know
how
we
can
live
and
work
together.
So
I
like
code,
because
it
kind
of
like
puts
all
that
in
code
in
some
way
and
we
get
to
play
with
that
in
ways
that
that
that
we
can
kind
of
prove
it
out
so
yeah
yeah.
D
I'm
also
part
of
that
part
of
the
helm
team,
and
I
don't
know
if
I
could
call
myself
an
expert.
But
I
you
know
I
have
a
lot
of
things
to
show
and
to
help
with
and
I'm
trying
to
help
bridge
some
of
these
communities,
so
especially
the
the
get
ops
and
and
kubernetes
packaging
like
the
helm,
related
stuff.
So.
B
D
Right
areas
of
expertise-
I
guess
you
know,
but
yeah
yeah,
yeah
yeah.
No,
it's
really
the
the
all
these,
the
teams
that
really
make
all
of
this
work.
So
I'm
super
it's
thrilled
to
be
to
intercept
these
yeah
so
right.
So
what
I
was
just
going
to
do
was
show
not
really
so
much
about
openshift.
So
I
hope
I'm
not
being
I'm
my
demo
on
a
kind
cluster,
so
no
offense
to
openshift.
D
You
know
taking
something
that
you
most
many
people
are
probably
doing
now:
a
get
ci,
ops
approach
where
you've
got
you
know,
maybe
github
actions
or
circle
ci
or
whatever
jenkins
or
whatever,
making
event
driven
responses
to
the
things
that
you
do
inside
of
your
version,
control,
like
cornelia,
said
last
last
time.
This
is
just
it's.
How
do
you
migrate
that
to
a
different
tool
and
we're
going
to
be
focusing
on
flux?
Of
course,
there
are
other
projects
in
the
ecosystem,
but
we're
going
to
be
focusing
on
this
one.
D
C
A
A
B
D
D
C
D
Gonna
be
a
couple
more
so
as
as,
as
you
requested,
boom
kind
of
leaked
luster.
I
deleted
it
and
if
anybody
wants
to
know
it's,
it's
the
it's,
the
the
kubernetes
kind.
Sig
is
where
you
find
it
so
so
yeah.
So
what
I
was
thinking
as
this
title
might
imply
that
hey
people
want
to
know
how
to
do
some
fairly
basic
things,
things
that
are
that
they
usually
have
to
write
some
kind
of
scripting
around
doing,
and
I
was
thinking
here's
a
really
good
example.
D
D
You
know
whether
it's
like
you
know,
ingress
engine
x
or
traffic
or
whatever
else,
and
I
just
chose
traffic
for
simplicity
and
really
could
be
anything,
I'm
just
showing
you
how
really
how
it
installs
and
works,
I'm
not
going
to
be
demoing
all
of
these
applications
and
sir
manager
to
help
you
automate
your
your
certs.
So
this
is
this
is
primarily.
D
This
is
just
a
very
a
very
common
setup,
and
I
I
mention
this
because
I
myself
have
written
scripting
around
this
and
I've
seen
many
other
people
do
it.
So
so
I'll
show
you
how
you
can
do
that
without
this,
so
what
I
should
have
done
actually
I'll
do
this
in
a
sec.
While
I
describe
this
it'll
only
it'll
take
less
than
30
seconds,
so
I'm
just
going
to
create
a
little
kind
cluster
right
now,
nothing
but
no
special
setup.
D
D
The
audience
is
not
going
to
destroy
me.
Well,
you
wouldn't
be
able
to
so
again.
So
basically,
what
what
flux
requires
that
the
cli
is
you?
You
want
to
set
a
github
token
environment
variable,
and
this
is
all
in
the
read.
This
is
all
in
the
the
getting
started
guide.
So
I
don't
need
to
go
in
in
depth
here,
but
this
is
just
why
I'm
doing
this.
It's
so
that
flux,
the
bootstrapping,
the
bootstrap
command
that
I'm
going
to
show
you
will
both
create
a
a
source
repository
of
different
kinds.
D
Right
now,
I'm
going
to
say
it's
a
github
kind
and
I'm
going
to
put
it
in
my
own
in
my
own
personal
github
user,
and
I'm
going
to
make
it
private
and
in
order
to
do
that,
it
needs
it.
It
needs
a
personalized
access
token
and
I
just
gave
it
repost
scope.
That's
all
you
really
have
to
do.
You
can
see
it
in
the
in
the
guide,
but
so
I'm
gonna,
I'm
gonna,
go
ahead
and
and
silently
read
this
take
note
demo,
gods,
okay,
I've
just
I
made
a
bootstrap
token.
D
Yeah
without
show
you
without
showing
you
so
okay,
so
what
I'm
going
to
do
is
I'm
going
to
use
this
flux,
bootstrap
command,
real,
quick,
and
I
just
mentioned
what
it
does.
There's
a
lot
of
other
things
you
can
pass
to
this.
You
can
also
specify
specific
components
to
add:
I'm
just
going
to
do
the
out
of
the
box
defaults
at
which,
which.
D
Which
installs
the
I
didn't
really
bring
a
diagram
with
me.
I
could
show
it,
but
we
did
last
week.
Essentially
it's
going
to
install
the
flux
components
which
is
a
microservice
style
or,
let's
say
a
multi-service
style
tool.
So
it's
going
to
install
a
customized
controller,
a
a
flex,
customize
controller,
a
flux,
helm,
controller,
flux,
notification,
controller
and
those
are
what
we're
really
going
to
look
at
right
now.
C
E
What
you
can
think
of
flux,
bootstrap
of
doing
is
at
the
at
the
root
of
get
ops
for
kubernetes
is
that
I
need
some
automation
and
those
controllers
are
the
automation
that
we're
installing
on
the
cluster
I'm
going
to
do
some
stuff
over
in
git
and
for
those
of
you
who
maybe
are
a
little
bit
newer
to
get
ops
in
the
beginning.
I
really
focused
on
what
was
happening
on
kubernetes.
E
I
focused
on
the
automation
and
it
took
me
a
little
while
to
realize
that
a
big
part
of
what
we
do
with
git
ops
is.
We
do
a
whole
bunch
of
magic
on
on
on
your
behalf.
We
automate
not
only
what's
going
on
in
the
cluster,
but
we
automate
what's
happening
in
git.
That's
why
you
need
the
github
token,
and
then
we
establish
the
relationship
between
those
two,
and
so
it's
really
that
whole
bunch
of
things
that's
happening
here
and
so
I'll.
Let
scott
continue!
E
Those
controllers
are
really
that
if
you're
thinking
about
get
ops
get
ops
is
about
declarative
configuration
version
controlled
with
software
agents
that
are
keeping
things
in
alignment
with
what
your
desired
state
is.
He
just
talked
about
the
controllers
that
ensure
that
our
alignment
there's
the
other
parts
of
git
ops
as
well.
B
A
B
C
B
B
D
Great
yeah
cool
all
right
thanks
for
thanks
for
letting
me
know
so
yeah.
This
is
what
cornelia
just
was
just
like,
followed
up
on
my
way.
So
I
just
mentioned
that
this
is
just.
This
is
one
of
the
diagrams
that
stefan
drew
at
some
point
and
it's
used
in
the
flux
documentation.
I
know
we
showed
it
last
week,
so
I
won't
belabor
this,
but
essentially
oops.
You've
got
your
your
sources
right
now,
where
I'm
using
github
for
this
demo,
you've
got
a
fluff
source
controller.
D
B
D
D
D
Immutably,
it
doesn't
have
to
be
merchant
control
system;
it
just
has
to
be
immutably
versioned
declarations
of
what
you
want.
Your
of
what
your
desired
state
should
be
of
your
system,
so
so
this
source
controller
in
flux
looks
at
that
and
watches
for
changes,
and
it
and
the
other
controllers
interact
with
the
source
that
it
inspects.
D
So
that's
how
that's
how
that
works
home
controller
customize
controller.
Does
I
don't
want
to
get
too
deep
into
it
at
the
moment,
but
you'll
you'll
notice,
you'll
note
in
a
moment
that
we
use
customized
controller
to
apply
plain,
yellow
manifest
for
this,
just
because
I
did
this
very
recently
with
a
helm
demo,
I'm
skipping
over
all
of
the
other
like
cool
things
that
you
can
do
with
customize,
and
I'm
only
focusing
right
now
on
on
on
its
use
of
applying
plain
automatically
applying
plain
ammo
manifests
to
your
cluster.
D
E
So,
actually,
scott
before
you
will
you
scroll
up
just
a
hair,
and
so
I
just
want
to
point
out
that
the
that
you
know
the
kind
of
hand
wavy
description
that
I
did
you'll
notice.
If
you
look
at
all
the
things
that
bootstrap
did
it
created
repositories,
so
that
was
the
get
part
it
installed
this
stuff
on
kubernetes
and
then
it
established
connections
between
them.
So
all
of
that
stuff
is
reported
for
you
through
the
flux
bootstrap.
E
Now,
when
you
do
the
open
shift
install
flux,
we
also
set
up
some
of
this
stuff
for
you.
So
we're
not,
I
don't
think
we're
running
the
flu
flux
bootstrap
command,
but
we
might
be.
I
don't
remember,
mahmoud
or
calling
my
mood
built
the
operator
so
but
that's
effectively
what
we're
doing
so.
You
can
see
kind
of
under
the
covers,
what's
happening
when
you
install
the
the
open
shift
operator
for
flux.
B
Yeah,
I
think,
and
also
also
it's
important
to
point
out,
that
the
the
bootstrap
is
not
only
your
bootstrapping,
the
the
the
cluster,
but
also
your
repository
that
you're
going
to
be
interacting
with
right.
So
yeah
you
have
that
the
so
it's
kind
of
like
an
end-to-end
bootstrap,
not
necessarily
one
or
the
other.
D
D
D
D
D
D
D
Boom-
okay
done
all
right
so
now
I
could
have
probably
done
that
at
the
same
time,
I
probably
could
have
pushed
that
because
you
can
actually
your
repo.
You
can
bootstrap
an
existing
repass,
so
I
could
do
that
next,
but
just
to
keep
keep
on
topic
here,
I'm
going
to
I'm
going
to
put
that
extra
line
in
and
just
make
sure
to
specify
the
path.
It's
not
going
to
show
you
too
much
magic
here.
It's
really
just.
D
D
A
D
Let's
see
the
road
map
is
a
good
place
to
get
an
idea
of
what's
happening,
but
we
had
made
this
link
very
recently
to
get
to
give
a
timetable,
and
I
hope
it
helps
people
some
people
said
it
was
very
helpful.
Other
people
said
it
was
more
confusing
for
them
and
I
don't
know
which
is
right.
So
let
me
let
me
take
your
temperature
here's
a
table
with
dates.
Some
of
the
dates
are
tbd
because
we
can't
know,
but
it
is
actively
being
worked
on,
and
so
it's
you
know
imminent.
D
The
dates
are
you
know
what
happened
for
each
part
of
the
flux
project
on
that
date,
so
october
of
last
year,
flux1
and
went
into
maintenance
mode.
There's
some
details
about
that.
I
won't
like
waste
the
rest
of
our
demo
time
with
that
flux2cli
went
to
development
mode.
We
were
at
that
point
working
to
finish.
Parity
with
flux1
and
people
were
encouraged
at
that
point
to
test
flux.
Two
prereleases
in
non-production,
which
many
people
did
the
git
ops
toolkit
kit
by
that
date,
was
all
alpha.
D
So
this
is
just
a.
This
is
just
like
a
slightly
more
complicated
answer,
because
with
flux
one
we
could,
it
was
really
just
we
didn't
have
it
separate.
We
didn't
have
versioning
separated
because
the
system
wasn't
as
multi-faceted
as
it
is
now
it's
now.
It's
a
multi-service
architecture,
so
the
flux,
the
flux
2cli
uses,
cement,
simver
and
the
tool
kit
apis,
follow
kubernetes
api
versioning
pattern
and
we're
even
a
little
bit
more.
D
So
flux,
what
so
so
so
these
these
are
two
columns
because
it
just
had
to
be
that
way.
Flux
one
is
really
just
one
column,
it's
easy
to
it's
more,
it's
easier
to
describe,
or
at
least
it's
it's
less
faceted
to
describe
for
flux.
Two
we've
got,
we've
got
flux,
two
is
really.
It
really
has
two
parts:
one
is
the
client
or
the
cli,
and
the
other
is
is
the
get
ops
toolkit
which
is
the
what
we
I
think
at
some
point
called
an
sdk?
D
D
E
E
It
would
do
updates
from
the
the
image
registries
out
to
the
git
repositories.
Then
it
would
also
you
know,
deliver
over
into
kubernetes,
so
it
did
all
of
these
things
and
as
we
as
an
industry,
became
better
versed
at
what
git
ops
was,
we
started
to
want
to
build,
have
a
little
bit
more
control
over
exactly
what
that
git
ops
flow
looked
like
from
get
over
into
the
runtime
environments
and
those
types
of
things
and
so
flux.
E
E
What
we
did
in
flux,
too,
was
we
said
we
actually
want
to
be
able
to
control
these
get
up
flows,
so
we're
gonna,
break
flux,
one
into
various
components
and
then
what
the
cli
does
is
it
does
it
first
of
all,
gives
you
cli,
but
then
what
we're
also
doing
with
the
cli
is
some
of
these
commands,
like
the
flux,
bootstrap
and
so
on,
takes
those
components,
because,
as
soon
as
you
break
things
into
components,
it
gets
harder
like.
How
do
you
get
started.
C
E
So
that's
why
we
have
the
two
columns,
the
flux
cli,
as
well
as
the
components.
The
components
are,
a
set
of
components.
You
can
extend
that
set,
do
all
sorts
of
cool
things
and
then
the
flux
cli
is
was
part
of
what
we
have
in
flux
one
and
it
allows
you
to
kind
of
put
those
things
together
and
leverage
those
components
and
scott's
going
to
show
more
of
that
today.
C
D
D
If
you
only
use
those
features
so,
for
example,
if
you
do
flux,
one
read
only
mode
and
use
the
helm
operator,
you're
good
to
go
the
the
the
image
automation
at
that
date,
image,
automation,
controller,
the
image,
update,
automation,
controller
apis
are
an
alpha
only
and
all
the
others
have
reached
beta.
So
basically,
if
you're,
not
using
automated
image,
update
functionality
from
flux
one,
then
you
should
be
good
to
go.
You're.
D
Yeah
now
the
very
next,
the
very
next
date
is
when
we're
going
to
say
that
that
that
flux
one
is
has
been
superseded,
so
that
that,
on
that
date,
which
is
tbd,
we
don't
know
exactly
when
it's
going
to
be
because
it's
you
know
like
flux,
is
having
improvements
really
primarily
being
released
every
week.
But
this
actually
was
a
two-week
release
and
there
were
a
lot
of
improvements
so,
but
we're
still
very,
very
careful
with
versioning.
So
the
helm
operator
will
also
be
archived.
D
A
B
D
We
want.
We
don't
want
to
have
to
go
to.
You
know,
flux
three,
just
to
like
change,
some
really
obvious
and
important
click
cli
command.
So
the
thing
that
really
matters
the
most
in
the
superseded
period,
which
is
the
next
one
is
that
is
that
all
the
flux
api
apis
are
are
beta.
So
that
means
they're
production
ready.
D
A
D
D
Now
this
has
been
documented
by
the
way
this
isn't
new.
This
has
been
documented
all
over
the
in
different
places
and
has
been
mentioned
a
number
of
times,
but
it
was
never
really
put
in
one
spot.
So
that's
why
it's
here
and
again,
you
can
get
to
it
either
from
the
migration
section
under
migration
timetable
or
get
to
it
from
the
road
map,
and
it's
just
linked
right.
There
hope
that
helps
a
little
bit.
D
D
I
can
go
back
to
what
I
did
before
and
and
just
do
my
git
clone
and
get
in
there
oops
and
then
and
then
you
can
see
you
know
what
it
really
did.
Is
this
didn't
really
do
anything
super
special,
but
it
just
gave
me
a
a
you
know.
You
can
really
set
up
your
file
system.
However,
you
want,
but
the
most
important
thing
is:
when
you
do
the
flux
boot
it
opens,
it
opens
sorry.
I
want
to
give
it
one.
Second.
D
Flux
system
it
puts
you
know
it
gives
a
an
okay,
an
opinionated
structure
when
it
starts
at
least
where
you
tell
it
to
go,
and
this
is
just
represents
a
namespace
and
all
of
these
all
these
components
are
in
the
namespace.
So
if
you
want
to
take
a
look
at
there's,
a
single
customization
file
which,
by
the
way
is
not
necessary,
but
it
just
kind
of
shows
you
what
what
is
installed
that
these
other
two
resources.
D
D
This
is
the
the
the
flux
source,
controller,
git
type
source,
and
it
shows
where
you're
getting
the
information
from
so
that's
the
source.
There's
a
customization
object
that
the
customize
controller
uses
when
looking
at
that
source
it
and
it
uses
the
source
ref.
So
it
uses
the
git
repository
type
in
flux
system,
which
we
created.
D
E
Yeah,
which
are
the
things
that
you
saw
scrolling
by
when
you
did
the
flex
bootstrap
you
saw
these
things
getting
created.
Those
are
all
the
things
that
are
in
that
that
30ml
file
yeah,
but
there's
something
here
that
I
want
to
emphasize,
because
what
we've
done
here
is
we've
installed
flux,
but
we
are
get
opsing
that
installation.
E
E
Do
you
want
to
edit
the
get
ops
flow
that
brings
things
from
git
over
into
the
cluster?
All
you
need
to
do
is
change
that
in
git
and
commit
it,
and
we
will
sync
that
into
the
cluster.
So
what
we've
done
is
it's
got
the
auto
update
stuff.
So
now
all
auto
updates
are
just
commits
into
the
git
repository.
B
Yeah,
it's
kind
of
us
and
someone
says
someone
chatted.
Hillary
challenge,
chatted
get
ups
inception
almost
right,
so
yeah,
exactly
the
the
bootstrapping
process
basically
just
creates
the
manifest
applies
a
manifest
and
then
and
then
flux
uses
itself,
essentially
just
to
keep
those
in
sync
right.
So
if
you.
B
Make
changes
to
the
the
crds
for
whatever
reason
right
or,
like
you
said,
upgrades
you
just
make
a
you
know
you
you,
you
don't
have
to
do
that
outside
of
the
the
get
ups
framework.
I
guess
I'll
use
it
for
lack
of
a
better
term.
You
could
or
paradigm
right
you
don't
you
do
it
actually
within
the
own
paradigm
itself,.
E
E
D
D
I'm
using
this
to
show
as
well
what
we
just
showed
that
flux
that
source
for
this
excuse
me
that
that
custom
resource
for
the
that's
defined
by
the
source
controller
you
can
use
flux
commands
to
get
it.
You
can
also
just
use
cuddle
commands
to
get
these,
but
the
flux
commands
are
kind
of
nice
because
it
can.
It
can
help
you
with
discovery
a
bit
if
you're
not
exactly
sure
what
to
look
for
in
kubernetes.
Yet
it
will
tell
you
so
I'll.
Tell
you
that.
B
Yeah
go
ahead.
Well,
I
was
going
to
say
you
kind
of
have
to
hunt
around
for.
Like
you
know,
you
have
all
these
manifests
everywhere.
You
know
they
have
to
and
you
have
to
kind
of
piece
together
in
your
head.
You
know
labels
help
a
little
bit,
but
it's
nice
to
have
like
a
point
of
entry.
It's
like
just
give
me
everything
related
to
x,
right
yeah,.
E
D
E
D
D
So
what
I
was
going
to
show
you
real,
quick
again
the
tools
themselves
like
like
it's
not
really
that
critical
for
me
to
show
you
this,
but
I
just
wanted
to
give
people
a
sense
of
how
they
could
do
all
the
stuff
that
they
normally
kind
of
usually
have
scripts
to
wire
together
and
have
weights
and
checks,
and
so
on.
So
I
was
just
going
to
follow
a
similar
pattern.
Just
put
it
inside
the
make
a
name
space
for
this.
D
B
D
C
B
D
Know
why
I
I
thought,
maybe
I
screwed
up
the
tabbing.
Okay,
that's
good
yeah!
So
so
right,
so
it's
just
like
a
simple
namespace
object
right
and
the
reason
that
this
matters
is
that
you
know
helm
does
have
a
the
helm.
Helm
does
have
a
you
know,
it
helps
read,
didn't
initially
have
the
the
namespace
creation
functionality,
but
then
by
popular
demand
it
was
added
back
with
with
a
command.
This
is
just
using.
This
is
really
just
a
similar
thing.
D
D
D
D
D
D
Exactly-
and
this
is
what
it
looks
like
and
I
mean
truly,
the
components
are
quite
and
under
the
source
controller.
There's
the
git
repository
crd.
We
saw
the
home
repository
crd,
it's
fairly
clear,
of
how
how
to
I
mean
not
fairly.
It
is
very
clear
how
to
do
this,
but
you
don't
you
don't
need
to
you.
Can
you
can
just
use
these
comm
excuse
me
use
these
commands
to
help
you,
but
this
is
what
it
looks
like.
C
D
For
for
home
repositories,
you
probably
want
it
at
like
a
10
minute
interval
or
whatever
so
whatever
or
less.
You
know
once
every
hour.
What
it
really
just
depends
on
what
you
want
if
you're,
if
a
home
repository
updates
very
frequently,
you
might
want
to
bump
it
up.
If
you
don't
deploy
that
frequently,
maybe
it
doesn't
matter
to
you,
so
you
get
to
change
that,
but
luckily
you
can
do
that,
get
up
style
at
this
point
and
do
it
all
within
within
these
files.
E
And
while
you're
cutting
and
pasting
there,
I
want
to
clarify
a
little
bit
what's
going
on
with
that
export
command,
so
the
export
flag
says
go
ahead
and
stick
that
you
know
pipe
this
to
a
file,
so
he
he
you
know
had
it
sent
to
the
file.
If
you
don't
have
that
export
command,
what
it's
going
to
do
is
it's
going
to
take
care
of
sending
that
over
to
git,
for
you.
B
Yeah,
that's
a
I
was
actually.
I
was
thinking
about
that
that
automation
like
how
it
gets
back
to
it.
So
that's
good
to
know
that
I
can
just
create
it
from
the
cli,
but
since
it
has
the
github
token,
it
can
take
those
pieces
and
then
I
guess
retroactively.
I
don't
know
how
what
what
it
would
be,
but
it
would
apply.
You
know
what
that
the
state
of
the
cluster
to
the
get
repo.
So
now
they
match
exactly.
B
D
I
just
I
just
sort
of
started
from
scratch
too,
but
but
yeah.
So
this
is
the
home
release.
You
know,
helm
users
will
notice
this
if
you're,
not
a
home
user.
Maybe
just
just
realize
that
this
is
metadata
that
relates
to
how
that
tool
does
package
management
in
kubernetes
or
applies
different
app
packages
of
application
manifest
to
kubernetes?
So
I
don't
want
to
assume
the
audience
here,
but
well.
B
D
Yeah,
so
so
what
so,
so
it
really
depends
on
what
we're
talking
about
so
there's
you
can
have
intervals
for
these
various
things.
So,
when
you're
talking
about
the
helm,
excuse
me
the
the
the
source,
the
home
source
for
the
for
a
helm,
repo
that
for
that
the
source
controller
will
use
that
interval
to
check
if
there
were
any
updates
to
that
hell
repo.
D
So
it
will
essentially,
you
know,
get
the
excuse
me,
get
the
the
the
home
repositories
index.yaml
file
and
see
if
there
are
new
versions
for
any
of
the
any
of
the
metadata
for
the
different
charts
that
it
describes
and
the
the
the
helm
release
the
interval
this
is.
This
is
actually
the
helm
controller
now
going
back
over
here
oops.
D
D
Am
I
showing
the
home
release
object?
It's
this.
You
may
have
a
values
section
here
that
overrides
helm
values
you
may
have
values
from
for
a
config
map
from
a
config
map
or
a
secret
etc.
All
of
that
is
described
in
the
in
these.
This
is
the
home
repository
crd,
but
in
the
helm,
release
crd
definitions,
there's
a
lot
of
information
about
that.
D
It's
kind
of
maybe
a
bit
more
than
we
can
show
right
now,
if
we're
going
to
get
through
this
stuff,
but
but
that
that's
what
that
is
what
that
interval
represents.
So
you
may
make
different
changes
to
your
chart
for
deploying
like
people
do
in
other
and
get
ci
ops,
often
change
a
value
change,
something
else
change
a
dependency
and
but
rather
than
your
push
to
to
your
version
control
system.
D
D
E
C
B
D
If
you're
doing
and
if
you're
and
if
you're
adding
even
a
path
like
this,
please
do
get
diff
stage
just
to
see
what
you've
got
staged
anyway,
I
don't
need
to
do
a
get
psa
here,
but
but
yeah
thanks
for
neil
yeah
yeah.
So
so
now
I've
got
I've
got
this.
I've
got
local
stage
changes,
so
I'm
going
to
do
git
commit.
D
D
D
E
D
Yeah,
you
were
correct.
Thank
you,
so
reconciliation
in
progress-
that's
great!
So
I
can.
I
can.
If
I
want.
This
is
kind
of
cool.
So
now
I
can
do
if
you
want
to
see
like
oh
great
so
there's
now
a
traffic
helm
release.
I
can
do
it.
Okay
describe
just
like
you.
Would
all
right,
kubernetes,
administrators
or
or
operator,
or
human
operators
perk
your
ears
up.
So
it's
just
it's
just
this
okay
come
on!
D
C
D
D
Correct
yeah:
it's
not
using
help
templates
using
help,
so
I'm
actually
gonna.
I'm
gonna
get
out
of
this
because
I
think
you
know
what
it
looks
like
and
we
can
look
at
it
in
a
bit.
I
wanna
show
you
real,
quick
how
you
can
you
don't
actually
need
to
use
these
commands
to
do
this?
Do
we
still
have
a
moment?
We
don't
have
that
much
time.
D
D
D
D
Because
that's
where
people
should
be
looking
for
packages,
the
cncf
artifact
hub
so
go
to
cert
manager
check
out
the
installation,
okay,
so
I'm
actually
just
going
to
keep
it
sort
of
managed
for
now.
If
I
wanted
to,
I
could
call
it
just
actually.
Why
don't
I
do
it
I'll
keep
it
start
manager
for
now
for
fun.
If
we
had
more
jet
stack
stuff,
we
could
we
could
name
this
jet
stack.
We
could
really
do
it.
D
D
Okay,
so
hopefully
you
got
what
I
was
showing
you
is
that
these
are
just
the
the
files
that
I
showed
you
in
vi
before
and
all
I
was
doing
is
copying
pasting
and
I
changed
the
sorry
about
the
font
size
folks
and
then
I
changed
the
the
url
to
be
the
actual
url
of
where
the
jet
stack
helm.
Repo
is
for
cert
manager.
B
D
Exactly
it's
just
kind
of
an
easy
way
to
do
it.
You
can
also
just
go
to
the
these
these,
the
spec
inside
of
the
documentation
too,
and
go
to
the
home
controller
helm,
both
the
source
controller,
home
repository
crd
and
the
help
controller
home
release.
Crd,
that's
pretty
much
all
I
just
did
you
know
it?
You
don't
actually
have
to
use
these.
These
commands
at
all
they're,
just
they're
helper
commands,
so
so
anyways.
We
have
that
and-
and
I
just
got
the
right-
I
got
the
right
version.
D
D
For
the
condition,
I
do
not
know
why
it's
waiting
for
a
condition,
what
condition
it
would
be
waiting
for,
but
I
think
with
what
the
time
we
have
right
now,
I'm
not
going
to
look
at
that.
I
had
just
done
this
and
it's
fine.
It's
fun!
Trust
me!
It's
fine!
So
so
now
what
I'm
going
to
do
just
to
show
you
this
part
of
it
is
I'm
going
to
do
a
git,
add
flux.
Boot
serve
manager.
D
D
D
But
if
I
do
a
you
know
a
you
know,
I
get
law,
get
log
n1
and
get
that
get
that
sha
and
then
just
do
a
flux,
get
source
get
and
you
you
see
where
we're
at
it's
not
correct,
because
it's
on
an
interval
and
so
because
you
know
in
order
to
instead
of
just
talking
for
a
few
a
few
minutes.
While
I
roll
this
reconciles,
I'm
going
to
trigger
that.
D
So
it's
as
if
the
time
period
of
all
had
elapsed,
I'm
going
to
do
a
flux,
reconcile
source
for
the
name
of
my
source,
and
now
it
should
it
should
match,
and
it
does
now.
Let's
do
a
a
cuddle
saying
that
just
oops
get
name
spaces
looks
like
cert
manager's
there
just
for
fun,
I'm
gonna
do
a
helm
and
sir
manager
installed
quite
fast.
I'm
not
really
sure
what
I
did
with
traffic.
D
You
know
what
I
mean
an
ingress
statement
to
the
to
the
chart
for
pod
info
and
then
just
like
port
forward
traffic,
because
I'm
unkind
locally
and
you
can
see
it
running,
but
I
don't
think
I
need
to
show
you
all
that
I'm
not
really
trying
to
demo
what
ingress
looks
like.
I
hope
this
gave
you
a
sense
of
how
how
you
can
really
interact
with
or
basically
how
you
how,
how
how
the
flex
components
work
in
general,
how
you
can
set
up
your
repo.
It
can
be
setable
differently.
D
D
D
D
Multiple
different
names,
yeah,
it's
so
yeah,
one
flux,
controller
or
one
source
control.
Ultimately,
one
set
of
flux
components
is
the
optimal
way.
You
can
scale
it,
of
course,
but-
and
it
really
just
follows,
excuse
me
sorry
it
really.
It
really
is
built
on
top
of.
What's
what
kubernetes
is
using
already
for
controller
runtime?
It's
like
sid
controller
runtime,.
E
A
E
If
you
will,
okay,
lux
one
was:
was
single
tenant.
If
you
will,
it
depends
on
how
you,
you
know,
define
tenant,
but
what
you
did
with
flux.
One
is
anytime,
you
had
a
different
repository.
You
needed
to
have
a
new
flux
controller.
So
ever
there
was
a
one-to-one
mapping
between
those,
and
so
this
is
a
common
question
that
we
get,
which
is
hey
the
more
workloads,
the
more
different
repositories.
I
have
the
more
flux
controllers.
Now
the
flux
controller
is
really
lightweight,
so
it
actually
wasn't
a
big
resource
hog
or
anything
like
that.
E
But
what's
happening
now
with
flux
too.
Is
that
it's
not
that
there's
one
controller
anymore,
remember:
there's
these
we've
broken
down
what
we
used
to
be
in
one
controller
into
a
set
of
controllers,
but
you
don't
need
a
separate
source
controller
for
each
one
of
these.
You
have
one
source
controller,
you're
going
to
have
separate
source
objects
per
repository,
so
crs
you'll
have
separate
source
crs
source
get
you
know,
git
repository
crs
or
helm
repository
crs.
C
A
C
D
Good
yeah
and
to
be
clear,
you
may
have
one
source
one
defined
source
per
repository
or
per
source
type,
even
if
it's
not
a
git
repository,
it's
one
of
the
other
types,
but
you
can
have
multiple
customized
objects
that
then
are
responsible
for
applying
manifests
within
a
specific
path.
That's
specified!
D
A
D
Got
it
yeah?
So
so,
if
you
maybe,
I
should
share
my
screen
again.
Actually-
maybe
I
don't
have
to,
but
if
you
remember,
if
you
want
me
to,
I
will,
but
if
you
remember
the
because
I
pinned
a
specific
version
of
that
chart,
even
if
new
chart
versions
are
pushed
to
that
home
repository
it
won't,
it
won't
do
anything.
D
Char
charts
are
intended,
helm,
charts
are
supposed
to
be
item
potent,
and
so,
if
you
make
a
change
to
your
chart
and
don't
bump
the
version,
tough
luck,
you
know
you
really
should
because
otherwise
you're
really
screwing
your
own
you're.
Excuse
me:
you
are
really
not
following
best
practices
at
that
point
or
whoever
would
be
doing
this
right
would
would
have
been,
would
be
making
mistake
at
that
point
and
not
following
best
practices,
so
definitely
bump
your
chart
versions
when
you
want
those
your
changes
to
be
made
to
each
chart.
D
That's
correct
that
then,
then
it
would
do
that.
So
if
right,
so,
then,
if
you,
if
you
if
the
source
controller,
was
on
an
interval
to
check
every
half
hour
or
10
minutes
or
whatever
one
minute,
whatever
you
want,
and
it
sees
a
new
a
new
version
that
matches
december
range
rules
that
you've
set
out,
then
it
would
say:
okay,
cool,
I'm
gonna
go
I'm
going
to
go
grab
that
we.
D
D
Excuse
me,
that's
being
moved
from
worked
on
from
alpha,
hopefully
getting
to
beta
and
not
too
distant
future,
very
soon
for
other
aspects
of
flux
which
allow
you
to
set
different
policies
and
then,
and
then
the
image
update,
automator
will
write
back
to
your
get
and
actually
pin
versions
based
on
based
on
annotations
that
you
want
to
set.
You
can
also
do
that.
That
kind
of
thing
like
this
without
using
image,
update
automation,
controller
using
ci.
You
know
you
can
you
can.
E
A
D
Okay,
yeah,
so
it's
really
more
of
a
con.
I'm
just
like
mentioning
this
in
the
same
breath,
because
the
concept
is
similar,
you
would
you
yeah
if
it's
very
imperative
that
you
have
a
specific,
a
specific
version
which
it
often
is,
then
you
want
to
you
want
to
do
whatever
use,
whatever
tools
are
available
to
make
sure
that
you
are
pinned,
that's
it.
You
know.
B
D
A
B
D
B
Nice,
so
just
real,
quick,
like
we
mentioned
last
time,
we
are
putting
on
a
kubecon
day,
zero
event.
The
get
ups
working
group
is
putting
on
get
ops.
Con
we
are
cfps,
are
still
still
open
right,
I'll
put
it
in
the
chat,
I'll
paste
it
in
here
for
all
those
I
was
trying
to
grab
it
yeah
I
made
a
bitly
for
it.
B
So
it's
easy
to
remember
I
put
in
the
chat
there,
please,
if
you
have
any
ideas,
if
you
want
to
share
some
use
cases
that
you
guys
had
or
done
we're
interested
in
users
and
end
user
stories
right.
Anything
you
want
to
share
with
the
broader
group
of
you
know:
cfp
still
open
until
next
week,
next
friday
closes
and
we'll
be,
you
know
contacting
those
that
are
that
are
selected,
so
yeah.
A
C
C
C
C
B
D
It's
probably
worth
noting
that
there
are
other
events.
We
don't
probably
have
a
lot
of
time
to
get
into.
I
think
we
mentioned
them
the
last
round,
but
but
there
there's
a
there's
get
ops
days.
There's
there's
the
get
up
summit
at
cdcon,
there's
a
there
are.
This
is
the
year
of
a
lot
of
a
lot
of,
hopefully
not
the
only
year
but
a
year
where
a
lot
of
this
is
happening
so
get
your
cfps
everywhere,
not
just
to
this
yeah.
B
D
B
Definitely
definitely
yeah
the
it's
a
community
and
we
even
cross,
like
you
say,
cross-pollinate
communities
as
well,
so
yeah
come
share
wherever
you
can.
This
is
the
year
of
get
ups.
I
guess
right
we
can
say,
since
all
these
are
popping
up
so
yeah
the
the
year
of
the
linux
laptop,
wasn't
here,
but
maybe
the
year
the
getups
is
so.