►
From YouTube: In the Clouds (E34) | Let’s Talk OpenShift 4.12 Update
Description
Across industries and business sectors, senior leadership has to execute at an ever-increasing pace, and today's technology decisions must balance short-term risk with long-term gains. Join host Stu Miniman as he leads insightful and candid discussions with a broad spectrum of experts, executives, and decision-makers on diverse and hot technology topics.
In this episode of In the Clouds, Stu Miniman gets chatting with Ju Lim, a Senior Product Manager for OpenShift, about the new OpenShift 4.12 product release. This episode comes after the ‘What’s New OpenShift 4.12’ episode released on Jan 11th 2023, and will expand on the features further, taking more time to answer questions and angles left out from there. This frank discussion will give others an opportunity to ask questions live. As Ju has previously worked for Amazon AWS as well, this will give us a chance to speak about our competitive positioning at Red Hat.
Don't miss this episode.
Want to learn more?
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
A
Openshift
really
is
you
know
the
solution
for
hybrid
Cloud
and,
to
be
honest,
one
of
the
big
reasons
why
IBM
made
the
acquisition
of
red
hat
and
last
night
actually
IBM
had
its
fourth
quarter,
2022
earnings
report
and
there
was
an
exciting
announcement,
the
CFO
of
IBM,
Jim,
Cavanaugh,
actually
and
I'll
redo,
the
quote:
openshift
our
industry-leading
hybrid
Cloud
platform
now
has
a
billion
dollars
in
annual
recurring
Revenue.
So
I
can
tell
you
from
the
red
hat
side.
A
A
It
saw
that
we
could
reach
this
Milestone,
but
you
know
want
to
say
huge
Kudos,
not
just
you
know
to
the
team
as
our
our
head
of
products
as
Chef
badani
put
out
on
social
media.
He
said
you
know:
hey
congratulations
to
all
the
current
team
members,
the
previous
team
members
and,
of
course,
a
special
shout
out
not
only
to
the
customers
but
the
community,
because
everything
that
we
do
at
red
hat
and
at
openshift
is
open
source
space.
So
the
community
is
so
important
to
build
what
we've
done.
A
The
momentum
that
has
gotten
us
to
where
we
are
and
I
think
we
have
a
really
exciting
future
going
forward.
Since
we
are
talking
about
openshifted,
it
was
awesome
timing
happy
to
welcome
in
our
guest
for
the
show
today.
Julim
she
is
a
senior
manager
from
the
product
management
team.
Part
part
of
the
openshift
group,
Jew
and
I
have
actually
worked
together
a
couple
of
times.
So
thank
you
so
much
for
joining
me.
B
Oh,
that's
a
great
question
so
back
when
I
worked
with
Stu,
this
was
probably
about
a
decade
ago
we
met
up
at
EMC
and
I
was
lured
to
join
Red
Hat
by
somebody.
I'd
worked
with
at
EMC
who
actually
joined
red
hat,
and
it
was
sort
of
the
promise
to
work
on
open
source
and
change
the
world
and
fast
forward
to
today,
I've
been
with
red
hat
now
about
seven
years
and
it's
been
very
exciting.
B
The
company
has
evolved
from
Rel,
which
was
our
bedrock
and
Still
Remains
and
I
got
to
be
lucky
enough
to
be
part
of
that
containers
and
kubernetes
kubernetes
journey
that's
evolved
into
what's
open
shift
today,
and
so
it's
been
a
wild
ride
very
exciting.
A
lot
of
changes,
the
company's
grown
from
less
than
10
000
people
when
I
started
to
well
over
20
000
some
odd
people.
B
During
that
time,
I
did
leave
a
red
hat
for
a
time
for
about
two
years
where
I
joined
AWS,
and
that
was
also
very
fun
and
exciting
ride,
because
I
got
to
see
things
from
an
hyper
hyperscaler
perspective.
Part
of
the
reason
I
left
was
to
gain
an
appreciation
for
how
hyperscalers
are
so
successful
in
running
public
clouds
and
get
sort
of
a
first-hand
experience
with
operating
first
in
the
cloud
in
what
that
entails
in
terms
of
what
Amazon
calls
their
mechanisms.
B
A
Yeah,
so
some
some
great
background
there
Drew
I,
appreciate
it.
Yeah,
it's
interesting,
I
I'd
worked,
you
know
a
bit
on
open
source
when
I
was
at
EMC,
always
really
enjoyed
my
interactions
with
red
hat
back
from
the
earliest
days,
when
relfirst
came
out
and
just
great
culture,
great
people
and,
of
course
the
the
open
source
mission
is
what
brought
a
lot
of
us.
You
know
on
board,
so
you
know,
we've
got,
we've
got
quite
a
few
sprinkled
in
from
you
know
the
EMC
and
vmware's
of
the
world.
A
Here
at
Red
Hat,
you
were
the
lead
one
of
the
leads
for
openshift
4.12
we've
had
on
this
show
last
year.
Basically,
every
time
we've
done
a
release,
I
I,
bring
on
the
product
manager
who
leads
it
as
as
way
of
a
preamble.
You
know
we
know
it
takes
a
lot
of
people
to
put
together
all
of
these
releases.
There
are
so
many
things
that
go
into
openshift
I
I've
talked
about
it.
We'll
put
put
the
note
out
there.
A
We
do
a
whole
live
stream
where
the
product
management
team
goes
through.
You
know
a
majority
of
all
the
things
in
there
and
it's
it's
a
really
deep
dive,
so
many
different
components
that
make
up
openshift.
You
know
way
more
than
we
can
cover
here,
but
Drew.
Maybe
if
we
start,
you
know
a
lot
of
the
things
that
get
the
the
high
the
the
top
mention
or
some
of
the
customer
enhancements
that
go
into
each
release.
A
B
Yeah
so
I
think
412
as
you've
mentioned
a
lot
of
different
people.
A
lot
of
different
teams
have
worked
on
it
and
I'm
pleased
to
say
we
brought
about
I
want
to
say
somewhere
in
the
neighborhood
of
almost
50
enhancements
requests
delivered.
But
some
of
the
highlights
in
there
that
I
should
probably
mention
include
things
like
the
extending
the
openshift
life
cycle.
For
the
extended
update
releases,
in
particular,
our
extended
update
releases
tend
to
be
even
numbered,
so
things
like
410,
412
and
so
on,
but
specific
to
extending
the
release.
B
What
up
until
recently,
each
open
shift
release
was
supported
for
18
months,
starting
from
the
412
release
onwards.
We're
changing
it
so
that
starting
with
openshift
412,
we
are
now
extending
the
total
life
cycle
to
24
months,
and
this
is
really
for
the
x86
architectures.
If
you
have
other
architectures
like
power
or
Z
systems,
or
those
still
remain
in
18
months.
A
Moving
forward,
I
I,
wonder
I'd
love
to
get
your
opinion
on
this,
because
it's
a
dynamic
we've
seen
for
a
long
time.
If
you
ask
many
Enterprise
companies,
you
know
how
often
they
want
to
update
it's
well.
If
I've
got
it
testing
and
it's
working
I
want
to
leave
it
that
way
and
the
original
promise
of
the
cloud
would
be
hey.
A
You
know
I
used
to
joke.
It's
like
you
know,
you
don't
think
about
what
version
of
something
you're
running
in
Azure
you're
just
running
on
Azure
and
Microsoft
takes
care
of
that
now
the
devil
is
in
the
details,
because
you
know
in
kubernetes
we
see
you
know
the
cloud
providers
are
supporting
more
than
one
version
out
there,
and
we
know
customers
need
time
to
be
able
to
upgrade
so
we're
hoping
there's
a
little
bit
of
convergence.
You
understand,
there's
a
lot
of
it
depends
and
if
I've
got
certain
requirements,
I
need
to
keep
it.
A
B
That's
a
really
really
good
question:
it
is
a
careful
balance.
It
does
require
customers
and
partners
to
really
plan
how
they
go
about
doing
the
upgrades
we've
made
tremendous
strides
in
terms
of
offering
things
like
eus
to
eus
release
updates
so
that
way,
you're
able
to
skip
a
release
for
your
worker
nodes.
B
Upgrades
I
mean,
but
the
idea
behind
all
of
this
is
we
know
that
upgrades
are.
You
know
nobody
wants
to
change.
Nobody
wants
to
make
those
updates,
but
it
is
a
necessary
evil,
especially
if
you're
looking
for
newer
features
new
functionality,
that's
one
or
also
you're,
dealing
with
cves
or
you
know
it
needs
to
get
patched.
Let's
face
it,
we
don't
like
it,
but
we
have
to
do
it.
B
That
being
said,
is
we've
made
significant
Investments
to
ensure
that
upgrades
are
minimally
intrusive
in
that
sense,
by
reducing
the
duration
and
it's
safer
and
quicker
with
what
we've
done.
I
think
one
of
the
things
that
has
been
a
good
Comfort
to
me
is
that
I
recall
speaking
with
a
customer
last
year,
and
they
also
said
your
upgrades
are
getting
better,
especially
with
all
these
new
features
you've
introduced
so
much
so
that
we
now
actually
do
our
upgrades
during
the
work
week.
B
A
That's
awesome,
yeah
so
to
I
know.
You
know
you
personally,
your
team
really
close
to
the
installers
and
I'm
sure
things
like
the
upgrades.
You
know
that
flexibility
that
that
we've
been
building
out
we're
trying
to
make
it
simpler.
You
know
people
often
you
know
we
know
you
know.
Kubernetes
is
not
easy
and
there's
a
lot
of
things
that
go
into
openshift.
B
Yeah,
so
on
the
installation
front,
there's
a
lot
of
new
changes
that
we've
introduced
and
what
I
mean
by
that
is
We've
introduced
a
more
flexibility
with
our
installer
and
what
that
means
is.
We
now
have
the
capability
to
actually
disable
some
of
the
operators
from
being
installed,
and
you
can
actually
learn
more
about
it.
B
You
need
smaller
footprints
on
what
ends
up
happening.
Is
you
need
less
resources
for
that,
and
as
part
of
that,
we
need
to
also
reduce
the
consumption
being
used
by
some
of
the
openshift
components.
So
we've
made
a
lot
of
Investments
there
and
are
continually
improving
and
optimizing
openshift,
but
as
part
of
it,
we're
also
like
I,
said
letting
you
exclude
some
of
the
components
at
installation
time
and
in
the
412
release.
B
We
are
now
making
it
a
lot
easier
to
deploy
openshift
in
those
environments
and
compared
with
previous,
where
you
needed
an
extra
note
or
a
bootstrap
node.
What
the
agent-based
installer
lets
you
do
is
actually
install
on
all
the
supported
topologies,
whether
it's
a
standard,
High
availability,
cluster
or
a
compact,
39
cluster
or
a
single
node
openshift
cluster.
A
A
You
know,
I
know,
I
talked
with
lots
of
customers,
the
difference
between
openshift
3
and
openshift.
4
was
practically
a
different
product.
What
we
often
lose
over
time
is
openshift.
4
today
on
4.12
is
very
different
from
openshift,
for
you
know
going
back
a
year
or
two
years
ago,
but
what
I
love
is
the
flexibility
we've
built
in
there
to
hopefully
make
things
easier?
Make
things
more
flexible,
give
the
customers
what
they
need
today
and
allow
them
to
take
advantage
of
new
technology.
So
you
know
just
reminder
if
you're
familiar
with
it.
A
As
you
said,
the
upgrades
are
becoming
even
easier.
It's
becoming
simpler,
there's
a
lot
of
work
behind
the
scenes
that
goes
into
that.
So
so
many
things
you,
you
really
explained
it.
You
know
phenomenally
and
I
know.
You
know
you
and
your
team
have
done
a
lot
of
a
lot
of
great
work
to
help
enable
those
and
I'm
glad
you
teed
up.
You
know
this
show
is
in
the
cloud,
so
we
absolutely
want
to
talk
about
clouds.
A
So
when
we
talk
about
the
hybrid
solution
that
we
have
a
lot
of
that
now
is
working
on
the
solutions
that
we
have
with
our
hyperscaler
partners.
So
last
year
we
talked
a
little
bit
about
Azure
stack
Hub
and
how
we're
supporting
openshift
on
it,
and
so
why?
Don't
you
bring
us
up
to
date
with
the
AWS
enhancements
that
we
have
in
4.12.
A
B
B
Planes
are
still
running
in
the
regions,
but
when
you
actually
deploy
onto
Outpost
your
workers
or
their
edge-based
workers
now
are
running
on
outposts
and
then,
in
the
case
of
local
zones.
What
that
means
we're
also
extending
the
workers
to
the
edge
with
the
use
of
local
zones
and
so
definitely
take
a
look
at
our
documentation
and
release.
Notes
I'll
go
into
more
detail,
but.
A
A
You
know
a
cluster
that
I
got
down
to
a
certain
footprint,
but
one
of
the
big
enhancements
we
had
I
think
it
was
you
know,
might
have
been
almost
two
years
ago
was
to
be
able
to
have
remote
worker
nodes
where
you
have
the
control
plane
running
one
location,
but
the
REM
the
worker
node
could
run
but
still
have
connectivity
back
to
the
control
plane.
So
is
it
it's
just
taking
that
architecture
which
could
have
been
in
a
customer's
data
center,
hosted
data
center
or
in
the
cloud,
and
now
we're
leveraging.
A
A
B
Absolutely
when
we
released
openshift
412
and
it
released
on
January
17th,
that
book
is
a
ga
and
fully
supported
version
of
openshift.
Like
all
versions
before
we
actually
release
anything
to
GA.
We
make
early
candidates
available
so
that
when
you
actually
download
it
it'll
actually
say
easy.
If
it's
an
early
candidate,
but
if
you
don't
see
that
it
and
we've
officially
released
release,
notes
and
documentation
and
actually
listed
it,
it
is
fully
stable
and
ready
for
production
use.
A
Awesome
yeah,
as
you
said,
what's
nice,
when
we
did
the
live
stream,
it
was
just
about
ready
to
be
released
in
between
when
the
live
stream
happened.
For
what's
new
and
and
this
we
we
are
generally
available.
So
absolutely
it's
there.
It's
ga,
you
know,
go
forth.
There's
some
other
questions,
but
I
want
to.
Let
you
I
I,
know,
there's
way
more
features
than
we're
gonna
get
get
to
on
this
one.
B
That
makes
it
a
lot
easier
to
deploy,
but
also
to
manage
all
the
profiles
related
to
it,
and
what
this
actually
does
is.
It
gives
the
necessary
privileges
to
The
Container
processes.
So
that's
why
that
one's
important
and
then
the
other
one
that's
really
exciting,
also
is
around
our
compliance
operator.
B
We've
made
some
enhancements
to
make
running
compliance
scans
or
which
also
provides
remediations
for
issues
found,
and
what
we've
added
to
it
is
not
administrators
have
better
controls
on
a
prioritization
of
which
parts
get
to
run
first,
and
so
this
way
you
can
ensure
that
your
scans
are
timely.
You
get
your
results
and
you
can
have
enter
your
compliance
in
a
timely
manner.
B
If
you
will
is
our
Network
observability
operator,
while
it's
not
specific
to
security,
this
is
sort
of
a
core
to
actually
being
able
to
observe,
monitor,
trace
and
actually
manage
your
Network,
and
so
with
this
now
you
can
actually
identify
bottlenecks
or
troubleshoot
connectivity
issues
and
I
know
any
open
shift
administrator.
Our
user
is
going
to
find
this
really
handy,
especially
when
you're
trying
to
find
that
performance
issue
that
you've
been
chasing.
So
these
are
just
some
of
the
exciting
features.
A
Yeah,
I'm
and
I'm
so
glad.
Of
course,
you
know
we
talk
about
Security
in
almost
every
episode,
because
you
can't
have
a
discussion
on
what's
going
on
in
the
cloud
without
that
a
couple
quick
plugs
to
mention
you
know
kubecon,
one
of
the
big
shows
that
we
go
to
I've
been
to
many
times
next
week.
There's
actually,
for
the
first
time
an
independent
show
called
Cloud
native
security
con,
the
red
hat
team
will
be
there.
We
we've
got.
A
You
know
product
managers
and
Technical
marketing
people
all
going
to
be
there.
So
if
you're
going
to
be
in
Seattle,
definitely
check
that
out.
Also
we'll
we'll
put
up
in
the
chat
there
is
one
of
our
other
live
stream
shows
called
the
secure
cloudcast,
so
Mike,
Foster
and
Kim
Carlos
do
that
they
they
just
had
an
episode
this
week,
so
be
sure
if
you
want
to
learn
even
more
about
security,
that's
happening
in
this
space.
A
You
know
check
out
those
playlists
I
believe
that
one's
run
once
a
month.
You
know
some
really
good,
in-depth
topics
from
from
a
security
standpoint,
yeah
and
ju,
for
you
know
from
my
standpoint
when
I'm
talking
to
our
our
customers,
you
know
security,
one
of
the
top
issues
they
all
have,
of
course,
and
it's
also
one
of
the
you
know
one
of
the
big
reasons
why
people
turn
to
Red
Hat
we've
got
Decades
of
experience
into
making.
A
A
So
do
there's
a
question.
You
know
what
we'll
throw
it
up
here
and
if
it's
something
you
can
answer
great,
if
not
we
we
can
do
some
follow-up,
but
they
asked
about
performance,
something
I
get
every
once
in
a
while,
but
you
know
from
release
to
release.
You
know:
how
do
we
look
at
performance?
They
specifically
asked
if
there
was
impact
on
using
ovn
kubernetes
versus
openshift
sdn.
A
So
you
know
if
you
can
handle
that
specifically
or
generally,
you
know
it's
one
of
those
tough
things
because
we're
software
there's
infrastructure
underneath
it
that
impacts
it
and
configuration.
So
you
know
I
know
from
my
networking
background.
You
know
there
there's
always
so
many
different
factors
on
there,
but
you
know
we'll
throw
up
the
the
performance
question
for
you.
B
We
invested
a
lot
of
time
into
our
performance
and
scalability
testing
and
what
we'd
do
was
to
ensure
that
what
you
could
do
in
the
previous
ovs
is
something
that
you
can
also
do
in
ovn.
We've
also
made
it
possible
to
do
additional
security
related
things,
so
it's
more
secure
but
from
a
performance,
Wise
It's,
also
enabling
us
to
reach
new
limits
or
I
shouldn't,
say
any
limits:
New
Heights
that
we
haven't
previously
at
cleaned.
Having
stated
that
I
would
probably
differ
folks
to
look
at
our
performance
and
scalability
guidelines
in
our
release,
documentation.
A
Phenomenal
yeah
and-
and
you
know
it's
so
funny
Drew,
you
know
what
we
talked
about
at
the
beginning.
You
know
there's
so
many
things
that
go
into
it.
You
know
when
I
talk
to
customers
these
days.
You
know
we
throw
up
all
these
various
projects
that
we're
involved
in
there's
always
new
things
coming
down
the
pike.
You
know
my
disclaimer
is
like
look.
There's
I
looked
through
one
of
these
releases,
there's
often
a
third
to
half
of
them.
A
A
You
know
at
the
project
level
at
the
product
level
and
everything
we
do
so
we've
got
a
little
bit
more
time
left
if
there's
some
other
kind
of
key
highlights
in
412
that
you
want
to
do
otherwise.
I
do
have
one
or
two
questions
for
you
before
we
wrap
once
we're
we're
through
some
of
the
main
pieces
and,
of
course,
we've
already
put
in
there.
You
know
some
of
the
places
people
can
follow
up
to
read
all
of
them
when
it
comes
to
412.
yeah.
So.
B
I
think
one
of
the
things
I
wanted
to
highlight
when
we
were
talking
about
installer
and
the
cloud
is
in
412.
In
Tech
preview,
we've
introduced
a
capability
need
to
install
openshift
onto
Google
Cloud
platform
into
a
shared
VPC,
while
it's
technology
preview,
the
reason
I
bring
it
up
is,
if
you're
thinking
about
it.
Traditionally
we've
told
customers
they
had
to
use
our
full
sorry,
full
control,
method
of
user
provision,
infrastructure
well
with
412
I'm
happy
to
see
we're
actually
going
to.
B
Let
people
do
this
through
our
full
stack,
automation,
method
of
installer
provision,
infrastructure
or
IPI
to
actually
do
this,
so
instead
of
having
to
that
sort
of
complex
process
to
actually
configure
it,
we're
making
it
easier
and
so
right
now
it's
in
Tech
preview
and
obviously
we're
going
to
make
this
available
in
upcoming
releases.
Another
exciting
installer
change
that
we've
made
recently
is
that
you
now
can
install
openshift
on
nutanix
using
our
hosted,
assisted
installer,
and
so
now
now
you
have
a
web-based
experience
to
actually
deploy
onto
newtonics.
So
it's
a
lot
easier.
B
So
these
are
just
some
of
the
exciting
changes.
One
of
the
other
things.
That's
also
interesting
to
mention
that
people
don't
typically
think
about
is
running
Windows
workloads
and
I.
You
can
now
run
Windows
workloads
in
Google
Cloud,
also
with
openshift,
on
running
on
gcp.
So
these
are
just
some
of
the
exciting
things.
A
That's
awesome
because
I
know,
like
generally
Windows
container
support.
I
know
there
are
a
lot
of
caveats
when
it
first
came
out
about,
like
you
had
to
be
on
the
latest
version
of
everything
in
Windows
and
I
heard.
A
lot
of
customers
were
interested
but
didn't
have
there
and
while
it
was
supported
in
openshift,
getting
it
supported
in
the
cloud
you
know
has
been
a
little
bit
challenging
so
so
yeah
are
we
starting
to
see
some
real
world
adoption
now
of
Windows
containers.
B
We
are
seeing
a
lot
of
Ventures
and
we're
starting
to
see
some
adoption
and
and
that's
why
you're
starting
to
see
that
we're
expanding
our
coverage
into
the
cloud,
and
so
that's
why
you're
seeing
it
on
gcp
in
terms
of
adoption,
I
can't
speak
to
the
adoption
myself
but
I
know.
We've
had
tremendous
interests
on
this
front
and
we're
actually
looking
to
expand
our
footprint.
There.
A
Yeah
so
awesome,
thank
you
and
again,
you
know
there's
way
more
people
should
learn
about
4.12.
Definitely
you
can
take
a
look
to
one
of
the
things
I
I
find
kind
of
helpful.
Is
there
are
often
things
that
you
know
the
dot
releases
that
happen
add
little
pieces,
but
you
need
to
almost
look
back
and
aggregate
to
be
like,
oh
well,
you
know
we
just
talked
about.
A
A
I
expect
you've
got
a
pretty
good
Viewpoint
because
you,
you
spent
a
couple
years
outside
of
red
hat,
probably
heard
certain
things
about
how
people
thought
about
openshift
or
even
from
when
you
left
Red
Hat
to
when
you
came
back.
Openshift
changed
a
lot,
so
you
know
what
would
you
get
you
know?
What
would
you
mention,
or
you
know
what
What
observations
have
you
had
about
out?
A
B
You
think
about
openshift.
Our
unique
offering
here
is
that
we
target
the
open,
hybrid
Cloud
across
the
physical,
the
virtual,
the
bare
metal,
the
cloud,
whether
it's
private
or
public,
and
now
to
the
edge
and
also
starting
to
expand
into
the
far
Edge
I.
Don't
know
that,
there's
any
other
offering
out
there
that
has
as
diverse
and
as
wide
a
coverage
as
we
do.
I
I
truly
believe
that
and
I
think
one
of
our
when,
when
I
left,
we
were
much
smaller
than
we
are
today
and
also
what
we
covered
platform
wise.
B
Even
though
we
have
this
great
dream
for
a
hybrid
Cloud
platform,
which
is
much
much
smaller
today,
where
on
all
the
major
hyperscalers,
where
we
have
such
deep
coverage
and
white
coverage
that
it's
almost
near
impossible
for
anyone
to
sort
of
catch
up
in
a
sense
and
what
I
mean
by
that
is,
if
you're,
only
doing
a
single
kubernetes.
It's
easy.
There's
a
lot
of
choices
out
there,
but
I
have
yet
to
meet
a
customer.
A
B
The
public
Cloud
also
will
always
be
there
and
there
for
as
long
as
I've
lived,
there
are
still
mainframes
today
and
there's
still
a
lot
of
virtualization
out
there,
so
that
it's
a
very
mixed
and
very
diverse
set
of
requirements
that
people
have
and
for
that
very
reason,
the
multi-cloud
and
hybrid
is
going
to
be
here
for
a
very
long
time
to
come.
And
that
being
said,
openshift
does
really
well
in
those
environments
by
providing
a
single
platform
for
actually
building
delivering,
operating
and
managing
applications
across
all
of
this.
Without
having
to
relearn
for.
A
B
A
different
variant
of
it,
and
so
that's
probably
I,
think
where
we
shine
the
best
and
where
we
see
a
lot
of
interest,
and
today
you
know
when
I
left,
Red
Hat
the
first
time.
What
I
noticed
is
we
had
a
lot
of
it
was
sort
of
openshift
and
we
had
ansible.
We
had
our
middleware
portfolio.
We
just
had
a
lot
of
different
pieces
that
were
not
as
well
integrated
and
if
you
look
at
where
we
are
today,
everything
sort
of
centers
around
openshift
and
it
it
Bridges
the
gaps.
B
If
you
will
into
all
these
other
areas.
So,
for
example,
we
have
the
capability
to
have
ansible
work
together
and
it's
better
together
with
openshift.
You
can
write
operators
in
ansible.
You
can
make
calls
to
ansible
if
you
need
to
cover
last
Model
automation
for
doing
your
full
end-to-end
provisioning
of
your
applications.
B
B
B
in
the
future,
we're
going
to
start
to
see
some
of
those
exciting
capabilities
brought
into
open,
gym
and
and
what's
interesting
about.
Kepler
is
they're,
taking
some
of
the
power
consumption
measurements
and
inferencing
for
covering
some
of
the
measurements
that
they're
not
able
to,
but
have
to
infer
and
actually
using
that
to
make
recommendations
on
how
the
vertical
pod
Auto
scalar
should
actually
dynamically
rescale
or
move
workloads.
A
No,
due
to
that
was
perfect
actually
to
look
a
little
bit
going
forward,
so
we
actually
put
up
in
the
chat.
First,
the
hybrid
discussion,
I
I,
worked
on
an
e-book
back
in
2021,
so
cloud.redhat.com
hybrid
people
too
often
get
caught
up
on
the
terminology.
Oh
my
hybrid
and
my
multi-cloud.
How
do
I
do
this?
The
reality
is
it
by
its
very
nature,
is
additive,
as
you
said,
I
always
joke
almost
nothing
ever
dies
in
it.
A
We
need
to
be
able
to
change
and
get
rid
of
things,
but
the
the
breadth
and
the
depth
of
our
offering
and
our
customer
experience
that
we
have
is
unmatched
in
this
industry.
It's
one
of
the
things
that
brought
me
to
Red
Hat
is
all
the
real
customers
that
shared
what
they'd
done.
The
journey
that
they've
been
on
I'm.
A
Actually
super
excited
I'm
going
to
be
hosting
a
panel
of
customers
at
Red,
Hat
Summit
in
May,
to
talk
about
some
of
the
real
things
that
they've
done
and
how
openshift
not
just
that
they
chose
openshift,
because
it's
great
but
the
impact
that
it's
had
on
their
business
and
you
know
how
they
can
help
to
over
time,
transform
their
applications
and
that
has
direct
impacts
on
their
customer
experience.
Their
employee
experiment
experience
but
you've
laid
out
Drew
so
nicely,
there's
so
much
more
work
that
we
have
left
to
do
so.
A
You
know
I
started
it
off
the
the
discussion
about
the
billion
dollars
that
we've
reached.
What's
really
interesting
on
the
inside
is
when
I
hear
the
product
managers
and
the
engineers
almost
like.
Oh
we've
got
so
many
challenges,
and
so
many
things
on
our
plate.
It's
like
we've
come
so
far
on
the
journey
and
we've
done
awesome,
but
we
will
continue
to
focus.
You
know
back
in
the
Amazon
calls
it
the
customer
obsessive.
A
But
you
know
we
are
not
comfortable
with
where
we
are
there's
so
much
more,
that
we
want
to
be
able
to
do
in
the
product
and
with
our
customers
to
to
make
those
products.
So
with
that
Jew
I
I
think
this
is
a
great
conversation.
I
really
appreciate
you
coming
on
to
share
everything
that
we
had
in
4.12,
and
so
please
congratulations
to
the
whole
team
and
we
look
forward
to
hearing
you
know
our
our
customers
feedback
as
they
continue
their
Journey
foreign.
A
If
you
go
to
Red
Dot
HT
slash
live
streaming,
you
can
see
all
of
the
red
hat
live
streams
as
as
well
as
you
know,
what
we
have
with
this
show.
I
will
be
back
with
two
weeks.
We've
got
a
great
external
guest
talk
about
kind
of
the
future
of
cloud
and
where
we're
going
Andy
man
is
scheduled
for
that
I'm
working
on
some
really
exciting
guests
that
we've
got
in
the
coming
weeks,
so
try
to
make
it
every
two
weeks.
A
I've
got
a
little
bit
of
travel
that
might
switch
things
by
a
week
or
two
so
be
sure
to
check
either
the
YouTube
playlist
for
this
for
in
the
clouds
or
that
live
streaming
website.
For
all
of
the
updates
that
we
have
in
the
meantime,
please
feel
free,
as
always
reach
out
give
us
your
feedback
love
to
hear
any
themes.
Topics
guests
that
you
would
like
us
to
cover
in
in
coming
episodes
do
check
out.
A
If
you
go
to
cloudnative
security,
con
registration
is
open
for
red
hat
Summit,
just
redhat.com
Summit.
You
can
find
out
lots
of
what's
going
on
it's
in
Boston
at
the
big
Convention
Center.
We're
expecting
to
be
back,
you
know
really
a
full
in-person
event,
so
hope
many
of
you
can
join
us
in
Boston
for
that
so
until
next
time,
I'm
Stu
miniman
and
thank
you
as
always,
for
joining
us
on
your
journey
in
the
clouds
laughs.