►
From YouTube: In the Clouds (E26) | Cloud Ecosystem
Description
The cloud native ecosystem has grown far beyond Kubernetes. The hundreds of projects show the innovation in open source, and the challenge for anyone to keep up with current technology. Red Hat Senior Director, Technical Marketing & Field PM, Cloud Platforms Chris Morgan joins host Stu Miniman to discuss the evolution of the cloud-native ecosystem. Chris was intimately involved in development of OpenShift and its partnerships with many key vendors.
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
B
Hi
and
welcome
to
another
episode
of
in
the
clouds,
I'm
your
host
stu
miniman
and
we
have
a
special
time
and
special
place
for
today.
Yes,
we
are
actually
in
person
in
a
physical
studio,
not
doing
it
remote.
So
I'm
really
pleased
I'm
here
in
raleigh
north
carolina
in
the
shadow
of
the
mothership
of
red
hat
joining
me
is
chris
morgan
senior
director
of
the
customer
and
field
engagement
group
at
red
hat
chris.
Thank
you
so
much
for
joining
it's
great
to
see
you
in
person
and
great
to
be
here.
A
B
A
B
A
Company,
I
I
some
international
business
machines
is
what
I
I
reckon
they
call
it
completely
and
you
know,
and
so
for
me
it
was
kind
of
coming
back
after
the
acquisition,
but
I
I've
had
the
good
fortune
to
you
know.
I
was
a
contributor
to
open
source
when
I
was
in
college,
that's
a
fun
story,
maybe
for
off
the
stream
and
so
to
come
back
to
red
hat.
A
Then
I
started
working
on
our
management
products
and-
and
then
you
know
this,
this
open
shift
thing
came
up
and
I
I'm
super
lucky
that
was
one
of
the
original
four
or
five
business
unit.
Folks,
along
with
joe
fernandez
and
grant
shipley,
you
know
who's
just
returned,
you
know
to
to
really
be
involved,
and
you
know
donnie
was
leading
that
group
and
and
we
worked
with
matt
hicks,
he
was
actually
the
lead
engineer
on
it.
B
A
Team,
you
know
sully
andrew
sullivan
on
the
team
was
the
one
that
he
mentioned.
He's
like.
Why
don't
we
do
something
on
twitch
and
I
was
like
what
is
a
twitch.
I
mean
I
knew
what
a
twitch
was,
but
you
know
so
I
did
what
any
adult
would
do
at
my
age,
and
I
spoke
to
my
kids
and
they
explained
it
all
to
me
and
then
we,
you
know,
came
back
and
the
guys
were
really
all
into
it,
because
it
was
such
an
uncertain
time.
A
You
know
we
we
wanted
a
way
to
to
show
that
we
were
still
humans,
just
like
the
people
out
there,
even
in
isolation
and
and
we
wanted
to
kind
of
create
a
way
for
the
users
in
particular
whether
you
know
they
were
community
users
or
existing
customers,
but
people
that
were
interested
in
our
technologies
to
to
really
connect
with
us
and
and
do
some
things-
and
you
know
it's
just
kind
of
great
to
see
it
grow
up
to
have
a
studio
right.
I
mean
heck
the
fact
that
red
hat
even
has
a
studio.
A
B
We
are
working
on
studios
now,
you
know
matt's
ceo,
he
likes
doing
video,
he
tells
everyone
at
red
hat.
You
know
how
to
get
the
right
camera
and
all
these
things
so
we're
working
on
studios
in
boston,
some
of
the
teams
actually
working
on
that.
You
know
as
we
speak,
but
you
know
so
excited
to
be
here.
Yeah.
B
After
you
know,
I
used
to
spend
a
lot
of
time
in
studios
and
in
front
of
front
of
the
bright
lights
and
everything
like
that.
But,
let's
you
know
we
have
a
little
bit
of
background
sure
and
the
intro,
but
you
know
this
is
in
the
clouds.
So
right
you
have
lived,
you
know,
you've
got
the
scars
and
the
history
of
of
what
comes
on.
B
So
you
know
we
look
today
at
this
like
cloud
native
ecosystem
right,
you
know,
we've
been
going
through
the
cambrian
explosion
of
all
the
companies
that
are
there
and
every
subsection
there's
all
these
startups.
All
the
big
players
are
heavy.
There
I
mean
kubernetes
is
everywhere
right.
It
wasn't
a
given
that
this
would
be
big.
B
A
A
Now,
admittedly,
where
did
we
start
from
an
acquisition
like
everyone
else,
and
I
can
say
that
we
used
absolutely
none
of
that
code
as
you,
you
learned
this
week
in
some
of
our
breakouts,
but
it
did
at
least
plant
the
seeds
and
the
ideas,
and
from
that
we
grew
into
what
is
now
openshift,
but
in
the
first
few
iterations
you
know
an
interesting
thing.
I
I
always
tell
people
you
know,
while
you
know
docker
made
containers
sexy,
you
know
real
had
been
using
them
for
a
few
years
right.
A
You
know
because
they're
fundamentally
a
linux
process,
and-
and
so
you
know
what
the
team
did
actually
led
by
matt
hicks,
he
did
the
coding
for
it.
We
knew
we
had
to
get
some
economies
of
scale,
and
so
we
did
this
first
version
of
openshift
that
was
based
on
rail
containers
and
securing
those
as
best
that
we
could
and
and
then
we
had
a
plugable
system.
We
called
a
cartridge,
you
know
believe
it
or
not.
You
know
for
the
kids
out
there
if
you've
ever
used
the
nintendo
or
your
parents
still
have
theirs.
A
As
you
can
imagine,
the
problem
with
that
is
well.
That
was
just
a
red
hat
standard.
While
it's
a
an
upstream
project,
it's
still
just
us,
and
so
it
was
exciting
when
what
I
would
say,
docker's
contribution
to
what
is
now
this
kubernetes
ecosystem
that
we
took
advantage
of.
Was
they
made?
You
know
plugging
things
into
the
system
and
made
the
containers
just
easier
to
work
with
and
deal
with,
and
you
know
it's.
A
It
has
been
a
journey
on
that
and
starting
from
that
idea
of
you
know,
we've
been
a
linux
company
and
we'll
likely
always
be
a
linux
company.
Our
containers
are
linux,
linux
or
containers,
as
the
t-shirts
show.
It's
great
to
you
know
see
where
we
can
take
that
further
right.
You
know,
I
I
think
you
and
I
were
even
speaking
earlier
today.
I've
always
looked
at
openshift
and
the
way
I
even
explained
it
to
partners
is
think
of
it
as
nothing
more
than
a
better
way
more
easier
way
for
you
to
use
rail.
A
B
Right
so
it's
funny,
I'm
thinking
about
like
the
cartridge
analogy
and
I
think
back
to
you
know,
I
played
on
the
game
systems
that
had
cartridges
and
one
of
the
problems
was
like.
Oh,
you
know
I'll
date
myself,
you
know.
Oh,
you
got
the
atari
system.
Oh
the
new
atari
system
comes
out.
Oh
my
gosh.
None
of
those
cartridges
work
with
the
old
ones
or
you
know
it's
nintendo
versus
sega
versus
something
else.
None
of
those
work
right
across
platform
containers
in
kubernetes.
B
B
If
I
build
an
operator,
you
talked
about
making
relevancy,
but
it's
it's
kubernetes
there.
So
yeah
not
just
works
on
openshift.
You
know
you
change
your
tanzu
xks
any
of
those
other
things
there.
I
I
can
take
they're
there,
so
maybe
talk
to
that
that
shift
from
the
ecosystem,
because
red
hat
has
played.
You
know
an
important
role
not
to
get
everybody
on
red
hat
but
to
grow
that
that
ecosystem.
A
Yeah,
and
so
I
think
what
happened
we'll
start,
you
said
a
lot
of
things
in
there,
so
I'll
kind
of
pick
them
apart
a
little
bit.
If
I
may,
the
kubernetes
piece
the
reason
for
me
personally,
everyone
at
red
hat
will
have
their
opinion
on
it.
Was
you
know,
red
hat
excels
at
taking
communities
that
maybe
already
exist
and
making
them
even
better
right?
If
you
look
at,
we
didn't
invent
linux,
you
could
argue,
we
made
it
pretty
good
right,
it's
to
say
the
least.
A
We
didn't
invent
kubernetes,
you
know
as
the
good
folks
at
google
and
you
know,
and
and
but
they
asked
us
to
join
them,
and
and
we
did
right
and
our
contributions
as
a
company
and
there's
been
so
many
people
that
have
contributed
to
it.
It
was
that
that
piece
was
the
big
change
right
is,
instead
of
going
to
the
ecosystem
and
saying
hey,
this
is
a
red
hat
thing.
A
We
were
able
to
truly
say
it
was
a
community
thing
and
while
we
were,
you
know
obviously
one
of
the
most
major
contributors,
it
wasn't
just
us
and
then
hoping
to
get
people
along
and
and
so
that
really
impacted
all
the
different
ecosystems.
We
talked
about
isvs
right
your
cartridges.
Now
I
thought
you
were
going
to
talk
about
blowing
into
the
cartridge
when
it.
A
But
you
know
we
we
essentially
we're
now
able
to
say
well
hey
this
is
a
community
and
we're
using
this
standard
that
you're
now
used
to
with
regards
to
the
container
run
time
right,
because
the
the
original
runtime
was
even
the
the
open
source
docker
version
in
kubernetes
and
that
caused
then
the
sis
right,
the
solutions,
integrators
and
then
some
of
the
regional
sis.
And
then
you
know
we
still
have
partners
even
in
those
cartridge
days,
but
it
was
just
a
little
tougher.
A
You
know-
and
I
do
have
to
you
know,
point
out
the
the
more
successful
partners
we've
had
that
they
have
been
long-term
with
us.
You
know
and
they've
seen
that
journey
and
I
think
they've
appreciated
it
more
and
they
knew
we
didn't
switch
directions
that
quickly.
You
know,
I
think
you
know
joe
dickman
at
missouri,
right
and
so
joe.
This
is
for
you,
he
you
know
he
he
always
likes
to
say
he
was
the
first
openshift
partner
and
he
was
right.
B
So
yeah,
no,
it
was
great.
Actually
I
saw
joe
down
in
new
york
city.
He
was
there
with
us
at
the
amazon
show,
which
you
know
you
talk
about
things
different
remember
early
days,
you
know
kubernetes.
Well,
it's
google's
hail
mary
to
make
sure
that
multi-cloud
actually
might
become
a
thing
or
of
course
you
need
to
be
able
to
run
multiple
places,
because
otherwise
we
will
all
live
in
amazon.
Now
amazon,
you
know
a
lot
of
us
partner
with
amazon
they're
part
of
it.
So
let's
talk
about
how
things
have
changed.
B
You
know,
I
I
think
back.
You
know
one
of
the
things
I've
spent
you
know
some
time
is.
I
talked
to
some
of
those
early
customers
and
those
early
partners.
There
was
a
lot
of
you
know,
chewing
glass
and
you
know
bleeding
edge
things
of
the
immaturity
of
the
ecosystem
boy.
A
lot
has
changed
in
the
last.
You
know
I
mean
we
know
how
fast
things
are
changing,
but
things
have
changed
a
lot,
so
maybe
give
us
if
you
could
compare
contrast.
If
hey.
B
A
I
think
that's
actually
a
great
question
it.
It
actually
has
evolved
the
same
way
as
the
technology
itself.
I
I
think,
two
or
three
years
ago
we
still
had
to
do
a
lot
of
explaining
to
people.
What
even
a
container
is
right.
It's
it
wasn't
as
universal,
as
at
least
we
at
red
hat
would
like
to
have
believed
it
was
you
know
now
I
think
that's
a
little
better.
A
You
know
probably
closer
to
three
or
four
years
ago
on
some
of
this
stuff,
and
then
you
know
as
but
we
were
doing,
kubernetes
right
and
and
we've
been
doing
it
for
quite
some
time
by
then
and-
and
so
it
was
really
that
was
the
inflection
point.
We
we
no
longer
have
to
convince
people.
Kubernetes
I
mean
it
won
right,
like
kubernetes,
is
a
project
that
is
a
de
facto
way
to
to
manage
containers
at
scale
right.
You
know
there
there's
several
there's
its
own
ecosystem
built
around.
A
If
any
of
you
have
ever
seen
the
cloud
native
compute
foundation
poster
with
all
the
projects
now
that
are
built
off
of
it.
It's
it's
awesome
to
see
right,
so
I
think
now
the
challenge
particularly
for
the
ecosystem
and
even
for
us
at
red
hat,
is
well
now.
Where
do
we
place
our
bets
right
and
and
when
I
think
about
the
ecosystem,
I
look
for,
if
I'm
thinking
of
isvs,
what
are
those
technologies
that
will
complement?
A
You
know
helping
secure
that
platform,
helping
make
it
more
stable,
more
manageable,
all
the
pieces
around
it
right.
We
don't
really
look
on
the
partner
side,
help
us
make.
You
know
core
kubernetes
better
right.
I
mean,
I
think
our
track
record
speaks
for
itself
there,
but
when
we
can
find
those
partners
that
really
can
enhance
the
value
of
it
and
it's
mutually
beneficial
in
that
way,
because
maybe
there's
customer
demand
for
it
it's
great
and
then
on
the
on
the
services
side
you
know.
A
A
To
me,
one
of
the
biggest
benefits
of
openshift
is
we're
consistent.
Actually,
that's
been
always
one
of
the
the
biggest
benefits
of
red
hat
is
we
are
literally
everywhere
and
we
we
treat
all
the
hyperscalers
as
first-class
citizens,
and
we
can
give
you
as
you
consume.
Our
technology
is
a
very
consistent
experience,
so
I
don't
have
to
worry.
Is
this
an
atari
2600
cartridge
or
a
nintendo
cartridge?
B
Yeah,
it's
always
it's
always
interesting.
When
you
look
at
the
you
know,
adoption
trend
of
technology,
you
get
a
certain
hype
and
then
there's
that
you
know
oh
well,
maybe
it's
matured.
Maybe
it's
gotten
boring
it's
good.
When
technologies
still
get
boring,
you
know
we
look
at
this
space.
I
had
mike
barrett
on
the
program
when
we
had
the
last
release
and
talked
about
like
oh
well,
we
went
from
four
releases
three
releases
a
year.
Things
have
slowed
down
right
and
mike's
like,
oh,
my
god.
Have
you
seen
our
road
map?
B
Have
you
seen
the
hundreds
of
things
we're
working
on?
You
know
we're
having
debates
inside
you
know.
We
spend
90
minutes
explaining
what
comes
in
a
new,
a
new
release
of
open
shift
and
we
can't
even
get
everything
in
that.
You
know
longer
period
because
you
know
hey.
Can
we
do
like
you
know
the
six
hour
marathon
of.
A
So
that
is
a
great
shameless
plug,
though,
for
openshift
tv
right,
you
know
we.
It
was
always
ironic
to
me
going
back
to
my
time
here
that
I'm
like
why
we're
open
source.
Why
are
we
hiding
our
roadmap?
We
should
just
do
it
for
the
world
at
any
time.
Right,
you
know,
and
so
that's
actually
been
great
to
see,
but,
like
you
said,
we
have
a
hard
time.
You
know
we're
both.
A
Security
of
openshift
so
yeah
we
well.
I
can
tell
you
right
now.
Obviously
we
we
have
the
stack
rocks,
acquisition
acs
now
and
we
that
is
matured
enough,
where
it's
it's
more
of
a
complete
part.
If
you
will
of
openshift,
you
know
it's
been
a
journey,
as
you
can
think
before,
but
even
before
acs,
I
I
just
I
hearken
back
to
my
se.
Linux
joke
right,
yeah,
but
folks
say
the
the
operating
system
doesn't
matter.
A
Doesn't
it
I
mean
at
the
end
of
the
day
we
were
securing
things
all
the
way
down
at
the
colonel
level.
Four
years
right,
you
know,
dan
walsh,
you
know
was
one
of
the
the
primary
engineers
that
created
that
thing
and
and
was
a
red
hatter
and
then
work
very
closely
with
the
nsa
and
other.
You
know,
agencies
that
are
three
letters
that
care
a
little
bit
about
security,
to
say
the
least,
and
so
for
us,
what
acs
even
became
was.
A
Yeah
and
so
security,
it's
interesting.
You
say
that
that
was
one
of
the
first
areas
that
we
looked
at
for
the
ecosystem
you
know
was:
was
we
really
wanted
to
to
make
sure
we
knew
what
we
have
I
mean
now
the
I
had
one
customer
tell
me
that
they
considered
the
new
sc
linux
or
security
context,
which
was
a
contribution
that
we
originally
made.
That
used
to
be
only
in
open
shift
but
commitment,
open
source.
We've
made
it
available.
A
It's
all
the
way
upstream
in
cube
itself
and
so
yeah,
but
it
what's
next
right
so
to
mike's
point
the
things
in
the
roadmap
really
are
about
enabling
all
these
things
on
top
of
kubernetes
and
around
kubernetes.
You
know,
and-
and
we
spend
a
lot
of
time
there
and-
and
I
know
I
work
closely
with
you-
know
our
partner
team.
You
know
we
have
a
tire
partner
team.
Remember
stephanie
cheers
she.
She
was
one
of
the
first
guests
on
this
show,
I'm
so
thankful
to
her
from
back.
B
All
right
so,
chris,
you
talked
a
little
bit
about
your
history.
You
talked
about
the
partner
piece,
maybe
bring
it
to
today.
So
you
know
you
you
the
reason
we're
actually
sitting
here
for
the
first
time
in
a
couple
of
years
you
brought
your
whole
organ,
which
disclaimer
I
report
to
chris.
So
you
know
I
know
we
were
all
first
of
all
thrilled
to
like
you
know,
be
like
oh
wait,
I'm
not
hearing
you
through
your
super
nice
microphone
or
you.
B
A
So
the
the
great
thing,
first
of
all,
I
agree
with
you
man,
it
it
just
it.
It
was
so
nice
to
party
like
it
was
2019
again,
I
you
know
to
actually
be
able
to
see
people
and
we
got
a
lot
of
work
done
as
well.
I
think,
but
when
I,
when
I
think
about
what
our
role
in
the
ecosystem
is
it's
to
continue
to
be
that
push
right,
we
don't
sit
in
the
organization
as
part
of
the
the
cto's
office
right,
that's
really
forward-looking
and
research,
but
we
do
keep
an
eye
right.
A
Now
you
know,
I
don't
have
to
explain
to
most
techies
and
admins
what
a
pod
is
anymore
right
and
what
yeah
any
of
these
basics
are,
and
so
now,
where
we
want
to
fit,
is
what
can
we
do
to
a
enable
the
partner
ecosystem
working
through
the
other
tools?
I
mentioned
stephanie
cheers
organization
because
she's
got
an
army
of
people
to
help
with
some
of
this,
but
we
always
want
to
try
to
help
be
the
canonical
source
on
our
team
to
give
them
the
information
right.
A
We
we
sit
with
product
management
and
we
sit
with
engineering
and
we
like
to
take
those
things
and
you
know
make
them
more
consumable.
You
had
mike
barrett
on
and
as
you're
well
aware.
I
think
mike,
I
feel
like
I'm
being
prone
to
hyperbole
here,
but
I
feel
like
sometimes
there's
300
product
managers
right
and
so
bringing
all
of
that
together
and
understanding
and
prioritizing
that's
really
our
job
right.
Can
we
make
it
consumable
to
the
masses,
particularly
the
technical
masses,
going
back
to
again
the
history
of
openshift
tv?
A
Is
we
wanted
to
to
give
a
voice
potentially
because
it
is
a
live
stream?
Not
a
recorded
webinar
to
folks
to
really
engage
with
some
experts,
and,
and
so
as
far
as
today,
what
we're
really
driving
the
ecosystem,
I
feel
like
is
hey
we're
here.
We've
done
this
now
for
a
really
long
time
tell
us
what
you
have
like
what
is
what
is
the?
What
is
your
value?
What
do
you
do
for
your
business
and
how
are
you
making
your
business
successful?
A
Let
us,
instead
of
hey,
do
something
with
us
and,
let's
just
do
it
together.
Let's
work
and
help
make
us
both
more
successful.
Like
it's
an
actual
partnership,
I
mean
I'll,
be
fully
transparent.
There
were
always
times
that
it
would
feel
like
one
partner
was
a
customer
and
the
other,
the
vendor,
not
an
actual
partnership,
and
I
think
now
what's
happening,
is
they're.
True
partnerships
going
forward.
B
All
right
well,
chris,
I
think
that's
a
great
place
to
leave
it.
We've
got
lots
of
the
openshift
tv.
You
know,
andrew
sullivan,
sully
ask
an
openshift
admin.
I'm
on
your
team,
doing
some
of
the
thought
leadership
executive
interviews
here
within
the
cloud
so
I'll
give
you
the
final.
You
know
final
word
here.
A
Yes,
for
me,
success
will
be
defined,
so
matt
hicks
actually
asked
me
this
question
randomly.
I
think
we
were
in
orlando
at
a
tech
exchange,
internal
talking
about
training,
our
internal
essays,
and
he
just
he
asked
me.
He
said
what
does
success
look
like
to
you
and
even
the
cheshire's
asked
me
the
same
thing
and
I
give
them
both
the
same
answer.
It's
when
we
actually
don't
have
to
talk
about
openshift.
A
Just
like
honestly,
we
like
to
talk
about
red
hat
enterprise
linux,
but
people
just
presume
it's
there
right
and
it's
there
and
it's
making
it
work,
and
so
when
we
think
about
the
partner
ecosystem
and
growing
it
and
for
mutual
customers,
we
want
to
be
everywhere.
I
mean
we're
in
the
space
station.
I
mean
come
on
like
how
many
companies
have
their
software.
In
you
know
the
international
space
station.
B
I
love
that
is,
if
you
check
out
the
in
the
clouds
playlist,
you
will
find
that
chris.
Thank
you.
So
much
awesome
to
be
here
with
you
in
person
to
see
everyone.
We
thank
you,
of
course,
for
joining
regularly
scheduled
programming
every
two
weeks.
11
a.m.
On
thursday,
I'm
stu
miniman.
As
always
thank
you
for
joining
us
on
your
journey
in
the
clouds.