►
Description
Did you catch GitOps Days 2021? In this episode, Scott Rigby of Weaveworks and the OpenGitOps Working group joins to talk about our favorite things from GitOps Days, the release of the GitOps Principles v1.0, and the GitOps Working group. Don’t know about the GitOps Working Group? The focus of the GitOps WG is to define a vendor-neutral, principle-led meaning of GitOps. The group’s initial task to determine a vendor-neutral, principle-led meaning of GitOps is now at hand with GitOps Principles v1.0. So join us live to find out more about the principles and the process of building the foundation of GitOps practices.
Learn more:
https://opengitops.dev
https://github.com/gitops-working-group/gitops-working-group
https://www.gitopsdays.com/
Follow us:
Christian Hernandez https://twitter.com/christianh814
Scott Rigby https://twitter.com/r6by
What is GitOps Guide to the Galaxy?
Every other Thursday at 3pm 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:
B
This
is
the
post
post,
chris
short
stream,
so
welcome
everyone
get
off
the
guide
to
the
galaxy.
I
am
christian
hernandez.
I
will
be
your
captain,
so
we
have
a
passenger.
Today
we
have
a
passenger,
no
stranger
to
the
show,
no
stranger
to
the
stream
scott
rigby
from
weavework
scott
give
us
a
little
introduction
little
little
haya
I
mean
I,
I
know
you've
been
on
the
the
stream,
I
think
more
than
anyone
other
guests.
A
A
A
And
open
source
work,
I
help
to
maintain
the
flux
project.
I
do
various
things
for
that,
including
the
community
stuff,
and
I
am
a
health
maintainer
as
well,
so
I
formally
co-maintained
the
the
the
stable
and
incubator
repos
that
everyone
used
before
we
distributed
those
to
artifact
of
the
cncfr
event
hub
so
and
I'm
on
a
great,
a
team
with
really
really
great
people
on
both
projects.
B
Yeah,
it's,
which
is
you
know,
it
sounds
like
a
lot
of
work.
To
be
honest
with
you
like
you,
it's
it's
like,
I
think
helm
would
be
a
just.
Maintaining
helm
would
be
a
full-time
job,
but
like
you're
like
straddling
both
helm
and
flux,
but
I
guess
it
kind
of
makes
sense
right.
You
know,
with
with
flux,
being
able
to
deploy
helm,
charts
right,
like
it
kind
of
makes
sense
that
you're
in
both
in
both
ecosystems,.
A
A
There's
different
things
that
I
contribute
and
that
we
all
contribute,
and
yes,
the
overlap
between
helm
and
flux
definitely
definitely
helps.
I
will
say
that
I
haven't
contributed
a
lot
to
the
flux
film
controller
in
the
year
that
I've
been
at
we
works.
Interestingly,
most
of
that
has
been
hidda.
Who's
just
been
just
an
incredible
powerhouse
behind
that
piece
of
the
flux,
ecosystem
and
contributions
by
others
too.
B
Yeah,
I
I
imagine
it
helps
both
sides
right
where,
like
you're
you're
trying
to
you
know
like
like
you're
working
on
an
issue
in
one
project,
and
it's
like
this
is
not
going
to
work
well
for
the
other
one.
That's
can
we
you
know,
so
I
think
I
think
it's
it's
good
to
kind
of
straddle
the
both.
You
know
a
little
bit,
so
I
yeah
I
I
don't
know
about
you,
but
my
brain
is
still
mush
from
last
week.
I
don't
think
I
don't
think
I've
recovered
from
from
kubecon.
So
it's
been.
B
B
Animal
crossing
for
real,
you
know
yes,
exactly
exactly
yeah,
so
real
life
animal
crossing,
so
it
was,
you
know
all
the
stuff
leading
up
to
kubecon
and
then
kubecon
itself,
and
then
you
know
there
was
the
for
you.
You
guys
had
the
the
get
ups
one
stop,
so
we're
gonna
get
to
those
in
a
second.
So,
but
I
don't
know
about
you,
my
brain
has
been
mush
and
finally,
today
thursday,
I
finally
started
recovering
from
from
kubecon
and
get
ops
con.
B
So
I
think
next
week,
you'll
start
recovering
because
you
have
the
the
one
stop
thing
so
so
I
actually.
I
think
I
think
this
is
a
good
segue,
so
get
ops
con.
So
we
for
those
of
you
who
didn't
know
we
had
our
second
ever
get
ops
con.
The
and
the
in
our
first
in
person
get
ops
con
here
at
kubecon.
It
was
a
day,
zero
event.
It
was
absolutely
fantastic.
I
had
a
great
time.
You
know
scott
mentioned
that
you
know
he's
he's
in
the
open.
B
Get
ops
working
group
right
where
open
get
ops
is
a
a
sandbox
project
right
that
a
lot
of
a
lot
of
vendors
are
are
taking
a
part
of
and
a
lot
of
end
users
are
taking
part
of
so
we
decided
to
come
together.
Do
git
ops
con
the
first
one
was
great:
it
was
online
second
one.
We
did
it
in
person
at
kubecon,
so
so
get
up's
gone
right,
so
yeah.
So
what
were
your
impressions
of
actually
being
there
and
actually
walking
into
that
room?
It
was
kind
of
surreal.
B
A
A
I
don't
want
to
skip
ahead
to
some
of
the
other
news
that
you
have,
but
there
are
also
a
few
other
places
we
have
thanks
when
you
get
to
those
all
I'll
mention
I'll
mention
that
there
then,
but
I
think
your
question
was
really.
How
did
it
feel
yeah
well
yeah,
so
I'm
proud
of
what
everybody
did
and
yeah
thanks
for
you
know
and
including
myself,
I'm
proud
of
that
too,
and
it
was.
B
A
B
The
numbers
speak
for
themselves,
right
yeah,
but
I
mean
it
was
actually
pretty
nice
too,
because
I
was
jumping
back
and
forth
at
a
lot
of
day.
Zero
events
it's
but
the
the
the
last
half
I
spent
it
all
on
get
ups
con.
It
was
really
cool
to
be
able
to
like
walk
in
and
like
see
all
the
people
it's
it
was.
It
was
pretty
cool
to
be
like
there
were.
You
know
at
kubecon,
it
was
you
know,
not
a
lot
of
people
registered.
B
You
know
fully
understand,
you
know
it's,
you
know
traveling
and
with
covid,
and
you
know
that
the
situation
and
everything
is
you
know
we
were
built
for
maybe
larger
than
the
antennas
was
there.
So
there
was,
you
know
a
lot
of
empty
chairs.
Getupscon
there
was
a
lot
of
empty
chairs.
There
was,
I
mean
there
was
empty
chairs,
but
not
a
lot.
I
mean
there
was.
B
A
B
Oh
yeah,
definitely
definitely
so.
100
kudos
shout
out
to
rachel
who
was
from
the
cnc,
was
helping
us.
She
was
fantastic,
putting
up
with
us
from
the
open,
open,
get
ups
working
group
and
and,
and
you
know,
helping
us
there
so
talking
about
the
event
specifically,
I
want
to
know
what
your
favorite
talks.
I,
I
wonder,
you
know
I'll
I'll,
keep
mine
close
to
the
vest
and
see
if
we
have
the
similar
favorite
talk.
So
what
were
your
like?
B
A
A
B
B
A
A
Super
interesting
because
it's
really
speaking
from
the
perspective
of
different
end
users
and
it
was
a
way
to
kind
of
I'll
say-
maybe
I
don't
know-
perhaps
I'm
just
betraying
my
limited
attention
span,
or
maybe
the
fact
that
I
also
had
to
like
do
several
things
during
the
conference.
But
it
was
easier
for
me
to
be
able
to
compare
and
contrast,
different
processes
and
different.
A
Let's
say
salute
problems
that
different
people
that
various
people
had
and
how
they
went
about
solving
those,
but
what
alternatives
they
they
tried
before
moving
to
get
ups
and
then
what
they
did
move
to
get
us
how
they
how
they
are
currently
implementing
it.
It
was
a
lot
easier
for
me
to
compare
those
in
my
mind
because
they
were
all
they're
actually
in
a
discursive
setup
on
a
panel
where.
B
B
B
A
Don't
know
I
don't
know,
that's
not
my
area
of
expertise,
it
probably
should
be
but
yeah
yeah
like
I
agree
and
and
then
we
had.
Let's
see
we
had,
we
had
may
large
from
state
farm.
So
that
was
really
coming
an
end
user
that
was
coming
from
the
the
insurance
world
and
that
side
of
the
finance
and
insurance
world
and
then
and
then
mike
bowen
from
blackrock.
So
he.
B
B
A
B
B
She
pre-recorded
her
talk
right,
so
she
pre-recorded
because
she
couldn't
make
it
to
l.a.
So
I
think
it's
it's
one
thing
to
be
like
captivated
or
captivating
like
on
stage
live
right.
That's
in
itself!
I
think
it's
hard
to
do
right.
I
I
endeavored
to
try
to
not
make
things
boring
right.
You
know
I
always
continue
to
try
to
improve
emily
freeman.
She
can
captivate
you
via
video
like
I
was.
B
I
was
sitting
there
and
like
I
was
as
if
it
made
me
feel
like
she
was
actually
there
and
her
presentation
was
was
fantastic
as
well.
So
that
was
another
great
presentation,
my
favorite
and
it's
it's
gonna
seem
kind
of
weird
where
I'm
looking
through
it,
I
wanna
get
the
name
of
it
just
right.
Yes,
so
my
favorite
was
a
day
in
the
life
of
getups
platform
team
from
the
team.
B
B
Yeah,
oh
yeah,
yeah
yeah,
you
got
to
gotta
gotta
stay
on
brand
right,
so
your
personal
brand,
all
right
so
pinky's
brand
I'll
stay
on
pinkie's
brand,
so
pinky
and
and
and
may's
presentation
was
fantastic
only
because
because
like
they
took
you
through
the
whole
process
of
failing
at
first
and
then
and
then
what
led
to
them
to
be
an
ultimate
success
right.
So
it
was
kind
of
like
oh
yeah.
B
We
messed
up
a
lot,
and
this
is
the
kind
of
stuff
we
did,
and
this
is
the
kind
of
stuff
that
we
did
to
fix
it
right
so
kind
of
like
a
like
an
rca
right
root,
cause
analysis
and
what
what
we
did
and
it
was
actu
and
it's
funny
because
it
I
think
it
shows
the
power
of
get
ops
just
in
general,
because
they're,
a
small
team
they're
like
a
team
of
three,
maybe
four
right
from
what
I
remember
yeah
taking
care
of
a
large
deployment
using
git
ups.
So
it
it.
B
I
think
it
really
speaks
to
the
the
power
of
get
ops
and
it
you
know-
and
it
was
just
a
fun
presentation
as
well
right.
They
were
energetic,
and
you
know
again,
I
I
like
the
the
energy
that
came
out
of
I
came
out
of
that
that
talk
it
was.
It
was
really
great
to
hear
you
know
the
not
only
like
the
success
part
of
it,
but
also
the
failure
part
of
it
as
well.
Oh.
B
A
B
A
Not
boring
me
you're,
not
boring
me
christian
yeah,
no
seriously,
it
is
great
to
hear
failures,
so
I
think
that's
why
I
think
with
sonia
who
came
up
with
the
the
the
the
tales
from
the
branches
twist,
the
tails
from
the
trenches.
But
in
any
case
it
was
a
collective
collaborative
brainstorm
effort,
but
but
I
think.
A
For
it
really
sort
of
brings
the
spirit
of
yeah,
this
thing's
got
not
only
for
that
talk,
but
others.
You
know
you
know
there
there's
also
things
that
we
can.
I
mean
even
more
so
sometimes
things
we
can
learn
by
the
problems
people
faced
and
how
they
did
something
in
a
way
they
would
never
recommend.
A
B
Yes,
well
and
also
again
tips
for
people
writing
cfps,
like
failure
talks,
they
they
automatically
shoot
for
the
on
the
top,
for
whatever
reason,
after
being
a
part
of
a
few
committees
right,
cfp
committees,
it's
like
hey,
I
failed,
and
this
is
what
I
did
they
ought
to.
You
know
automatically
people
love
that
so
just
kind
of
a
a
little
hint
that
people
like
failure,
because
they
because
it's
like
I
want
to
know
what
I
should
do.
B
A
B
A
Loved
that
I
loved
her
talk-
oh
my
god.
Yes,
yes,
so
good,
so
good
yeah
like
folks,
please
watch
that
it
was
amazing.
I
really
liked.
I
also
liked
your
talk
christian
by
the
way
christian
gave
the
other
or
one
of
the
other
keynote
talks
as
a
representative
of
red
hat.
Basically,
just
you
know
how
these
things
work.
There
are
sponsors,
so
there.
B
Was
it
was
yeah?
Actually,
if
you
know
those
those
who
are
watching
the
the
more
sponsors
that
come
the
bigger
we
can
make
this
so
yeah
we
can.
We
couldn't
do
it
like.
You
know,
thanks
to,
like
you
know,
obviously,
red
hat,
but
also
weave
works
code,
fresh
hashicorp,
aws,
amazon
folks.
They
sponsors
help
put
this
on
right
because
it's
we're
for
them.
We
wouldn't
be
able
to
have
like
all
this
talk,
so
it
was.
A
I
mean
this
is
not
a
small
section
of
you
know
of
cloud
practices
anymore
or
I.t
practices.
This
is
quickly
becoming
a
standard,
so
yeah,
and
by
this
I
mean
get
ups
in
whatever
folks
want
other
folks
want
to
call
it
they're,
it's
certainly
becoming
can't
actually
say
a
standard.
There
are
standards
coming
around
it
through
the
good
offspring
group
that
I
think
we're
going
to
talk
about
next,
but.
A
A
B
Yeah-
and
actually
you
know
to
your
point-
is
it
is
definitely
a
good
segue
to
our
next
topic.
Is,
you
know,
get
ops
con.
It
was
great
to
to
see
everyone
there.
It
was
great
to
hear
the
stories,
and
even
even
with
this
hangover,
we're
gonna.
Do
it
again
in
the
eu.
We're
gonna
do
it
again
in
the
eu,
so
I
I'm
already
signing
because
it's
like
man,
that
was
a
lot
of
work,
all
right,
get
ready
to
do
it
again,
but
we're
gonna.
Do
it
again.
B
So
for
those
of
you
who
were
in
emea
that
couldn't
make
it
here
in
person,
we're
gonna,
do
it
in
person
again,
so
you
know.
Hopefully
we
need
to
start
planning
that
so
we'll
we'll
figure
that
out
sometime
next
week
but
get
ops
con
was
there
was
a
big
announcement
there
around
the
open
ship
get
ups
and
openshift
get
ops
working
group.
It
was
the
openshift
sorry,
the
openshift,
the
open,
getups,
everything
with
open
it's.
We
need
to
stop
doing
things.
B
B
A
B
A
Exactly
go
until
the
end
and
then
stop
yeah,
so
yeah.
In
short,
this
this
was
summarized
in
our
release.
Notes.
So
first
I'll
show
you
ultimately
on
this
website.
The
very
first
question
you'll
see
is
what
is
open?
Give
ops
so
I'll
just
tell
you:
it
is
a
set
of
open
source
standards,
best
practices
and
community
focused
education.
A
A
Getups
is
a
cncf
sandbox
project
that
is
part
of
the
the
cncf
app
delivery
technical
advisory
group.
So
for
those
of
you
who
don't
know,
in
short,
they
used
to
be
called
sigs
or
special
interest.
Groups
named
after
the
sigs
in
kubernetes
they've,
now
changed
a
little
bit
in
format,
otherwise
the
same,
but
if
you're
interested
check
that
out
that
thread
out
on
its
own,
but
now
they're
tags,
technical
advisory
groups.
A
So
the
app
delivery
tag
working
groups
since
you've
heard
about
this
thing
called
the
get
ops
working
group
working
groups
within
the
cncf
are
are
meant
to
be
short-lived
groups,
however
long
or
short
short
means
just
in
or
only
long
enough
to
fulfill
their
goals
that
are
all
within
a
technical
advisory
group.
So
so,
in
the
case
of
the
get
ops
working
group,
the
githubs
working
group
is
below
the
the
app
delivery,
the
cncf
app
delivery
tag.
B
A
If
it
doesn't
to
you,
you
can
read
up
on
it
or
or
ping
us
and
we'll
send
you
more
more
info,
but
I
hope
that
helps
a
little
bit
and
some
folks
have
been
asking
well,
what's
the,
what
how
does
opengetops
and
the
getups
working
group
relate
are,
is
open,
get
ups,
the
new
get
ups
working
group,
etc.
The
answer
is
sort
of.
B
A
A
That's
the
sandbox
project
is
the
place
where
the
lasting
any
lasting
documents,
programs
and
any
possible
code
like
for
interoperability
between
tools
or
whatever
else
will
will
live,
and
so
right
now
I'll
show
you
very
quickly
effective
view
I'll
scroll
all
the
way
down.
Just
to
so,
you
can
easily
see
how
you
get
to
this.
The
open,
git,
ops.
A
A
But
you
can
go
to
the
basically
the
project,
repo
is
the
entry
point
and-
and
it
gives
you
information
about
what
the
really
what
the
different
repositories
within
opengetops
are
for.
So
I
hope
that's
fairly
clear
yeah.
I
just
realized
we
have
to
update
these
links
in
any
case,
so
the
documents
repo
is
well
sorry
just
to
be
clear,
so
things
like
governance
and
other
documents
are
still
within
the
getups
working
group
repo.
A
B
A
Exactly
and
it's
set
up
to
be
fairly
easy
for
folks
to
contribute
to
so.
Yes,
that's
actually
another
note
from
the
from
the
events
committee
within
the
get
offs
working
group
events
like,
for
example,
this
one
we're
doing
right
now
would
have
been
really
nice
for
me
to
open
a
pr
for
that.
Maybe
I'll
just
do
that
retroactively
christian.
A
Yeah
but
but
any,
and
it
does
actually
on
the
website
list-
past
events
right
here
so
and
on
the
events,
tab
so
yeah.
So
that's
actually
a
good
call
to
action
for
everyone,
but
to
stay.
Excuse
me
to
say
I'm
to
stay
on
track
with
this
v.
I'm
the
place
where
you
want
to
go
to
see
the
the
the
current
documents
and
what
was
just
published
is
the
documents
repo.
A
A
But
if
you
are
on
the
main
branch,
there's
really
just
an
urgent
placeholder
to
make
it
very
clear
that
this
is
something
that
is
a
project
that
folks
are
contributing
to,
and
you
can
too,
but
once
those
contributions
happen
between
versions.
No
one
will
look
at
this
page
and
be
confused
that
that,
what's
in
the
actual,
tagged
version
isn't
what
is
stated
up
above.
If
that
makes
sense,.
B
A
Exactly
and
and
and
if
you
want
to
learn
more
about
the
you
know,
get
ups
working
group,
and
I
think
that
you
know
pretty
much
all
of
these
repos,
including
this
one
will
say
it
outright.
What
what
the
relationship
is.
So
if
you
came
in
a
little
late
for
me
describing
that
before
you
can
just
get
it
there,
but
this
is
a
fancy
thing
right
here:
releases
there's
one
non-pre-release
a
full
release
season,
yay
this
of
was
over
for
over
six
months
by
people
from.
B
A
Listed
down
here
so
so,
when
you
go
to
the
1.0.0,
excuse
me:
release
under
open
dash.
Get
up.
Excuse
me,
github.com,
open
dash,
get
off
slash
documents.
If
you
go
to
the
1.0.0
release
you'll,
you
know,
there's
a
very
short
change
log
between
this
and
the
last
release
candidate,
but
there's
a
few
like
little
introductions,
but
basically
it's
clear.
A
This
is
the
first
full
release
of
the
principles
in
the
glossary
by
the
get
ups
working
group
and
the
attribution
list
of
the
folks
who
have
contributed
to
this
is
here.
So
it's
an
alphabetical
order
by
last
name.
So
it's
also
in
git
fashion.
We
do
give
proper
co-authorship,
so
you'll
actually
see
on
the
home
page
as
well,
that
that
it
will
show
a
list
of
contributors.
I
think
we
need
to
link
up
people's
actual
email
addresses
so
that
once
you
click
into
contributors,
you
see
them,
but
they're.
A
Actually,
here
and
and
and
one
thing
thing,
I
want
to
point
your
attention
to
is
at
the
very
beginning,
there's
also
a
special
thanks
here
to
all
the
interested
parties
from
the
initial
get
ops
working
group
sign
up
list
and
really
it's
true.
This
line
saying
your
continued
support
and
involvement
are
critical
for
this
community
initiative.
That
is
completely
true.
If
it
were
really
just
a
few,
people
wouldn't
be
much
of
a
standard,
would
it
so
yeah?
B
Yes,
kubecon,
so
what
I?
What
I
really
really
liked
about
the
principles
and
I
think
dan
he
tells
the
story,
and
I
think
I
think
it's
really
really
great
and
I
think
it
it
really
highlights
the
the
principles
themselves.
Is
he
there
was
a
talk
where
people
say
where
they
started
with
hey?
How
many
of
you
are
doing
get
ops
today
and
I
was
like
60
of
the
people
raised
their
hand.
They
did
the
presentation
all
right,
how
many
are
actually
doing
get
ups
and
there's
like
three
people
right,
like
oh.
A
B
Which
I
mean
it's
it,
it's
it's
not.
So
I
think
what
I
really
like
the
principles
is
that
it's,
it's
really
a
guide
right
to
for
those
who
really
want
to
do
get
ops.
It's
not
meant
to
be
like
a
gatekeeper
or
it's
not
meant
to
be.
Like
you
know,
this
is
the
club
and
you're
out
of
it
sort
of
thing.
It's.
B
I
think
this
is
this
is
a
great
vendor,
vendor
neutral
kind
of
guiding
principles
of
of
what
needs
to
happen
in
order
to
truly
do
get
ops
right
because
yeah,
it's
like,
I
always
say
I
always
say
it's
much
much
more
than
infrastructure
as
code
and
as
as
you
as
you,
you
always
point
out.
It's
like
it's
much
more
than
a
bunch
of
web
hooks
right.
So,
can
you
quickly
go
over
yeah
like
like
the
four
like
just
the
principles
and
kind
of
like
what
they
mean.
A
B
A
Yeah
yeah.
Yes,
so
so
don't
let
the
simplicity
of
these
fool
you
kind
of
in
haiku
fashion.
These
were
meticulously
marked
over
over
the
past
six
months,
sometimes
going
back
to
the
drawing
board
when
certain
directions
didn't
really
suss
out,
and
there
are
also
a
couple
of
open
discussions
about
about
extending
these
principles.
But
this
is
the
1.0
version.
So
this
is
exactly
what
you'll
see
in
in
github
right
here
or
at
least
on
the
v
1.0
photo.
A
So
but
I'll
I'll
just
show
this
screen,
because
it's
a
little
cooler
to
look
at
yeah.
I
hope
so
for
accessibility
purposes.
If
somebody
has
a
better
idea
about
colors
and
other
support,
just
let
us
know,
but
in
any
case
the
very
first
principle
and
and
and
one
thing
that
is
actually
not
on
here-
that
I
should
make
sure
that
we
clarify
is
that
for
the
git
ups
principles
there.
This
is
the
very
first
introduction
we
think
it's
super
important.
A
A
A
B
Yeah,
I
think
I
think-
and
I
remember
being
part
of
this
process
is-
I
think
the
glossary
was
almost,
I
think,
more
important
than
the
actual
principles
themselves,
because
it's
like
well.
What
do
you
mean
by
declarative?
Or
what
do
you
mean
by
system?
It's
like
well
yeah.
We
should
probably
define
those
terms,
because
you
know
sometimes
some
terms
are
overloaded
right,
it's
like
well,
we
mean
it
in
a
specific
way.
B
A
Exactly
yeah,
I'm
glad
you
said
that,
okay,
so
that's
really.
I
hope
that
makes
sense
that,
like
you
know,
in
order
to
move
ahead,
your
whole
system
and
everything
that's
running
should
be
able
to
be
expressed
declaratively
so
that
when
folks
are
just
connecting
infrastructure
as
code
with
get
ops
and
wondering
how
they
relate.
This
is
how
they
relate
principle.
One
of
open,
github
excuse
me
principle.
One
of
the
getups
principles
is
essentially
infrastructurous
code.
A
You
could
kind
of
easily
you
could
kind
of
say
that
the
second
principle
is
that
your
desired
state
should
be
versioned
and
immutable.
So
it's
really
important
that,
however,
you
store
it
and
let's
be
clear,
we're
trying
we're
making
sure
that
this
is.
This
is
a
set
of
principles,
so
it
has
to
be
quite
neutral:
you're
not
forced
to
use
git
with
git
ops.
It
happens
to
be
the
most
popular
version.
A
A
A
A
Okay,
in
all
cases
of
any
type
of
storage
system,
for
for
get
up,
storage
or
excuse
me
desired
state
store,
the
state
source
need
to
be
properly
configured
and
certain
precautions
have
to
be
taken
in
order
to
comply
with
the
requirements
set
out
in
the
principles
in
the
githubs
principles.
So,
for
example,
even
using
git
out
of
the
box
doesn't
mean
you're
using
githubs.
A
It
also
doesn't
mean
that
it's
that,
if
you're
using
git,
it's
automatically
qualifies
as
as
a
as
a
state
store
in
line
with
github's
principles,
for
example,
if
you're
using
get
up
a
cloud
manage,
get
ops,
excuse
me
get
system
or
a
get
say
provider
that
that
gives
you
options
to
protect
your
branches
and
and
gives
you
options.
Let's
say
to
protect
your
tags
or
to
make
sure
that
your
tags
are
immutable
or
whatever
it
is
that
you're
doing.
A
Then
then
you're,
then,
if
you're
not
choosing
those
options,
you're
not
really
setting
it
up
well
to
the
immutable
same
with
same
with
object,
storage,
buckets
like
s3,
compatible
ones
or
any
object,
storage
bucket,
that's
supported
right
by
whatever
tool
you're
using
I
mean,
if
you
don't
set
those
up
to
be
versioned
and
most
of
them
do
allow
versioning.
Do
you
allow
versioning
as
configuration
and
have
other
things
that
help
with
immutability?
A
B
A
lot
of
people
don't
don't
know
like
so
a
mutation
of
of
your
desired
state.
It
even
applies
when
you're
trying
to
roll
back
right,
because,
technically
speaking,
you're
rolling
back
you're
still
rolling
forward
right.
It's
still
a
it's
still,
a
a
mutation
of
of
whatever
that
old
desired
state
was
so
it's
I
think,
version
and
immutable
together.
I
think
it's
is
that's.
I
completely.
You
know
not
not
to
toot
your
own
horn
right,
but
it's
like
completely
agree
right.
A
A
Basically,
a
trustworthy
storage
system,
so,
okay,
then
the
third
principle
is
that
a
desired
state
should
be
pulled
automatically
that
there
is
some
debate
about
this,
because
folks
can
also
do
pushes
as
well
in
most
with
most
tools
and
that's
also
supported
and
completely
fine,
not
just
fine,
but
it's
also
very
valuable
at
times
to
speed
up
certain
processes.
But
excuse
me,
the
point
is
that
there
are
software
agents
and
for
those
that
don't
know
what
I'm
talking
about
by
an
agent
kubernetes
land.
A
A
They
have
to
be
able
to
do
that
at
any
time,
and
so
that
is,
it
doesn't
just
happen
when
you,
when
you
do
some
action
like
I
change
my
configuration
and
or
run
or
rerun
a
ci
job
or
something
like
that.
Those
agents
have
to
have
agency
to
do
that
on
their
own,
and
the
reason
for
that
is
that
one
of
the
big
values
of
git
ops
besides
I
had
mentioned
disaster
recovery
and
other
things
like
that-
are
that
your
system
may
drift
for.
A
B
Yeah-
and
I
think
I
think
polled
is
is-
is
less
of
a
of
how
the
action
happens
and
more
of
like
how
I
get
my
declarations
right
so
like
we're
talking
about
pulling
in
terms
of
because
you
can
set
up
a
system
to
either
push
out
the
cheat.
You
know
reach
out
and
make
those
changes
or
the
you
know
the
agent
sitting
on
the
actual
system,
that's
being
managed,
and
then
it
manages
itself.
B
A
Yeah
we
could
have,
we
actually
debated
using
the
word
accessed
automatically
and
a
few
other
different
options,
but
somehow
this
seemed
to
be
very
valuable
because,
no
matter
what
we
wrote
before
there
was
still
kind
of
people
to
skim
over
these
things.
Right,
yeah
and-
and
it's
pretty
this
so
far
anyway-
has
stood
the
short
test
of
time
with
the
group
that
it
seems
to
always
bring
up
this
question
about
wait.
A
second
can't
we
just
can't.
We
just
push
can't
we
just
run
ci
job.
A
B
B
You
know
you
know,
noticing
the
bathroom
being
dirty
and
then
me
telling
my
kids
to
clean
it
versus
telling
them
to
keep
the
bathroom
clean
continuously,
but
and
but
that
was
kind
of
complex,
but
that
was
kind
of
complex.
I
think
dan
did
a
perfect
job
of
saying
it's
really
like
a
thermostat
right
instead
of
like
me
sitting
here.
Oh,
I
feel
warm.
Let
me
turn
on
the
air.
You
just
set
the
thermostat
to
your
desired
state
and
it'll
turn
on
and
off
and
it'll
the
feedback
loop.
A
A
A
A
B
A
I'm
just
giving
the
comments
you
all
are
so
funny:
okay,
yeah
yeah,
so
so
so
please
join
in
on
that
because
it's
it's
it's
not
something
that's
important
at
this
very
moment
or
it's
important,
but
it's
not
there's
no
critical
timeline
on
it,
but
it
could
potentially
make
its
way
into
a
future.
Release
of
the
principles
is
the
talk
about
closed
loop
and
a
system
that
is
intelligent
and
uses
feedback
from
it
from
its
past
runs
and
from
the
system
itself.
Yeah.
B
Like
a
thermostat,
yes,
like
a
thermostat
exactly
so
so
so
over
the
last
few
minutes
here
that
we
have,
by
the
way
great
conversation,
it's
always
great
conversation
with
you,
scott.
We
have
the
the
one
stop
event
that
happened
yesterday.
I
believe
that
we've
put
together,
but
it
was
people
from
all
over
the
place
from
microsoft,
red
hat,
amazon,
aws,
all
kinds
of
folks
took
took
part.
I
don't
know
how
you
had
the
energy
for
it,
because
my
brain
is
was
so
much,
but.
A
A
B
A
A
We're
it's
the
the
the
the
goal
of
this
here
ultimately,
is
to
showcase
the
different
cloud
providers
who
offer
git
ups
services.
There
are
a
lot
of
other
companies
who
offer
get
up
services.
There
are
a
lot
of,
let's
say,
hosted
products
and
projects.
There
are,
for
example,
like
I'll
just
say,
for
example,
code
fresh
right
also
also
provides
a
github
service.
I
don't
believe
they're
a
cloud
provider
if
I'm
saying
that
right
dan
kill
me
if
I'm
wrong,
but
but.
A
There
are
a
lot
of
services
out
there
that
relate
to
get
ups
now
and
and
because
people
people
need
it
and
people
are
using
it.
But
these
are.
These
are
cloud
providers
who
really
the
idea
is
you
can
run
kubernetes
anywhere
and
you
should
be
able
to
run
git
ups
anywhere,
and
if
you
do
you
don't
really.
A
The
idea
here
is,
of
course
they
all
want
to
keep
your
business,
but
but
you
can
pick
and
choose
you
know
you
can
choose
what
works
for
you,
which
which
features
of
those
products
and
whatever
else
you
use
to
make
your
decisions.
You
can
go
with
you,
but
you
don't
have
to
use
whether
or
not
excuse
me.
You
do
not
have
to
choose
whether
or
not
to
use
git,
ops
and
one.
A
Here,
because
I'm
also
representing
as
a
chair
of
the
the
vendor
neutral,
get
ops
working
group,
I
do
work
for
weworks
and
we
work
organize
this
event
with
these
other
with
these
other
cloud
providers.
And
to
that
end
the
primary
focus
was
on
the
flux
tool,
because
that's
the
tool
that
these
cloud
providers
are
using
to
deliver
to
deliver
git
ups
and
are
building
it
as
the
under
structure
of
their
tooling.
It
doesn't
mean
that
other
tools
aren't
useful
as
well.
So,
but
that's.
B
What's
what
was
really
cool
is
I
actually
I
put
a
put
a
link
in
the
chat.
There
was
a
talk
given
by
one
of
our
architects
andrew
block.
He
did
one
about
flux
and
openshift
so
b.
Whenever
the
recordings
go
up,
be
make
sure
to
check
that
out
and
yes
that
that's
the
one
I
I
posted
that
link,
so
the
links
will
be
there
and
yeah
check
out
check
out
any
of
those
so
yeah.
It
was
a.
A
A
Yeah,
I
want
to
call
out
every
single
one
of
these
people.
We
can't
do
that
in
three
minutes
and
be
able
to
tell
you
how
to
participate.
You
know
in
open
ups
moving
forward,
but
this
was
a
really
a
really
good
event.
Recordings
are
going
up
if
they're
not
already.
I
probably
should
know
that
yeah,
but
but
yeah.
Please
check
it
out.
B
A
A
Repo
that
I
mentioned
is
probably
the
one
that
you
want
to
start
and
watch,
because
that's
where
the
majority
of
that's,
where
the
lasting
documents
are,
if
you
care
about
the
website,
changes
or
things
that
relate
directly
to
the
project
itself,
as
an
overall
cncf
project,
feel
free
to
obviously
star
and
or
watch
those
two.
But
you
really
want
to
make
sure
to
to
to
do
that
on
on
the
the
open
github's
documents.
Repo
also
inside
of
the
contributing
document,
sees
the
inside
of
the
contributing
document.
A
And
we're
going
to
be
moving
this
again
to
the
tag
to
go
to
the
app
delivery
tag,
but
here's
the
high
level
of
things
you
need
to
know
right
now
the
working
group
still
meets
every
other
wednesday
at
1800
gmt,
so
whatever
that
is
for
you
in
your
time
zone.
Every
other
wednesday
is
not
yesterday,
but
it
will
be.
It
will
be
this.
A
A
Here's
my
question
or
here's
my
here's,
my
request
or
here's
my
idea
and
there's
also
youtube
playlists
for
all
the
recordings
and
previous
meetings.
Now
they
are
being
updated,
so
they're
a
little
behind,
but
we've
had
a
lot
of
them.
So
please
bear
with
us
if
you're
interested
in
a
particular
one.
Sooner
than
later.
Let
us
know
we'll
try
to
prioritize
that
and
then
the
other
way
is
you
can
be
part
of
a
you
can
be
part
of
a
committee
within
the
get
up
to
working
group.
B
Yeah
well
just
real
quick.
I
put
it
in
the
chat
reach
us
at
cncf
slack
as
well.
That's
probably
just
holler
at
us
we're
all
we're
all
there
so
yep,
so
we're
at
the
top
of
the
hour.
Thank
you,
scott.
Thank
you
for
all
that
information
and
yeah,
we'll
we'll
see
you
around
get
involved
and
thank
you
for
joining
so
also
special
thanks
to
john
here
who
was
in
the
background,
helping
us
do
all
this
stuff
and
yeah
I'll
see
you
guys
next
time,
yeah.