►
From YouTube: Ask an OpenShift Admin (Ep 62) | MicroShift
Description
Need to run Kubernetes at the edge? A small form factor version of OpenShift designed for edge computing devices would be great. This is exactly what MicroShift provides. This episode, Miguel Angel Ajo and Ricardo Noriega De Soto join the show to discuss MicroShift. They're both helping to develop Microshift - OpenShift tailored for edge computing. Don't know why developers might want OpenShift on a smaller footprint? Join us to learn more as we'll discuss how Microshift compares to other platforms, what features make it different, and how it manages to pack so much technology into a small form factor.
Want to learn more?
https://next.redhat.com/2022/01/19/introducing-microshift/?sc_cid=7013a000002qG1LAAU
Try Red Hat OpenShift: https://red.ht/3uVxkya
Follow us:
Andrew Sullivan https://twitter.com/practicalandrew
Jonathan Rickard https://twitter.com/jrocktx1
Ricardo Noriega https://twitter.com/rickynds
Miguel Angel Ajo https://twitter.com/mangel_ajo
OpenShift https://twitter.com/openshift
Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1
About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Jonathan Rickard sit down to answer your questions about Red Hat OpenShift.
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
OpenShift on redhat.com https://red.ht/3rYz5ZS
OpenShift on GitHub https://github.com/openshift/
#RedHat #OpenShift #Kubernetes #ContainerPlatform
A
B
D
Hello
and
welcome
to
this
week's
ask
an
openshift
admin
office
hours
live
stream.
I
am
as
always
your
host
andrew
sullivan,
so
as
the
the
ticker
down
at
the
bottom
states,
you
can
reach
me
on
social
media
at
practical,
andrew
on
twitter,
or
you
can
always
reach
me
via
email
at
andrew.sullivan
redhat.com
and,
as
always,
I
am
joined
by
my
I'm
going
to
use
the
word
effervescent
today.
Johnny
because
you
are,
you
are
very
effervescent
this
morning.
D
I
you
know,
I
can't
complain
it's
another
beautiful
red
hat
day,
so
indeed,
indeed
yeah,
it's
never
a
dull
moment,
and
today's
topic
certainly
reflects
that.
I
think
it's
something
that
when
the
the
blog
post
and
the
other
stuff
was
first
released
about,
it
was
first
talked
about.
There
was
a
tremendous
amount
of
excitement
around
microshift
and
the
possibilities
of
having
an
open
shift
or
an
openshift-like
environment
in
like
very,
very
small.
You
know
footprints,
so
we
we
jumped
at
the
opportunity
to
have
our
two
guests
join
us
today.
C
Hey
hello,
thank
you
very
much
for
having
us
and
spreading
the
the
word
about
microsieve.
So
I'm
miguel
I've
been
working
at
red
hat
for
eight
years
and
this
last
year
I
joined
the
city
office,
the
on
the
edge
team
for
emerging
technologies
and
yeah.
They
were
already
working
on
microsift
I
joined
them.
C
D
B
Hello,
everyone
yeah.
First
of
all,
thanks
for
having
us,
I
joined
red
hat
six
years
ago.
I
come
from
the
telco
world,
I'm
a
telecom
telecommunications
engineer,
and
about
two
years
ago
I
I
joined
the
emerging
technologies
group
in
the
edge
computing
team
and
yeah
about
a
year
ago.
Something
like
that.
We
started
to
think
how
we
could
feed
a
small,
kubernetes
and
open
shift
into
these
really
small
devices
and-
and
we
yeah
microchip
was-
was
born
so
very
glad
to
be
here.
D
D
Of
followers
yeah,
my
wife,
on
the
other
hand,
who
is
she's,
I
think
I
said
before
she's
an
exercise
instructor
like
everybody
around
town,
knows
who
she
is
like.
I
can't
go
to
the
grocery
store
with
her.
I
can't
can't
go
to
a
restaurant
without
people
stopping
to
say
hi,
and
you
know
we
just
have
the
internet.
We
have
all
of
you,
lovely
people.
B
D
D
D
So
if
anybody
has
any
thoughts
or
any
input
on
that,
please
please
don't
hesitate
to
reach
out,
especially
if
you're
watching
this
you
know
recorded.
You
know
where,
because
it's
not
your
working
hours
right
now,
when
we're
doing
this
live,
don't
hesitate
to
reach
out
again,
you
know
social
media,
practical,
andrew
or
email
andrew.sullivan
at
redhat.com,
because
we'd
we'd
like
to
know
right,
we
want
to
be
accommodating.
D
We
want
to
include
everybody
as
much
as
we
can,
and
if
that
means
you
know
varying
our
our
time
zone
a
little
bit,
I'm
okay
with
that,
so
we
do
have
a
what
I'm
going
to
call
a
reoccurring
segment.
I
keep
saying
that
as
though
it's
a
new
thing
like
I
haven't,
been
doing
this
for
what
62
episodes
now,
which
we
call
the
top
of
mind
topics
so
top
of
mind.
A
D
Oh
yeah,
the
I
replaced
it.
It's
I've
been
trying
to
have
a
more
regular
schedule
of
changing
out
my
artwork.
So
yesterday
was
the
first
day
of
spring
here
in
the
u.s.
Well,
I
guess
everywhere
spring
spring
is
the
same
everywhere
right,
so
I
decided
to
change
out
my
artwork
and
then
I
was
I
was.
I
won't
say
I
was
up
late.
I
was
up
late
for
me
like
10
30.
You
know
looking
at
other
artwork
that
I
can
use
in
the
future.
So.
A
D
The
the
business
t-rex
right,
so
it's
it's
very
spring-like,
so
first
top
of
my
topic
for
today
so
johnny
and
I
got
pulled
into
a
conversation
with
a
customer
recently
and
it
was
a
big
conversation
right.
I'm
using
big
in
air
quotes,
but
there's
a
big
conversation
around
auto
scaling,
and
you
know
we
talked
about
things
like
the
horizontal
and
vertical
pod,
auto
scalers.
D
We
talked
about
machine
and
cluster,
auto
scalers
and
we
happen
to
have
gorov
the
product
manager
for
scaling
in
openshift,
join
us,
and
I
learned
something
new,
so
we've
been
asked
about.
You
know
a
lot
of
people
have
been
asking
about
being
able
to
do
cluster
scaling
based
off
of
custom,
metrics
or
or
pod
scaling
rather-
and
I
I
remember
hearing
about
this
like
six
versions
ago-
and
nothing
is
ever
right-
it
kind
of
popped
up
and
then
never
nothing
ever
came
of
it.
D
D
So
the
the
keta
project,
kubernetes
event
driven
auto
scaling,
is
exactly
what
the
name
implies
right
and
you
can
see
down
here
under
scalars.
We
can
set
a
whole
bunch
of
differences
for
metrics
to
do
things
like
determine
when
I
want
to
scale
up
or
scale
down.
So
if
we
come
down
here,
there's
like
prometheus
right.
D
I
can
point
it
at
a
one
or
more
prometheus,
metrics
and
say
things
like
you
know,
hey
when
my
web
server,
you
know,
shows
more
than
x
number
of
connections
per
second
or
responses
per
second
or
something
like
that
scale
up.
So
it's
an
upstream
project
now,
but
I
did
check
the
the
what's
new.
What's
next
slides
and
it
is
on
the
roadmap,
so
I
think
it'll
be
a
tech
preview
feature
in
one
of
the
next
next
next
releases.
D
I
don't
think
it's
in
4.10,
but
we
do
have,
and
that
reminds
me
that
we
do
have
a
what's
next.
So
that's
a
roadmap
presentation
coming
up
in
early
february
sometime.
I
should
have
checked
on
this
beforehand,
but
it
just
now
occurred
to
me
early
early
may
or
april
early
april.
Yes,
I
don't
know
where
february
came
from.
D
What
that
was
all
about
so
yeah
anyway,
so
we
do
have
have
a
a
what's.
Next,
a
road
map
presentation
coming
up
so
keep
an
eye
on
the
stream
calendar.
So
if
you
are
not,
you
know
subscribed
if
you
don't
have
the
alerts
for
the
stream
coming
up.
I
would
also
encourage
you
to
go
to
red.ht
live
streaming
and
that
will
have
a
link
to
our
calendar.
So
in
the
calendar
there
you
can-
and
I
can
bring
that
up-
actually
dot
ht
live
stream.
D
It
takes
us
to
this
lovely
page
and
if
we
scroll
down
here,
we
have
this
episode,
calendar
and
I've
been
trying
to
do
a
a
better
job.
You
can
see
here.
We've
got
like
today's
topic
in
here
for
episode
62.,
but
if
we
scroll
down
through
here,
you
can
see
all
of
the
other
topics
that
are
here
and
if
you
click
this
little
plus
down
in
the
corner,
you
can
add
that
to
your
calendar.
D
So
it's
a
a
stretched
cluster
when
we
are
distributing
the
control,
plane,
nodes
across
multiple
locations
and,
of
course,
I'm
not
logged
in
so
I
just
posted
the
link
to
this
kcs.
This
kcs
has,
you
know
some
some
guidance,
some
things
to
consider
some
things
to
be
aware
of
when
you
are
deploying
a
a
cluster,
specifically
the
control
plane
nodes
across
multiple
sites,
whereas
remote
worker
nodes
are
where
your
control
plane
is
in
one
place,
but
your
worker
nodes
can
be.
D
D
While
they
are
supported,
they
can
be
complex
and
they
don't
often
meet
the
needs
that
you're
looking
for,
which
is
you
know
most
of
the
time
people
want
high
availability.
I
have
you
know
two
or
three
data
centers.
I
want
to
spread
out
my
cluster
across
them
so
that
way,
if
one
data
center
fails,
you
know
the
cluster.
D
The
open
shift
applications
keep
running,
but
you
know
my
opinion,
there's
so
much
that
can
go
wrong
there
that
you
often
end
up
with
lower
total
availability
of
the
cluster
and
the
applications,
because
you
know
some,
you
know
the
the
lawnmower
guy
ran
over
the
wrong.
You
know
sprinkler
head
and
it
caused
water
to
flood
into
the
the
fiber
box,
that's
running
underground,
which
caused
a
short
which
caused
you
know
the
the
campus
link
to
go
down,
and
now
the
two
data
centers
are
isolated
right.
D
A
D
Yeah
yeah
and
again
anybody
who
has
any
thoughts
or
comments
questions
feel
free
to
post
those
into
chat,
so
I've.
I've
got
two
other
things
here.
So
two,
hopefully
quick
things
so
one
I
happen
to
stumble
across
a
set
of
open
shift
checks.
So
you
can
see
this
comes
from
red
hat
cis
engineering,
so
this
is
stuff
that
was
created
by
red
hat
folks,
but
it
is
not
officially
supported
by
red
hat.
So
you
can
see
here.
This
is
an
unofficial
tool
right.
D
This
repo,
you
can
see
here,
there's
a
whole
bunch
of
checks
down
here
here
for
things
like
you
know,
I'm
entropy
for
doing
encryption,
and
you
know,
is
there
ovn,
pod
port
thrashing
you
know,
are
pvcs
that
aren't
bound
blah
blah
blah
right
there
lots
of
stuff
inside
of
here.
I
know
we've
had
a
lot
of
folks
ask
about
you
know:
is
there
something
I
can
use
to
check
the
health
or
the
status
of
my
openshift
cluster?
Aside
from
the
the
the
console,
the
overview
right
with
green
light
red
light
type
stuff?
D
A
A
D
D
So
even
though
you've
had
access
to
the
bits
for
at
least
a
week,
if
you
were
to
look
at
cloud.redhat.com
today,
you'll
see
a
number
of
blog
posts
that
talked
about
all
the
stuff
that
that's
in
4.10,
so
I'll
link.
This
blog
post
also
included
in
our
blog
post,
the
one
that
we
follow
up
with
here:
where's
the
right
window,
links
to
the
other
episodes
the
other
streams
that
we've
done
on
opengif4.10
and
then
so
that's
the
last
top
of
my
topic.
I
had
johnny
you
you
had
one
or
two.
I
think.
A
A
I
don't
want
to
say
it's
terraform,
but
it's
it's
an
iec
tool
like
terraform,
but
it's
more
from
like
a
programmer's
perspective,
so
you
can
use
different
languages
like
you
know,
go
python,
you
know
whatever,
and
you
can.
You
know
completely
configure
a
deployment.
So
I'm
posting
a
link
here.
If
you
don't
mind,
sharing
that
link
yeah,
if
you
guys
just
go
check
it
out
and
then
you
know
pulling
me
seems
like
a
pretty
cool
tool.
Both
the
cats
had
a
good
time
doing
it.
A
It
was
a
pretty
good
presentation,
so
go
check
it
out.
If
you
have
some
time
and
then
the
last
one
is
ansible
automates
is
tomorrow
it's
a
free
event
that
red
hat
puts
on
the
link
should
be
popping
up
pretty
soon
here.
So
if
you
get
some
time,
go
check
out,
what's
going
on
with
danceball
and
yeah,
hopefully
help
you
learn,
that's
it.
D
D
D
All
right
well
so
today's
topic
so
as
as
we
started
the
stream
with
today,
our
topic
is
microshift
and
steven
reeves.
I
see
your
your
comment
there
about
multi-node
and
some
other
things.
So
I
wanted
to
kick
this
off
by
handing
over
to
ricardo
and
miguel
to
talk
about,
you
know
kind
of
one,
what
is
microshift,
what
what
makes
microshift
micro
shift
and
not
open
shift,
and
you
know
kind
of
go
from
there
and
talk
about
use
cases.
D
B
B
B
So
the
thing
is
where
what,
if
we
want
to
use
in
in
these
edge
computing
use
cases
in
this
edge
computing
scenarios?
What
if
we
want
to
use
kubernetes
applications
that
the
same
applications
that
we
have
design
or
build
for
for
openshift?
And
this
is
where
microshift
started.
We
we
created
microsieve
to
fill
that
gap
in
in
the
middle.
B
B
B
D
D
It's
rpm
os
tree
based,
it's
really
optimized
for
containers,
and
I
saw
a
really
interesting
demo
recently
of
using
openshift
pipelines
to
build
an
application
and
do
things
like
you
know,
use
acs
to
do
container
image
scanning
and
all
that
other
stuff
and
then
push
that
to
a
registry
and
then
use
ansible
automation
platform
to
push
that
out
to
rel
for
edge
nodes.
You
know
and
and
have
it
run
on
or
via
podman
out
at
those
nodes.
So
I
thought
that
was
really
interesting
and
kind
of
very
much
to
your
point
here
of
it's.
D
It's
rel,
so
you're
managing
it
in
the
railway
as
opposed
to
openshift
or
kubernetes,
where
you're
managing
it
in
the
kubernetes
way,
which
is,
I
think,
the
primary
difference
between
you
know,
relf
for
edge
and
and
micro
shift
right.
So
so
questions
so
sean
asks.
What
do
you
mean
when
you
say
edge
computing?
C
C
D
Yeah
and
I
think
it's
it's
hard
to
narrow
down,
because
the
use
cases
are
almost
unlimited
right,
because
I
mean
you
can
consider
you
know
a
a
retail
scenario
right
where
you
know
I'll
pick
on.
You
know
pick
any
big
box
retail
store.
You
know
walmart
target,
etc.
If
they
have
it
resources
in
the
stores,
you
could
consider
that
edge
the
same
thing
with
like
restaurants,
right
mcdonald's.
D
If
they
have
I.t
resources
in
those
stores,
you
could
consider
that
an
edge
you
know
yeah.
I
think
one
that
a
lot
of
people
don't
think
about.
Is
things
like
the
electronic
billboard
signs
that
we
see
here
in
the
us
on
the
side
of
the
highway,
like
those
are
edge
devices
right.
So
it's
really
almost
unlimited
different
use
cases.
C
D
D
And
like
crc
mini
cube,
yeah
crc,
so
on
and
so
forth.
You
know:
frost
mcgeddon
here
is
it
frost,
mcgedden
and
I'm
losing
track
of
it?
I'm
losing
track
of
my
chat
here:
frost,
mcgeddon.
What's
the
difference
between
okd
and
microshift
right
okd
is
the
upstream
version
of
openshift.
So
it's
a
full
open
shift
in
that
respect.
So
I
I
think,
we're
getting
ready
to
answer
those
questions
in
the
slides
that
that
you
had
up.
B
Sure
the
we
have
designed
microshift
with
the
goal
of
fulfilling
the
edge
computing
use
cases
that
we,
you
know
that
we
have
in
mind
mini
cube,
microcades
and
so
on.
The
the
first
idea,
it's
more
like
a
development
environment
or
for
your
home
lab
or
to
to
get
some
kubernetes
in
a
in
a
resource-constrained
environment
that
microsoft
can
do
as
well,
but
our
target
our
main
goal.
It's
been
always
edge
computing.
B
Let
me
finish
very
quickly.
The
the
slides
microshift
as
well
as
openshift
can
be
managed
by
acm.
You
know
advanced
cluster
manager
and
the
way
that
we
have
built
microshift
is
basically
a
single
binary
that
contains
all
the
control
plane.
The
kubernetes
control,
plane,
openshift
apis,
cubelet
cube
proxy,
all
the
components
in
a
single
binary.
B
B
It's
an
rpm
package
or
container
image
and
we
have
an
extra
which
is
an
all-in-one
container
image
that
contains
our
cryo,
the
container
runtime.
So
it
can
also
work
in
macos
windows
and
so
on.
We've
built
microshift
in
different
architectures,
basically
x86
and
arm,
but
also
risk
5
and
power
pc
and
so
on.
B
B
B
B
B
So
in
the
left
side
we
have
open
shift
and
the
openshift
has
been
designed
is
that
it's
like,
like
a
whole
stack,
so
we
have
railcar
os
as
the
operating
system
and
it's
it's
a
fundamental
part
of
open
shifting.
In
the
end,
then,
we
have
kubernetes
plus
the
openshift
apis
that
that
we
provide-
and
we
have
a
bunch
of
cluster
operators
that
will
manage
the
cluster
from,
for
example,
the
cluster
version
operator
that
will
manage
the
versions
of
the
protein
system
and
the
components
the
machine
api
operator
that
can
manage
the
infrastructure
itself.
B
D
So
a
couple
of
things
here
so
one
observation
for
me-
is
this
kind
of
goes
back
to
the
model
that
we
had
with
openshift
3
right
of
the
the
underlying
operating
system
and
its
management
is
decoupled
from
the
microshift
management
right.
So
in
this
model
you
don't
have
machine
config
operator,
for
example,
that's
going
in
and
pushing
down.
You
know
a
rel
for
edge
rpm
os
tree
updates.
Instead,
you
would
manage
that
operating
system.
The
way
that
you
always
have
you
just
have
that
micro
shift.
D
B
Microshift
is
a
an
open
source
project.
It's
not,
let's
say
a
product.
Our
goal
is
to
get
it
productized,
but
so
far,
is
it's
just
a
a
project
that
from
the
office
of
the
cto
we
launched?
And
if
you
let
me
go
here
just
there
too
too
much
information
here.
But
if
you
look
at
at
how
we
build
microshift,
basically
we
are
pulling
the
objects
from
okd.
B
So
we
is,
as
you
mentioned,
the
upstream
version
of
openshift
and
since
microsoft
is
an
open
source
and
upstream
project.
So
far,
we've
pulled
versions
from
okd,
so
every
component
that
is
embedded
in
the
microsoft
binary
all
the
extra
services
that
are
running
as
pods
schedule.
Pods
are
also
container
images
pulled
from
the
okay,
the
repositories.
So
the
latest
version
of
microship
is
pointing
at
four
point:
eight,
okay
and
we
are
working
on
the
rebase
to
4.10.
B
Microchip
does
not
provide
cluster
operators,
but
we
can
deploy
operators
on
top,
so
we've
tried,
for
example,
submariner
we've
tried
cmv
cubeverd
we've
tried
yeah.
There
are
plenty
of
operators
that
you
can
deploy.
You
can
even
deploy
olm
in
case
you
want
to
have
the
catalog
and
so
on
and
deployed
from
olm
the
application.
B
D
Yeah,
I
I'm
I'm
not
gonna,
give
christian
a
hard
time
this
week
he's
on
pto,
so
I
I
usually
only
do
it
when
he's
here,
and
I
know
he
he
shouldn't
be
listening
this
week
because
he
because
he
better
be
on
on
and
enjoying
his
pto
yeah.
He
needs
it
yeah.
So
I
I
also
saw
thomas
tom
paul
asked
about
what
is
the
recommended
tooling
for
managing
the
underlying
operating
system
and
hardware
with
microshift
and
miguel.
I
think
that
was
something
you
were
gonna
address.
C
Yeah,
so
we
are
working
on
the
I
mean,
along
with
microsoft,
we
are
working
on
the
whole
end-to-end
history
about
how
how
to
manage
devices
on
the
ads.
So
I
mean
our
goal
for
microsoft
was
its
devices
so
its
devices?
Normally
you
I
mean
you
manufacture
them,
you
configure
them,
and
then
you
put
them
on
the
field
or
a
variation
of
of
this
or
you
put
them
on
the
field
and,
as
you
put
them
on
the
field,
they
are
going
to
configure
the
way
you
want
them
to
to
be.
C
C
This
is
one
of
one
of
the
reasons
why
we
are
building
on
real
it
because
it
uses
os3
and
with
os3,
is
very
easy
to
get
your
device
connected
to
an
os3
repository
and
and
get
atomic
updated
updates
of
of
your
operating
system.
That
operating
system
could
be
an
image
that
contains
the
role
for
it,
minimal
tools,
microshift
and
even
if
your
device
is
not
going
to
have
like
a
very
stable
connection
or
or
you
want
to
pre
configure
the
device
before
you
send
it
into
the
field
you
could.
C
Even
I
mean
we
are
developing
the
mechanisms
to
embed
the
container
images
into
the
os3
image.
So
as
soon
as
you
boot,
you
have
microsieve
the
container
images.
Your
end
applications
in
in
container
images
too
and
and
the
deployment
the
details
for
your
application.
So
microsoft
boots
are
so
rel
forex
boots
microchip
boots
inside
real
forage
and
your
applications
start
inside
microsieve.
C
C
We
are
also
looking
for
for
scaling
that
so,
as
you
know,
ecm
was
designed
to
to
handle
lots
of
clusters,
but
maybe
in
the
use
cases
we
are
looking
into
the
thousands
or
hundreds
of
thousands
of
devices
and-
and
we
need
to
make
that
scale
but
yeah.
We
are
mostly
designing
around
managing
everything
via
the
the
the
os3
enroll
for
it
acm
and.
D
Yeah
and
I'm
thinking
back
to
the
the
what's
new
in
openshift
4.10
presentation,
where
we
we
you
know,
announced
to
the
world
that
we're
working
with
oems
to
pre-install
openshift
onto
you,
know,
hardware
and
so
very
much
like
what
you
have
in
that
upper
left-hand
block
there.
You
know,
put
put
microshift
on
there
and
ship
it
out
and
turn
it
on,
and
it
can
connect
up
to
the
world
and
you
know,
fall
underneath
management
automatically.
And
you
know
that
very
much
to
that.
Hundreds
of
thousands
of
nodes
thing.
B
B
If
you
want
to
include
also
microc
view,
you
would
be
able
to
do
that
and
then,
once
you
have
your
image
you
you
can
send
it
to
your
manufacturer.
It
will
be
image
into
2000
devices
and
sent
to
the
remote
locations,
and
once
you
connect
them,
it
will
be,
you
know
all
automatic.
So
if
you
want,
we
can
do
the
demo
very
quickly
and
I'm
sure
there
will
be
more
more.
B
B
Let
me
open
the
terminal
okay,
so
I've
created
a
fedora,
a
vagrant,
fedora
vm,
and
what
I'm
gonna
do.
Do
you
see
both
sides?
Yes,
yes,
yes,
okay,
so
I'm
gonna
follow
the
official
documentation
to
see
that
it's
working.
We
have,
as
mentioned
two
different
ways
of
the
of
deployment
rpm
based
and
container
image,
based,
let's
do
the
rpm
based,
which
is,
let's
say,
the
easiest.
B
I
don't
think
we've
planned
to
push
it
to
cncf
like
as
a
you
know,
as
a
personal
opinion,
I
don't
know
if
it
makes
sense
to
have
distributions
in
cncf,
because
it's
the
core
components
are
basically
the
same.
It's
just
a
matter
of
how
how
you
package
them
and
well
yeah
for
for
microchips.
I
don't
think
so
far.
It's
in
our
plans.
Let's
see.
D
B
So
here
we
are
enabling
the
the
copper
repo,
where
we
have
where
we
store
the
microsoft
rpms.
We
are
installing
microchip
adding
some
firewall
rules
to
open
some
ports
and
launching
microsoft.
Basically,
the
rpm
package
deploys
a
systemd
service
and
once
microshift
is
up
and
running,
you
will
see
the
logs
in
in
the
journal
and
so
on.
It's
like
a
another
application
right.
A
D
The
female
yep
yeah
mike
murphy
pies
are
hard
to
come
by
yeah.
Thank
you.
Global
chip
shortage
pandemic
supply
chain
issues.
All
that
other
nonsense.
I've
been
trying
to
get
some
for
months
for,
for
various
reasons,
and
just
I've
been
unable
to
without
paying
exorbitant
prices
that
I'm
unwilling
to
pay.
B
A
B
C
Yeah,
so
for
for
disconnected
environments,
I
mean
you,
you
need
to
put
the
the
container
images
that
we
use
into
the
system.
So
we
it's
it's
not
on
the
repository.
Yet
we
need
to
finish
a
few
things
because
it
it
was
a
complex
thing,
but
we
we
managed
to
to
package
the
container
images
into
another
rpm.
C
So
if
you
want
you
can
install
the
in
that
rpm
and
it's
going
to
go
to
cryo
and
configure
like
a
local
grid,
only
storage
for
those
containers
and
and
then
there
is
no
more
download
that
needs
to
happen.
You
can
just
install
microshift
install
the
the
package
with
the
containers
and
then
it's
completely.
I
mean
it
could
run
completely
offline,
gotcha.
B
Just
to
mention
when
microshift
starts
the
rpm
version
of
microshift,
it
will
create
a
folder
in
slash
vars.
Lastly,
microshift
and
there
you
have
all
the
resources,
all
the
cubeconfig
files
certificates,
configuration
for
each
of
the
components
and
so
on,
and
the
the
way
that
the
user
interacts
with
microsoft
is
basically
using
the
cube
config
file
with
for
the
cube
admin
user.
So
we've
copied
it
to
the
default
location
and
yeah.
Here
in
vardlip
microsoft,
you
can
see
all
these
resources.
B
C
C
I
think
we
don't
have
arm
64
yet,
for
example,
in
okd.
I
think
it's
something
that
is
being
worked
out,
so
we
we
build
our
own
images
for
that
and
something
that
I've
noticed
is
that
the
the
images
that
we
managed
to
build
are
much
smaller
than
the
ones
from
from
openshift.
So
I
was
thinking
about
taking
providing
some
feedback
about
how
to
hopefully
optimize
those
images.
It
will
mean
removing
things
that
are
on
the
system
that
I
I
don't
know
I
mean.
C
B
Yeah,
so
we
we
have
these
two
different
deployment
models.
You
know
one
of
them
has
some
advantages
and
disadvantages
and
so
on,
for
example,
we
have
always
in
mind
the
edge
computing
use
case.
So
in
case
of
rail48,
you
have
you
know
you,
you
go,
you
install
image
builder
and
you
want
to
create
your
own
rail48
customized
version
of
of
reference
right
and
you
you
will
include
in
the
rpm
os3.
B
What
are
the
benefits
of,
for
example,
running
microshift
as
a
as
a
container
in
case
that
we
want
to
upgrade
microshift
without
impacting
the
workloads
that
are
running
our
applications?
It's
just
a
as
simple
as
creating
a
new
tag.
You
know
like
upgrade
a
container,
that's
that
will
not
have
any
impact
on
the
applications
that
are
running
on
microsoft,
because
in
the
end
they
are
running
on
top
of
cryo.
B
In
case
you
want
to
have
everything
included
in
the
rpm
os3.
You
will
use
the
rpm
to
to
to
have
an
immutable
operating
system
and
when
you
have
to,
when
you
upgrade
the
whole
os3,
you
will
have
to
reboot
that
will
have
some
workload
downtime
right.
So
it
depends
on
on
how
you
want
to
to
deploy
your
devices
and
and
manage
your
your
devices.
D
D
B
A
And
there's
another
question
from
mike
murphy
about:
essentially
he
was
asking
like
once
you
have
the
micro
shift
up,
realistic
or
theoretically,
you
could
use
an
internal
registry
if
you
wanted
to
write
like
I'm
assuming
he's
talking
from
another
like
oc
cluster
but
like.
If
you
wanted
to
run
a
registry
on
microsoft,
it's
essentially
just
running
either.
You
know
like
the
docker
registry
and
then
exposing
it
that
way,
or
you
know
just
any
other
deployment
type
for
register
right.
B
Yeah
for
for
the
components
that
are
embedded
into
the
binary,
we
basically
use
the
libraries
we
we
don't
pull
any
image
from
anywhere.
It's
basically
using
you
know
from
this
from
the
binary
from
a
central
service
manager
that
we
have
implemented,
you
will
use
the
different
versions
of
the
components,
basically
using
gold
modules
and
so
on,
and
for
the
infraservices
that
that
you
can
see
here
that
are
running,
we
point
at
certain
tags,
from
okd
images
and
for
the
disconnected
environment.
C
I
shared
a
link
to
our
image
repository,
but
if
you
I
mean
in
in
there,
we
we
create
like
multi-architecture
tags
for
for
the
images.
But
if
you
deploy
microshift
on
an
intel
platform
and
you
look
at
the
at
the
bots,
you
will
notice
that
we
are
not
using
that
repository.
We
are
just
using
the
the
okd
image
tags
from
the
okd
repository.
C
B
B
B
D
B
C
B
So
now
it
will
try
to
install.
So
we
have
the
cluster
that
running.
Acm
has
recognized
microshift
as
an
imported
cluster.
Now
some
addons
will
will
be
deployed.
This
takes
a
little
bit,
but
we
can.
We
can
continue
with
creating
our
own
applications
and
one
once
the
the
cluster
is
fully
imported,
let's
say,
or
with
all
the
add-ons
and
so
on,
it
will
apply
and
install
our
our
application.
B
Let
me
remove
some
tags
that
maybe
we
don't
need
here,
for
example,
the
aim
certainty
policy
policy
control-
okay,
let's
let's
keep
it
like
this.
This
is
like
you
know,
as
as
many
add-ons
as
we
add
there
will
be
less
room
for
applications
right.
So
I
don't
know
if
the
add-on
controller
is
it's
not
yet
there,
but
let's
go
to
the
applications,
tab
in
acm
applications
and
I'm
going
to
install
a
very
simple
application.
It's
an
nginx
with
a
service
we
create
application
subscription.
D
D
It's
open
cluster
dash
management,
dot
io,
so
it
doesn't
have
all
of
the
you
know,
gui
stuff
right,
because
that's
what
they
you
know,
that's
all
the
red
hat
stuff
that
they
add
on,
but
all
of
the
functionality
all
of
the
stuff
that
you
do
through
the
kubernetes
api,
because
remember
everything
is
just
a
kubernetes
crd
inside
of
there.
All
of
that
stuff
is
there.
So
I
found
that
out.
I
was
working
with
jimmy
alvarez
recently
and
found
that
out.
D
So
so
one
thing
that's
interesting
to
me,
is
you
know
you're
you're
using
you
know,
oc
get
pods
and
other
oc
commands
here.
Can
you
like
from
the
host?
If
you
were
to
do
just
a
podman
ps?
Would
you
see
all
of
those
containers
running
there
or
is
it
through?
You
know
creo
or
cryo,
or
something
like
that.
So
would
you
use
crack
control.
B
D
So
it's
very
much
like
open
shift
right
if
you
were
to
debug
to
an
open
shift,
a
core
os
node
and
you
know
if,
if
you
do
a
sudo
or
seo
over
to
root,
you
can
use,
you
know,
cry
cuddle,
cry,
control
and
just
like
we
see
here
see
all
of
the
all
of
the
container
images
that
are
running
inside
of
there.
So
that's
that's!
Really
cool.
A
A
B
B
B
Here
acm
through
the
the
wizard
or
the
gui,
it
creates
the
subscription
and
the
placement
rules
I've
clicked
on
deployed
on
all
online
clusters.
So
this
is
the
placement
rule
and
it
will
take
a
little
bit
until
microsoft
is
detected
as
up
and
running
and
fully
imported,
and
then
it
will
deploy
the
application.
D
B
D
So
that
does
ask
or
bring
up
a
couple
of
interesting
questions
and
and
frosm
again.
I
think
you
asked
earlier
so
one
is
there.
When
multi-node
becomes
a
thing,
will
we
follow
the
same
control,
plane
requirement
node
count
requirements
that
openshift
does
so
you
know
one
or
three,
or
can
we
have
five
or
seven
or
nine,
and
then
also
is
there
like
a
minimum
requirements
for
microshift
like
can
I
use
a
raspberry
pi
with
you
know,
2
gigs
of
ram?
D
B
D
Yeah
we've
talked
about
before
here
on
the
stream.
How
going
beyond
three
control
plane
nodes
is
often
an
a
counter-intuitive
anti-pattern,
because
you
add
so
much
complexity
that
it
can
make
things
more
fragile,
mike
murphy.
Is
there
a
recommended
operating
system
when
running
in,
for
example,
a
raspberry
pi?
D
A
B
Of
course,
rpm
won't
work
on
on
those
environments,
but
you
can
download
the
code
and
compile
it
and
if
cryo
is
installed,
it
would
work.
Also,
the
container
image
would
work
if
you
can
deploy
it
on
docker,
for
example,
in
in
the
main
website.
There
is
also
what
we
call
an
application
development
microchip
deployment
model,
which
is
this
all-in-one
image,
so
you
can
deploy
a
container
in
your
mac,
os
or
windows,
and
it
will
have
microchip
plus
cryo
plus
all
the
dependencies.
C
B
D
Well,
so,
to
be
clear,
I
I
work
for
you
all
for
the
next.
However
long
you
want
to
be
on
the
stream,
so
I
want
to
be
respectful
of
your
evenings.
I
know
it's
getting
kind
of
late
in
the
day
for
you,
so
I
don't
want
to
eat
into
too
much
of
that
time.
So
for
our
audience,
if
you
have
any
questions
or
anything
like
that,
please
feel
free
to
submit
those
and
we'll
do
our
best
to
address
all
of
those,
and
you
know,
try
and
keep
to
a
reasonable
time.
D
D
Well,
it's
it's
so
funny
right
because
I've
been
recently
having
some
conversations
with
folks
around,
like
you
know,
is,
should
we
expect
or
be
surprised
when
kubernetes
works
the
way
it's
supposed
to
right?
It's
a
seven-year-old
project
or
you
know
kubernetes
1.0
was
may
of
2015.
I
think
so.
You
know
it's
seven
plus
years
that
it's
been
around
and
it's
sometimes
it
still
feels
like
people
are
surprised
when
kubernetes
does
exactly
what
it
is
supposed
to
do
like.
No,
we
shouldn't
be
surprised,
that's
what
we
should
expect.
D
So
a
couple
of
questions
in
here-
let's
see
so
felipe,
I
know
we're
talking
about
microshift,
but
can
I
use
single
node
openshift
for
edge?
Yes,
you
absolutely
can
so
the
big
difference
there
is
single
node.
Open
shift
is
going
to
be
a
quote:
unquote:
full
openshift
right.
It's
going
to
have
things
like
the
metric
service
and
operator,
lifecycle
manager
and
machine
config
and
all
all
of
those
other
things
inside
of
there.
D
Whereas
microshift
and
please
correct
me
if
I'm
wrong,
microshift
is
really
targeted
at
providing
that
openshift
api
for
deploying
you
know,
containerized
applications
to
those
ultra
low
resource
edge
devices,
it
doesn't
have
to
be
ultra
low
resource,
but
that
that's
one
of
the
goals.
So
it
doesn't
have
a
lot
of
those
other
things
and
it
may
make
sense
for
a
lot
of
different
use
cases
install
podman
on
your
macbook.
I
I
don't
they're
still
working
out
kinks
with
podman
on
the
m1.
D
C
D
B
D
A
B
B
We
are
trying
to
stabilize
it
as
much
as
possible,
rebase
it
to
4.10,
okay,
d4
to
10
and
yeah,
get
better
support
for
different
use
cases,
for
example
miguel.
If
you
can
copy
the
the
devconf
youtube
video
that
we
have.
We
did
this
demo
about
aids,
where
we
used
microsieve
to
in
one
of
these
nvidia
jetson
boards,
and
there
we
deployed
microshift
and
an
application,
a
face
recognition,
application
on
top
and
we
used
really
low
end
equipment
with
five
bucks
cameras,
esp
cameras
and
and
and
the
nvidia
gets
on
board.
B
B
Yes,
it
can,
we
have
deployed,
I
mean
in
in
regarding
the
jetson
family.
There
is
this,
what
it's
called
nvidia
container
runtime,
that
you
hooked
up
to
cryo
and
then
you
can
access
the
gpu,
the
integrated
gpus,
and
we
have
also
tried
in
a
discrete
gpu
environment,
where
you
have
the
the
cards
to
install
the
gpu
operator
the
same
as
in
in
openshift,
and
the
device
plugin
will
take
the
gpu
device
and
the
workload
can
can
see
it.
We
have
tested
that.
C
Yeah,
but
just
keep
in
mind
that
I
mean
there
are
still
no
nvidia
drivers
in
fedora,
for
example.
So
in
our
testing
we
were
using
linux,
the
linux
for
tegra
distribution,
that
the
media
builds
with
their
own
kernel
and
so
on,
and
then
we
we
used
a
non-containerized
microshift
inside
because
we
need
to
use
the
nvidia
container
runtime.
So
one
option
could
have
been
using
the
microsift
all
in
one.
C
C
We
did
it
by
installing
the
the
microsd
binary,
but
probably
if
you
install
cryo
and
then
on
on
the
linux
for
tera,
and
then
you
install
the
micro
shift
container,
not
the
only
one
just
the
microchip
container,
it
should
theoretically
work.
Otherwise,
the
binary
the
binary
works,
and
we
know
that
the
media
is
working
to
have
full
support
for
upstream
capitals.
D
C
C
D
I
feel
like
that's
one
of
those,
the
gosh.
When
was
it
that
I
think
it
was
dockercon,
they
had
the
thing
with
kubernetes
objects
and
minecraft,
where,
like
when
you
it
like
imported
all
of
the
kubernetes
objects
into
different
animals.
I
was
just
having
a
conversation
about
that
with
somebody
the
other
day.
D
D
If
there's
anything
that
comes
up
if
you're
not
watching
this
live,
please
don't
hesitate
to
reach
out
to
us,
so
you
can
reach
me
at
practicalandrew
on
social
media,
so
twitter
reddit
all
of
the
things
I
have
basically
the
same
username
and,
of
course,
email
as
well.
Andrew.Sullivan,
redhat.com
and
johnny
is
johnny
j-o-n-n-y
at
redhat.com
and
j-rock
t-x-1.
D
Did
I
get
it
right?
Johnny?
Yes,
it's
only
taken
like
20
shows
for
us.
You
know
together
for
you
to
remember
that.
Never
too
late
man,
it's
never
too
late.
So
thank
you
so
much
for
joining
us
miguel
ricardo.
This
has
been
really
phenomenal
and
it
it.
It
has
really
got
me
excited
about
a
lot
of
things
I
can
do
in
my
home
lab
and
my
wife
is
going
to
be
upset
because
I'm
probably
going
to
accelerate
my
my
purchasing
plans
for
some
raspberry
pies,
so
yeah
this.
This
has
been
really
great.
D
D
Yeah,
thank
you.
Thank
you.
You
all
are
welcome,
anytime.
If
there's
any
time
anything
that
you
ever
want
to
talk
about
on
the
stream.
I
know
everybody
would
love
to
hear
from
you.
So
for
our
audience.
Thank
you
for
joining
us
today.
We
will
be
back
next
week.
I
don't
think
we
know
what
our
topic
is
yet
johnny
stephanie
is
behind
the
scenes.
D
You
know
shaking
her
fist
at
us
because
we
haven't
haven't
gotten
a
tour
yet
so
we'll
figure
that
out
and
then
april
six
we're
gonna
have
kirsten
newcomer
join
us
to
talk
about
security
and
openshift,
so
yeah,
that's
gonna,
be
really
good
yep,
so
we'll
we'll
figure
out
what
we're
talking
about
next
week
keep
an
eye
on
the
calendar,
keep
an
eye
on
all
the
social
media
and
we'll
publicize
that
but
yeah.
Thank
you,
everybody
for
joining
us
and
johnny
I'll
leave
you
with
the
last
word.