►
Description
The end of the year typically comes with a lot of great reminders about security, compliance, best best practices. In this episode as we close out 2023 we’ll take a look at the External Secrets Operator on OpenShift for how to manage secrets the operator way.
Join GitOps all-stars Hilliary Lipsig and Christian Hernandez guests for a fun and engaging trip through the galaxy of GitOps. She’ll take us from orbit down to the street level of how we can achieve and manage our infrastructure using modern best practices.
Want to learn more?
https://external-secrets.io/v0.7.0/
https://github.com/external-secrets/external-secrets
Try Red Hat OpenShift: https://red.ht/3sMaW7O
Follow us:
Hilliary Lipsig https://twitter.com/Int2Caffeinate
Christian Hernandez https://twitter.com/christianh814
OpenShift https://twitter.com/openshift
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
What is GitOps Guide to the Galaxy?
Every other Thursday at 3pm ET host Hilliary Lipsig and guests dig in to discuss everything in the GitOps universe, from end-to-end CICD pipelines to creating Git workflows.
Learn GitOps https://red.ht/3saqlzS
What is GitOps? https://www.redhat.com/en/topics/devops/what-is-gitops?sc_cid=7013a000002qG1BAAU
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
OpenShift on redhat.com https://red.ht/3LGCIeD
OpenShift on GitHub https://github.com/openshift/
#RedHat #GitOps #Kubernetes
A
We're
live
now,
For,
Better
or
For
Worse
technical
difficulties
include
we're
gonna,
be
doing
some
live
debugging
for
today's
demo,
because
the
setup
didn't
work
so
I'm
sure
it's
a
me
problem
like
I'm
I'm,
really
sure
it's
a
me
problem,
but
I
had
20
minutes
to
work
on
this
at
the
end
of
the
day.
So
I'm,
okay,
with
it
being
a
me
problem
right.
B
A
Hello,
we're
back
we're
back
for
the
first
time
and
last
time
for
the
year
after
a
bit
of
a
break,
I
went
on
vacation
and
then
I
came
back
from
vacation
with
the
flu.
So
we
didn't
stream
when
we
were
supposed
to
and
then
I
had
two
weeks
of
work
to
catch
up
on
instead
of
one
week
to
work.
I've
worked.
B
To
catch
up
exactly
yeah,
exactly
yeah,
it's
it's
it's!
It's
been
a
a
really
weird
December
for
me
as
well.
You
know
coming
back
to
Red
Hat
and
like
in
a
new
and
and
also
a
a
brand
new
role,
so
it's
kind
of
like
I'm
like
oh,
that's,
right,
we're
supposed
to
stream
and
you're
like
I,
am
sick
as
a
dog
I'm
like
well
I.
Could
you
definitely
use
this
hour
because
I
need
to
catch
up
on
some
things
as
well.
A
You
know
that
was
so
bad.
It
was
so
bad
I
I
haven't
had
influenza
in
like
20
years
and
I
I
caught
it
and
I
had
a
fever
for
four
days
I.
My
fever
was
102
degrees,
Fahrenheit,
someone
smarter
than
me
do
that
conversion
to
Centigrade
after
fever,
reducers
and
I
was
I
was
like
and
I
was
dying
right.
Oddly,
my
husband
and
children
did
not
get
sick,
not
even
a
little
bit
sick
from
me,
but
no
so
it
was
terrible.
I've
never
been
so
out
of
it
and.
B
A
A
B
A
True
right,
so
why
are
we
here
today
right
we're
here
to
look
at
the
external
external
operator,
and
this
is
just
really
a
timely
episode.
I
wanted
to
kind
of
end
the
year
with
security,
because
I'm
in
compliance,
land
and
security
training
land
which
I
have
to
do
every
year
around
this
time
and
I
figure
lots
of
people
have
to
do
that
every
year
around
this
time.
So
that's
a
great
way
for
us
to
just
kind
of
end
the
year.
B
B
Great
yeah,
which
is
what
I
think
some
people
like
it
when
it's
not
working
live
debugging
as
we
say
right
so
yeah.
It
is
very
timely
because,
like
just
like
in
my
new
role
here
at
Red,
Hat
I'm
actually
focusing
more
on
the
security
side
of
get
Ops,
and
so
it's
very
very,
very
topical
right,
like
kind
of
like
yeah,
let's
work
on
the
security
Secrets
operator,
there's
many
many
opinions
on
this
too,
as
well
and
I.
Think
the
external
Secrets
operator
is
kind
of
like
a
good
compromise.
B
So
that's
kind
of
like
the
idea
of
like
sealed
Secrets,
which
we
I
think
we
talked
about
like
way
way
earlier
in
the
beginning
of
this
of
the
stream.
And
then
we
have
like
secret
reference
kind
of
like
what
we
talked
about.
I,
think
I,
think
I
had
Rosemary
from
from
talk
about
Vault
right
and
those
are
kind
of
the
two
that
bubbled
up
there's
another
one
where
it's
like.
You
can
mount
a
drive
amounts
of
volume
or.
B
So
but
I
think
that
the
two
big
ones
are
like
you
know,
either
store
the
secret
encrypted
or
so
the
secret
reference
I.
Think
external
Secrets
falls
under
the
reference
part
of
it
on
the
on
that
part
of
that.
But
I
think
what
makes
the
external
Secrets
operator
great
is
that
you
can
connect
it
to
different
kms's
right
or
different
back-ends.
So
I
think
that's
that's
like
the
power
in
it
right.
I'd,
really,
that's
the
reason.
A
Sounds
great,
so
we
actually
do
we
actually
do
the
secret
reference
model
in
a
lot
of
the
service
delivery,
managed
products
I'm
actually
going
to
just
pull
up
here.
The
documentation
which
I've
also
linked
in
the
chat
for
everybody
and
and
that
kind
of
talks
about
this,
but
I
also
found
this
great
blog
here.
A
So
the
external
Secrets
operator,
before
it
was
an
operator,
was
kubernetes
external
Secrets
right,
and
this
is
actually
the
engineering
blog
from
GoDaddy
in
2019
about
why
they
ended
up
developing
that,
and
so
here
we
are
now
what
like
more
than
three
years
later
and
it's
evolved
into
it's
an
operator,
and
it's
it's.
You
know
beyond
that,
but
I
really
liked,
and
they
talked
a
little
bit
about
kind
of
similar
themes.
A
B
A
A
So
yeah,
so
this
blog
that
they
posted
about
it
is
I
thought
it
was
really
good.
I
read
through
it,
and
obviously
we
know
like
this
is
this
is
out
of
date
their
examples.
Don't
real,
don't
really
work
anymore,
because
it's
probably
just
like
a
passing
issue
and
you
can
change
this
GoDaddy
here
to
kubernetes
and
maybe
it
would
work.
I
don't
actually
know,
but
because
this
is
now
I,
don't
know
if
it's
an
official
like
kubernetes
project
I,
think
it
is
it's
a
Linux
Foundation
product
yeah.
A
A
Perfect
now
we
know
was
it
this
one?
Yes,
flux,
CD,
okay,
I
didn't
get
anywhere
into
setting
this
up,
although
I
did
put
flux
on
our
cluster
in
case
I
got
there,
but
getting
back
to
get
Ops
right.
They
actually
have.
My
everything
is
cool.
That's
why
I'm
like
bundled
up
for
those
of
you
who
don't
know
my
office
is
in
a
basement
and
it's
an
ice
box.
A
A
I
might
have
mentioned
that
I'm
a
baby
and
I
like
to
whine
still
true
so
anyway
right,
so
they
actually
talk
through
in
their
documentation,
combining
the
two
things
with
flexity
rather
and
the
external
Secrets
operator,
using
the
helm,
installation
method
and
customize
and
so
forth
and,
like
I,
said,
I
didn't
even
get
here,
I
tried.
I
really
did
you
know?
A
It's
probably
a
great
feature:
I
should
use
more
is
the
do
not
disturb
settings
on
my
laptop,
so
that
slack
doesn't
interrupt
me,
but
that's
that's
what
happened
to
my
attempts
at
setting
up
this
demo
in
terms
of
time
time
management
right
so
anyway,
future
reading
I
will
link
it
in
the
in
the
language
is
failing
me,
everything's
shutting
down.
Cordova
is
occurring,
chat
in
the
chat
and.
A
A
Right
so
they
actually
have
all
of
these
other
Integrations,
though
I
almost
set
up
a
one
password
account
just
for
this,
and
then
I
was
like
no,
because
I
do
have
a
one
password
account
I'm,
very
tempted
to
try
this
on
my
own,
but
I
don't
feel
like
I,
don't
feel
like
managing
making
sure
you
all
don't
see
like
the
keys
or
anything
that
we
required
to
set
it
up.
So.
B
What's
what's
really
cool
is
that
it
provides
like
it's
because
it
kind
of
like
was
mentioning
before
is
it
provides
it's
kind
of
an
abstraction
right?
It's
like
it
doesn't
actually
do
anything
with
Secrets
other
than
like
know
how
to
talk
to
these
different
back
ends.
So
if,
if
you're
in
a
multi-tenant
system,
it's
very
it's
very
I,
think
that
is
when
it's
very
powerful,
because
it's
like
it
happens,
you
know
different
teams
use
different
methods
to
store
their
secrets.
A
I
had
read
this
last
night
remembered
it
was
in
the
docks
somewhere.
So
while
you
were
talking
I'm
like
clicking
around
like
they
have
that
they
talk
about,
the
docs
are
actually
quite
thorough
in
terms
of
example,
so
like
decoding
strategies,
multi-tenancy
multiple
Secrets
templating,
so
that
was
I.
There's
a
lot
in
here.
There's
a
lot
in
here
to
go
through
and
and
get
the
thing
in
somewhere
I
forget,
which
page
it
was
one
of
their
Pages.
They
were
saying,
testing
wanted
so
yeah.
B
A
A
A
A
A
B
B
B
A
B
A
A
Oh
yeah,
I
I
think
I
spent
I'm
I'm
I'm
I'm
what
they
call
leadership,
which
means
that
I
spend
all
of
my
job
in
Google
Slides.
This
point
and
jira,
that's
like
99
of
what
I
do
is
is
Google
Docs,
Google,
slides
and
jira.
So
it's
like
I'm,
like
oh
I'm,
getting
rusty
here,
I
gotta,
I
gotta
do
something
about
that
so
anyway,
so
I
followed
the
we're
gonna
go
back
to
the
thing
I
was
following
so
that
I
have
it
handy.
A
That
was
not
it
really.
If
I
could
remember
where
things
were,
my
life
would
be
better.
We're
just
gonna,
search
fake
at
this
point,
I'm
not
trying
to
navigate
these
Docs
there
we
go
not
not
to
say
the
dogs
are
fantastic
I,
just
not
trying
to
remember
where
I
found
the
things
right.
So
this
was
the
guy
that
I
was
following.
Basically,
it
is,
it's
create
a
Secret
store,
create
a
secret
reference
and
then
it
should
actually
make
the
thing
right.
A
So
I've
got
the
external
secret
here,
which
I
made
two
copies
of
it
in
case
there
was
something
I
had
done
and
I
actually
did
put
it
in
the
flux,
flux,
namespace
and
then
have
the
Secret
store,
which
I
could
have
also
like
literally
right
before
this
call
I
put
one
in
the
flux,
namespace
I,
don't
know
why
it's
not
there,
we'll
just
edit
it.
Maybe
that's
my
problem
anyway.
A
B
A
B
A
A
B
Okay,
like
on
a
on
a
tangent
like
I
I've,
been
using
a
co-pilot
with
a
GitHub
co-pilot
right
and
it's
like
sometimes,
and
it
kind
of
messes,
with
my
autocomplete
like
vs
codes
autocomplete,
because,
like
I
like,
like
most
people,
rely
on
the
autocomplete
like
I'll,
just
like
tab,
my
way
through
something
but
like,
but
then
copilot
like
recommends
something
and
then
I
tab
it.
And
it's
like
the
wrong
thing
like
no
I
didn't
want
that.
Stop!
Helping
me
stop
helping
me.
A
I
turned
off
all
of
the
going
editions.
I
think
I
talked
to
you
about
this
because
it
kept
breaking
my
workflow,
because
you
know
I'm,
I'm
old
enough
to
be
of
that
generation
of
I
lost
my
progress
on
a
word
doc,
one
time
because
I
didn't
save
it
every
five
seconds
and
now
I
habitually
save
anything
every
five
seconds
right.
So
I,
you
know
brand
new
brand
new
file.
A
So
basically,
according
to
their
guide
here,
getting
you
know
back
on
track
according
to
their
guide.
Here
you,
you
put
these
two
things
together
and
it
should
give
you
the
secret,
and
that
is
where
it
wasn't
working
for
me
or
it
wasn't
appearing
to
work.
For
me,
what
am
I
looking
for
I'm
looking
for
workloads
secrets,
flux
system,
yes,
so
it's
not
there
and
I
feel
like.
A
A
That's
where
that
lives
and
I
tried
this
a
few
times.
That's
why
it's
this
like
five
different
places
where
the
name
the
names
exist,
so
the
next
thing
I
wanted
to
do,
because
when
I
don't
know
what
I
did
wrong,
the
obvious
solution
is
to
check
logs.
The
next
I
need
to
do
is
actually
look
at
the
operator.
B
A
A
A
B
B
A
A
B
A
A
B
A
A
A
A
B
A
A
A
Let's
actually
go
back
to
those
things
right,
so
it
creates
those
installed
operators
right,
the
crd
is
what
we
needed,
so
you
have
to
create-
and
these
are
like
cluster
scoped
right,
because
I
made
this
a
cluster,
you
can
have
a
cluster
scope,
so
you
can
have
cluster
Secrets
or
these
are
namespace
or
project
scoped
secrets
right.
So.
A
You
have
no
idea
how
bad
it
is
right
now
anyway.
So
yeah,
though
the
security
compliance
is
just
hours
and
hours
of
time
and
then
I
have
additional
security
compliance
considerations,
I'm
worried
about
for
like
day-to-day
stuff,
too.
Here's
the
thing
right
and
if
you've
heard
me
talk
ever
I
stole
this
phrase
from
somebody
else
and
I
use
it
all
the
time
most
amount
of
actions
least
amount
of
access.
A
So
you
don't
want
people
to
be
able
to
necessarily
see
Secrets,
but
you
need
them
to
be
able
to
reference
secrets
in
their
own,
like
having
an
application,
expect
certain
secrets
and
have
this
ship
those
secrets
to
that
application,
but
they
don't
need
if
it's,
even
if
it's
a
cluster
secret,
they
don't
need
to
actually
have
access
themselves
to
the
cluster
secrets
to
get
what
they
need.
They
just
need
to
be
able
to
know
the
reference,
and
then
this
takes
care
of
that
access
level.
A
So
when
you're
in
when
I
was
installing
this
operator,
I
actually
had
the
option
to
install
it
at
a
cluster
scope
or
add
a
name
space
scope
and
so
I
decided
to
install
it
the
cluster
stroke
because
yeah,
it's
awesome
but
yeah.
So
the
fact
that
there's
both
I
love
that
it's
so
nice
it
just
keeps
keeps
the
role-based
access
clean,
gives
people
what
they
need
without
giving
them
things.
They
don't
need
anyway.
So
this
is
what
the
Secret
store
was
right.
So
this
this
is
the.
B
A
There
we
go
Secret
store
right
resource,
separate
conservative
authentication,
access
to
the
actual
secret
configuration
needed
for
workloads.
The
external
secret
specifies
what
to
fetch.
The
Secret
store
specifies
how
to
access,
and
so
this
resource
is
namespace
right.
So
it's
a
secret
store.
There's
the
external
Secret
cluster
Secret
store
Global
cluster-wide
Secret
store
that
can
be
referenced
from
all
namespaces.
You
can
use
it
to
provide
a
centralized
gateway
to
your
secret
provider.
A
B
Yeah,
and
especially
like
since,
like
in
your
world
right
where
it's
like,
like
security
at
least
previously
right
like
like
doing
this
managed
Services,
this
is
kind
of,
like
you
know,
breath
fresh
air
kind
of
like
or
mixed
like
yes.
Finally,
someone
gets
like
it's
like
SRE
life
right
on
how
and
how
to
manage
this
at
scale
with
multi-tenants
right
like
because
you're
mad
yeah,
yeah
lots
of
stuff
yeah.
A
They
own
the
Clusters.
Now
we're
also
operating
software
for
customers
that
lives
on
red
hat
owned
clusters
and
there
are
tenants,
but
there's
also.
The
reverse
is
true,
where
we're
operating
software
that
lives
on
their
clusters,
and
they
may
have
tenants
within
that.
So
when
you're
doing
that
right,
you
want
to
basically
keep
all
of
the
considerations
completely
separate.
So
it's
almost
I'm
gonna
I'm
gonna
coin,
a
term
here,
it's
like
a
shadow
tendency
right,
interesting.
B
A
Need
to
be
able
to
extract
abstract
them
out
away
from
the
customer
themselves
so
that
we
can't
create
then,
like
an
injection
point
back
into
the
rest
of
the
systems
for
everybody
else
right.
So
these
types
of
practices
and
things
like
that
enable
I
mean
enable
multi-tenancy
and
enable
tenancy
in
ways
that
go
beyond
somewhat
traditional.
A
You
know
as
a
service
models,
so
I
love
stuff
like
this,
because
this
took
a
very
hard
problem
and
solved
it
like
very
eloquently
and
the
fact
that
the
fact
that
this
is
an
operator
right
so
like
you,
can
change
the
references
in
a
propagate
propagate
out
all
the
stuff,
so
you've
got
one
creates
that
one
source
of
Truth,
which
we
like
right
single
source
of
truth.
Yes,.
A
Love
that
right
I,
so
you
don't
have
to
you-
don't
have
a
bunch
of
cascading
changes.
You
can
have
a
single
source
of
Truth
and
because
it
sees
the
updates,
it
sees
the
changes
and
can
and
take
them
and
transform
them
live.
Then
everything
can
kind
of
work
together
and
that
nice
holistic
get
Ops
way.
B
And
it
removes
like
kind
of
like
the
need
for
me
like
as
an
end
user,
to
like
worry
about,
like
where
my
secrets
is
coming
from
right,
like
I
can
just
like
now
now
it's
like
now,
I'm
just
consuming
them
now,
I,
don't
care
like
where
that
the
security
and
all
that
stuff
is
being
handled
for
me
and
I'm
just
now
using
the
platform
right.
So
this
this
is
great.
A
The
business
case
right
the
business
case
for
this
I
think
it
has
there's
a
lot
of
layers
of
business
cases
for
stuff
like
this
in
in
both
like
that
kind
of
that
managed
multi-tenancy
situation
that
we're
talking
about
General
multi-tenancy
situations,
but
also
just
separating
out
developments
and
developers
from
Ops
right,
letting
letting
devops
handle
those
pieces
and
just
giving
developers.
Here's
what
you
need
to
know
and
we've
put
in
a
source
of
Truth
for
you
to
know
it
right
that
not
having
to
spend
the
mental
Cycles
as
a
developer
on
that
of
oh
I.
A
Just
need
to
pull
these
references
from
this
repo
and
I'll.
Have
the
things
I
need
to
get
access
to
these
dependencies
right
and
then
you
don't
have
to
worry
about.
Do
things
expire?
What,
if
the
secret,
what
if
the
secrets
did
get
leaked
and
they
all
need
to
be
updated
right?
It's
all
handled
for
you
through
this
model
and
the
fact
that
there's
an
operator
in
to
kind
of
pick
up
all
the
changes
and
propagate
them
out
and
you're.
A
Just
looking
at
references
and
as
long
as
the
last
step
of
what's
being
referenced
is
updated,
then
it
all
percolates
back
out
so
like
that
is
very,
very
nice
from
an
Ops
factor
of
I.
Don't
have
to
go
through
a
forensic
review
of
everything
that
needs
to
be
changed.
It's
very,
very
nice
from
a
development
factor
of
I.
B
The
what's
what's
really
cool
like
I'm,
always
thinking
about
like
man
like
I
wish
I
had
this
before,
like
it
like
things
like
like
a
password
rotation,
actually
becomes
like
a
something
that,
like
an
end
user,
doubt
further
down
the
line,
doesn't
like
a
developer
or
like
like
an
SRE
or
devops.
Whatever
doesn't
have
to
worry
about
like
the
credential
rotations,
because
they
they
just
have
the
reference
as
long
as
the
red,
whatever
the
reference
is
pointing
to
they
don't
care
right,
it's
kind.
A
B
Now,
I'm
kind
of
talking
more
about,
like
you
know,
like
I'm
I'm,
just
kind
of
remembering
back
where
we
used
to
work
together,
like
just
imagine
like
me,
trying
to
change
the
password
to
the
database
and,
like
all
the
things
we
had
to
touch
in
order
for
that
to
happen.
Like
that's.
That's
like
that's
a
headache
whereas,
like
in
this
model,
it's
it's
kind
of
cool,
because
I
can
do
that
right,
like
as
an
admin
like
I,
can
go
rotate.
B
The
password
update
the
secret
management
system
and,
like
everything,
should
just
work
right
because
you're
just
you're,
referencing,
you're
referencing,
the
secret,
you
don't
have
to
you,
know,
make
any
changes
in
your
application
right.
Yeah
you
make
zero
change
your
application,
which
is
always
great,
especially
when
you're
doing
something
like
you
know,
rotating
passwords
right.
It
makes
those
kind
of
things
effortless,
yeah,.
A
A
A
B
B
A
A
A
No
I
did
it
to
both.
Well,
it
still
worked.
It
would
still
work
because
an
external
secret,
even
if
it's
namespace
scope,
should
be
able
to
reference
the
cluster
secret,
so
it
doesn't
actually
matter.
But
yes,
when
copy
pasting
do
try
to
make
sure
that
you
actually
map
the
things
correctly,
yeah
right.
Okay,
so
that's
the
name.
What
am
I
looking
at
key
fobar.
B
B
A
B
A
A
B
A
B
Would
yeah
because
so
then
like
it
just
it
just
depends
right
and
that
and
then
just
I'm,
just
like
I
guess
the
the
my
point
being.
Is
that
that's
just
something
you
need
to
keep
in
mind
right
like
just
that
that
you
know
the
the
change
from
like
when
you
change
it
to
how
when
it
when
it
appears,
because
it
looks
like
it
does
appear
when
you
change
it
Upstream,
it
does
appear
Downstream
but
like
it
does
take
time
right
and
so
I.
You
know
just
kind
of
keep
that
in
mind.
B
A
A
B
A
A
Yeah,
usually
I,
guess
it
depends.
Some
operators
I
believe,
do
let
you
inside
a
loop,
frequent
frequent
and
the
reconcile
Loop
is
for
those
who
don't
know.
That's
that
process
in
the
operator
where
it
goes,
and
it
says
here
are
all
the
things
I'm
expecting
to
be
true
and
it
will
go
check
each
individual
one
of
those
things
and
make
sure
that
they
are
true.
If
the
thing
is
not
true,
it
will
make
it
true.
Yes
right.
A
B
B
Do
all
the
things
I
think
I
think
you
once
I
think
during
a
talk,
I
think
you
once
made
a
great
analogy,
since
you
have
young
kids
about
Are,
We,
There,
Yet,
sort
of
thing
it's
like.
Are
you
there
yet
are
we
there
yet?
Are
we
there
yet?
And
this
Are
We
There
Yet
the
time
between?
Are
we
there?
Yet
that's
the
reconcile
Loop
right
now
between
one
Are
We,
There,
Yet
versus
the
other.
That's
your
reconcile
loop,
I,
I
know
for
art,
so
I
know
for
Argo
CD.
B
The
default
time
is
three
minutes,
but
that
can
be
adjusted
so
you
can
like
for
Argo
CD.
You
can
say
you
know.
Instead
of
checking
every
three
minutes,
please
check
every
five
seconds.
This
thing's
true
for
flux,
right
flux
does
the
same
thing
so,
but
that
has
to
be
written
in
like
to
your
point.
Hillary
is
like
that
has
to
be
written
in.
So
that's
what
we're
unsure
about
is
like,
if
that's,
if,
if
it's
short
and
if
it's
short
and
configurable,
that
would
be
cool.
A
B
B
A
A
A
B
A
B
A
A
A
A
B
A
B
A
B
A
A
B
A
B
A
Have
this
computer
back
here
yeah,
it's
my
friend's
computer.
They
asked
me
to
pull
the
stuff
down
off
the
hard
drive,
so
they
could
get
rid
of
the
computer
and
then
they
were
going
to
come
pick
it
up
and
they're.
Like
just
kidding.
We
moved,
we
don't
have
space
for
it.
You
can
just
have
that
thanks
for
the
hard
drive
copy
and
I
was
like.
Nothing
is
a
beast.
Do
you
see
yeah.
A
A
Then
I
don't
need
a
space
heater
exactly
so
maybe
maybe
I'll
slide
it
under
my
desk
and
plug
it
in
and
and
have
to
re.
It
is
an
old
Apple
old
enough
that
I
should
be
able
to
get
Linux
on
it,
although
it
would
definitely
be
a
little
bit
of
a
hack
job
because
they
don't
like
that,
but
yeah,
it's
a
very
powerful
machine.
Even
you
know,
even
today,
for
being
several
years
old.
So
we'll
see
I'll
update
on
that
ask
me
if
I
actually
do
anything
along
those
lines
over
the
break.
A
So
when
we
come
back
starting
off
January,
we
are
kicking
off
the
year
with
managing
your
migrations
with
Git
Ops
and
specifically
talking
about
conveyor
and
we're
going
to
be
joined
by
one
of
the
one
of
my
friends,
Cloud
success,
architect,
God
I,
hope,
that's
the
correct
job
title
Christopher,
Newland,
so
he'll
be
joining
us
he's.
Also
a
red
Hatter
and
he'll
be
going
over
some
of
the
use
cases
in
ways
that
he's
actually
done
these
migrations
for
customers
and
made
them
happy.
A
So
that
is
I
know
that
was
requested,
specifically
Walid,
actually
I
think
had
asked
for
conveyor.
So
Aston
answered
we'll
kick
off
the
new
year
with
that
and
then
I
think
we'll
continue
on
some
of
that
Trend
coming
in
through
the
the
rest
of
that
of
that
quarter,
and
then
I
have
no
idea
what
we're
doing
past
that
point,
but
we'll
figure
it
out
as
we
go.
A
B
Yeah,
it's
been,
it's
been
great.
Thank
you
all
for
joining
it's!
It's
thank
you
for
taking
the
ride
and
his
Guide
to
the
Galaxy
right
on
this
on
the
ship
that
we
call
devops
and
so
yeah
I'm
excited
I'm
excited
for
2023..
I'm
excited
to
be
off
to
be
honest
with
you
for
for
an
extended,
because
I
I
took
some
PTO
around
Red
Hat
shut
down,
and
so
I
have
an
extended.