►
From YouTube: Ask an OpenShift Admin (Ep 48): Disconnected Deep Dive
Description
What is a disconnected OpenShift installation and why would you need one? In this episode, we take a deep dive into disconnected and look at deploying a disconnected OpenShift cluster. Disconnected installations of OpenShift Container Platform occur when the OpenShift cluster is not connected to the Internet, but there are a few other differences that come into play as well. We'll discuss mirror images, disconnected Operators, and learn whether a cluster actually needs to be disconnected to install disconnected. We'll also examine ImageContentSourcePolicy and how to reconnect a detached cluster. Please join to learn more and ask us anything about disconnected OpenShift.
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Chris Short sit down to answer your questions about Red Hat OpenShift.
Follow us:
Andrew Sullivan , https://twitter.com/practicalandrew
Jonathan Rickard, https://twitter.com/jrocktx1
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
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.com https://red.ht/33Fh6uV
OpenShift on github https://github.com/openshift/
OpenShift on redhat.com https://red.ht/2o4ccDk
#RedHat #OpenShift #ContainerPlatform
A
B
Yeah,
it's
it's
funny.
We
were
both
talking
about
how
it's
been
a
crazy
week.
You
know
you've
switched
roles
right
you're
now
fully
in
your
new
role.
I
I've
been
just
running
all
out
because
I
don't
know
it's
november
and
for
some
reason
november
is
just
a
a
good
day
to
be
or
a
good
time
to
be
busy.
A
A
B
B
So
if
you
all
remember
when
bobby
was
here
and
all
of
that
other
stuff
that
that
group
of
folks
created
that
I
think
was
actually
played
for
red
hatters,
I
think
it
was
played
during
one
of
our
all
hands
sessions.
Maybe
during
one
of
the
shows
something
like
that
and
then
the
second
one
was
created
by
our
creative
team.
So
behind
the
scenes
our
producer
stephanie
worked
and
got
all
that
stuff
done.
So
I
can't
compliment
her
enough
on
just
how
professional
she
makes
us
a
bunch
of
amateurs.
B
B
So
this
week
this
week
is
a
bit
different.
If
you
noticed,
if
you're
subscribed
to
the
streaming
calendar,
we
extended
this
one
to
two
hours
and
the
reason
for
that
is
because
of
our
topic
today.
Our
topic
is,
of
course,
disconnected
installs,
and
specifically,
we
want
to
do
a
deep
dive
and
this
topic
came
at
special
request.
B
For
some
of
you
may
remember,
I
went
to
an
in-person
event
for
the
first
time
in
about
two
years,
which
was
the
red
hat
summit
connect
here
in
raleigh
and
one
of
the
folks
there
who
works
on
what
we
lovingly
refer
to
as
the
synergy
team
they
had
asked
me
like
hey,
you
know
we're
doing
a
lot
of
and
seeing
a
lot
of
disconnected
installs.
Can
you
do
a
deep
dive
on
that
and
it
just
so
happens
that
johnny
is
an
expert
here.
B
Yeah,
it's
you
know,
constantly
changing,
there's
little
nuances
stuff
like
that,
so
I
know
we
had
reached
out
to
the
product
management
team.
There's
some
stuff
in
the
pipeline.
That's
going
to
make
this
a
lot
better.
We
just
can't
show
it
yet.
I
will
make
some
allusions
to
it
and
if
I
can
remember
what
the
github
repo
is
johnny,
if
you
happen
to
remember
the
one
that
they
pointed
us
to
for
the
disconnected
registry
mirror,
we
can
show
that
in
a
little
bit
I
forgot
to
grab
the
link
before
we.
B
Yeah
we'll
talk
about
all
that
stuff.
My
goal
here
today
is
to
kind
of
walk
through
the
different
phases
of
a
disconnected
install
so
for
a
long
time,
viewers
long
time
watchers,
you
may
remember-
we
talked
about
this
way
back
in
episode
13.,
but
that
was
just
an
hour
long
and
it
was
crammed
in
with
a
bunch
of
other
stuff.
So
I
think
I
got
as
far
as
like
kicking
off
the
install,
but
never
actually
finished
so
hopefully
this
time
we
can
get
through.
B
So
oh
hey,
christian's,
here
christian.
I
hope
you
can
see
because
I
wore
this
shirt
special
for
you
right.
Do
you
see
my
shirt
here?
It
says
I'm
a
few
records
shy
of
a
dns
zone
so
that
one's
for
you,
because
you're
you're,
my
favorite
dns
expert
okay.
So
all
of
that
being
said,
thank
you
for
the
for
the
compliments
on
the
intro
appreciate
it
everybody.
B
So,
essentially,
when,
when
it's
the
current
release,
it's
under
full
support
once
it
moves
off
from
being
the
current
release,
so
when
4.9
was
released,
theoretically,
there's
a
an
overlap
period
of
a
few
weeks
or
a
month
and
then
4.8
rolls
into
maintenance
phase
and
then
once
four
dots
well,
whatever
three
versions
later
so
four
dots
for
talking
4.7,
so
four,
eight,
four
nine
so
once
410
is
released,
four
seven
would
then
roll
off
and
become
unsupported,
so
nothing
has
really
changed
in
that
respect.
Right,
it's
always
been
the
policy.
B
B
What
we
should
see
here
is
this
maintenance
support,
and
this
kind
of
this
breaks
down
the
differences.
I'm
not
going
to
sit
here
and
read
it
and
or
anything
like
that,
but
it
should
describe
the
differences.
What
those
are
technically,
I
I
don't
honestly
know
you
know
I
can
see
here
qualified,
critical
and
important
security,
advisories,
qualified,
critical
and
important
security
advisories.
B
B
B
B
So
with
that
change,
we
moved
to
it
being
time
frame
based,
so
it
is
for
18
months,
regardless
of
how
many
releases
are
inside
of
there,
although
it
should
coincide
with,
I
think
it's
four
releases
with
the
the
yearly
or
maybe
five
releases,
five
releases
with
the
yearly,
because
now
I'm
remembering
mike
barrett's,
blog
post,
so
I'll
put
a
link
to
that
in
the
blog
post.
That
goes
out.
B
If
all
releases
are
supported
for
18
months,
you
might
be
thinking
to
yourself.
Well,
then,
why
are
some
of
these
called
eus
eus
usually
means
that
it's
supported
for
longer
than
whatever
that
period
of
time
is
so.
The
eus
is
one
in
the
immediate
term,
starting
with
4.8,
with
the
update
to
4.10
you'll
be
able
to
do
an
accelerated
update.
B
So
basically,
what
that
means
is
that
you
will,
when
you,
when
you
choose
that
option,
the
control
plane
will
update
from
4.8
to
4.9
to
4.10
linearly
because
it
has
to,
but
we
will
pause
the
worker
nodes
so
that
they
only
go
straight
from
4.8
to
4.10.
So
it's
basically
only
one
reboot
for
all
of
the
worker
nodes
which
can
dramatically
shorten
the
amount
of
time
needed
for
an
update
so
longer
term
those
even-numbered
eos
releases.
B
If
we
have
the
opportunity
to
extend
support
beyond
18
months,
it
would
happen
with
those
even-numbered
eos
releases.
So,
for
example,
let's
say
that
you
know
api
stability
or
whatever
it
is
that
they
use
to
measure.
That
is
where
they
want
it
to
be,
and
you
know:
hey
yeah,
let's,
let's
go
ahead
and
extend
support
to
24
months
or
whatever.
That
is
that
would
happen
with
those
even
releases
so
I'll
I'll
dig
up,
maybe
on
the
side
here
mike
barrett's
blog
post
on
blog.orgcloud.openshoe
cloud.redhat.com
man
I'll
get
it
right
eventually.
C
B
That
over
here
in
the
chat,
so
this
blog
post
from
mike
baird
goes
through
all
of
this
in
excruciating
detail.
If
you
have
any
questions
about
this,
don't
don't
hesitate
to
reach
out.
You
can
always
contact
me
here
through
chat.
If
you
happen
to
be
watching,
you
can
also
contact
me
social
media
at
practicalandrew
on
twitter,
or
you
can
send
me
an
email,
andrew.sullivan
redhat.com.
B
C
B
If
you
click
this
google
calendar
down
here
in
the
corner,
it'll
open
your
google
calendar,
I'm
not
signed
into
an
account,
but
if
you
are
it'll
open
that
google
calendar-
and
you
have
the
option
to
subscribe
to
that,
if
you
so
choose
or
just
bookmark
the
calendar
so
that
you
can
see
it
whenever
or
bookmark
this
page,
this
page
is
it's
a
good
one
right.
We
have
links
to
the
youtube
channel.
B
We
also
have
all
of
the
other
streams
that
are
available
here
so,
along
with
all
of
the
other
stuff,
that
the
new
media
team
is
working
on,
so
lots
of
great
stuff.
I
definitely
recommend,
if
you
don't
bookmark
the
calendar
subscribe
to
the
calendar
at
least
bookmark
this
page,
so
you
can
keep
up
with.
What's
going
on,
oh
johnny,
thank
you
for
posting
that
image
or
that
link
rather
we'll
take
a
look
at
that
in
a
few
minutes.
B
Faced
a
lot
of
issues,
while
downloading
operators
for
external
registry
using
pruned
index
images.
Yes,
I
sympathize
with
that.
I
was
going
through
this
yesterday
as
I
was
trying
to
get
ready
for
this
particular
stream
johnny,
and
I
were
chatting
back
and
forth
because
we
were
both
having
infrastructure
issues
so
me
due
to
a
misconfiguration
and
johnny
due
to
his
isp
being
flaky.
I
don't
know
what
it
is
about,
my
co-hosts
and
and
flaky
internet.
I
got
nothing
so
I
think
I've
got
that
resolved,
we'll
walk
through
that.
So
the
good
news
is.
B
I
went
through
and
documented
everything
that
I'm
going
to
show
today
in
a
in
a
markdown
document,
and
my
goal
is
to
put
that
up
onto
github
after
the
stream
and
then
we'll
link
that
from
a
blog
post.
So
everything
that
you
see
here
and
probably
more
will
be
available
there
and
you
can
always
reach
out
and
ask
questions
about
that.
B
We've
been
doing
this
for
a
number
of
years
and
that's
kind
of
where
our
expertise
lies.
So
we
are
here
to
answer
those
questions,
and
usually
we
do
that
again.
You
can
ask
anything
that
you
would
like,
regardless
of
what
topic
that
we're
talking
about
for
the
day,
but
we
also
have
a
theme
or
a
topic
for
the
show.
So
that
way
we're
not
holy,
and
only
you
know
we're
not
sitting
here
staring
at
each
other
and
waiting
on
you
all
all
the
time
we
also
have.
B
B
B
B
So
if
you
have
been
to
the
openshift
documentation
page
recently-
and
let
me
refresh
it
here
if
you've
been
to
that
page
recently
within
the
last
few
days,
you'll
notice
that
it
looks
a
little
bit
different,
so
they
they
did
their
best
and
and
really
the
goal
here
was
to
improve
the
overall
experience
with
the
docs
to
make
it
as
friendly
as
possible.
So
you
noticed
some
little
things
like
this
side.
Menu
now
scrolls,
independently
of
the
rest
of
the
page,
hey.
B
B
I
can
only
I
can
only
paint
so
much
of
a
picture
with
words
right.
So
the
page
we're
looking
at
here.
This
is
just
the
docs
landing
page
for
4.9.
They
retroactively
applied
the
formatting
to
all
of
the
docs
versions,
but
you'll
see
things
like
this
side
menu
here,
scrolls
independently
of
the
content
window.
If
we
click
on
one
of
these
here
we'll
pick
on
this
one,
because
it's
relevant
for
today
see
our
center
section
scrolls
independently.
We've
got
a
table
of
contents
over
here,
that's
much
easier
to
use
and
find
things.
B
So
this
is-
and
I
think
I've
mentioned
before
that
I
I
have
or
tried
to
have
kind
of
regular
meetings
with
our
docs
team.
So
this
is
just
one
step
or
one
one
phase
of
the
improvements
that
they're
working
on
that
team
is
really
great
about
really
trying
to
take
into
account
the
things
that
you
all
have
your
opinions,
your
perspectives,
usability
stuff
like
that,
so
don't
ever
hesitate
to
send
that
feedback
either.
You
can
send
it
to
me,
I'm
happy
to
pass
it
on.
B
B
So
I
think
it
was
our
hope.
Nine.
I
don't
know
if
you're
on
today,
but
you
had
sent
me
some
messages
asking
about
some
features
in
service.
Mesh
kind
of
all
dependent
on
2.1,
well,
2.1
is
released,
so
if
you're
using
service
mesh
definitely
take
a
look
at
all
of
the
things
that
are
inside
of
here,
I
will
admit
that
service
mesh
is
one
of
those
things
that
I
am
not
super
familiar
with.
B
So
I
cannot
necessarily
answer
a
lot
of
questions
about
it,
but
I
will
certainly
try
my
best,
which
brings
me
to
an
excellent
point,
which
is:
if
we
don't
know
the
answers
you
know
johnny
and
andrew
only
knows
so
much
we're
more
than
happy
to
go
and
find
those
answers
for
you.
So,
even
if
it's
something
like
service
mesh
that
I
don't
know
a
whole
lot
about
some,
I
don't
know
about
johnny,
I'm
happy
to
take
those
and
we'll
figure
it
out
aj.
B
B
B
B
So
last
week
openshift
virtualization
released
their
version
4.9,
so
their
versions
tend
to
match
the
version
of
openshift
that
they
are
associated
with,
and
the
integration
team
here
posted
a
couple
of
things
that
are
interesting
that
are
coming
out
of
this
particular
release.
So
one
hot
plug
discs,
two
is
mtv.
There
was
an
update
to
mtv
and
three
sysprep.
This
one
is
particularly
interesting
to
me
because
I
was
just
doing
some
work
with
windows
nodes
and,
while
I
don't
know
how
about
sysprep,
I
know
that
it
is.
B
B
If
you've
used
openshift
virtualization
previously,
like
you'll,
you
might
be
able
to
see
if
you
squint
a
little
bit
this
ssh
service
like
there's.
Now
you
can
upload
your
your
public
key
into
a
secret
and
then
we'll
automatically
add
that
to
linux
virtual
machines
that
are
using
cloud
init
it'll
automatically
create
a
service
so
that
you
can
ssh
into
the
virtual
machine
and
all
that
other
stuff,
so
they're
really
making
improvements
on
the
usability
there.
B
A
B
B
It
seems
like
why
wasn't
that
there,
but
when
you
think
about
it,
their
mantra
is
kubernetes
native
virtualization
and
if
you're
trying
to
add
a
disk
to
a
running,
you
know
a
pv,
essentially
add
a
pvc
to
a
running
pod,
that's
not
possible,
so
they
work
some
magic.
I
I
I
have
no
idea
how
it
actually
works,
where
you
can
add
a
pvc
to
the
pod,
so
interesting
stuff,
that's
going
on
there,
I'm
looking
forward
to
diving
into
it
a
little
bit.
B
All
right,
I
think
that
is
all
of
the
stuff
that
I
had
for
today,
at
least
for
the
top
of
mind:
topics
yeah,
that's
all
I
got
on
my
list
so
disconnected
disconnected.
Is
it's
an
interesting
topic?
It's
an
interesting
problem.
If
you
will
of
you
know
hey,
I
have
this
isolated
network,
or
maybe
it's
not
isolated.
B
And
when
you
think
about
this,
it
can
be
a
little
bit
complex
and
a
little
bit
intimidating,
especially
if
we
look
at
the
documentation
right.
So
let's
come
over
here
to
the
documentation.
You
know
I
was
just
showing
this
documentation.
Page
and
you'll
notice
that,
like
this
is
a
this
is
a
long
page
right.
This
is
this
is
a
lot
of
stuff
and
this
is
just
to
mirror
the
content.
B
This
isn't,
you
know
doing
all
the
other
steps
that
are
associated
with
it.
So
I
want
to
walk
through
and
you
know
look
at
a
bunch
of
different
aspects
of
this.
You
know
I,
like
I
said
I
went
through.
I
stepped
through
this
again,
so
it's
been
a
little
bit
since
I
did
a
disconnected
install,
so
I
went
through
and
stepped
through.
All
of
these
things.
I
want
to
look
at
some
other
things
like
the
openshift
update
service,
mirroring
registry
catalogs.
B
A
C
B
So
when
we
think
about
deploying
a
cluster,
you
know
we
think,
okay.
Well,
I
need
to
create
my
install
config.
I
need
to
generate
my
ignition
files.
I
need
to
deploy
my
you
know,
virtual
physical
machines
and
then
I
go
and
instantiate
the
cluster
and
then
some
magic
happens
behind
the
scenes
and
you
know
roughly
20
to
40
minutes
later.
I
have
a
cluster
that's
up
and
running
so
for
the
most
part,
none
of
that
changes
right.
The
actual
install
process
is
effectively
the
same.
B
Where
it
gets
a
little
complex
is
that
well
we
need
to
make
sure
that
all
of
those
resources
that
it's
using
in
the
background
so
remember,
open
shift
is
kubernetes
that
has
olm
installed
to
it
operator,
lifecycle
manager
and
then
a
specific
operator
cvo.
The
cluster
version
operator
basically
works
to
pull
in
all
of
the
container
images,
all
of
the
things
that
are
openshift
and
deploy
them
to
that
kubernetes
cluster,
converting
that
kubernetes
from
well
kubernetes
into
openshift.
B
So
all
of
those
container
images
that
are
openshift
need
to
be
made
available
in
that
disconnected
network.
So
that's
kind
of
step,
one!
That's
getting
the
deployment
done
and
being
able
to
just
stand
up
a
cluster
step.
Two
is
deploying
useful
software
from
the
red
hat
operator
catalog
into
that
cluster.
B
B
So
this
was
released
in
the
4.8
time
frame,
4.74.8
time
frame
and
it
effectively
mimics
the
same
service
that
we
have
on
the
internet.
Coming
from
red
hat
for,
if
you're
using
a
connected
cluster
right,
you
can
go
into
the
admin
console
and
you
can
say,
update
cluster,
and
it
has
that
nice
channel,
where
oh,
I'm
on
4.9
stable.
I
want
to
go
to
whatever
the
next
one.
In
the
4.9
stable
channel
is.
A
B
B
So
please,
let
me
know
if
it's
just
completely
not
legible.
You
know
completely
unusable
and
we'll
take
more
drastic
measures,
but
hopefully
that'll
resolve
itself
here
in
a
little
bit,
yeah
even
switching
tabs
see
that
one
looks
okay,
maybe
no,
that
one's
a
little
blurry
too,
all
right
I'll,
forge
ahead,
but
johnny.
Just
let
me
know
if
I
need
to
drop
and
rejoin,
I
can
zoom
in
a
little
bit.
B
All
right,
yeah
welcome
back
to
240p,
let's,
let's
hope,
not,
okay,
let
me
I'm
going
to
close
from
the
stream
and
I'm
going
to
rejoin
and
see
if
that
helps.
So,
let's
stop
sharing
that
and
I
will
turn
off
my
camera
and
audio
so
johnny.
If
you
don't
mind
doing
a
little
dance,
I'll
be
back
in
10
seconds.
A
Okay,
cool
yeah,
so
where,
where
andrew
was
kind
of
you
know,
trying
to
get
to
was
the
open
shift
update
service
and
it's
using
the
cincinnati
operator
which
it
you
know
when
you
have
in
a
disconnected
environment,
you'll
build
out
like
a
graph
image
and
what
that'll
do
is
it'll.
Allow
you
to
see
like
your
update
path.
So,
if
you're
on,
like
a
specific
version
of
4.7
or
4.8
it'll,
tell
you
like
you
know,
you
can
update
to
this
path.
B
All
right
well
strange
browsers.
I
I
got
nothing,
I'm
afraid
to
look
at
at
my
memory,
utilization
or
whatnot
on
on
the
browser,
it's
probably
through
the
roof,
and
that
might
be
the
contributing
factor,
because
I
have
a
lot
of
things
open,
anyways,
please
let
me
know
if
that
happens
again,
we'll
we'll
figure
out
how
to
address
that
all
right.
So
let
me
close
out
some
things
here,
so
I
can
refocus
all
right.
B
So,
as
and
my
apologies,
I
lost
all
the
chat
when
I
disconnected
and
reconnected,
but
as
somebody
was,
was
highlighting
right
mirroring.
Those
operators
is
a
little
bit
confusing
because
it's
not
just
mirror
the
container
images.
It's
mirrored
the
catalog
that
operator
lifecycle
manager
uses
to
you
know
be
aware
of
those
things.
B
So
what
I
want
to
do
is
show
how
to
prune
that
down,
because
if
you've
ever
tried
this
before,
if
you've
ever
mirrored
the
entire
operator
catalog,
it's
something
like
350
gigabytes
and
not
all
of
the
operators
are
supported
disconnected.
So
we
can
prune
that
down.
We
can
cut
it
down
to
well.
In
my
test
the
smallest
I
got,
it
was
14
gigabytes,
but
that's
better
than
350
for
sure.
A
B
C
B
All
right,
so,
let's
get
started.
Let's
look
at
a
couple
of
things
here,
so
the
first
thing
that
we
want
to
do
is
mirror
that
data
over
and
if
we
come
up
here
in
the
documentation
to
installing
and
mirroring
images
effectively,
I'm
going
to
be
going
through
and
following
this
documentation,
the
difference
is
that
I've
actually
created
a
couple
of
bash
scripts
to
make
this
helpful
for
me.
So
what
I'm
going
to
show
in
just
a
moment
is
if
we
scroll
down
here
to
the
actual
mirroring
of
the
content.
B
So
what
I've
done
here
is
basically
take
all
of
these
commands
and
drop
them
into
a
single
script.
So
that
way,
it's
just
easier
for
me
to
be
able
to
do
this
in
a
repeatable
manner
and
then,
at
the
end
of
all
of
this,
we
get
down
here
to
step
three
and
you'll
notice.
A
couple
of
things
here
so
one
this
first
sub
bullet
is
if
your
mirror
host
does
not
have
internet
access.
So
basically,
if
you're
going
to
a
disconnected
installation,
fully
disconnected
installation.
B
This
is
the
set
of
steps
that
you
want
to
follow,
whereas
down
here,
if
the
host
that
you're
using
so
you're
what
I
call
a
bastion
host,
if
it's
straddling
between
connected
and
disconnected,
then
you
can
basically
use
that
bastion
host
that
admin
host
to
pull
images
from
one
side
and
push
them
to
the
other
side
and
then
from
there.
We
we
go
through
and
do
all
of
the
regular
installation
stuff.
C
B
Okay,
so
just
to
try
and
eliminate
as
much
confusion
as
possible.
This
is
the
normal
host
that
you'll
see
me
use
so
anchor
you'd
see
the
prompt
is
green
with
a
little
bit
of
yellow
or
blue,
or
excuse
me
yellow,
green
or
red,
depending
on
the
outcome
of
the
last
command,
and
then
this
one
over
here,
which
is
going
to
be
all
white
and
named
bastion.
B
B
B
I've
got
a
number
of
different
scripts
inside
of
here,
so,
let's
first
look
at
this
dry
run.
The
dry
run
is
that
first
command
that
we
run
under
step
three
and
you'll
notice
that
it
basically
mimics
everything
that
we
want
to
do,
including
this
to
release
image
line
and
you'll
notice
that
that
has
this
local
registry,
which
is
intended
to
be
your
destination
registry.
B
So
let's
say,
for
example,
that
you
you
know
your
host
names
are
sensitive,
for
whatever
reason
you
you
don't
want
to,
you
know
even
type
those
into
your
connected
machine.
That's
perfectly
fine!
Just
use
dummy
values.
Inside
of
here,
it's
not
going
to
actually
try
and
push
anything
or
anything
like
that.
It
just
uses
those
at
this
phase
for
the
dry
run.
It
just
uses
those
for
those
image
content,
source
policies.
B
So
all
I
did
here
as
I
kind
of
walk
through
in
the
documentation
there.
Here's
all
of
my
environment
variables
that
we
set,
and
then
I
execute
our
our
command.
So
this
dash
a
this
is
our
credentials.
So
this
would
point
to
my
pull
secret
that
I'm
going
to
use
so
just
like.
If
you
were
to
go
to
console.redhat.com
openshift,
you
grab
your
pull
secrets,
store
it
in
a
file.
That's
exactly
what
you
want
to
use
here
from
there.
We
just
build
out
this
quay.io
url,
using
the
parameters
up
here.
B
Documentation
walks
through
examples
for
each
one
of
these.
I
selected
494
for
my
ocp
release.
So
two
again,
this
is
based
off
of
those
temporary
things.
Right.
These
don't
have
to
be
real
values.
They
can
be
fake
values
if
you
don't
want
to
post
those
in
because
this
is
just
the
dry
run
and
we'll
look
at
the
actual
mirror
command
here
in
just
a
moment.
B
You
know,
pull
down
then
digest
all
the
metadata
do
all
the
stuff
that
it's
got
to
do
and
what
we're
going
to
end
up
with
here
is
it's
going
to
scroll
by
a
ton
of
information,
it'll
list
out
every
single
image
it'll
list
out
how
big
each
one
is:
it'll
list
out
the
sha.
You
know
here
all
of
that
information
about
each
one
of
these
images.
B
B
The
object
down
here-
and
this
is
a
kubernetes
yaml
object.
If
I
had
a
cluster
that
is
disconnected
or
excuse
me
connected
today,
and
I
wanted
to
change
it
so
that
it
is
going
to
pull
all
of
this
content
from
my
mirror,
so
whether
it's
a
connected,
mirror
or
disconnected
mirror.
This
is
what
I
would
do
so
this
is
particularly
useful
if
maybe
like
johnny
you've
got
a
less
than
reliable
internet
connection.
B
I
better
knock
on
wood.
I
like
I'm,
going
to
jinx
myself
here.
So
if
you
have
maybe
a
less
than
reliable
internet
connection,
maybe
your
throughput
isn't
great.
You
know.
Lots
of
edge
sites
have
limited
throughput
stuff,
like
that.
Maybe
you
just
don't
want
to
download
nine
gigabytes
of
data
for
every
openshift
cluster
that
you
deploy.
You
know
if
you're,
downloading
or
you're
deploying
you
know
two
five.
Ten
a
hundred
clusters.
That's
a
lot
of
data
to
pull
across
your
internet
pipe,
so
you
can
mirror
all
of
that.
B
You
can
point
everything
over
to
here.
This
format
is
also
good
because
you
can
use
it
to
kind
of
blanket
redirect
so
we'll
we'll
talk
a
little
bit
about
that,
hopefully
I'll
be
able
to
go
into
our
node
and
look
at
what
this,
what
this
configures,
because
it's
basically
configuring
or
setting
the
registries.com
file
on
the
node.
So
if
you
have,
for
example,
a
caching
registry,
you
can
point
everything
by
default
to
all
go
through
that
caching
registry
and
then
it
will
take
care
of
that.
B
B
B
So
remember,
if
I
put
it
in
here
or
not
anyways,
I
can
pull
it
later
if
we
happen
to
need
it,
because
what
I
want
to
move
on
to
is
the
mirror
much
like
before
I
followed
the
documentation
exactly
so
just
like
you
would
copy
and
paste
this
or
type
it
in
on
the
command
line
from
the
documentation.
I
did
the
same
thing
right,
openshift,
release
version
where
I
want
to
download
these
images
to
so.
B
In
my
case,
I
have
mounted
an
nfs
export
to
this
location
that
nfs
exports
doesn't
need
to
be
super
high
performance
or
anything.
You
know.
Obviously,
if
you
are
on
a
physically
air-gapped
network,
this
would
be
something
like
a
thumb
drive
or
a
usb
hard
drive
usb
ssd.
Whatever
that
happens
to
be
so,
you
would
want
to
download
all
of
that
information
into
some
location.
B
B
Kick
off
that
mirror,
and
I
don't
know
if
we'll
let
it
run
the
whole
time
here,
because
my
internet
is
well.
I
have
gigabit
internet,
it
still
takes
about
10
minutes
or
so,
and
I
don't
think
anybody
wants
to
just
stare
at
us
while
we
stare
at
a
screen,
so
I'll
probably
interrupt
it
here
in
a
little
bit
after
it
gets
going.
B
So
this
is
going
to
download
every
one
of
those
images
and
they're
going
to
land
in
the
directory
that
we
specified
here
so
remember,
it's
was
the
directory
that
I'm
in
slash
images
so
we'll
give
it
a
second
just
like
we
did
with
the
dry
run.
It's
doing
all
of
its
metadata
thing,
finding
out
all
the
information
about
it
and
then
it'll
begin
that
pull
operation.
B
B
B
Look
inside
of
here,
you
can
see
that
this
is
effectively
a
very
similar
layout
that
you
would
find
with
a
registry.
So
if
I
do
a
tree
inside
of
here
and
go
all
the
way
back
up
to
the
top,
we've
got
all
of
these
different
files.
Folders
rights-
these
are
links,
symbolic
links,
all
right,
all
of
the
information
that
we
have
for
each
one
of
those
container
images
and
do
a
quick,
dude,
actually
sh
in
here
it
comes
out
to
our
9.5
gigabytes
in
size
that
we
would
expect.
B
So
in
my
instance,
I
have
downloaded
these
things
into
this
other
directory.
So
basically,
in
my
hypothetical
situation
here,
everything
in
this
mirror
directory
that
I'm
currently
in
so
this
this
mirror
directory.
This
is
all
of
the
data
that
I
would
expect
to
move
over
to
the
disconnected
network.
So
I
also
did
this
for
4.8
we're
using
4.9
today,
but
the
other
one.
B
B
B
B
B
B
A
B
Yeah
nexus
jfrog,
jfrog
yeah,
so
there's
a
whole
bunch
of
them
out
there.
I
just
pulled
the
docker
registry
because
it
works
great.
It's
pretty
simple
and
easy
and
straightforward
to
get
up
and
running
so
we'll
need
that
on
our
disconnected
network.
Aside
from
that,
the
other
things
that
are
in
here
so
I've
got
openshift
install
and
the
openshift
client.
B
B
You
know
just
accessed
or
console.redhat.com
went
through
the
normal
download
process
to
get
those
so
openshift
install
oc,
cubecuddle
or
kubecontrol
all
as
a
part
of
those
packages,
our
registry
container
image
and
then
the
last
two
that
I've
got
here
is
our
coreos
install
iso.
So
remember
we
do
need
core
os
right.
We
have
to
have
something
to
install,
so
I
grab
the
iso
here
because
I'm
doing
single
node
openshift.
We
need
to
use
the
iso
for
that.
B
So
no
so
the
installer
won't
have
a
built-in
registry.
So
we
were
talking
johnny
and
I
were
talking
with
the
product
management
team
about
this
so
effectively.
What
they're,
working
on
and
johnny
posted
the
link
earlier
is
a
way
to
with
a
single
command
on
a
rel
host,
deploy
the
quay
registry
and
then
pull
all
of
that
data
into
it.
So
that
way,
you
have
you
know
a
very
quick
and
very
easy
way
to
do
everything
that
I've
shown
you
to
this
point
right.
B
B
B
B
B
So,
if
we
look
inside
of
disconnected,
you
can
see
it
is
the
exact
same
file,
folder
structure
that
we
had
on
the
other
one.
If
I
go
into
other,
for
example,
you
can
see
that
this
november
10th
at
11,
48
eastern
name.tar,
is
the
thing
that
we
just
created
so
literally
just
pretend
like.
I
mirrored
this
over
to
a
disconnected
network,
and
that
is
what
it
is
so
before
we
can
do
the
next
step.
B
B
B
B
B
The
reason
for
that
is
because-
and
you
can
create
just
a
traditional
common
name-
certificate
you'll
just
get
an
error
when
using
oc
against
it.
So
if
you
look
in
the
docs
there's
a
a
go,
environmental
parameter
that
you
set
and
it'll
ignore
those
errors.
Otherwise
oc
will
come
back
or
any
other
go
command
that
you
run
against.
It
will
come
back
and
complain
saying
that
hey
you
need
to
update
your
your
certificate
to
use
you
know
sans
so
and
I
will
validate.
So
if
I
do
a
curl.
C
A
And
if
I
can
do
a
shameless
plug
real
quick,
if
you're
looking
for
an
easy
way
to
create
a
certificate-
or
I
say
easy,
relatively
easy
way
to
create
a
certificate
with
the
sand,
look
at
ansible
with
the
openssl
modules,
because
then
you
can.
Actually
you
can
add
the
constraints
that
you
need
for
like
the
ca
equals
true
and
then
you
can
add
a
common
name
with
all
of
your
subject:
alt
names.
A
B
Yeah,
I
I
just
used
a
gui
in
my
in
my
router
that
has
that
I
cheated.
So
all
I'm
going
to
do
here
is
just
to
kind
of
prove
that
hey
this.
This
docker
registry
instance
is
up
and
running
with
a
certificate
right,
https
port
5000,
I'm
just
doing
a
very
simple
curl.
I
did
not
include
any
sort
of
authentication
on
this
registry.
B
Of
course
you
know,
depending
on
your
registry,
whatever
third-party
one
you're,
using
whatever
your
security
policy
is,
that's
probably
a
good
idea.
I
just
did
not,
and
you
can
see
that
when
I
query
that
it
goes
through
and
it
finds
all
of
the
certificate
stuff,
there's
no
complaints
or
anything
like
that,
and
then
it
spits
out
all
of
the
repositories
that
we
have
inside
of
there.
So
this
is
my
just
quick
and
easy.
You
know
cli
based
way
of
saying,
hey.
B
B
B
And
I'm
actually
going
to
use
this
with
4.8,
because
I
don't
want
it
to
interrupt
what
we're
going
to
do
later
in
case
it
does
a
partial
upload
and
corrupts
anything
like
that,
because
I'm
going
to
interrupt
it
as
well,
because
this
process,
while
downloading
it,
takes
me
about
10
to
15
minutes
uploading.
It
takes
closer
to
30
minutes
because
yeah.
My
the
storage
that
I'm
using
for
this
is
not
not.
B
B
So
you
notice
that
inside
of
here,
this
is
the
only
time
that
we're
using
that
local
registry
local
repository
information.
Again,
if
you
use
something
different,
when
doing
the
dry
run,
that's
fine!
It
has
no
meaning
at
this
point
so
just
make
sure
that
here
on
the
disconnected
network,
these
values
are
set
correctly.
B
So
let's
go
ahead
and
do
our
import
of
that
data,
and
oh
one
other
thing
that
I
wanted
to
highlight
here
notice
that
this
format
is
pretty
specific.
So
we
want
to
make
sure
that
it
points
to
the
same
location
right
this
base
location
that
it
mirrored
all
of
that
data
to
so
over
here
so
remember.
This
is
now
back
on
our
connected
network.
B
Do
our
mirror
so
in
our
mirror
our
removable
path?
Is
this
so
mirror
slash,
4.8
and
then
down
here,
because
I
copied
this
from
the
docs,
and
this
is
the
way
they
did
it.
They
appended
slash
images
moving
back
over
to
disconnected.
We
have
4.8
images
so
make
sure
you
use
that
path.
That'll
have
the
it
has
the
v2
folder
inside
of
it
and
then
it'll
import
based
off
of
that.
Okay.
So,
let's
run
our
import.
B
B
So
normally
this
would
go
through
and
it
would
be
literally
uploading
all
of
the
data
into
our
registry.
Again
it
takes
like
30
minutes
on
my
system
just
due
to
storage
performance,
not
for
any
other
reason.
Just
it's
using
spinning
disks
on
the
background,
not
just
any
spinning
discs,
5400
rpm,
spinning
discs.
B
So
now
all
of
our
data
is
accessible
from
a
registry.
On
the
disconnected
side,
there
is
a
way
that
I
don't
remember
off
the
top
of
my
head.
You
can
use
the
cli
to
search
for
essentially
this
repository
anything
that's
in
a
part
of
this
repository
using
curl
from
the
docker
registry.
I
don't
remember
it
off
the
top
of
my
head,
so
I
won't.
I
won't
cover
that,
but
if
you
needed
validation
of
everything
being
there,
that
is
one
way
to
get
it.
B
B
I'm
typing
what
I'm
saying
and
the
gzip
files
now
we're
back
to
where
we
started,
but
now
I
have
open
shift,
install
version
4.9.0.
Oh,
I
did
forget
I'll
I'll
talk
about
it
more
in
depth.
In
just
a
moment.
I
I
don't
have
it
in
these
notes,
because
I
referenced
my
other
one
for
doing
single
note,
open
shift
from
the
command
line,
but
we'll
also
need
core
os
install
and
there's
one
other
binary
that
we
need.
What
is
the
other
binary
that
we
need
anyways?
B
B
B
B
B
B
B
Excuse
me
this
when
it
connects
over
to
that
registry.
It
won't
throw
an
ssl
error
and
this
automatically
gets
added
to
the
cluster
at
deployment
time
as
well,
so
it'll
automatically
propagate
out
to
all
the
hosts
and
everything
else.
I
don't
have
to
do
anything
else
for
that,
so
that
is
an
important
one.
B
A
Yeah,
I've
actually
only
done
it
this
way
I
mean
we.
When
we
talk
to
our
customers,
we
essentially
kind
of
we
push
them
to
do
as
secure
as
possible.
One
thing
to
say
about
the
cert,
though,
is
that
when
you're
doing
a
self-signed
certificate,
I
kind
of
alluded
to
it
earlier,
but
you
have
to
have
a
the
ca
constraint
within
that
certificate.
A
B
Okay,
so
after
that
kind
of
moving
down
this
is
a
standard
install
config.
So
we've
got
our
networking
here.
You
can
see
I'm
going
to
use
ovn
kubernetes
I'll,
accept
the
defaults
for
service
network
for
cluster
network.
It's
only
a
single
node,
so
I'm
not
overly
worried
about
it.
I
do
set
my
machine
network
correctly
here
down
below
remember
this
is
single
node
openshift,
so
we
have
no
workers
and
only
a
single
master
or
a
control
plane.
Node
again,
single
node
means
that
we
use
platform
none.
So
I
was
corrected
by
the
way.
B
B
Networking
type
is
ovn.
Is
that
a
requirement?
It
is
not
a
requirement,
so
you
can
use
s
or
openshift
sdn.
If
you
would
like
I'm
I'm
trying
to
so.
We
changed
the
default
to
ovn
kubernetes
with
4.9.
So
I'm
I'm
trying
to
you
know
I'm
trying
to
be
brave,
I'm
trying
to
try
something
new,
but
I
get
it
if
you
want
to
stick
with
what
you
know
and
what's
comfortable
familiar,
and
so
one
thing
to
note
here,
my
pull
secret.
B
This
is
obviously
not
a
real
pull
secret.
I
don't
need
one
right.
Remember
how
I
said
that
I
didn't
configure
authentication
on
my
registry,
so
therefore
I
just
need
to
meet
the
format
requirements.
The
bare
minimum
format,
requirements
for
openshift
install
to
pass
the
check.
I
actually
stole
this
from
from
okd.
If
you
look
at
the
okd
docs,
they
tell
you
to
do
the
same
thing.
B
So
the
one
fancy
thing
to
note
here
is
that
I
have
this
little
copied
network
parameter
here
so
remember.
I
said
that
we're
going
to
do
a
static,
ip,
install
of
single
node,
open
shift,
and
the
last
time
when
we
talked
about
single
node
openshift,
I
kind
of
hand
waved
over
this.
A
little
bit
and
said:
oh
yeah,
it's
possible
to
do
a
static
ip
install,
but
I
didn't
go
into
any
detail.
B
So
it's
a
two-step
process
or
we'll
call
it
1.1
steps.
So
the
first
step
is-
and
the
point
one
is
to
add
this
parameter
here
to
installation
disk
and
the
magic
that
happens
here
is
effectively
in
the
logic
of
what's
going
to
happen
at
the
bootstrap
level.
It
will
append
this
string
to
the
end
of
the
core
os
install
command.
B
So
in
our
instance,
we
want
it
to
copy
the
network,
the
static
ipconfig
into
the
installed
coreos
instance.
So
that's
the
point
one.
The
full
step
is
just
like
you
would,
with
any
other
core
os
install
where
you're
setting
the
static
ip.
I
want
to
interrupt
that
boot
prompt.
I
want
to
hit
the
e
button
and
then
append
the
ip
equals
blah
blah
blah
blah
for
my
node.
B
So
we'll
look
at
all
of
that
in
just
a
moment
when
I
go
to
actually
boot
our
virtual
machine
here,
all
right,
so
that's
our
install
config,
so
pretty
pretty
straightforward
I'll
scroll
back
up
here
just
to
review
the
additional
truss
bundle
is
important.
That
is
what
gives
or
allows
it
to
trust.
The
registry
instance
that
we're
using
our
image
content
sources,
which
again,
if
we
come
back
over
here,
let's
go
to
this
guy
and.
B
Up
nope
anyways,
if
I
do
that
dry
run
again
right,
that
is
the
stanza
that
gets
output
at
the
end
of
that.
I
just
copied
that
over
pasted
it
in
here
maybe
copy
paste
that
you
know
save
that
as
a
text
file
in
the
content
that
gets
mirrored
across,
I
modified
it
to
be
actual
reality
on
my
destination
network.
So
again
I
set
the
host
name,
the
actual
destination
registry
correctly,
and
we're
ready
to
go
from
here,
let's
exit
out
of
there
into
our
working
directory
copy
the
install
config.
B
B
At
this
point,
I'm
more
or
less
going
to
be
following
the
the
the
guide
or
the
the
set
of
steps
that
I
created
back
when
we
did
the
single
node,
openshift
stream.
So
right
now
I
am,
I
just
completed
what
is
effectively
step
two
in
that
link
that
I
just
posted
into
chat
the
github
gist.
I'm
getting
ready
to
do
step
three,
which
is
the
open
shift,
install
create.
B
B
So
the
next
step,
if
I'm
looking
at
that
link
that
I
just
referenced
in
my
apologies,
I
would
have
both
of
these
up
and
I'd
switch
back
and
forth
between
them.
But
when
we
tried
to
do
that
whole
full
screen,
monitoring
full
screen,
sharing
thing
it
borked.
So
I'm
going
to
try
and
rearrange
my
desk
so
that
way,
next
time
we
do
one
of
these
I
can
share
the
whole
screen
and
it's
just
easier
anyways.
B
B
Inside
of
this
other
directory,
I
have
my
core
os
iso,
so
remember
that
the
core
os
install
files-
you
see
this
is
4.9.0.
They
don't
have
to
match
the
version
of
coreos
of
openshift
that
I'm
installing
it
will
automatically
adjust
it'll
automatically
change
or
update
coreos.
If
it
needs
to
be
so
they
only
re-spin
these
isos
periodically.
Basically,
if
there's
been
a
major
change
or
something
inside
of
there
so
like,
if
you
look
back
at
4.8,
I
think
there
was
like
4.8.2
and
then
4.8.14
are
the
two
coreos
versions
you
can
download.
B
B
Is
there
a
doc
link
for
that
install
on
disk?
Unfortunately,
no,
so
as
it
stands
right
now,
the
documentation
only
shows
single
node
openshift
with
assisted
installer.
Unless
this
has
changed
in
the
last
few
days,
I
don't
think
it
has,
but
it
could
have
so.
The
problem
with
that
is
assisted.
Installer
itself
is
a
tech
preview
feature
so
using
an
assisted,
installer
great.
It
works
in
my
experience.
It
works
well,
but
just
be
aware.
Tech
preview
means
that
ai
itself,
assisted
installer
itself,
is
not
supported
the
resulting
cluster.
B
B
B
So
he
worked
with
the
engineering
folks,
so
at
the
top
of
that
github
gist
that
I
plugged
into
the
chat
there
is
a
link
to
ben's
blog
that
I
used
for
all
of
this
so
and
he
also
documents
how
to
do
a
disconnected
install.
I
think
I
modified
his
blog
post
to
be
connected,
so,
okay,
our
copy
command,
finished
here.
If
I
look
inside
of
here,
we've
got
this
pro
s
iso.
So
now
I
want
to
do
a.
B
B
So
remember,
I
said
that
there
was
another
binary
that
we
would
need
core
os
installer,
so
this
one
was
downloaded
just
like
all
of
the
others
from
the
openshift
mirrors,
so
there's
also
a
way
that
you
can
extract
it
from
the
release
in
the
documentation
johnny.
I
don't
know
if
you
happen
to
have
that
linkedness
at
hand,
but
it's
available
through
the
normal
mechanisms.
C
B
And
I
want
to
embed
our
bootstrap
ignition
file
and
I
want
to
embed
it
into
our
core
os
iso,
so
as
ben
points
out
in
his
blog
post
and
something
he
reminded
me
of
a
command
that
I
haven't
used
in
about
a
decade
which
is
you
know,
there's
no
output
from
this.
I
have
no
idea
whether
or
not
it
succeeded
or
failed.
So
I
can
do
an
echo
dollar
question
and
it
will
output
the
status
of
the
previous
command,
so
the
outputs
result
was
zero,
which
means
that
it
exited
successfully.
B
So
our
bootstrap
or
excuse
me
our
core
os
iso
here
now
has
our
ignition
embedded
into
it
so
notice
that
the
file
didn't
change
sizes.
I
actually
asked
them
about
this.
That's
expected
they
do
some
magic
inside
of
there.
That
puts
in
like
a
dummy
file
or
something
like
that.
I
don't
know
exactly
what
it
was,
but
basically
they
said
yeah,
that's
that's
the
way
it
should
be.
B
So
at
this
point
I
have
my
installation
iso.
I
have
the
ignition
file
for
my
single
node
open
shifts
in
that
ignition
or
excuse
me
in
that
coreos
install
now.
I
need
to
take
that
iso.
I
need
to
attach
it
to
the
host
that
I'm
going
to
install
to
so,
as
I
said
before,
we
would
expect
that
fully
supported
you're
doing
this
with
bare
metal,
so
burn
it
on
a
physical
cd.
B
B
B
Iso
that'll
take
a
couple
of
seconds
for
that
to
copy
over
oh
pclouderbach
peter,
thank
you
for
posting
ben's
blog
and
it
is
a
great
blog
post
ben,
which
I
think
you
all
may
have
may
remember
him
from
the
single
note
open
shift
or
the
assisted
installer
stream
that
we
did
ben's
the
guy
that
I
go
to
with
all
the
crazy
esoteric
questions
like.
I
wonder
if
anybody
has
ever
tried
this
before
and
it
ben
almost
always
has
so.
C
B
All
right,
so,
if
you're
a
quick
guide
before
you
saw
my
vsphere
host,
so
this
is
just
a
standalone
esxi
host,
I'm
not
not
doing
anything
fancy
here.
You
can
of
course
use
vcenter.
I
just
don't
have
vcenter
running
at
the
moment
because
it
uses
precious,
precious
resources
that
I
just
don't
have
to
spare.
B
Is
this
replacing
the
part
that
you
insert
the
v-app
properties
in
the
iso
template?
Yes?
And
no
so
normally,
when
you
do
a
vmware
install
with
the
ova,
it
will
use
a
vm
property,
so
it
used
to
be
a
vip
property.
We
changed
it
to
a
vm
property
due
to
size,
so
the
vip
property
was
limited
to
it
was
80
kilobytes
or
something
like
that,
and
the
bootstrap
ignition
specifically
is
way
more
than
that,
whereas
the
vm
property
has
a
much
larger
size
limit.
B
So
it
does
replace
that
you
know
how
we
get
the
ignition
into
the
boot
process
or
into
the
core
os,
because
with
the
iso
install
basically
not
the
ova,
there's
no
tools,
there's
nothing
that
allows
it
to
reach
up
into
that.
You
know
vsphere
layer
and
look
at
the
vm
properties
to
ingest
that
information,
so
we
have
to
get
it
somehow.
B
B
B
So
I
created
a
virtual
machine
here.
So
one
thing
to
note:
if
you
use
assisted
installer,
to
do
single,
node
open
shift,
it's
going
to
require
you
to
use
four
or
eight
cpus
and
32
gigabytes
of
memory.
If
you
do
it
from
the
cli
like
this,
it
won't
enforce
those
checks.
So
you
can
go.
You
see
I'm
using
6
and
32
I've
done
it
with
4
and
24.
Before
I
generally,
don't
recommend
folks
go
too
much
below
that
because,
particularly
for
cpu,
you
start
it
starts
extending
the
timeline
for
install
other
than
that.
B
B
It's
connected
to
the
same
network
that
10.0.101
network
and
I'm
going
to
attach
our
cd
device.
So
let's
come
in
here
to
our
cd
drive.
I
want
to
connect
to
a
data
store
iso
file.
I
want
to
choose
the
one
I
want,
so
our
nfs
blue
data
store
and
we
want
our
aoa
disconnected
iso.
So
this
other
one
in
here
that
was
from
earlier
when
I
was
testing,
so
we
can
just
ignore
it.
B
So
for
this
I
capture
my
so
I
set
a
boot
delay
inside
of
my
virtual
machine,
so
I'm
going
to
zoom
this
back
out
since
it's
a
little
bit
big.
So
I
set
a
boot
delay
in
here
so
that
I
can
click
in
and
hit
escape.
This
is
so
that
I
can
reuse
the
virtual
machines
normally
if
it's
a
brand
new
vm
right,
never
been
loaded
or
anything
it'll
automatically
boot
to
the
cd
drive
first.
So
that's
why
you're
seeing
this,
because
I
don't
constantly
destroy
and
recreate
the
vms.
B
I
reuse
them,
so
I'm
going
to
have
it
boot
to
our
cd-rom
drive,
which
remember:
has
the
iso
for
the
core
os
install
that
we
added
the
bootstrap
in
place
ignition
file
to,
and
here
is
where
we
want
to
capture
it.
So
before
that
screen
times
out,
you
want
to
hit
e
and
it's
going
to
drop
you
into
this
prompt
and,
if
you've
ever
done.
B
You
know
a
traditional
open
shift,
install
before
you're,
familiar
with
the
kernel
parameters
that
we
can
configure
here
to
do
things
like
set
static
ip
or
tell
it
where
the
bootstrap
file
is.
So
that's
exactly
what
we're
going
to
do
here,
so
I'm
going
to
go
down
to
the
make
note
of
the
linux
line
here,
not
the
init
rd
line,
the
linux
line,
we're
going
to
go
all
the
way
out
to
the
end
and
we're
going
to
set
our
ip
equals.
One.
B
B
Single
colon,
the
interface
to
use,
so
this
is
it's
a
vm,
obviously
so
ens
192
is
the
first
nic
if
you're
using
a
physical
host.
You
know
you
probably
have
you
know
four
eight
12
interfaces.
One
thing
I
found
is
you
can
boot
to
the
live
iso?
So
not
the
one
that
we
have
here
with
the
bootstrap
added
or
the
ignition
file
added,
but
just
the
regular
live
iso.
B
B
Ipa
and
it
will
show
you
those
interface
names
and
you
can
kind
of
map
that
back
from
there
right.
It's
it's
a
regular
linux
environment
at
that
point
that
I
found
is
kind
of
the
quickest
and
easiest
way,
particularly
because
if
you
want
to
do
everything
in
one
step,
you
can
boot
into
that
live
environment.
You
can
configure
the
network
and
then
you
can
do
the
core
os
install
dash
dash
copy
network.
B
C
B
B
C
B
C
B
Our
registry,
what
we
should
see
is,
as
it
goes
through,
it's
going
to
be
pulling
in
all
of
those
container
images.
So
if
we
sit
here
and
watch
this
we'll
see
all
those
container
images
get
pulled
as
it
does
its
thing,
the
other
thing
we
can
look
at
is
so
I
can
go
into
my
cluster,
so
this
is
where
I
was
running.
The
coreos
install
where
I
did
open
shift
install,
create
single
node,
blah
blah
blah.
I
can
do
my
open
shift.
Install
wait
for
bootstrap
completes.
B
B
You
do
need
those
four
dns
entries,
so
this
is
in
step,
one
of
the
gist,
so
you
need
the
node,
so
sno
sno-node,
as
we
saw.
Where
did
that
go
so
sno-node
to
be
there.
We
need
the
api
dot,
cluster
name,
api-int,
dot,
cluster
name
and
star.apps.cluster
name.
So
those
three
dns
entries
need
to
be
there.
Our
four
dns
entries
need
to
be
there
in
the
case
of
single
node
openshift.
They
all
need
to
point
to
the
same
place
because
it's
one
node.
So
there
is
no
virtual
ip
addresses.
B
There
is
no
load
balancer
right.
It's
a
single
node!
You
can't
load
balance
with
a
single
node,
so
there
bootcube.service
succeeded,
see
that
was
pretty
quick
and
painless
here
in
a
minute
here
in
a
minute,
we'll
we'll
see
that
complete.
What
I'm
going
to
expect
here
is.
This
will
probably
drop
my
connection
so
before
it
does
that
we'll
exit
out
and
then,
if
I
were
to
switch
back
over,
I
would
see
that
my
virtual
machine
will
eventually
go
through
a
reboot
process.
A
And
just
real,
quick
andrew,
like
the
thing
that
you're
just
doing
whether
you're
following
the
journal
ctl
along
the
boot
cube
service.
That's
a
good
way
to
determine
very
quickly
if
your
registry
and
comps
between
registry
and
your
cluster
are
good
to
go.
Because
what
you'll
see
on
the
disconnected
side
is
when
you
go
and
you're
running
that
boot
cube.
A
If
it
can't
talk
to
the
registry,
if
it
can't
pull,
then
you'll
see
where
it's
trying
to
it's
kind
of
misleading,
where
it
says:
hey,
pull
in
from
quay.io
the
image
name
and
then
the
hash
or
the
shaw.
It
it'll
say
like
trying
this
mirror,
which
is
going
to
be
your
registry.
And
then
it's
going
to
say.
B
Yep
yeah
and
you'll
notice,
as
I
was
scrolling
up,
you
probably
saw
a
bunch
of
red
lines
go
through
and
there's
some
as
we
look
through
here.
There's
some
fails
like
here
failed
to
create
blah
blah
blah.
Oh,
that
is
normal.
What
you're
seeing
here
is
the
sausage
being
made
with
regard
to
the
bootstrap
process
and
the
install
process,
so
don't
be
alarmed
with
this
stuff.
It's
one
of
those
it's
normal
because,
like
particularly
with
up
here,
these
failed
to
create
basically
we're
waiting
for
the
the
kubernetes
api
to
understand.
B
What
are
these
things?
What
are
these
objects?
Like
you
see,
you
know
it's
saying
the
namespace
openshift
machine
api
doesn't
exist
yet
so
we're
waiting
for
machine
api
to
be
deployed.
You
know
the
operator
to
be
deployed
to
create
its
namespace,
to
define
the
crds
so
that
it
can
then
add
all
of
these
various
objects.
Inside
of
there,
and
after
a
few
seconds,
you
notice
that
they
eventually
do
succeed
and
it
moves
forward.
B
So,
generally
speaking,
these
things
are,
if
they
don't
last
for
long
they're
not
to
be
alarmed
about
if
they
last
for
a
while,
like
to
the
point
where
your
install
fails.
Obviously
that's
when
you
need
to
look
at
it,
so
you
can
see
here.
The
connection
to
the
server
api
ends
was
refused.
That's
because
it's
not
up
yet,
like
literally
the
pods
hadn't
started
in
order
to
to
accept
those
connections
and
then
once
it
did,
it
moved
on.
It
succeeded.
B
Okay,
so
while
that's
doing
its
thing,
just
like
any
other
openshift
deployment,
it's
going
to
take
a
few
minutes.
So,
interestingly,
if
you
have
done
connected
installs
before
usually
the
vast
majority
of
the
time,
unless
you
have
just
a
really
really
nice
internet
connection
is
just
waiting
for
it
to
download
those
container
images
to
each
node
right.
Every
every
control
plane
host
has
to
download
a
couple
of
gigabytes.
Every
worker
node
has
to
download
a
couple
of
gigabytes
and
so
on
and
so
forth,
and
it
can
take
a
while
just
to
download
all
those.
B
If
you
do
this
disconnected,
then
it's
running
at
the
speed
of
whatever
your
local
network
is
whatever
your
local
storage
is.
So
this
is
one
reason
why
I
will
often
recommend
to
folks
like
hey,
if
you're
doing
a
lot
of
installs
a
lot
of
deployments,
doing
it
disconnected
for
the
install
and
then
to
reconnect
a
cluster.
B
So
as
well
as
saving
all
of
that
bandwidth,
I
know
particularly
for
some
home
labbers.
You
know
some
isps
limit
your
download
bandwidth,
so
something
to
be
cognizant
of
so
all
right.
That's
doing
its
thing,
we're
going
to
ignore
it
for
a
little
bit,
because
I
want
to
talk
about
mirroring
operators,
so
I'm
going
to
switch
back
to
the
browser
briefly
just
to
look
at
the
documentation.
B
B
B
B
B
All
namespaces
you
see,
I
have
all
of
these
things
that
come
up
inside
of
here,
so,
for
example,
if
I
wanted
to
mirror,
if
I
wanted
to
only
mirror
the
mtv,
the
migration
toolkit
for
virtualization
operator,
then
I
just
need
to
know
this
name
right.
If
I
wanted
to
do
keta,
I
have
no
idea
what
keta
is
right.
If,
whatever
these
happen
to
be,
you
basically
have
to
map
those
over.
B
B
B
So
let's
dispose
of
our
temporary
cluster
here.
So
that's
what
this
process
is
describing
so
the
other
way
to
get.
That
is
what
they
describe
here,
which
is
you
know,
pull
the
operator
index,
use
grpc
curl
to
get
the
list
of
them
and
then
extract
the
one
that
you
want,
and
then
you
use
that
name
or
names.
With
this
opm
index
prune
command.
C
B
B
B
B
B
So
the
reason
I
specifically
tagged
this
with
quay
is
because
this
image
does
need
to
be
pushed
to
an
actual
registry
for
the
next
step.
I
don't
have
one
deployed
on
my
connected
network,
so
I
just
use
quay
and
I
push
it
up
there
and
and
use
quay
to
do
to
to
do
that.
So,
if
you
it
is
a
public
repository.
So
if
you
happen
to
browse
to
quite
at
ios
and
solid
you'll,
see
a
cincinnati
repository
there
with
two
tags
of
4.9
and
a
4.8.
B
B
B
B
There
we
go
so
again:
ocadm
catalog
mirror
this
time.
I
need
to
provide
my
pull
secret,
so
this
is
the
same
pull
secret
that
I
used
before
right.
Just
as
if
I
were
to
go
to
console.redhat.com
pull
down
all
my
pull
secret,
it
needs
to
be
able
to
authenticate
to
the
red
hat
registries
to
pull
down
content
for
for
openshift.
B
Operator
index
file
that
we're
going
to
use
or
image
that
we're
going
to
use,
and
then
last
but
not
least,
is
the
destination
that
we're
going
to
put
all
of
the
data
at.
So
you
notice
that
this
is
going
to
put
it
into
the
local
file
system
that
I'm
currently
on
and
it
will
go
from
there.
So
if
we
hit
return
here,
it'll
take
out
a
moment
to
do
its
thing.
B
So
you
can
see
it
pulls
that
image
again.
I
don't
know
why
it
can't
use
or
doesn't
use
the
cached
one
that
I
have
on
my
host.
It
wants
it
to
be
in
a
registry
for
the
reasons
that
it
wants
it
to
be
in
a
registry,
so
it'll
use
that
it'll
build
up
the
index
of
images
that
it's
getting
ready
to
download
after
about
30
seconds.
Here
it
will
spit
out
literally
a
couple
of
thousand
thousand
lines
of
text
like
too
much
it'll
scroll
off
of
the
backlog.
Here
in
my
browser
window.
B
So
we'll
let
that
go
through
and
anyways
at
the
end
result
of
all
of
this
is
it's
going
to
pull
down
all
of
those
images
I'll
let
it
get
started
before
I
cancel
it
because
just
like
before
I've
already
done.
This,
do
note
that
this
is
it
mirrors
a
lot
of
data
here,
so
the
openshift
install
itself
for
4.9
is
about
nine
and
a
half
gigabytes.
B
Just
doing
this
with
the
cincinnati
operator
is
14
gigabytes.
If
I
do
openshift
logging,
it's
like
18
gigabytes,
so
it
pulls
down
a
lot
of
data
and
it's
there
there's
multiple
reasons
for
that.
The
most
non-obvious
one
in
my
opinion
is
it
includes
previous
versions
of
the
operator
so
that,
if
you
wanted
to
you
know,
maybe
the
current
version
of
the
operator
is
six.
B
Maybe
you
know
you
don't
six
doesn't
work
for
you
or
whatever
you
can
deploy
version
five
or
version
four,
and
it
has
all
of
the
relevant
images
for
those
as
well.
There
is
a
way-
and
I
think
it's
in
the
documentation.
There
is
a
way
where
you
can
tell
it's
to
specifically
only
pull
one
version.
I
don't
remember
how
to
do
that.
I
didn't
test
that,
so
I'm
not
going
to
show
that,
but
I
think
you
can
reduce
this
content
pretty
significantly.
B
B
B
B
B
B
B
If
I
come
into
4.9
and
I
go
into
operators-
yes,
I
know
this
isn't
the
other
record
from
before
I'm
just
using
a
different,
a
different
iteration
and
we
still
have
our
cincinnati
inside
of
here.
So
you
notice
a
couple
of
things
about
this,
so
this
is
all
of
our
data.
So
remember,
I
said
it
uses
up
some
room,
so
if
I
let
this
run
for
a
minute,
it'll
eventually
come
back
with
14
gigabytes.
B
So
now
that
we're
on
the
disconnected
side,
I
want
to
now
import
all
of
this
data
into
the
registry
and
that
works
basically
exactly
like
the
the
previous
command
right
when
we
did
it
for
the
open
shift.
Installation
content,
I'm
not
going
to
let
that
run.
So,
let's
paste
this
in
here,
so
we
have
the
same
oc.
Adm
catalog
mirror
command
this
time,
we're
telling
it
the
source.
B
B
That's
where
it's
getting
this
information
from,
so
where
it
mirrored
the
content
to
and
then
the
tag
associated
with
our
catalog
index
and
then,
where
I
want
it
to
send
that
data
to
so.
If
we
let
it
do
its
thing,
it
will
do
exactly
what
you
would
expect
it's
going
to
go
through.
It's
going
to
take
all
of
those
images
off
of
disk
and
shove
them
into
our
catalog
or
excuse
me
our
registry
instance,
and
that's
that's
really
all
there
is
to
it
at
least
as
far
as
importing
the
content
and
the
data.
B
B
So
if
I
were
to
let
that
previous
command
run
through
completion,
so
it
took
all
of
the
data
that
was
in
this
v2
directory
off
disk
and
shoved
it
up
into
a
registry.
At
the
end
of
that,
it's
going
to
create
this
folder
structure
and
inside
of
here
is
another
mapping
file.
So
this
time
I
sourced
it
from
disk
and
pushed
it
up
into
the
registry,
but
it
also
provides
us
a
sample
catalog
source
which
we'll
need
in
order
to
point
olm
at
our
new
or
our
mirrored.
B
B
B
C
B
So
we'll
let
that
reboot,
I
have
slight
hope
that
it
might
come
back
up
in
reality.
What
would
normally
happen
is
if
I
weren't
talking
about
other
things.
At
the
same
time,
you
know
you
would
do
an
open
shift,
install
wait
for
install
complete
and
you'll,
be
able
to
get
that
output
and
see
what
all
is
going
on
inside
of
there.
B
B
If
I
can
figure
out
what
happens
I'll
put
it
in
the
blog
post
just
to
point
out
what
it
is.
So
this
is
also
the
first
time
that
I
think
that
we've
shown
or
in
any
way
documented
how
to
do
the
static
ip
stuff
with
single
node
openshift,
so
I'll,
be
sure
to
highlight
that
in
the
blog
post
as
well,
which
reminds
me,
I
don't
think
I
published
last
week's
blog
post
yet
so
my
apologies
to
anybody
who's
been
waiting
on
that
I'll
have
to
do
a
double
deal.
B
A
A
B
At
least
this
well,
we
haven't
even
gotten
a
disconnected
oil,
yet
it
was
just
the
disconnected
single
node
openshift.
I
may
have
been
a
little
over
ambitious
with
the
instead
of
doing
a
regular
old
cluster
install
with
something
like
vsphere
ipi.
So
I
I'm
relatively
confident
that
the
olm
side
will
work
like
I
said,
I've
got
a
a
markdown
document
that
I'll
publish
as
a
gist
that
has
all
of
the
steps
that
we've
gone
through
here.
B
A
Yeah
and
something
else
to
mention
too
that
icsp
when
you're
looking
at
that,
you
know
you
see
like
the
the
source
and
destination.
If
you
go
look
in
your,
if
you
were
to
go
to
your
openshift
nodes,
you
could
actually
see
that
in
your
etsyregistriesregistries.com
or
etsy
containers
register.
Whatever
the
path
is,
I
can't
remember,
but
that
mapping
is
actually
there.
So
that
way
you
can
kind
of
see
like
okay,
I'm
going
to
try
and
hit
this.
A
B
B
This
is
what
it
does.
It
goes
into
every
node
in
the
cluster.
It
does
not
require
reboot,
it
is
not
machine
config,
so
it
doesn't
do
a
node
reboot,
but,
and
it
adds
these
files
in
so
this
is
how
it
redirects
all
of
those
things
at
kind
of
the
lowest
level
or
the
level
closest
to
where
the
pods
get
or
the
images
get
pulled
at.
C
B
B
Strange
so
we've
only
got
just
a
couple
of
minutes
left
seven
by
my
clock.
So
if
anybody
has
any
questions,
if
there's
anything
that
we
haven't
addressed,
that
we
happen
to
miss,
if
there's
anything,
you
want
to
bring
up
please
by
all
means,
go
ahead
and
do
that,
as
always
you're
welcome
to
reach
out.
I
I
think
stephanie's
been
flashing.
Our
twitter
handles
on
there
a
few
times,
you're
welcome
to
reach
out
on
twitter,
practical
practicalandrew
for
me,
or
you
can
reach
out
via
email,
andrew.sullivan
redhat.com.
B
I
don't
mind
that
at
all
I'll
also
note
so
next
week
we
have
a
stream.
I
haven't
quite
nailed
down
the
topic
yet
so
we'll
hopefully
by
the
end
of
today,
we'll
have
that
down
stephanie's
grimacing
right
now,
because
because
she's
she's
dependent
on
me
to
get
a
lot
of
the
organization
stuff
done.
So
I'm
sorry
so
next
week
we
will
be
streaming
two
weeks
from
today.
We
will
not.
That
is
the
thanksgiving
holiday
here
in
the
u.s,
so
yeah.
B
So
we
won't
be
here
that
week
we
will
be
streaming
three
weeks
in
december,
the
1st,
the
8th
and
the
15th,
and
then
we
will
go
on
holiday,
hiatus,
so
kind
of
the
last
two
weeks
of
the
year,
we'll
be
off
the
air.
I
don't
know
about
the
bigger
red
hat,
live
streaming
or
openshift
tv,
but
this
stream
will
be
off
the
air.
We
do
have
some
interesting
sessions
or
episodes
planned
for
the
rest
of
this
year.
B
B
B
So
hopefully
you
know
don't
go
on
holiday
mode
just
yet
you
know
we
we
would
love
for
to
have
you
join
us
for
those
streams,
if
not
they're,
of
course,
available
through
whatever
streaming
platform,
twitch,
youtube,
etc,
as
well
as
we'll
have
the
blog
posts
mirror
ggg.
Thank
you.
If,
if
anybody
has
any
requests
again,
this
session
itself
was
a
request.
B
So
if
you
have
any
requests
suggestions,
ideas,
corrections,
I
love
corrections
by
the
way
andrew
is,
as
my
shirt
says,
right,
a
few
records
shy
of
a
dns
zone
by
all
means
reach
out
to
us.
You
know
we
love
to
get
those
and
making
sure
that
we're
able
to
interact
with
you
all
and-
and
you
know
answer
your
questions-
is
really
good,
our
hope,
nine.
So
this
is
the
two
hour
length.
While
I
I
kind
of
like
it
right,
it
gives
us
the
ability
to
really
dig
in
right
now.
B
This
is
just
a
one-off,
so
we
haven't
broached
the
topic
of
going
longer
than
that
consistently
yet,
but
it
does
feel
good
to
me
so
we'll
talk
on
the
back
end,
we'll
see
if
we
can
find
some
other
topics
that
that
makes
sense
for
the
longer
stream
length
where
we
can
go
more
in
depth
with
those
things
you
know.
Sometimes
we
do
have
some
not
not
to
disparage
product
managers
or
things
like
that.
B
Loki
would
be
a
cool
topic.
Yes,
so
there's
actually
several
things
related
to
logging
that
I'd
like
to
cover
at
some
point,
not
the
least
of
which
is
the
move
towards
fluent
d
and
so
yeah
fluentd
loki.
All
that
other
stuff,
that's
happening
with
the
openshift
logging
service,
so
the
observability
stuff
is
it's
becoming
more
and
more
important
and,
as
a
result,
we're
getting
additional
pms
associated
with
it.
So
hopefully
that
means
that
we
can
get
some
more
in-depth
information
both
from
product
management,
as
well
as
from
engineering.
B
A
No,
I
just
you
know
just
keying
in
on
some
of
like
the
the
stuff
that
you're
talking
about
you
know
like.
If
you're
you
know,
I
think
everything
that
you
went
through
today
is
it's
really
good
for
any
type
of
cluster
install
right
like
mirroring
the
images.
If
you're
you
know,
checking
the
bootstrap
logs
checking.
You
know
using
curl
to
to
hit
your
registry
to
make
sure
that
your
repos
are
there
like.
That
stuff
is
all
like.
A
It
seems
basic
and
simple,
but
that
is
literally,
like
I'd,
say,
a
killer
in
like
80
of
the
installs
that
we
do
where
it's
just
something
silly,
but
just
having
those
tools
in
your
tool
bag
where
you
know
that,
like
you
run
curl
to
go
check
the
authentication.
Can
I
log
into
my
my
registry?
If
I
have
it
set
up
yeah,
you
know
using
ht
password
or
using
podman
login
to
output
the
the
login
credentials.
A
So
that
way,
when
you
do
have
to
use
like
a
pull
secret
in
your
install
config,
you
actually
get
the
format
and
everything
that
you
need.
Just
all
you
have
to
do
is
really
remove
the
spaces.
So
just
having
all
those
tools
available
and
and
knowing
like
okay,
where
I'm
at
in
this
process,
how
do
I
check
this
and
yeah?
I
I
think
it's
it's
awesome.
I
think
you
hit
on
a
bunch
of
like
awesome,
big
key
points
that
we
need
to
get
out
more.
B
Yeah-
and
this
has
been
a
fun
one
for
me
too,
because
it's
stuff
that
honestly,
I
rarely
do
like
the
the
catalog
the
operator
index
mirroring.
I
I
semi
regularly
do
a
disconnected
install,
which
started
back
when
not
to
not
to
sound
disparaging.
But
you
remember,
there
was
a
short
period
of
time
there,
where
the
red
hat
infrastructure
was
a
little
shaky.
B
And
stuff
like
that,
and
it's
one
of
those
like
I
gotta-
have
a
cluster.
I
need
to
deploy
this
I'm
getting
ready
to
do
this,
so
I
started
mirroring
content
and
I
would
do
those
do
the
install
offline
and
then
just
remove
the
icsp
and
reconnect
it,
and
you
know
everything
went
went
well
from
there,
so
I
I
always
find
that
that's
an
excellent
way
of
also
speeding
up
your
installs.
You
know,
especially
if
you're
doing
a
lot
of
them
ossm
federation.
Yes,
I
would
love
to
learn
more
about
that.
B
Ossm
has
been
on
my
backlog
of
things
to
learn
more
about
basically,
since
it
was
released,
so
I
I'm
I'm.
I
would
love
to
get
some
experts
on
to
talk
about
that
I'll
see.
If
I
can
find
that
find,
find
the
right
folks,
so
I
won't
dillydally.
I
won't
hold
folks
any
longer.
Thank
you.
So
much
for
joining
us
today
really
enjoyed
doing
the
two-hour
stream
with
you
johnny.
Thank
you
so
much
for
helping
in
chat
and
all
of
that
you
know.
I
know
that
there
was
a
bunch
of
stuff
through
there.
B
B
If
you
have
any
questions,
if
there's
anything
that
comes
up
anything
like
that,
please
don't
hesitate
to
reach
out
we're
happy
to
help
as
much
as
we
can
and
like
I
said
at
the
beginning,
if
I
don't
know
the
answer
or
we
don't
know
the
answer,
because
johnny
knows
more
than
I
do.
If,
if
we
don't
know
the
answer,
we'll
find
the
right
people
and
get
you
connected
with
that.