►
From YouTube: A Tall Tale of GitOps - Prasanjit Singh, Starzplay
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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.
A Tall Tale of GitOps - Prasanjit Singh, Starzplay
In 1962, in his book “Profiles of the Future: An Inquiry into the Limits of the Possible”, science fiction writer Arthur C. Clarke formulated his famous Three Laws, of which the third law is the best-known and most widely cited: “Any sufficiently advanced technology is indistinguishable from magic”. This quote is the seed of the session "A Tall Tale of GitOps!" It is a 'Tall Tale' because it is nothing short of that! What GitOps can do is larger-than-life and the session will see it unfold.
We will also share a repository of "Awesome GitOps" resources that you can use for hands-on demonstration about how one can write code, build it, create infrastructure, deploy the application and monitor the application all from a git version control push! The talk is focussed at beginners and will introduce the concept of GitOps and explain the building blocks of the architecture with a fictional story analogy.
A
A
Now,
before
we
begin
a
little
bit
about
me,
my
name
is
prasanjit
singh
and
I
am
the
cloud
and
devops
director
at
stars
play
the
wave.
We
are
a
large-scale
media
streaming
service
in
the
middle
east
and
north
africa
region,
and
I
am
also
a
subject
matter
expert
and
trainer
at
coursera.
I'm
an
aws
community
builder,
cncf
speaker
and
speak
widely
at
different
meetups,
and
I
also
like
to
teach
a
lot
so
I
have
recently
opened
up
a
youtube
channel
called
bin
pipe.
You
can
subscribe
to
that
as
well.
A
A
Well,
once
upon
a
time
there
was
a
little
honeybee,
his
name
was
git
b.
He
had
lost
his
parents
and
lived
with
his
grandma
lilly
b.
Now
lilly
b,
the
grandma
owned,
the
largest
pastry
shop
in
town
and
the
shop
was
famous
for
honey,
cakes,
honey
waffles
and
a
special
rainbow
donut
called
unicorn
poop.
A
A
Also,
since
there
were
other
worker
bees
in
the
factory,
all
of
them
needed
to
have
access
to
the
batter
and
other
ingredients.
So
tagging
and
organizing
the
raw
materials
helped
kid
bee
to
allow
his
team
members
to
work
in
unition
on
the
same
recipe
so
that
way,
granny
b's
problems
were
getting
solved.
She
has
this
problem
of
not
being
able
to
manufacture
a
large
amount
of
cakes
because
of
because
she
was
getting
old
and
her
workers
didn't
couldn't
work
well
without
direction
and
organization.
A
So
those
were
her
problems
and
git.
We
solved
this
problem
by
tagging,
the
different
ingredients
and
tagging
the
different
bowels
and
separating
mixing
bowels
with
different
flavors
of
the
batter
that
we
are
going
to
use
to
bake
the
cakes,
get
b
being
smart,
organize
the
ingredients
that
made
the
batter
in
separate,
mixing
bowls
and
tagged
them.
A
If
he
needed
more
of
the
batter
of
a
particular
flavor,
he
could
use
same
amount
of
ingredients
and
literally
clone
his
bat
about
also,
since
there
were
other
worker
bees
in
the
factory,
all
of
them
needed
to
have
access
to
the
batter
and
other
ingredients.
Of
course,
so
tagging
and
organizing
the
raw
materials
helped
get
b,
allow
his
team
members
to
work
in
unition
on
the
same
recipe,
and
even
if
some
of
them
were
working
on
different
recipes,
there
was
no
risk
of
ingredients
getting
mixed
up,
so
it
improved
their
productivity.
A
They
could
have
multiple
different
cakes
rolled
out
and
they
became
more
organized
in
the
way
they
were
making
or
baking
their
cakes.
Now,
if
we
want
to
correlate
get
b's
tacking
system
to
software
development,
we
can
see
that
git
is
a
version.
Control
system
used
for
tracking
changes
in
computer
files.
It
is
generally
used
for
source
code
management
and
software
development.
A
It
is
used
for
tracking
changes
in
the
source
code,
and
it
also
allows
multiple
developers
to
work
together
similar
to
how
multiple
worker
bees
were
able
to
bake
cakes,
and
it
also
supports
non-linear
development
through
its
thousands
of
parallel
branches.
So
using
git
we
can
develop
multiple
features,
have
a
multi
developer
team,
all
working
together
towards
the
same
end
product,
but
each
one
working
independently
on
a
separate
feature.
So
all
those
could
be
enabled.
So
that
is
what
git
is
all
about.
A
A
Similarly,
in
software
development
we
can
use
git
and
use
and
take
advantage
of
its
various
features
like
it
allows
you
to
track
history
of
whatever
code.
You
are
writing
and
that
opens
up
the
possibility
of
making
mistakes
and
then
going
back
and
correcting
them
and,
of
course,
it's
free
and
open
source.
It
supports
non-linear
development
and
creates
backups.
A
Now
the
process
of
baking
cakes
wasn't
an
easy
task.
It
involved
a
series
of
steps
from
mixing
the
ingredients,
whipping
the
batter,
adding
eggs
and
baking
it
in
the
oven
and
finally
topping
it
with
the
cream.
Now
get
b
felt
these
tasks
being
repetitive,
can
be
defined
as
a
workflow,
so
he
wrote
down
the
rules
and
the
sequence
of
tasks
to
follow
until
the
cake
is
baked,
so
he
had
his
series
of
sequences
perfectly
defined
and
he
knew
what
to
do
and
what
would
come
after
the
other.
A
A
They
would
not
allow
you
to
make
an
end
to
end-to-end
deployment
or
automation
of
your
infrastructure
as
code,
so
using
githubs
joins
all
these
dots
and
allows
you
to
deploy
everything
automatically,
just
as
kit
b
worked
out
how
he
could
automate
his
steps
of
baking
the
cake
by
putting
down
all
the
steps
that
occur
and
creating
a
documentation
out
of
it.
Similarly,
at
its
core,
gitops
is
code
based
infrastructure
and
operational
procedures
that
rely
on
gate
as
a
source
control
system.
A
More
simply,
it
is
the
practice
of
git
pull
request
to
verify
and
automatically
deploy
system
infrastructure
modifications
in
addition
to
git
as
a
key
devops
mechanism,
git
ops
is
used
to
describe
tools
that
augment
get
default.
Functionalities
githubs
ensures
that
there
is
a
systems.
Cloud
infrastructure
is
immediately
reproducible
based
on
the
state
of
the
gate,
repository
of
course,
and
the
pull
request
modify
the
state
of
the
gate,
repository
and
once
approved
and
merged.
The
pull
request
will
automatically
reconfigure
and
sync
the
live
infrastructure
to
the
state
of
the
repository.
This
live
syncing
pull
request.
A
Workflow
is
the
core
essence
of
get
ops.
Now
going
back
to
our
story
one
fine
morning,
the
queen
bee
sent
an
order
for
a
gigantic
layered
honey
cake
and
scores
of
unicorn
poop
donuts
granny
b,
who
was
used
to
manually
baking
and
everything
declared
it
was
impossible
to
get
the
order
completed
because
the
timeline
was
very
short.
Queen
bee
wanted
the
order
to
be
delivered
by
evening,
and
that
is
when
git
be
our
hero
jumped
in
again
he
buzzed
around
in
enthusiasm
and
said
friends.
A
I
got
another
idea
yet
another
idea,
yes
I'll
automate
everything
and
he
set
out
to
build
a
chain
reaction,
machine
wow.
What
was
that
the
machine
was
actually
dictated
by
logic
and
physics
and
worked
on
the
principles
of
cause
and
effect
and
wash
from
mixing
the
ingredients
to
whipping
the
batter
to
molding
the
cake,
baking
cooling
it
over
icing
and
garnishing.
Everything
was
a
part
of
the
chain
reaction
machine
and,
if
you
folks
are
wondering
what
would
that
chain
reaction
machine
look
like
it
is
something
like
this
a
cause
and
effect
machine.
A
A
Now
gitops
uses
git
repository
as
a
single
source
of
truth
for
infrastructure
definitions.
Now,
using
these
concepts,
we
can
build
our
own
cause
and
effect
machine.
Just
like
it
be.
A
git
repository
is
a
dot
git
folder
in
a
project
that
tracks
all
the
changes
made
to
the
files
in
the
project
over
time
now,
infrastructure,
as
code
is
the
practice
of
keeping
all
infrastructure
configurations
as
code,
the
actual
desired
state
may
or
may
not
be
stored.
A
As
code
example
say,
if
you
are
using
kubernetes,
the
number
of
replicas
boards
and
all
those
information
may
not
be
stored
as
code,
and
then
you
use
the
mechanism
of
merge
requests
and
gitops
uses.
Merge
requests
as
the
change
mechanism
for
all
the
infrastructure,
the
mr
is
where
teams
can
collaborate
via
reviews
and
comments
and
formal
approvals
take
place.
A
Now,
when
new
code
is
merged,
the
ci
cd
pipeline
enacts
the
change
in
the
environment
and
any
configuration
drift,
such
as
manual
changes
or
errors,
is
overwritten
by
github's
automation,
so
the
environment
converges
on
the
desired
state
defined
in
gate.
Any
configuration
drift,
such
as
manual
changes
or
errors,
is
overwritten
by
gitops
automation,
so
the
environment
converges
on
desired
state
defined
in
the
gate
repository
now.
This
approach
has
a
lot
of
benefits.
A
The
git
ops
framework
makes
infrastructure
automation
possible
and,
while
automation
has
a
value
in
itself,
it
is
not
the
only
advantage
of
git
ops
organizations
that
adopt
githubs
enjoy
other
benefits
that
can
make
a
long-term
impact,
since
every
change
will
go
through
the
same
change,
merge
request,
review
approval
process.
Senior
engineers
can
focus
on
other
areas
beyond
critical
infrastructure
management.
A
Now
improved
access
control
is
there.
There
is
no
need
to
give
credentials
to
infrastructure
components,
so
they
will
just
have
to
work
on
their
git
repositories
and
all
the
other
key
based
authentications
are
separately
configured,
so
you
don't
have
to
individually
share
the
configuration,
so
there
is
less
grace
less
risk.
A
All
the
changes
attract
through
merge
requests,
so
you
can
keep
on
keep
an
eye
on
the
changes,
then,
because
this
is
all
automated,
it
leads
to
a
faster
time
to
market,
so
execution
via
code
is
faster
than
manual
point
and
click
test
cases
are
automated
and
repeatable,
so
stable
environments
can
be
delivered
rapidly
with
githubs
and
auditing
is
simplified.
You
have
all
the
records
in
place
and
with
githubs.
A
All
changes
to
environments
are
stored
in
the
git
log,
making
audits
simple,
as
I
said,
and
automation
of
the
infrastructure,
definition
and
testing
eliminates
all
the
manual
tasks
that
were
being
done.
So
that's
how
git
ops
helps
and
that's
how
it
works.
Now,
going
back
to
the
story,
the
cause
and
the
effect
machine
was
a
huge
hit.
A
A
Now,
git
top
tools
are
no
different
than
the
cause
and
effect
machine
that
we
saw
some
time
ago
this
one
well,
what
makes
gitops
unique
is
that
it's
not
a
single
product,
plugin
or
platform
git
ops
is
a
framework
that
helps
teams
to
manage
id
infrastructure
through
processes
that
they
already
use
in
application.
Development,
popular
tools
like
ansible,
terraform,
kubernetes
and
so
on,
but
github's
process
is
largely
technology
agnostic,
except
for
gate.
Of
course,
without
it
get
ups
wouldn't
exist.
Now
qtops
is
suited
for
a
variety
of
scenarios.
A
Git,
ops
and
kubernetes
is
a
particularly
good
match.
For
example,
kubernetes
works
on
all
major
cloud
platforms
and
uses
stateless
and
immutable
common
git,
ops
tools
and
containers.
Containerized
apps
running
in
kubernetes
are
self-contained,
so
you
don't
need
to
provision
and
configure
services
for
each
app
provision,
kubernetes
clusters
and
other
needed
infrastructure,
like
databases,
networking
etc
using
terraform,
and
you
can
deploy
stateful
applications
with
ease
now.
A
So
what
are
the
take?
Aways
the
best
practices
of
kit
ops,
one
of
the
main
things
is
to
document
what
you
cannot
automate
if
it's
not
always
possible
to
automate
everything,
because
that's
very
important,
because
half
automation
is
more
dangerous
like
if
you're
doing
manually,
you
know
you
can
do
things
manually,
but
if
you
have
parts
automated
and
parts
manual,
then
documentation
should
be
well
written
and
you
should
work
on
ways
to
automate
those
steps
that
have
yet
not
been
automated
now.
A
Some
teams
already
use
a
git
repository
as
a
place
to
store
config
code,
but
don't
use
features
like
merge
requests
as
a
starting
point.
Take
a
look
at
the
code
review
guidelines
and
try
to
induct
the
team
into
these
practices.
Once
the
teams
are
familiar
with
the
tool
and
practices
implement,
mandatory
reviews
to
ensure
code
reviews
happen
every
every
week
say
or
every
few
days,
and
and
always
remember,
to
keep
these
guidelines
simple
so
that
it
is
easy
to
follow
and
not
work
around
it
and
that's
exactly
what
git
b
and
grandma
lilly
did.
A
So
that's
the
end
of
her
little
analogy
and
beginning
of
your
journey
into
githubs.
We
don't
have
much
time
left
today
for
a
live
demonstration.
I
would
rather
leave
you
with
some
useful
repositories
and
resources
that
will
help
you
pursue
githubs
and
try
out
the
demos
there
are
demo
links
also
I'll,
be
sharing
that
in
the
next
slide.
A
So
you
can
visit
that
repository
and
try
out
the
steps
and
read
the
notes
about
githubs
that
will
help
you
work
on
githubs
and
you
can
reach
me
out
anytime
for
any
help
if
you
need
to
get
onboarded
with
devops
and
github's
practices.
In
conclusion,
gitops
is
an
incredibly
powerful
workflow
pattern
for
managing
modern
cloud
infrastructure.
A
It
allows
you
to
be
more
productive
as
a
developer
as
a
devops
engineer
and
makes
your
finished
product
less
prone
to
errors.
Now,
back
to
the
story,
our
little
git
bees
cake
shop
is
now
the
most
sought
after
in
town
and
thanks
to
git
b's
cause
and
effect
machine
and
his
declarative
delivery
pipeline
and
thanks
to
gitops,
to
subscribe
to
my
channel
reach
me
to
learn
more
about
devops
on
my
email
address,
and
you
can
check
out
this
repository
at
github
and
learn
more
about
github's
practices.
Thank
you.