►
Description
Bringing Cloud Native Innovations into the Enterprise
Fueled by cloud, cloud-native apps are becoming commonplace across enterprises of all sizes. As these organizations invest in their people and process to enable Cloud Native technologies and look to the cloud to deliver business value, adopting collaborative and innovative open source strategy has become a key factor in their success.
All this open source success does not happen in a vacuum. In this session, Red Hat’s Chris Wright will highlight how the CNCF is helping to drive innovation in order to bring a wave of modern open source cloud native portfolios to the enterprise by ensuring industry collaboration on common code bases, standardized APIs and interoperability across multiple open hybrid clouds. Together with the help of the CNCF, Red Hat is helping to drive the development and ensure environmental consistency from the developer laptop to the hybrid and multiple footprint clouds that enterprise are deploying today.
In this closing keynote, Red Hat’s Chris Wright will talk about how the CNCF’s cross-industry collaboration initiatives is driving is the success of one of the first open source cloud native enterprise portfolios to emerge, Red Hat’s OpenShift Container Platform.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
I
also
wanted
to
thank
you
know
the
cnc
f
for
coming
together
and
and
pulling
together
this
this
day,
which
is
the
beginning
of
a
long
journey
that
we're
on
building
this
community
around
understanding
what
it
means,
as
you
saw
on
the
panel
earlier
today,
we're
still
figuring
out
what
it
means
to
build
infrastructure
and
deliver
cloud
native
apps.
So
I
wanted
to
talk
to
you
a
little
bit
today
about
bringing
these
kind
of
the
innovations
behind
the
technologies
or
bringing
this
technology
into
the
enterprise.
Something
that
we
do
at
Red.
A
Hat
is
what
we
focus
on
servicing
our
enterprise
customers
so
see.
If
I
can
operate
the
the
clicker,
you
know
you
hear
a
lot
about
disruption
and
every
you
know
software
is
eating
the
world
and,
more
importantly,
open-source
software
is
eating
the
world,
and
you
know
what
that
means.
Two
different
kind
of
of
enterprises
in
the
industry
on
a
certain
level.
A
People
are
just
learning
how
to
become
software
companies,
so
this
is
kind
of
a
lengthy
quote
from
the
CIO
at
Ford
forge
not
some
somebody
you
would
immediately
think
of
as
a
software
company,
but
they're
from
a
infrastructure
IT
perspective,
they're
really
refocusing
themselves
to
think
about
the
way
I
put.
It
is
IT
transitioning
from
a
cost
center
to
a
source
of
really
differentiated
value
in
the
industry
like
how
do
you?
A
How
do
you
build
yourself,
as
somebody
different
from
all
the
players
in
your
in
your
specific
industry,
especially
in
the
context
where
the
sort
of
traditional
business
is
the
brick-and-mortar
type?
Businesses
are,
potentially
being
you
know,
completely
turned
inside
out
and
upside
down
by
new
players
who
have
a
very
software
centric
view
of
the
world.
So
to
me
this
is
heavily
led
by
open-source
innovation,
and
it
really
is
looking
at
where
we
were.
A
You
know
five
ten
years
ago,
really
pushing
open
source
as
a
commoditization
concept
and
lowering
your
cost
because
I
t
well,
it's
a
cost
center
to
open
source
is
the
place
where
we're
doing
innovative
work
and
that's
what
you
want
to
leverage
when
you're
looking
at
IT
as
a
source
of
your
you
know,
differentiated
business
value,
so
the
the
buzzword
compliant
part
of
this
is
digital
transformation.
You
hear
a
lot
about
digital
transformation.
Your
analysts
have
all
the
different
ways
of
defining
it
again.
A
This
is
about
driving
business
value
through
through
your
IT
infrastructure,
more
and
more,
at
the
top
of
mind
for
for
CIOs.
This
is
a
survey
that
we
did
and
you
know
trying
to
get
some
insights
into
where
the
heads
of
CIOs
are
right
now
and
so
they're.
Looking
at
how
can
they
show
business
to
French
differentiated
value
from
their
IT
departments?
How
can
they
do
that,
while
managing
security
and-
and
you
know,
being
a
risk-averse
traditionally
risk-averse
department?
Managing
risk
is
really
important
things
to
top
a
mind
to
to
the
CIO?
A
You
don't
want
to
be
the
next.
You
know
Wall
Street
Journal
article
showing
how
you've
been
hacked
and
leaked
out,
a
bunch
of
of
credit
card
information
or
other
kind
of
critical
information,
and
in
order
to
support
these,
you
know
this.
This
sort
of
transformation
of
this
journey,
building
up
a
new
set
of
skills
and
an
infrastructure
that
enables
these
modern
architectures.
A
So
one
of
the
things
that
the
you
know
we
see
just
from
talking
to
all
of
our
customers
and
something
that
I
like
to
highlight
when
you're
in
conversation
with
any
one
particular
kind
of
industry
vertical
is
this
is
common
across
all
of
the
industry.
It's
not
just
a
that.
You
see
in
the
public
sector
or
an
issue
that
you
see
in
retail
or
an
issue
that
you
see
with
telcos.
A
In
the
telco
case,
that
specialization
is
important
to
understand,
but
it
doesn't
mean
we
need
to
write
something
fresh
from
the
ground
up
for
peach
and
Industry
vertical
and
in
the
past,
there's
been
a
lot
of
temptation,
and
you
know
businesses
that
grown
up
around
that,
but
today
and
part
of
the
power
of
open
source
where
we
bring
people
together,
we
collaborate
and
build
these
more
sophisticated
systems.
You
know
architected
to
extend
and
be
able
to
to
take
on
these
these
varying
kind
of
requirements.
A
I
think
that's,
that's
really
an
important
message
to
get
out
to
make
sure
we're
collaborating
together
and
bring
it
as
much
the
industry
together
to
focus
on
solving
problems
together
and
at
the
bottom
of
all.
This
is
this
infrastructure
modernization,
that's
helping
the
these.
These
businesses
adapt
to
the
the
business
demands
that
are
that
are
feeding
this,
this
sort
of
sense
of
urgency
as
a
technologist.
It's
really
tempting
to
just
get
enamored
with
technology
and
I
think
we
do
a
disservice
in
general
to
the
industry,
when
we
over
focus
on
just
technology
we're
developers.
A
At
least
you
know
my
background
is
coming
from.
You
know:
developer
developers
at
heart,
you're
focused
on
writing
code
and
using
technology
to
solve
problems.
You
know
Donny
touched
on
this
this
morning.
It's
not
just
about
technology,
there's
really
critical
component
from
the
DevOps
movement
that
recognizes
people
in
process
actually
really
matter.
So
you
can
have
a
pipeline.
You
know
kind
of
a
not
STI
CD
pipeline,
which
is
the
conceptual
pipeline
of
activity
that
starts
with
developing
your
software
and
ultimately
deploying
it
that
has
a
lot
of
arcane
processes
involved.
A
You've
got
different
groups
that
throw
things
over
the
wall
and
don't
speak
with
each
other,
and
the
end
result
is
every
one
of
those
touch
points
along
the
way
is
a
stall
point.
You
know
it's
it's
a
queueing
point
if
you're
thinking
about
network
queueing
or
it's
a
place
where,
where
things
are
going
to
slow
down-
and
so
you
know
recognizing
that
this
is
a
big
part
of
your
efficiency
gains-
is
really
important
in
that
you
can
throw
any
amount
of
technology
at
the
problem.
A
But
if
you're
not
really
focusing
holistically
on
solving
that
problem,
you're
not
going
to
get
there
so
I
T
must
evolve
and
that's
people
process
and
and
technology
I
think
we've
seen
a
lot
of
this
kind
of
concept.
I
like
to
think
of
this
in
four
parallel
streams
in
terms
of
IT
evolution
and
one
of
the
things
that
I,
I
think
is
important
to
look
at
is,
if
you
look
from
a
kind
of
development
process,
point
of
view
waterfall
through
to
dev
ops
or
an
application
architecture,
client-server
multi-tier,
apps
microservices.
A
Each
of
these
different
forms
of
evolution
are
taking
place
to
some
degree
in
isolation
and
I.
Think
what's
really
special
about
right.
Now
is
the
confluence
of
all
of
these
ideas
coming
together,
and
this
is
why
we're
seeing
a
the
you
know
it's
in
some
cases.
It's
repeating
ideas,
but
it's
the
fact
that
they're
happening
at
the
same
time
that
really
makes
them
powerful.
So
on
the
cloud
side
you
have
API
driven
infrastructure.
A
You
could
still
be
deploying
virtual
servers,
multi-tiered
apps
and
using
a
waterfall
methodology
and
you're
going
to
gain
some
level
of
efficiency
so
stand
alone.
Just
have
an
API
driven
infrastructure
is
beneficial.
You
know
as
you
and
you
can
think
of
that
in
any
of
these
dimensions,
each
one
of
those
have
some
standalone
efficiency
gain.
It's
the
it's
the
confluence
of
these
streams.
That
really
brings
the
fundamental
change.
I.
Think
we're
seeing
right
now
and
to
me:
that's
what's
exciting.
A
So
brief
digression,
I
was
in
Australia
recently
and
I
was
talking
with
some
customers
and
we're
actually
talking
about
this
topic
cloud
native
and
how
do
they?
How
do
we
help
them,
get
adopting
new
technologies
and
transform
their
IT
departments
to
help
support
that
that
those
knees
from
the
lines
of
business
and
I
completely
independent?
These
two
different
customers
are
through
me,
arguing
with
each
other
about
who
has
the
older
main
in
Australia,
and
these
are
mission
critical
systems,
one
of
which
the
last
time
they
touched.
A
The
software,
I
think,
was
1978
handling
a
large
number
of
transactions,
and
you
know
we're
sort
of
struggling
with
this.
On
the
one
hand,
everything
is
new
and
we're
trying
to
move
fast
and
on
the
other
hand,
we
have
real
critical
systems
that
are
part
of
large
enterprise
infrastructure
that
actually
aren't
going
to
change,
or
at
least
not
change
quickly,
and
so
there's
some
design
patterns
that
kind
of
we
can
derive
from
from
those
requirements
that
can
help
us
understand.
A
So
my
sort
of
hypothesis
here
is
that
change
is
constant
and
with
constant
change.
Your
technology
choices
are
point
in
time
choices.
It's
your
mindset,
your
process,
your
your.
How
do
you
manage
and
adapt
to
change
that
really
matters?
So
how
do
you
build
in
this
environment
of
constant
change
and
to
me
this
is
sort
of
a
simple
thought:
experiment
that
applies
both
to
the
application
tier
as
well
as
the
infrastructure
tier,
so
the
infrastructure
as
a
code
concept,
we
can
be
doing
the
same
things
as
we're.
A
In
a
modern
sort
of
world,
the
same
principle
I
think
holds,
and
that's
the
hardware
level
now
we're
talking
about
a
data
center
wide
pool
of
hardware.
You
have
some
resource
management
at
the
bottom,
some
infrastructure
management
or
virtualization
layer.
Potentially,
there
are
virtual
machine
primitives
associated
with
that
virtual
virtualization
layer,
there's
useful
for
certain
types
of
tasks,
but
there's
also
an
application
orchestration
tier
that
makes
it
more
accessible
to
a
different
set
of
developers.
You
know
specifically
running
containerized
applications
and
you
know
again
it's
just
a
box
diagram.
A
So
it's
easy
to
make
things
look
the
same,
but
I
think.
The
point
is
that
there's
different
tools
for
different
jobs
and
one
of
the
things
that
we
hear
from
our
customers
is
confusion
about.
Why
are
we
making
a
change
because
it
sounds
an
awful
lot
like
what
we
just
did
virtualizing
ourselves,
so
we're
really
trying
to
help
articulate
the
difference
between
why
you
should
care
about
application
orchestration
as
independent
from
resource
management
and
I'm
using
this
sort
of
operating
system,
JVM
analogy
as
a
way
to
cut
that
make
it
really
accessible.
A
That
sort
of
differing
views
of
you
know
requirements
is
focusing
again
on
separation
of
duty,
which
is
that
similar
to
that
Java
to
application
orchestration
diagram.
I
was
showing
before
and
this
pacifically
we're
talking
about
OpenStack
and
kuba
Nettie's
from
a
red
hat
point
of
view.
But
the
point:
isn't
you
know
it's,
not
the
technology
choices,
just
the
abstraction
layers
and
really
helping
people
see
that
there's
value
in
in
recognize,
and
you
know
in
utilizing
the
abstraction
at
each
layer
I
think.
A
Sometimes
we
get
confused
because
there's
a
lot
of
amazing,
open
source
projects,
tackling
problems
in
slightly
different
ways,
and
you
know
we
we
see,
there's
temptation
to
grow
up
or
go
down
and
functionality
so
again,
just
because
you
could
port
a
JVM
to
an
x86
bare
metal.
Maybe
that's
not
the
best
choice,
so
open
shift
is,
is
the
product
from
from
Red
Hat
and
that's
something
that
we're
really
proud
of
we're
building
that
out
of
some
core
technology.
A
Certainly
Linux
is
at
the
base
dockers,
a
core
component
for
for
the
container
engine,
Kuber
Nettie's
for
application,
orchestration
some
additional
logic
to
help
improve
developer
efficiencies
so
that
you
can
start
with
source
code.
Push
your
code
go
through
a
CI
CD
pipeline,
ultimately
deploy
your
code.
Have
that
code
be
deployed
across
a
large
skip
scale,
pool
of
infrastructure
and
manage
all
of
the
load,
balancing
application,
level,
routing,
etc,
and
you
know
having
registries
and
persistent
storage
and
all
the
things
that
actually
make
a
system
work.
A
So
we're
you
know
we're
active
in
oci
trying
to
help
standardize
the
runtime
and
image
format
for
for
for
containers
and
then,
as
we
were
talking
earlier
today,
whether
it's
standardization
best
practices
sharing
of
information
taking
that
those
core
building
blocks
and
expanding
that
into
the
entire
infrastructure
needed
for
cloud
native
infrastructure
to
to
build
out.
You
know
an
industry
understanding
through
combination
of
open
source
development
and
and
some
level
of
standardization.
A
What
does
it
mean
to
bring
all
these
things
together
here
at
CN
CF,
we
have
been
able
to
we've
been
blessed
with
an
awesome
gift,
which
is
a
thousand
node
cluster
I.
Don't
think
it's
quite
a
thousand
nodes
yet,
but
it's
growing
quickly
to
be
a
thousand
notes,
and
so
we
took
advantage
of
that
cluster
to
run
open
shift
on
the
cluster
in
just
experiment,
with
what
scaling
looks
like
in
that
environment,
the
actually
I
wanted
to
say
one
other
thing.
A
This
is
the
cloud
native
computing
foundation,
initial
charter
architecture,
diagram-
and
you
heard
earlier
today
that
we
weren't,
quite
in
total
agreement
over
exactly
what
this
architecture
diagram
looks
like
so
think
of
this
as
just
a
placeholder,
but
it
does
call
out
some
of
these
different
layers.
You
know
different
notions
of
orchestration
versus
infrastructure
versus
that
top-level
application,
definition
that
we
talked
about
earlier
today.
That
I
think
is
really
important
and
trying
to
help
define
some
of
those
distributed
services.
A
Now
the
the
scale
testing
that
we
did
was
see
in
CF,
so
first
a
big
thank
you
to
Intel
and
switch
for
putting
together
this
infrastructure
forest
and,
of
course,
the
CNC
F
hosting
it.
Our
goal
was
to
scale
open
shift
to
a
thousand
nodes.
We
actually
use
300
physical
notes,
we
virtualized
the
infrastructure
using
OpenStack
and
then
ran
openshift.
On
top
of
that,
we
learned
a
lot
out
of
this
process
and
we
were
really
happy
to
be
able
to
share
that
with
the
community.
A
I
have
a
link
in
here
that
that
links
to
a
blog
post,
we
put
on
cnc,
f
dot
blog
post
two
days
ago.
I
definitely
want
to
thank
Jeremy,
who
I
think
is
here
and
the
rest
of
the
team
for
a
lot
of
work
that
it
took
to
run
through
some
trial
and
error,
discovering
some
of
the
challenges
with
just
getting
this
infrastructure
working
because
there
hasn't,
it
hasn't,
been
utilized,
I,
don't
believe
to
the
scale
yet,
and
one
of
the
things
that
I
think
is
cool.
Is
this
I'm
running
out
of
time
here?
A
So
I
won't
go
into
much
detail
over
what
the
internal
architecture
was
of
the
deployment.
But
one
of
the
things
that
I
think
it
was
cool
is
the
outcome,
and
what
this
is
is
just
a
list
of
the
bugs
that
we
found
filed
in
and
either
resolved
or
in
the
process
of
resolving.
As
a
result
of
trying
to
scale
up
the
system
to
that
size-
and
you
can
see
it's
spanning
across
a
number
of
different
projects-
we
we
found
issues
in
Cuba
Nettie's.
We
found
issues
in
dr..
A
We
found
issues
in
ansible
or
using
ansible
and
discovered
a
performance
regression
that
was
really
important
for
us
to
fix.
So
you
know
you
see
that
using
this
Hardware
resource,
something
that
we
haven't
CN
CF
to
do
this
kind
of
scale,
testing,
where
we
were
focused
on
not
just
kind
of
micro
benchmark.
How
many?
How
many
containers
can
you
launch
within
a
period
of
time,
but
trying
to
look
at
it
more
comprehensively
from
a
user?
A
realistic
use
case,
point
of
view
and
one
of
the
things
that
came
out
of
this
or
that's
driving?
A
This
is
the
cluster
loader,
which
is
a
open
source
project
that
that
we
use
to
kind
of
generate
the
load
for
this
system
and
that's
something
that
we
would
be
happy
to
share
with
the
CNC
f,
or
at
least
you
know,
give
you
pointers
to
it
on
github.
But
the
you
know,
the
outcome
of
this
again
is
touching
a
lot
of
different
subsystems
and
helping
us
understand
the
challenges
and
then
advance
the
state
of
the
art
for
the
industry.