►
From YouTube: The Level Up Hour (E56): Unboxing Red Hat OpenShift
Description
What is Red Hat OpenShift, and why should you learn more about it? Join us for an introductory look at Red Hat OpenShift Container Platform. If you're new to Kubernetes, using containers or want to build, deploy, and manage applications in a cloud environment, then OpenShift is a good place to start. In this episode, we'll take a look at the open source, enterprise-grade Kubernetes platform with fresh eyes and discuss how it can help manage containerized applications across on-premise, private cloud, and public cloud infrastructure. So join us to learn more as we unbox Red Hat OpenShift.
Learn more: https://www.redhat.com/en/technologies/cloud-computing/openshift
Want to try OpenShift?
https://www.redhat.com/en/technologies/cloud-computing/openshift/try-it
Follow us:
Scott McBrien https://twitter.com/stabby_mc
Randy Russell https://www.linkedin.com/in/randy-russell-0312243
Jaafar Chraibi https://twitter.com/ChraibiJc
What is the Level Up Hour?
Every Wednesday at 9am ET we stream live demos on how Red Hat Enterprise Linux (RHEL) users and admins can benefit their organizations and improve their careers by learning how to use containers, Kubernetes, and Red Hat OpenShift.
Learn more at:
https://red.ht/leveluphour
http://red.ht/3ayHlHI
How to participate in the The Level Up Hour:
Watch on YouTube every Wednesday at 9amET
Chat with us on Discord https://discord.gg/5VMVGJt
Check out our GitHub repo https://github.com/level-up-hour/
About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
https://www.openshift.com/
https://github.com/openshift/
#RedHat #RHEL #tluh
A
Geos
and
then
you
can
optimize
the
the
traffic,
so
you
can
have
central
images
that
are
mirrored
to
local
registries.
Of
course,
in
an
automated
way,
and
then
you
can
optimize
the
traffic
between
your
original
openshift
clusters
and
that
regional
quay
registry
that
you
have
there,
but
you
are
still
optimizing.
A
The
management
of
of
your
your
registries
and
because
the
the
registries
are
such
a
critical
part
of
your
architecture
que
has
an
architecture.
So,
basically
you
can
have
disaster
recovery
scenarios
or
architectures,
and
that's
also
something
that
you
probably
want
to
envision
when
you
have
critical
workloads
that
are
running
on
your
openshift
clusters.
A
B
A
Okay,
so
I'm
switching
to
so
first
thing:
how
do
we
get
access?
We
we
now
know
what
openshift
is
we
want
to
try
it.
We
want
to
experiment
with
it.
How
do
we
do
that?
So
if
you
go
to
try.openshift.com
you're
going
to
end
up
on
this
page-
and
it
shows
you
that
you
have
at
least
three
starting
points
where
you
can
start
digging
into
the
platform,
there's
what
we
call
the
developer
sandbox
and
it's
basically
a
30
days,
free
trial
that
we
host
for
you,
you
just
have
to
go.
A
A
A
Exactly
yeah,
so
this
is
a
full-fledged
open
shift
with
all
the
the
latest
innovations
that
we
provide
in
there.
It's
not
restricted,
I
would
say
in
terms
of
content
or
in
terms
of
experience,
it's
just
that
it's
limited
in
the
in
the
in
time.
So
it's
30
days
to
try
and
see
if
that's
something
that
you
want
to
to
go
further
with,
you
can
start
as
managed
services
with
your
cloud
accounts.
A
B
Right
so,
if
I
might,
we
did
have
some
technical
difficulties
earlier
where
we
were
not
necessarily
streaming
everywhere.
We
seem
to
have
addressed
some
of
those,
and
so
maybe
some
folks
are
joining
us.
I
just
wanted
to
say
very
briefly
today
we
are,
you,
know,
rewinding,
coming
out
of
the
deep
dive
and
and.
B
Talking
about
what
is
openshift
and
getting
some
back
background
from
jafar
on
the
fundamentals
of
what
openshift
is
what
what
comprises
it,
and
you
know
what
the
what
it's
about
from
both
you
know
administrator
perspective
and
also
from
a
developer
perspective
and
so
jafar
back
to
you.
I
just
wanted
to
kind
of
put
in
a
little
bit
of
an
explanation
there
for
the
folks
who
might
have
been
joining
us
late,
yeah.
A
Sure
thanks
so
I'm
gonna
go
and
hit
that
that
starter
trial
for
the
self-managed
part.
Just
to
give
you
an
overview
of
how
you
can
do
things,
and
so
basically
you
see
that
there
are
a
lot
of
supported
architectures
you
can
deploy
on
bare
metal,
z,
power,
openstack,
rev,
vsphere
or
just
any
agnostic
infrastructure,
which
is,
which
is
what
we
refer
to
as
the
upi
user
provision
and
depending
on
the
path
that
you
choose,
you're
going
to
have
guided
instructions
to
to
do
the
installation.
A
A
A
It's
gonna
ask
me
for
some
parameters
where
I
want
to
deploy
the
platform
mode
version,
and
afterwards
all
I
have
to
do
is
so
I
can
say
I
want
to
add
hosts
and
the
way
it
works
is
you
are
going
to
generate
either
a
full
iso
or
a
minimal
iso
image
that
you
are
going
to
load
on
your
target
environment.
So
this
is
mostly
directed
at
bare
metal
installations,
and
it's
going
to
generate
an
iso
that
you
push
on
your
bare
metal
instances
and
the
the
the
the
node
on
which
you
run.
A
The
the
iso
is
going
to
report
back
to
the
to
this
ui
and
get
configured
as
a
master
or
a
a
node
for,
for
instance.
So
it's
a
very
easy
way
to
to
do
the
installation,
and
I
I
really
love
the
way
that
we
have.
We
are
making
it
even
easier
for
our
customers
to
deploy
openshift
on
their
target
environments.
A
What
I
wanted
to
cover
regarding
installation,
so
you
have
the
cli,
which
was
the
traditional
way
of
doing
the
openshift
installation,
and
now
we
have
also
that
assisted
installer,
so
a
same
tech
preview,
but
we
are
going
to
release
it.
As
you
know.
Basically,
we
have
the
full
the
traditional
workflow,
where
we
have
dev
preview
tech
preview
and
then
it
goes
into
ga
okay,
so
that
wasn't
in
terms
of
installation.
A
A
A
B
A
Yeah,
so
I
I
actually
in
the
early
days
of
of
trying
to
enable
people
on
what
operators
are
in
terms
of
kubernetes
landscape.
I
had
a
funny
picture
where
it
was
actually
a
gift
where
there
was
a
a
guy
getting
into
a
box
like
you
know,
entering
into
a
box
and
and
it's
basically,
if
you
look
at
the
traditional
way
of
doing
things,
you
have
the
operators,
which
are
the
knowledgeable
guys
that
understand
how
to
install
and
manage
your
java
servers.
A
Your
databases,
whatever
specific
proprietary
solution
that
you
have,
they
understand
how
they
configure
it
for
they
understand
how
to
manage
upgrades.
They
understand
how
to
recover
from
failures
and
such
things,
and
basically
you
really
need
that
knowledge
in
order
to
be
able
to
to
provide
a
99.999
person
of
service.
A
For
instance,
or
something
so
when
you
switch
to
the
containerized
space,
you
have
many
things
that
are
much
easier
to
do.
It's
easier
to
package,
your
your
content,
your
application,
it's
easier
to
run
it
kubernetes
can
do
basic
things
like
okay,
the
application
has
been
shut
down,
meaning
the
container
has
stopped.
A
So
kubernetes
does
not
understand
how
to
manage
a
say,
for
instance,
a
couch
based
database,
which
is
one
of
the
operator
operator-based
databases
that
we
provide
in
the
openshift
catalog,
thanks
to
the
the
work
that
we
have
done
with
our
partner.
Kubernetes
does
not
have
that
knowledge.
It
only
knows
that
there's
a
part,
the
plug
can
be
shut
down
or
started,
and
that's
it.
So
basically,
the
operator
in
terms
of
container
architecture
is
a
side
companion
to
your
solution.
A
A
Couchbase
have
implemented
the
way
installation
should
be
done.
The
way
scaling
should
be
done.
The
way
data
propagation
should
be
done
in
terms
of
automatically
distributing
the
data
across
the
different
nodes.
When
you
have,
for
example,
a
new
node
that
joins
or
something
like
that,
they
have
implemented
things
like
automate
or
automatic
recovery,
say,
for
instance,
you
have
a
cluster
that
is
comprised
of
three
nodes
in
terms
of
your
database,
and
one
of
the
nodes
has
an
issue,
so
the
the
operator
has
that
built-in
knowledge
to
say:
okay.
A
First,
I
need
to
start
a
new
instance,
and
then
I
need
to
do
those
specific
actions
which
are
probably
something
that
a
traditional
operator
would
have
known,
except
that
you
need
the
guide
to
do
it
now.
The
knowledge
is
embedded
within
a
side
container
that
we
call
the
operator
that
is
shipped
with
the
solution
and
does
all
of
that
magic.
In
the
background.
A
A
We
have
something
like
the
cube
api
operator,
something
that
manages
the
underlying
infrastructure
like
the
nodes,
how
they
they
get
configured,
how
they
get
updated
and
such
things.
So
I
think
we
have
over
37
operators
just
for
the
the
platform
content
itself
and
as
a
again,
the
reason
why
we
did.
That
is
it's
because
it
provides
you
so
much
with
so
much
built-in
automation
that
you
can
delegate
to
the
operator
and
then
have
everything
happen
magically
when
you
hit
that
update
button
here.
A
A
So
basically
they
said
we
don't
want
to
wait
for
you
to
release
a
specific
version
before
starting
to
do
our
sandbox
tests
and
see
if
we
can
upgrade
to
that
specific
version.
We
want
to
have
a
little
earlier
access
and
be
able
to
do
that
on
the
fly,
so
we
started
to
publish
first,
we
created
those
candidate
channels
for
the
updates
which
basically
provide
you
with
the.
A
I
think,
weekly
updates
for
openshift
in
terms
of
batches
and
such
things,
and
we
also
provide
nightly,
builds
for
the
installers
if
and
for
the
components
if
the
customers
want
to
go
and
download
them
and
install
them.
So
it's,
I
would
say
a
much
more
iterative
process
and-
and
you
have
access
to
those
features,
much
easier.
B
Well,
you
know
one
of
the
things
that's
interesting
to
me.
Jafar
is
you
know
if
you,
if
you
think
about
it,
you
know
historically,
there's
generally
the
if
it
if
it
works,
don't
mess
with
it.
You
know
if
it's
not
broke,
don't
fix
it,
and
you
know
and
there's
not
always
that
eagerness
to
move
on
to
the
latest
and
greatest
and
the
bleeding
edge.
You
know
and.
B
There's
the
sort
of
behavior
that
you're
describing
where
they're
saying
no,
we
want
to
see
it
before
it's
even
out
so
that
we
can
plan
for
it
so
that
we
can
prepare
for
it
so
that
when
it
does
come
out
we're
ready
to
leverage
it
and
and
hit
the
ground
running.
Does
that
seem
like
a
fair,
a
fair
assessment.
A
Yeah
so
there's,
I
would
say
two
sides
of
that
coin,
which
is
so
if
you
look
at
the
kubernetes
iterations
or
release
frequencies,
it's
a
new
release
every
three
months
and
nobody
in
the
traditional
I.t
enterprise
level
would
even
think
of
upgrading
their
core
systems
every
three
months.
So
that's
that's
a
very
challenging
way
because
they
have
validation
processes
and
such
things,
and
only
if
they
are
100
sure
that
the
upgrade
is
not
gonna
affect
their
their
running
workloads.
A
They
are,
they
are
going
to
think
about
the
possibility
to
do
it
and
not
necessarily
do
it.
So
that's
that's!
Basically
what
we
wanted
to
to
to
enable
is
to
to
have
that
shifting
in
the
mentality
that,
yes,
we
can
do
things
in
a
much
more
agile
way.
We
don't
have
to
wait
18
months
to
upgrade
to
the
the
last
version
and
wait
for
for
four
versions
of
patches
before
we
are
confident
in
something
that
has
been
released.
A
Of
course,
not
everyone
is
going
to
be
able
to
upgrade
their
platform
every
three
or
every
six
months,
so
we
still
have
a
lot
of
customers,
of
course,
that
have
they
are.
They
are
regulated
they
they
have,
I
would
say,
obligations
that
force
them
to
have
a
very
rigid
validation
process
and
they
cannot
upgrade
what
whenever
they
want.
A
So
again,
it
really
depends
on
the
types
of
workloads
and
the
types
of
regulations
that
control
your
platform,
but
what
we
did
is
actually
we
gave
them
the
ability
to
do
it,
which
it's
just
it's
a
it's
a
start
and
depending
on
on
how
flexible
they
are,
they
they
can
benefit
from
that.
From
that
feature,
I.
A
A
I
go
back
to
engineering
and
submit
some
issues
because
that's
also
surely
not
sure
why
we
do
that
and
and
basically
that
that
helps
us
make
fixes
before
we
go
into
the
ga.
So
if
we
have
customers
who
are
experimenting
with
the
with
the
candidate
releases
and
they
they
they
face
issues
and
they
submit
the
fixes,
that's
a
way
for
us
to
to
to
gain
some
time
and
be
able
to
fix
the
issues
before
they
they
land
into
the
the
the
the
ga
versions.
A
A
A
So,
if
you
think
about
the
way
things
were
done
before
you,
you'd
have
to
go
to
a
configuration
file,
you
would
have
to
edit
the
configuration
file
manually
and
then
you'd
have
to
restart
the
services
on
all
of
the
openshift
components,
to
make
sure
that
the
the
change
that
you
have
submitted
has
happened.
Well,
it's
basically
the
way
we
did
things
before
now
with
the
operators.
A
You
just
make
the
changes
in
here
the
operator
does
what
we
call
the
reconciliation,
it's
basically,
it's
monitoring
the
desired
state
versus
what
it
has
in
in
its
current
configuration
and
it's
gonna
say
okay,
so
you
want
me
to
add
a
new
identity,
identity,
provider.
Okay,
let's
do
that
and
it's
gonna
reconfigure,
the
authentication
component
automatically
in
the
background,
so
that's
basically
how
how
we
we
changed.
A
So
let's
continue
with
that
operator
story
and
and
administration
and
let's
have
a
look
at
what
we
have
in
the
in
this
current
cluster.
So
I
see
that
I
have
three
masters.
So
that's
a
requirement
because
we
we
want
to
have
three
eight
cds
and
so
that's
a
traditional
architecture
in
kubernetes
and
we
have
two
workers
which
are
so.
This
is
currently
deployed
on
aws
and
I
have
basically
two
nodes
and,
as
an
administrator,
I'm
often
responsible
for
managing
the
infrastructure.
A
A
So
we
have
what
we
call
this
notion
of
machine
sets
and
just
basically
it's
a
grouping
of
of
machines
or
nodes,
and
we
have
three
zones
in
here.
We
have
eu
west
a
west
b
and
west
c,
but
we
see
that
one
of
them
has
no
machines
yet
because
if
you
remember,
we
had
two
workers,
which
are
the
two
ones
we
can
see
here
say
now
that,
as
an
administrator,
I
want
to
provide
more
capacity
for
my
users.
A
A
If
you
wanted
to
configure
your
clusters
and
post
changes
and
that's
actually
what
we
do
when
we
are
using
acm,
for
instance,
you
can
have
a
set
of
centrally
defined
standard
configurations
like
this
is
the
ldap
configuration
that
I
want
to
push.
These
are
the
authorized
registries,
etc,
etc.
So
everything
you
want
to
configure
and
whenever
you
create
a
new
cluster,
you
can
have
acm
push
those
configurations
as
yaml
files
to
the
target
cluster
and
apply
them,
and
it's
going
to
be
automatically
picked
up
by
the
operators.
A
B
A
B
A
Yeah
sure
so
I
think
we're
gonna
have
to
maybe
wait
for
for
an
upcoming
show.
For
that
part,
and
again
it's
not
a
problem
because,
as
we
said,
we
want
to
kick
off
those
new
shows
with
new
ways
of
doing
you
know
coming
from
the
ground
up
and
going
step
by
step,
and
so,
as
you
can
see
here
here,
we
have
the
worker
which,
which
is
starting
to
to
appear,
which
means
that
the
automation
has
has
correctly
happened.
A
One
of
the
things
that
I
wanted
to
speak
about
is
the
operator
hub.
We
spoke
about
the
core
operators
that
manage
the
platform
itself,
but
as
an
administrator,
you
are
also
responsible
for
providing
content
to
your
end
users
and,
as
you
can
see
here,
we
have
over
500
items
that
appear
in
the
catalog,
and
this
is
comprised
of
some
solutions
that
are
provided
by
red
hat.
A
So
again,
we
have
our
solutions,
for
instance,
the
acm
or
acs,
which
are
the
multi-cluster
and
the
security
solutions
are
both
deployable
as
operators,
meaning
that
you
can
install
them
very
easily
on
the
platform.
But
we
have
also
some
components
that
are
part
of
openshift,
like
I
believe
we
have
the
login.
A
And
actually
let
me
do
that
because
I
wanted
to
show
you
how
to
do
that
for
a
developer,
oriented
solution.
So
now,
as
an
administrator,
I
want
to
provide
openshift
pipelines
as
a
service
to
my
users,
and
openshift
pipelines
is
basically
our
downstream
version
of
the
tekton
project
techjohn,
which
is
the
kubernetes
native
ci
cd,
or
we
have
git
ups
here,
which
is
our
distribution
for
argo
cd.
B
A
Correct
and
so
so
yeah
as
an
admin,
we
said
the
question
here
is:
how
do
I
configure
the
platform?
How
do
I
manage
the
content
and
how
do
I
add
or
remove
services
from
the
platform?
And
if
you
look
at
the
the
left
pane
here,
we
currently
don't
see
a
pipeline
section.
We
don't
have
that
capability
enabled
yet
on
the
platform
and
we
are
going
to
do
it
by
installing
the
the
operator.
Actually.
A
A
And
what
what
I
can
do
from
from
this
perspective
is
I
can
deploy
from
different
sources.
I
can
choose
to
deploy
from
git,
which
is
what
we're
going
to
do.
I
can
deploy
from
a
docker
file,
for
instance,
but
I
can
even
upload
a
jar
file
directly
into
my
ui
and
that's
a
nice
feature
that
we
can
show.
Maybe
in
one
of
the
upcoming
shows
it's
basically,
you
just
drag
and
drop
your
jar
file
on
the
openshift
console
and
it's
going
to
create
everything
that
you
need.
A
So
let's
go
ahead
and
choose
a
kit
triple
or
no
no,
let's
go
back
and
and
choose
the
samples,
and
just
for
for
the
record,
you
see
now
that
we
have
the
pipeline
section
that
has
been
added,
which
means
that
just
by
enabling
the
operator
on
the
platform
as
an
administrator,
I
now
as
a
developer,
see
that
this
service
is
available
to
me.
So
what
I'm
gonna
do
here
is
I'm
gonna
hit
that
basic
node.js.
A
So
what
happens
in
the
background
is
openshift
is
going
to
kick
off
the
build
process.
It's
going
to
fetch
the
the
code.
The
source
code
from
the
repository
is
going
to
trigger
the
build
for
for
me
and
as
soon
as
I
have
my
image
that
is
ready.
I
can
then
have
the
application
running
on
the
developer
perspective,
which
is
this
one
here
so
because
we
have
added
the
pipeline
feature
here.
A
A
We
already
have
the
the
node.js
starter
application
that
is
deployed
so
yeah
very
easy
for
me
as
a
developer
to
get
started
with
the
platform.
The
nice
thing
is
that
I
also
have
monitoring
capabilities
for
my
workloads.
I
can
see
metrics,
I
can
see
alerts
etc.
For
my
applications,
I
can
configure
the
ui
if
I
want
it
so,
for
instance,
I
want
to
add
something
that
is
called
deployments,
because
I
don't
see
it
in
the
ui
here.
A
A
Databases,
for
instance,
you
see
here
that
we
have
60
items
that
can
be
deployed.
Some
of
them
are
certified
operators.
Some
of
them
are
community
operators
and
often
times
you
have
the
two
versions
that
can
exist.
You
can
have
the
certified
version
by
the
third
party
provider
or
the
community
edition
of
it.
If
you
want
to
experiment
with
it
before
going
into
the
the
the
buying
process
in
the
commercial
option,.
B
A
Exactly
yeah
so
yeah,
that's,
I
would
say
a
very
convenient
way
of
configuring.
The
the
the
services
from
an
admin
standpoint.
The
goal
here
is
basically
provide
a
cloud-like
experience.
When
you
go
to
the
cloud
you
just
go
to
the
catalog,
you
order
your
components
and
they
are
there.
They
are
accessible.
A
A
B
Administrator
has
to
say:
well,
okay,
here
are
the
components
in
the
catalog
that
we
will
make
available
exactly,
but
they
have
the
ability
to
do
that
and
it's
like
you,
say
it's
sort
of
that
cloud-like
experience
of
okay.
I
have
enabled
that
particular
capability
and
now
all
of
the
developers
automatically
have
that
capability
and
they
can
choose
among
the
capabilities
that
that
have
been
approved
and-
and
there
is
some
degree
of
governance,
but
there's
also
the
benefit
of
having
this
huge
catalog
that
can
be
enabled
very,
very
easily.
A
Exactly
yeah,
you
saw
how
much
time
it
took
to
to
enable
the
pipeline
feature.
I
just
hit
the
install
operator,
then
less
than
a
minute.
Afterwards,
I
had
the
service
enabled
on
the
platform,
and
I
really
think
that
that's
what
what
we
provide
in
terms
of
of
user
experience
for
both
the
administrator
and
the
developer.
B
A
B
B
You
know
we're
here
regularly
on
wednesdays.
We
are
going
to
be
changing
our
our
schedule.
A
bit
we
have
gone.
We
have
previously
been
a
mostly
weekly,
occasionally
missing
weeks,
we're
now
going
to
be
going
more
officially
to
a
bi-weekly
schedule
and
we
hope
that
you'll
remain
interested.
All
of
you,
regular
watchers.
B
Our
next
show
will
be
on
february
2nd
and
we're
looking
forward
to
bringing
a
lot
more
information
about
about
openshift,
about
containers,
about
kubernetes
about
all
of
these
things
and
the
things
that
touch
them
this
year
in
2022.
So
please
do
like
subscribe
share.
Look
for
our
next
episode
and
again,
thank
you
very
much
jafar
for
for
a
really
great
walk
through
on
on
openshift.