►
From YouTube: Keynote: CNCF Project Update: Flux - Stefan Prodan, Developer Experience Engineer, Weaveworks
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.
Keynote: CNCF Project Update: Flux - Stefan Prodan, Developer Experience Engineer, Weaveworks
A
A
A
A
We
soon
realized
that
these
operations
can
be
made
in
a
collaborative
manner
by
using
git
as
the
desired
state
of
our
production
system.
So
we
needed
a
tool
that
would
watch
git
and
reconcile
the
cluster
state
once
changes
are
approved
and
merged
in
the
repository.
This
is
how
the
github's
ideal
was
born.
A
A
The
people
that
are
maintaining
flux
is
no
longer
a
weworks
only
project
other
companies
have
joined,
and
I
want
to
thank
them
all
for
for
stepping
up
and
help
with
with
flux,
with
with
more
organizations
adopting
githubs
and
cloud
native
technologies
and
with
kubernetes
evolving.
So
fast,
we've
hit
the
limits
of
flux,
initial
design.
A
A
We
want
to
provide
the
complete,
continuous
delivery
platform
on
top
of
kubernetes
with
support
for
common
practices,
and
you
know
the
popular
tools
that
are
in
this
field,
such
as
customize
helm.
The
new
cluster
api
also
offer
observability
inside
your
your
delivery
pipelines
and
we'll
see
how
how
we,
how
we
got
to
that
here
is
a
is
a
diagram
that
shows
you
how
flux
can
now
manage
multiple
clusters.
You
can
look
at
different
sources
and
so
on.
A
Okay,
let's
talk
about
the
github
toolkit,
so
is
the
toolkit.
The
toolkit
is
a
collection
of
go
libraries,
apis
and
kubernetes
controllers.
All
these
put
together
can
help
you
build
declarative,
continuous
delivery
pipelines
and
the
toolkit
is
kubernetes
native.
It's
built
with
control,
runtime
libraries,
it
can
be
configured
using
kubernetes
custom
resources
is
composable.
A
A
We
try
to
bridge
the
gap
between
source
control,
access
and
kubernetes
access
in
a
way
that
you
can
validate
the
authenticity
of
a
person
that
creates
a
creates,
a
commit.
You
can
verify
that
that
person
has
the
right
access
to
to
modify
something
on
your
production
cluster
and
then
the
toolkit
can
run
those
changes.
A
Those
operations
under
by
impersonating
a
kubernetes
account
which
is
restricted
according
to
how
the
cluster
I
mean
define
that
particular
term
also
the
toolkit
is,
is
event
driven,
so
you
can
subscribe
to
external
events
like
a
git,
push
or
a
hand,
chart
upload
or
a
docker
push
and
define
how
these
events
should
change.
The
cluster
state.
A
Also,
the
toolkit
has
a
component
for
you
to
define
alerts.
So
events,
what
happens
inside
the
cluster
can
be
pushed
outside
the
cluster
using
using
the
alerting
api.
With
with
this
api,
you
can
push
errors
to
slack
microsoft
teams,
discord
even
right
back
to
let's
say
a
github
commit
status
or
gitlab.
A
We,
you
can
define
your
your
cluster
state
in
in
any
kind
of
s3,
compatible
storage.
For
example,
mania.
We
have
built-in
sequence
management
we
integrate
with
mozilla
swaps
and
cloud
kms
flags
version.
2
comes
with
with
multi-tenancy
features
where
it
impersonates
users,
when
it
tries
to
reconcile
something.
A
You
can
also
run
flux
on
a
central
cluster
and
control
all
your
cluster
fleets,
all
the
clusters
that
are
making
your
fit
without
installing
flux
on
on
each
cluster
and,
of
course,
observability.
We
we
issue
events
for
everything,
that's
happening.
We
have
metrics
alerts
and
we
also
offer
graphana
dashboards
for
you
to
see
what's
happening
with
your
continuous
delivery
pipelines.
A
We've
developed
a
new
flux,
cli
and
also
telephone
provider,
so
you
can
have
a
github's
first
approach
to
bootstrap
in
clusters.
The
flux
cli
comes
with
a
with
a
single
command.
Where
and
with
that
command
you
can
create
your
git
repos.
You
can
install
flux
on
the
cluster
and
and
pair
the
two
with
deployment
keys,
team
access
and
so
on,
and
it
works
with
a
variety
of
kit
providers
over
ssh
directly
with
with
github
api
or
gitlab
api,
and
so
on.
A
Another
update
is
that
flagger
has
joined
the
flux
family.
What
what
flagger
does?
Is
it
decouples
the
the
deployment
of
an
application
from
the
release
process?
So
flux
does
the
deployment
while
flagger
can
do
the
the
release
through
canary
with
progressive
traffic,
shifting
a
b
testing
blue,
green
blue,
green
with
mirroring
and
so
on
and
flagger
works
with
a
variety
of
service,
mesh
providers
and
ingress
controllers?
A
And
finally,
I'm
going
to
ask
you
to
join
the
flux
community.
We
have.
We
have
a
slack
channel
on
cncf
and
we
use
github
discussions
for
for
everything
around
flux
version
to
what
features
are
going
to
be
shipped
and
so
on,
and
I've
listed
here.
Some
hot
topics
like
we
are
now
working
on
flux,
web
user
interface.