►
Description
Justin Pittman and Andrew Sullivan discuss automating the deployment of OKD on Bare Metal with User Provisioned Infrastructure (UPI).
A
So
that's
just
to
clarify
bare
metal,
often
gets
used
and
okay
and
falls
to
a
agnostic
platform
small.
So
this
is
agnostic,
it's
just
in
the
sense
that
you
run
it
on
any
linux.
But
it's
not
known
that
how
usually
people
think
of
bare
metal
right.
The
hardware
pizza
boxes
not
meant
to
be
just
to
clear,
so
our
goals
today
is,
we
will
show
the
actual
call
using
a
linux.
A
Has,
I
think
he
said
33
andrew,
so
we'll
show
that
and
then
we'll
there's
lots
of
recommendations
and
gotchas
andrew
was
chatting
me
today.
He
finally
saw
a
lot
of
things
that
he
probably
will
share
with
you
in
getting
this
working
and
then
we'll
wrap
up
with
some
q.
A
from
you
all
about
your
questions
about
spinning
up
or
in
this
way
so
andrew
you
want
to
do
a
brief,
bio
intro
sure.
Do
you
want
to
use
the
slides
that
we
have
for
that
or.
A
B
John,
I
I
agree.
This
is
it's
a
whole
new
experience
for
sure.
I'm
I'm
just
seeing
a
black
screen
justin
it
has
a
this
platform,
has
a
lot
of
potential.
I
like
the
separation
of
the
stage
in
the
sessions.
I
like
how
everybody
can
break
out
and
there's
chat
for
everything,
but
I
don't
know
if
it's
just
unfamiliar.
A
A
B
All
right
so
apologies
for
the
the
rough
starts,
such
as
life,
sometimes
with
technology
and
especially
with
streaming
platforms.
So
I
am
andrew
sullivan.
I
am
a
technical
marketing
manager
with
the
red
hat
cloud
platforms,
business
unit,
so
my
day,
job
is
really
focused
around
openshift
and,
broadly
speaking,
openshift
on
various
virtual
platforms,
as
well
as
openshift
being
a
virtual
platform,
so
openshift
virtualization
convert
that
type
of
stuff.
B
So
there's
some
contact
information
there
anybody's
always
welcome
to
reach
out
to
me
andrew.sullivanredhat.com
or
via
twitter.
I
also
have
a
weekly
live
stream
on
openshift.tv.
It's
the
ask
an
openshift
administrator
office
hour,
so
that
happens
wednesdays
at
11
a.m.
Eastern
time
so
anybody's
welcome
to
stop
by.
We
have
a
whole
bunch
of
different
topics.
Last
week
we
talked
about
etcd.
This
week
we
talked
about
vmware.
B
A
B
Re
are
openshift
youtube,
so
if
you
just
go
to
or
openshift.tv,
if
you
go
to
openshift.tv
you'll
find
links
to
twitch
as
well
as
to
youtube
where
they're,
all
at
yeah
john
on
openshift
youtube
we're
working
on.
We
have
a
an
intern
who
will
be
starting
in
the
next
few
weeks,
who
is
going
to
work
on
automating
the
process
of
creating
playlists
for
all
of
our
different
streams
and
all
the
other
metadata
and
stuff
that's
going
on
there.
So,
hopefully
it'll
get
a
lot
easier
to
find
them
in
the
future.
A
Awesome
because
you
mentioned
that
I
I
had
to
follow
up
so
people
would
know.
Good
thing.
John
has
is
already
familiar
with
them.
They
are
really
extremely
beneficial
just
to
see
you
and
others,
because
there's
a
bunch
of
others
who
also
go
on
there
too,
just
demoing
the
the
technology
live,
so
I'm
justin
pittman.
You
can
find
the
links
there
on
my
linkedin.
I've
been
in
tech
for
a
while.
What
I
do
for
red
hat
is:
I
currently
do
enablement
for
our
partner
sales.
A
So
if,
if
you
know
any
of
our
partners,
it
could
be
f5
or
dynatrace
or
dell,
I'm
usually
involved
in
those
types
of
opportunities
for
our
technology
and
then
at
home.
I
use
a
bunch
of
stuff
like
that's,
not
necessarily
red
hat
productized,
but
might
be
upstream
like
I'll
use
overt
or
something
like
that
in
my
home
lab
anyway
good
to
be
here
with
with
you
all.
A
B
A
A
A
This
may
look
somewhat
familiar
to
you,
but
let's
just
describe
that
for
anyone
watching
it
live
here
or
in
recording
so
okd
and
kubernetes
in
general,
they
do
have
certain
external
dependencies,
whether
you're
trying
to
access
a
application,
that's
hosted
inside
the
cluster,
and
you
need
that
application
to
be
routable.
That's
the
first
thing
through,
let's
say
a
load
balancer
and
the
client
can
only
get
to
it
through
dns
resolution
right.
A
lot
of
those
components,
especially
at
scale,
will
be
done
externally
from
the
cluster.
A
A
Actually,
one
of
andrew's
peers,
christian
hernandez,
initially
came
up
with
the
idea
of
this
helper
node.
That
has
a
bunch
of
these
external
dependencies
as
services,
so
it
comes
with
a
load.
Balancer
is
h,
a
proxy.
It
has
a
dhcp
service
installed
on
it.
It
has
a
dns
server
installed
on
it.
So
it
has
all
of
this
very
quickly
built
out
through
ansible
playbooks,
so
you
don't
have
to
build
out
each
and
install
each
of
these
services
just
to
get
the
external
dependencies
done.
A
A
So
there
needs
to
be
some
image
available
that
the
install
can
in
basically
and
or
have
available.
So
this
gets
back
to
the
helper
node.
Where
do
you
put
these
images?
If,
for
example,
you
can't
download
them
like?
Maybe
you
have
a
bit
of
a
restricted
network
in
some
way
or
you
need
to
configure
the
boot
up
process
like
we're
going
to
do
here,
andrew's
going
to
show
you
well,
you
can
store
those
on
a
web
server,
so
the
image
gets
stored
on
a
web
server.
A
That
is
one
piece
about
how
a
node
gets
its
initial
operating
system.
Other
pieces
of
the
installation
are
pretty
detailed
and
and
documented
elsewhere.
We
have
some
links
about
those
documents,
but
basically
there's
a
couple
of
things
like
the
ignition
config
about
how
those
machines
are
supposed
to
boot
up
inside
the
cluster
and
those
can
be
manipulated,
but
the
installer
does
generate
those
ignition
configs
as
well.
A
At
least
personally
I
find
I
don't
know
your
opinion
on
that
andrew
you've
done
so
many
of
them.
Maybe
it's
like
yeah,
it's
so
easy
for
you
now,
but
for
newbies.
I
kind
of
think
that
it's
helpful
to
understand.
Okay,
you
have
the
installer
binary,
but
there's
some
other
things
that
are
needed
like
a
a
node
os
image,
and
you
need
other
things
that
need
to
be
ingested
by
the
installer
generated
by
the
install
like
ignition
configs
and
just
have
helping
people
visualize
that
process.
B
B
B
A
B
It
was
a
huge
you
know
the
openshift
three
or
okd3
you
know.
Install
process
was
basically
a
huge
set
of
ansible
playbooks,
which
was
really
nice
because
well
ansel
is
familiar
to
most
everybody
at
this
point
and
you
could
easily
go
in
and
troubleshoot
and
look
at
the
nodes
and
find
logs
and
see
what's
going
on,
and
you
know
they
were
rail
nodes,
so
you
could
easily
connect
to
them
and
and
see
all
that
with
four
it's
switched
to
where
now
it's
coreos
right,
so
fedora
core
os
is
harder
to
connect
to.
B
If
you
will
right,
there's
only
key
based
authentication,
it's
only
there
after
ignition
has
run.
You
know
a
lot
of
stuff
like
that,
and
it's
just
meant
to
be.
You
know
they
dramatically
reduce
the
scope
of
the
installer,
whereas
with
three
the
installer
was
responsible
for
you
know,
basically,
you
handed
it
the
rel
nodes
and
then
it
would
go
through
and
it
would
deploy
docker
at
the
time
and
then
it
would
deploy
kubernetes
and
it
would
deploy
like.
B
On
and
on,
and
on
including
things
like
the
logging
service
and
the
metric
service,
and
all
that
with
four,
they
changed
the
installer
so
that
it's
only
responsible
for
basically
getting
the
cluster
up
and
running,
and
then
everything
after
that
is
a
day
two.
So
the
installer
is
much
more
successful
or
more
frequently
successful,
I
should
say,
but
it
can
be
more
difficult
to
troubleshoot
if
you're
not
familiar
with
it,
and
we've
done
a
couple
of
streams
about
that
I'll
touch
on
some
of
those
things.
A
But
I'll
andrew
was
it
was
troubleshooting
late
into
the
evening.
I
I
I
saw
those
messages
late,
but
this
is
the
nature
of
I
think
the
sometimes,
if
it's
a
latest
build
right,
which
I
think
is
what
you
bumped
into
last
night
and
a
couple
others
that
are
in
the
other
sessions
here
today
that
they
bumped
into
similar
issues
with
the
latest
builds.
But
you
know
that's
what
happens
when
you're
fed
or
core
west
instead
of
the
downstream,
like
rel
core
os.
A
I
don't
think
that
you
know
speaking
speaking
of
the
demo
andrew.
Maybe
we
we
jump
to
that
the
next
slide.
I
don't
want
to
bore
people
with
slides
right.
The
next
slide.
We
can
always
come
back
to
later.
Actually
you
know
the
recommended
sizing.
Do
you
mind?
Just
let's
go
to
the
recommended
sizing?
First,
just
so
people
understand
yeah.
So
there
was
some
discussion.
A
If
people
didn't
see
it
in
chat
earlier
that
you
could
get
a
single
node
okd
on
16
gig.
All
right
now
I
have
tried
single
node
on
my
laptop,
the
16
gig.
It
really
you
better
not
have
anything
else
running
basically
right.
So
it
is
possible,
but
what
you're
seeing
now
are
the
recommended
specs
for
a
a
fuller
cluster
and
we
kind
of
added,
I
kind
of
just
threw
this
together
added
it
up
for
you.
A
B
A
The
good
news
is,
it
doesn't
have
to
be
ginormous,
so
you
can
get
by
and
and
and
the
demo
that
andrew
is
going
to
do
is
a
a
fully
featured
cluster
and,
and
there
have
been
inroads
to
to
kind
of
reduce
the
footprint
over
time.
Probably
another
thing
to
think
about
is
storage,
and
if
you
can,
what
is
that
term?
It's
not
sparse
provisioning,
but
it's
thank
you,
then
provisioning,
so
that
you
don't
bump
into
errors
with
kvm
or
or
kim.
A
You
complaining
about
your
storage
going
beyond
what
you
have
locally
vadim
in
chat
also
recommended
that
you
at
least
have
an
ssd
andrew,
and
I
have
been
in
many
conversations
where
the
ncd
instances
inside
okd
just
expect
a
certain
amount
of
response
time
low,
latency,
a
certain
amount
of
iops.
They
just
expect
that
from
the
discs.
So
don't
don't
try
this
with
old,
spinning
rust.
Those
are
just
some
some
basics
for
how
to
get
this
up
and
running
what?
What
kind
of
box
you
need
yeah.
I
would
definitely.
B
Recommend
at
a
minimum
and
ssd,
and
if
you,
if
you
have
available
in
nvme
disk,
I
I
a
week
and
a
half
ago,
so
not
this
past
week,
but
the
10th
I
believe
it
was
march
10th.
I
I
spent
my
live
stream
hour
just
talking
about
egcd
scdu
with
the
product
manager-
and
I
have
you
know,
worked
with
the
support
team.
B
I've
worked
with
the
engineering
team
and
all
that
other
stuff,
and
really
you
want
low
latency
storage
for
ncd
and
the
lower
the
latency,
the
better
and
the
happier
it
will
be
for
a
lab
which
is
more
or
less
what
we'll
be
deploying
today.
You
know
everything
is
going
to
be
in
one
box
that
will
be
deployed
with
libverts
you'll,
see
I'll,
be
using
virtual
machine
manager
for
some
parts
I'll
be
using
the
cli
for
some
parts,
but
you
can
probably
get
away.
A
B
Less
especially
because
you're
not
going
to
be
scaling
right,
you
know
there's
no
at
least
four
for
what
I'm
doing
today.
You
wouldn't
necessarily
want
to
use
it
for
production.
You
wouldn't
want
to
deploy.
You
know
massive
applications
that
are
scaling
the
hundreds
of
pods
on
there,
but
definitely
take
into
account
storage
and
storage
latency
when
you're,
if
you're
doing
any
sort
of
production
type
of
deployment.
A
B
B
So
if
you
want
to
like
see
the
exact
steps
that
I
took
and
all
that
because
I
am
going
to
skip
over
some
things
like
my
helper
node
is
already
set
up.
So
if
you
wanted
to
see
how
I
did
that
it's
all
inside
of
that
just
so
now
I
need
to
so.
I
don't
distract
myself
by
seeing
myself
moving
the
mouse
around
and
I
hide
one
of
these
windows
all
right.
B
So,
let's
start
with
well,
let's
start
at
the
beginning,
I'm
going
to
use
this
as
a
bit
of
a
reference
and
kind
of
walk
through
the
different
parts.
So
I'll
start
here
by
saying
that
you'll
note
that
I'm
going
to
be
deploying
more
or
less
a
five
node
okd
cluster,
so
three
control
plane
nodes.
You
can
see.
I
I've
worked
up
the
name
there,
but
that's
okay.
We
will
temporarily
need
a
bootstrap
machine
and
then
I
have
the
helper
machine.
So,
as
justin
mentioned,
the
helper
is
what
is
providing
to
us
several
different
services.
B
A
B
And
as
justin
said
right,
we
can
use
libvert
for
some
of
that.
So
let
me
bring
up
virtual
machine
manager
here,
so
I've
got
another
a
number
of
other
machines,
so
these
are
just
laptops
and
other
stuff
that
are
sometime
powered
on
that
I
sometimes
use
in
my
lab.
If
we
look
at
the
details
for
this
machine,
however,
all
I
did
was
create
a
new
virtual
network.
So
if
we
click
down
here
on
the
plus,
so
give
it
a
name
whatever
we
want
to
call
it.
B
B
So
if
we
were
to
click
the
finish
there,
what
we
would
end
up
with
is
this
network.
Here
you
can
see
it's
very
straightforward.
Now,
livert
does
use
effectively
behind
the
scenes.
Dns
mask
as
well,
and
you
can
go
in
and
you
can
create
essentially
remember
which
section
it
is
you
can
assign
it
to
give
out
static,
dhcp
leases
you
can
assign
it
to
do.
Dns
resolution
for
all
of
those
nodes
and
all
that
other
stuff
inside
of
there.
B
B
B
A
A
B
A
B
Fedora
33
is
one
of
the
operating
systems
that
is
now
using
systemd
resolve
d
as
the
defaults
resolver.
So
the
result
of
that
is
basically
I
want
to
be
able
to
have
my
box
right.
My
workstation
here
resolve
over
to
the
machines
that
we're
going
to
be
deploying
with
okd
inside
them.
So
I
already
know
that
I'm
going
to
call
my
that
internal
and
that
temporary
one
that
I'm
using
for
my
okd
deployments,
okd.lan
so
effectively.
B
B
So
I
have
this
virtual
bridge
one
and
I
can
do
an
ipa
and
show
that
virtual
bridge
one
here,
is
my
110
network.
So
essentially
I
need
to
tell
systemd
resolve
d
that
hey
when
you
see
an
okd.lan
domain
name.
I
want
you
to
send
those
dns
queries
to
this
location
and
same
thing
with
reverse
dns
and
all
of
that.
So
that's
what
this
set
of
commands
here
is
going
to
do
so,
I'm
literally
going
to
copy
and
paste
those.
B
A
B
B
B
B
Api.Cluster.Okd.Clan,
it
will
well
theoretically,
it
will
resolve
over
there
and
I'll
have
to
see
why
that's
it
could
be
that
my
dns
service
isn't
running
over
here
in
the
helper.
So
we'll
take
a
look
at
that
now,
so
here
I'm
connected
to
the
helper,
so
this
particular
interface.
I
guess
I
should
have
changed
the
colors
on
these,
so
that
way,
they're
easier
to
see.
So
this
particular
one
is
in
so
beret
is
the
name
of
my
fedora
machine
helper
is
the
name
of
my
helper
machine
and.
A
B
B
B
B
B
Christian
hernandez
created
the
helper
node.
So
if
you
go
to
the
helper
node,
let
me
dig
up
that
link
real,
quick,
I'll
I'll
share
it
in
the
chat
okay.
So
if
you
change
the
tag
on
that,
if
there
is
a
helper,
node,
v2
beta
and
that
whole
thing
is
containerized,
so
christian
has
gone
through
and
he
took
it
from
being.
You
know,
services
that
are
deployed
as
normal
services
to
a
system
they're
all
now
in
pods,
and
they
can
all
now
be
used
that
way.
B
B
So
if
I
do
at
you
know,
test.apps.cluster.okd.land
that
should
resolve
same
as
over
here
to
the
the
helper
node,
which
has
that
load
balancer
going
on
the
other
thing
that
we
need
is
our
node
entries.
So
I
said
before
that
we're
doing
static
ip
addresses,
so
I
went
ahead
and
added
those
ip
address
and
name
resolutions
into
the
dns
mask
config,
and
that's
really
all
we've
got
so.
Let
me
double
check
why
this
is
not
in
p1
s0.
A
C
B
B
Control
shifts
for
plus
from
inside
of
a
vnc
session,
yeah
all
right
every
time.
So
hopefully
that's
easier
to
see
so,
okay
good,
so
I
did
get
dns
mask
working.
I
don't
know
why
it
didn't
start
by
default.
If
you
were
paying
attention
there.
I
just
did
a
simple:
you
know,
assist
control
starts
dns
mask
and
if
we
do
the
same
thing
here,
you
know
I
did
that's
nslookup
and
it
goes
right
over
and
it
resolves
my
test.
So
I
can
also
do
a.
B
Test.Apps.Cluster.Okd.Lan
and
it
resolves
right
over
to
our
helper
node,
so
a
couple
of
things
to
note
here,
so
you
saw
when
I
first
set
up
everything
I'm
using
this
okd.lan
subnet
or
a
domain
name
rather
so
cluster
is
actually
going
to
be
my
extremely
creative
right
because
you
know
I'm
a
tme,
not
a
not
a
designer
extremely
creative
cluster
name.
So
this
will
be
unique
to
each
okd
deployment
that
you
have
and
then,
after
that,
we
have
these
different
names
for
the
different
functions
inside
of
there,
with
apps
being
a
wild
card.
B
B
So
after
that
we
start
getting
into
the
actual
load
balanced
endpoints.
So
the
first
one
is
the
api
server.
So
this
is
what
api
dot
cluster
name
dot
domain
name
points
at.
You
can
see
it's
6443
and
then,
on
the
back
end,
we're
passing
it
to
our
bootstrap,
because
the
bootstrap
comes
up
first
and
then
our
three
control
plane
nodes
being
h.a
proxy.
I
don't
need
to
modify
the
configuration
of
this
as
this
bootstrap
node
goes
up
and
down
and
as
I
reload
the
clusters,
because
it'll
automatically
say:
hey
you're
not
responding
right.
B
A
B
The
front
end
and
back
end
for
the
machine
config
server
same
as
above
that
points
to
the
bootstrap
and
the
control
planes.
So
one
interesting
thing
to
note
here
right:
the
machine
config
server-
is
how
the
machine
config
operator
serves
up
the
configuration,
the
machine
config
to
the
nodes.
So
this
is
an
unauthenticated
endpoint.
Basically,
you
can
go
in.
You
can
pull
that
http
traffic
or
https
traffic,
but
it
is
not
authenticated
and
be
able
to
see
that
machine
config.
So
this
one
is,
this
is
effectively
the
api
int
api
internal
endpoint.
B
B
The
cluster,
or
even
possibly
on
an
internal,
only
network-
that's
available
there
so
moving
on
down
here.
We
then
have
our
ingress
endpoints.
So
this
these
two
are
going
to
be
the
api
or
excuse
me
the
start.apps
wildcard,
so
we
have
one
for
http
and
one
for
https
and
notice
that
it's
not
in
here,
because
I
set
it
up
at
the
top.
I
apologize
on
my
page
up,
so
it's
going
to
jump
around
on
you
see
my
default
mode.
Here
is
tcp,
so
it's
doing
layer,
4
or
layer,
4
load
balancing.
B
So
it's
just
passing
through
things
like
all
of
the
ssl
encryption,
all
of
that
directly
to
the
routers
that
are
running
inside
of
okd.
So
that
way
it
can
do
re-termination
and
all
that
other
stuff
itself.
You
can
do
layer
seven!
I
have
not
done
it,
but
I've
been
told
multiple
times
that
it
is
possible
so
and
just
to
check
on
that
we'll
go
ahead
and
go
to
helper
dot
and
we'll
go
to
port
9000.
B
B
A
B
A
B
B
A
A
B
B
B
Aside
from
that,
I
had
gone
in
and
inside
of
my
web
docs,
and
I
just
linked
here
we'll
bring
up
oops,
bring
up
that
page
again.
So
you
see
I
attached
a
volume
of
our
www.html
to
the
pods,
hd,
docs
or
ht
root,
and
inside
of
here
you
see,
I've
got
two
different
directories.
I'll
do
a
quick
tree
in
here,
so
the
first
one
is
ignition.
We'll
use
that
in
just
a
moment.
This
is
where
we'll
dump
the
ignition
files
that
our
nodes
are
going
to
need
when
we
install
them
the
other
one.
B
Is
this
install
directory?
So
these
are
the
three
metal
files
that
we
need
for
our
deployment.
So
why
is
that?
And
what
do
I
mean
by
that?
So
with
libert?
There
is
no
upi.
There
is
no
ipi
type
of
integration
right.
So
that
means
that
we
have
to
do
what
red
hat
and
what
openshift
calls
a
platform
agnostic
non-integrated
deployment.
B
Now,
if
you're
deploying
to
overt
or
something
like
that,
there
is
that
integration
right,
you
can
deploy
an
installer
provisioned
infrastructure,
ipi
cluster
and
it
will
connect
to
your
your
overt
manager.
It
will
talk
through
the
apis
to
revision,
the
vms.
It
will
configure
the
csi
provisioner
right.
It
will
do
all
that
stuff
out
of
the
box.
B
So
I'm
jumping
ahead
here
by
showing
you
this,
but
a
little
bit
further
down
and
I'll
revisit
this
in
a
moment,
a
little
bit
further
down
I'll
show
the
links
to
download
those.
I
just
do
a
quick
w
get
and
then
move
them
over
there
and
make
sure
that
the
permissions
are
correct.
So
that
way
they
can
be
retrieved
by
the
nodes
when
we
need
them,
which
is
the
next
step
there
we
go
so
from
my
libvert
host.
So
that
means
that
I'm
on
this
beret
host,
you
can
see
I'm
in
the
okd
directory.
B
I
tried
doing
it
with
the
very
latest
bits
with
the
latest
4.7
bits
and
was
having
issues
with
the
bootstrap.
So
if
you
happen
to
be
on
the
github
page,
if
you're
looking
for
the
issues,
you'll
see
there's
some
comments
for
me
regarding
that,
so
I'm
using
4.6
I'm
using
from
back
in
mid-february
here,
because
that's
the
one
that
I
was
able
to
get
to
work.
B
We
need
to
pull
down
two
files,
so
we
need
the
open
shift
install
and
we
need
the
openshift
client.
So
when
we
pull
those
two
down
pretty
straightforward,
all
we're
going
to
do
is
unpack
them
and
then
move
the
three
files
that
are
within
openshift
dash,
install
oc
and
kubecuttle
into
user
local
bin.
You
don't
have
to
put
them
in
the
path.
I
just
find
it
easiest
to
do
that.
So
if
we
come
back
over
here
and
we
do
an
open
shift,
install
version,
what
we
should
see
is
open
shift,
install
version,
4.6
2021.0214.
B
B
B
B
A
B
A
B
A
A
A
A
B
B
A
Here's
here
I
want
to
wrap
up
my
previous
thought,
because
I
think
this
is
still
a
good
point
to
mention
it.
You
know
some
folks,
maybe
not
here,
because
we
seem
pretty
techy,
but
in
the
recording
we'll
say
this
is
a
lot
of
heavy
lift.
I
download
all
these
files.
I
had
a
set
up.
All
of
this
configuration
isn't
there
in
a
push
button
thing.
A
B
So
if
we
walk
through
this,
it's
pretty
straightforward.
So
first
we
want
to
make
sure
that
we
have
an
ssh
key
in
here.
So
that
way
we
can
connect
over
to
the
vms
once
they've
been
deployed.
Remember,
there's
only
key
based
authentication
with
the
user
core
and
then
the
pull
secret
is
actually
just
a
dummy
secret.
You
can
see
here
we're
just
using
this
non
non-useful
text.
B
A
B
Workers
so,
but
we
still
want
to
set
this
to
zero.
This
is
basically
indicating
that
it's
not
responsible
for
provisioning
any
of
those
we'll
have
three
master
replicas
or
three
control,
plane,
replicas
and
then
down
here.
These
will
be
defaults,
so
the
the
cluster
network.
This
is
what
it
uses
to
assign
pod
networks
to
each
one
of
the
nodes.
So
it'll
take
this
slash,
14
and
it'll,
carve
it
up
into
23s
and
assign
a
23
to
each
one
of
the
nodes
in
the
cluster,
and
that's
where
those
pods
get
assigned.
B
The
service
network
is
the
set
of
ips
that
are
used
for
services.
So
when
you
create
a
service,
the
ipa
gets
designed
comes
from
here,
so
this
networking.machinenetwork.cider
is
very
important,
so
we
want
to
make
sure
that
this
value
matches
the
subnet
that
we're
deploying
our
virtual
machines
to
so
110.0
is
what
I'm
using
here.
The
reason
why
this
is
important
is
because
okd
core
os
looks
for
an
interface
on
this
subnet,
and
that
is
the
interface
that
it
will
configure,
for
example,
the
sdn
on
it's
also
used,
for
example,
if
you're
using
a
proxy.
B
B
Create
ignition
conv
oops,
not
ignition,
config,
install
config
right
so
using
ipi.
I
can
use
the
interactive
installer
and
I
can
step
through
each
one
of
these
things
that's
happening
here
and
I
can
choose
the
one
that
I
want
to
use
or
the
infrastructure
that
I
want
to
deploy
to,
and
actually
I
need
to
pull
the
most
recent
version
of
the
cli
tool.
B
A
B
Take
this
guy
and
paste
it
here,
so
this
is
effectively
the
the
kind
of
how
to
set
up
and
how
to
use
this
ipi
livered
api
side
of
things.
So
the
important
thing
here
and
I've
done
this
with
my
host-
that
I'm
working
with
we'll
skip
past
all
this
configure
libvirt
to
accept
tcp
connections
so
effectively.
What
we're
doing
is
telling
libvert
to
accept
an
unauthenticated
connection
across
tcp
and
that's
how
it
connects.
B
So,
if
I
copy
this
string
here
and
we'll
copy
that-
and
if
I
go
to
virtual
machine
manager
and
do
a
add
connection,
I
can
do
a
custom
url
paste
that
in
and
you
notice
it
didn't
authentic.
It
didn't
ask
for
any
kind
of
authentication
right.
It's
the
these
two
are
the
same
host.
So
if
I
were
to
go
here
and
disconnect
this
one
and
then
connect
it
again,
it
prompts
me
for
authentication.
B
B
A
B
A
B
Thing
that
we
were
talking
about
with
fedora,
33
and
systemd
resolve
d.
This
is
the
same
thing
if
you're
using
other
operating
systems
that
use
network
manager
with
the
dns
overlay.
So
this
is
how
you
tell
network
manager
to
configure
your
resolver
to
point
to
that
local
network
inside
of
there
and
note
that
it
does
deliberately
do
this
126.1
so
make
sure
that
you
do
that
ip
address.
B
B
And
what
it's
going
to
do
is
it
will
go
through
and
I
should
have
turned
on
the
debug
logging,
but
behind
the
scenes
it's
creating
the
resources
that
it
needs.
Oh,
I
forgot.
I
created
the
ignition
config
and
if
we
look
at
our
so
here's
our
ignitions
and
all
of
that
I
meant
to
create
install
config,
not
ignition
config
and
if
I
do
a
simple,
create
cluster
now.
B
So
it's
going
to
pull
down
the
terraform
provider,
it's
going
to
do
everything
that
it
needs
to
get
started,
and
if
I
check
over
here,
you
can
see
that
it's
automatically
created
a
new
network
right
and
this
is
where
it's
using
you
know
the
internal,
essentially
a
round-robin,
dns
load,
balancer
quote
unquote
to
resolve
all
those
things
here.
In
a
moment,
it'll
start
up
a
virtual
machine.
Do
all
that
other
stuff.
It
also
created
a
new
storage
pool.
So
we
have
this
cluster
one.
You
can
see.
B
B
There's
a
bug
in
the
current
one
where
here
in
a
moment
it'll
finish,
and
it
will
create
two
virtual
machines
that
will
create
a
bootstrap
and
it
will
create
a
control,
plane,
node
and
the
bootstrap
only
has
four
gigs
of
ram,
which
is
not
enough.
So
it
turns
on
when
the
the
okd
bootstrap
process
goes
through.
It
pulls
down
a
new
image
and
then
uses
rpm
mastery
to
switch
to
that
image,
and
that
image
is
larger
than
the
temporary
swap
space.
The
the
slash
var
run
or
slash,
run
rather
space.
B
That
is
available,
so
it
runs
out
of
space
and
it
never
succeeds.
You
can
get
it
to
go
further
if
you-
and
I
think
I
almost
had
one
running
earlier
today,
if
you
catch
it
before
it
boots.
So
basically,
if
you
immediately
turn
off
those
virtual
machines,
edit,
both
of
them
to
give
them
at
least
16
gigabytes
of
ram
and
then
turn
them
back
on
and
then
wait
long
enough,
you
should
be
able
to
get
a
cluster
at
that
point
and
it
will
do
it
will
be
ipi.
B
A
But
so,
let's
pause
for
a
moment
just
to
recap,
because
that
that
was
a
lot
to
digest.
So
there's
two
methods:
the
the
method
that
you
just
are
showing
us
now
showing
everyone
now
is
the
automated
integrated
quote:
unquote:
ipi
method
against
libvert,
where
the
installer,
the
okd
installer,
is
calling
libvert,
making
all
those
calls
creating
the
vms.
It
already
downloaded
everything
it
needed.
Oh
there,
it
is
yep
the
vms.
A
So
the
previous
method
that
you
had
started
to
take
us
down
was
the
non-integrated
non-automated,
where
you
basically
have
to
download
all
the
images
and
set
up
all
the
configuration,
etc.
So
just
to
be
just
to
restate
that
these
were
two
different
install
methods
and
the
reason
to
not
use
the
automated
one.
Is
it's
brand
new
as
of
4.7,
and
there
is
that
memory
bug
that
you
were
mentioning
correct,
yeah.
B
And
and
the
goal
is,
and
I'm
sure
that
we'll
get
there
before
long,
the
the
goal
is
right
sure
it
would
be
great
to
have
ipi
and
especially
if
we
can
do
a
single
node
ipi
on
something
like
this.
Where
you
just
say
you
know
open
shift,
install
create
cluster
and
it
points
to
that
local
livert.
It
deploys
a
virtual
machine,
it
gets
everything
up
and
running
all
inside
of
that
single
node.
That
would
be
great.
B
B
So
I
said
so,
can
I
can
you
set
the
memory
in
the
install
config
so
unfortunately,
no
and
the
reason
why
that
is,
is
because
it's
not
actually
defined
as
an
option
inside
of
there.
So
if
I
do
open
shift,
install,
explain,
install
config
dot
and
we
can
just
step
through
this
right.
So
we
see
we
have
our
platform
here.
So
if
I
do
install
config.platform
and
then
we
have
libvert.
B
B
B
Those
values
live,
verts
see,
we
don't
have
any
options
in
install
config
to
set
them
so
for
the
worker
nodes,
you
could
do
it
by
so
creating
the
install
config
and
then
doing
a
generated
manifest
and
then
going
into
the
manifest
and
modifying
the
machine
set
that
it
creates
to
put
the
right
amount
of
memory,
but
the
control
plane
nodes
are
created
by
the
installer
and
the
installer
has
no
right.
We
we
just
walk
through
that
tree.
There's
no
parameters
in
there
for
adjusting
it.
So
yeah
we
have
seen
hidden
parameters.
B
A
B
At
that
yeah
the
the
library
ipi
feels
a
little
neglected.
Sometimes
so
it's
it's
not
there,
but
definitely
with
overt
slash,
rev,
definitely
with
vsphere.
Definitely
with
openstack
as
well
as
I
believe,
the
hyperscalers.
You
can
change
all
of
those
things
so
with
the
hyperscalers
like
aws,
you
would
change
the
instance
type
that
it's
using,
but
okay,
so
I
just
I
just
destroyed
those
resources,
so
that
is
one
of
the
nice
things
it
does
clean
up
after
itself.
So
if
we
come
back
here
and
we
see
our
network.
B
B
Domain
name
coming
down
through
here.
We
need
to
make
sure
that
our
machine
sider
is
set
correctly.
So
this
is
110
and
then
everything
else
we
can
pretty
much
leave
at
the
default
again.
Definitely
make
sure
that
you
have
your
your
public
key
for
ssh
inside
of
here,
so
you
can
connect
over
to
the
nodes
and
the
last.
B
I'm
now
going
to
copy
that
into
this
cluster
folder
and
it's
just
an
empty
folder.
I
just
created
it
as
a
holding
spot.
The
reason
why
I
always
do
this
is
because
when
you
do
the
next
step,
it's
quote:
unquote
ingests
the
install
config.yml
and
deletes
it.
So
if
you
want
to
go
through
multiple
iterations
without
having
to
constantly
recreate
that
file
by
hand,
I
always
put
it
someplace
and
then
copy
it
into
so
we'll
put
that
guy
inside
of
there
and
then
the
next
step
that
we
want
to
do
so
all
right.
B
A
B
B
Look
for
hidden
files
in
the
directory
that
are
like
open
shift,
install
logs
and
stuff
like
that,
because
the
install
app
the
the
binary
will
look
at
those
files
and
it'll
make
decisions
for
you
you're
like,
but
it
didn't
ask
me
that
or
why
did
it
do
this?
I
didn't
tell
it
to
do
that
so
make
sure
you
and
you
remove
all
of
those
files
that
are
inside
of
there
and
I'll
show
you
what
those
look
like
in
just
a
minute.
B
So
if
we
go
into
our
cluster
directory
here
and
do
an
lsla
see
these
two
files,
those
are
files
that
it
uses
to
make
decisions
for
you
right
so
more
or
less
pick
up
where
an
install
left
off
or
something
like
that.
So
this
is
why
I
always
recommend
you
know:
create
a
subfolder
copy,
your
install
config
into
there
and
then
do
everything
inside
of
there
when
you're
done
with
it
just
rm
dish,
rf
that
whole
folder,
so
you
can
clear
it
out
and
start
completely
fresh
each
time.
B
B
A
B
A
I
put
it
in
the
chat
earlier,
but
I
do
want
to
take
the
time.
This
is
actually
a
good
time
to
ask
you
andrew.
Sometimes
it
gets
a
little
confusing
which
of
the
steps
to
execute
for
the
installer,
sir.
You
showed
us
generate
the
install
config
generate
the
ignition
config
generate
the
manifest,
and
sometimes
it's
not
clear
when
to
do
which,
like
the
manifest.
B
A
B
So
that's
a
really
good
point
and
it's
something:
that's
you
know.
Even
the
openshift
documentation
does
a
terrible
job
of
pointing
out.
So
if
you're
doing
ipi
with
a
hyperscaler,
so
aws
azure,
google
et
cetera,
then
you
can,
I
absolutely
go
in
and
do
an
open
shift
install
create
cluster
and
just
go.
You
don't
have
to
worry
about
anything
if
you're
doing
an
on-prem
ipi
deployment,
I
always
recommend
doing
a
create,
install
config.
First
answer:
all
the
questions
so
on-prem
ipi
open
shift,
install,
create
install
config
it'll.
Ask
you
all
the
questions.
B
So
what
do
you
want
to
install
too?
I
want
to
install
to
overt
okay.
What's
your
overt
manager
endpoint?
What's
your
over
manager
credentials?
Which
cluster
do
you
want
to
use?
Which
network
do
you
want
to
use
which
storage
domain
do
you
want
to
use
so
on
and
so
forth
and
we'll
spit
out
that
install
config
at
the
end,
then
you
want
to
modify
that
install
config
to
make
sure
that
that
networking
dot
machine
network
dot
sider
is
correct
because
by
default
it'll
be,
I
think,
it's
10.0.0.0.8
or
something
like
that.
B
Now,
if
you're
doing
on-prem
upi,
I
tend
to
recommend
always
doing
well,
it
varies,
but
almost
always
I
end
up
doing
I
create
the
install
config
by
hand.
Sometimes
I'll,
do
a
kick
it
off.
With
the
open
shift
install
create,
install
config,
I
keep
wanting
to
say
ignition
configs,
which
is
wrong,
install
config.
B
It
gives
me
that
template
and
then
I
can
go
in
and
edit
it
by
hand
to
remove
the
platform
section,
for
example,
so
create
the
ignition
config
or
install
config
rather
create
manifests
specifically
because
we
want
to
mark
the
schedule
of
the
masters
as
non-schedulable
unless
you
want
that
three-note
compact
deployment-
I
very
rarely
do
that
just
because
I
I
almost
always
have
other
my
my
default.
Config
is
a
lot
of
times
to
test
kubert
and
stuff
like
that,
so
I
want
to
have
dedicated
physical
notes.
B
So
that's
why,
like
I
have
all
of
those
other
random
laptops,
old
laptops
and
stuff,
like
that,
I
turn
those
into
okd
nodes
for
coovert
and
then
from
there.
You
know
going
on
with
the
rest
of
the
process,
so
yeah
we,
we
don't
make
it
easy
in
the
documentation
for
when
to
use
each
one
and
why
to
use
each
one.
B
A
B
B
So
now
I
need
to
put
those
ignition
configs
onto
our
helper
node
onto
the
web
server,
and
this
is
so
that
when
our
nodes
boot
up
right,
they're
able
to
reach
out
they
pull
down
that
ignition
config.
That
way,
they
can
do
that
initial
configuration
so
we're
getting
better
with
the
various
ipi
installs
of
being
able
to
attach
those
without
having
to
host
them
on
a
web
server,
but
with
the
non-integrated
method.
We
do
still
have
to
do
that.
B
So,
for
example,
if
you
were
to
do
a
vmware
deployment
right
with
vmware,
you
can
go
in
and
you
can
set
a
vm
property
that
will
attach
all
of
that
data
inside
of
there.
So
we'll
copy
this
command
and
paste
it
inside
of
here.
You
can
see
I'm
just
copying
all
of
those
ignition
files
over
to
our
helper
node
into
the
right
place,
but
we
need
to
do
it
as
the
correct
user,
not
as
that
user.
B
B
B
B
So
the
first
thing
that
we're
going
to
do
is
create
the
disks
that
we
need
for
our
virtual
machines,
so
I
am
not
on
the
helper
node,
I
am
on
my
libert
node
and
I'm
going
to
paste
that
command
in
all
we're
doing
here
is
a
simple
loop.
Where,
for
each
one
of
the
nodes,
we
do
a
qmu
image,
create
of
a
120
gigabytes,
qca2
image.
Inside
of
our
remember,
my
mounted
storage
pool
all
right.
So
now
we
have
all
of
those
files
inside
of
there.
B
B
It's
it
I
would
say
it's
the
minimum
size
that
you
would
want
for
any
kind
of
production
cluster,
any
kind
of
long-running
cluster.
I
remember
that
this
space,
this
120
gigabytes,
will
be
used
for
everything.
Fedora
coreos
is
doing
as
well
as
any
container
images
that
are
downloaded
as
well
as
any
scratch
space,
as
well
as
any
empty
doors
logs
that
are
generated
right.
All
of
those
things
go
inside
of
there
and
effectively.
If
that
fills
up,
it's
it's
a
bad
day
right.
B
A
B
Directory,
I
really
miss
being
able
to
do
a
keyboard
copy
and
paste,
but
pnc
doesn't.
Let
me
do
that.
We
have
our
files
inside
of
here
they're
available
to
us
now.
The
reason
why
I
want
them
locally
on
this
box
is
because,
in
the
next
step,
we're
going
to
tell
it
to
do
a
local
kernel
boot
of
our
virtual
machine
to
do
the
install
so
we're
going
to
use
a
couple
of
variables.
A
A
I
don't
even
remember
if
it's
just
standard
it
might
be
extended,
attribute
permissions
that
if
you
don't
put
things
there,
whatever
isn't
there
or
if
you
try
to
use
a
different
directory,
libvert
will
start
to
complain
a
vm
might
not
it
might
boot
once
and
then
not.
I've
seen
it
not
be
able
to
reboot
after
a
while,
so
that
that's
a
special
directory
for
sure
for,
for
things
like
storing
images
for
libvert.
B
Yeah,
it's
I've
had
the
same
thing
and
permissions
are
always
an
issue.
It
seems
like
so
my
three
variables
here
right
kernel
is
pointing
to
the
file
that
we
just
described
up
here
same
thing
within
it,
rd
kernel
args
is
important.
So
remember.
I
said
that
we
needed
to
point
it
to
where
the
root
fs
is
at
and
it's
hosted
off
of
our
helper
web
server.
B
B
So
let's
break
the
string
down
and
all
of
this
is
in
the
documentation.
So
if
you
go
into
that
agnostic
out
here
installing
on
on
any
platform,
all
of
this
is
described
inside
of
there.
So
don't
don't
worry
that
you
have
to
remember
what
what
I'm
saying
here.
So
the
first
thing
is
the
ip
address
that
we
want
this
node
to
use
double
colon
and
then
what
is
the
gateway
for
this
subnet?
B
What
is
the
net
mask?
What
is
the
hostname,
including
fully
qualified
domain
name,
that
we
want
to
assign
to
it
the
interface
that
we
want
to
configure
with
all
of
this
information?
None.
I
don't
remember
what
that
one
is,
but
it's
always
none
and
then
the
dns
server
that
we
wanted
to
use
so
because
all
of
this
information,
except
for
these
two
bits,
the
node
ip
and
the
node
name-
is
the
same.
B
B
B
Real
quick
and
then
I'm
going
to
copy
and
paste
the
rest
of
this
just
to
execute
it
and
do
all
of
them
at
once.
So
we
can
move
on
to
the
next
step,
but
we're
just
repeating
that
for
each
one
of
the
control,
plane,
nodes
and
worker
nodes,
the
one
thing
to
note
is
that
I
did
a
little
bit
of
and-
and
you
see
I
use
the
term
jiggery
pokery
up
here,
so
I'm
doing
bash
variables
by
reference.
B
So
essentially
I
determine
what
the
node
name
is
without
the
dash,
because
that
throws
an
error
and
I
create
basically
the
same
variable
name
that
we
created
up
here
and
then
down
here
where
I
actually
want
to
use
it.
I
reference
it
or
I
use
it
by
referencing
that
name
here
with
the
bang
in
front
of
it.
So
I
had
some
fun
doing
research
on
bash
last
night,
because
I
had
never
done
that
method
before.
B
B
B
So
if
I
look
at
this
bootstrap
xml
definition
see
even
though
I
told
it
the
kernel
file
is
in
var,
live
live
vert
boot
it
it
grabs
this
random
name.
I
have
no
idea
where
that
name
comes
from
or
why
and
so,
essentially,
all
I'm
doing
and
here's
the
output
of
that
whole
big
kernel
line
with
all
those
variables
and
stuff
like
that.
A
B
B
B
B
B
B
B
B
That's
just
to
make
sure
that
has
more
than
enough
to
do
the
things
that
it
needs
to
do,
and
then
the
magic
that's
happening
here
is
underneath
the
boot
options.
I'm
doing
this
direct
kernel
boot
and
I'm
having
it
boot
off
of
that
kernel
and
that
init
ram
fs
image
with
all
of
those
kernel
args
that
we
built
to
do
the
static
ip
assignments
and
where
to
install
to
and
all
that
other
stuff.
B
After
that,
it's
pretty
standard
right,
the
disk
that
we
created
the
network
adapter.
We
don't
really
care
what
mac
address
it
gave
it
or
anything
like
that,
because
we're
using
static,
ips,
not
dhcp,
and
everything
after
that
is,
is
standard.
The
one
thing
to
note
here:
we
are
using
the
fedora
core
os
stable.
So
if
you
were
to
search
here
for
just
core
os
you'll
note
that
there
are
three
of
them
that
come
up,
I
happen
to
be
using
the
stable
one.
B
A
B
So
I'm
just
going
to
let
it
default
create
a
disk
here
we
can
select,
we
can
put
it
into
an
alternate
pool
if
we
choose
and
then
give
it
some
sort
of
name.
So
one
thing
to
note:
we
want
to
make
sure
that
we
put
it
on
to
the
right
network
and
I'm
going
to
customize
the
configuration
before
install
and
then
this
is
where
I
would
want
to
go
in
and
make
sure
that
my
boot
options
are
set
correctly.
So
we
just
click
that
and
then
we
browse
to
our
bar
live
boot.
B
B
C
B
I'm
doing
it
this
way
is
because
it's
much
faster,
so
you
can,
you
can
host
those
files,
you
can
have
it
pixie
boot,
for
example,
there's
a
number
of
different
ways
of
doing
it.
I
find
especially
with
a
single
libert
host
like
this
hosting
those
on
the
local
local
file
system,
makes
it
tremendously
quicker
to
do
the
the
install
process.
B
A
B
Yeah
yep
so
neil,
so
we
have
gone
through.
We've
set
up
our
stage,
everything
that
we
need
on
the
helper
node
we've
created
our
ignition
configs.
We've
staged
those.
So
at
this
point
I
just
installed
the
bootstrap
but
we're
getting
ready
to
install
coreos
to
the
rest
of
them
as
well,
so
very
much
to
justin's
point
it's
nice
to
have
the
console
up,
so
we
can
see
if
something
goes
wrong.
You'll
also
notice
that
once
it's
finished
instead
of
doing
a
reboot,
it
shut
down
the
machine.
B
So
that
is
quite
convenient
and
one
of
the
one
of
the
things
that's
nice
here.
So
I'm
just
going
to
turn
the
rest
of
these
on
and
let
them
do
their
thing.
I
think
in
the
gist.
I
note
I
have
automation
over
here
that
says
just
a
virtual
start
and
then
optionally
add
in
a
sleep
if
you're
using
slightly
slower
storage.
So
this
is
an
nvme
device.
Now
you
may
want
to
consider
staggering
these
because
they
can
take.
C
C
B
B
So
remember
at
the
very
beginning,
I
said
that
effectively
the
install
process
is
super
complex
and
and
like
we've
spent
what
an
hour
now
going
through
all
these
different
steps
of
staging
everything
and
making
sure
all
the
processes
are
set.
Well
now
all
we
do
is
turn
these
vms
on
and
it
sets
itself
up
with
one
exception:
that's
approving
csrs,
so
I
do
need
to
go
in
and
I
need
to
remove
that
config
that
we
had
just
done
so.
B
B
Now,
if
we
look
at
our
vm
definition
here,
you
can
see
our
boot
options
have
been
removed
and
if
I
check
the
xml
here,
our
on
reboot
is
now
set
to
restart
instead
of
destroy
like
it
would
have
been
before
so
now
we
simply
power
it
on
right.
We
can.
We
can
check
over
here
with
our
so
virtual
start,
I'm
going
to
stagger
these
just
a
little
bit
because
they
do.
B
B
B
B
A
At
this
point,
go
ahead:
justin,
while
we
watch
the
the
bootstrap,
I
think
a
couple
of
points
have
been
brought
up
too.
One
is
from
neil,
he
just
joined
his
question
was
about
upi
and
why
is
it
required
to
use
static
ip
you?
You
me,
you
talked
a
little
bit
about
this
earlier,
but
just
to
repeat,
while
we're
doing
it
this
way,
so
it's
not
required
to
use
static.
B
B
A
B
B
B
H,
a
proxy
can't
I'll,
so
your
question
so
load
balancers
can't
do
dns
based
selection,
aj
proxy.
I
don't
think,
can
the
last
time
I
checked,
which
I'll
admit
has
been
like
a
year
ago.
It
could
not
so
maybe
that's
changed.
I
should
probably
look
into
it
but
yeah
that
that
is
why
I've
always
done
either
static,
ips
or
dhcp
reservations.
B
A
I
think
you
know
just
to
give
everyone
background
andrew
and
I
kind
of
went
back
and
forth
on
this
about
we
we
did
want
to
show
the
most
simplified
way
to
install
at
first,
but
when
we
saw
that
the
automated
integrated
installer,
for
example,
that
was
the
first
issue,
then
we
decided
okay.
Well,
let's,
let's
do
the
upi
method
and
just
it
provides
a
more
under
the
covers
view.
When
you
say
andrew,
you
get
to
really
see
the
mechanisms
that
are
working
right,
yeah,
just
definitely
yeah.
A
I
mean
there's
all
kinds
of
different
ways
to
do
this.
I
mean
let's
not
get
into
even
like
pixie
booting
stuff,
because
even
though
that's
possible-
and
it
would
definitely
get
a
fleet
of
nodes
operational,
we
kind
of
figured
this-
would
be
a
small
group
that
probably
doesn't
have
enterprises
stuff,
like
pixie
servers
and
enterprise
level,
load
balancers,
and
things
like
that.
So
we
wanted
to
try
to
say:
hey
if
we
do
just
one
box,
a
linux
box
hosting
okd.
B
I
was
as
justin
and
I
were
preparing
for
this-
I
kept
telling
them
like
you
know.
We
have
like
this
world
of
possibilities,
and
this
is
this
is
one
way
out
of
about
300
of
doing
it,
and
it
was
I
I
switch
between
them,
because
I
try
to
be
familiar
with
a
lot
of
the
different
ways.
So
this
it
was
hard
for
me
to
narrow
it
down.
B
A
B
B
B
That
ignition
config
and,
among
other
things
it
uses
the
ncd
operator,
the
cluster
lcd
operator
to
instantiate
a
single
node,
ncd
and
then
instantiate
the
cluster
or
the
machine
config
operator.
The
control
plane
nodes
then
come
up.
So
those
three
nodes
come
online.
They
look
to
that
machine,
config
operator
instance.
They
get
their
configuration
and
then,
after
they
configure
themselves,
they
start
talking
to
the
bootstrap
and
the
bootstrap
says
I'm
going
to
using
the
lcd
cluster
config
operator,
I'm
going
to
increase
my
xcd
node
count
to
three.
B
So
adding
two
control
plane
nodes
decrease
it
to
two
removing
the
bootstrap
and
then
increase
it
back
to
three
bringing
it
up
to
the
three
control
play.
Notes
the
bootstrap
then
hands
over
all
of
the
kubernetes
control
plane
operations
to
the
newly
instantiated,
those
three
new
control
plane
nodes.
So
that's
effectively
what's
happening
here
in
the
background.
That's
what
we're
watching
all
these
pods
right.
All
these
messages
scroll
by
this
is
it
handing
over
all
of
that
information
and
waiting
for
the
control
plane
nodes
to
take
ownership
of
it.
So
we
can
see
right.
A
B
B
Want
so
at
this
point,
what's
happened
is
and
it's
going
through
and
you
see
all
of
these
different
mammals
that
are
being
applied
so
on
that
new
control
plane.
Remember
it's
just
kubernetes,
so
it's
a
kubernetes
control,
plane
the
cluster,
instantiated
or
deployed
operator
lifecycle,
manager,
olm,
and
it
is
now
using
operators
to
instantiate
all
of
those
okd
services.
So
there
there
are.
Our
service
has
succeeded.
A
B
To
the
cluster,
just
like
bootstrap
wasn't,
and
it's
not
saying,
okay,
now
you
need
to
do
this.
Okay.
Now
you
need
to
do
this.
It's
just
monitoring
and
reporting
back
the
status
of
what's
going
on
in
the
cluster,
and
we
can
actually
get
this
information
this
right
here,
that's
working
towards
five
percent
complete
by
querying
the
cluster
directly.
So
that's
what
I
want
to
show
over
here
in
this
one,
while
that's
going
so
inside
of
my
cluster
folder,
so
remember
this
is
where
I
place
the
ignition
or
install
config
file.
B
This
is
when
we
created
the
manifest
it
was
done
inside
of
here.
This
is
where
we
have
our
ignition
files
when
they
were
generated.
Very
importantly,
we
have
this
off
directory
inside
of
here
are
two
things.
One
is
the
cube
admin
password.
So
if
you
walk
away,
if
you
forget
to
record
it
or
anything
like
that,
the
coupe
admin
password
is
stored
in
this
file
and
then
the
kube
config
file
that
we
can
use
to
connect
as
a
system
admin
to
the
cluster.
A
B
B
B
B
I
don't
know
who
came
up
with
this.
I
think
it
was
christian
who
originally
discovered
this,
and
I
think
he
did
literally
spend
something
like
two
or
three
hours,
trying
to
figure
out
the
go
template
to
extract
this
specific
string,
wow
so
the
first
it
will
request
two
of
these
one
for
each
one
of
the
nodes.
So
here's
the
line
right,
you
see
it's
requesting
one
for
each
one
of
the
nodes
and
then
once
those
are
approved,
there'll
be
two
additional
ones
that
come
up
so
here's
worker
zero.
B
B
B
B
A
B
Yeah
yeah,
that's
a
strange
one.
I've
never
had
that
happen
before,
but
it's
coming
up
the
cluster
will
deploy
with
a
single
worker.
What
we'll
see
is
the
ingress
operator
is
angry
because
it
wants
to
have
two
replicas
by
default,
so
we
can
fix
that
by
just
changing
it
to
having
one
replica.
Of
course,
then
it's
not
highly
available,
but
that's
okay.
B
A
B
B
B
B
If
we
do
oc
get
node
and
oc
describe
node
on
one
of
our
control
plane
nodes
here
way
down
at
the
bottom.
We
have
this
allocated
resources.
You
can
see
that
requests
only
total
five
gigabytes
of
memory.
So
that
tells
me
that
your
slide
that
you
had
shared
earlier,
that
has
the
eight
gigabyte
ram
that.
A
B
A
B
B
A
A
A
A
C
You
guys
are
bare
metal,
so
was
the
vsphere
folks
finished
theirs
and
they
did
cut
out
a
little
bit
early
because
it
was
going
to
be
another
10
to
20
minutes
of
staring
at
the
screen
to
watch
an
upgrade.
So
those
two
are
done
and
you
know
just
keep
on
keeping
on
as
as
you
want
to,
and
what
I'm
curious
about
is
that
there's
things
that
people
who
are
listening
in
here
think
that
we
should
be
adding
to
the
documentation.
C
B
A
No,
that's
explaining
I
I
did
this
was
awesome
again,
andrew
because
you're
I
I've
noticed
that
first
timers,
whether
it's
okd
or
openshift,
the
the
docs,
can
really
lead
you
astray,
so
diane.
I
think
this
is
a
great
effort
to
have
maybe
more
streamlined
or
verbose
documents
on
deployment
of
okd,
because
it
it
you
know
you
you
explaining
the
process
is
kind
of
what's
missing
in
some
of
the
documentation
andrew
yeah.
B
Yeah,
so
I
I'll
also
say
that
so
it's
funny
my
team,
the
tech
marketing
team,
we
have
a
bi-weekly
meeting
with
the
ux
group
where
they
just
go
through
and
say
hey.
This
is
what
we've
been
working
on.
You
guys
interact
with
a
lot
of
customers.
What
do
you
think
so?
One
of
the
things
that
we've
been
trying
to
set
up
is
basically
the
same
thing
with
the
docs
folks.
B
C
Our
documentation
is
always
a
work
in
progress.
I
think
this
we're
going
to
try
and
do
these
hop-in
sessions
there's
some
variation
like
once
a
quarter,
and
I
think
we're
also
going
to
try
on
thursdays
to
have
like
open
office
hours
for
okd,
that
is
that
are
all
community
driven.
So
this
has
been
this.
C
I
would
love
to
get
one
product
manager
from
the
openshift
team
to
to
come
on
a
regular
basis
to
these
just
to
hear
some
of
the
things
that
people
are
doing
and-
and
I
think
a
lot
of
the
pms
are
also
deploying
home
labs
and
things
like
that,
and
I
think
I
heard
a
a
threat
that
all
of
them
have
to
manage
the
internal
cluster
for
a
period
of
time.
Each
pm.
It's.
B
Not
it's
not
a
threat,
it
is
a
reality
yeah.
We
actually
right
now
we're
going
through
a
process
of
pairing
product
managers
with
tech
marketing
managers,
because
I
love
our
product
managers
and
they
are
extremely
knowledgeable
and
deeply
technical
on
their
focus
areas
and
having
them
branch
out
and
learn
more
about
openshift
as
a
whole
is
nothing
but
amazingly
positive.
So
I've
already
seen
some
benefits
there.
B
C
C
As
a
monday
morning
at
my
house,
I
will
be
able
to
upload
them
on
wednesday
or
on
monday
afternoon,
so
look
for
them
there
and
I'll
make
a
post
of
the
mailing
list
when
they're
there,
but
this
stuff
is
just
hugely
useful
for
everybody
and
just
really
grateful
for
you
guys
time.
So
I'm
going
to
leave
you
to
finishing
this,
go
pop
into
the
other
session
and
see
how
they're
doing
and
then
I'll
pop
back
here
and
we'll
just
keep
going
back
and
forth
until
you
finish
your
deployment
here.
Okay,.
B
While
we
were
chatting
there,
if
you
were
watching
my
screen,
I
found
out
where
the
issue
with
the
the
single
worker,
zero
name,
is
here
so
up.
When
I
was
doing
this
variable
assignments,
I
did
not
replace
that
one
which
then
propagated
down
into
the
others,
so
they
do
have
distinct,
ips
right
all
that
other
stuff.
They
just
have
the
same
hostname.
I
don't.
I
don't
know
how
that's
affecting
opensh
or
okd
it
may
may
not
like
it.
It
may
be
okay
with
it.
B
B
B
B
B
B
B
So
what
I
need
to
do
is
because
you
can't
really
change
the
ip
address
or
hostname
of
an
a
coreos
node
easily.
Really
the
recommendation
is
treated
like
an
appliance
blow
it
away
right
and
and
reload
it.
So
that's
exactly
what
I'm
going
to
do
so,
I'm
just
going
to
rather
than
doing
it
all
automated
from
the
cli
like
I
did
before.
I'm
just
gonna.
Do
it
manually
from
here
so
I'll
paste
this
guy
in
here
and
then
jump
back?
B
B
A
B
B
C
C
A
B
A
moment
you
can
see
so
it
started
and
installed,
and
then
it
stopped.
So,
let's
flip
this
back
to
restart
and
apply,
and
then
on
our
boot
options.
We
uncheck
this
and
apply,
and
then
we'll
start
our
node
and
just
like
during
the
install
process.
What's
going
to
happen
is
it'll
turn
on
it'll
come
up.
It
already
has
its
network
config
and
everything
it'll
look
to
the
machine
config
operator
so
that
api
ends.
B
You
can
see
it
trying
to
get
to
it
from
here,
so
it
pulled
down
its
ignition
config
and
now
it's
going
through
and
it's
trying
to
it'll
reconfigure
itself
here.
In
a
moment
it
will
reboot
again
because
it
pulled
down
a
new
rpmos
tree.
So
it's
going
to
flip
over
to
the
new
one
and
then
we'll
reboot
and
then
at
that
point
is
windows.
We
should
have
to
approve
the
csr
for
to
join
the
cluster,
but
that'll
take.
B
Console's
up
you
can
see,
we
do
have
a
degraded
operator,
that's
the
ingress.
So
remember,
I
said
with
only
one
worker
node
it
will
deploy.
He'll
just
have.
The
ingress
will
be
angry
because
there's
it
wants
by
default,
to
be
scaled
to
two,
and
that
means
that
there
needs
to
be
two
worker
nodes
available
for
it.
A
So
this
is,
this
is
great.
I
I
think
this
is
where
I
totally
get
that
you
wanted
to
see
that
second
worker
node
up,
but
you
successfully
showed
us
the
deployment
of
okd.
I
think
we
had
some
good
questions
so
far.
Any
questions
that
folks
have
that
just
joined
us
or
have
been
sticking
with
us
from
the
get-go
about
the
install
to
to
we
used
andrew
use
fedora
here
any
any
questions
that
still
don't
make
sense.
B
B
B
C
B
B
So
in
my
when
I
normally
because
I
turn
through
especially
openshift
clusters,
sometimes
three
or
four
a
day
when
I'm
creating
demos
and
stuff
like
that,
so
all
I
have
to
do
is
turn
on
my
vms
and
then
hit
escape
and
tell
it
to
pixie
boots
and
walk
away
from
it
and
come
back
and
half
an
hour
later.
I
have
a
fully
new
cluster,
that's
been
deployed,
so
you
can
absolutely
have
it
to
do
that.
So
if
we
do
a
cat
on
the.
A
B
See
how
I
have
a
pending
one.
So
if
you
were
again
quick
guide
with
my
worker
one
here
see:
oh,
it's
only
been
up
for
like
30
seconds.
My
my
cursor
disappears,
but
it's
only
been
up
for
a
minute
or
two,
because
it
it
booted
and
then
it
got
the
new
rpm
os
tree
image
and
then
applied
that
and
rebooted,
and
then
it
came
up
and
now
it
wants
to
join
the
cluster.
B
So
now
I
need
to
approve
this
csr
I'll.
Do
a
find
my
xox
thing
here
so
I'll
approve
that
csr.
So
we
can
see
here
the
pending
one,
so
this
is
node
bootstrappers,
the
first
thing
that
will
request
one
for
each
new
node
and
then
we'll
give
it
a
second
and
we
should
see
another
pending
show
up
after
just
a
second
and
these
csrs
they
do
disappear
after
I
think
24
hours
they'll
automatically
disappear
from
the
list
there
here's
our
pending-
and
we
see
it's
for
worker
one
this
time.
C
B
B
B
B
If
we
look
here
so
yes,
this
is
also
upset.
That's
because
we
just
added
the
new
node
and
therefore
it's
going
through
and
all
of
those
operators
are
going
to
adjust
for
the
new
node
and
deploy
additional
services
once
that
new
node
is
fully
joined,
it'll
go
back
into
a
healthy,
happy
status
and
it'll
be
ready
to
go
one
thing
to
note
with
4.7.
B
C
B
B
B
B
A
B
Yeah,
really,
the
the
only
investment
quote
unquote
that
I
did
is
an
nvme
device.
I
think
I
spent
eighty
dollars
on
a
512
gigabyte,
nvme
device,
pcie
nvme
device
just
make
sure
that
your
motherboard
is
capable
of
plugging
those
in
and
it's
it
sold
all
of
the
performance
deployment
issues
right.
You
saw
it
took
us
what
less
than
30
minutes
total
to
deploy
the
cluster.
A
Authorization
to
purchase
that's
great
yeah,
so
I
don't
see
any
more
questions
in
the
chat
and
the
the
cluster
is
up
you.
You
showed
us
that
I
think
we
had
a
great
chat
back
and
forth
and
totally
understand
about
the
document
wanting
to
get
that
up
to
so
that
other
people
can
can
run
through
this.
It
would
be
great
because
I
think
it's
very
clear,
well
written
and
now
they
have
this
recording
to
step
through
it
as
well.
If
they
have
a
question.
C
Yeah,
I
think
this
this
was
excellent.
This
is
this
is
like
the
perfect
way
to
end
the
end
the
day
with
this
up
and
running,
and
I
think
you
guys
nailed
it
on
the
head
here.
So
thank
you
so
much
for
taking
the
time
today
I
I
know
it's
a
saturday
it
may
we
may
all
be
down
in
lockdown
and
that,
but
I
you
know,
you
still
need
to
go
out
for
a
walk
and
get
some
fresh
air.