►
From YouTube: State of the Union: OpenShift Roadmap Marek Jelen OpenShift Commons Gathering Helsinki 2018
Description
State of the Union, OpenShift Roadmap and Vision - Marek Jelen @ OpenShift Commons Gathering Helsinki 2018
A
A
So
let
me
start
from
the
back
from
the
past.
I
found
this
this
slide
in
one
of
the
marketing
presentations
and
I
quite
liked
it,
because
it
actually
shows
that
Red
Hat
and
Google
and
core
OS.
We
have
been
there
with
kubernetes
for
a
long
time
today,
everybody's
on
kubernetes
right,
do
you
know
somebody
who's
not
on
kubernetes,
not
really
so
today
everybody
wants
to
be
into
abilities,
but
only
those
three
companies
has
been
there
since
the
beginning,
like
really
involved
and,
as
you
probably
heard,
Red
Hat
and
core
OS
is
one
company
now.
A
What
is
the
goal
of
Red
Hat
and
what
has
always
been
the
goal
of
Red
Hat
is
to
be
independent
to
be.
I
cannot
stick
to
the
infrastructure
to
the
technology.
If
you
are
running
convey
and
if
you
are
running
on
IBM
or
something
we
would
like
you
to
be
able
to
run
open
chip
on
top
of
that
right,
you
don't
want
to
lock
you
into
one
thing
like
we
have
OpenStack.
A
A
So
you
can
run
open
shift
wherever
you
want
and
we
don't
talk
you
into
one
specific
infrastructure
or
tooling,
and
this
is
just
a
compliment:
Dianne's
presentation
from
the
more
businesses
side,
so
you
can
see,
as
the
number
of
the
customers
growing
the
split
between
the
different
industries
on
the
right
side.
So
just
a
just
a
peek
into
into
that.
How
open
chief
is
is
faring
in
these
are
in
these
areas
and
big
overview
for
you
like
what
open
shift
or
like
the
open
shift
ecosystem
actually
consists
of.
A
So
there
is
a
lot
of
different
red
head
portfolio
projects
and
products
that
run
on
open
shift
and
integrated
it.
There
is
a
lot
of
third
party
integrators
that
we
always
add
to
the
ecosystem,
so
that's
growing
as
well
and
as
before
the
result
Hat
Enterprise
Linux
and
the
agnostic
infrastructure
that
you
can
run
on
and,
as
you
probably
heard,
there
is
going
to
be
something
called
open
shift
for
which
is
going
to
be
the
marriage
of
technology
from
core
OS
and
the
open
shift
technology
that
we
had.
A
So
there
is
not
so
many
public
details
to
speak
about
right
now,
but
essentially
we
will
be
using
integrator
of
note
indicators,
operators
from
the
ground
up
a
lot,
and
you
will
see
that
pattern
in
the
future
way
more
and
it
will
be
very
more
eight,
automated
and
the
marketplace
will
be
more
prominent
in
the
in
the
release
and
have
you
heard
about
operators
already?
Ok,
those
who
did
not
I
have
few
slides
at
the
end.
A
So
don't
worry
we
will
get
to
that,
so
that
was
from
the
for
the
for
the
basic
ecosystem
and
business
side.
So
now,
let's
get
to
something
more
technical.
This
is
more
to
my
liking,
greater
than
those
slides
so
in
the
free
10
release
that
was
a
few
months
back
or
mountebank
a
few
months
back,
I'm,
not
sure
something
like
that.
We
really
used
all
the
features,
one
of
the
best
ones.
A
That
I
liked
was
the
support
for
device
manager
and,
as
Diane
mentioned
already,
that
we
have
a
very
active
community
among
the
machine
learning
and
a
I,
and
this
in
these
areas.
Kubernetes
is
also
doing
very
well
in
these
areas,
and
device
manager
allows
you
to
manage
your
workloads
in
the
relation
to
different
Hardware
thingies
that
you
need
for
for
equip
you
edition.
A
So
if
you
know
that
you
need
a
graphic
card
for
for
good
arithmetic,
then
OpenShift
can
schedule
your
pods
in
a
way
that
the
graphic
cards
will
be
able
to
lies
in
the
right
way,
etc.
So
it
will
not
be
just
just
the
basic
stuff
that
we
know:
memory
CPUs
and
that
have
been
there
all
the
time
and
load
balancing
cond
up
of
that.
A
But
you
can
also
manage
this
kind
of
these
kind
of
things
like
GPUs
and
utilize
them
in
your
containers,
and
it
will
also
handle
the
security
aspects
and
all
these
things
that
you
need.
If
you
do
that
or
production,
so
that's
already
there
and
for
the
future
we
will
be
providing
more
documentation
and
information
how
to
how
to
use
this
stuff
and
how
to
utilize
it
in
your
applications.
A
A
So
the
other
thing
is
that
we
are
moving
forward
with
not
breaking
docker
but
like
replacing
some
parts
of
it
in
two
different
other
products,
so
we
have
been
using
docker
since
up
since
we
released
OpenShift
free
as
a
container
technology
and
I
guess,
everybody
here
is
familiar
with
daca
right
rice,
your
hand,
if
you
are
familiar
with
it,
okay,
good
and
you
are
using
actively
dr.
containers.
Yes,
so
I
think
it's
pretty
cool
if
you
do
it
on
your
desktop.
It's
very
smooth
experience
very
nice
very
easy
to
do.
A
However,
if
you
start
doing
it
on
the
scale
of
Burnette
ease
or
openshift,
if
you
do
it
on
the
servers,
it
may
be
slightly
more
challenging
because
of
the
architecture
of
of
docker,
with
having
a
demon
with
not
real
good
separation
of
roles
and
authorizations,
and
this
kind
of
things
can
be
quite
complicated
if
you
do
it
in
production
environments.
So
for
that,
the
idea
was
to
break
down
docker,
essentially
reusing
as
much
of
the
of
the
code
that
has
been
actually
in
in
docker,
which
has
been
contributed
back
into
CN.
A
Cf
has
container
D
project
right
and
has
been
on
the
slide
Diane
had,
and
it
is
taking.
For
example,
cryo
is
the
project
that
runs
containers
in
kubernetes.
So
instead
of
having
dr.
on
the
machine
you
have
cryo
cryo
is
stripped
down
to
only
being
able
to
spin
up
a
container
and
do
it
in
the
secure
and
reasonable
life
or
production
environments.
Alright,
and
it's
integrated
directly
into
into
kubernetes.
So
you
don't
have
all
the
other
features
that
doctor
would
provide
you,
because
you
don't
need
them
for
running
containers
which
is
burning.
A
A
So
if
you
want
to
build
a
container-
and
you
would
use
builder
as
a
command
line
to
you
and
then
there
is
a
pod
man
which
is
like
trial
but
outside
of
kubernetes,
so
in
in
free
10
cryo,
is
there
I
believe
it's
supported,
but
it's
not
default
so
by
default
it
would
still
be
using
docker,
but
you
can
switch
during
the
installation
and
use
use
cryo
instead
of
the
curse.
So
cryo
will
be
there
utilizing
all
the
different
project
that
has
already
been
there,
but
you
will
not
be
running
doctor
will
be
running
cryo.
A
There
is
a
switch
in
the
inventory
file,
so
when
you
are
installing
just
open
chief
use,
cryo
equals
true
should
set
that
should
not
install
docker
but
should
install
cryo
so
bill
doc
has
been
available
since
our
l75,
yes,
and
also
it
now
supports,
move
to
stage
built
and
provides
much
more
much
higher
compatibility
with
the
doctor
files
that
are
available
in
docker.
So
pretty
much
all
the
daily
tasks
that
you
can
have
today.
A
You
can
do
with
builder
instead
of
inside
of
docker,
but
it's
a
command-line
tool
doesn't
have
the
nice
gooey
things
for
OSX,
etc.
So
it
depends
on
the
use
case.
You
have
it's
very
nice
for
automation
and
if
you
do
things
on
the
server
in
script,
it
simplifies
simplifies
things
and
all
of
the
project
builder
cryo
boatman.
A
A
Another
thing
that
has
been
in
free
10
has
been
helm
operator
so
who
is
using
helm
or
who
want
to
use
helm?
Everybody
know
almost
no
one,
okay,
so
it
was
one
of
the
big
requests
that
we
had
like
I
would
like
to
use
helm
on
OpenShift.
We
are
saying:
hey
it's
not
so
easy,
because
there
is
still
ER
and
there
was
a
component
that
you
need
to
deploy
the
helm
charts
on
on
the
cluster,
but
it
needed
like
cluster
admin,
access
to
everything.
A
So
there
was
like
single
component
that
had
access
to
everything
with
freaking
release.
There
is
a
hell
operator
that
doesn't
use
tiller,
so
you
can.
You
should
essentially
be
able
to
take
a
help
chart
and
deploy
it
using
the
helm
operator
instead
of
the
normal
helm,
tiller
thing
that
has
been
there
created
by
the
project
and
it
will
follow
all
the
our
back.
A
A
Nice
feature
also
operator:
SDK
has
been
released,
so
SDK
is
go
essentially
package
that
helps
you
to
build
operators,
so
I
will
move
the
operators
at
the
at
the
end
of
the
presentation,
but
for
the
for
the
way
future
operator
seems
to
be
one
of
the
main
and
most
important
patterns
to
design
applications
for
kubernetes
and
OpenShift,
and
the
ecosystem
is
growing
everyday.
So
getting
familiar
with
that,
it's
pretty
it's
pretty
important
and
it
you
will
see
very,
very
more
operators
in
the
future
with
openshift
okay,
so
that
was
for
free
10
release.
A
What's
my
time
very
well,
I
have
so
much
time
so,
what's
coming
in
in
the
next
releases,
who
is
using
service
catalogs
almost
no
one,
yeah
okay,
so
there
are
two
things
that
will
be
coming
for
a
service
catalog
one
is
the
automatic
injection
of
of
the
cigarettes
and
information
into
the
pots.
So
today,
if
you
do
use
service
catalog
any
provision
service,
it
will
create
a
secret
and
then
you
have
to
bind
it
to
some
specific
port
or
like
create
a
binding
manually.
A
What
will
be
possible
in
the
future
when
both
presets
are
are
released?
Essentially,
you
will
have
a
pot
press
set
and
put
press
had
said
if
there
is
spot
with
this
labels
injected
with
this
specific
secret.
So
whenever
you
create
a
secret
with
some
specific
selector,
it
is
possible
to
inject
it
into
all
the
pots
that
have
some
specific
labels.
It
will
be
automatic
and
there
will
be
no
manual
stuff
to
do
so.
A
So
essentially,
whenever
you
deploy
a
database,
you
can
say
when
my
database
is
deployed,
just
might
bind
it
to
this
application
pot
etc.
So
this
is
for
the
operation
side
or
like
developer
deployment
side,
and
also
today,
when
you
are
deploying
the
services,
the
security
aspect
of
that
is
not
so
complex
and
the
limitation
of
different
roles
who
can
deploy
what
is
not
very
well,
not
so
good
as
it
could
be.
A
There
already
are
the
endpoints
for
monitoring,
etc,
but
we
will
be
also
having
a
full
matrix
system
based
on
on
on
primitives,
and
it
will
be
complementary
complementarity
to
the
ocular
one
and
that
will
also
provide
some
other
features
like
charge,
backs
and
calculations
on
top
of
that.
So
this
is
spirit.
This
is
coming,
and
you
mean
you.
If
you
want
to,
you
will
be
able
to
use
hope.
You
learn
to
use
prom.
It
is
very
more
during
your
operations
of
the
cluster,
then
you
are
using
it
today.
A
Open
chief
do
or
audio
although
different
names,
so
this
is
a
tech
preview
of
a
tool.
Well,
tech
preview
is
maybe
which
too
strong
more
like
a
proof-of-concept
how
to
deploy
applications
on
top
of
open
shift.
So
if
you
are
a
developer
and
you
are
using
OC
client
tool,
it
may
be
a
bit
overwhelming
with
all
the
information
on
all
the
options,
all
the
stuff
that
you
can
do
with
the
cluster.
A
So
audio
tries
to
simplify
that
essentially
just
use
the
basic
English
sentences
to
do
stuff
and
you
would
not-
and
the
developer
would
not
be
not
would
not
have
to
be
so
familiar
with
kubernetes
and
just
saying
I
want
to
create
an
application.
I
want
to
add
my
some
storage
to
my
application.
I
want
to
push
my
source
code,
etc,
etc.
Instead
of
doing
OSI,
build
trigger
something
something
etc,
data
right
so
simplifying
the
lives
and
the
experience
for
for
engineers
and
now
I'm.
A
Moving
to
the
last
topic
that
I
have
in
my
presentation,
which
is
operators,
so
somebody
raised
their
hand
before
but
who
actually
used
operators
or
built
operators.
Already,
yes,
one
two
three
okay,
mostly
read
hitters
or
partners,
and
who
is
using
some
kind
of
operators
in
production
environments
or
non
production
environments
almost
no
one.
Ok!
So
what
is
an
operator
before
when
you
want
it
to
extend
kubernetes,
you
need
to
change
the
code
base,
but
I
said
it
was
involving
the
flexibility
of
kubernetes
has
been
also
evolving.
A
So
today
we
have
something
called
custom
resource
definitions,
custom.
As
you
know,
we
have
a
port.
We
have
a
service
etc,
which
is
the
definition
of
the
llamó
file
that
you
can
upload
into
YouTube
and
openshift
and
do
something
you
can
define
your
own
resources.
So,
for
example,
if
you
would
define
a
resource
called
PostgreSQL,
it
should
create
a
PostgreSQL
right.
Then
you
need
something
that
can
read.
A
Read
that
llamo
file
and
do
something
with
the
cluster
create
a
pod
created
appointment,
create
something
do
the
changes
which
is
called
controller
contour.
You
already
have
controllers
in
your
kubernetes
that
are
provided
by
the
project,
but
you
can
create
your
own
control
controllers.
So
if
you
take
C
Rd
and
you
take
D
controller
together,
it's
called
an
operator
operator
is
essentially.
This
is
how
you
define
your
resource,
and
this
is
the
tool
it
needs
to
be
running
in
the
cluster
to
make
it
happen,
actually
most
materialize.
A
The
definition
in
the
cluster
and
for
the
field,
like
the
pattern
says
that
operator
should
be
able
to
manage
everything
from
the
start
of
the
service
over
to
the
undeploy
menteur
the
service.
So
you
say,
I
I
will
stay
with
my
PostgreSQL
example.
So
I
have
Postgres
operator
running
in
my
cluster
and
I
create
a
CRD
that
says:
Postgres
replicas,
one
master
one
storage
days,
something
something
something
I
will
upload
the
TMO
file.
That
controller
sees
that
and
deploys
one
deployment
with
the
replication
controller.
Maybe
stateful
said
with
a
port
running
my
Postgres
server.
A
Now
I
want
to
update
my
my
my
PostgreSQL
server,
so
either
the
operator
will
do
it
manually
or
I
need
to
change
the
version
of
the
of
the
database
server
in
the
definition
and
the
controller
should
be
able
to
pick
up
the
change
and
do
the
update
for
me
now.
I
want
to
underplay
my
my
cluster,
so
I
will
delete
this
definition.
A
It
will
undo
everything
that
was
created,
so
the
whole
life
cycle
of
the
application
should
be
managed
to
at
changing
the
definition
and
the
contour
doing
the
work,
so
essentially
I
usually
call
it
the
operations
know-how
written
in
a
code
right.
This
is
how
do
the
control,
essentially
so
the
operator
SDK,
provides
a
tooling
ingo
that
allows
you
to
easily
write
more
easily
write
d
controllers
and
they
also
provide
two
different
things.
A
There
is
a
metal
ring
aspect,
so
if
you
want
to
do
charge
braking
stuffs
stuff,
then
you
need
to
monitor
what
was
happening
in
the
cluster.
So
that's
also
based
on
the
operator
platform
pattern
and
and
their
lifecycle
management
is
as
I
understand
it.
It's
an
operator
for
managing
operators
so
like
something
that
can
help
you
to
actually
manage
the
versions
of
the
operators
that
manage
the
applications
that
you
have
so
in
the
wild.
A
It's
it's
growing
and
different
companies
are
actually
using
operator
pattern
to
do
stuff.
So
we
see
the
adaption
happening
all
over
the
world
or
the
ecosystem
in
kubernetes
itself
in
OpenShift.
As
well
and
open
ship
is
adopting
the
the
the
pattern
for
ground
up,
so
the
future
releases
will
be
very,
very
more
based
on
on
predators
as
well,
and
so
it's
called
there's
called
something
called
operator
maturity
model.
So
over
here,
like
you
have
different
things
that
can
the
operator
can
do
so.
It
can
deploy
our
stuff.
It
can
upgrade
your
stuff.
A
It
can
handle
the
whole
lifecycle
of
application.
It
can
give
you
some
insights
and
can
manage
all
the
aspects
of
the
application
like
completely
from
the
ground
up.
So
if
you
do,
you
only
want
to
do
installation
and
the
upgrade
of
the
platform
you
can
use
the
helm
operator
essentially
and
just
use
helm
chance
to
do
that
stuff.
A
If
you
want
to
add
some
more
features
and
manage
the
whole
lifecycle
and
you
will
be
able
to
use
the
unstable
operator
and
if
you
do
also
have
like
either
some
metrics
provide
charge
based
on
this
kind
of
things,
then
you
will
need
to
go
to
the
go
as
DK
actually
write
their
code
in,
and
it
has
to
be
your
obligation
essentially
and
that's
it
I'm
still
13
minutes.
13
minutes
but
I
guess
there
could
be
some
Christians
in
the
audience.
B
Questions
I'd
also
like
to
add,
if
any
of
you
are
interested
in
creating
an
operator
or
using
an
operator,
the
operator
sig
is
really
active.
There's
a
inside
of
kubernetes
and
an
operator
sagen
openshift
has
one
and
we
meet
the
third
Friday
of
every
month,
which
is
probably
at
9:00
a.m.
my
time,
which
is
probably
Saturday
morning
your
time
or
something
crazy
like
that.
But
everything
that
we
do
we've
done
a
number
of
presentations.
People
have
walked
through
how
to
build
an
operator.
What
the
OLM
is,
the
operator
life
cycle
cycle
management.
B
All
of
that
information
is
on
the
YouTube
channel,
which
is
our
H
OpenShift
on
on
YouTube.
So
if
you
want
to
get
started
with
operators
or
you're
interested
in
it
at
all,
let
me
know
on
and
on
comments
let
OpenShift
org,
there's
a
sig
sign-up
page.
Go
to
that
and
you
will
get
you
know
added
to
the
mailing
list
for
Google
you'll
get
added
to
the
events
notification.
B
When
there
are
meetings,
it
really
is
the
next
wave
of
how
we're
going
to
automate
operations
and
make
all
of
these
things
like
databases
as
a
service
and
like
a
number
of
the
first
ones
that
are
coming
on.
Are
people
like
Postgres,
with
crunchy,
DB
and
Redis
and
Couchbase,
and
all
of
those
guys
so
you'll
see
the
the
usual
suspects
coming
on?
First,
because
those
are
the
necessities
of
life,
but
there's
a
lot
of
great
work.
B
That's
going
on
and
there's
a
great
team
of
folks
in
the
community,
not
just
from
Red
Hat
who
are
working
on
this
as
well.
So
it's
another
when
you
see
a
marketplace
cropping
up
on
kubernetes
anywhere,
it
is
going
to
be
basically
using
operators
to
to
populate
that.
So,
if
you
have
a
service,
this
is
this
is
the
place
you
should
be
studying
and
working
and
looking
at
right
now
pretty
closely.
C
A
Mean
like
operator
on
top
of
multiple
clusters,
I
have
no
idea
actually
like
he
technically.
Yes,
because
you
can
have
like
operator
is
just
an
application
that
talks
to
your
api's
right.
So
you
can
have
an
operator
that
has
access
to
multiple
clusters
and
do
it
if
that's
a
best
practice
or
good
practice
already
or
it's
not
I
am
Not
sure
right
so,
like
technically
sure,
if
it's
reasonable
to
do,
I
will
not
be
answering
that
question.
A
Might
be,
maybe
maybe
answer
but
could
be
used
for
this,
like
cross
cluster
management
of
stuff
like
their
different
tools
and
would
be
depending
on
the
use
case
you
have.
There
has
been
in
the
presentation
that
I
stole
my
slides
from
some
of
them.
There
is
some
one
slide
on
Federation,
so
you
can
also
look
into
that
and
give
it
your
customers
yeah.