►
Description
OpenShift Commons Gathering
Milan Italy 2019
Speaker: Brian Gracely (Red Hat)
Title: Unified (Open) Hybrid Cloud Vision
A
Good
morning,
a
couple
weeks
ago,
well
couple
months
ago,
Diane
said:
I
need
you
to
go
to
Milan
I.
Need
you
to
go
and
present
to
Milan
and
I
was
like
a
Diane.
Anything
you
want.
I
am
happy
to
do
that,
for
you.
I
will
do
that
for
you
anywhere.
You
want
me
to
go
and
my
daughter's
asked
me
where
I
go
and
I
said
my
friend
Diane
wants
me
to
go
to
Milan
and
present
and
they
said
dad
it's
Fashion
Week,
my
daughter's
teenaged
daughters.
They
said
it's
Fashion
Week.
They
said
it's
really
important.
A
You
need
to
be
really
plugged
in
and
I
said.
Honey
I
am
a
short
pudgy,
not
that
attractive.
Looking
man,
they
don't
want
me
in
Fashion
Week.
They
said
dad.
You
have
to
be
prepared
for
Fashion
Week.
This
is
not
a
fashion
week
audience,
but
thank
you
for
coming.
It's
great
to
be
here.
I've
had
a
chance
to
speak.
It
I
think
almost
every
one
of
these
since
way
back
in
the
very
beginning
when
it
was
about
two
rows
of
people
or
what
would
be
the
equivalent
of
that.
A
A
Ultimately,
you
know
when
we
talk
about
hybrid
cloud.
I
think
it
boils
down
to
a
lot
of
real,
simple
things,
maybe
not
so
much
buzzwords,
but
basically
everybody
sort
of
walks
in
the
room
and
they
go
look.
I
have
two
problems:
I'm
trying
to
and
to
a
certain
extent,
I'm
trying
to
solve
them.
At
the
same
time,
it's
the
classic
sort
of
you
know
two
variable
problem
you
know
one
is.
My
business
would
like
to
create
growth
we'd
like
to
move
into
new
areas,
we'd
like
to
take
on
new
opportunities.
A
We
want
to
drive
profitability
whatever
that
might
be
and
at
the
same
time,
we're
also
trying
to
figure
out.
How
do
we
prioritize
things
where
we
may
want
to
take
cost
out
of
the
system
we
may
want
to
reduce
costs.
We
may
want
to
automate
things
and
ultimately,
we're
always
sort
of
you
know
this
small
bird
here
trying
to
figure
out
which
one
do
I,
which
one
do
I
focus
on
and
in
some
cases
you
come
in
you
go.
A
You
know
what
my
job
is
all
about:
growth,
I,
don't
care
about
saving
cost
and
that's
great
there's
a
place
in
this
conversation
for
you
and
there
are
others
in
the
room
who
go.
Look.
We
have
to
take
20%
out
of
the
set
amongst
all
the
other
fancy
things
you're
going
to
tell
me:
I
still
need
to
take
20%
of
the
system
or
whatever.
That
number
is
and
there's
room
in
this
conversation
for
you
as
well.
So
let's
break
this
down.
A
A
But,
more
importantly,
it's
about
the
realization
that
if
we
believe
for
any
reason
that
we
have
all
the
answers
to
solve
your
problems,
we're
out
of
our
mind-
and
so
it's
interesting
to
us
to
see
more
and
more
of
the
industry
start
to
sort
of
embrace
open
but
open
in
sort
of
a
what's
in
their
best
interest.
Open
right,
open
in
the
sense
of
like
yes,
we
contribute
to
a
project,
but
it's
our
project
right
and
we
sort
of
believe
in
this
idea
that
open
around
open,
hybrid
cloud
is
about
being
open
all
the
time.
A
A
Is
this
idea
that
they're
going
to
provide
me
a
stable
baseline
of
technology
they're,
going
to
help
make
sure
that
you
know
kind
of
the
latest
things
that
are
in
Diane's
diagrams
are
going
to
get
into
these
platforms
that
we
use,
but
I
don't
have
to
rely
on
them?
They're,
not
my
bottleneck
and
for
us,
that's
a
really
big
deal.
A
That's
a
part
of
not
only
our
culture,
but
we
think
it's
something
that
that
attracts
people
to
working
with
us
and
with
the
communities
that
we
work
in
now
for
those
of
you
in
the
back
I
want
you
to
cover
one
of
your
eyes
and
read
from
the
left,
and
just
tell
me
what
these
are.
This
is
this
wonderful
diagram
that
the
CNC
F
puts
together?
How
many
of
you
have
ever
seen
this
before
you've
heard
of
this
thing,
so
the
cloud
native
computing
foundation
is
a
great
organization.
A
But
you
know
sort
of
gives
you
a
sense
of
what's
going
on
out
there
and
it's
also
something
where
you
go.
Oh,
my
goodness!
What
in
the
world
do
I
pick?
What
do
I
learn?
Where
do
I
spend
my
free
time?
How
do
I
figure
out
which
of
these
things
like,
for
example,
of
the
I,
don't
know
12
or
so
API
gateways,
which
one
should
we
use?
Which
project
is
viable,
which
one
has
the
best
features,
which
one
is
some
crazy
idea
out
of
out
of
a
garage
and
which
one
is?
A
Is
the
next
thing
and
what
we
try
and
do
as
Red
Hat?
Is
we
sort
of
we're
kind
of
an
early
warning
system
sort
of
a
canary
in
the
coalmine?
If
you
will
of
saying
look
we're
going
to
put
the
effort
in
to
to
live
in
these
communities
to
live
in
these
projects,
to
put
people
into
the
projects
to
work
on
them
and
hopefully
provide
some
sanity
right,
provide
some
sort
of
enterprise
perspective
on
where
these
things
are
going,
and
not
every
single
one
of
these
by
any
means
we'll
get
into
openshift.
A
Many
of
these
won't
make
it.
That's
the
reality
of
our
industry,
but
many
of
these
will
get
better
because
we
bring
your
voice
to
how
we
contribute
to
these.
You
give
us
your
feedback,
on
which
one
of
these
you
would
like
to
see,
prioritized
and
OpenShift,
or
better
integrated
with
something
else
you're
doing,
but
this
is
kind
of
the
reality
we
have
it's,
it's
thousands
and
thousands
of
projects
and
at
some
point
you
have
to
whittle
that
down
and
narrow
that
down
into
something
that
you
can
use
for
your
business.
A
That's
the
beauty
of
open
right.
It's
unlimited
amounts
of
innovation,
right
tons
and
tons
of
venture
capital
are
going
into
here.
So
new
ideas
can
come
to
market,
but
then
the
reality
is,
you
have
to
figure
out.
How
do
we
use
those
for
ourselves
right
and
that
yin
and
yang
is
just
like
that
little
bird
you're
trying
to
figure
out
what's
important,
what's
cool
and
exciting
and
which
one
makes
sense
for
us?
So
what
we
try
and
do
is
a
part
of
that
beyond
the
technology.
A
Is
we
try
and
make
sure
that
when
you
need
to
go,
learn
things
we
make
that
as
simple
as
possible?
So
for
things
like
learned,
OpenShift,
calm,
which
have
any
of
you
ever
been
to
learned,
OpenShift
calm,
so
write
that
down
easy
to
remember
totally
free
ways
of
going.
I
would
just
like
to
learn
something
about
this
stuff.
I
learned
today,
I
want
to
learn
about
containers.
I
want
to
learn
about
operators.
I
would
like
to
play
with
whatever
it
might
be,
and
oh
by
the
way,
maybe
I
don't
have
an
environment.
That's
fine!
A
You
need
a
laptop.
You
know
browser
fully
sort
of
hands-on,
interactive
self,
driven
learning
modules.
These
things
are
available
to
you,
because
we
want
to
make
sure
that,
as
new
cool
stuff
comes
along,
whether
you're
going
to
put
them
into
into
production
or
into
testing
in
your
environment.
Today,
you
still
want
to
get
ahead
of
the
learning
curve
right.
Make
yourself
the
smartest
person
in
the
room.
The
other
thing
that
we've
invested
in
around
open
is
very
much.
This
idea
that,
while
the
technology
is
very
cool,
kubernetes
is
neat
and
serviced.
A
Mesh
is
neat
and
K
native
is
neat
and
blah
blah
blah.
At
some
point,
you
have
to
figure
out
like
we're
a
traditional
organization.
You
talked
about
this
idea
of
blameless
post-mortems.
My
boss
has
no
idea
what
the
word
blameless
means.
My
boss
loves
the
word
blameless
blame
ful.
He
likes
to
point
the
finger
at
things.
How
do
we
take
this
idea
of
doing
stuff
like
that?
How
do
we
do
DevOps,
which
is
this
idea
that
we're
just
gonna
keep
moving
things
along?
We're
gonna
keep
integrating
things.
We
don't
necessarily
have
to
have
outage
windows.
A
How
are
we
gonna
do
that,
and
so
we've
spent
a
lot
of
time.
Investing
in
these
things
that
we
call
Red,
Hat,
open
innovation,
labs
which
again
are
ideas
of
how
do
we
help
you
not
only
learn
the
technology
but
learn
sort
of?
How
do
we
live
in
these
sort
of
cultures
of
rapidly
building
software
of
dealing
with
distributed
systems
that
are
going
to
fail?
How
do
we
you
know?
A
How
do
we
deal
with
those
and
they're
things
that
not
only
you
can
come
and
work
with
us
directly,
but
we
come
out
and
work
with
you
as
well,
so
we've
tried
to
bring
this
idea
of
learnings
that
we
get
from
the
community
put
them
into
systems
that
can
be
kind
of
packaged
up
if
you
will
and
go
and
work
with
you
both
on
the
technology
side
in
the
culture
side?
Ok,
so
that's
kind
of
the
hybrid
that
the
open
piece
of
it.
So
what
about
hybrid?
A
So
when
we
think
about
hybrid,
if
you
go
back
a
decade
and
I
was
involved
with
this
a
decade
ago.
Originally,
when
we
talked
about
hybrid
as
vendors,
it
was
really
kind
of
a
reactionary
thing
to
when
the
public
cloud
came
out
and
we
all
went
uh-oh
if
everybody
likes
the
public
cloud.
Essentially,
public
cloud
is
bypassing
IT
and
that's
not
necessarily
a
good
thing.
So
we
will
create
this
thing
that
says
hey.
A
Why
can't
you
just
do
what
you
can
do
on
premises
somewhere
in
the
public
cloud
or
somewhere
else,
and
all
will
be
good
and
we've
gone
through
about
10
years
or
so
of
gyrations
of
what
does
that
really
mean
in
reality,
and
is
it
based
on
you
know
these
Hardware
stacks?
Is
it
based
on
software
err?
Do
we
have
a
standard
we
can
use
for
getting
there
and
I
think
throughout
that
iteration?
A
The
other
thing
we
sort
of
realized
is
that
most
of
your
businesses
in
one
way
shape
or
form
ultimately
work
in
some
sort
of
hybrid
mode
right,
so
you've
got
pieces
of
what
you
do
that
tend
to
be
sort
of
physical
or
direct.
The
way
you
interact
with
the
marketplace,
there's
pieces
of
it
that
are
going
to
be
sort
of
digital
engagement,
right
you're,
interacting
with
your
customers,
but
it's
through
some
sort
of
third-party
interface.
A
It's
ride-sharing,
it's
you
know
mobile
app
and
the
third
part
is
you're
going
to
deal
with
some
sort
of
marketplace
or
API,
there's
very
little
that
you
do
directly
anymore
a
lot
of
it's
through
these
things.
So
if
we
look
at
this
as
an
example,
if
I
take
banking
or
finance,
for
example-
yes,
there
are
still
bank
buildings,
there
are
still
branch
offices,
there
are
still
ATMs
right,
there's
still
a
physical
aspect
of
what
we
do,
but
there's
also
marketplaces
that
we
interact
with.
A
There
are
also
you
know,
sort
of
digital
internet
interactions
that
we
have
mobile,
banking
and
so
forth.
Those
things
are,
the
reality
is
what
we
do
and
as
a
business
you're
sitting
there
saying
which
one
of
these
do
we
vest
more
in
which
one
of
these
do
we
have
a
competitive
advantage
in,
and
the
realities
is
the
way
that
you're
going
to
deliver.
A
Applications,
deliver
computing,
deliver
security
and
so
forth,
isn't
necessarily
one-size-fits-all
and
it
sort
of
backs
itself
into
this
idea
that
having
an
ability
to
be
hybrid,
whatever
percentage
that
might
be,
and
the
ability
to
say
hey,
the
business
might
change
that
percentage
over
time
becomes
really
important
and
we
can
kind
of
apply
this
to
other
industries
as
well.
We
can
apply
it
to
the
car
buying
process,
whether
you're
going
to
a
dealership
you're.
You
know
ride-sharing
you're
buying
through
some
sort
of
marketplace.
A
You
begin
to
think
of
it
as
the
way
that
you're
going
to
build
those
systems
behind
the
scenes
are
going
to
have
to
have
some
fluidity
in
terms
of
what
you're
dealing
with,
and
we
see
this
in
lots
of
different
markets.
It's
not
just
location
matters.
It's
not
just
the
physical
thing
matters,
but
also
things
like
you
know,
is
the
people
that
I'm
working
with
you
know.
Ten
years
ago,
gdpr
didn't
exist.
We
didn't
have
to
think
about
locality
in
that
sense,
five
years
ago,
Amazon
didn't
own
grocery
stores.
A
So
if
you're
a
grocery
store
five
years
ago,
maybe
you
said:
hey
Amazon's,
fine,
where
I'll
work
with
and
now
you
say
well,
do
I
want
to
pump
my
profits
into
AWS,
because
that
now
competes
directly
against
me
and
the
dynamics
of
how
we
deal
with
the
industry
gets
sort
of
different
right
and
those
things
will
continue
to
evolve
over
time.
So
the
hybrid
piece
of
this
is
you're.
Gonna,
walk
away
going.
I
know
that
some
sort
of
change
in
my
business
is
coming.
A
I,
don't
necessarily
know
when
I
don't
necessarily
know
the
impact
of
it
and
you're
always
sort
of
balancing
that
against
what
do
I
need
to
do
today.
What's
my
immediate
thing,
do
I
invest
in
the
future?
What
do
I
need
to
do
today
and
hybrid
is
essentially
that
call
it
an
insurance
policy
call
it
a
flexibility
aspect
that
you're
saying
I
know
these
are
the
dynamics
of
what
I
have
to
deal
with,
but
do
I
have
the
flexibility
and
the
architecture
I'm
building
to
do
that
or
to
do
that
in
the
future.
A
So
what
is
cloud
all
right,
dummy,
I'm,
gonna,
try
and
explain
cloud
to
all
of
you,
smart
folks,
all
right,
so
I'm
gonna
give
you
cloud
in
the
sense
of
what
will
you
sort
of
learned
over
the
last
five
years,
so
OpenShift
has
been
a
platform
that,
for
many
of
you
has
been
around
for
a
number
of
years.
How
many
of
you
remember
openshift
before
it
was
kubernetes,
where
any
of
you
involved
with
that
back
in
version
2?
Okay,
a
few
of
you
how
many
of
you
were
open?
A
She
actually
used
open
shift
today
as
a
version.
Three
or
something
okay
and
then
some
that
are
new,
so
we've
learned
quite
a
bit
about
this.
We've
run
OpenShift
as
a
managed
cloud
platform.
Over
the
years
we've
delivered,
manage.
We've
delivered
open
shift
as
software
that
runs
and
things
that
you
can
run
yourself,
but
that
they're
run
in
lots
of
different
places
and
there's
been
a
lot
of
learnings
that
we've
gotten
having
lived
in
both
of
those
world
and
having
to
live
in.
What
does
it
seem?
What
is
it
like
to
run
and
manage
software?
A
That's
in
corporate
data
centers
that
are
essentially
snowflakes.
What
does
it
like
to
run
them
in
public
clouds
that
are
very
API
driven
and
then
start
to
realize
that
every
public
cloud
is
a
little
bit
different,
as
your
storage
is
a
little
bit
different
than
AWS
storage,
it's
different
than
Google
storage
and
so
on
and
so
forth,
and
so
we've
learned
a
lot
of
things.
We've
learned
that
not
every
public
clouds,
the
same
they're
fantastic
and
what
they
do,
but
they're
not
exactly
the
same,
and
so
somewhere.
Somebody
has
to
figure
out.
A
A
We've
learned
that,
in
order
to
be
successful
to
have
a
successful
platform
that
people
want
to
come
back
to,
you've
got
to
be
able
to
work
with
a
lot
of
different
applications
right,
and
this
was
one
of
the
learnings
that
we
had
from
the
early
kubernetes
days
where
everything
was
gonna,
be
cloud
native
and
everything
was
gonna,
be
stateless
and
at
some
point
somebody
raised
their
hand
and
said
where's.
The
state
go
like
how
do
I
deal
with
the
data
part
of
this?
A
It
can't
all
be
stateless,
and
so
we've
had
to
learn
from
that
and
now
today
we're
going
to
talk
about
AI
and
ml
and
a
whole
bunch
of
other
things
running
on
top
of
kubernetes.
That
five
years
ago
you
never
would
have
thought
of.
It
was
just
gonna,
be
a
bunch
of
stateful
web
apps
that
we're
gonna
scale
like
Google,
okay
and
there's
a
lot
of
things
that
we've
learned.
We've
learned
that
inconsistency
drives
up
cost
we've
learned
that
inconsistency
drives
up
complexity.
The
integrations
are
complicated.
To
maintain
people.
Ask
us
all
the
time.
A
You
know
why
can't
I
just
build
this
stuff
myself
right.
It's
just
kubernetes,
it's
just
out
there
for
free,
and
then
you
go
back
to
that
slide
a
few
pictures
ago.
That
was
the
eye
chart.
You
go.
Oh
yeah,
I'm
gonna
integrate
a
whole
bunch
of
those
things
and
oh
yeah.
It
comes
out
every
three
months
and
oh
yeah,
it's
not
always
backwards
compatible.
So
how
do
I
deal
with
that?
A
So
we've
learned
a
whole
bunch
of
things
and
from
those
learnings
we've
kind
of
boiled,
a
lot
of
those
things
down
to
a
couple
of
basic
things
right.
We
know
that
as
much
as
possible,
we
have
to
automate
operations
and
we
can't
necessarily
rely
on
just
some
tool
to
do
that.
For
us
we
kind
of
have
to
bake
that
into
the
architecture.
We
know
that
standards.
A
Interoperability,
Portability
are
incredibly
important
to
you
right,
there's,
a
reason
why,
even
though,
as
Diane
mentioned
openshift
does
things
above
and
beyond
kubernetes,
everything
that
we
do
is
first
and
foremost
contributed
to
kubernetes
and,
first
and
foremost,
make
sure
that
doesn't
break
anything
in
kubernetes,
so
that
when
Amadeus
or
SIA
or
anybody
else
comes
along
and
says,
I
have
an
application.
I
want
to
build,
they
know
in
the
back
of
their
mind,
this
will
just
work
on
on
kubernetes.
The
OpenShift
piece
just
makes
it
easier
for
us
to
manage
right.
A
So
we
have
to
make
sure
we
do
that.
We
have
to
make
sure
that
as
much
as
possible,
we
make
it
such
that
things
are
on
demand
right,
whether
you
deliver
those
on
demand,
they're
built
into
the
platform,
is
on
demand,
but
also
that
you
can
get
to
the
marketplace
of
ideas
and
technology.
That's
out
there
make
that
as
simple
as
possible.
You'll
see
those
things
integrated
in
the
platform.
We
want
to
make
sure
that
it's
continuously
secure.
A
Nobody
wants
to
be
on
the
front
page
of
The,
Wall,
Street
Journal
or
your
local
paper
on
the
front
page
of
hacker
news
going
that
dummy
didn't
integrate
that
feed
that
that
CVE.
We
want
to
make
sure
that
there's
a
mechanism
to
keep
the
platform
continuously
secure
sort
of
secure
by
default
and
then
continuously
secure
and
then
finally,
we
want
to
make
sure
that
it
supports
a
broad
set
of
applications,
and
there
are
lots
of
other
considerations
that
we
find
a
lot
of.
A
A
So
this
is
sort
of
our
vision
for
going
with
open
shift4
we've
always
delivered
open
shift.
We've
always
believed,
even
though
kubernetes
and
containers
are
sort
of
at
the
core
of
what
we
do.
We've
always
believed
that,
in
order
for
us
to
help,
customers
be
successful
in
deploying
applications
and
ultimately
making
their
business
better,
which
is
the
business
that
you're
in
we're
in
the
business
of
building
platforms
you're
in
the
business
of
of
satisfying
your
customers
in
various
ways
we
needed
to
sort
of
deliver
it
as
a
complete
Pat,
complete
Pat
platform.
A
That
means
we
package
a
lot
of
things
together,
but
it
also
means
we
integrate
a
lot
of
things.
So
you'll
always
see
us
sort
of
lay
this
out
as
somewhat
of
a
stacked
diagram,
but
think
about
this
is:
is
the
entire
experience
from
automated
infrastructure,
secure
infrastructure
cluster
services
to
allow
you
to
scale
this
application
services
to
allow
you
to
bring
a
lot
of
different
types
of
applications
to
it
and
then
developer
services
in
order
to
allow
your
developers
to
just
write
code,
continue
to
write
code
and
be
successful
doing
that?
A
A
The
first
is
because
we're
talking
about
the
enterprise
and
because
we're
talking
about
large-scale
organizations,
we've
got
to
be
able
to
bring
the
power
of
open
shift
as
a
cluster
as
a
place
where
you
run
this
into
a
more
holistic
view
of
things,
and
so
you
will
see
us
do
quite
a
bit
of
work
around
essentially
federating
your
clusters,
regardless
of
where
they
run
it's
one
of
the
powers
of
OpenShift
is
you're,
going
to
run
consistently
everywhere.
You're
going
to
see
us
deliver
a
more
sophisticated
way
of
doing
software
updates.
A
One
of
the
great
challenges
that
people
have
told
us
with
earlier
versions
of
OpenShift
was
it's
great
that
you're
giving
me
new
functionality,
it's
great
that
the
community
is
moving
fast.
We
are
an
enterprise,
we're
not
used
to
doing
updates
every
three
months.
You
better
make
this
simpler
for
us.
We
would
like
the
power
of
what
comes
out
of
kubernetes,
but
we
don't
necessarily
like
the
pain
of
it.
So
you'll
see
a
lot
of
work
that
goes
on
about
making
the
update
process
more
simplified.
That
also
allows
us
to
get
a
little
more
information
about.
A
What's
going
on
with
these
things
right,
we
call
it
telemetry,
we'll
talk
about
it
more
throughout
the
day,
but
I'll
give
you
just
one
sort
of
thing
to
keep
in
the
back
of
your
mind.
So
if
you
start
playing
with
the
new
version
of
OpenShift
OpenShift
4,
so
if
you
go
out
to
try
dot
OpenShift
comm,
you
can
go
play
with
the
bits
at
any
point
in
time.
One
of
the
things
is,
it
says:
hey.
A
We
are
going
to
collect
a
little
bit
of
telemetry
information
about
what's
going
on
in
your
cluster,
and
none
of
that
is
the
data
that
you
deal
with.
None
of
it
is
things
that
you
have
to
be
worried
about
in
terms
of
privacy.
It's
basically,
where
are
they
running
it?
So
we
have
some
sense
of
where
you
want
to
run
the
platform,
but
it
also
gives
us
a
sense
of
like
what's
the
health
of
the
things
running
under
the
covers
in
the
platform.
A
Just
a
quick
data
point,
so
we
fix
hundreds
of
bugs
every
release
that
go
in.
We
implement
dozens
of
CVEs
throughout
20%
over
the
lens
over
the
last
just
a
couple
of
months,
20%
of
the
CVEs
and
bugs
that
we
have
found
have
come
via
that
automated
telemetry.
So
we
Abell
now
in
working
sort
of
cooperatively
with
you
with
your
clusters
to
make
the
product
better
on
a
more
automated
basis
and
that's
something
we
want
to
be
able
to
deliver
to
you.
We
know
the
software
is
moving
quickly.
We
know
the
innovations
coming
quickly.
A
A
What's
going
on,
this
touches
the
security
team,
it
touches
networking
and
storage
and
monitoring
and
logging
and
all
those
things,
and
so
there
has
to
be
elements
of
this
that
make
the
balance
between
building
software
faster
and
more
secure
and
running
the
platform,
and
so
there's
a
number
of
things
that
we've
been
doing
around
this,
that
there
go
one
of
them
that
we'll
talk
about
a
lot
today.
How
many
of
you
heard
of
this
concept
called
operators
right?
A
How
many
of
you
heard
of
Amazon,
RDS
or
Amazon
s3,
something
as
a
service
right
operators
is
in
essence
the
instantiation
of
software
as
a
service
that
you
run
in
your
platform,
we
want
to
make
anything
that
you
run
internal
to
the
platform
and,
more
increasingly,
the
software
you
run
on
top
of
the
platform,
not
only
be
highly
automated,
but
have
a
lifecycle
built
around
it
and
be
sort
of
kubernetes
native.
If
you
will,
in
terms
of
understanding
how
to
take
advantage
of
the
advanced
things
that
happen.
A
So
we've
been
doing
a
lot
of
work
around
that
you
can
find
that
as
Diane
mentioned
out
an
operator
hub,
that's
the
community
place,
so
you
can
find
this
operator
hub.
Do
all
of
that
gets
embedded
now
into
openshift
4.
So
all
the
things
going
on
in
the
community,
around
operators
and
you'll,
see
it's
becoming
very
broad,
now
become
just
part
of
your
marketplace
that
you
can
offer
to
your
internal
teams.
A
The
second
part
is
we're
giving
a
ton
more
visibility
to
the
operational
side
of
the
platform,
so
whether
it's
metering,
monitoring,
chargeback
cluster
health,
again
I
talked
about
telemetry.
Your
operational
teams
will
have
much
more
visibility
as
to
what's
going
on,
and
this
is
again
us
integrating
things
like
prometheus
graph
on
ax
key
ollie,
also
jäger,
all
sorts
of
things,
but
again
making
this
things
that
are
just
natively
built
into
the
platform.
A
Things
like
serverless,
K
native
Williams
gonna
talk
more
about
this.
You
know
the
ability
to
build
functions
as
a
service
right.
The
platform
has
been
containers
as
a
service.
It's
been,
it
does
sort
of
platform
as
a
service.
If
you
will
it
also
now
embeds
functions
as
the
service
is
essentially
a
first-class
feature
of
the
platform
as
well.
We
want
you
to
be
able
to
bring
that
broad
set
of
applications
to
the
platform,
and
we
also
want
you
to
be
able
to.
A
You
know
build
around
the
idea
that
it's
not
just
about
the
application,
but
it's
about
the
pipeline
for
that
application.
How
do
we
build
it
securely
and
as
kubernetes
evolved,
then
people
better
understand
kubernetes?
How
do
we
start
to
build
those
pipelines?
Our
software
pipelines,
our
CI
CD
pipelines
around
natively,
the
capabilities
of
the
platform,
so
you
will
see
more
kubernetes
native
CI,
CD
pipelines
becoming
a
native
part
of
the
platform,
as
well
so
again
trying
to
give
your
operations
teams
the
tooling
and
visibility
they
need
to.
A
What's
going
on
and
begin
to
give
your
developers
the
foundation
for
a
lot
of
flexibility
in
the
platform
now?
Finally,
in
terms
of
experience
for
developers,
you
know
we've
always
we've
always
had
this
yin
and
yang
in
terms
of
the
development
experience
of
openshift
there
is,
there
is
a
terminology
out
there
called
opinionated
and
people
will
say
well.
I
would
like
an
opinionated
experience.
I
would
like
my
developers
to
all
sort
of
conform
to
this
one
way
of
building
software.
A
It
was
very
much
the
way
that
when
we
were
doing
things
in
the
past
days,
so
when
it
was
has
openshift
open
version,
two
Cloud
Foundry
did
this
Heroku
stun
this
for
a
while
we're
going
to
give
you
specific
guardrails
for
your
developers
as
long
as
they
stay
within
those
guardrails,
it
will
be
an
incredible
experience
and
you
can
go
from
there.
The
great
part
about
that
is,
you
can
train
your
developers
and
you
can
build
tooling
around
one
experience.
A
The
downside
of
that
is
as
soon
as
you
want
to
do
anything
outside
of
those
guardrails
or
that
box
things
sort
of
break
right,
and
so
we've
always
sort
of
come
back
to
this
mantra
that
we
want
to
be
flexible
for
developers.
We
want
to
be
opinionated
in
certain
ways
and
we
want
to
be
flexible
in
certain
ways,
and
so
what
you've
seen
us
do
over
time
is
we've
sort
of
said.
A
A
I
just
want
you
to
plug
into
the
things
that
I
love,
so
vs
code
and
JetBrains
and
others
we
can
plug
into
those
as
well
and
then
more
and
more
we're
beginning
to
see
this
sort
of
trend
called
get
ops
where
people
say
you
know
what
everything
should
live
and
get
gets
my
single
source
of
truth
and
I'd
like
you
to
drive
all
of
the
interactions
through
get
and
we're
beginning
to
work
around
that
space
as
well.
There's
some
very
interesting,
tooling,
that's
coming
there!
A
So
from
a
developer
perspective
and
we're
gonna
talk
about
this
more
throughout
the
day,
we've
always
had
the
mindset
that
your
developers
are
all
going
to
be
a
little
bit
unique
or
company.
The
company
they're
gonna
be
a
little
bit
unique.
We
want
to
be
able
to
give
you
opinionated
views
on
that
in
certain
lanes,
but
we
also
realized
that
you're
going
to
have
developers
that
are
comfortable
with
the
tools
they're
comfortable
with,
and
we
don't
want
to
limit
them
from
being
able
to
do
that.
A
So
you
will
see
us
sort
of
have
multiple
developer
experiences.
The
end
goal
is
ultimately
build
code.
Push
it
through
push
it
through
automated
pipelines.
Automated
testing
get
it
into
the
platforms
that
can
be
highly
automated,
but
the
path
to
get
there
the
sort
of
supply
chain
to
get
there
sometimes
they'll,
be
a
little
bit
different,
depending
on
what
you're
trying
to
drive
for
your
developers.
So
with
that
I'm
gonna
kind
of
wrap
it
up
today.
For
my
first
talk,
I'll
be
around
all
day.
A
If
you
want
to
ask
questions,
but
the
thing
that
I'll
ask
you
and
I'll
kind
of
leave
this
as
an
open-ended
question
as
you're
thinking
about
your
journey
is
you're.
Thinking
about
what
you're
trying
to
build
is
you're
trying
to
think
what
you're
learning
today,
where
are
you
when
you
come
in
the
room?
A
There's
going
to
be
a
ton
of
really
interesting
information,
you're
gonna
learn
from
the
development
teams
that
are
building
this
you're,
going
to
hear
from
some
people
that
have
been
working
with
us
for
a
number
of
years
and
some
that
are
very
new
take
advantage
of
it.
This
is
a
great
chance
to
learn
the
person
next
to.
You
may
have
five
years
of
experience
of
things
that
you
want
to
learn
about.
Like
Diane
mentioned,
we
hope
we're
giving
you
a
platform
that
is
really
robust.
That
helps
solve
your
needs.