►
From YouTube: Self-Driving Kubernetes with OpenStack
Description
Containers are rapidly finding their way into enterprise datacenters, but change is difficult. How do enterprises transform their architecture with technologies like containers without losing the reliable components of their current solutions? In this talk we will talk about the challenges enterprises are facing today as they move to containers and discuss how CoreOS is making it easier to deploy and manage Kubernetes on any OpenStack configuration. The talk will go over how Kubernetes applicati
A
Good
afternoon,
okay
I
brushed
my
teeth.
I
took
a
shower
I'm
clean
smell
good.
Why
y'all
so
far
away
from
me?
If
you
don't
mind,
if
you
can,
it
just
make
me
feel
a
whole
lot
better.
If
y'all
came
a
little
bit
closer
just
you
don't
have
to
come
to
the
front
row
just
a
little
bit
closer.
Let
me
look
into
your
eyes.
Will
you
do
that?
For
me?
Please
pretty
please
one
knee.
What
do
I
have
to
do?
Please
just
a
little
bit
closer.
Thank
you.
I
appreciate
y'all.
Thank
you.
Thank
you.
A
We
are
family
here
in
OpenStack,
so
I
want
to
feel
like
we're
all
a
part
of
the
same
crews.
I
can
see
it
talk
to
you
interact
with
you,
how's
everybody
feeling
feeling
good
and
if
I
go
to
those
keynotes
this
morning,
that
was
pretty
exciting.
Some
exciting
happenings
in
the
keynote
definitely
enjoyed
that
have
y'all
been
attending.
Let
me
start
this,
so
I
am
from
Texas
and
in
Texas.
Y'all
is
a
real
word,
so
I
will
use
it
this
conversation.
A
A
How
many
are
using
kubernetes
and
OpenStack
two
hands:
okay,
okay,
okay,
there's
a
couple
of
you
all
good
all
right!
Well,
today
we're
going
to
talk
about
self-driving
kubernetes
on
OpenStack.
That
is
a
mouthful,
but
hopefully,
by
the
time,
I'm
finished.
You
understand
exactly
what
I'm
talking
about
all
right.
So
a
little
bit
about
me.
My
name
is
Tony
Campbell
I'm,
director
of
educational
services
at
core
OS.
A
How
many
of
you
have
heard
of
core
OS
good
nice,
all
right,
so
I'm
with
core
OS,
basically
take
care
of
traveling
around
the
world
and
teaching
people
about
kubernetes
about
containers
about
the
core.
Os
stack
before
joining
core
OS
I
spent
about
fourteen
years,
our
Rackspace,
so
I
was
at
Rackspace
when
they
founded
OpenStack
and
worked
closely
with
the
teams,
who
did
that
so
I've
been
around
the
OpenStack
community
for
a
long
time.
So
that's
why
I
want
y'all
to
stay
closer
to
me,
because
this
is
family.
This
is
my
twelfth
summit.
A
First
one
was
in
Boston
back
in
2011
for
those
of
you
who
may
not
be
familiar
with
core
OS.
So
core
OS
is
members
of
the
kubernetes
community.
We
do
a
lot
of
work
around
kubernetes
and
containers,
so
how
many
of
you
have
heard
of
at
CD
nice,
all
right
so
at
CD,
was
a
product
of
core
OS
at
CD.
For
those
who
don't
know
is
the
back
end
store
a
key
value
store,
distributed.
Key-Value
store,
that's
used
across
all
kubernetes
deployments.
A
So
if
you've
deployed
a
kubernetes
cluster,
the
state
for
that
kubernetes
cluster
itself
is
being
stored
in
at
CD.
We
also
started
the
project
called
a
rocket
I
mean
you've
heard
a
rocket
good,
so
rocket
is
a.
It
is
a
container
runtime
kind
of
like
container
deep.
So
most
people
will
use
docker
containers,
but
there's
also
rocket
containers.
A
I
said
docket
containers
because
I'm
a
derive
docker
containers,
so
there's
also
a
racket
containers
also
Claire.
So
Claire
is
an
image
security
scanning
tool
that
we
have
for
images
and
also
flannel.
So
any
of
you
are
using
the
flannel
overlay
network.
Those
are
all
projects
that
were
started
by
core
OS
along
with
a
bunch
others
if
you're
interested
go
to
our
github
account.
Take
a
look
at
that.
We
have
a
ton
of
open
source
software
available
for
you
there,
but
today
the
topic
is
self-driving
kubernetes,
self-driving
kubernetes.
A
You
got
to
let
that
roll
off
your
tongue
say
quickly,
say
self.
Yes,
driving,
kubernetes.
Okay,
these
people
over
here
self-driving
kubernetes,
I
love.
It
see
this
guy,
oh
wait
he's
with
me.
Okay,
that's
why
he
fell
out
okay,
what
is
self-driving
kubernetes,
so
this
is
an
image
from
it's
called
way.
Moe.
Now
it's
the
Google
car
right.
So
this
is
what
the
Google
car
sees
when
it's
driving
an
autonomous
vehicle.
It's
driving
the
streets.
A
Ideally
a
human
is
not
behind
the
steering
wheel,
but
this
is
what
the
car
sees.
So
it
takes
everything
and
it's
view
and
makes
images
of
it
and
pictures
of
it
and
uses
these
sensors
to
drive
the
car
right.
But
the
key
element
only
thing
you
need
to
take
away
from
the
slide
is:
ideally
the
driver
does
not
have
to
have
their
hands
on
the
steering
wheel
right.
The
car
can
drive
itself.
A
The
driver
does
not
have
to
have
his
hands
or
her
hands
on
the
steering
wheel.
Okay,
what
does
that
have
to
do
with
self-driving
kubernetes
glad?
You
all
asked
all
right
so
operators
how
many
of
your
operators
you
take
care
of
system.
You
take
care
of
infrastructure,
you
wake
up
in
the
middle
of
the
night
when
the
phone
goes
off.
Yes,
we
love,
you
all
dearly,
all
right
a
lot
of
times.
A
The
things
you
all
have
to
take
care
of
are
numerous,
so
you
got
things
like
security
patches
right,
dirty
cow
comes
out
or
whatever
the
new
exploit
is
you
got
to
get
up
and
you
got
to
patch
all
your
servers
right
and
make
sure
that
they
are
not
vulnerable
to
this
attack.
Okay,
got
your
hands
on
the
wheel,
all
right
deployments!
Developers,
how
many
developers,
in-house
developers,
software
developers,
all
right,
good
deal
software
developers
right
this
awesome
code
and
we
have
to
get
it
into
production
right.
So
we
have
to
deploy
that
code.
Writing.
A
It
is
usually
a
joy,
but
sometimes
getting
that
into
production
can
be
a
pain.
You
definitely
have
to
have
your
hands
on
the
wheel.
How
about
upgrades
all
right?
How
many
of
you
have
upgraded
an
openstack
cluster?
A
live
production
opens
that
cluster
good
times
right.
You
haven't
lived
until
you've
done
that
right.
How
about
any
kubernetes
upgrades
all
right
been
through
that
a
couple
times?
Good
right?
You
have
to
upgrade
these
servers.
What,
if
you
want
to
scale?
You
got
much
as
much
success.
You
want
scale.
A
These
servers
I
need
to
back
up
these
servers.
These
are
all
things
that
our
operators
have
to
do,
and
sometimes
our
developers
help
out,
but
they
are
with
our
hands
on
the
wheel.
We
have
to
get
in
build
tools,
pull
this
stuff
off.
What?
If
much
like,
Google's
self-driving
car,
we
had
self-driving
infrastructure.
A
A
I'll,
wait:
I'm
patient.
What
does
the
thermostat
do?
Controls
the
temperature
right?
Okay,
so
if
you're
in
your
house
and
it's
a
little
chilly
a
little
cold,
you
can
go
adjust
the
thermostat
and
the
thermostat,
through
all
its
magic
will
eventually
make
the
temperature.
Do
it
go
up
right,
you
just
down
the
temperature
goes
down,
so
the
thermostat
takes
my
desired
state.
How
warm
or
cold
I
wanted
to
be
in
the
room
and
make
it
an
actual
state.
A
That's
what
the
thermostat
does
for
us,
okay,
so
in
kubernetes
we
have
something
kind
of
similar
to
that.
We
call
them
controllers
all
right.
So
for
those
of
you,
maybe
in
robotics,
you
think
about
a
control
loop
right.
This
is
an
infinite
loop
that
just
keeps
listening
and
checking
the
state
of
the
system.
Okay
and
if
the
state
of
the
system,
if
the
actual
state
of
the
system
does
not
match
my
desired
state,
the
control
loop
will
take
the
necessary
action
to
make
my
actual
state
match.
A
A
I
will
declare
what
I
want
my
system
to
look
like
and
in
this
example,
I'm
deploying
a
simple
front-end,
and
you
see
there
the
line
one,
two,
three
four
or
five
or
six
lines
down,
says
replicas
since
I
want
three
replicas,
so
I'm
deploying
this
front-end
service.
Actually,
this
front-end
deployment
there's
a
service
attachment
not
in
this
yellow
and
then
I've
got
these
three
replicas
across
the
bottom.
A
So
my
desire
state
is
to
have
three
instances
of
this
front-end
application
and
I
tell
kubernetes
that
in
this
yamo
and
then
kubernetes
uses
its
controllers
to
make
sure
my
desired
state.
I
want
three
equals.
My
actual
state
you've
got
three
makes
sense.
All
right,
so
I
got
controllers,
that's
pretty
cool!
Okay.
What
else
do
I
need
to
if
I
want
to
get
to
self-driving
infrastructure?
Okay,
I
got
controllers
also
need
this
concept
of
self-hosted,
how
many
Verte
of
self
hosted
kubernetes
couple?
Okay,
let
me
walk
you
through
it.
A
So
here's
the
cool
thing
about
kubernetes
right,
if
I
have
an
application,
I
can
deploy
that
application
into
kubernetes
and
I
can
tell
kubernetes
how
many
replicas
I
wanted
to
have
how
I
wanted
to
scale
scale
it
up
and
scale
it
down
and
kubernetes
just
takes
care
of
that.
For
me
it
just
does
it
right,
it
just
makes
sure
the
state
is
there,
wouldn't
it
be
cool
if
I
could
dog
food
for
lack
of
a
better
word,
my
own
kubernetes?
A
What
if
I
could
use
kubernetes
to
manage
the
control
plane
of
my
kubernetes
deployment?
Okay?
So
what
are
you
talking
about?
So
there's
several
things
in
a
kubernetes
up
here
from
from
layer,
zero
up
to
layer,
four,
so
layer,
zero.
We
got
this
couplet
right
that
runs
and
then,
on
top
of
that
we
got
at
CD
right.
Then
we
have
this
API
server,
then,
on
the
row
three
there
we
have
a
scheduler
controller
manager
and
a
proxy
and
then
Row
4
is
our
add-on.
So
you
can
do
add-ons
like
around
DNS
and
other
add-ons,
ok.
A
So
what?
If
I
actually
ran
the
API
server,
Row,
2
and
Row
3,
the
scheduler
controller
manager
and
proxy,
what
if
I
actually
ran
those
as
pods
within
the
cluster
itself,
because
once
they're
in
the
cluster
as
pods,
if
I
need
to
scale
one
up,
I
use
the
kubernetes
mechanism
for
scaling
to
scale
up
my
API
pod
control
plane
or
to
recover
from
failures
on
my
control
plane.
If
it's
in
kubernetes
I
can
use
the
kubernetes
features
to
recover
from
failures
in
the
control
plane.
A
Right,
mind-blown,
crazy
right,
so
this
is
so
closely.
This
is
the
concept
of
self
hosting
we're
actually
doing
this
today
and
the
way
it
works
is
with
a
project
called
boot
code
and
by
her
to
boot,
coop
all
right,
good
couple,
boot
coop.
So
what
boot
coop
will
do
you
have
a
problem?
You
have
a
chicken-and-egg
problem
when
you
do
self
hosted
right,
so
I
want
to
run
my
control
plane
inside
my
cluster
right,
but
I
need
an
API
server
to
put
any
pods
in
the
cluster
right.
A
So
how
do
I
start
to
put
stuff
in
the
cluster
before
the
API
servers
come
up?
That's
where
boot
Kubb
comes
in,
buku
will
spin
up
temporarily
and
temporarily
play
the
role
of
your
control
plane.
So
it'll
spin
up
this
API
server
for
you
allowing
you
to
spin
up
a
self-hosted,
API
server.
Why
that
one's
waiting
and
all
the
other
control
plane
elements?
You
can
spin
those
up
place
them
in
the
cluster
and
then,
once
all
that
stuff
is
running
in
the
cluster.
A
Buku
has
done
its
job
and
it
will
shut
itself
down
and
go
away,
never
to
be
seen
again.
Ok
makes
sense,
that's
kind
of
crazy.
You
can
stay
with
you
stay
with
me.
Okay,
so
I
got
controllers
now,
which
is
cool.
I
got
this
control
loop
to
make
sure
my
desired
state
equals
my
actual
state
and
I
also
have
self-hosted.
So
oh
you
got
a
question
already
hit
me.
A
Cool
ATM,
18
I'm,
not
familiar
with
that
one,
but
buku
is
the
kubernetes
project.
This
isn't
something
that
Carlos
is
written.
This
is
a
open-source
kubernetes
project,
so
we're
not
the
only
one
self
hosting
it's
just
on
my
slide:
alright,
okay
and
then
automatic
updates.
This
is
the
next
part
right.
So
this
is
a
part
that
we
push
through
with
with
tecktonik
our
particular
project,
but
imagine
a
backup
a
little
bit.
A
So
when
core
OS
was
started,
the
founders
of
the
company
wanted
to
solve
a
big
problem
and
the
solve
the
problem
they
selected
was
making
the
internet
more
secure
and
they
figured
the
way
they
can
make.
The
internet
more
secure
is
to
make
sure
it
was
easy
to
update
so
a
lot
of
the
the
vulnerabilities
that
we
run
across
in
the
internet
simply
because
people
don't
patch
their
boxes.
So
how
do
we
make
that
easier
where
we
can
push
those
updates?
A
So
what
if
there's
a
way
I
could
automatically
have
a
channel
that
my
kubernetes
cluster
was
listening
to
and
that
I
could
push
updates
to
my
kubernetes
cluster,
either
manually
if
I
choose
to
or
automatically
where
it
would
push
these
updates
to
the
kubernetes
cluster.
Some
ops
folks,
like
whoa,
wait
a
minute.
If
you
push
yourself
to
my
cluster
automatically,
what
if
it
breaks
the
cool
thing
about
being
in
kubernetes
is
we
can
use
rollbacks?
We
can
use
canary
deployments
all
of
this
stuff.
A
We
have
in
kubernetes
to
make
sure
we
don't
stomp
ourselves
out
with
an
upgrade
interesting
that
my
friends,
you
put
it
all
together,
become
self-driving
infrastructure.
I've
got
controllers,
I
got
self-hosted,
kubernetes
and
I
got
automated
updates.
I.
Put
that
all
together,
we
package
it
at
core
OS
and
a
product
called
tectonic,
but
tectonic
has
an
installer
that
you
all
can
get
to
from
github
I'll
give
you
the
links
to
that
just
a
bit.
You
can
all
get
to
that
installer
and
github,
and
look
at
the
code
and
adapt
it
for
yourself.
A
A
A
So
there's
a
concept
in
the
kubernetes
community
called
operators,
how
many
you've
heard
of
operators,
the
software
cool,
so
an
operator
represents
a
human
operational
knowledge
in
software
that
allows
you
to
reliably
manage
an
application
set
differently.
An
operator
is
software
that
takes
all
your
know-how
as
a
human
operator
and
puts
as
much
of
it
as
possible
into
code
allowing
that
code
to
take
the
actions
that
you
would
take
at
the
human
operator.
A
So
these
operators
are
real.
There
are
a
few
built
already
and
they
are
based
upon
kubernetes
resources
and
controller
concepts
all
right.
So
this
isn't
something
outside
of
the
kubernetes
realm.
This
isn't
some
proprietary
thing.
This
is
based
upon
kubernetes
and
the
concept
kubernetes
has
around
resource
and
controllers.
These
are
applications
specific
controllers,
these
operators,
so
they
know
how
to
control
a
particular
application.
They
know
all
the
ins
and
outs
all
the
dirty
secrets,
all
the
little
tricks
of
that
application,
how
to
control
it.
It
extends
the
kubernetes
api.
A
So
it's
based
upon
the
kubernetes
api
Onix
simply
extends
it
third-party
resources
and
you
are
able
to
create,
configure
and
manage
these
instances
right
through
through
these
operators
and
the
domain.
Specific
concepts
and
knowledge
are
built
into
them.
So,
for
example,
kubernetes.
If
we
wanted
to
scale
up
an
application
in
kubernetes,
you
used
coop,
CTL
or
coop
cuddle
for
those
who
prefer
that
use
coops
ETL
and
you
do
a
scale
up.
You
tell
us
the
skeleton
geing
the
replica
set
here.
So
you
see
at
the
very
bottom
left.
A
It
says
my
desired
count
is
3
and
if
you
look
at
the
pod
to
the
right,
it
says,
I
have
one
right
now
and
I
want
to
get
to
3.
So
I
tell
coops
ETL
that
my
desired
is
3.
Coops
ETL
will
look
at
that
and
see
the
current
state
compared
to
your
desired
state
and
it'll
do
what
it
needs
to
do
to
make
sure
the
to
match.
So,
in
this
case,
it'll
count
me
up
to
3
right.
A
That's
a
simple
example
of
how
we're
able
to
use
deployments
controllers
and
whatnot
in
kubernetes,
but
why
not
do
something
other
than
just
scaling
up
so
real
world
again
we
talked
about
Etsy
D
earlier
when
we
started.
Ncd
is
the
back
in
store
for
all
kubernetes
clusters
at
core
OS
we've
created
an
Etsy
D
operator,
so
we
have
all
those
folks
to
quarrel
us
through
no
sed
inside
and
out
because
they
wrote
the
code.
They
understand
it
deeply.
A
They
have
now
built
an
operator
taking
a
lot
of
that
operational
knowledge
and
began
to
port
that
into
code
that
can
be
used
by
anyone.
So
now,
I
can
use
this
operator
for
Etsy
D
and
instead
of
doing
the
scale-up
I
can
say:
do
an
Etsy,
D
backup-
and
this
thing
knows
everything
that
has
to
happen
for
an
SE
d,
backup
how
we
maintain
quorum,
how
we
do
the
rollout
all
that
stuff
is
contained
within
the
code
and
the
code
executes
that,
for
you
we're
able
to
create
and
destroy
we're
able
to
recover
a
member.
A
You
can
do
rolling
upgrades
all
this
is
built
in
to
the
sed
operator
if
you
want
to
actually
see
the
code.
For
that
see,
the
operator
link
is
on
the
bottom
of
the
screen.
There
I'll
leave
that
for
just
a
second
for
those
who
want
to
snap
a
pic,
but
it's
not
just
that
CD,
okay,
don't
get
them.
If
you
don't
hurry
up
and
get
them
I'm
gonna
jump
in
there
with
them.
Take
a
picture
good
deal.
Y'all
are
good.
I'll
come
back
to
this
stuff
later
too
prometheus.
A
So
Prometheus
is
a
popular
monitoring
tool.
That's
used
in
the
kubernetes
community
and
other
communities.
There's
an
operator
for
Prometheus.
We
can
create
and
destroy
do
configurations.
Do
service
level
targets
for
Prometheus
monitoring
all
built
into
code
built
into
the
operators.
Snap
snap
snap
photo
photo
op
photo
op
good.
Do
all
right,
not
just
that.
There's
several
other
operators
that
are
out
there
there's
one
for
rook
one
for
elasticsearch.
We
actually
use
one
protect
tonic,
which
we'll
talk
about
in
a
bit
even
one
for
Postgres.
A
So
self-driving
kubernetes-
if
you
actually
want
to
try
this
out
use
it
yourself,
see
it
live.
There
is
an
installer
called
tectonic
the
tectonic
installer.
This
is
a
sim
stall
that
you
can
access
that
you
can
actually
use
yourself
and
it'll
deploy
this
in
what
we
call
the
tectonic
way
it
will
install
the
kubernetes
cluster
it'll,
be
secure
by
default
with
TLS
auerbach.
A
You
can
automate
the
installation
process,
you'll
be
able
to
plug
in
your
own
scripts,
CI
CD
scripts
to
automate
it.
You
can
deploy
this
on
any
infrastructure.
So
right
now
we
have
production,
support
for
Amazon
and
bare
metal,
and
we
have
free
alpha
alpha
support
for
things
like
open,
sac,
Asscher
and
we're
working
on
GCP.
Okay,
you
can
run
tectonic
on
any
operating
system,
so
core
OS
has
an
operating
system
called
container
Linux.
So
you
can
choose
that,
but
you
can
also
run
it
on
different
operating
systems.
A
It's
customizable
and
it's
a
che
by
default
cool.
Alright.
So
how
does
this
work
real,
quick?
This
is
high-level,
alright.
So
for
an
example,
if
you
choose
contain
Linux
and
you're
going
to
deploy,
you
can
deploy
kubernetes
on
top
of
OpenStack
and
a
self-driving
infrastructure
way.
The
first
thing
you
need
to
do,
if
you
do
it,
pure
our
style
you're,
going
to
take
our
operating
system,
which
is
container
Linux
nice
thing
about
container
Linux,
is
that
it
is
self
updating,
auto
updating,
just
like
we
want
the
kubernetes
cluster
to
be.
A
The
operating
system
will
auto
update
for
us,
so
you
can
use
container
Linux.
You
can
upload
that
into
glance
and
I
just
snag
the
new
glance
logo
this
morning.
Any
glance
contributors
in
here
alright.
Well,
that's
their
new
logo
there.
It
is
you
upload
that
in
now
it
is
based
upon
terraform,
hashey,
corpse,
tara,
terraform
and
your
body
heard
to
terraform
used
it
good
deal
so
spaced
upon
terraform.
A
So
we
have
a
pinned
version
of
that,
so
in
our
instructions,
you'll
grab
the
pin
version
that
we
use
okay
and
then
the
high
level
steps
are
as
simple
as
this.
You
don't
need
to
grab
all
this,
but
this
is
just
for
me
to
walk
you
through
it
you're
just
going
to
clone
down
the
repo
you're
going
to
download
and
make
the
custom
version
of
terraform,
okay
and
then
just
going
to
make
sure
that
version
of
terraform
is
running.
A
Then
you
can
pull
down
a
couple
of
flavors
for,
and
this
is
an
overloaded
term
I
know
in
the
OpenStack
community.
Flavor
means
one
thing:
I'm,
not
talking
about
that
type
of
flavor
right
now,
I'm
talking
about
a
flavor
of
the
tectonic
installer,
you
can
either
have
a
nova
flavor
or
a
neutron
flavor,
so
nova.
A
If
you
just
do
nova,
you
got
to
handle
the
networking
a
tab,
and
if
you
do
neutron,
that
means
you're
going
to
give
me
floating
ip's
and
whatnot
and
handle
all
that
okay
and
then
you
got
the
the
regular
open
our
see
stuff
down
there
at
the
bottom.
Okay,
then
I'm
just
going
to
export
export.
My
cluster
name
there's
this
variable
file.
This
terraform
variable
file,
I,
can
go
into
this
file
and
I
can
set
all
the
customizations
I
need
to
set.
A
So
this
is
where
I'm
able
to
go
into
the
installer
and
if
I
don't
like
the
way
that
core
OS
does
it
by
default,
I
can
go
in
and
tweak
it
to
my
likings
and
then
I
use
terraform
plan
which
to
basically
do
a
dry
run.
It'll
go
through
and
run
through
the
whole
script.
Do
a
dry
run,
make
sure
everything
works.
The
way
I
expect
it
to
work.
Here's
the
artifacts
are
going
to
be
built,
and
then
you
do
an
apply
and
the
ply
runs
out
and
actually
creates
the
kubernetes
cluster.
A
A
It
uses
backup
capabilities.
It
has
the
ability
to
upgrade
kubernetes
on
the
fly.
So
the
cool
thing
is,
you
can
log
into
your
console
and
there's
a
new
update
for
the
whole
kubernetes
cluster.
You
can
literally
push
a
button
and
say
yes
and
it
will
upgrade
your
kubernetes
cluster
for
you.
It's
doing
that
through
a
tectonic
operator
at
CD
operators.
That
is
doing
all
that
to
pull
together
to
pull
that
off.
A
Not
only
can
we
self
update,
auto
update
self-drive
the
kubernetes
layer,
but
if
you
are
using
container
linux,
you
can
also
do
those
updates
across
container
Linux
as
well
same
concepts
apply.
You
can
update
your
operating
systems,
so
new
vulnerability
comes
out.
Zero-Day
vulnerability
hits
you
can
go
ahead,
push
a
button,
get
all
that
push
to
your
container
Linux
updates
and
get
it
all
updated
and
pushed
without
having
a
fire
drill,
cool,
so
self-driving
kubernetes
on
top
of
OpenStack,
it's
available
for
you
to
start
playing
around
with
right.
A
Now
it's
an
alpha
version,
but
it's
an
exciting
project
to
find
a
way
to
take,
what's
been
happening
with
self
autonomous
vehicles
and
figure
out
how
we
can
apply
some
of
that
to
the
infrastructure
that
we're
running
early
days
exciting
days,
but
for
those
who,
like
living
on
the
edge,
give
it
a
shot.
Alright,
so
we'll
see
you
on
the
road
but
boom
boom.
That
was
a
pun.
No
all
right!
So
y'all
got
it.
Arrr
I'll
see
you
at
the
booth.
A
B
A
C
A
So
you
can
either
set
it
to
either
stable
release
or
if
you
want
to
be
on
the
bleeding
edge,
you
can
be
out
for
release
and
basically,
what
we're
doing
is
we're
doing
rolling
updates
in
the
cluster,
so
you're
taking
a
new
release,
you're
deploying
it
all
new
pods
checking
it
making
sure
those
pods
are
working
good
and
then
you're
shutting
down
the
old
pods
and
having
the
new
pods
run.
I
can
go
into
way
more
detail
than
that.
But,
okay,
that
gets
you
kind
of
very
wet.
You
bet.
D
A
D
A
Coming
back
to
itself
correct
yeah,
so
now
you're
not
running
just
one.
So
if
you
have
just
one
you're
going
to
be
in
trouble
right,
but
you're
already
gonna
be
running,
multiple
API
servers
right
and
again
load
balance
for
you
behind
a
service
right.
So
you
come
back
and
gonna
hit
that
service
API
service
and
then
the
different
knows
one
of
the
knows
behind.
It
will
answer
it
and
then
begin
that
process
Skelly
out,
but
in.
D
A
A
A
Well,
I
appreciate
you
all
sitting
closer
I
appreciate
your
attention.
I
know
it's
right
before
lunch,
so
that
means
a
lot
to
me.
That
y'all
came
to
see
me
before
lunch.
I
know
you're
pretty
hungry,
but
come
see
me
at
the
booth.
If
you're
interested
in
chatting
offline,
please
reach
out
to
me
my
contact
information.
Is
there
y'all
been
a
blast?
Hope
you
enjoy
the
rest
of
the
show,
take
care.