►
From YouTube: Technical Bootcamp - GitOps
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone,
my
name,
is
kurt
dusek
and
in
today's
partner
technical
bootcamp
we're
going
to
be
talking
about
git
ops,
so,
let's
level
set
with
what
git,
ops
actually
means
or
how
gitlab
defines
git
ops.
So
this
is
an
operational
framework
that
incorporates
devops
best
practices
used
in
application
development,
so
things
like
version
control,
collaboration,
compliance
and
ci
cd,
and
we
apply
those
concepts
to
infrastructure,
automation,
think
of
it
as
almost
devops
for
your
infrastructure.
A
Gitops
is
another
aspect
of
devops
that
encourages
organization
to
embrace
change,
rather
than
fear
it
so
fundamentally
altering
the
infrastructure
is
an
intimidating
task
for
many
people
and
historically
it's
represented
physical
change
and
the
risk
of
downtime
with
automation
and
cloud
computing.
We
can
remove
this
risk
and
make
the
changes
small
policy
driven
and
then
repeatable
and
reversible.
A
Now
there
are
three
main
components
to
get
ops.
The
first
is
using
infrastructure
as
code
and
storing
that
in
a
git
repository
next
are
merge,
requests
and
those
are
our
change
agents
and
essentially
our
audit
trail
of
what's
been
changed
when
it's
been
changed
and
who
changed
it.
And
finally,
ci
and
cd
automation
provides
our
reconciliation
loop.
This
ensures
that
our
infrastructure
is
up
to
date
at
any
given
time
infrastructure,
as
code
really
goes
beyond
just
the
infrastructure.
A
It's
really
more
like
x,
is
code
and
x
can
represent
infrastructure,
configuration
policy
or
any
other
operational
work
that
we
can
define
via
code.
This
is
declared
in
a
desired
state
and
it's
stored
in
the
git
version
control.
There's
a
lot
of
power
to
storing
code
in
a
version
control
system
similar
to
what
we
use
in
app
development.
Your
ops
teams
can
now
leverage
git
tools
as
the
user
interface
and
it's
a
tried
and
tested
and
easy
method
to
use
your
git's
main
branch
becomes
your
production
branch.
Whatever
is
in
that
branch
is
considered.
A
The
single
source
of
truth,
merge
request,
gives
you
a
gating
and
collaboration
capabilities,
code,
reviews,
discussions
and
even
approvals,
so
many
people
can
contribute
to
this
change,
but
a
small
number
of
approvers
are
the
only
ones
who
are
allowed
to
enact
the
change.
This
helps
with
auditing
and
compliance
standards.