►
Description
Hardware still matters in public cloud, and there are exciting new supported environments to discuss in Red Hat OpenShift 4.10. So let's take a deeper look at new architectures for public cloud and hybrid deployments that enable enterprise developers and IT organizations a flexible and powerful application platform. In this episode, Stu Miniman is joined by Red Hat Senior Director Mike Barrett to discuss the new version of OpenShift, new spotlight features, enhancements, and other improvements to the platform that developers and IT organizations can utilize.
Want to learn more?
https://cloud.redhat.com/learn/whats-new?sc_cid=7013a000002qG16AAE
Try Red Hat OpenShift: https://red.ht/3Haxapr
Follow us:
Stu Miniman https://twitter.com/stu
OpenShift https://twitter.com/openshift
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 on redhat.com https://red.ht/3JBaOia
OpenShift on GitHub https://github.com/openshift/
#RedHat #OpenShift #HybridCloud
A
B
Welcome
to
another
episode
of
in
the
clouds.
I
am
your
host
stu
miniman
and
still
coming
to
you
from
our
home
offices.
Things
are
starting
to
open
up
a
little
bit
here
in
the
united
states
as
well
around
the
globe.
Earlier
this
week
I
actually
went
to
the
boston,
the
the
global
ebc
for
red
hat,
which
was
the
first
time
I'd
been
there
this
year
and
got
to
see
actually
we're
working
on
studio
there.
So
we
have
a
temporary
setup
got
to
the
space
we're
going
to
build.
B
You
know
a
more
permanent
setup
and
I'm
looking
forward
to
the
day
where
I
will
be
able
to
sit
down
with
an
actual
guest
in
person
for
this
program,
but
until
then
happy
to
bring
the
guests
in
remote.
It
makes
it
easy
we
can
just
go
meeting
to
meeting
to
meeting
and
just
some
of
them
get
broadcast
out
to
the
world
so
really
happy
to
welcome
to
the
program
mike
barrett,
who
leads
the
product
management
on
the
openshift
team
which
which
I'm
a
part
of
mike
it
is
great
to
see
you.
B
All
right
awesome,
so
hey
just
for
our
audience,
you
know,
could
you
just
give
us
a
bit?
You
know
how
long
you
been
at
red
hat
and
you
know.
As
I
said,
you
know,
you
lead
the
product
management
team,
we're
going
to
put
a
link
up
up
in
the
chat
there.
Your
team
actually
does
like
a
90
minute
deep
dive.
So
if
people
want
to
know
all
the
wonderful
features
and
all
of
the
things
that
are
there,
they
can
go
watch
that
we
of
course,
are
gonna
up
level.
B
A
Yeah,
I
mean
a
little
bit
about
myself
and
how
I
got
here.
You
mentioned
boston.
We
have
a
boston
connection.
Stew.
I
lived
in
boston
for
14
years.
I
I
went.
I
was
in
chestnut
hill,
brighton,
chelmsford,
watertown
medford
lynn
shore,
so
I
bounced
around
quite
a
bit
but
yeah.
You
know
I
it's
interesting
enough.
I
got
into
computers
through
finance
and
marketing.
A
Then
then
I
yo,
I
I
get
into
sun
through
tech
support,
and
that
is
that
is
stayed
with
me
as
an
experience
and
it
still
stays
with
me
here
at
red
hat
how
you
have
to
be
very
connected
to
the
customer
and
during
that
time,
in
my
career
I
was
taking
probably
50
support
incidents
a
day
you
you
would
hang
up
the
phone,
you
would
pick
it
up.
You
would
work
25
whip.
You
know
you
have
that
case
load,
always
in
your
in
your
queue.
A
Turning,
but
that
really
brought
me
to
an
understanding
that
I
wanted
to
get
into
product
management.
So
I
it
was,
it
was.
How
did
this
happen?
How
did
this?
How
could
that
fault?
How
didn't
somebody
not
think
about
that
right,
and
so
I
gradually
went
from
support
to
sustaining
the
fine
fix
to
isv
partnerships,
to
field
enablement,
to
technical
marketing
and
then
into
product
management,
and
that
that
was
my
sort
of
trajectory
into
product
management.
B
Yeah,
it's
interesting
mike
you,
you
and
I
have
some
parallels
there.
So
you
know
I
actually
I
started
you
know
doing
some
coding
studied
engineering
did
had
a
few
field
roles
and
actually
took
a
product
management
role.
So
I,
when
I
joined
emc,
I
worked
there
for
10
years
from
2000
to
2010
and
it's
funny.
You
know
sun,
sun
hardware
and
all
that
stuff
there.
You
know
we
got
to
talk
about
that
and
everything,
but
as
like
the
junior
product
manager,
they
were
like.
B
Oh
hey,
give
stu
the
stuff
that
nobody
understands
and
we
can't
really
figure
it
out,
and
one
of
the
things
I
got
handed
is
I
was
the
product
manager
for
linux.
You
know
back,
I
mean
I
hate
to
admit
it's
20
years,
you
know
more
than
20
years
ago,
which
predates
when
rel
existed.
If
rel
had
existed,
the
job
would
have
been
easy,
but
back
then
it
was
oh,
my
gosh.
How
do
we
support
that?
B
We
only
had,
like
one
engineer,
doing
the
integration
testing
of
how
that
worked
and
when
red
hat
came
out
with
raz
and
then
rel
it
made
our
lives
a
lot
easier
because
at
emc
we
were
like
okay
enterprise
production
workloads.
You
know
that's
what
we're
all
brought
to
the
market,
and
so
it
it's
interesting
to
watch
that
journey,
something
I'd,
watch
red
hat
for
a
long
time
and,
of
course
joined
a
year
and
a
half
ago,
but
it
does
tee
up.
B
You
know
my
background's
infrastructure
and
one
of
the
questions
we've
had
for
the
last
decade.
You
know
or
more
is
with
cloud.
You
know,
does
hardware
matter
those
of
us
that
watch
the
cloud
there
was
a
you
know,
rather
small
acquisition
that
amazon
made
a
bunch
of
years
back
of
annapurna
labs.
It's
only
350
million
dollars.
I
mean
I
see
you
know,
350
million.
Is
that
big?
B
Well,
let's
compare
you
know
like
red
ibm
bought
us,
for
you
know
34
billion
dollars,
so
350
million
is
not
an
insignificant
acquisition,
but
it
has
had
a
large
impact
on
the
on
the
cloud
because
annapurna
labs
is
the
chipset.
That
is
now
the
graviton
servers.
What
I've
heard
in
the
market
is,
the
you
know,
might
be
the
largest
volume
arms
you
know
server
in
the
world,
and
that
brings
us
to
where
we
are
with
4.10.
So
so
mike,
you
know
arm
servers
in
the
cloud
with
amazon.
B
A
A
It
was
a.
It
was
a
new
way
to
vocalize.
How
do
I
get
cpu?
How
do
I
get
memory?
How
do
I
get
another
instance
of
myself?
How
do
I
make
sure
that
my
persistence
is
there
and
kubernetes
really
helped
do
that
for
us?
And
so
now
we
have
that
layer
and-
and
we
want
to
bring
back
hardware-
and
I
got
to
tell
you
when
we
first
started
this
project
of
bringing
hardware
attributes
into
kubernetes.
A
There
wasn't
necessarily
a
lot
of
partners
or
friends.
There
were.
There
were
some
like
intel
and
nvidia,
and
companies
like
that
that
were
like.
Yes,
let's
double
down
on
that,
let's
go
after
it,
but
a
lot
of
the
kubernetes
ecosystem
were
primarily
really
focused
on
clouds
and
virtual
machines
at
that
time.
A
So
we
coined
the
phrase
kubernetes
native
infrastructure,
where
what
if
we
could
take
a
step
back
and
we
could
take
some
investments
in
some
other
areas
of
the
company,
like
our
virtualization
stack,
our
rev,
our
kvm,
our
qemu
knowledge,
our
ability
with
openstack
and
everything
we
do
with
network
interfaces
and
ipv6
and
pneumo
awareness.
I
mean
you
want
to
go
in
the
back
room
and
sort
of
stretch
after
going
through
all
these,
these
birds
that
you
have
to
be
aware
of
when
you
start
touching
metal.
A
How
do
we
bring
that
into
kubernetes?
How
do
we
codify
them?
How
do
we
get
them
to
run
in
a
way
that
would
be
kubernetes
native
and
the
project
took
a
couple
years
to
really
get
off
the
ground
and
4.10
is
really
a
declaration.
The
4.6
was
the
first
step
where
we
had
really
features
that
customers
could
touch
and
feel
in
production,
and
it
took
a
couple
releases
to
round
off
some
edges
and
now
in
4.10
we're
really
hitting
the
home
run.
A
So
we
you
know
in
4.10
we
we
announced
the
support
for
arm,
and
you
know
I
got
to
tell
you
it
wasn't
an
easy
decision
as
easy,
as
you
would
think
like
you
would
think
everybody
loves
arm.
This
would
be
an
easy
decision
to
go,
invest
in
arm
and
do
it,
but
you
really
have
to
know
your
customer
base
and
you
have
to
know
how
they're
going
to
be
using
arm
and-
and
that
has
a
lot
to
do
with
there's
no
one
arm
like
when
you
get
into
the
world
of
arm.
A
There's
a
lot
of
different
server
specifications.
There's
a
lot
of
different
ways.
People
build
those
armed
servers
and
you
really
have
to
focus
on
very
precise
investments.
We
decided
to
go
out
with
aws
arm
first,
so
in
and
4.10
you
have
aws
support.
You
also
have
some
bare
metal
on
premise
for
a
sort
of
a
server
specification,
not
the
not
the
cool
stuff
in
your
office.
A
Let's
do
the
the
more
expensive
arm
servers
are
what
we're
supporting
right
now,
but
that
has
a
lot
to
do
with
our
edge
journey
and
where
we're
headed
there
azure
will
most
likely
be
next
on
the
roadmap
that
we'll
declare
support
for
and
right
now,
with
the
arm
support
it's
a
homogeneous
cluster.
So
everything
in
that
cluster
in
that
kubernetes
cluster
is
going
to
be
arm,
and
our
net
in
our
releases
at
the
end
of
this
year
will
allow
you
to
mix
those
in
a
heterogeneous
way
with
other
x86
workloads.
A
B
Yeah,
no,
no
mike,
I'm
glad
that's
what
I
wanted
to
get
into
with
you
is,
you
know
arm's
been
around
for
a
number
of
years.
You
know
everybody
from
you
know:
hey,
you
know,
apple's
got
their
own.
Chipset
people
are
getting
their
hands
on.
You
know
laptops.
You
know
running
the
apple
chips
to
you
know:
oh
yeah.
No
I've
got
a
raspberry
pi
sitting
over
there.
Can
I
just
run
it
on
that?
B
Well,
no,
it's
you
there's,
there's
a
amount
of
resources
we
need
underneath
there
was
all
the
work
that
our
linux
team
needed
to
do
so
you
know
rel
support
for
arms,
so
yeah
you
know,
I
guess.
Could
you
mike
just
tell
us?
You
know
that
journey
for
arm.
You
said
we
started
touching
it
in
4.6.
Here
we
are
with
4.10.
B
A
A
A
A
We
support
precise
time
protocol,
which
is
time
stamps
on
on
hardware
and
clock
time
in
the
apis
that
you're
calling
out
the
kernel
device
manager
being
able
to
compile
drivers
for
intel
cards
as
you're
deploying
the
workload
like
mind.
Blown
like
you
just
like
these
are
all
the
things
that
build
on
top
of
each
other.
I
mean
sri
ov
through
put
being
able
to
talk
to
a
service
processor
on
a
server
like
there's,
there's
those
nuts
and
bolts
features
and
then
there's
even
stu.
There's
even
philosophical
differences.
A
B
A
Yeah,
so
you
you
have
your
container
on
one
spectrum
and
then
you
have
your
virtual
machine
on
the
other
spectrum.
We
cater
to
both
of
those
with
openshift
virtualization,
which
is
the
kubert
project,
and
then
you
have
the
obviously
rail
containers
in
between
you
have
sandbox
containers
right,
and
these
are
what
a
lot
of
people
in
the
industry
will
call
micro,
vms,
rel
sort
of
invests
in
qemu,
and
we
have
a
more
sort
of
slimmed
down.
A
B
Yeah
it
it's
always
interesting,
mikey
you
and
I
both
get
to
talk
to
a
number
of
customers
and
we've
reached
a
maturity
level
that
you
know
early
days
of
kubernetes.
It
was
yeah,
I'm
building
new
applications.
I'm
modernizing
everything
I
want
to
you
know
use
all
these
wonderful
new
workloads.
You
know
we
announced
this
at
the
nvidia
to
highlight
some
of
the
ai
and
ml
workloads.
We're
doing
well,
there's
some
workloads
that
you
know
it's
going
to
take
me
longer
to
modernize
them.
So
we
need
to
give
those
pathways
you
know.
B
Can
I
manage
them
in
a
new
cloud-native
way
and
that's
where
things
like
the
the
openshift
virtualization
built
off
of
qvert
can
help
with
and,
of
course,
security,
huge
concern.
Everybody
wants
to
make
sure
there's
there.
I
remember
when
containers
first
came
out,
it
was
like.
Oh,
my
god,
is
there
any
security
here
you
know.
Let's
just
you
know,
line
up
every
container
is
you
know
tied
to
a
virtual
machine?
Well,
it's
matured,
a
lot,
there's
so
many
pieces
throughout
the
entire
stack
that
we
do
so
you
know.
B
A
Yeah,
I
think
I
think
I
mean
you
hit
it
perfectly-
the
with
openshift
virtualization,
which
is
the
cubeverd
open
source
project.
We
have
a
lot
of
people
that
are
sort
of
lifting
shifting
virtual
machines.
These
are
these
are
people
who
had
virtual
machines
that
hold
them
in
production
and
they
want
a
new
way
to
launch
them.
They
want
a
new
way
to
to
consolidate
them
back
to
that
api.
We
were
talking
about
before,
where
I
have
a
consistent
way
to
ask
for
cpu
memory,
disk
and
io
and
routes
and
ip
addresses.
A
That
was
the
point.
So
when
we,
when
we
designed
openshift
virtualization,
we
could
have
totally
taken
the
path
where
we
take
openstack
and
rev,
and
we
sort
of
put
them
side
by
side
next
to
each
other,
and
we
put
a
user
experience
on
top
of
it.
And
you
know
one
of
our
competitors
went
down
that
path
with
their
virtualization
technology.
A
We
felt
that
we
needed
to
do
some
heavy
lifting
right
that,
if
you,
if
you
truly
believe
that
you're
into
containers
that
you're
going
to
have
more
containers
and
virtual
machines
over
the
next
eight
years,
then
you
probably
want
to
bring
the
virtual
machines
into
the
same
sort
of
dynamic
the
same
distributed
system
right.
It
should
be
able
to
scale
up
and
scale
down
in
the
same
way
the
same
yaml
template
it
should
be
able
to
ask
for
cpus
and
memory.
A
In
the
same
way,
it
should
be
able
to
get
a
an
ip
address,
a
a
route,
a
url.
These
all
need
to
be
the
same
in
the
system
for
you
to
be
successful,
mixing
these
old
virtual
machines
in
with
these
new
containerized
workloads
and
that's
what
the
design
premise
was
around
open
source
virtualization
in
this
release,
4.10,
it
actually
picks
up
support
for
service
mesh,
which
is
mind-blowing
right.
A
layered
product
is
now
sitting
on
top
and
bringing
these
these
products
together.
A
B
Yeah,
absolutely
it's
it's
something
that
you
know.
I
remember
first
hearing
hearing
about
it
mike
the
you
know,
architecturally.
You
say
you
know
what
is
my
center
of
gravity
right?
Do
I
want
to
move
things
forward?
Be
more
modern.
You
know,
containers
and
kubernetes.
Is
that
the
the
experience
that
I
want
to
build
around
or
do
I
want
to
try
to
backport
things
and
be,
as
you
said,
more
of
a
side
car
with
you
know
older
environments.
So
it's
a
little
bit
of
work
for
customers
to
to
to
move
to
a
new
learning
environment.
B
But
overall
that's
going
to
be
helpful
for
the
business.
Everybody
needs
to
be
able
to
move
faster
kind
of
leads
us
to
our
next
topic
of
conversation.
You
know
we
mentioned
the
aimo
workloads.
That's
a
big
focus.
We've
had
for
a
number
of
years,
the
the
automation
that
that's
really
needed
for
the
scale,
and
you
know
changing
of
those
environments.
It
really
has
been
a
nice
match,
for
you
know
what
we've
seen
in
kubernetes
in
openshift.
A
You
know
this
era,
where
only
data
scientists
and
only
the
most
privileged
in
the
company
have
access
to
the
best
hardware
is
at
the
sort
of
the
tear
point
of
going
away,
and
so
now
we
need
a
way
to
to
have
pipelines
for
the
use
of
these
gpus
with
pytorch,
with
cuda
containers,
with
a
lot
of
the
the
nvidia
stack
and
nvidia
at
their
conference
released
this
this
wonderful
suite
of
of
tools.
That
is,
if
you
just
add
the
platform,
the
openshift
and
you
load
these
tools.
A
On
top
of
you
now
have
an
out
of
the
box
experience
that
allows
you
to
really
add
security.
Allow
what
an
enterprise
would
need,
in
terms
of
their
compliance,
add
pipelines
to
bring
people
in
and
start
mixing
those
those
coding
patterns
with
the
results
of
a
lot
of
the
intelligent
applications
that
only.
B
A
Scientists
used
to
have
access
to
before
we
have
a
lot
of
customers
sort
of
building
that
themselves
and
that's
a
successful
project
as
well.
We
we
helped
there
with
open
data
hub,
which
is
a
reference
architecture
that
allows
you
to
plug
in
a
lot
of
other
people's
other
vendors.
Our
isp
partners
solutions
into
that,
but
this
nvidia
solution
that
just
launched
this
week
is
is
incredible
and
we're
we're
proud
to
have
them
qualified
on
openshift
and
opening
on
on
openshift.
A
We
first
created
node
feature
discovery
and
special
resource
operators
and
and
device
managers,
and
a
lot
of
automation
in
those
areas
and
video
was
able
to
bring
those
technologies
together
in
the
nvidia
operator
and
they
supported
on
everybody's
kubernetes.
But
we
had
a
a
really
great
partnership,
bringing
that
into
the
market.
B
Yeah
so
mike
we
got,
we
got
an
interesting
question.
I
think
that
one
that
tees
up
you
know
that
that
customer
journey.
So
when
I
think
back
to
the
you
know
the
early
days
of
paz,
you
know
before
containers
and
kubernetes
were
a
thing.
It
was
really
kind
of
narrow
as
to
what
applications
we
can
put
on
it.
B
It
was
you
know,
okay,
I
want
you,
know
micro
service,
12-factor
applications,
you
know,
that's
it
and
I'm
like
well,
I'm
going
to
have
some
of
those,
but
the
the
question
says
you
know
many
customers
aren't
even
ready
to
do,
lift
and
shift.
They
want
to
move
slowly.
You
know,
to
paraphrase
what
often
says
you
know,
how
do
we
meet
customers
where
they
are
and
move
at
the
pace
that
they
are
are
ready
to?
So
how
does
openshift
help
there.
A
Yeah,
I
would
say
openshift
you
know
going
as
far
back
as
even
pre
kubernetes
just
coming
into
kubernetes.
We
were
one
of
the
only
vendors
that
felt
you
you,
as
a
user,
had
the
right
to
say.
I
wanted
to
go
at
my
own
pace
that
that
I
we
we
weren't
necessarily
ever
going
to
force
you
into
a
12-factor
sort
of
position
and
what
that
means
is
we
were.
We
were
very
concerned
about
persistent
storage.
We
were
very
concerned
about
how
you
get
your
ip
addresses.
A
You
know
I
want
to
say
it
was
education
or
sort
of
awareness
that
drove
us
there,
but
we
were
in
our
you
know,
an
operating
system
company
at
our
heart
right
and
we
are
trying
to
bring
workloads
into
a
platform,
and
so
we're
we're
going
to
go
out
of
our
way
to
make
sure
that
you
can
run
complex
applications
inside
our
ecosystem,
and
so
we
were
one
of
the
first
to
really
invest
aggressively
on
stateful
sets
in
kubernetes.
We
were
one
of
the
founding
leaders
in
custom
resource
definitions.
A
B
B
One
of
the
toughest
conversations
is:
you
know,
customers
that
you
know
did
a
lot
of
work
on
on
openshift
3.,
openshift
4
is
almost
a
completely
different
product,
there's
just
so
many
things
that
matured
in
the
kubernetes
space
and
that
you
know
your
team
learned
a
lot
and,
as
you
said,
made
some
some
important
decisions
as
to
how
to
build
things.
So
this
space
moves
so
fast.
As
we
know,
we're
we've
now
gone
from
four
releases
to
only
three
releases
a
year,
but
there's
so
many
pieces
in
it.
So
I
did
get.
B
We
got
one
question.
I
want
to
open
it
up
to
you
as
to
some
of
the
other
cool
things
that
you're
excited
about
in
this
release.
The
the
the
audience
question
was
serverless,
which
is
an
area.
I've
spent
a
lot
of
time
watching
and
was
really
excited
when
the
eventing
capability
is
now
in.
You
know,
k
native,
which
is
the
container
based
serverless
and
and
that's
there.
A
Yeah
well
serverless,
and
this
is
gonna-
go
down
at
kubecon
as
well
in
in
amia
in
spain.
I
believe,
right
in
next
month
or
something
yeah
yeah
they're
really
gonna
celebrate
the
fact
that
k
native
goes
to
1.0
right,
and
so
this
release
and
4.10
it's
a
different
release
number
for
serverless,
but
we
we
graduate
and
we
move
it
to
1.0.
A
A
Some
of
the
there's
some
ux
changes
in
our
user
interface
that
really
help
a
developer
experience
around
serverless
somebody
interested
in
an
api
driven
topology
is
is,
is
important
and
and
definitely
there
but
yeah
a
lot
of
stuff
in
4.10
that
we're
proud
of
4.10.
You
know
10
releases
of
4.x
and
there's
that
movie
grossed
by
gross
point
blank.
Where
he's
going
10
years,
10
years,
man
and
it's
hard
to
believe
that
we
did
10
releases
in
like
four
years.
A
I
think,
since
we
this
will
be
your
number
four,
since
we
released
four
and
it
early
on.
In
any
product,
you're
going
to
be
building
windows
and
doors
and
floors
and
foundations,
big
items
and
then,
as
you
graduate
into
these
higher
numbers
of
the
releases,
you
get
to
go
back
and
put
in
the
trimmings
and
make
things
extremely
nice,
and
that's
where
we
are
right.
A
We
were
able
to
fix,
like
45
rfes
in
this
particular
release,
which
are
requests
for
enhancements
coming
from
actual
end
customers,
which
is
a
lot
to
get
into
a
minor
release
and
so
definitely
proud
of
the
team.
There's
there's
a
lot
of
you
know.
We
talked
about
the
bare
metal,
but
there's
a
lot
of
stuff
happening
in
infrastructure.
Support
right
and
you
know
don't
get
me
wrong.
A
Openshift
is
kubernetes.
You
can
run
kubernetes
anywhere.
The
difference
is
what
automations
you
want
with
that
installation
that
you're
experiencing
and
when
we
looked
at
what
we
wanted
to
do
with
4.x.
We
wanted
to
realize
what
infrastructure
you
were
installing
in
and
add
automations
around
that
infrastructure,
and
so
it's
taken
us
some
time
to
go
through
every
infrastructure
on
planet
earth
and
put
a
lot
of
those
automations
in
and
a
lot
of
those
kubernetes
on
by
default.
A
Right
and
in
this
release
we
do
it
with
alibaba
and
we
do
it
with
ibm
public
cloud
and
we
do
it
with
azure
stack
hub
on
premises.
The
azure
stack
hub
kind
of
exploded
in
requests
around
the
time
of
the
the
big
government
bid.
I
think
microsoft
got
a
lot
of
the
attention
there
because
they
had
an
on-premises
solution
and
the
a
lot
of
government
agencies
wanted
to
support
for
azure
stat
cup.
A
B
B
Yeah
and
there,
but
the
other
one
azure
stack
hubs,
so
you
know
we've
had
openshift
on
azure
for
a
long
time
and
the
way
microsoft
positions
it
is
azure
stack
hub
is
we're
extending
the
public
cloud
to
your
data
center.
I'm
curious,
you
know,
what's
the
nuance
there
of
okay,
we
could
support
openshift
in
azure.
Well,
this
is
just
you
know,
a
rack
of
certified
same
software,
so
you
know
it's
great
that
we
can
extend
and
cover
the
hybrid
solution
for
microsoft.
B
B
B
Oh
great
openshift
lives
all
those
places,
I'm
not
going
to
have
to
think
about
that.
You
know
from
a
development
from
an
operation
standpoint
we
we
take
care
of
that
for
them,
and
that
proof
point
it's
it's
good.
I
know
you
know
we.
We
work
with
a
lot
of
the
cloud
providers,
as
you
said,
and
as
they
go
more
hybrid,
we
should
be
able
to
live
in
those
environments
too
right.
A
Definitely
not
and
there's
gonna
be
another
infrastructure
that
pops
up
that
that
people
want
that's
completely
different,
we'll
have
to
go
work
on
it.
You
know
another
area
of
the
release
that
we're
really
proud
of,
and
it
is
a
combination
of
our
advanced
cluster
management
and
our
open
data
foundations
projects
coming
together.
What
could
they
do
together
to
solve
a
big
customer
problem
and
it's
around
disaster
recovery?
A
So
when
you
look
at
disaster
recovery-
and
you
look
at
so
these
projects
that
we
were
invested
in,
we
found
a
sort
of
a
pattern
and
a
picture
that
we
could
bring
together.
So
when
you
look
at
the
projects,
we
were
sort
of
investing
in
moving
forward
last
year
and
the
year
before,
we
have
something
called
odap
oadp
and
it's
a
open
shift
api
for
data
protection,
and
this
is
being
used
as
an
api
on
openshift
by
a
lot
of
backup
vendors
in
in
our
industry.
A
Kubernetes
doesn't
really
have
a
good
definition
of
application
and
it's
got
all
these
bits
and
pieces
and
labels
of
different
secrets
and
routes,
and
all
these
other
components
it's
got
a
project
called
valero
that
helps
you
scoop
those
up
to
find
them
and
scoop
them
up,
but
also
you
want
to
be
able
to
call
a
snapshop
snapshot
interface
for
the
csi
plugin
in
kubernetes.
At
the
same
time,
so
you
bring
up
the
persistence
and
all
the
guts
of
the
application,
and
through
this
single
api
call
you
can
like
snapshot
it.
A
A
B
Yeah,
I
guess
I
said
on
sort
of
a
related
topic
mike
you
know
we
talked
about
hybrid
and
edge,
but
one
of
the
things
that
we
have
a
lot
of
experience
is
not
just
the
customers
in
their
environment,
but
for
many
reasons
often
customers
will
need
to
run
in
in
a
disconnected
mode,
so
very
different
from
the
cloud
providers.
I've
always
got
that
heartbeat,
I'm
going
back
to
so
what?
What?
What's
the
latest
when
it
comes
to
you
know,
disconnected
or
any
you
know,
pauses
in
connectivity,
yeah
disconnected.
A
Has
been
a
hard
egg
to
crack
when
you
look
at
the
container
technologies,
they
all
have
a
prereq
that
you
have
a
container
registry.
So
if
you're
gonna
have
a
container,
you
need
a
registry
to
stick
it
in.
But
if
I'm
the
one
giving
you
the
registry,
how
now?
What
are
you
doing
like?
Are
you
standing
up
your
own
on
the
side
and
then
you're
sucking
stuff
down
in
the
something
that
you're
maintaining
and
then
you're
deploying
the
real
registry
that
you
want
it?
A
A
You
pull
those
things
down
when
and
when
I
say
pull
down,
it
seems
like
an
easy
task,
but
if
you
just
blindly
pull
down
you're
pulling
down
like
400
gigs
of
software
in
the
openshift
ecosystem
of
all
those
cncf
projects
that
we're
invested
in,
so
we
needed
to
give
you
filtering
commands.
So
that
says
hey!
A
I
only
want
the
latest
of
those
operators,
or
I
want
only
this
channel
of
openshift,
so
you
can
really
filter
in
on
what
exactly
you
wanted
to
pull
down
and
then
how
do
I
stay
up
to
date
for
the
the
the
biggest
problem
with
the
disconnected
customer?
Isn't
necessarily
the
first
install
it's?
How
do
I
maintain
that
investment
that
I
just
installed,
that
does
that
is
disconnected?
A
Will
something
in
the
product
tell
me
that
I'm
out
of
date
that
a
new
version
is
available,
so
we
we
had
through
our
core
wes
acquisition
for
the
connected
customers.
For
years
previous,
we
were
providing
this
update
service
that
allows
you
to
connect
up
to
red
hat
and
in
your
console
we
show
you
that
there's
a
new
version
available
and
that
you
should
upgrade,
and
then
you
click
an
upgrade
button.
A
B
Yeah
awesome
well
and
I'm
glad
mike
thank
you
for
helping
clarify
at
least
your
pronunciation
of
q-u-a-y.
I've
heard
it
pronounced
key.
I've
heard
it
pronounced
quay,
so
you
know
always
those
debates
as
to
some
of
those
things.
So
we
we've
been
putting
in
in
the
chat
in
the
comments.
There's
links
to
hear
more
there's
so
many
pieces
apologize.
If
we
didn't
get
some
of
the
questions
you
have
but
mike
I
I
got
one
last
question
for
you.
You
know
when
we
look
at
the
last
two
years.
B
You've
got
a
large
organization,
so
the
good
news
is,
you
know,
red
hat.
You
know,
pre-pandemic
was
already
you
know.
You've
got
a
global
team,
you
know
used
to
doing
things
asynchronously
between
product
managers
and
engineers,
I'm
sure
you've
got
way
more
slack
channels
and
workspaces
than
I
would
want
to
know
about.
But
you
know,
there's
changes.
You've
had
people
that
have
never
met
any
of
their
peers.
You
know
how?
How
do
you
as
a
team?
A
Yeah,
so
t-shirts
are
important
in
this
industry.
Stu
like
when
you
celebrate
in
an
I.t
industry,
you
have
to
get
a
t-shirt,
so
we
we
do
a
lot
of
swag
in
those
areas.
You
know
you
have
to
use
the
tools
that
you're
being
provided.
So,
if
you're,
if
you're
in
gene
mates
as
a
team,
if
you're
in
slack
as
a
team,
you
need
to
have
time
for
happy
hour
over
g
meets
right,
so
virtual,
happy
hours
our
we.
A
A
I
believe,
but
we're
also
very
excited
that
things
seem
to
be
returning.
We're
excited
that
sort
of
travel
to
shows
and
and
whatnot
are
starting
to
to
turn
on,
and
I
think
we're
we're
willing
to
experience
the
world
again.
I
think
what
what
we
need
to
be
conscious
of
and
and
probably
a
lot
of
people
are
going
through.
This
is
making
sure
that
we're
visiting
customers
before
we're
visiting
ourselves.
B
Yeah,
no
mike
absolutely.
I
I
mentioned
at
the
top
of
the
program
that
I
got
to
go
to
the
boston
office.
That
is
our
global
briefing
center.
I'm
excited
I've
got
some.
You
know
upcoming
meetings
with
customers
and
yeah
to
your
point
working
in
tech.
It's
not
just
a
job,
it's
also
a
wardrobe.
I
I'm
sporting,
the
openshift
commons.
You
know
north
face
from
some
of
the
commons
events,
quick
shout
out
to
those
people
attending
kubecon
eu,
as
mike
mentioned
in
may,
there
will
be
a
hybrid
openshift
commons
event.
B
You
can
definitely
you
know,
look
online
as
to
how
to
join
that
so
mike
4.10,
so
many
things
in
there
super
exciting
again
in
the
comments
we
posted.
If
people
want
to
dive
in
deep
there's,
you
know
the
blog,
the
press
release
the
90
minute.
You
know
session
that
your
team
did.
It
is
great
thank
you
for
joining
us
sharing
with
the
audience
and
look
forward
to
talking
to
you
more
in
the
future
yeah
thanks
for
having
me
stu.
It
was
a
great
time
all
right
and
really
appreciate.
B
You
know
this
topic.
You
know
lots
of
interest
from
the
community.
You
know
do
reach
out
mike
and
I
are
really
easy
to
get
in
touch
with
online
happy
to
answer
your
questions
hit
us
up
through
the
social
channels
through
the
websites,
and
you
can
get
this
and
we've
got
lots
of
great
programming
coming
up
every
two
weeks.
We
try
to
bring
this
program
and
thank
you
so
much
for
joining
us
on
your
journey
in
the
clouds.