►
Description
Panel: Kubernetes, Cloud Native and the Public Cloud [B] - Moderated by Dan Kohn, Cloud Native Computing Foundation
The six largest public cloud providers -- AWS, Microsoft, Google Cloud, IBM Cloud, Alibaba Cloud and Oracle -- are all now major backers of CNCF and Kubernetes. This is a chance to hear their perspective on investments they are making into Kubernetes and other CNCF technologies. How are they using these technologies internally? What changes are they making in their offerings to better suit cloud native enterprises? What is their perspective on the future of container runtimes? How do they deal with customers that need a hybrid cloud solution? Is the infrastructure layer becoming commoditized? What is their ability to differentiate in value added services at the higher layers? What projects should CNCF bring in to help fill out its stack?
About Dan Kohn
Twitter Tweet LinkedIn Connect Websitehttps://dankohn.com
Dan is Executive Director of the Cloud Native Computing Foundation, which sustains and integrates open source technologies like Kubernetes and Prometheus. He also helped create and launch the Linux Foundation's Core Infrastructure Initiative as an industry-wide response to the security vulnerabilities demonstrated by Heartbleed.
About Jon Mittelhauser
Jon runs engineering for the Container Native Platform team at Oracle (which includes all of Oracle’s Kubernetes offerings). Jon is considered one of the founding fathers of the World Wide Web with more than 20 years of open source and engineering management experience. He wrote the first widely used Web browser (NCSA Mosaic for Windows) as part of his Master’s thesis at the University of Illinois and was a founding engineer of Netscape Communications. More recently he ran engineering for Nebula, Inc., was on the OpenStack foundation board and was CEO of CloudBolt Software.
About Gabe Monroy
Gabe Monroy is the Lead PM for Containers on Microsoft Azure. Gabe was the founder and CTO of Deis, which was acquired by Microsoft in 2017. As an early contributor to Docker and Kubernetes, Gabriel has deep experience with containers in production and frequently advises organizations on PaaS, distributed systems, and cloud-native architectures. Gabriel speaks regularly at industry events including KubeCon, DockerCon, CoreOS Fest, GlueCon, QCon, and Microsoft Build.
About Todd Moore
Todd leads the IBM global team working to develop open communities that fuel both innovation and new business models. Todd can be found engaged with communities and technologies that span Cloud Computing, Mobile, Social Business, and Analytics. He has the pulse of where open innovation is happening around the industry. Todd has a unique background in software and hardware development, architecture, design and product management. He has served in executive roles in both IBM’s Software and Systems.
About Aparna Sinha
Aparna Sinha leads the product team at Google for Kubernetes and Container Engine. She started and co-leads the community PM Special Interest Group (SIG) to maintain an open backlog for the Kubernetes project on Github. Aparna is currently a secondary member of the CNCF Governing Board. She has worked in enterprise software for 15+ years, and was formerly a Director of Product at NetApp. Aparna holds a PhD in Electrical Engineering from Stanford and has co-authored several technical papers during her research.
About Hong Tang
Dr. Hong serves as Chief Architect at Alibaba Cloud, the cloud computing arm of Alibaba Group. He joined Alibaba Cloud in 2010 and has been instrumental in the development of Apsara, Alibaba Cloud’s large-scale computational engine.
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
My
name
is
Dan
Khan
I
am
the
executive
director
of
the
cloud
native
computing
foundation
and
I'm
thrilled
to
welcome
our
first
ever
public
cloud
panel,
where
we
have
representatives
from
almost
all
the
biggest
public
clouds
around
the
world
and
I'll
start
out
by
just
asking
each
of
them
to
introduce
themselves
also
how
you
joined
your
company,
where
you're
from
how
far
you
came
to
cut
to
get
here.
That
kind
of
thing
sure.
B
D
A
E
F
Hi
I'm
a
Pernod
Cinna
I'm
with
Google
Cloud
I
lead
product
management
for
kubernetes
the
open
source
project,
as
well
as
for
Google
container
engine,
which
is
our
hosted,
offering
and
I've
been
with
Google
for
a
little
over
four
years
and
I've
spent
most
of
my
life
in
enterprise,
IT
I'm,
originally
from
a
Silicon
Valley.
So
or
that's
where
I'm
traveling
from
so.
A
Maybe
we
could
start
with
kubernetes,
but
then,
since
this
is
also
the
cloud
native
conde,
I'd
love
to
go
on
and
and
talk
about,
some
of
the
other
13
projects,
I'm
curious,
which
ones
you're
using
today
in
introduction
the
clouds
and
then
which
ones
either
current
CNCs
projects
or
prospective
CNCs
projects.
You're
you're
particularly
excited
about
and
think,
there's
a
lot
of
opportunity
there
I
would
just
go
down.
Maybe
we
could
start
with
the
Pernod
sure.
F
So
obviously,
I'm
very
involved
in
kubernetes
that
takes
up
all
of
my
time
and
I
love
kubernetes
in
the
community,
but
in
terms
of
other
projects,
sto
is
a
huge
effort
for
us
at
Google
and
I
participate
in
that
and
we're
very,
very
excited
about
it.
I
think.
Actually,
a
decent
number
of
talks
here
are
about
sto
and
it'll.
Be
part
of
my
talk
as
well.
E
Obviously,
kubernetes
is
really
important
to
all
of
us.
We
wouldn't
be
here
with
it
without
it,
but
container
D
very,
very
important.
The
things
that
we're
doing
sto
as
well
to
working
closely
with
with
Google
on
sto
and
you'll,
see
all
the
tracks
and
all
the
talks
that
are
happening
here.
Having
that
you
know
mesh
layer
that
we
can
depend
on
really
is
super
important
to
all
of
us.
D
D
Looking
forward,
we
also
are
looking
at
micro
services
and
service
matches,
do
being
one
more
active
in
the
service
working
group,
we
announced
our
FN
service
cross
cloud
product
and
then,
just
today
we
announced
an
open-sourced,
a
multi
cluster
management
platform,
that's
built
on
top
of
kubernetes
Federation
called
Navarre
Coase,
it's
a
Greek
for
Admiral,
it's
following
the
same
theme,
so
you
know
we.
We
just
basically
published
that
and
we're
going
to
talk
with
a
bunch
of
the
folks
here
in
terms
of
where
it
should
fit
in
into
the
kubernetes
ecosystem.
C
At
Alibaba
cloud
I
will
work
with
mainly
well.
Work
mainly
involves
kubernetes
the
integration
of
kubernetes
as
manager
service,
our
cloud
and
also
enabling
people
to
use
kubernetes
to
run
machine
learning,
HPC
kernel,
workloads,
we're
also
looking
into
integrating
with
container
D,
and
also,
we
are
also
looking
into
some
other
sensitive
projects
in
how
that
can
help
us
inside
Alibaba
Group.
Obviously,
we
also
use
kubernetes
in
various
departments,
particularly
in
the
AI
and
a
training
kind
of
workload.
C
B
And
Microsoft
we're
very
focused
on
delivering.
You
know
what
I
like
to
refer
to
as
sort
of
the
CN
CF
stack
some
stuff
right
and
making
that
available
to
customers
things
like
our
kodoku
Brunetti
service,
which
we
just
launched
in
preview
a
little
while
ago.
You
know
also
technology
like
the
open
service
broker.
We
actually
just
today
announced
the
new
open
service
broker
for
Azure,
just
a
sort
of
a
ground-up
rewrite.
B
You
know
that
conforms
to
the
new
open
service
broker,
spec
sort
of
glue
kubernetes
to
other
outside
services,
but
I
think
what's
more
interesting
is
the
degree
to
which
the
CN
CF
technologies
have
start
to
penetrate
inside
of
Microsoft
we're
starting
to
see
a
lot
of
teams.
Just
you
know,
Microsoft's
a
big
company
right,
and
so
you
know
people
are
just
popping
up
kind
of
everywhere
who
are
using.
You
know:
hey
I'm,
using
G,
RPC
or
hey
I'm,
using
open
tracing
and
I.
Think
it's
really
just
a
good.
C
We
don't
pick
paddles
to
me,
I
think
that
the
container
runtime,
even
though
orchestration
would
eventually
be
standardized
and-
and
we
think
that
going
forward
that
likely
we're
gonna
go
with
the
container
d
Brita
by
open,
really
open
to
whatever
is
available
there,
and
also
we
think.
What's
really
important
is
from
the
control
and
side.
It's
the
API
consistency
from
Renton
side.
I
would
say
it's
a
performance,
stability
and
crossbone
cross-platform
compatibility.
So
that's
my
answer.
C
D
D
And-
and
you
know,
we've
worked
on
the
OCI,
you
know
we
actually
wrote
a
rust
implementation
of
OSI
I,
you
know
demonstrate
and
to
improve
that
format.
So
you
know
it's
not
something
we
have
particular
religion
on
and,
and
you
know
or
ya,
are
going
to
make
a
call
on
it's
not
our
place
to
do
that.
Yeah.
E
I,
don't
think
it
has
to
be
a
religious
argument
and
so
Phyllis
T's
from
our
team
you'll
see
a
lovely
talk
on
container
D
from
Phil
and
showing
something
so
I.
You
know,
look
up,
Phil's
talk,
we're
gonna
provide
what
people
want
to
have,
and
you
know
our
current.
The
IBM
cloud
is
is
docker
and
kubernetes,
and
you
know
it,
it
won't
be
a
religious
argument
for
us
it'll
be
what
is
being
asked
for
by
the
folks
at
large.
The
end-user
pace.
F
F
Interface,
which
allows
you
to
plug
in
multiple
different
runtimes
and
switch
them
out,
depending
on
which
one
is
better
for
your
application,
and
we
started
that
process
in
May
of
last
year.
You
know
so
that
so
that
there
could
be
many
different,
runtimes
and
I
think
after
that
we've
been
using
in
Google
container
engine
docker,
because
historically,
this
is
a
now
we're
in
our
third
year
of
the
service
or
it's
been
a
while,
but
we
also
have
contributed
to
container
D
right
from
the
beginning
and
so
lantau
on.
F
Our
team
is
a
essential
part
of
that
project
and
we
collaborate
with
the
other
runtimes
I'm
very
excited
about
cotta
containers,
I
think.
Actually
it
opens
up
a
new
range
of
applications
and
so
I
don't
expect
the
future
to
look
like
the
past
I.
Don't
necessarily
think
that
it'll
be
one
runtime.
It
may
be
different
runtimes
for
different
applications,
but
again
the
product
manager.
In
me,
it's
gonna
depend
on
as
far
as
Google
container
engine.
It's
gonna
depend
on
what
customers
want.
B
Anything
I
do
yeah
I
mean
you
want
a
controversial
yeah.
Who
cares
ya,
know
I,
because
customers
I
talk
to
they
don't
care
what
containment
runtimes
there
right.
They
want
to
deliver
code,
they
want
deliver
applications,
I
mean
we
use
docker.
Today,
UI
I
think
there's
a
lot
of
options
going
forward,
but
at
the
end
of
the
day
this
is
a
commodity
component
right
in
the
stack
it
shouldn't
be
doing
too
much.
It
should
be
boring
infrastructure.
We
get
to
hear
that
term
is
running
around
a
lot.
B
So
for
me,
I
value
mileage,
I
value
you
how
much
production
uses
this
have.
How
hardened
is
it
that
sort
of
thing?
And
if
customers
are
aware
of
what
container
runtimes
you
know
they're
using
beyond
things
like
you
know,
building
models
and
things
you
know
we
talked
talked
a
little
bit
about
servos
containers
in
a
bit.
Hopefully,
but
you
know
if
customers
care
what
the
runtime
is
we're
doing
something
wrong,
but.
A
And
I
really
do
just
he's
not
here,
but
just
call
out
for
a
second
the
open
container
initiative,
which
is
a
sister
project
to
see
mcf,
that's
been
led
by
Chris
and
check,
and
the
sea
change
here
versus
two
years
ago,
where
we
would
get
a
panel
up
and
they
would
argue
constantly
what
the
future
is
going
to
be
and
yeah
back
to
the
Tim
Hawke
and
quote
that
this
is
just
a
fantastic
situation.
That
is
boring
infrastructure,
but
those
projects
can
go,
compete
for
mine
share
and
market
share
and
and
technical
improvements.
F
What
is
mattered
as
far
as
the
runtime
is
stability,
you
know,
and
responsiveness
and
inclusiveness
as
far
as
the
community,
that
that
is
around
that
project
so
and
maybe
that
matters
more
from
an
engineering
perspective,
but
it
does
manifest
itself
into
customers.
If
there's
you
know,
if
there's
bugs
and
there's
lots
of
patches
and
it's
not
evolving
enterprise.
E
A
A
metaphor
in
the
Linux
world
that
the
kernel
developers
run
a
Linux
plumbers
conference
and
like
plumbing
it's
kind
of
boring
until
it
doesn't
work,
and
then
you
get
very,
very
upset.
So
one
more
try
for
controversy.
Austin
collins
of
serverless
calm
claim
to
me
last
week
that
within
two
years,
75%
of
the
applications
deployed
in
public
clouds
would
be
serviced.
So
a
give
me
your
own
percentage
and
then
B
to
make
it
a
tiny
bit
more
realistic.
A
B
B
Actually
think
event
based
programming
is
a
suited
to
every
work
load.
So
I
think
you
know
to
me.
You
know.
Server
list
is
just
a
terrible
term.
It's
just
completed
a
bunch
of
things.
I
think
we
all
can
agree
on
that.
I'll
put
it.
The
best
definition
I've
heard
is
a
three
thing.
So
it's
one
is,
is
invisible
infrastructure?
You
don't
see
the
infrastructure.
The
second
is
micro
billing
right
people
want
micro
billing,
and
the
third
is
the
event
based
program
model,
typically
associated
with
functions
as
a
service.
Now
what
we've
done
at
adder
is.
B
We've
actually
said
well
that
last
one
that
event
based
programming
model,
that's
a
little
restrictive.
So
why
don't
we
focus
on
delivering
something?
That's
micro,
build
and
invisible
infrastructure,
but
use
containers
as
the
form
factor,
because
this
gives
a
lot
more
flexibility,
so
we
released
back
in
July.
This
thing
called
as
your
container
instances
who
were
the
first
major
clouds
come
out
with
what
I
call
a
server
list
container,
runtime
and
I
think
this
is
a
really
interesting
space.
B
In
fact,
today,
just
at
11
o'clock,
we
just
announced
this
new
thing
called
the
virtual
couplet,
and
this
is
pretty
fascinating,
because
what
the
virtual
couplet
does
is.
It
allows
you
to
take
kubernetes
and
basically
have
a
virtual
node,
with
unlimited
capacity
backed
by
one
of
these
service
container
runtimes.
So
you
get
the
benefits
of
server
lists.
You
know
in
terms
of
micro,
billing
and
visible
infrastructure,
you're
not
restricted
by
the
event
based
program
model,
and
you
get
to
use
the
kubernetes
api
to
drive
it
so
we're
excited.
B
This
is
now
a
sort
of
a
community
effort.
We've
teamed
up
with
hyper
who
is
delivering.
You
know
one
of
the
other
service
container
runtimes,
the
repo
is
open,
source
and
available.
Today,
it's
you
know
we're
blogging
about
it
and
talking
about
it
actively,
so
definitely
recommend
checking
it
out.
Yeah.
C
I'd
also
want
to
argue
that
server.
This
is
probably
a
misleading
one.
Now
people
started
using
so
as
substitution
of
function,
computer
lambda,
but
I
would
argue.
You
know.
The
first
service
platform
is
really
the
Google
App
Engine
right
it
don't
know
it.
Then
you
don't
know
about
anything
about
the
service.
So
if
you
really
take
a
service
literally,
it's
really
means
cloud
native.
You
know
you
you
you,
you
really
want
to
take
advantage
of
the
elasticity,
on-demand
billing
of
the
cloud
services
and.
C
Let
me
just
rephrase
the
question,
so
if
you
really
ask
my
manager
event
based
computing,
I
would
say
really
depends
on
how
you
define
this
percentage
right.
I
would
argue
that
most
likely
70
PI
75
percent
application
use
more
or
less
of
those
event
triggering
to
glue
those
together.
Maybe
that's
a
realistic
number,
but
in
terms
of
for
the
computing
resources
being
consumed
that
I
doubt
that's
gonna
consume
a
lot
of
resources.
I
would
still
argue
you
know
there
would
be
the
diversity
of
computing
paradigms.
C
You
know,
you
know,
including
these
new
people
were
deploying
to
the
virtual
machines
using
containers.
Even
using
you
know,
for
the
data
analytical
workload,
which
is
the
bulk
of
the
computation
being
used.
People
want
to
use
the
managed
big
data
services
right,
so
so
in
terms
of
code
or
computing
resources
being
used
I
doubt
it's
gonna
be
a
big
percentage.
Yeah.
D
Yeah
I
think
you
guys
see
different
customers
than
I.
Do
you
know?
One
thing
about
my
group:
is
we're
really
targeted
at
you
know
not
surprising
the
Oracle
customers
right.
So
you
know
what
we
are
looking
at
is
the
large
enterprise
customers.
Who,
frankly,
are
you
know
still
running
Java
WebLogic
local
on
Prem
right.
So
you
know
that
the
transition
those
customers
are
looking
for.
It
is,
you
know
what
we
call
modern
application
development
and
it's
you
know
it's.
This
stack
we're
talking
about
its
CN
CF
based
kubernetes
transition,
etc.
D
I
mean
frankly,
docker
containers
is
pretty
new
for
a
lot
of
those
right.
So
you
know
75%
of
applications
and
the
cloud
being
server
list
is
I
mean
it's.
It's
ridiculously.
If
depends
on
what
you
mean
by
in
the
cloud
of
course,
which
I
think
you
have
to
define.
First,
you
know
if
you're
saying
new
applications
being
written
by
you
know
the
guy
at
Stanford,
pulling
out
a
credit
card
and
getting
an
Azra
in
AWS
account
I.
Think
a
lot
of
those
things
will
be
architected.
D
You
know
parts
of
them
in
an
event-based
architecture
like
Gabe
talked
about,
but
you
know,
applications
in
general
I
mean
to
start
with
all
the
massive
applications
out
there
I
mean
we
didn't.
Are
we
talking
quantity
of
applications?
Their
quantity
users
are
yeah.
My
first
instinct
was
20%,
but
again
without
defining
the
terms,
I
think
it's
it's
it's
hard
to
say.
One
of
the
other
things
that
Oracle
thinks
is
important,
or
my
group
thinks
is
important.
Is
that
that's
serverless,
which
I
agree
with
the
consensus
is
a
horrible
term.
D
You
know
shouldn't
be
a
vendor
lock-in,
type
thing
and
and
the
way
it
started.
Obviously
it
became
that
you
know
the
primary
the
primary
implementation
people
think
of
is
is
lambda
and
that
is
really
tied
in
deeply
with
with
AWS.
So
you
know
FN
and
one
of
the
reasons
we
open-source
and
announced
it
was
a
framework
by
which
you,
as
an.
D
E
I'm
the
open
source
guy
at
IBM
and
open
is
what
I
believe
in
and
for
this
world
I
believe
again,
as
john
has
talked
about
that,
we
should
have
an
open
alternative
that
we
can
all
get
behind.
To
that
end,
we
took
our
open,
wisk
infrastructure.
We
brought
it
out
to
the
Apache
Software
Foundation,
where
we're
actively
working
with
the
likes
of
Adobe
and
Red
Hat
and
others
to
go
and
build
up
essentially
a
ubiquitous,
widely
available
open-source
project
for
service.
It
really
comes
back
to
the
eventing,
though.
E
In
the
end,
we
all
have
this
multitude
of
service
platforms
that
we'll
have,
but
what
is
important
is
to
get
to
an
inventing
model
and
some
specifications
and
things
that
allow,
for
you
know
the
events
to
happen
triggers
to
happen,
policies
to
be
followed
and
work
to
be
done
and
that
people
will
use
that
technology
as
appropriate
to
orchestrate
and
run
the
applications
that
they're
they're
building
and
running.
But
it
won't
be
the
thing,
the
thing
that
everybody
does
it'll
be
a
big
part
of
their
portfolio
of
how
they
go
about
doing
work.
E
So
that's
what
we're
trying
to
enable
and
with
some
success
and
and
of
course,
lambda
I
get
the
plug
node.js
now
right,
so
you
know
lambda
and
others
and
ourselves,
you
know,
really
came
together
around
nodejs
is
the
way
of
going
and
doing
that.
So
you
know
anybody
who's
looking
at
serverless
also
and
then
needs
to
go.
Look
at
node.js
how
they're
gonna
go
put
that
together
and
use
it
and
I
think
there's
a
great
synergy
there.
E
Small
tight,
quick
startup
run
do
things
and
that's
what
we
see
and
you
know
currently
our
world
when
it's
opened.
Wisk
is
based
on
docker,
but
we're
working
quite
nicely
with
the
community's
team
now
to
to
look
at
moving
moving
over
on
to
kubernetes
and
I.
Think
the
future
is
bright
for
service
and
there'll.
Be
many
lightbulbs
excuse.
D
F
I'll
give
you
a
counter
prediction:
I
think
that
80%
of
public
cloud
will
run
containers
in
three
to
five
years.
I
hope
that
the
majority
of
that
will
be
running
kubernetes
I
think.
The
reason
for
that
is
because
kubernetes
is
open
and
it
runs
anywhere
and
I
think
that
you
can
apply
that
principle
to
serverless
as
well.
I
think
Hong
mentioned
that
App
Engine
is
the
first
serverless
offering
in
the
cloud
and
that's
true.
F
The
benefits
of
serverless
are
really
when
you
don't
get
charged
for
when
you're
not
running,
and
you
can
quickly
scale
to
zero
and
quickly
scale
up.
Those
benefits
are
difficult
to
realize.
On-Premise
and
I
think
that's
a
limiting
factor.
A
lot
of
enterprise
IT
is
on-premise,
and
so,
if
you
have
a
paradigm
which
doesn't
work
in
a
hybrid
environment,
then
that
can
limit
its
adoption.
F
The
other
piece
is
that
much
of
server
less
today
isn't
open
and
I
think
this
is
where
you
know
open
wisk
and
Q
bless,
and
some
of
the
other
vision
and
the
frameworks
that
are
coming
up
in
the
kubernetes
community
are
going
to
fill
that
gap
of
being
open.
I.
Think
if
server
lists
can
be
open
and
have
an
analogue
on-premise,
then
it
has
a
higher
probability
of
adoption
in
public
cloud.
I
think
75%
is
aggressive.
B
One
other
thing,
I'd
point
out
is
that
the
openness
is
not
just
you
know,
so
that
we
can
all
feel
good
that
we're
using
open
source.
You
know,
part
of
the
reason
here
is
that
functions
are
going
to
live
in
an
ecosystem.
That's
heterogeneous
functions
are
gonna,
be
talking
to
containers
talking
to
VMs
talk
into
legacy
stuff,
and
if
it's
you
know,
ideally,
if
we
can
get
it
all
running
on
kubernetes
as
a
partner's
is
adjusting,
we
can
you
allow
forth.
F
D
You
know
serverless
is
a
category
of
kind
of
moving
away.
You
know
making
infrastructure
boring
right,
so
is
micro
services
and
sto
and
service
mesh,
and
some
of
the
things
built
on
top
of
that
I
mean
a
lot
of
what
we're
worrying
about.
Is
you
know
how
you
do
abstract
that
away?
And
so
they
you
know
they
don't
care.
What
cloud
they're
running
on
they
don't
care,
what
infrastructure
they
care
about.
You
know
what
is
giving
them
the
characteristics
they
need,
whether
that's
data
locality
or
security
or
performance,
or
any
of
that
they're
writing
applications.
D
E
A
No
I
was
saying
on
on
the
ground
in
on
bare
metal
and
so
I
guess,
although
from
the
cloud
service,
you
might
prefer
enterprises
to
just
move
everything
up,
could
you
talk
for
a
second
about
your
hybrid
cloud
strategy
when
an
enterprise
says
I'm
only
willing
to
move
some
of
my
workloads
into
the
cloud?
It's.
E
More
than
that
enterprises
they're
also
not
willing
to
go
and
re-engineer
legacy
applications
and
that
thing
that
lives
in
the
corner
that
is
ancient,
that
IBM
probably
helped
you
go
and
build
and
define
a
long
time
ago
right,
but
with
the
technologies
that
we
have
were
able
to
front-end
those
and
turn
them
into
useful
services.
Now
that
they
can
depend
on
and-
and
you
have
to
have,
that
available
to
the
enterprise
they
they're
it's
just
too
difficult
to
go
re-engineering
everything
cloud
native.
E
What's
there,
you
can
take
that
workload
and
move
it
over
into
a
public
cloud
environment
using
kubernetes,
using
containers
and
keep
on
going
and-
and
this
is
something
that
we've
really
embraced
ourselves
internally
as
well.
So
even
Watson
everybody,
here's
well
Watson
right,
Watson,
there's
all
guess
what
running
in
containers
on
kubernetes
now
Watson
the
services
are
turned
over
every
24
hours
and.
F
E
Pick
up
the
very
latest
updates
out
of
all
the
open-source
code:
that's
out
there
and
the
code
clearance,
continuous
integration,
continuous
deployment,
2000
packages
or
95%
automated
and
just
clearing
them
as
they
go
through
and
it
runs
and
keeps
going
in
every
seven
days.
Those
servers
just
get
restarted
and
continue
right.
It's
it's
a
lovely
way
of
doing
things.
F
A
F
Yeah,
so
I
actually
have
a
talk
on
hybrid
on
Friday
at
11:00.
So
please
come
to
that.
I
think
that
our
open
source
initiatives,
obviously
kubernetes,
is
do
open
service
broker
fee.
Is
there
essential
to
enabling
hybrid
the
customers
that
I
talk
to
who
want
hybrid
art?
I
tend
to
be
really
large
enterprises,
they
have
large
IT
teams,
they
have
very
much
a
DIY
kind
of
operation,
and
so
the
more
we
can
give
them
to
run
open-source
software
on
their
premise
in
a
way
that
is
consistent
with
Google
cloud
and
with
other
clouds.
B
Sure
you
know,
Microsoft
has
a
lot
of
experience
dealing
with
enterprises
right
been
around,
for
you
know,
20-plus
years
doing
that
and
one
of
the
things
we
heard
when
we
were
planning
out
our
cloud
development
strategy
was
things
like
Azure
stack
and
the
ability
to
have
a
cloud
in
a
box.
You
know
that
you
can
run
on
an
environment
as
important
to
folks.
Folks
are
running
a
disconnected
environments
like
a
cruise
ship
or
have
a
retail
operation
where
they
have
lots
of
different
branches,
I
mean
so
we're
committed
to.
B
You
know
having
the
same
set
of
cloud
api's
you
can
use.
You
know
up
in
the
public
cloud,
the
hyper
scale,
environment,
yeah
get
those
same
api's,
you
know,
sort
of
in
an
edge
form
factor
running
inside
of
a
branch
location.
It's
part
of
our
strategy,
customers
love
it,
and
you
know
you
know
we're
actively
working
with
folks.
You
know
doing
using
kubernetes
in
those
environments,
so.
C
So
those
open
source
could
run
along
some
of
the
competing
products
we
have
we
developed
by
our
owns,
and,
secondly,
we
also
provide
a
product
called
the
Express
Connect,
which
is
essentially
link
your
unpress
minute
on
premise
network
with
VPC,
so
that
actually
for
those
services
that
that
cannot
be
exposed
to
the
public
network.
You
still
can
run
those
component
together
as
a
single
application.
And
thirdly,
we
also
provide
a
bare-metal
service.
I.
C
Think
a
lot
of
quite
a
few
of
public
cloud
providers
also
do
that
now,
so
that
it's
easy
for
you
to
run
your
applications
currently
running
on
physical
machines
and
running
on
bare
metal
on
the
cloud
right
and
also
we
provide
our
shrink,
wrap
a
version
of
for
our
UPS.
Our
software.
We
quote.
Ups
our
stack.
D
B
D
D
The
advantage
of
kubernetes
is
it
is
that
abstraction
layer
right,
so
you
know
applications
written
for
you
know.
Oracle
kubernetes
engine
also
work
on
on-prem
kubernetes,
also
work
on
the
other
public
clouds.
That's
you
know.
I
mentioned
the
multi
cloud
management
platform.
That
is
one
of
the
ways
that
we
believe
you
know.
Application-Aware,
hey,
I
need
this
to
run
on.
Prem
I
can
scale
it
up
as
load
demands.
I
can
run
it
across
regions.
You
know
again
sort
of
abstracting
away
the
application.
Knowledge
from
the
infrastructure
on
Prem
is
just
a
set
of
characteristics.