►
From YouTube: Upgrading Kubernetes - Kelsey Hightower & Brian Walden
Description
Recorded on Feburary 25th, 2015 at the Kubernetes Gathering in San Francisco, CA, USA
A
Next
presentation,
I'm
kelsey
hightower
again
from
coreos,
and
this
is
an
engineer
formerly
known
as
walden.
He
doesn't
like
us
to
use
his
government
name,
I'm
not
sure
why,
and
what
we're
going
to
do
is
demo
upgrading
the
full
kubernetes
stack
right.
So
once
you
get
kubernetes
deployed
out
in
your
cluster,
how
can
you
upgrade
it
to
the
next
version
of
kubernetes
right?
So
this
is
one
of
the
discussion
topics
we
have
within
the
team
is
how
do
you
manage
kubernetes
itself
so
core
os
by
design?
A
So
what
we're
going
to
see
today
is
we're
going
to
use
we've
actually
packaged
up
all
the
kubernetes
components
using
rocket
so
rocket
is
our
container
runtime
engine
and
we
have
all
the
components
in
rocket
and
we're
going
to
use
fleet
to
deploy
kubernetes
on
top
of
rocket
and
we're
going
to
walk
through
using
the
omaha
protocol
through
core
update
to
refresh
the
stack.
So
I'm
going
to
turn
it
over
to
walden
and
he's
going
to
walk
us
through
that
process.
B
Thanks
kelsey,
so
as
kelsey
said,
and
we
have
kubernetes
deployed
here
with
rocket
and
fleet,
I
mean,
if
you
don't
know
what
fleet
is
it's
a
distributed
internet
system
just
like
it
says
up
there
we're
not
going
to
dig
into
it
too
far.
It
runs
system
to
unit
files.
B
I
know
systemd
is
kind
of
a
dirty
word,
but
it's
coming
so
get
over
it.
So
everybody's
run
kubernetes
before
we've
all
run
the
guestbook
apps.
Just
something
simple
that
I
can
set
up
an
ssh
tunnel
into
my
local
cluster
and
then
then
hit
some
silly
port
and
get
hello
there
version
1.0.
So
there's
something
running
somewhere
on
my
laptop.
Can
you
see
that
okay
yeah
sort
of
anywho,
so
we've
got
kubernetes
cluster
running?
If
you
believe
me,
it's
there
to
prove
it
cube.
Ctl
list.
Minions,
oh
get
minions
there.
B
It
is
so
we've
got
three
node
cluster
got
stuff
running
in
it.
We've
got
replication
controllers,
we've
got
pods,
we've
got
services,
things
are
there
so
going
back
to
what
this
little
app
was.
You
can
clearly
see
there's
this
thing
called
hello.
B
I've
just
got
an
ssh
tunnel
set
up,
so
I
can
hit
this
service
port
and
see
something
happening
so,
as
kelsey
kelsey
said
earlier,
we're
actually
more
interested
in
the
the
upgrade
strategy
for
kubernetes.
I
know
there's
been
a
lot
of
discussion
around
this
as
far
as
how
upgrades
should
work.
Should
it
be
turtles
all
the
way
down.
Should
it
be
two
separate
tools?
B
If
you
don't
know
we're
core
os,
we
build
an
operating
system,
it's
really
small,
it's
great!
It
keeps
you
secure
from
poodle
heartbleed,
whatever
the
next
vulnerability
is
going
to
be,
but
we've
built
this
tool
to
help
manage
our
entire
deployment
deployment
of
coreos.
So
core
update
is
using
sorry.
The
product
is
called
core
update.
It
uses
something
called
the
omaha
protocol.
Omaha
protocol
is
what
I
don't
know.
B
B
So
going
back
to
this
dashboard
here,
this
is
not
a
kubernetes
dashboard.
This
is
a
core
update,
dashboard,
so
you're
not
going
to
see
pods
you're
not
going
to
see
services
you're
going
to
see
three
important
things:
there's
core
os
the
operating
system,
there's
kubernetes
the
the
thing
we're
all
here
to
talk
about,
and
then
there's
this
thing
called
hello
world
and
if
you
haven't
connected
the
dots
yet
there's
something
saying
hello
to
me
right
here.
B
We
should
be
able
to
see
statistics
about
what
versions
are
running
out
in
the
world.
We
should
have
some
level
of
control
over
what's
running
in
the
world
right
here,
see
I'm
sorry.
This
is
kind
of
hard
to
see.
You
see
this
little
number
right
here.
Oh
wow,
it's
0.10.1,
that's
the
it's
two
tags
back
in
the
kubernetes
tree,
so
we've
got
a
cluster
running
version.
0.10.1
like
I
said
this
is
an
update
dashboard.
So
you
should
be
able
to
update
something
I'm
going
to
first
prove
this
is
actually
running.
B
0.10.1
run
my
little
cube,
ctl
version
tool
and
there
it
is
server
version,
major,
zero,
minor
10..
So
there's
something
happening
here.
I
go
in
and
actually
run
my
upgrade
it's
as
simple
as
again
sorry
for
the
resolution
clicking
0.11.0,
which
is
the
next
version,
saving
it
and
then
something
happens.
I
don't
know
what.
So,
if
we
dig
into
it
a
little
bit
further
right
now,
we
still
have
it
says
10.
B
This
is
dumb
data
from
before,
when
I
was
trying
to
get
this
demo
working
hiding
in
the
room
over
there,
we
see
0.10.1
cube
ctl
version
like
well.
The
api
server
isn't
up,
apparently
there's
nothing
serving
my
requests.
So
if
we
sit
here
long
enough,
we'll
actually
come
back
up
with
version
0.10.,
I'm
sorry
0.11.0.