►
From YouTube: OpenShift Coffee Break: Managed Cloud OpenShift
Description
Get your espresso ready for the EMEA OpenShift Coffee Break as we welcome our special guest Simon Briggs, Solution Architect at Red Hat. With Simon we'll discuss how to take advantage of Red Hat and their Cloud partners capabilities in delivering fully performant OpenShift environments that are fast to deploy, quick to scale and bought directly from the cloud vendor, through our Managed Cloud OpenShift offerings.
Twitch: https://red.ht/twitch
A
A
A
I
I
forgot
that
you're
a
good
british
guy,
so
yes,
that's,
okay.
We
are
open
to
everything,
so
not
only
difficult.
So
please
sign
up.
Do
you
want
to
introduce
yourself
some?
I
know
you
very
well
because
we
work
so
lucky
to
work
with
you
on
the
same
team,
but
please
I
would
like
to
have
you
introduce
yourself.
B
Yeah,
thank
you
fabio
and,
and
thanks
everybody
else
for
joining
us
today.
As
fabio
said
the
name
simon
briggs,
we've
made
a
little
joke
about
me
being
from
the
united
kingdom.
Don't
hold
it
against
me,
I'm
very
happy
to
talk
to
you
all
today.
My
job
within
red
hat
is
to
be
a
solutions.
Architect,
so
do
a
very
similar
job
to
fabio.
B
A
B
B
There
are
other
red
hat.
Open
shift,
managed
services
available.
It's
just
it's
easiest
for
me
to
demonstrate
aws,
because
I
work
on
their
platform
and
then
hopefully,
fabio
will
open
it
up,
and
some
people
about
have
some
interesting
ideas
or
questions
and
answers
that
they
would
like
to
go
through.
A
B
Yeah
well,
the
first
thing
I
always
point
out
is
my
emails.
Address
is
on
these
slides
and
it's
there
for
a
reason.
Is
there
for
you,
as
customers
of
red
hat
and
our
partners
to
use?
Basically,
I'm
there
I'm
pretty
much
a
subject
matter:
expert
in
europe,
middle
east
and
africa
around
this
topic,
and
so
I'm
very
happy
for
you
to
reach
out
and
talk
to
me
about
things.
Obviously
fabio
zaire.
Many
other
members
of
our
team
are
available
to
talk
to
you.
B
But
if
you
want
to
speak
to
me
directly
use
our
email
address
and,
of
course,
the
title,
why
managed
openshift
cloud
services
and
I've
been
a
bit
provocative
in
the
question?
I
maybe
should
have
put
question
mark
at
the
end?
No,
no,
but
I'd
love
it
and
read
out
the
title
and
they,
the
the
reason,
is
what
I'm
trying
to
bring
out
in
that
title
is
the
fact
that
openshift
is
a
fantastic
tool,
but
why
have
we
gone
further
with
the
solutions
as
red
hat
and
our
apartments
and
this
side?
B
B
Yes,
so
just
to
make
it
make
sure
everyone's
familiar
now.
I
know
this
is
the
open
shift
coffee
break
session,
so
many
of
you
should
be
aware
of
what
open
shift
is,
but
a
very
quick
few
comments
around
why
openshift
has
been
important
in
the
kubernetes
space
for
a
long
time,
and
the
first
point
is
it's
more
than
kubernetes,
and
that
means
essentially
that
is
at
its
core.
Is
it
at
its
central
point?
B
So
it's
been
a
very
powerful
technology
and
really
transformational,
so
it
is
at
the
core
of
open
shift
and
always
will
be
full
for
a
long
time,
but
that
technology
stack
can
be
quite
complex
to
build
of
the
services
around
and
that's
what
we're
highlighting
here
with
the
many
icons
on
the
left
hand
side.
So,
yes,
kubernetes
as
a
release,
is
at
the
center
of
this
product,
but
we
also
rack
in
open
shift
all
the
other
cncf
the
foundation
that
manages
that
containerized
platform
open
source
community.
B
B
B
I
think
so,
obviously
in
the
middle
red
box.
What
we're
doing
here
is
explaining
that
all
those
pieces
come
together
in
one
tool
with
openshift
they're
all
built
together,
all
tested
together,
all
validated
together
and
all
hardened
together,
which
means,
as
a
customer,
you
can
rely
on
the
fact
that
the
openshift
tooling
will
make
these
things
work
for
you,
and
then
our
lifecycle
will
manage
those
pieces
together
in
synchronization.
B
I
know
the
point
on
the
right
hand.
Side
is
that
if
customers
choose
to
use
their
own
kubernetes
service,
they're,
ultimately
only
getting
the
engine
of
the
car
as
a
customer,
it's
their
choice
to
take
that
engine
and
then
add
all
the
other
pieces
that
I
was
talking
about:
the
seat
belts,
the
transmission,
etc
around
that
engine
themselves
now
often
because
the
industry's
full
a
very
bright,
technically
able
individuals
building.
B
That
infrastructure
is
not
such
a
great
challenge
because
you
tend
to
build
in
a
smaller
form
or
smaller
footprint
than
you
would
in
your
ambitions
to
go
hyperscale
with
your
services
and
at
the
point
you're
building
it.
You
are
just
plugging
together
pieces
that
are
all
understood
and
you're
able
to
make
sure
they
all
work
together,
but
the
image
there
is
showing
how
those
jigsaw
pieces.
Hopefully
that
translates
to
a
european
middle
east
and
african
audience.
The
little
blue
piece
is
on
the
left-hand
side
of
the
blue
box.
A
Yeah,
that's
definitely
a
great
point
could
be
something
already:
oh
an
old
story,
so
everything
is
integrated.
Everything
is
enterprise.
Great,
that's,
okay
could
be
a
boring
message,
but
the
fact
that
openshift
is
going
to
provide
or
is
is
there
because
to
allow
companies
enterprises
just
to
provide
the
final
value
because
technology,
but
we
are
technologists
that
we
are
passionate
about
technology
per
se.
But
when
we
speak
with
our
customers,
they
need
to
provide
value
to
their
and
customers.
A
B
Absolutely
I
sometimes
upset
technology
as
fabio,
because
I
do
like
to
be
a
bit
not
confrontational,
but
a
little
bit
controversial.
When
I
talk
to
my
customers-
and
sometimes
I
say
if,
if
us
technologists,
we
want
to
build
platforms
like
kubernetes,
but
we're
doing
it
for
kubernetes
sake
and
we're
not
actually
delivering
services
on
top.
That
actually
means
we're
hobbyists
we're
not
professionals,
and
that
comes
across
as
a
little
bit
argumentative.
B
I'm
trying
to
make
that
point
that
a
hammer
is
a
useless
hunk
of
metal
until
it's
hammering
something
into
a
wall,
and
until
you
recognize
that
the
value
of
openshift
is
opaque
and
you
don't
truly
understand
it.
But
when
you
think
of
openshift
as
giving
a
true
value
to
customers
as
a
tool,
then
suddenly
its
power
comes
forward
and
often,
as
you
say,
fabio,
it's
a
boring
message.
It's
boring
because
what
red
hat's
talking
about
is
productivity
security,
reliability,
performance
they're,
not
really
very
sexy
values
in
people's
brains
as
technologists.
A
A
B
And
many
of
our
customers
are
partners
with
us
in
the
open
source
community
right
absolutely
so,
ultimately,
the
oh
we've
lost
our
connection
again,
he
seems
to
be
a
bit
late,
yeah.
Ultimately,
I've
already
described
this
side,
so
we
won't
dwell
on
it.
But
the
idea
here
here
is
that
openshift
is
a
solution
that
is
dedicated
to
helping
organizations,
deliver
cloud-native
applications
effectively
and
productively
into
their
environments
and
make
sure
they
can
manage
the
life
cycle
of
that
service
as
a
quality
service.
B
Obviously
we
have
rel
for
the
traditional
applications
on
the
left
hand,
side
and
actually
the
cloud
native
apps
are
becoming
more
and
more
influential
in
the
the
new
usage
modes
or
use
cases
of
a
a
I
m
l
functions,
etc.
So
all
these
capabilities
are
covered
by
the
red
hat
portfolio,
but
we
are
concentrating
here
on
openshift
and
it's
really
the
bottom
line
of
icons
that
I
wanted
to
bring
to
your
attention
when
we're
talking
about
here
and
that's
moving.
B
So
we
have
deliberately
built
openshift
to
be
the
same
code
base
working
across
any
of
those
environments,
be
it
physical,
virtual,
public,
private
clouds,
edge,
etc
and
the
freedom
to
be
able
to
utilize
the
same
open
shift
across
those
different
platforms
is
part
of
our
gateway
towards
the
hybrid
cloud
capabilities
that
many
of
our
customers
are
looking
at,
where
some
workloads
some
use
cases
suit.
A
data
center,
private
data
center
type
delivery
mode
and
yet
many
others
suit
more.
B
Oh
we've
gone
the
other
way,
even
though
I
drove
and
because
of
that,
what
red
hat's
moved
towards
is
a
situation
where
we
have
been
able
to
deliver
our
software
for
the
traditional
on-premises
data
center.
What
we
call
customer
managed
self-managed
openshift
container
platform,
which,
if
you
look
at
the
middle
multi-colored
ribbon
running
through
this
slide,
is
it
is
the
red
box.
On
the
right
hand,
side
we've
always
been
able
to
deliver
that
with
our
open
shift
capability
and
we've
got
many
many
many
very
happy
customers.
B
B
We
all
know
about
the
the
media
going
wild
at
the
moment
about
the
great
resignation
and
how
difficult
it
is
to
hire
people
with
really
good
kubernetes
site
reliability,
engineering
skills.
So
many
organizations
have
effectively
found
the
resourcing
of
that
team
internally
as
being
a
restriction
on
their
overall
ability
to
scale
and
deliver
with
openshift
in
the
manner
that
their
organizations
are
demanding
of
them
and
they've
come
to
red
hat
and
said:
look
you
guys
are
the
experts
on
delivering
openshift?
You
know
openshift
intimately
from
the
core
upwards.
You
know
the
code.
B
You
know
how
best
to
deliver
this
solution.
Can
we
use
some
of
your
knowledge
some
of
your
capabilities,
some
of
your
team
skills
in
delivering
that
scale
beyond
our
self-managed
capabilities,
and
that's
really
where
we
expanded
into
the
gray,
I
believe
in
english
we
call
it
teal
box
on
the
slight
left
hand,
side
of
the
red
box.
I
don't
know
if
that
translates
internationally,
but
we
started
delivering
a
solution
called
openshift
dedicated
some
years
ago
and
what
that
was
was.
It
was
a
solution.
B
You
bought
directly
from
red
hat,
where
we
wrap
the
management
of
the
openshift
infrastructure
on
top
of
the
support
relationship
with
the
openshift
software
that
we
were
providing
and
then
customers
using
aws,
initially
as
a
as
a
cloud
could
buy
that
open
shift
dedicated
from
red
hat,
and
we
would
manage
that
environment
on
their
behalf
and
that
solution
still
exists
today
and
angie
has
expanded
across
into
google
cloud.
You
see
the
icon
above
it
now.
That's
a
good
capability,
the
site,
reliability,
engineering,
team
or
practice
that
red
hat
has
built
is
very
extensive.
B
We've
been
able
to
bring
some
very
large
customers
with
us
with
the
openshift
dedicated
solution
and,
ultimately,
particularly
on
aws.
It
was
highly
successful
and
if
you
just
put
a
pin
in
that,
as
our
american
friends
say,
I'll
go
back
to
the
fact
it
was
so
successful
when
we
talk
about
their
other
block
to
the
left.
That
has
the
aws
economy
in
this
list.
But
what
that?
B
What
our
customers
can
do
is
actually
buy
that
level
of
service
that
managed
openshift
service
and
the
openshift
support,
but
directly
from
that
hyperscale
cloud
vendor.
So,
of
course
we
we
have
a
solution.
It's
called
roik
red
hat,
open
shift
instance
for
kubernetes.
I
believe
on.
Oh
no
open
shift
on
ibm
cloud,
I'm
confusing
myself,
so
that's
relic
on
ibm
cloud
and
that's
purchasable
via
ibm
with
all
the
commercial
relationship
existing
with
ibm.
It's
not
transacted
directly
with
red
hat,
making
it
different
from
the
openshift
dedicated,
but
also
technically.
B
As
you
can
see,
there,
we've
got
more
solutions.
We've
got
what's
called
arrow
as
your
red
hat,
open
shift
and
actually
arrow's
been
around
a
few
years.
Now
we
never
had
the
ability
to
deliver
on
azure
separately
with
the
osd
solution
so,
and
the
success
of
osd
on
aws
actually
helped
us
in
conversations
with
azure,
where,
as
an
organization,
they
said,
look
many
of
our
customers
want
open
shift,
but
at
the
moment
they're
having
to
buy
openshift
and
then
build
it
themselves
on
our
azure
platform.
B
B
That
was
released
about
a
year
and
a
half
two
years
ago.
Now
and
that's
where
aws
sells
openshift
directly
to
customers
and
they
can
consume
it
as
part
of
any
commitments
commercially.
They
have
with
open
with
aws,
etc.
But
it's
underpinned
by
aws's
and
red
hat
site,
reliability,
engineering
organizations
as
a
quality
service.
A
A
And
anna
castro,
I
I
could
be
just
a
little
confusing
taking
a
decision
and
say:
oh,
yes,
gather
your
message,
but
why
actually
why?
I
should
take
this.
The
road
of
the
manager
service
from
not
taking
your
perspective
as
a
business
perspective,
let's
say
from
the
part
and
the
ops
part
or
from
the
business
final
and
business
customer
side.
B
B
B
B
On
top-
and
an
illustration
of
that
is
I
built
a
rosa
cluster
earlier
today
to
demonstrate
to
you
at
least
show
you
very
quickly
what
we're
talking
about
here
and
it
took
me
less
than
half
an
hour
to
go
from
having
no
infrastructure
in
aws
whatsoever
to
then
having
a
fully
performance,
secure
production,
ready,
open
shift
environment
ready
to
log
in
and
I'll
show
you
what
that
environment
in
a
minute.
But
that's
how
quickly
we
can
deliver
that
infrastructure.
What
we're
doing
is
taking
away
the
complication
for
the
customer.
B
The
middle
pillar
talks
about
efficiency.
Well,
obviously,
if
organizations
are
allowing
red,
hat
and
aws
to
manage
the
infrastructure
of
openshift
on
their
behalf,
then,
ultimately
we're
able
to
bring
the
economies
of
scale
of
hundreds
of
customers
utilizing
our
facility
to
be
able
to
deliver
at
cloud
scale
the
services
that
they
demand.
B
So
using
this
kind
of
model
allows
organizations
to
get
cloud
commercial,
open
shift
or
commercial
terms
for
openshift
in
the
cloud,
which
is
a
very
interesting
to
organizations
when
they're
looking
at
scaling
out
that
open
shift
capability
for
themselves
and,
of
course,
as
with
any
of
our
solutions,
these
are
driven
with
a
full
support,
wrap
as
well.
So
not
only
are
our
teams,
our
site,
reliability,
engineering
teams,
proactively,
managing
our
environments
for
rosa
and
the
other
managed
openshift
services.
B
We're
actually
offering
a
reactive
support,
wrap
in
that
offering
as
well
where
customers
can
log
with
us
at
any
point.
Any
problems
they
see
within
the
environment
to
concentrate
our
efforts.
If
it's
not
something
which
is
very
obvious
from
our
proactive
management
of
the
platform
and
then
the
other
pillar
is
really
just
talking
about
that
choice.
So
what
we're
doing
is
talking
about
being
able
to
allow
customers
to
move
from,
maybe
being
on
premises.
B
B
Please
just
drill
down
onto
a
bit
more
detail
of
how
that
choice
manifests
on
one
of
those
hyperscale
vendors.
Other
hyperscale
vendors
are
available,
as
we
always
say
in
the
uk
when
we
end
up
talking
about
a
specific
vendor.
But
as
you
can
see
here,
the
idea
of
choice
is
built
into
our
platform,
so
for
your
customers
or
for
yourselves.
If
you
are
a
customer
of
red
hat
by
allowing
organizations
to
utilize
a
solution
like
rosa,
what
we
feel
we're
doing
is
with
our
aws
partner,
making
sure
customers
can
choose.
B
But
equally,
you
can
manage
your
own
open
shift
on
aws
the
infrastructure
as
a
service
platform,
use
the
hyperscale
capability
of
aws,
but
cafe
specific
choose
to
manage
their
own
open
shift
on
top
of
aws
perfectly
valid,
very
powerful
for
them.
As
an
organization
and
then
obviously,
we've
got
two
choices
for
customers
who
want
red
hat
to
manage
that
open
shift
environment
on
their
behalf.
B
We've
got
the
dedicated
solution
and
globo's
a
good
reference
for
that
where,
as
a
customer,
globo
wants
to
buy
open
shift
directly
from
red
hat,
wants
to
remain
in
that
relationship
with
red
hat,
but
want
to
be
able
to
allow
red
hat
to
manage
on
their
behalf
that
open
shift
environment,
but
in
the
fourth
box
to
the
right.
What
we're
doing
is
stressing
that
many
customers
actually
would
like
to
use.
A
Simon,
might
I
ask
you
as
long
as
I
move
from
the
left
to
the
right
in
this
picture?
Do
I
miss
something
in
terms
of
flexibility?
In
the
configuration
phase,
I
mean
something
that
is
not
possible
to
do
when
if
I
go
from
the
on-premise
of
manage
open
shift
to
the
radar
dead
shift
service
on
nws
rosa
and
do
I
keep
the
same
level
of
flexibility,
freedom
in
terms
of
plug-in
network
plugins,
something
like
that
or.
B
Yeah
good
question
fabio,
so
if
you
move
left
to
right
across
this
picture
or
you're
effectively
moving
across
the
freedom
spectrum
and
and
that
that's
a
natural
result
of
the
solution,
I
did
say
when
I
was
talking
about
the
managed
openshift
cloud
services
earlier,
that
we
deliver
an
opinionated
way
of
consuming
openshift
with
those
services
and
and
that's
not
something
that
red
hides
from.
We
actually
think
there's
great
value
in
customers
using
our
knowledge
about
our
software,
but
if
you
think
about
it,
the
red
box
on
the
far
left.
B
As
you
look
at
this,
the
customer
managed
solution
that
gives
customers
ultimate
flexibility
on
what
they
want
to
deliver
from
an
infrastructure
and
an
openshift
point
of
view.
The
infrastructure
is
theirs,
it
resides
in
their
data
centers.
They
have
control
over
access
and
usage
of
that
infrastructure,
and
the
software
can
be
deployed
in
a
myriad
of
different
combinations
of
approach.
B
As
you
move
through,
it
gets
a
little
more
opinionated.
So
obviously,
when
you're
buying
from
a
cloud
vendor
in
the
customer
managed
on
aws
model,
the
infrastructure
is
managed
by
aws.
So
some
of
that
freedom
is
lost.
As
you
then
move
into
the
managed
solutions
on
the
right
hand,
side
of
these
blocks
actually
you're
consuming
red
hat's
opinion
on
what
is
best
when
using
openshift
on
these
cloud
platforms,
and
it
does
restrict
some
of
the
more
creative
construction
ideas,
infrastructure
ideas,
openshift
ideas
that
customers
and
partners
can
use.
B
What
I'm
not
doing
is
saying
customers
should
do
any
one
of
these
different
approaches.
What
I'm
trying
to
do
is
say
that
red
hat
as
an
organization
is
opening
up
its
capabilities
to
allow
customers
to
choose
which
one
of
these
blocks
suits
them
most
readily.
Okay,
cool.
So
it's
a
good
point
fabio
and
thank
you
for
yeah.
B
Yeah
absolutely
and
a
lot
of
my
job
is
helping
organizations
understand
which
one
of
these
kind
of
approaches
suit
the
most
to
be
honest,
and
actually
sometimes
he
answers
eks
or
aks.
You
know,
red
hat
is
trying
to
be
the
the
leader
in
thought
of
how
organizations
should
utilize
the
best
technology
on
on
their
behalf,
and
we
don't
shy
away
from
those
conversations
sometimes
talking
to
customers
with
our
aws
partners.
I
recommend
that
eks
is
the
solution
for
that
customer.
B
B
I
do
notice
a
time
and,
as
usual,
I've
talked
far
too
long
fabio,
so
I'm
actually
eating
into
my
ability
to
demonstrate
and
as
a
technologist,
I'm
sure
you're
all
chomping
at
the
bit,
as
we
say
in
england
to
be
able
to
see
this
technology
actually
working.
So
I'm
going
to
scoot
through
the
rest
of
the
slides
very
quickly.
What
I
wanted
to
do
was
quickly
illustrate.
B
B
So
obviously,
red
hat
aws
provide
support
for
the
pieces
we
deliver
in
this
solution:
aws
for
the
infrastructure,
red
hat
for
the
openshift
software
support,
but
all
the
pieces
to
the
right
the
customer
has
to
manage
to
make
sure
they're
working
in
concerts
for
the
cluster
and,
of
course,
at
scale.
What
they
need
to
do
is
manage
a
lot
of
this,
and
often
many
of
this
because
they're
using
multiple
clusters
when
we
move
to
a,
why
has
that
gone
upwards?
That's
crazy
right!
B
So
when
they
move
to
using
a
managed
cloud
service
rosa
in
this
case,
what
they're
actually
doing
is
allowing
aws
and
red
hat
to
take
over
the
management
of
all
those
pieces.
Those
pieces
don't
disappear
that
are
under
this
larger
pog.
I
actually
know
that,
because
I
put
this
larger
block
over
the
top
and
put
the
detail
of
red
hat
in
aws
manage
your
cluster
on
your
behalf,
so
that
complexity
still
exists,
but
it's
now
red
hat
and
aws
is
responsibility
to
deliver
it
for
the
organization
and,
of
course,
on
the
left-hand
side.
B
B
But
it's
using
virtual
machines
underneath
I
won't
dwell
on
this,
but
it's
using
all
the
great
value
that
red
hat
brings
with
core
os
and
a
mootable
os.
Se,
linux
is
enforced.
It's
a
highly
secure,
industry-leading
hyper-scale
kubernetes
management
system
available
to
organizations
very
rapidly
for
them
to
build
value
upon.
A
B
B
So
I've
signed
into
my
red
hat
account
logging
into
this
openshift
cluster
manager,
and
I
can
see
the
cluster
I
built
earlier
and
actually,
if
we
drill
down
using
this
view,
it's
a
very
easy
view
to
show
you
how
the
different
technology
works.
You
can
see
here
that
this
morning
I
created
it
for
everyone.
Obviously
I'm
an
hour
earlier
than
you
guys,
so
that
was
8
44
in
the
morning
on
central
european
time.
B
Fabio
and
I've
got
any
immediate
information
telling
me
that
that
cluster's
healthy
it
came
up
in
a
very
short
period
of
time,
and
I've
got
it
built
in
certain
ways.
So
this
tooling
then
allows
you,
as
the
manager
of
that
open
shift
cluster
within
an
organization
to
start
making
it
available
to
the
rest
of
your
organization.
B
B
But
you
can
integrate
this
with
your
ldap
facilities,
etc.
Just
like
you
would,
with
any
other
open
shift
environment,
you
can
add
on
extra
capability.
So
many
of
the
powers
of
open
shift
initially
are
not
turned
on.
When
you
deploy
an
open
shift
environment,
you
can
turn
them
on
because
they
actually
put
pressure
on
your
openshift
cluster.
So
it's
something
to
opt
into
they're
available
there
for
you,
the
cicd
engines,
the
devops
engines,
the
serverless
engines,
etc,
they're
all
available
to
run
as
operators
on
openshift.
B
Today
within
the
managed
cloud
services
model,
though,
there's
also
some
kind
of
uber
operators,
we
call
them
add-ons
and
when
you
deploy
them,
they
become
part
of
the
managed
service
for
the
managed,
open
shift,
and
in
this
case
we
might
want
to
integrate
the
already
existing
logging
that's
going
on.
In
the
background
some
reason
the
screen
is
not
refreshing.
B
B
So,
within
this
tooling,
it's
very
easy
to
be
able
to
set
up
a
new
machine
pool
of
worker
nodes
available
to
the
infrastructure,
and
importantly,
you
can
even
use
ec2
spot
instances
for
cost
control
within
this
environment.
I
actually
wrote
a
blog
about
that.
If
you
do
a
search
for
simon
briggs
and
spot
instances
on
aws
rosa
on
google,
you
will
find
that
information.
B
B
As
I
said,
I
created
my
cluster
admin
and
there
I
can
start
helping
organizations
within
my
business
and
to
get
ready
to
create
new
projects
to
deploy
my
software
into,
and
all
of
that
was
available
within
tens
of
minutes
from
commission
of
absolutely
nothing
to
the
point
of
getting
a
production.
Secure,
industry-ready
open
shift
available
for
my
software
to
be
quite
important.
A
A
The
reason
why
I
asking
this
because
I
how
to
highlight
again
the
something
they
already
mentioned,
so
freedom
in
the
choice
of
the
whatever
kind,
open
shift,
release
and
kubernetes
as
well
and
a
customer
would
like
to
leverage
so
through
acm.
Probably
you
can
have
your
rosa.
You
can
have
openshift
apprentice.
So
really
you
can
control
your
wide
range
of
upper
shift.
Instances
and
yeah.
B
Yeah,
the
acm
is
a
fantastic
tool
for
being
able
to
free
yourself
as
an
organization
at
to
that
level
fabio.
So
obviously,
with
acm,
you
manage
the
apple
from
an
application,
centric
approach
and
there
you
can
build
rules.
That
say
I
have
a
cloud
in
arrow.
I
have
a
cloud
in
rosa.
I
have
a
cloud
in
roik.
I
have
a
self-managed
cloud,
but
I
want
to
deploy
10
different
applications
all
with
different
use
cases
and
requirements
as
part
of
them,
so
some
of
them
might
want
to
deliver
on
arrow
and
self-manage.
B
Some
of
them
might
want
to
deliver
on
rosa
and
arrow,
and
all
that
logical
ruling
can
be
built
very
effectively
within
that
tool
set
to
deliver
across
these
platforms.
The
one
thing
you
can't
do
with
acm
today
is
build
a
roaster
cluster.
Okay,
presently,
you've
still
got
to
build
rosa
via
the
rosa
cli
tooling.
We
are
expanding
that
it's
just
taking
time
to
build
that
capability
in,
but
today
you
build
your
rosa
cluster
and
then
you
import
it
into
acm.
B
A
A
B
Much
I
crushed
my
demonstration
down
into
just
a
few
clicks.
I
do
apologize,
but
hopefully
it's
encouraged
people
to
be
interested
in
what
the
managed
cloud
openshift
services
are,
and
maybe
even
in
rosa
itself,
please
reach
out
to
red
hat,
we'll
be
able
to
give
you
much
more
detail.
Obviously
this
has
been
a
bit
of
a
drive-by
shooting
of
an
illustration
of
what
we
able
arrival
today.
A
And
anyway,
I
shared
in
the
meantime
on
I
googled
your
blog
post,
so
I
shared
it
in
the
chat.
It
looks
really
interesting
and
just
to
wrap
up.
First
of
all,
simon
really,
I
appreciate
your
appreciated
your
session
really
interesting
and
thanks
for
your
availability,
I'm
going
to
share
a
link
to
our
audience
in
order
to
so
that
they
they
they
can
look
at
the
all
the
agenda
of
the
openshift
tv
streaming
platform.