►
From YouTube: GitOps Happy Hour (Ep 8): Managing MachineSets
Description
Join Christian Hernandez, GitOps Extraordinaire, for a journey through how to achieve GitOps in any number of ways. The occasional Red Hatters and special guest will join us too.
A
Good
morning
good
afternoon
good
evening
and
welcome
to
another
edition
of
the
get
ops
happy
hour
with
myself,
chris
short
executive
producer
of
this
thing,
we
call
open
shift
tv
and
the
one
and
only
christian
hernandez,
get
out
extraordinaire
christian
we're
talking
about
managing
machine
sets
today.
B
Yeah
yeah
so
well,
someone
said
good
morning
so.
A
B
Span
across
across
the
globe
here,
yeah,
so
yeah,
so
we're
talking
about
machine
sets
and
auto
scaling.
Actually
in
a
in
a
get
ops
world
right,
so
I've
I
try
to
prepare,
I
I
was
telling
chris,
you
know
right
before
we
started.
I
try
to
prepare
some
slides,
but
you
know
work.
You
know
my
day-to-day
day-to-day
gets
in
gets
involved.
Actually
a
lot
of
people
don't
know
that,
like
this
isn't
considered
like
the
streams
we're
doing
isn't
considered
your
day
to
day
right.
So
so
I
was
like.
B
Yeah
yeah,
so
it's
so
I
got.
I
got
a
little
sidetracked,
so
I'm.
A
B
Be
doing
an
andrew
sullivan,
so
if
you
guys
haven't
never
checked
out,
andrew's
show
openshift
for
administrators
office
hours.
I
believe
it's
called
where
he
when
he
talks
about
a
topic
he
usually
just
goes
through
the
openshift
documentation,
which
makes
total.
B
Makes
total
sense
yeah,
so
I
think
I'm
gonna
do
that
and
you
know
a
lot
of
times
we
catch
things.
I
know
eric
eric
jacobs
when
he
goes
through
the
docks
he
finds
bugs
and
he
just
files
them
as
he
finds
them
yep.
So
maybe
we'll
find
some
of
those
today
here.
So
all
right.
So
because
you
know
first
and
foremost,
I
guess
you
know
talking
about
air,
putting
everything
in
a
git
repo
right
get
ups
world
where.
B
Gonna
get
repo
if
it's
not
gonna
get
repo,
then
you're
not
doing
get
ups
sort
of
you
know
drawing
that
hard
line
right
so-
and
I
talked
a
little
bit
about
this
when
we
talked
about
operators
using
operators
in
github,
and
I
should
actually.
B
B
Yeah,
so
I
think
I
think
I'll
put
that
put
that
as
yeah.
B
Of
a
test
I'll
tell
you
that
yeah,
so
by
the
way,
if
you
guys
don't
know,
that's
you
have
to
take
five
tests
on
on
top
of
the
rhce,
so
it's
so.
A
B
I
need
new
business
cards
and
now
I
have
a
something
else
to
put
on
on
the
business.
A
Card,
so
I
would,
I
would
feel
disrespected
if
you
didn't
put
get
ops
extraordinary.
B
Yeah
yeah
yeah,
so
now
I
have
to
do
it
right
right,
so
yeah.
So
so
you
know
back
to
the
that's
what
I
was
talking
about
about
the
operators
right,
you're,
wearing
an
operator
shirt
actually.
B
It's
all
so
I
actually
joked
that
chris
shart's
closet
is
just
nothing
but
swag
t-shirts
that
he's
gotten
through
throughout
all
the.
A
C
A
Newsletter
but
I
never
ended
up
doing
anything
with
it.
B
B
A
B
A
B
B
C
B
Yeah
so
yeah.
So
if
you
remember
in
the
previous
episode,
we
talked
about
operators
right
and
how
operators
is
the
the
automation
core
of
openshift
four
right
and
how
do
you
kind
of
get
ups,
the
the
the
the
operator
right
like
so,
if,
like
you
know,
automation
everywhere
and
oh
what
shari's
on
yeah.
B
Yeah
welcome
back
if
you
could
drop
the
also
chris
if
you
drop
the
the
bang
link
of
the
the
playlist
right.
So
if
you've
missed
past
episodes
of
the
happy
hour,
yeah
we'll
drop
those
in
the
link.
I
talked
about
operators
and
this
is
kind
of
the
the
same
idea
with
machine
sets
and
machine,
auto
scalers
right.
So
what's
a
machine
set?
So
let's,
let's
do
a
andrew
sullivan
here.
A
A
B
Yeah,
let's
yeah,
so
that's
you
know.
Basically
a
machine
set
is
a
set
of
machines,
as
chris
said,
and
I
went
to
the
official
docs
sorry
so
docs
openshift.com
and
I
kind
of
you
just
kind
of
navigate
to
machine
management
and
creating
machine
set.
I
use
aws
a
lot.
I
mean
it's
the
same
idea,
no
matter
what
which
one
you
go
to
gcp
azure
yeah.
B
Yeah
apis
talking
to
other
apis,
so,
and
so
so,
let's
talk
about
a
little
bit
of
the
machine
api
over
here
right.
So
the
machine
api
is
like
the
the
guy.
That's
doing
all
of
this
stuff
here,
the
the
the
controller
as
it
were
right,
so
the
custom
resource
definition.
So
we
have
something
called.
Let
me
make
this
a
little
bigger
for
those.
Oh.
B
And
so
so
we
have
two
primary
resources
right,
so
we
have
something:
that's
called
a
machine
right.
So
a
machine
is
a
definition
that
describes
a
node
right
or
a
host.
B
It
is
right
and
actually
andrew
did
a
did.
A
stream
about
machine
sets
a
machine
api.
He
goes
really
really
in-depth
into
it.
I
recommend
you,
you
guys
watch
that
as
well,
but
a
machine
is
a
a
description
right
of
of
what
an
instance
is
right.
So
we're
talking
about
things
like
a
machine
has
certain
characteristics
right
like
what
like
cpus,
like
four
cpus
ram,
16.
B
This
mini
disks
right,
so
it's
basically
a
description
of
of
what
a
machine
is
right
in
aws
land
right.
Those
are
these
the
node
types
right
so
like
you're,
talking
about
like
m4
extra
large
or
whatever.
B
Right,
like
that's
how
it
is
in
in
azure
it's
different
right
in
azure.
I
forget
how
they
define
theirs
in
gcp,
but
the
concept's
pretty
much.
The
same
is
a
a
definition
of
a
machine
right,
so
a
machine
set
kind
of
like
the
same
paradigm,
from
like
a
replication
controller
and
a
pod
same
idea.
Right
machine
set
is
kind
of
like
a
replication
controller,
but
for
machines
right.
So
it
describes
a
group
of
machines
right.
B
It
controls
the
scale
of
it
right
and,
and
it
controls
the
the
the
overall
health
of
it
right
so
kind
of
like
here.
It
actually
says
in
the
documentation
machine
sets
are
to
machines,
as
replica
sets
are
to
pods
right.
So
if
you
need
more
machines,
you
just
scale
the
machine
set
right
or
kind
of
like
a
replication
controller.
Where,
where
you
have
you
say,
I
want
four
pods
you,
don't
you
don't
modify
the
pod
definition.
You
modify
the
replication
controller
right.
B
You
know
that
was
back
in
the
day.
Actually
you,
you
modify
the
deployment
which
then
deploys
a
new
replica
set,
and
you
know
yada
yada,
but
like
conceptually,
you
can
see
that
you
know
you.
You
change
the
number
of
replicas
right
and
if
a
machine
goes
away,
the
idea
is
a
machine
set.
Will
then
re-uh
redeploy
that
that
machine
right?
So
it's
kind
of
it
controls
the
scale.
B
So
so,
once
a
machine
set
controls
the
machine
right,
it'll
instantiate,
a
machine
and
then
the
machine
will
then
bootstrap
a
node
right
and
then
it
becomes
a
node
right.
So
you
go
from
machine
set
to
machines
to
node.
So
that's
kind
of
like
the
difference
between
a
lot
of
people,
get
understand.
Machine
sets
and
they
don't
understand.
Like
the
relationship
between
machine
and
a
node,
I'm
like
well
aren't
they
the
same
thing.
I
was
like
no
a
machine.
A
B
Machine
is
a
definition
of
a
node
like
a
hardware
right.
A
node
is
actually
has
a
red
hat,
coreos
installed
on
it
with
the
kubelet
running
and
it's
joined
to
the
cluster.
So
they're,
like
your
machine,
is
basically
a
blank
vm
and
a
node.
Is
that
vm
that's
running
part
of
the
cluster
right,
so
it's
kind
of
like
the
the
difference.
Is
there
so
and
so
there's
a
lively
chat
going
on
about
the
the
domain.
B
Yeah
yeah
so
yeah
well,
I've
been
kind
of
following
you
know.
I
guess
it's
like
it's
a
good
lively
chat.
So
so,
and
then
we
have
the
concept
of
a
machine
auto
scaler
right,
so
the
machine
auto
scaler
identifies
actually
sorry.
It's
connected
to
a
machine
right,
so
you're
saying
that
you
know
for
us.
B
Take,
for
example,
aws
us
west
one
right
or
like
one
us,
a
right
or
or
whatever
right,
like
you're
you're,
identifying
that
specific
zone
right
within
the
region-
and
I
say
I
want
you
to
keep
this
at
x
scale
and
you
have
to
do
that
for
each
availability
zone
that
you
have
and
then
you
use
the
cluster
auto
scaler
in
conjunction
with
the
machine,
auto
scaler
right.
So
you.
C
B
Machine
auto
scaler
defined,
saying
you
know
when
you
reach
x,
amount
of
you
utilization,
then
spin
up
another
machine.
The
cluster
auto
scaler
use
that,
in
conjunction
with
saying
okay,
like
my
cluster
as
a
whole,
I
want
I
want
to
make
sure
you
know
no
more
than
80
utilized
right.
So
it
takes
kind
of
like
an
aggregate
of
all
your
machines
and
uses
the
machine
auto
scaler
to
to
to
scale
that
right
so,
and
so
the
machine
health
check
is
exactly
what
what
you,
what
you
think
it
is
right.
B
It
detects
when
the
machine
is
unhealthy
and
deletes
it
right
and
then
creates
a
new
one
right.
So
this
is
the
idea-
and
this
is
where
kind
of
people
get
tripped
up
with
your
with
your
journey
like
with
just
in
general,
from
your
journey
from
to
cloud
native
right,
because
that's
like
a
journey
in
itself
and
then
from
cloud
native
to
get
ops,
it's
like
a
whole
nother,
you
know
journey
is
like
a
lot
of
people
treat
their
machines
as
pets
right
yeah,
instead
of
cattle.
B
So
this
is
the
idea
of
just
treating
your
your
servers
as
as
cattle.
Essentially
right,
like
you,
you
you
want
it
to
be
a
commodity,
you
want
it,
you
know
the
important
thing
is
the
application,
not
not
the
machine,
so
you
kind
of
have
to
get
that
paradigm
shift
of
like
well
you're.
Deleting
machines
is
like
yeah
yeah
like
it
shouldn't
matter.
B
You
know.
That's,
that's
your
your
journey
to
to
cloud
native
is
that.
A
A
B
Yeah
yeah
exactly
exactly
and
so
yeah
you're
pushing
the
you
know
you
keep
pushing
the.
What
do
you
call
it?
The
pets?
Sorry.
A
C
B
B
A
B
Itself,
yeah
yeah,
so
I
come
from
an
operations
background
so
like
I
I
always,
but
I'm
like
one
of
those
like
rogue
operator,
guys.
That's
like.
C
B
You
should
I
should
be
able
to
delete
it,
so
I
had
my
you
know.
I
always
do
dollar
sign
last
job
in
my
last
job,
my
ex-boss,
he
would
say
I
I
should
be
able
to
pull
this
machine
out
of
the
wall
sock
and
throw
it
out
the
window
and
you
shouldn't
care
right
yeah.
So
it's
yeah
same
idea,
right
like
I
should.
I
should
be
able
to
go
into
aws
console
delete
that
instance
and
you
shouldn't
care
that
I
did
that.
B
That's
the
idea
right
so
and
that's
the
idea
about
this,
this
kind
of
automation.
B
My
thought
here
is
that
that's
this
is
a
point
of
automation.
Right
and
get.
Ups
is
a
point
of
automation
as
well
right.
You
know
like
where,
where
is
where's,
where
do
you
control
these
things
right
so
kind
of
similar
to
the?
What
do
you
call
it
the
operator
right
so
the
operator
stream
that
we
did
it's
like,
especially
it's
it's.
Basically,
it's
like
where's,
your
point
of
demarcation.
B
Do
I
put
my
machine
sets.
Do
I
put
my
machines
to
put
my
auto
scaler
and
get
like
where,
where
should
I
release
that
control
of
automation
right?
So
I
think
I
came
up
with
I've
been
playing
around
with
it
again
kind
of
like
the
operators.
There's
no
magic
bullet.
You
know
it
all
depends
what
you
want
to
do
and
what
works
for
you,
but
I
think
you
can
leverage
both
the
automation
from
the
operator
framework
in
openshift.
B
Alongside
with
get
ops
practices
right,
you
don't
it
doesn't
have
to
be
an
or
it
could
be
an
end,
so
I
do
have
so
usually
so
I
was
actually
telling
chris
yeah.
Usually
I
have
like
things
teed
up
right
today.
I
don't
so
you
guys
are
going
to
watch
a
lot
of
a
lot
of
things
paint
drying,
but
I
think
I
think
it'd
be
advan
advantageous
to
actually
see
what
I
go
through
in
order
to
set
something
up
right,
because
you
know
it's
a
lot
of
the
times.
B
A
B
My
beat.
B
Beat
my
head
here
to
my
cli
here,
so,
oh
by
the
way
I've
switched
speaking
of
derailing
right,
I
switched
from
using
power
line
to
pure
line.
I
don't
know
if
you
guys
seen
pure
light,
so
it
is
this
guy
called
chris
marsh.
He
kind
of
maintains
it.
Oh.
A
B
So
it's
using
bash,
so
it's
basically
cause
you
know.
Power
line
is
basically
your
shell
wrapped
in
python,
right
or
pearl.
I
forget
which,
which
one
of
the
two
right,
but
this
does
it
completely
in
bash
right.
So
it's
actually
pretty
easy.
You.
C
B
Overhead
of
running
a
daemon-
this
is
basically
it
but
anyways.
It
looks
the
same
right
and
it's
customizable,
so
anyways
nice
kind
of
little
geek
thing
that
I
use.
I
like
it.
So
if
you
do
an
oc
oc
status,
what
am
I
looking
for?
Oh
yeah,
so
I
am.
I
am
on
the
right
cluster
here.
Okay,.
A
A
B
Machine
set
so
machine
sets.
So
let's
look
at
the
the
machine
sets
actually
instead
of
doing
dash
a
let's.
Do
the
right
thing
right.
It's
in
the
machine
config
api.
So
you
see
here
that
I
have
a
definition
of
of
a
machine
one
in
each
availability
zone
right,
so
us
west,
2a
to
b
to
c
right.
B
So
this
machine
set
controls
a
scale.
As
you
see
here,
there's
one
desired
one
current
when
ready
and
then
for
this
cluster
there's
one
in
there's
a
machine
set
created
so
there's
an
one
automatically
created
for
each
availability
zone
available
to
you
yeah.
But
you
know:
it'll
set
the
scale
as
zero
right,
so
cool.
B
B
Yeah
or
likely
to
center
scale
that
up
yeah
yeah
machines
right.
So
if
I
do
oc
get
machines,
openshift
api,
so
this
here
to
a
corresponds
with
this
to
a
here
right
so
right
and
it
gives
you
the
status
right.
It
gives
you
the
type
right
here
again.
Remember
we're
saying
m5
large!
That's
like
the
type
it's
running
on
and
it's
running
in
this
region,
this
zone
right.
It's
been
up
for
four
hours
right,
so
I
installed
it
this
morning
because
that's
so
good
yeah.
B
So
like,
if
you
do
oc,
get
oc
scale,
machine
set
right,
let's
take
d
here
and
then
you
do
replicas.
You
want
one
right
like
I
wanna,
because
it
goes
at
zero
right
now.
So
let's
just
say
I
want
one
right
so
then,
now,
if
I
do
get
machine
sets
you'll
see
that
I
scaled
right.
B
B
Who
am
I,
where
am
I
right?
So
it's
yeah,
I
do
oc
yeah
oc
status
will.
B
Yeah,
so
I'm
like
okay,
I'm
using
this
cluster,
so
yeah
so
and
then
there's
oc
something
else
I
always
find
stuff.
And
then
I
oh
yeah
cluster
info,
right,
yeah
and
then
there's
cluster
info.
B
B
Right
so
so
yeah,
so
I
have
I'll
see
get
notes.
Maybe
maybe
the
nodes
are
oops
notice
up.
They
go
kubernetes
oops.
No,
it's
node
roll.
B
So
yeah,
so
so
one
way
to
kind
of
get
ups.
This
here
is
that
I
have
you
have
to
kind
of
do
what
kind
of
do
if
you
guys
have
looked
up
get
ups,
you
probably
see
a
lot
of
weave
works,
coming
up
kind
of
do
what
what
weworks
guys
recommend
is
just
basically
export
everything
and
import
everything
right.
So
if
you
do
oc
get
machine
sets
open
shift
machine,
api,
okay,
you
basically
take
these
and
export
them
yeah
and
put
them
in
get
so.
B
I
kind
of
did
this
with
my
old
cluster.
So
let's
look
at
my
machine
sets
here
and
let
me
look
at
my
overlay.
What
cluster
am
I
on
okay?
A
B
Okay,
that
way
you
can
yeah
okay,
so
so
that
way,
it'll
apply
because
it
argo
cd
does
doesn't
apply
right.
It
doesn't
do
a
create,
it
doesn't
apply,
so
so
it'll
apply
it.
But
if
there's
no
change,
then
it
you
know
it
goes
okay.
Then
it's
telling
me,
okay-
and
I
did
this
for.
B
A
B
B
Already
right,
yeah
yeah,
it's
like
it's,
not
interesting
enough!
Wow
interesting!
Well,
I
like,
I
can
actually
see
the
colors
better
like
when
I'm
looking
at
yaml
or
like
shell
or
something
oh.
B
Yeah,
so
so
yeah,
so
essentially
what
I
did
was
I
just
exported
all
of
these
right
so
and
I
control
the
machine
sets
there.
So,
let's,
what
would
be
the
easiest
way
thing
to
do
here?
I
can
do
this.
B
I
could
probably
do
it
through
vi
right.
So,
let's
let
me,
as
you
can
see,
I'm
working
on
like
300
things
at
once.
Here.
B
Yeah
so
so
I
leave
my
laptop
on,
so
I
can
log
into
it.
Oh
remotely.
B
A
Yeah,
I
I
only
turn
it
on
when
I'm
in
the
house.
If
I
know
I'm
gonna
be
like
working
on
that
machine,
yeah
or
someplace
else
in
the
house
or
outside
of
the
house
potentially
so,
like
all
of
my
machines
in
the
house
have
ssh
enabled
and
on
but
there's
an
ssh
gateway
that
I
use
and
it's
very
locked
down.
And
if
you
start
hammering
it,
it
will
ban
your
ass
for
life
kind
of
thing
and.
B
Oh,
I
got
you
gotcha
it'll
bend
your
ass
for
lime.
B
So
if
I
do
machine
machine
sets,
oops
machine
sets
and
then
I
am
on
overlays
cluster
two
right,
so
I
have
this
here.
So
let's
do
this
one
at
a
time
right.
So
I
have
so
let
me
move
so
which
one
this
one
is
a
right.
So
two
oops
east
one
a
to
this
guy
ammo
right.
So
I
do
that
guy
right.
So
then,
what
I'm
looking
for
is
to
change
this
d.
B
F,
seven
right
to
this
cluster
name
right,
so
I'm
gonna
look
for
this
cluster
name
here,
nice.
So
what
I
can
do
is
oh.
A
B
Right
not
found
because
oh.
B
Think
yeah
yeah,
yeah,
yeah
you're
right
search
for.
C
B
Look
for
that
guy
he's
there
and
then
the
other
thing
is
that
I'm
not
in
us
east
anymore,
us
east,
one
right,
I'm
not
a
u.s
east
one.
I.
B
C
A
B
And
so
so
that's
you
know
one.
The
cluster
name
rich
is
usually
your
cluster
name
dash
some
hash
right
and
then,
wherever
you
are,
is
you
you
know
in
in
the
region
right
and
the
rest
is
pretty
much
the
same
right.
One
thing
I
do
have
to
change
is:
I
do
have
to
make
sure
if
I
do
get
machine
sets.
B
If
I
get
a
2a
grade,
oh
yaml,
there's
other
things.
I
need
to
look
out
for
like
this.
Isn't
the
instance
type
right,
so
this
is
type
I'm
using
I'm
five
large
here.
So
I
have
to
make
sure
that
matches
right
instance
type
yeah.
So
I'm
using
that
and
then
one
last
thing
is
the
the
ami
right.
The
ami
id
is
different,
so
so
where's,
the
ami.
Why
am.
A
B
Region,
yeah
yeah,
am
I
shouldn't
it
be
the
same?
No,
it's
not
so,
and
the
rest
is
pretty
much
the
same
right.
If
you
guys
are
interested.
Let's
look
at
the
documentation
right
there
is.
I
basically
use
this
right.
The
and.
B
Yeah
in
in
the
chat
here,
I'm
using
just
basically
this
right
as
my
template
right,
because
it's
the
same
no
matter,
you
know
if
you
have,
you
know
one
or
ten
right.
So
so
that's
the
thing
here.
Oh,
let
me
make
sure
the
the
iops
things
are
correct
here.
So
let's
do
where
am
I
okay?
Where
am
I
say?
Oh.
B
We
go,
we
should
have
used
it
so
yeah.
So
that's
fine,
okay,
cool!
So
that's
one
right,
so
I
have
to
do
this
two
more
times
right
because
I
have.
I
have
two
more.
A
B
On
the
let's
see
here,
how
much
time
do
we
go.
C
B
B
So
as
I'm
doing
this,
if
there's
any
questions
feel
free
to
ask.
A
B
A
B
Let
me
see
here
this
graph
ami
I'm
using
this
ami.
B
And
then
I
am,
I
hope
I
do
mess
this
up,
because
you
know
it's
always
good
to
see
errors
sometimes.
A
B
There
we
go
m5,
large,
large
and
in
charge
and
then
that's
about
it
all
right
and
then
I'm
trying
to
think
here
last
one
so
cluster
two
two
to
see
here
we
go
to
see
or
not
to
see.
C
B
Too,
globally
and
then
it's
do
you
remember,
it's
m
something
right
in
five
large
yeah
origin
in
charge,
and
then
the
ami
is
different
from
what
I
understand.
B
Where
is
it
there?
It
is
cool
all
right
that
should
be
good
and
then
oh
yeah.
I
need
to
update
my
customize
file
customization
right,
because
I
don't
want
to
load
these
guys.
B
All
right
all
right
cool
and
then
the
customization
file
basically
also
reads:
base
right
and
base.
All
it
does
is
just
make
sure
the
api.
Is
there
right,
the
openshift
namespace
is
there.
You
don't
have
to
do
this
because
openshift
machine
api
is
like
a
protected
namespace.
However
comma,
for
the
sake
of
being
complete,
I
always
put
it
in
there.
It
does.
It
doesn't
hurt,
because
if
it's
already
there,
it
doesn't
do
anything
so
right.
B
Get
push
so
I
go
back
to
master.
B
I
had
an
interesting
error
earlier
with
argo.
Oh,
it
was
an
error.
It's
me
user
error,
I'm
so
used
to
typing
master
and
new
repos
are
now
main.
So
I'm
like,
why
isn't
this
working?
Why
isn't
this
working
I'm
like,
and
then
I
started
like
spelunking
through
the
logs
and
it's
like
master
doesn't
exist.
I
was
like
what,
like.
B
B
I
have
the
machine
that
right
so
essentially,
as
you
saw
the
the
paint
dry
essentially,
it's
the
only
difference
is
a
cluster
name
right
where,
where
you're
at
right
us,
you
know
I'm
in
us
two
region
right
and
then
the
instance
type
and
like
the
ami.
So
so
you
know
the
basic
things
that
would
be
different
right.
It's
you
know!
No!
No!
This
is
a
surprise.
B
A
B
So
yeah
so
there's
a
reason
for
this.
I
actually
can't
say
it
on
air
I'll
I'll.
Tell
you
later
chris,
why
I'm
doing
it
this
way.
C
C
B
So
so
so
yeah,
so
it's
it's
actually
I
can
you
know
I
can
what
I
can
do
machine
sets.
I
can
copy
it
right.
I
can
just
do.
B
A
B
Oh
well
right
see
for
open
pixel
there
we
go
there.
A
B
There,
it
is
all
right
all
happy
yeah,
I
could
do
a
git
revert.
B
And
so
now,
if
I
reload
this
page,
I
get
closer
three
right
so
now,
cluster
three
has
cluster.
Three
all
right,
sweet
all
is
well
in
the
world
right
and
which
is
what's
cool.
Is
that
the
customize
works
right?
I
use
the
same
base
for
all
three
of
them,
so
I
don't
even
have
to
change
the
base.
So
again,
if
you,
if
you
missed
any
past
episodes,
I
do
actually
do
go
over
customize
earlier.
A
B
Yeah
yeah,
and
so
so
there
we
go
so
now.
I'm
gonna
apply
this
to
this
cluster
right.
So,
if
I
do,
let
me
see
here
new
app
right
so
application
name.
What
do
we
call
this?
Let's
call
it
something:
it's
called
a
cluster
three
app
right,
so
let's
call
it
whatever
this
machine
is
here
actually
to
see
if
our
new,
a
new.
B
There
we
go,
we
got
four
years,
yeah
easy
as
that
right,
so
we'll
call
that
cluster
c
app
again
we're
putting
us
default
name
space
in
argo,
cd,
remember,
they're,
different
argo
cd
handles
its
own
projects
differently
than
you
know,
then
openshift
yeah
they
shift
as
well.
So
I'm
going
to
do
a
manual
sync
right
just
go
so
we
can
see.
What's
going
on
repository
url,
we'll
get
get
ops
examples
we'll
use
instead
of
cluster
two
we'll
do
cluster
three,
so
it
all
matches
nice
destination
clusters,
this
cluster.
B
What's
the
name?
What's
the
name
space
again,
it's.
B
B
Well
and
every
time
you
do
tab,
completion
like
it
literally
hits
the
api.
So
it
depends
on
how
fast
your
cluster
is.
So
you're
like
right,
bashing
the
tab,
so
this
namespace
is
the
namespace
within
the
cluster
right.
So
I'm
gonna
target
that.
So,
let's
do
the
create
here.
I'm
gonna,
just
spec
invalid,
enable
to
get
app
machine,
says
overlay.
Oh,
that
doesn't.
C
B
B
So
so
it's
so
then
it
actually
creates
this
here
and
if
I
do,
let's
just
run
a
watch
here.
So
let's
do
a
watch
of
that
right
and
let's
sync
it:
let's
see
what
happens
right.
Synchronize.
B
Synchronize
happens
quick
because
it's
already
there
right,
it
doesn't
have
to
change
anything,
nothing
changed
here.
My
machines
didn't
go
away
and
I
think
it
deleted
because
because
it
was
it's
like
for
like
right,
it's
the
same.
Essentially
I
exported
the
config
and
imported
it
and
make
now
I
can
handle
this
with
with
in
a
get
ops
fashion
right.
B
So
so,
actually
so
now
that
I
have
this
in
in
git
the
idea
being
that
if
a
user
right
wants
to
come
in
and
do
a
pr
right,
it
says
say
I
want
to
scale
this
guy
from
one
replicas
two
right.
I
can
actually
control
the
scale
with
git
now
right
so
now,
when
I,
when
I
sync
this
guy.
B
Just
notice
how
now
I
have
this
machine
set
now
has
modifies
two
machines
right
and
then
the
status
here
change
from
desired
two
to
current
to
two
right
and
then
that
will
actually,
if
I
do
go,
see
get
machines
now
I'll
have
a
new
one,
provisioning
right.
So
now
in
a
git
ops
fashion.
Now
I
can
control
the
scale
of
my
cluster.
If
I
delete
a
machine,
it
will
reconcile
that.
For
me.
I
have
also
the
way
a
developer
now
say:
like
a
developer
wants
to
scale
the
cluster.
B
Now
they
can
submit
a
pr
right,
so
now
they
can
submit
a
pr.
We
have
it
all
tracked
and
get
right.
I
can
connect.
You
know
you
can
have
hooks
into
whatever
service
now,
whatever
you
want,
but
the
idea
is
that
now
you
have
a
an
audible
track
of
like
developers
saying:
okay.
Well
then
you
know:
why
do
you
want
this
scaled?
Why
do
you
need
more
machines
right,
like
you.
B
Is
that
you
know
anyone
could
get
like
you
know?
If,
if,
if
you
know
the,
if
the
marketing
manager
is
gonna
run
a
a
campaign,
and
he
knows
that
we
need
to
scale
the
the
cluster,
he
can
go
and
do
a
pr
anyone.
B
The
idea,
and
so.
B
The
scale
right
I
want
to
scale
this
right.
I
want
to
be
preemptive
about
it,
so
actually
I'm
actually
hillary
braided
silver
is
actually
part
of
our
osd
team
right,
openshift
dedicated
I'm
actually
curious
to.
If
she
wants
to
chat
it
out
how
we
manage
this
in
osd
right
because
it'd
be
interesting,
how
they
manage
machine
sets.
So
if,
if.
A
B
Yeah,
so
I'm
going
to
go
through
it
very
briefly,
because
that
is
a
topic
subject.
A
B
One
is
a
deep
subject
and
two
it's
a
topic
for
that.
I
have
in
line,
so
I
am
going
to
do
a
stream
about
machine
sets.
Oh
sorry,
machine
configs,
so
when
so
this
here
you
see
this
is
is
is
starting
provisioning
right
so
that
provisioning
step
it
actually
do.
If
I
do
oc
get
machine,
config,
configs
right,
it
actually
takes
this
machine
config
and
passes
it
through
ignition
right.
So
what
is
what
is
ignition
right?
B
Ignition
is
a
way
to
set
up
your
server
or
set
up
red
hat
core
os
before
pid
one
runs
right
and
it
runs
in
ram
fs
and
I'll
I'll.
Explain
all
that
in
in
another
stream,
but
the
the
idea
is
it's
like.
How
do
I
run
cloud
init,
but
only
once
right.
B
That's
a
big
difference
between
cloud
init
versus
ignition
is
ignition
runs
once
cloud
and
it
runs
every
time
the
machine
is
booted
right,
but
the
idea
is
is
like
it
has
things
like
things
like
ssh
configuration,
kublet
configuration,
container,
runtime
configuration
right
and
all
that
gets
glommed
together
into
what
we
call
a
rendered
worker
right
or
rendered
master
right.
B
So
if
I
do
oc
get
machine,
configs
rendered
worker
right,
oops
dash,
oh
animal
right,
it's
essentially
a
dump
of
configuration
things
that
you
would
want
to
see
right,
like
there's
a
c
system
d
units
here,
there's
like
username
passwords
right.
If
I
do,
if
I
get
the
the
ssh
one,
is
here
dash:
oh
yaml,
it's
basically
you're
setting
up
authorized
keys
right.
B
So
I'm
going
to
I'm
going
to
go
over
this
more
in
detail,
but
essentially,
when
you
bring
up
a
machine,
a
machine
config
is
how
is
how
the
machine
gets
configured.
Hence
the
name
machine
config
and
it
has
all
kinds
of
stuff
and
it's
based
on
ignition
right.
So
you
know
I
can
do
a
whole
hour
of
just
this,
which
is
why
I'm
gonna
reserve
it
the
rest
of
this
for
for
another
episode,
because
you
know
we
have
a
few
10
minutes
left
here.
B
So
one
last
thing
I
want
to
talk
about
is
it
so?
This
is
one
way
to
managing
it
right
right.
Another
way
of
managing
this
is
actually
setting
up
machine,
auto
scalers
right.
So
if
I
do
so,
let's
go
to
my
repo
here
is
I
have
a
machine,
auto
scaler,
so
let's
go
over
here,
overlays
cluster
two.
I
will
edit
this
to
cluster
three
right,
so
I
have
an
auto
scaler
setup
right
so
like
this
is.
B
This
is
an
example
of
auto
scale
right,
so
I
wanna
say:
I'm
gonna
target
this
machine
set
and
I
want
minimum
of
one
replicas
and
a
maximum
of
three
replicas
right.
So
what
is
that
so?
That's
kind
of
like
the
lower
end
and
higher
end
right
and
this
will
it
won't,
go
lower
than
one,
but
it
won't
go
more
than
three
right.
B
So
that's
and
you
know
I
kind
of
have
the
similar
configuration
for
each
one
of
the
machine
sets,
but
what
you
do
need
to
you
need
to
map
a
machine,
an
auto
scaler
to
this
right
so
because
it
won't
work
without
an
auto
scaler
definition
right.
B
So
I
want
to
say
I
want
a
max
total
of
nine
nodes
right
and
that's
what
my
auto
scaler
does,
and
these
are
kind
of
some
of
the
things
that
you
can
set
up
right
like
delayed
after
ad
rich
means
like
how
long
to
wait
after
you
add
it
for
it
to
trigger
another
one
right
delayed
after
they
have
to
delete
how
long
to
wait.
B
You
know
after
you
delete
it
to
trigger
another
one
right,
so
you
can
kind
of,
and
you
can
find
these
in
the
in
the
dock
right.
So
let
me
put
the
dock
here:
auto
scaling.
B
Yeah
there
we
go
nice.
Thank
you
so
yeah.
So
it's
just
info
about
the
the
machine
auto
scaler
right,
so
you
can
target
things
like
not
even
just
total
nodes
you
can
do.
I
want
minimum
number
of
cores
right,
so
you
can,
you
know,
play
around
with
this,
as
as
you
need
to
right
so
so
I
basically
target
the
auto
scaler.
B
The
auto
scaler
sets
up
like
okay,
what
I
want
to
auto
scale
and
then
in
the
machine
auto
scale
actually
schedules
the
machine
set
right.
So,
let's,
let's
go
to
where
am
I
here
there
we
go?
Oh
see.
Where
am
I
machine,
auto
scaler
right?
So
let's
go
to
the
base.
First,
openshift
machine
api.
That's
still
the
same
cluster,
auto
scaler!
That's
the
same,
doesn't
matter!
This
is
generic
enough
to
where
it
doesn't
matter
where,
where
you
have
it
here
so
but
my
overlays
right.
B
And
this
is
basically
the
same
thing:
east
one,
a
two
which
is
this
called
here:
oc
get
mush
machine
sets.
B
Let's
call
this
us
west.
B
B
And
then
we're
gonna
target.
What
are
we
gonna
target
we're
going
to
target
this
guy
here,
all
right,
all
right
and
then,
for
the
sake
of
time,
I'm
not
going
to
do
the
other
ones.
So
let's
remove
these
guys,
but
I
do
need
to
update.
B
A
B
Get
paul
ff.
C
B
A
A
B
Get
so
here
so
here
I
have
this
auto
scaler
up
so
here
I
can
add
this.
So
if
I
go,
let's
do
oc
get
machine,
autos,
scaler
right,
it's
not
there
yeah!
So,
let's
add
this.
Application
name
is
autoscaler
app
project
defaults
to
the
normal,
no
more
normal
things
here,
get
ops
examples
actually
auto
skiller
overlays
cluster,
three,
that
guy
and
then
I
forget
what
name
space
this
guy
here.
B
B
And
so
there
we
go
so
it
creates
the
the
auto
scaler
right.
I
go
here
yeah,
so
it
creates
auto
scaler
for
me,
and
so
you
can
control
it
that
way
as
well
right,
so
you
can
control
it
either
through
all
the
through
just
exporting
the
machine
sets
directly
or
doing
it
with
the
auto
scaler
right.
A
C
B
Where
how
you
you
know,
where
do
you
want
the
control
right?
The
auto
scaler
is
kind
of
nice
because
you
can
set
lower
and
higher
limits,
right,
right
and
so
it'll
it'll
scale,
and
you
can
tweak
those
right
so
it'll
scale
based
on
those
limits
right
so
it'll
scale
up
when
it
needs
to
it'll
scale
down
when
it.
You
know
when
you
don't
need
it,
so
you
kind
of
set
lower
and
higher
limits.
So
that's
kind
of
nice.
B
If
you
want
a
bit
a
bit
more
control,
you
export
the
the
machine
set
itself
right
and
then
you
control
the
scale
via
pull
request
or
whatever.
So
by
the
way,
if
you're
curious,
what
this
warning
is,
it's,
like:
hey,
you're,
managing
a
namespace
in
two
separate
apps:
that's
yeah!
Okay!
So
you
by
the
way
you
can't
do
that
you.
C
B
Namespaces
two
separate
apps
right,
so
it's
yeah
they
are
the
way
to
handle
that
is,
is
something
called
the
app
of
apps
design.
A
B
B
You
guys
you
guys
can
read
up
on
this.
I'm
actually
going
to
do
a
stream
about
this.
Actually,
you,
you
know
this
chris.
They
made
us
give
like
five
months
of
show
ideas
in
advance.
So,
like
I
already
I
know,
what's
up.
A
No,
but
to
be
honest
with
you
this
so
we're
working
with
our
illustrious
team
at
the
corporate
level.
Now.
B
A
B
B
So
yeah,
so
you
know
it's
kind
of
like
pick
your
poison.
What's
what's
really
cool
about
get
ups
is
that
you
know
you
can
kind
of
tailor
it
to
what
your
environment
is
right.
As
long
as
you
are,
you
know,
following
the
principles
right
everything
and
get
everything
through
pull
requests.
You
can
kind
of
tweak
it
to
where,
where
it
fits
for
your
environment
right,
you
know,
I
show
you
both
examples,
because
none
of
these
are
right
right.
None
of
these
are
wrong.
It's
kind.
B
C
A
B
Wood,
but
it's
the
second
episode
without
issue,
so
awesome.
B
Yeah,
so
we
are
making
progress,
we
are
making
progress,
so
yeah
so
feel
free
to
reach
out
to
me,
I'm
on
I'm
on
the
twitters
right
at
christianh814.
B
So
you
guys
can
find
me
on
twitter
feel
free
to
throw
me
a
tweet
there
or
on
linkedin.
If
you
find
that
yeah.
A
I'm,
for
short,
I'm
always
answering
tweets
and
dms
so
feel
free.
B
Yeah
chris's
dms,
like
you
nee,
you
need
a
a
pa
for
just
for
just
the
so.
A
B
That
would
make
my
job
so
much
easier.
Yeah.
If
you
don't
know
chris
is
like
in
the
kubernetes
world
in
the
cncf
world,
a
devops-ish
he's
in
the
ansible
world
he's.
I
don't
know
how
many
of
you
there
are,
I'm
sure
they're
more
there's
a
bunch
of
chris
shorts
running
around
actually
doing
this,
and
I'm
only.
A
Getting
the
openshift
tv
one
yeah,
maybe
but
yeah
great
show
today
tomorrow
we
only
have
one
stream,
but
we'll
be
talking
about
silos
and
other
windmills
kevin
bear
is
joining
us
so
yeah.
It
should
be
a
good
show.