►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
Three-Point-Seven
is
out
the
door
and
Steve
Spikers
was
part
of
the
product
management
team
is
going
to
give
us
a
basically
a
quick
and
dirty
very
fast
overview
of
everything
in
3.7.
You
can
ask
questions
in
the
chat
will
have
live
Q&A
at
the
end
and
we're
going
to
try
and
do
this
in
right
right
around
30
minutes,
which
is
a
lot
because
there's
tons
of
new
features
in
3.7,
so
I'm
going
to
let
Steve
get
started
and
take
it
over
there
to
you.
Thanks.
B
You
know
some
of
its
been
pushed
to
the
back,
there's
something
like
120
I
didn't
count
the
final
one
that
covers
everything
in
sort
of
detail,
but
I'm
just
going
to
hit
some
of
the
highlights,
and
so
we'll
go
with
that
through
that
in
the
next
30
minutes
feel
free
to
put
some
questions
in
the
chat.
I
know,
Diane
and
teach
are
in
the
background.
Can
I
keep
an
eye
on
that,
but
we'll
just
go
forward.
B
So
a
quick
intro
slide
as
far
as
open
shift
and
the
base
of
what
it
is
and
we
look
at
what
Red
Hat
provides
with
open
shift.
It's
it's
a
it's
kind
of
a
complete
layer
for
your
for
your
application.
You
know
from
the
standardization
down
to
a
secure
operating
system
as
far
as
Enterprise
Linux
goes
for
for
for
extracting
away
the
physical,
virtual
or
public/private.
B
The
deployment,
automation
bill,
an
automation,
number
of
services
and
the
ability
to
self-service
so
we'll
we'll
dig
into
some
of
those
first,
let's
talk
a
little
bit
about
the
timeline
and
the
roadmap.
So
typically
we
put
out
a
release
about
every
three
to
four
months
and
so
our
three
six
release.
We
we've
just
delivered
an
August.
It
seems
like
yesterday-
and
here
we
are
getting
ready
to
put
out
three
seven
and,
as
you
know,
you
can
take
the
kubernetes
distribution
number
and
add
2.0
to
it
and
you
get
the
overshift
numbers.
B
So
within
the
container
platform,
it's
our
it's
our
distribution
of
the
software
of
OpenShift
of
that,
namely
the
open,
shipped
origin,
repository
open
source
project,
and
so
what
you
look
they
through
there
and
then,
as
we
build
on
top
of
those,
was
the
main
capabilities
we've
delivered
on
it
and
around
it.
It's
really
around
enabling
some
capabilities
around
multi
cloud
services.
B
So
there's
always
this
cave
and
they'll
dig
in
more
about
what
we've
done
there
around
bringing
different
platform
services
onto
the
platform
and
better
ways
to
integrate
with
a
different
infrastructure
and
automation
for
delivering
of
that.
So
thinking
in
what
is
what
is
sort
of
the
main
pain
point
you
folks
struggled
with
in
ninety
a
lot
of
times
it's
like!
B
Well,
how
long
is
it
going
to
take
me
to
spin
up
a
VM
to
do
some
testing
on
or
to
do
some
development
on
or
what's
it
going
to
take
for
me
to
to
be
able
to
request
access
or
some
amount
of
data,
or
either
a
test
database
or
even
a
production
one?
You
know
it's
going
through
the
process.
It's
typically,
you
got
to
open
some
type
of
ticket
where
there's
service
now
or
or
whatnot
you
have
to
you
know,
clearly
identify
your
business,
the
ager,
the
request
itself
wait
weeks
months.
B
Hopefully
not
you
you
get!
The
approval
will
eventually
come
back.
You
have
something
that
is
the
credentials
you
need
to
connect
to
that
thing
and
then
hopefully
it
can
work,
and
hopefully
you
understand
how
they
inject
into
your
application.
Well,
the
whole
point
of
this
is
to
automate
that
away
right.
B
So
the
request
the
consumer
says:
hey
I,
want
a
piece
of
this
service
fills
out
the
needed
form
the
service
provider
will
receive
that
request
and
then
either
immediately
or
asynchronously
return
back
the
the
the
needed
pieces
to
to
connect
to
it
and
then
inject
it
on
that
place.
So
good
stuff,
part
of
the
that
model
is
built
off
of
a
open
API.
So
there's
a
a
multi
vendor
standardization
effort
that
has
taken
the
proven
service
broker
API.
B
They
had
been
part
of
the
Cloud
Foundry,
Service
Catalog
feature
and
a
lot
of
effort
into
kind
of
faking
it
and
really
hardening
some
of
the
definitions
around
that
API
and
then
leveraging
that
for
work
within
within
kubernetes
and
openshift.
So
what
is
the
service
broker
service
workers?
Really
it's
just
automated
standard
thing,
entry
point
into
this
service,
so
it
it's
the
one
who
Dino,
as
the
name
would
say,
broker
it's
a
conversation
between
the
Service
Catalog
are
really
the
consumer
through
the
service
catalog.
B
That
catalog
is
just
a
manifestation
of
all
the
services
that
the
service
brokers
provide,
and
then
the
service
provider
will
facilitate
that
request,
and
so
one
of
the
big
things
we've
done
in
the
three-seven
release
is
we've
completely
redone
the
user
experience.
So
when
you're
looking
at
the
initial
login,
you
will
see
a
page,
not
just
telling
you
about
hey,
you
need
to
create
a
project
or
hey
here's.
The
project.
B
You
need
to
work
with
it'll,
say:
here's
a
service
or
is
the
things
you
can
do
on
the
platform
and
also
some
additional
material
to
help
you
get
started.
So
there's
ability
to
take
a
tour,
so
it'll
just
take
a
minute
from
off
the
presentation
here
and
I'll
drop
over
to
actually
a
running
instance.
So
here
we
have
a
starter
cluster.
That's
running
3:7,
as
you
can
see,
it's
a
new
experience
but
wanted
to
I
could
take
the
guided
tour.
B
B
B
B
What
I've
done
is
I
downloaded
the
OC
command
and
I
can
do
an
OC
OC
up
and
then
I
can
point
to
the
version.
I
went
to
I
can
say,
deploy
the
Service
Catalog,
and
it's
that
simple.
It's
up
and
running
I've
done
that
already
so
I've
pre-loaded
it-
and
here
you
know,
here's
an
instance
of
of
that
running.
It
looks
just
like
what
I
just
showed
there
hosted
by
Red
Hat
as
part
of
our
online
starter
tier,
but
here
it
is
running
locally
in
my
environment,
and
so
I
can
go
to
my
project.
B
I
can
see
you
know,
I
have
different
applications
already
running.
If
things
don't
look
healthy,
whenever
reason
I
could
kick
off
a
build
and
I
can
also
see
the
great
integrated
experience.
We
have
here,
including
that
came
in
three
six.
They
all
come
together
here
and
seeing
the
things
working
to
build
logs
in
line
and
and
see
everything
I
need
to
see
at
a
glance.
B
B
So
now
you
can
take
your
open
chef's
templates
like
you've,
been
deploying
today
and
continue
to
deploy
those
applications,
we're
rolling
out
a
new
Hansel
service
broker,
which
you
can
define
a
nard
if
I
call
the
can
school,
playbook
bundle
and
we'll
deploy
that
we
demonstrated
by
the
way
back
in
right
at
summon
some
Amazon
integration,
while
we're
doing
work
to
bring
that
forward
as
well.
In
the
sense
it
is
an
open-source
broker,
API,
it's
an
open
API.
You
know
it's
in
people
can
write
their
own
brokers.
B
You
can
bring
3-part
third-party
brokers,
etc,
so
instable
service
broker.
So
this
is
a
relatively
busy
sargent
number
of
pieces,
but
it's
actually
fairly
simple
concept.
It's
really
there's
some
broker
that
pulling
content
from
a
catalogue
itself
so
some
place.
That's
got
to
hold
that
image.
That
image
is
just
basically
a
bundled
somewhere
and
they
can
provision
us
as
services,
so
that
fundal
itself
just
looks
like
a
runtime
to
execute
on
it
in
a
standard
set
of
verbs
that
mat
files
that
match
verbs.
B
So
if
you
match
it
up
to
the
open
service
broker,
API
that
different
things,
you
can
do
provision
deep
revision,
fine,
etc
and
matches
those
things
plus,
it
adds
some
capabilities
to
do
some
additional
validation,
such
as
testing.
It's
a
lot
of
good
stuff.
There
I
mentioned
the
template
service
broker,
so
that
these
are
the
flexibility
of
leveraging
the
same
interface
to
bring
it
onto
the
platform.
B
So
we
talked
about
the
initial
experience,
one
thing
and
in
highlight,
but
there's
a
neat
way
to
be
able
to
search
either
from
the
search
bar
itself.
You
can
do
it
through
the
filtered
views
down
below
there's,
there's
many
easy
ways
to
manage
giving
it
what
you
want-
and
you
know
hopefully
there's
a
lot
of
great
content
in
there.
So
you
need
to
you
need
the
search
to
find
what
you
want.
B
So
this
is
showing
the
binding
operation.
So
if
you
have
an
existing
set
of
instances,
you
can
actually
combine
them
together.
Another
great
piece
is
notification,
so
you
bring
all
of
the
notifications
under
the
single
of
bell
at
the
top,
so
we're
all
kind
of
used
to
seeing
this
now,
whether
it's
from
about
other
places
is
a
common
paradigm,
with
a
notification
and
so
now
on.
The
number
of
key
notifications
are
here
and
you
can
do
all
kinds
of
things
as
you
see,
there's
your
mark
on
red,
clear
them,
etc.
B
That
provides
a
way
to
run
a
single
node
open
shift
cluster
on
your
on
your
machine
and
allows
you
to
really
validate
how
your
application,
in
a
number
of
ways
and
one
of
the
some
of
the
different
features
that
people
monastic
or
it's
really
been
helpful,
isn't
like
a
run,
multiple
profiles
or
instances.
So
now,
I
can
easily
say
I
have
this
this
profile,
that
kind
of
matches
a
certain
set
of
applications
and
I
want
to
quickly
switch
to
a
different
type
of
profile.
Then
you
can
do
that
now
within
the
cdk,
a
minute
shift.
B
So,
let's
move
I
guess
we
will
start
at
the
top
of
the
stack.
We're
gonna
move
down
the
stack
so
we're
looking
at
like
the
orchestration
layer,
but
one
thing
I'm
just
going
to
point
to
is
that
there's
already
a
commons
webinar
that
talks
about
some
of
the
work
that's
gone
into,
kubernetes
1-7,
so
I
encourage
you
to
go.
Watch
that
and
then
also
there's
a
you
know.
Number
of
citing
project
we
can
just
want
to
highlight
was
the
custom
resource
definition.
B
So
that's
one
of
the
some
of
the
different
ways
that
extensibility
has
been
integrated
into
the
platforms
from
now.
It's
easier
to
add
capability
into
a
running
Kuby
career
day's
instance
itself,
including
encryptions
and
secrets,
within
that
CD
daemon
sets
and
upgrades
to
the
to
both
staple
sets
and
burst
mode
as
far
as
a
scale
up
it
goes.
So,
let's
take
you
that
a
little
bit
more
so
lot
of
work
around
installation
and
upgrade
improvements
around
what
we
do
with
our
interval
playbooks
that
we
should
product.
B
So
we
have
the
capability
to
migrate
at
CD,
as
it
was
before
the
three
seven
upgrading
that
can.
They
also
be
able
to
scale
out
the
at
CD
clusters.
So
it's
a
quite
important,
but
the
other
is
the
the
ability
to
have
a
more
modular
installer.
So
you
have,
though,
you
may
want
to
break
things
up
in
the
roles
and
different
playbook
so
that
you
can
target
certain
ad
hoc
administration
tasks.
B
So
a
fair
amount
of
work
has
gone
into
provide
those
capabilities
in
a
new
install
experience,
around
sort
of
breaking
breaking
up
the
the
installer
itself
into
phases,
and
so
you'll
see
that
as
well.
You
know
jumping
over
to
networking
if
you've
been
following
along,
especially
within
the
openshift
releases.
B
We've
had
no,
this
core
feature
of
a
network
policy
and
preview
for
a
couple
releases
and
and
happy
to
announce
his
coming
out
of
tech
preview,
and
so
we've
done
done
the
work
to
to
validate
it
and
actually
I'm
supported,
and
so
it's
a
great
way
to
have
really
fine
control
access
and
rules
around
or
policies
on
communication
between
the
different
services
you
have
on
the
platform.
So
in
the
past
you
would
have
the
ability
to
either
talk
all
services
within
a
given
namespace
or
you
would
have
it
open
up
across
the
cluster.
B
And
then
you
could
do
certain
things
around
joining
namespaces.
If
you
had
that
multi-tenant
STM
plugin,
which
would
pair
those
Network
those
namespace
networks
together
and
then
they
could,
you
know,
have
access
to
everything
between
those
two.
Now
you
have
the
ability
to
fine-grain,
say
this
specific
service
at
this
port
can
only
receive
incoming
traffic
from
this.
B
This
desk
this
source
itself,
so
really
a
key
a
key
feature
some
stuff
around
networking
is
we
allow
the
some
flexibility
around
the
cluster
IP
ranges,
so
it
really
allows
for
things
around
a
multiple
set,
some
knitting's
for
hosts
getting
this
request
a
lot
so
glad
to
be
able
to
provide
this.
This
is
also
a
popular
topic.
Is
reference
architectures,
and
so
we
have
a
lot
of
you
know.
B
One
of
the
great
things
about
OpenShift
is
the
ability
to
to
run
on
them
and,
as
I
mentioned,
on
bare
metal,
on
virtualized
instances
on
different
infrastructure
layers
and
through
different
configurations.
So
with
that
level
of
flexibility,
it's
it's
awesome
very
valuable
to
have
reference
architectures
and
implementation
guides
around
that.
B
So
you'll
see
as
we
put
out
releases,
we
usually
have
a
little
bit
of
time
after
released
when
we
roll
out
updates
to
these
reference
architectures,
so
those
will
be
rolling
out
as
the
release
rolls
out
as
well
or
after
they're
released
rolls
off
so
well.
That
was
a
I
did
not
do
a
dis,
a
true
coverage
of
everything.
B
B
Does
that
may
expand
the
overall
capability
of
it
and
they
expand
the
number
of
interfaces
and
then
possibly
different
attack
vectors
in
with
that
as
well,
since
we're
focused
on
that
that,
given
use
case
we're
able
to
really
focus
on
scale
and
performance
for
that
without
having
to
be
concerned
about
a
wide
variety
of
cases
there
as
well,
and
that
the
the
great
thing
about
it
is,
you
don't
have
to
change
anything.
So,
like
someone
asked
recently
well
whoa
how
I
know
it's,
the
difference
is
like
what
you
won't
I
mean
from
an
end-user.
B
It's
just
how
containers
run
in
the
background.
You
still
build
your
your
images.
The
way
you
do
today,
it'll
just
run
them
and
you'll
end
user
will
not
know
any
difference
them
they'll
notice,
better
performance
along
those
lines
is
when
you're
looking
at
how
you
build
those
containers,
you
also
want
to
have
a
solution
that
will
allow
you
to
have
minimal
dependencies
as
well
and
so
build
as
a
daemon,
less
tool
for
building
and
modifying
OCI
base
images.
B
It's
only
looking
forward
to
to
rolling
this
on,
and
so
this
is
just
in
a
preview
fashion
as
well
so
builders,
great
stuff
system,
containers
that
come
out
and
support
for
Braille,
anatomic
hosts
and
as
a
key
part
from
the
operating
system.
Update
that
can
that
open
shift
container
platform
is
actually
is,
is
using
in
a
tech
review
fashion.
So
it
allows
you
to
bootstrap
some
of
these
capabilities.
B
So
if
you
container
runtime
is
actually
running
within
the
system
container
itself,
so
it's
a
it's
a
more
flexible
way
to
be
able
to
manage
and
run
the
various
pieces
of
the
platform
and
also
allows
for
a
set
of
capabilities,
and
it's
mentioned
here.
You
know
it's
real
simple
to
to
upgrade
and
rollback
pieces
within
the
managed
by
the
system,
containers,
and
so
that
gives
that
level,
isolation
and
flexibility,
as
we've
seen
with
containerized
application.
B
It's
now
coming
at
a
lower
level
within
the
operating
system,
stack
itself,
so
I
over
achieved
and
been
shooting
down
my
cutting
down
my
slides
and
and
trying
to
get
through
the
content,
but
one
of
some
of
the
things
that
I
just
wanted
to
reiterate
is
it's.
This
is
there's
so
much
content.
I
just
didn't
want
to
take
too
much
time
to
like
cover
everything
in
a
bunch
of
detail,
but
I
also
want
to
make
sure
I
covered.
Some
of
the
key
highlights,
and
the
thing
to
to
note
is
it's:
it's
a
release
coming
out.
B
You'll
see
announcements
about
it
over
the
coming
weeks,
but
the
announcement
of
it,
the
availability
of
it.
When
you
get
your
hands
on
it,
the
fee
there's
the
ways
you
can
get
your
hands
on
it
today,
as
I
mentioned,
is,
is
hopping
into
the
bush,
with
the
github.com
overshift
origin
repository
grabbing,
the
three
7rc
release
and
playing
with
it
there.
The
other
aspect,
as
I
mentioned
you
can
go
to
OpenShift
comm
register
for
the
open
shift
online
starter.
We
are
starting
to
roll
off
of
three
seven
upgrades
here.
B
We
have
it
available
in
the
Canadian
regional
cluster
today
and
then
yeah.
There's
there's
all
these
great
ways
you
can.
You
can
always
get
your
hands
on
the
product,
that's
kind
of
early
and
see
what
it
does
and
and
also
provide
feedback
through
github
issues,
issues
the
community
forums,
openshift
Commons
many
many
good
ways
to
provide
feedback.
So
with
that
I'll
see
if
there's
any
questions,
I.
C
B
So
they
can
get
access
to
three
seven
yeah.
The
only
code
that
you
can
get
available
today
is
through
the
what's
built
through
the
open,
shipped
origin
or
repository,
and
then
the
the
actual
release
bits
as
far
as
like
when
Red
Hat
will
release
the
open
shift
container
platform.
3.7,
that's
due
out
in
a
couple
of
weeks,
as
far
as
when
those
bits
will
actually
be
available.
I.
A
B
They
were
doing
some
tech
preview
there,
so
that
is
not
so
see.
Therefore,
from
Venice
and
answer
some
of
these
were
rate.
It's
there
still
needs
to
doctor
for
some
of
the
building
aspects.
But
if
you're
looking
to
isolate
some
of
your
clothes,
I
mean
there's
always
some
a
lot
of
interesting
things.
A
D
We
take
that
Steve
go
for
it,
then
your
your
yeah
so
system
container-
all
it
is,
is
it's
still
a
regular.
You
know,
docker
container,
we
just
add
a
little
bit
of
metadata
to
the
image
and
then
we
run
it
slightly
different.
So
if
you've
done
the
existing
container
eyes
and
saucer
open
ship,
those
will
drop
the
unify
on
the
host.
We
carry
that
forward
with
system
containers.
What's
different,
though,
is
we
store
them
on
disk?
We
we
leverage
OS
tree
for
the
deduping,
so
you
know
again
the
classic
example
of
that
is.
D
If
you're
troubleshooting
a
node-
and
you
know
you
fill
up
the
darker
pool,
you
blow
that
away
with
a
system
container.
As
that
Kubb
role
or
as
the
container
runtime
role,
you
won't
blow
away.
Those
really
important
roles.
Have
you
ever
wiped
the
storage
pool
right?
So
it
gives
us
kind
of
extra
resiliency
4-bits.
He
would
you
would
classically
associate
with
being
a
part
of
the
operating
system,
but
you
could
still
iterate
and
get
all
the
advantages
of
running
and
containerized
did
that
that
kind
of
help.
A
B
B
So
yeah,
it's
a
network
policy
has
really
just
focused
at
and
I
think
to
Sharlee.
That
mentioned
it
there's
a
layer.
Three
four
aspects
were
SCO
is
layer.
Seven
really
I
mean
you
look
at
network
policy,
it's
a
declarative
model
to
define
kind
of
the
communication
path
between
the
different
services
and,
what's
a
lot
of
and
not
and
initio
itself
is
as
a
service
mesh,
which
has
a
lot
of
different
capabilities
around
policy.
B
As
far
as
like
you
know
what
network
policy
kind
of
does
and
then
also
kind
of
a
program
that
a
programmatic
kind
of
riling
aspect,
so
you
can
do
intelligent
routing,
based
on
whatever
criteria
you
define
the
program
in,
among
other
things,
like
tough
telemetry,
dilemma
tree
and
and
different
reporting
aspects
to
understand
what
the
different
you
know
usages
are
you
know?
What's
those
actual
traffic
was
being
allowed
denied,
etc?
So
yeah?
Those
are
kind
of
in
some
ways,
complimentary
and
and
also
SEO,
will
provide
a
fair,
more
capability
as
well.
B
B
That
might
be
good
developed
with
a
Lincoln
and
the
blog
post
itself,
but
I'll
start
digging
into
it.
We
we're
working
on
our
increasing
our
enable
material
we've.
We
have
someone
called
it
their
pre
alpha
version
of
even
in
a
go
SDK
to
help
end
users
when
writing
brokers
and
working
with
the
appropriate.
B
D
I'll
chime
in
on
arm
real
quick.
This
has
been
on
the
rel
side
and
and
eventually,
from
the
whole
container
platform.
I
will
say
that
we're
definitely
looking
at
at
multi
arch
being
being
on
option,
so
we
will
have
base
container
enablement
coming
up
soon
in
rel
forearm,
so
probably
around
the
75
timeframe
that
all
extras
repository
and
base
images
will
be
there.
But
then
you
know
from
there
it's
it's.
You
know
it's
a
lot
more
work
to
bring
openshift
to
it.
So,
but
you
know
that
that
first
phase
is
definitely
pretty
solidified.
A
B
Yeah,
so
the
the
Federation
roadmap
I
can
talk
about.
So
if
folks
know
and
pay
attention
the
kubernetes
community
there's
the
the
Sikh
Federation
has
been
doing
work
around
understanding.
You
know:
what's
the
right
path
forward,
how
Federation
fits
into
the
cooperate
in
these?
So
there's
a
couple
different
pieces
of
work
around
you
know:
what's
the
right
use
case,
which
is
the
right
approach
and
so
they're
doing
some
analysis
around
those
pieces.
B
A
So
I'm
gonna
my
final
pitch
here
for
questions
and
have
one
pop
it
in
the
chat,
Ryan
aspect.
The
other
thing
I
want
to
just
remind
everybody,
is
that
the
open
ship
Commons
gathering
the
face
to
face
for
all
the
upstream
project
leads
and
roadmaps
will
be
happening
on
December
5th
in
Austin
Texas
the
day
before
pucon.
A
So
if
you're
coming
to
coupon,
please
consider
registering
and
coming
for
that,
because
you'll
get
folks
from
the
engineering
team,
Clayton,
Dan
Walsh
and
while
a
number
of
the
PM's
will
be
there
as
well
as
folks
from
on
the
project
lead
for
kubernetes
and
from
Amazon
talking
about
running
up
and
shipped
on
and
on
there.
So
there'll
be
a
lot
of
good
folks
in
the
room,
as
well
as
lots
of
customer
case
studies.
So
I'd
love
to
see
you
all
come
there.
Here's
one
last
question
for
you:
for
the
open
ship
specific
add-ons
to
kubernetes.
A
B
B
So
one
is
you
know
we
published
blog
articles,
what
it
takes
to
run
to
run
helm
with
open
ship
and
so
there's
some
ways.
You
can
run
it
your
till
our
server
within
they
give
a
namespace
that
will
allow
you
to
know,
deploy
health
charts,
that's
not
something!
That's
we
don't
ship
and
support
helm,
our
helm
so
tell
her
today,
but
that's
a
you
know:
we
define
how
you
can
do
it
as
far
as
running
a
tiller
cluster
wide
server,
there's
some
considerations
there
you'd
have
to
be
aware
of.
B
If
you're
doing
that,
I
mean
it
sort
of
depends
on
your
own
deployment
and
and
and
what
you're,
okay
with
there.
As
far
as
and
what
we're
continuing
to
track
and
watch
in
the
upstream
there's
within
the
SE
gaps
around
arrays
there's,
you
know
it's
that
primary
focus
around
that
is
around
enabling
a
number
of
application.
B
Tooling,
if
you
all
around
kubernetes,
not
that
it's
there
any
given
supported,
set
of
tools
are
endorsing
one,
but
clearly
helm
is
one
that
is
as
used
widely
by
the
community
and
they're
going
through
a
process
of
defining
what
helm
three
is
and
so
we're.
You
know,
redhead
continued
to
work
in
that
community
get
to
you
to
work
with.
B
You
know
that
to
try
it
to
find
a
way
forward
to
provide
a
supportive
fashion,
a
supported
solution
as
needed
to
meet
the
customer
use
cases
so
yeah
any
feedback
there
and
we're
continue
to
look
at
it
and
evaluate
that
it
were,
and
we're
continuing
also
to
evolve
what
open,
how
we
build
open
shift
and
how
we
add
the
different
capabilities
into
kubernetes.
And
so,
as
you
look
at
the
service
catalog,
it's
actually
built
in
as
an
add-on
itself,
and
so
then.
A
B
B
We've
worked
with
the
community
to
help
build
those
things
in
and
start
to
build
new
capabilities
that
way,
but
at
the
same
time,
there's
a
cost
involved
in
time
right
to
to
move
things
to
be
more
of
this
add-on,
the
plug-in
model.
So
we're
continue
to
evaluate
those
things
and
do
what
makes
sense
based
on
our
customer
needs
there
and
how
those
add-ons
exactly
get
installed.
Whether
technology
is
home
or
something
else,
I
think
that's
still
to
be
determined.
But
since
currently
Red
Hat
doesn't
have
home
supported
solution,
I
would
have
to
see.
A
Something
at
a
close
here,
Steve.
Thank
you
very
much.
I
know
it's
like
trying
to
get
you
to
do
this
in
30
minutes
or
less
it's
impossible.
So,
thanks
for
all
the
questions
and
to
char
for
joining
us
and
then
as
well,
we
will
do
this
again
soon
and
again.
Hopefully,
you'll
all
join
us
in
Austin,
where
we
have
lots
of
engineers
in
the
room
to
answer
even
more
questions
around
3:7
before
the
blog
post
shortly.
Alright,
guys
thanks
thanks.