►
From YouTube: Ask an OpenShift Admin (Ep 42): OpenShift at the Edge
Description
You've probably heard about the growth of edge computing, but what is edge? And what does it mean- especially for OpenShift admins? By moving workloads to the edge of the network, devices spend less time on the cloud, react faster to local changes, and operate more reliably. But with the opportunities that edge computing brings, some complexities need to be considered as you build out an infrastructure to support these use cases.
So in this episode, let's talk about what it's like to work with OpenShift at the edge. That means things like running nodes at remote sites, single-node OpenShift instances, and compact clusters. We'll also take a look at management tools and philosophies. Red Hat Principal Technical Marketing Manager Mark Schmitt will join the stream to help explore how the edge is a very different place from the data center and gives us a unique perspective on OpenShift at the edge.
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
Chris Short https://twitter.com/chrisshort
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
Good
morning,
good
afternoon,
good
evening,
wherever
you're
handling
from
welcome
to
another
episode
of
ask
an
open
shift
admin-
I
am
chris
short
host
for
the
most
here
on
red
hat
live
streaming,
I'm
joined
by
the
one,
and
only
andrew
sullivan
and
fellow
teammate
mark
schmidt.
How
are
you
today
y'all.
B
A
A
A
B
I
don't
either
actually
that's.
I
should
look
that
up
anyways,
so
hello.
Everyone
welcome
to
the
ask
an
open
shift
administrator
office
hour.
So
this
is
one
of
our
office
hour.
Series
of
streams
here
on
red
hat
live
streaming,
which
means
that
we
are
here
much
like
if
you
ever
had
a
teacher
or
a
manager.
B
B
B
B
B
Yeah
anyways,
we'll
we'll
we
won't
pick
on
him
he's
not
here
to
defend
himself.
We
won't
pick
on
him
too
much
but
yeah
so
happy
to
have
you
mark.
I
know
it's
it's
fun.
When
we
chat
about
your
your
experiences
in
the
telco
industry
and
with
openstack
a
long
time
ago
I
was
an
openstack
user,
I'm
happy
to
happy
to
say
I'm
fully
recovered.
A
B
B
Yes,
so
I
we
first
talked
about
this
briefly
when
we
did
the
what's
new
in
openshift
4.8
stream,
and
that
was
we
talked
about
it,
because
one
of
the
things
that
I
thought
was
really
cool
and
interesting
is
you
can
see
which
apis
are
being
used.
So
let
me
I'm
going
to
share
my
screen
just
so
that
we
can
see
what
this
looks
like.
B
There
we
go
hey,
I
got
the
right
one
on
the
right
on
the
first.
Try
hey,
hopefully
that's
big
enough
for
everybody
to
see.
If
not
just
let
me
know
so
with
openshift
4.8,
we
have
an
api
specifically
that
tells
us
which
apis
are
being
used.
So
if
I
do
an
oc
get
api
requests,
it
will
return
back
this.
Oh
of
course
you
don't.
B
Remember
last
time.
I
did
this,
it
was,
I
completely
borked
it
and
it
took
me
a
little
while
to
find
it.
So
we
have
this
git
api
request
counts
and
it
returns
back
all
of
these
different
apis
that
are
in
use
how
often
they're
in
use,
if
we
scroll
all
the
way
up
to
the
top
here,
so
requests
and
current
hour
requests
in
the
last
24
hours,
all
that
other
stuff.
So
you
can
see,
for
example,
this
api
request
counts.
Api
is
pretty
popular
for
some
reason.
B
I
have
not
done
it
507
times,
so
you
know
here
cluster
role,
bindings.
Of
course
you
would
expect
the
rbac
stuff
to
be.
You
know
pretty
widely
used,
so
the
interesting
part
here
is.
We
have,
for
example,
this
dot
ingresses.v1
beta,
1
extensions,
and
you
can
see
this
column
here.
1.22
represents
which
release
it's
being
removed
in
so.
B
B
You
know
we're
aware
of
this,
we're
working
on
this
with
all
of
our
you
know,
you
would
expect
the
ingresses
to
be
one
of
ours,
so
we're
working
on
updating
all
of
our
operators,
all
of
our
stuff,
to
make
sure
that
before
that
time
comes
all
of
our
stuff
will
be
not
using
those
removed
apis.
Our
partners
are
also
doing
the
same
yeah.
This.
B
Yes,
so
just
be
aware,
if
you
have
created
your
own
operators,
if
you're
using
any
of
these
apis
in
any
of
your
own
codes
or
if
you
have
partners,
you
know
you
may
want
to
reach
out
and
poke
your
partner
and
basically
say
hey.
Are
you
guys
aware
of
these
things?
You
know
we
need
to
take
this
into
account.
A
And
the
one
of
the
main
reasons
you're
hearing
this
from
us
first
potentially
is
because
well
we're
gonna
be
one
of
the
first
to
update
to
122..
So
these
things
need
to
change
before
you
do
that
and
that's
why
we're
I'm
beating
the
drum
in
the
community
and
I'm
going
to
beat
the
drum
here
as
well.
Deprecations
happen
in
kubernetes
and
that's
not
a
bad
thing.
It's
actually
a
good
thing,
because
a
lot
of
them
are
being
upgraded
to
stable,
as
opposed
to
beta.
B
B
B
You
got
it
okay,
I
can
get
it
yeah.
Well,
then,
I'm
going
to
share
my
screen
so
that
we
can
all
look
at
it
together.
Yes,
let's
see
share
this
guy
and
paste
that
in
there
so,
a
while
ago,
you
can
see
not
quite
a
year
ago
we
published
this
blog
post
that
I
think
it's
overlooked
fairly
often,
and
it
is
basically
what
are
all
of
the
components
like
the
specific
components
inside
of
openshift
from
upstream
projects.
B
So,
for
example,
we
say
openshift
has
you
know
the
the
monitoring
service
or
the
logging
service?
What
does
that
actually
mean
right?
The
monitoring
service
is
made
up
of
prometheus
and
grafana.
You
know
the
logging
service
is
made
up
of
a
lat,
elasticsearch,
fluentd
and
kibana,
so
on
and
so
forth.
So
this
this
blog
post
kind
of
walks
through
each
one
of
those
projects
that
make
up
different
components.
Different
features,
different
functions
inside
of
openshift.
B
So
nothing
really,
you
know
surprising
or
outstanding.
Here.
This
is
just
a
lot
of
times.
I
have
come
across.
You
know
account
teams
who
are
asking
us
in
the
view.
Like
you
know,
hey
my
customers.
Security
team
needs
to
know
you
know
what
is
the
component
or
what
is
the
thing
used
for
this
or
used
for
that
type
of
stuff,
because
they
want
to
know
you
know
what
what
is
it?
What
version
is
it
so
that
they
can
compare
it
against
any?
You
know,
kind
of
vulnerability
or
other
databases
that
they
have.
B
So
this
is
a
great
starting
point
for
that.
I
always
encourage
folks
to
look
at
this
whenever
they're
trying
it
out.
One
thing
to
point
out
I'll
put
in
my:
I
do
have
marketing
in
my
title,
officially
technical
marketing
I'll
put
on
my
marketing
hat
of
you
know
we
take
all
of
these
components.
You
know
the
what
makes
openshift
is
we
take
all
these
components.
We
combine
them
together
into
a
product
that
is
fully
tested
for
integration
and
all
that
other
stuff.
A
B
B
So
if
we
do
and
things
like,
you
know,
hey,
can
I
change
or
or
how
do
I
change?
What's
the
setting
to
change
the
amount
of
cpu
or
memory,
that's
dedicated,
to
say,
a
control
plane
node
in
vsphere
ipi,
so
it's
pretty
easy
to
figure
out.
So
if
we
do
an
open
shift
install
and
then
we
do
explain
if
I
can
type
install.
B
A
B
So
again,
it's
openshift,
install,
explain,
install
config
and
then
from
here
just
like
with
oc,
explain
or
kubecuttle
explain.
I
can
go
through
and
I
can
dig
into
each
one
of
these
so
install
config.compute
and
it'll.
Tell
me
okay,
what
are
all
of
the
options
available
inside
of
here
so
compute
dot,
let's
go
with
platform,
okay
and
then
okay,
I'm
using
the
vsphere
platform,
dot,
vsphere
and
okay.
Well,
if
I
want
to
modify
any
of
these
fields,
I
can
do
so
inside
of
here
so
for
compute.
B
Remember,
compute
is
going
to
represent
the
worker
nodes.
So
if
I
want
to
change
the
default
size
of
the
worker
nodes
provisioned
by
an
ipi
install,
I
would
do
so.
Compute.Platform.Vsphere
dot
say
memory
megabytes
and
I
can
specify
hey.
I
want
you
to
provision
worker
nodes,
write
that
initial
machine
set
should
have
24
gigabytes
of
memory
or
whatever
that
happens,
to
be
yeah
whatever
yeah.
I
want
to
use
a
one
terabyte
operating
system
disk
instead
of
a
120
gigabyte
disk.
B
And
then
inside
of
here
I
want
to
look
for
bare
metal,
so
bare
metal.
A
I
bare
metal
ipi
has
a
whole
bunch
of
options
available
to
it
and
to
me
they
can
be
very
confusing
and
even
inside
of
the
documentation.
Not
all
of
these
are
thoroughly
fleshed
out.
So
it's
an
easy
way
for
me
to
look
and
see
like,
oh,
you
know.
Do
I
need
to
set
this
provisioning
bridge.
You
know
what
is
this
provisioning
dhcp
range?
Do
I
need
to
create
that?
B
Do
I
need
to
provide
that
so
a
ton
of
options
in
here?
If
there's,
you
know
see
here
valid
values
you
know
are:
are
there
specific
things
that
I
can
provide,
or
that
are
only
you
know,
valid
fields,
etcetera,
so
a
helpful
one
there
if
you
just
happen
to
be
exploring
around,
want
to
know
what
options
are
stuff
like
that
I've
found
the
install
or
excuse
me
the
explain,
command
to
be
extremely
helpful,
just
in
general,
so
yeah.
A
B
It
gives
me
back
all
of
the
different
fields
that
come
back
from
that
and
an
explanation
of
what
each
one
of
those
is.
So
I
can
see
how
this
is
an
object,
so
I
can
do
the
same
thing
with
spec
oops.
If
I
could
spell
it
correctly
so
number
of
users
to
report,
you
can
see
it's
an
integer
and
stuff
like
that.
B
So
this
is
one
of
those
ways
that
you
can
see
like
hey.
Maybe
I
want
to
expose
certain
fields
like
so
if
I
do
that,
dash
o
and
provide
a
specific
fields
or
stuff
like
that,
or
if
I
want
to
do
kind
of
a
raw
query
or
output,
the
whole
thing,
you
know
what
are
all
of
the
fields
with
all
the
data
that
I'm
going
to
get
returned
back
so
again,
super
helpful
to
to
use
the
explain,
commands
whether
it's
oc,
explain,
openshift,
install
explain,
etc.
B
B
B
A
B
So
openshift
has
not
yet
done
that
that
is
targeted
for
next
year
right
when
we'll
start
to
adopt
that
schedule.
So
we
are
still
on
a
four
annual
release
cycle,
so
approximately
every
three
months
every
quarter
there
will
be
a
an
open
shift
release.
I
say
approximately
because
there's
any
number
of
reasons
that
it
could
get
delayed
out
or
or
anything
like
that.
B
B
A
B
B
It
is
a
method
of
deploying
virtual
machines
into
an
application
and
oftentimes,
because
there's
also
a
guest
agent
and
stuff
like
that.
That
also
means
doing
things
like
installing
packages
etc.
So
vrealize
is
a
very
powerful
suite
of
tools.
I've
previous
employer.
I
wrote
a
plugin
to
use
vrealize
to
configure
control
right
and
consume
storage
devices
stuff
like
that
super
powerful
uses,
a
java
dialect,
javascript
dialect
just
said:
scripting
language,
so
we
get
asked
fairly
regularly
about
hey.
B
Is
it
possible
to
use
open
shift
or
excuse
me,
vrealize
automation,
to
provision
openshift,
and
the
answer
to
that
is
yes,
but
not
in
any
official
way
from
red
hat
and
really
not
an
official
way
from
vmware
either.
So
the
only
pseudo-official
thing
that
we
have
from
vmware
is
this
fling,
so
you
can
see
it's
from
november
of
2019,
so
we're
coming
up
on
two
years
old
here.
B
So
remember:
flings
are
effectively
a
proof-of-concept
type
of
thing
or
or
a
pre-supported,
or
what
do
we
call
them?
Dev
preview
yeah,
so
it's
hey,
we
can
publish
something.
I
think
vsphere
on
arm
is
a
fling
right
now,
so
we
can
publish
something
we
can
get
it
out
there
and
you
know
we
can
see
how
popular
it
is,
how
much
people
want
to
use
it,
whether
or
not
it's
sustainable
from
our
model
stuff
like
that,
and
I'm
speaking
in
the
perspective
of
vmware
here
but
anyways.
So
this
fling
was
published
a
while
ago.
B
However,
one
of
the
vmware
folks
recently
published
to
their
blog
effectively
a
way
to
do
this,
so
this
is
dean
lewis,
so
you
can
see
just
a
little
over
two
months
ago
published
a
deploying
openshift
ipi
using
vra,
so
vra
being
vrealized
automation.
So
if
you
can
walk
through
this
blog
post,
it's
it's
fairly
lengthy.
It
goes
into
pretty
good
depth
here.
That
explains
one
method
to
deploy
openshift
using
vrealize
automation.
B
B
So
I've
just
got
two
more
that
I'm
going
to
quickly
go
through
before
we
talk
with
mark
here,
so
one
this
one
gets
brought
up
pretty
frequently,
and
that
is
how
can
I
resize
control
plane
nodes,
so
control,
plane,
nodes
resizing?
Any
node
is
interesting
with
openshift
4.,
and
I
say
that
because
in
theory
and
especially
with
ipi,
we
exert
some
positive
control
over
the
configuration
of
those
nodes.
B
So,
for
example,
if
I
want
a
you
know,
a
machine
that
is
four
cpus
and
eight
gigabytes
of
ram,
I
create
a
machine
set
and
say:
hey,
deploy
me
all
of
these
machines.
If
I
need
a
machine
that
has
a
different
amount
of
of
resources,
I
would
create
a
new
machine
set
and
provision
machines
out
of
it.
Alternatively,
I
can
edit
the
existing
machine
set
and
then
basically
do
a
scale
up
scale
down
so
scale
up
to
provision
new
resources
and
then
scale
down
so
that
it
removes
those
old
ones.
B
So
or
you
can
specify
like
explicitly
to
remove
these
ones
that
type
of
stuff
we
covered
that
before
as
well
here
on
the
stream.
If
I'm
using
upi
or
a
non-integrated
platform,
then
the
method
is
slightly
different
and
specifically
we
don't
support
hot
add
it
may
technically
work,
but
we
don't
officially
support
it.
So
you
would
want
to
shut
down
the
node.
B
So
do
a
cordon
do
a
drain
shut
down
the
node,
adjust
the
resources
assigned
to
it
and
then
turn
it
back
on
and
let
it
you
know,
come
back
into
the
cluster
so
for
worker
nodes
that
basically
works
exactly
as
you'd
expect.
You
know
it's
it's
going
to
fall
in
line
with.
You
know
all
of
the
parameters.
You
know
when
you
do
that
coordinate
drain,
it'll,
make
sure
that
the
pod
disruption,
budgets
and
all
that
other
stuff
are
adhered
to.
Cetera
control,
plane
nodes
are
a
little
different
as.
A
B
B
So
if
you
do
like
vsphere,
upi,
absolutely
shut
them
down
one
at
a
time,
resize
them
turn
them
back
on
and
then
return
them
to
service
for
other
platforms,
so
think
aws,
azure,
et
cetera,
where
it's
not
as
simple
as
right-clicking.
The
virtual
machine
and
saying
add
cpu
right
where
you
have
to
replace
it
with
a
whole
different
machine
size.
The
suggested
method
is
to
remove
the
node
so
you're,
effectively
failing
a
control,
plane,
node
and
then
reprovisioning
a
new
one
and
having
it
rejoin
the
cluster.
C
B
So
this
would
be
the
process
that
you
want
to
follow.
So
you
know
it's
a
little
intimidating.
It
is
some
work
in
order
to
do
that,
but
it
is
possible
and
that's
literally
just
the
safest
way
that
we
can
do
it.
Might
it
work
if
you
were
to
just
go
in
and
change
the
instant
size
or
something
like
that?
B
B
Yeah,
so
you
you've
for
a
long
time
we
used
to
say
a
bare
metal
installation
right
and-
and
I'm
saying
we
referring
to
kind
of
red
hat
at
large.
We
would
say
a
bare
metal
installation
or
sometimes
a
bare
metal,
upi
installation,
and
what
that
was
referring
to
is
effectively
any
open
shift
deployment
where
in
the
install
config
it
was
set
to
platform
equals
none.
B
So
what
that
means
is
there's
no
cloud
provider
integration.
It's
not
using.
You
know
the
vsphere
cloud
provider,
it's
not
using
the
azure
cloud
provider,
whatever
that
happens
to
be
I'm
going
to
check
and
see.
If
I
can,
let
me
share
this
real,
quick
and
the
goal
being
so
with
a
with
a
cloud
provider
integrated
install.
B
It
means
that
the
cluster
has
additional
awareness
of
the
underlying
platform
with
a
non-integrated
or
platform
agnostic
or
what
we
used
to
call
bare
metal,
upi
installation
again
that
ins
that
infrastructure
integration
isn't
there
so
things
like
machine
sets
or
ipi
don't
exist.
I
can't
provision
new
nodes
because
it
doesn't
know
it
doesn't
understand
what
that
underlying
infrastructure
is
infrastructure.
Cluster.
B
So
if
I
look
inside
of
here
so
all
I
did
here
was
oc,
get
infrastructure
and
then
the
instance
is
cluster.
So
here
you
said
it
was.
You
can
see
the
oc
get
infrastructure
there's
one
instance
cluster,
and
then
I
did
an
output
to
yaml
so
that
I
can
see
the
full
output
down
here
in
the
spec.
You
can
see
that
my
platform
here
is
azure.
That's
to
be
expected.
I
deployed
this
cluster
to
azure.
B
So
this
one
yeah
that
worked
well,
I
got
the
eye
yeah.
Oh
it's
capital,
so
this
one
has
platform,
none
yeah.
So
this
this
would
deploy
a
non-integrated
cluster,
whereas
normally
this
owb
cluster
that
I
have
here
normally
I'd,
deploy
that
onto
a
vsphere
platform
and
that
vsphere
platform
would
then
have
you
know
the
the
provider
integration
so
being
able
to
do
things
like
consume
pvcs
through
the
storage
provisioner,
either
the
entry
or
the
csi
all
that
type
of
stuff.
C
B
B
B
And
very
quickly,
I
want
to
get
this
done
in
like
less
than
a
minute,
so
it
was
highlighted
that,
if
you're
using
an
image
content
source
policy
to
redirect
your
images
to,
for
example,
an
offline
mirror
so
remember
an
icsb
image.
Content
source
policy
basically
says
hey
if
you're
looking
for
an
image
here
redirect
automatically
over
to
this
other
place.
B
So
one
thing
to
note
is:
if
you
have
if
that
registry
instance
requires
authentication,
you
have
to
provide
those
credentials
in
your
cluster
level,
pull
secret
right.
So
in
the
pull
secret,
the
one
that
I
just
quickly
scrolled
up
past,
it's
in
your
install
config.yml,
that's
where
those
credentials
would
be.
It
is
also
cluster
wide,
so
pod
level
pull
secrets
depending
on
what
you're
doing
may
or
may
not
get
applied.
So
you
may
need
to
change
that
cluster
level,
pull
secret
to
include
or
exclude
different
characteristics
of
that
install
registry.
B
C
B
A
B
B
B
B
So
what
I
mean
by
that
is
open
shifts.
You
know,
and
we
just
saw
in
the
documentation
here,
go
back.
You
move
go
back
so
in
the
documentation
here.
Underneath
this
installing
we
explicitly
test
openshift
deployed
to
aws
azure,
google.
You
know
physical
servers,
ibm
z
power,
oh
right,
all
of
these
things,
but
if
you
want
to
install
openshift
to
other
places,
you
can
anything
that
is
a
certified
or
a
supported
deployment.
B
B
But
if
we
attribute
the
error
to
something
with
the
underlying
platform,
we
may
ask
you
to
move
to
a
tested
platform.
So
that
way
we
can
eliminate
that
as
a
possibility.
So
you
want
openshift
on
hyper-v.
Absolutely
yes
right!
It
is
a
supported
platform
for
rel.
You
can
deploy
it
inside
of
there
using
the
non-integrated
method.
Just
be
aware
of
those
caveats
and
if
you
haven't
posted
this
I'll
post.
B
All
right,
I
know
I
went
that
was
like
six
minutes
instead
of
one
minute
so
but
that's
okay.
It
was
questions
and
we
love
questions.
Yes,
we
do
so
again,
don't
don't
hesitate
to
ask
whatever
questions
are
top
of
mind
for
you
all
again
we're
talking
about
edge
today,
but
don't
let
that
limit
your
imagination
and
the
things
you
want
to
ask
about
so
mark
edge.
I
hear
it's
a
thing
these
days.
It.
C
B
A
B
B
B
A
C
C
We'll
talk
a
couple
of
edge
computing
use
cases
and
then,
if
there's
any
question
and
answer,
I
also
have
some
technical
detail
towards
the
end.
I
am
in
technical
marketing,
so
we'll
start
with
fluffy
stuff
first
and
then
talk
about
you
know
what
actually
happens
when
stuff
hits
the
van
from
an
edge
perspective
and
how
that
may
impact,
how
you
deploy
your
applications
out
there.
C
C
Okay,
yep
and
some
of
the
key
challenges
for
edge
computing
at
the
edge
security
is
always
a
big
concern
for
customers,
whether
you
know
it's
a
legacy
infrastructure
or
you
know
any
time.
Your
attack
surface
moves
out
of
the
data
center.
It's
going
to
cause
concerns
right.
Connectivity
is
also
of
concern
right
and
we'll
talk
a
little
bit
about
either.
C
When
we
talk
about
edge
deployments,
you
know,
data
centers
usually
are
in
the
hundreds
of
nodes
and
it
can
go
up
to
the
tens
and
tens
of
thousands
of
nodes
in
terms
of
real
customer
workloads
out
the
edge
and
maintenance
monitoring
of
those
is
is
a
key
factor
to
consider
when
thinking
about
edge
computing
and
what
your
architecture
is
going
to.
Look
like
go
ahead.
C
C
So
the
openshift
focus
is
kind
of
the
edge
endpoint
edge
gateway,
edge
server,
you
know
end
user
premise
edge,
and
you
know
next
slide
will
show
you
kind
of
what
exactly
this
means
from
a
hardware
perspective
and
a
scale
perspective
as
well
right.
Some
of
that
tier
one,
telco
kind
of
user
is
going
to
be
a
larger
16
core.
You
know
128
gig
you'll
have
hundreds
hundreds
of
those
not
really
considered.
C
You
know
data
center,
but
not
far
from
it,
and
then
we
see
a
tier
two
is
more
of
a
data
aggregation
again.
This
just
gets
into
kind
of
the
declining
hardware
capacity
and
the
scale
going
up
at
this
point
right
so
in
points
toco
workloads
would
be
a
really
good
example
of
this,
except
they're
going
to
go
with
a
way
more
core
and
memory
for
that
particular
workload.
C
C
Let
me
go
ahead
and
go
to
the
next
slide,
so
this
is
kind
of
where
we're
at
now
from
a
product
perspective
at
red
hat,
starting,
I
think
four
or
five
we
offered
a
three
node
cluster.
It's
fully,
aha
capable
it
gives
you
the
ability
to
schedule.
You
know
workloads
on
control,
plane,
nodes
essentially
and
we'll
get
into
a
little
bit
more
of
that.
In-Place
upgrades
are
available
here
as
well.
C
More
recently,
I
think
for
seven
we
offered
a
remote
worker
node
environment,
which
has
individual
work
worker
nodes
displaced
from
the
control
plane
that
are
reasonably
reliably
connected.
We'll
talk
a
bit
more
about
what
that
looks
like
and
and
what
happens
when
things
go
wrong
between
that
worker.
Node
and
the
the
control
airplane
and
available
this
year
is
the
single
node
edge
server
for
low
bandwidth
and
disconnected
sites.
So
if
you
don't
need
a
full
eha,
you
know,
openshift,
node
and
in
place.
C
B
B
B
B
You
know
a
store
chain
or
or
a
restaurant
chain
that
has,
you
know,
hundreds
thousands
of
of
nodes.
You
don't
have
to
have
that
type
of
deployment.
It
could
be
as
simple
as
you
know,
I'm
gonna
use
the
word
conglomerate,
a
conglomerate
of
like
lawyers
offices
right.
You
know
where
you've
got
a
dozen
offices
and
each
one
has
a
little.
You
know
infrastructure
node
out
in
it,
and
you
can
use
something
like
a
remote
worker
node
to
offer
them
those
capabilities
or
a
single
node
openshift.
B
B
They're
fun
to
me,
because
it's
effectively,
it's
just
like
any
other
worker
worker
node,
there's
nothing
special
about
it.
There's
nothing
unique
about
it.
It's
literally
like
it's
just
happens
to
be
way
out
at
the
other
end
of
a
link
with
probably
high
latency
and
yeah.
You
just
want
to
take
some
extra
considerations
with
how
the
workload
is
scheduled
to
those
nodes.
C
C
B
A
C
B
A
C
C
B
Yeah
it's
one
of
those
technically,
yes,
you
can
squint
and
consider
it
a
deployment,
but
really,
no
so
one
there's
a
complete
lack
of
support
there
like
I
don't
I
don't
even
know
how
much
community
support
you
would
get
for
something
like
that,
and
you
know
single
node
openshift
is
intended
to
become
a
fully
supported
deployment
option
right
today.
It's
in
dev
preview
or
tech
preview
or
whatever
it
is,
but
it
won't
be
long
and
it'll
be
fully
supported,
whereas
code
ready
containers
will
never
be
supported
for
a
production
type
of
use
case.
B
B
C
Yep,
so
this
is
kind
of
just
walking
through
the
different
options
to
deploy
your
three
node
ipi
upi
and,
most
recently
with
the
assisted,
installer,
basically
yeah.
The
only
thing
you're
changing
from
a
regular
openshift
install,
is
you're
setting
your
worker
replicas
to
zero
in
the
install
config
and
that's
basically
it
for
each
of
those
nodes
would
be.
You
know:
six
vcpu,
24,
gig
ram,
200,
gig
storage,
and
then
you
know
that
cluster
can
be
expand.
Expanded
at
will
and
you
can
add,
storage
nodes.
B
C
B
Had
this
big,
you
know
bare
metal,
only!
That's
referring
to
the
installation
method,
the
you
know,
the
platform
agnostic
platform
equals
none
deployment
type.
It
doesn't
matter
if
it's
physical
or
virtual.
So
as
you
have
on
the
slide
here
right,
the
minimum
system
resources
six
cpus
24
gigs
of
ram
that
can
be
virtual.
It
just
can't
have
a
cloud
provider
integration
inside
of
it.
Somebody
else
asked
me
recently
of
you
know:
how
do
we
determine
what
the
you
know
if
I'm
combining
roles?
B
What's
the
minimum
amount
of
resources-
and
it's
literally
you
just
add
them
together?
So
I
think
odf
or
ocs
with
4.8,
now
supports
a
compact
cluster
deployment
yeah.
So
you
would
want
to
if,
if
you
only
have
three
nodes
in
the
cluster,
you
would
want
to
sum
all
of
those
resource
requirements
together
so
for
a
control,
plane,
node,
it's
two
or
four
cpus
and
16
gigabytes
of
ram
for
a
worker
node,
it's
two
cpus
and
eight
gigabytes
of
ram,
which
is
how
we
get
to
six
and
24
here
right
and
for
ocs.
It's.
B
The
other
thing
I
wanted
to
highlight-
and
you
kind
of
already
said
this-
is
three
node
cluster.
You
can
absolutely
add
additional
worker
nodes
after
the
fact,
and
you
can
even
go
in
and
you
can
and
you
can
mark
the
control
plane
as
non-schedulable
after
the
fact
so
that
you
know
hey.
I
started
out
with
this
small
cluster.
Things
got
out
of
control.
Now
I
have
a
50
node
cluster
and
I
I
just
I
don't
want
the
control
plane
to
be
scheduling
workload
anymore.
I
want
it
to
be
focusing
on
doing
control,
plane
things
so.
C
Not
yet
no
it's
it's
one
of
the
things
that
we're
looking
at
nha,
I
think,
is
another
thing:
a
two
node
two
node
h,
a
single
mode,
is
another
thing,
that's
also
being
considered,
but
but
right
now
you
know
if
that
node
goes
down,
that
node
goes
down
and
you
replace
it.
Then
you
start
from
from
ground
zero.
So.
B
A
C
C
C
To
use
like
the
csi
provisioner,
or
something
like
that-
that's
true,
yeah,
yeah,
very
true,
okay,
next
slide
sure
single
node.
This
is
available
for
use
or
install
only
with
the
assisted
installer.
Currently
right,
so
you
go
to
cloud.redhat.com,
and
you
can
try
this
today
and
via
the
bare
metal,
assisted
installer.
C
B
C
C
C
I
think-
and
I
know
the
public
sector
has
been
playing
with
single
run
out
single
mode,
but
compact
clusters
on
hp,
like
el
8000,
000
yeah,
the
four
node
kind
of
looking
thing
that
they're
adding
additional
security
features
to
to
bring
that
up
for
some
government
agencies,
so
cool
yep
next
slide:
yeah,
okay,
acm
advanced
cluster
management.
So
it's
managing.
C
You
know
the
edge
just
like
the
core
right,
so
it's
multi-life
cycle
or
multi-cluster
life
cycle
management,
some
policy
driven
government
governance
and
risk
compliance
and
then
advanced
application
application
life
cycle
management
as
well.
If
you
want
to
roll
to
the
next
slide
real
quick,
we
can
get
a
little
bit
more
in-depth.
Look
at
what
acm
looks
like
from
an
edge
perspective
and
you
can
kind
of
see
far
edge.
What's
in
kubernetes
node
control
versus
the
cluster
management,
you
know
as
well.
C
C
It's
aimed
at
the
regional
distributed
and
on-prem
deployment
perspective.
So
it's
going
to
be
an
automated
path.
You
know
from
getting
you
know,
uninstalled
infrastructure,
to
getting
applications
on
on
an
openshift
cluster.
So
you
start
with
site
plan.
You
have
your
manifesting
git
and
then
you
deploy
via
ztp,
so
it
integrates
the
existing
technology
stack
for
acm,
which
is
hive
middle
cubed
and
the
work
being
done
on
the
assisted
installer.
C
The
goal
for
zero
touch
is
minimal
prerequisites
right.
So
hopefully
we
can
get
it
to
the
point
where
untrained
technicians
can
scan
a
barcode
to
trigger
an
install
right.
That's
the
goal
and
the
deployments
can
be
customized
as
well
here.
So
it's
you
know,
connected
disconnected
ipv4,
v6
and
then
dhcp
or
static
ip,
and
then
supports
the
upi
and
ipi
deployment
framework
as
well.
B
B
So
to
our
audience,
thank
you
so
much
for
joining
us
today.
Really
great
conversation
really
appreciate
you
on
all
your
questions.
Please
don't
hesitate
to
reach
out
at
any
time.
You
can
contact
me
at
andrew.sullivan
redhat.com
or
on
twitter
at
practicalandrews,
so
just
like
you've
seen
my
username
on
twitch
there
or
rebroadcast
across
all
the
others,
so
don't
hesitate
to
reach
out
if
you
have
any
questions,
if
there's
anything
we
didn't
get
to
today
and
with
all
of
that
being
said,
thank
you
so
much.