►
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Helm Users! What Flux 2 Can Do For You - Scott Rigby & Kingdon Barrett, Weaveworks
Helm, the Package manager for Kubernetes. Flux, the GitOps continuous delivery solution for Kubernetes. Both can be used independently, but are more powerful together. Scott Rigby, Helm and Flux maintainer — and Kingdon Barrett, OSS engineer — will share the benefits of Helm and GitOps for developers, with live demos showcasing the extra awesomeness of Flux v2 and Helm together. This talk is for Helm users who have either never used Flux, or Flux v1 users looking forward to new features in Flux v2.
A
A
So
yeah,
first
of
all
welcome
the
assumption
for
people
coming
to
or
watching
this
recording
and
coming
to
the
q.
A
are
that
you
have
some
familiarity
with
helm.
There
is
no
assumption
about
familiarity
with
flux
yet,
but
we
can
guess
that
some
people
have
there's
a
variety
or
there's
a
range
of
experience,
so
some
some
of
you
may
have
tried
the
current
version
of
fox.
Some
of
you
may
have
tried
the
older
version
of
books.
A
So
I
think
flux's
hub
controller
is
the
best
way
to
do
hell
according
to
get
up's
principles
and
our
team
and
and
me
in
particular,
I'm
dedicated
to
doing
whatever
I
can
to
help
make
sure
that
you
feel
that
way
too.
So,
please,
in
the
q,
a
and
and
outside
of
that
please
keep
in
touch
about
how
you
feel
about
it
and
what
and
how
it
works
for
you.
A
So,
at
least
as
of
film
three,
I
almost
designed
with
a
client
and
an
sdk
on
which
the
client
was
built,
but
no
running
software
agents
of
any
kind
and
this
architecture
intended
anything
outside
of
the
client
scope
to
be
addressed
by
other
tools
in
the
wider
ecosystem,
which
could
then
make
use
of
helm's
sdk,
just
as
as
the
helm
client
does.
So.
Why
am
I
even
mentioning
that
it's
because
flux's
held
controller
built
on
kubernetes
controller
runtime?
A
It
is
it's
an
example
of
a
mature
software
agent
that
uses
helm's
sdk
to
full
effect.
Every
feature,
at
least
that
is
non-experimental,
is
available
of
helm
is
available
in
the
helm
controller
using
purely
using
sdk.
However,
there
are
some
things
that
are
added
to
this.
Otherwise,
why
would
you
bother
using
it?
A
A
Let
you
declare
what
you
want:
the
helm,
sdk,
what
you
want
and
the
help
and
the
hell
mesty
pape
will
do
that
for
you
automatically
and
that's
the
main
benefit
that
it
offers.
But
there
are
a
couple
of
additional
benefits
that
are
worth
noting.
I
won't
get
into
every
detail,
but
just
just
at
the
high
level
before
as
we're
diving
in
managing
and
structuring
multiple
environments
outside
of
the
scope
of
the
health
climate,
you
can
do
that
with
health
controller.
Very
well
also,
a
control
loop
with
configurable
retry
logic.
A
A
So
that
includes
trying
to
reconcile
those
two
things:
notifications
for
you
when
that's
not
happening
the
way
you
intended
it
to
happen
and
unified
logging
as
well
and
and
other
other
really
valuable
things
that
come
with
flux's
version
of
get
out.
So
I
hope
that
gives
you
some
sort
of
a
sense
of
of
why,
or
at
least
what
and
some
of
the
why
so,
let's
go
ahead
and
and
show
you
something
so
just
to
introduce
what
king's
gonna
say
is
that
I
here's
here's
the
truth
with
it.
A
B
B
B
So
values.yaml
is
not
a
first
class
object.
Maybe
it
is
if
you
apply
the
schema.json,
but
as
as
you
work
with
alan
releases,
you
find
that
helm
enables
you
to
install
a
lot
more
things.
What
we're
going
to
find
on
our
cluster
is
that
we
actually
need
more
than
just
a
blog
to
have
a
blog.
Our
blog
uses,
persistent
volumes,
our
blog
uses
wordpress
there
could
be
vulnerabilities
in
wordpress
and
and
we're
not
just
going
to
use
this
cluster.
For
one
thing
we
want
other
things
on
the
cluster.
B
B
B
When,
when
we
get
there,
you
might
see
some
of
the
problems
that
haven't
been
resolved
still,
if
we're
lucky
we'll
get
a
chance
to
debug
something
and
we're
gonna
install
some
other
things.
Alongside
of
flux,
caverno,
webhook,
wordpress
itself,
there's
lots
more.
We
wanted
to
show
you
jenkins
way
to
get
a
terminal
in
a
web.
Browser
linker
d
is
a
service
mesh.
B
B
B
Okay,
so
I
apologize
in
advance
for
some
aliases
that
you
will
see
me
use
throughout
this
if
you're
not
familiar,
who
is
not
familiar
with
k
as
the
others
for
cube
control.
Probably
most
of
you
ks
there's
a
namespace
cube
system
if
you're
not
familiar
with
it,
where
lots
of
things
are
deployed
by
default
on
most
clusters,
so
we
can
see
what
those
things
are.
B
B
B
B
B
A
A
It's
important
to
note
for
the
moment
that
the
that
flux's,
customized
controller
is
what
is
used
not
only
for
people
who
are
doing
more
advanced
customization
overlay
things
and
other
and
other
other
benefits
that
customize
can
can
give
people
if
you
choose
to
use
that,
but
also
the
customization
controller
is
what's
used
to
ingest
plain
yaml
and
reconcile
that
into
your
cluster
as
well.
So
in
this
case
right
kingdom
we're
using
the
the
customized
controller
to
to
actually
bring
in
the
manifests
for
helm.
B
Hopefully,
if
everything
worked,
okay,
great,
we
got
a
flagger
customization
customization
for
secrets,
we'll
get
to
that
in
a
little
bit
and,
moreover,
we
have
flux,
get
helm
releases,
some
helm
releases
that
have
been
installed
or
are
being
installed,
and
so
this
is
one
of
the
points
of
the
demo
here
is
to
show
you
can
install
a
bunch
of
stuff
with
just
a
couple
of
keystrokes.
So
granted
that's
a
little
bit
of
an
exaggeration
here.
B
B
B
B
We
tell
if
we
wanted
to
be
a
personal
repo
as
opposed
to
a
repo
in
some
arc
that
we
belong
to
the
owner.
Is
me
the
repository
is
for
this
demo
and
we're
installing
some
extra
components
we
we
haven't
talked
about
these
we'll
explain
what
these
are
for
in
a
moment.
Image,
automation,
controller
and
image.
Reflector
controller
are
the
extras,
so
we're
going
to
install
caverno.
B
B
I've
expanded
some
things
in
the
caverno
namespace
and
for
the
most
part,
these
were
meant
to
be
individually,
carbon
copies
of
each
other.
But
what
you
find,
as
you
try
to
prepare
a
demo
like
this
is
some
tools
are
not
really
meant
to
be
installed
with
film
and
and
what
what
flex
shows
is
that
you
can
still
use
those
things.
B
B
B
Customization.Yaml,
so
we've
excluded
it
by
referring
to
all
other
files.
Here
and-
and
you
can
see
what
I'm
talking
about-
we
want
to
install
the
crds
separately
from
the
helm
release,
because
if
we
don't
it
will
cause
problems
when
we
do
upgrades
and
this
this
is
not
exactly
the
best
way
to
do
it
and
in
the
toolkit
guide,
they're,
stronger
demonstrations,
but
anyway,
so
caverno,
helm,
release
we'll
see
that
file.
B
Okay,
so
this
this
is
another
flux,
custom
resource
we're
defining
a
helm
release
which,
if
you've
used
helm,
this
is
equivalent
roughly
equivalent
in
get
terms
to
an
actual
helm
release.
It's
the
declarative
form
of
a
helm
release
says.
I
would
like
this
helm
release
to
be
installed
in
the
cluster.
A
B
A
B
Right
now,
yeah,
the
default
interval
here
is
one
minute
for
the
git
repository
and
10
minutes
for
the
customization
itself.
So
if
we
wait
a
little
while
this
will
take
care
of
itself,
but
we're
doing
demo
and
we'd
like
this
to
proceed
rapidly,
so
we're
going
to
synchronize
it
and
we're
going
to
use
this
with
source
flag
to
reach
through
this
is
probably
unnecessary
at
this
point
because
it's
already
been
longer
than
one
minute,
so
the
helm,
the
git
source,
is
already
synchronized
or
it'll.
Synchronize
now
we'll
see
status,
output.
B
That
indicates
what
revision
is
reached
and
then
it's
going
to
reconcile
our
customization,
which
should
in
turn
reconcile
our
helm
release.
Oh
it
failed
well.
Here
we
go
what
went
wrong,
let's
find
out
validation,
error,
unknown
field
release,
name
and
customization
spec.
Well,
that's
because
that's
not
a
field
in
customization!
Stick!
What
were
you
thinking?
This
wasn't.
B
A
B
B
B
A
A
B
B
B
B
A
A
It's
something
that
you
can
also
do
on
your
own
flux,
your
own
flux
system,
if
you,
if
you
want
to
issue
a
reconciliation
faster
than
the
normal
than
the
normal
excuse,
me
interval
that
you've
configured
right.
One
common
use
case
is
you
want
to
make
that
happen.
Every
time
you
push
to
get
or
or
your
version
control,
whatever
right,
your
buckets
or
whatever
they
are.
You
can
do
that
with
a
web.
That's
that's
a
really
common
feature
for
or
for
get
workflows.
A
I
just
want
to
be
really
clear,
though,
that
that
in
itself
is
not
while
it's
acceptable
to
add,
as
if
to
extend
what
you're
doing
with
githubs.
That
in
itself
is
not
get
ups,
that
is
see,
get
ci,
ops,
the
distinguishing
feature
of
githubs,
not
just
for
flux,
but
for
other
tools
in
the
in
the
github
ecosystem.
The
wider
githubs
ecosystem
is
that
you've
got
automatic
reconciliation
in
a
closed
loop
based
on
your
own
configured
interval
and
rules.
A
B
B
It
has
also
cut
up,
I'm
not
sure
if
that's
because
we
got
lucky
or
because
our
web
hook
is
working,
it
is
called
a
receiver.
You
can
check
on
the
status
here.
It
looks
like
it
should
be
working,
because
this
hook
is
the
same
as
the
last
one
I
saw.
So
I
think
that's
a
hash
based
on
a
configured
password.
B
B
B
B
Blog
well,
you
can
do
all
kinds
of
things
and
that's
what
we're
using
jenkins
for
is
all
kinds
of
things.
Lord
only
knows
what
we're
using
this,
for
maybe
you
know
if
you're
in
the
audience,
everyone
knows
jenkins,
it's
a
it's,
a
big
mysterious,
boondoggle
who's
using
it
for
what
we
don't
know
everyone,
nobody
all.
At
the
same
time,
we
have
jenkins
installed
here
too
we're
gonna
skip
that
for
expedience,
because
we're
almost
out
of
time
actually
the
tardis
is
really
not
keeping
up,
but
we
have
another
application
installed
here.
A
B
On
linker
d,
all
right
this-
this
is
in
the
list,
because
this
is
a
prerequisite
for
flagger
the
way
that
we
have
configured
it
don't
really
have
much
time
to
talk
about
linker
d,
but
linker
d
is
a
service
mesh
that
lets
you
use
technologies
like
flagger
that
depend
on
request,
inspection
and
other
interesting
behaviors
that
you
can
find.
I
recommend
you
check
this
stuff
out
heavily.
We
will
not,
unfortunately,
have
enough
time
to
demonstrate
flagger
right
now,.
B
There
are
lots
of
demos
in
the
flex
of
the
york.
We
hope
that
you
will
check
them
out,
for
example,
the
customized
helm
example,
which
gives
more
detail
about
how
to
use
customize
and
helm
together,
including
how
to
avoid
duplication
of
resources.
In
your
manifest
repository
when
you
are
working
with
multiple
environments,
and
you
want
the
same
software
to
be
installed
in
multiple
environments,
perhaps
with
different
configurations.
B
B
A
B
A
B
B
B
B
B
Cert
manager
is
installed.
We
haven't
done
anything
with
it.
Multi-Tenancy
is
a
very
complicated
area.
There
are
many
tools
out
there.
We
recommend
you
take
a
look
at
kiosk
for
some
interesting
perspective
on
how
to
manage
multi-tenancy
another
subject
we
had
to
skip
over,
but
all
of
this
we
were
able
to
configure
using
helm
releases
in
flux
in
less
than
30
minutes.