►
Description
Contain yourselves, as A Cloud Guru has just launched our brand new series, Kubernetes This Month! This show will bring you the latest and the greatest from the Kubernetes world, to make sure you’re kept up-to-date. In our inaugural Kubernetes This Month episode, we introduce the structure of the show, run through some key announcements and go in-depth in some of the bigger features and releases. Finally, we announce our very first (but certainly not last) Kubernetes Guru of the Month competition!
Guru of the Month Question (June):
http://facebook.com/acloudguru
Kubernetes Deep Dive (ACG Course):
https://acloud.guru/learn/kubernetes-deep-dive
KubeCon + CloudNativeCon Barcelona 2019 Recap Video:
https://www.youtube.com/watch?v=iGbAdyOKKhc
Kubernetes 1.14 Windows Nodes GA:
bit.ly/2HVgR4g
Digital Ocean Kubernetes:
https://www.digitalocean.com/products/kubernetes/
Service Mesh Hub:
https://www.solo.io/
Service Mesh Interface:
https://smi-spec.io/
Helm 3:
https://helm.sh/
Follow Nigel on Twitter:
https://twitter.com/nigelpoulton
Follow us on Facebook!
http://facebook.com/acloudguru
Follow us on Twitter!
https://twitter.com/acloudguru
A
A
The
show
is
going
to
look
like
this.
We'll
start
each
episode
with
a
quick
catch-up
section.
This
is
where
we
run
through
the
major
announcements:
it'll
be
quick
fire
with
the
aim
being
to
make
sure
you're
at
least
aware
of
what's
been
going
on,
then
we'll
run
a
deep
dive
section
where
we'll
dive
a
bit
deeper
into
a
couple
of
the
announcements,
then
we'll
finish
each
show
with
our
kubernetes
guru
of
the
month
section.
A
This
made
it
the
biggest
cube
con
Europe's
ever
seen,
and
it
gives
us
an
idea
of
the
kind
of
growth
of
communities
experiencing
we're,
also
hot,
on
the
heels
of
the
kubernetes
1.14
release.
So
if
you're
looking
for
the
latest
and
greatest
kubernetes
1.14
is
where
that's
currently
at,
though,
of
course
this
is
the
bleeding
edge
and
you
probably
want
to
give
it
a
chance
to
settle
a
bit,
certainly
before
running
it
in
production
and
on
that
point
actually,
we've
started
seeing
kubernetes
1.13
appearing
on
some
of
them
managed
kubernetes
platforms
as
an
example.
A
Google
kubernetes
engine
is
letting
you
run
as
new
as
one
dot
13.6
back
to
1.14.
For
a
second,
though,
probably
the
biggest
thing
to
come
with,
that
was
the
general
availability
of
windows
nodes,
so
Windows
is
obviously
hugely
important
in
the
cloud
negative
world
and
as
of
kubernetes
1.14
windows,
servers
can
now
be
joined
to
kubernetes
clusters
as
worker
nodes.
An
important
announcement
from
cube
con
was
the
service
mesh
interface
or
SMI.
A
If
you
like
your
economies,
will
we
finally
be
getting
some
stability
in
the
service
mesh
space
more
on
that
in
just
a
minute,
a
favorite
project
of
mine,
though
virtual
cubelet
hit
the
1.0
milestone.
So
huge?
Congratulations
to
everyone
behind
that
and
if
you're
like
me
and
your
dream
of
nodelist
kubernetes
clusters
go
check
it
out,
it
is
exciting
stuff.
Congratulations
as
well
to
the
folks
behind
the
kubernetes
extension
for
visual
studio
code.
This
also
got
a
1-0
release.
A
We've
got
an
alpha
release
of
Hound,
3
Google
has
announced
gke
sandbox
and,
as
the
name
suggests,
this
is
a
feature
of
the
google
kubernetes
engine
and
it
offers
better
workload.
Isolation
based
on
the
G,
Weiser,
runtime,
very
cool
stuff
and
finally,
for
this
month's
catch-up,
digitalocean
announced
general
availability
of
its
own
hosted
kubernetes
service,
simply
called
digitalocean,
kubernetes
and
interestingly
they'll
be
making
kubernetes
1.14
immediately
available,
which
I
like
ok
to
dig
a
little
bit
deeper
into
some
of
those
announcements
in
our
deeper
dive
sections.
A
In
this
month's,
deeper
dive
section
will
pick
up
on
three
things:
kubernetes
1.14
the
service,
mesh
interface,
specification
and
town
3,
and
will
do
them
in
that
order.
It's
fair
to
say
that
kubernetes
has
a
reputation
as
a
melting
pot
of
innovation
and
that's
great,
but
innovation.
Kubernetes
style
generally
means
a
ton
of
change.
Only
you
know
what
kubernetes
1.14
feels
different
I
was
almost
disappointed
on
the
cool
new
features
front.
A
Instead,
we
got
what
almost
feels
like
a
long
term
stable
release,
which,
if
you
know,
technologies
like
a
bunch
of
Linux
every
couple
of
years,
you
get
a
special
release,
that's
tagged
as
stable
and
you
can
rely
on
it
and
build
on
it
for
a
long
time.
In
no
way
am
I,
saying
kubernetes
1.14
is
a
long
term
stable,
but
I
am
saying
it's
feeling
a
lot
like
we're
in
a
period
of
stabilization.
A
In
fact,
a
lot
of
the
recent
kubernetes
releases
have
had
this
stability
and
maturity
feel
to
them
so
less
of
the
crazy
new
stuff
and
more
of
this
stability
and
GA
stuff,
which
is
good,
especially
from
an
adoption
perspective
like
if
you're
a
company
looking
at
maybe
deploying
kubernetes,
and
you
start
seeing
lots
of
stable
features
and
the
likes
you're
gonna
be
more
likely
to
deploy.
So
is
kubernetes
entering
a
phase
of
stability.
A
Well,
I
guess
only
time
will
tell,
but
it
certainly
feels
like
the
relentless
pace
of
innovation
is
starting
to
be
matched
by
a
phase
of
relentless
stabilization.
I
like
that.
But
as
well
as
recent
kubernetes
releases,
there
was
a
similar
feel
to
cube
con
in
Barcelona
I
mean
I
personally
felt
a
little
bit
let
down
on
the
announcement
fronts
only
to
be
reminded,
though,
by
the
community
that
technologies
like
kubernetes
are
supposed
to
be
boring
and
they're
right,
of
course,
boring
being
another
way
of
saying,
stable
and
reliable.
A
Anyway,
kubernetes
1.14
gave
us
general
availability
of
windows
nodes,
but
aside
from
that,
it
felt
a
lot
like
stability,
stability,
stability,
sticking
with
the
stability
theme
service,
meshes
yeah,
there's
two
things:
I
bet
you
never
thought
you'd
hear
in
the
same
sentence:
well,
we're
not
there
yet,
but
service
measures
may
be
in
the
process
of
taking
a
giant
step
in
the
direction
of
stability.
So
I
think
a
lot
of
us
probably
recognize
that
service
mesh
technologies
are
promising
a
lot
and
they're
going
to
be
key.
A
As
we
move
towards
cloud
native
architectures
I
mean
not
only
are
they
solving
a
bunch
of
the
application
networking
challenges?
We
already
have
they're
opening
up
a
whole
new
world
of
things
that
maybe
we
never
even
thought
of,
and
that's
great
null,
but
the
landscape
is
confusing
like
which
service
mesh
do
I
choose.
Does
it
need
to
be
a
CNC
F
project?
Does
it
need
to
use
envoy
there's
just
too
many
decisions
and
then,
when
you've
finally
decided,
the
learning
curve
is
steep
like
practically
vertical,
none
of
which
is
good
anyway.
A
Add
a
keynote
at
Q
Khan
in
Barcelona
gave
Monroy
from
Microsoft
announced
the
service
mesh
interface,
the
short
and
skinny.
We
might
be
just
about
to
get
some
standards
in
the
service
mesh
space
now,
if
you're
not
playing
with
a
service
mesh
at
the
moment,
but
you
know
you're,
kubernetes,
think
of
SMI
as
being
like
the
CRI,
the
CNI
or
the
CSI
yeah
just
for
service
meshes.
A
So
with
that
I
mean
a
standardized
API
that
mesh
providers
interface
with
making
it
easier
for
users
to
implement
measures
and
easier
to
swap
them
in
and
out,
all
of
which
is
good
and
should
drive
adoption.
Now,
it's
early
days,
of
course,
but
we've
already
got
off.
First
reference
implementations
from
solo
IO
with
their
super
glue
and
their
service
mesh
hub
products,
so
go
check
out
those
guys
and
also
check
out
SMI
spec
for
the
actual
spec
and
some
basic
info
and
finally,
for
our
deep
dive,
section,
helm,
3,
the
de
facto
kubernetes
package
manager.
A
Currently,
those
of
us
using
helm
will
be
using
helm
2,
but
the
project
in
the
process
of
overhauling
its
internals
and
all
of
that's
happening
under
the
umbrella
of
helm,
3
which,
as
we
said,
got
an
alpha
release.
So
an
important
milestone
and
congratulations
to
everyone
involved.
Alpha
releases
tend
to
be
a
bit
hairy
and
they're,
definitely
not
for
production.
A
A
And
on
that
note,
let's
move
on
to
our
first-ever
kubernetes
guru
of
the
month
segment.
Now
with
this
being
the
inaugural
episode
of
the
show,
there's
no
winner
from
last
month,
but
it
does
mean
you
get
the
chance
of
being
the
first
ever
kubernetes
guru
of
the
month.
So
here
we
go.
We've
posted
a
question
on
our
Facebook
page
here
and
if
you
think
you
know
the
answer
get
typing
and
you
know
what
wrong
answers
are
allowed.