►
Description
Join best-selling author Nigel Poulton and learn what Kubernetes is, why it's central to the future of cloud-native infrastructure and applications, and what it means to your career. The live session will include live Q&A where all questions are good questions.
A
Hey
folks,
welcome
back
from
break,
I
hope
you
all
managed
to
get
a
coffee
or
tea.
Whatever
your
choice
is
now
we
are
moving
over
to
so
there's
been
a
slight
change
of
the
agenda.
Hopefully,
you've
all
noticed
that
so
we're
staying
with
just
one
track
from
track,
one
for
now
it'll
split
onto
two
tracks
at
12
15,
due
to
as
paula
said
earlier,
due
to
one
of
our
speakers,
unfortunately
being
ill.
So
now
it's
it's.
A
You
know
really
looking
forward
to
introducing
nigel
paulton
who's
gonna
have
a
bit
of
a
what
we're
calling
an
ana
asked,
nigel
anything,
but
just
to
keep
him
in
track.
We've
got
our
own
adrian
mueller
who's
gonna,
be
there
to
keeping
me
keep
him
in
order
and
keep
an
eye
on
questions
and
stuff.
So
really
looking
forward
to
that.
Listening
to
this
chat
with
with
two
guys.
C
Okay,
so
I
think
that
was
my
cue
and
I
completely
missed
it.
I
didn't
yeah
we're
all
good
yeah.
It's
like
we've!
Never
ever
done
this
before
eh
yeah
welcome
to
nigel,
so
nigel
poulton,
I'm
not
sure
you
need
much
for
introduction,
author
trainer,
perhaps
most
famous
for
the
kubernetes
book,
and
I
think
that's
actually
a
good
place
to
start,
because
I
have
written
a
book
myself.
C
So
I'm
aware
of
how
much
work
it
is,
but
I
think
the
fantastic
thing
he's
done
with
like
the
kubernetes
book
and
the
docker
book
and
so
on
is
that
you've
kept
it
up
to
date.
So
you
did
a
lot
of
work
continuously
updating
it,
and
I
just
wonder
if
you
want
to
talk
about
that
for
a
second
then,
and
what
that
was
like
and
how
much
work
it
takes.
B
Yeah
absolutely
mate,
it's
it's
an
absolute
pain
in
the
rear
end
to
keep
up
to
date.
I
say
to
people
all
the
time
right
that
I
would
absolutely
love
to
write
a
book
about
technology
that
you
can
stick
on
the
shelf
or
on
amazon
or
whatever
yeah
and
it'd
be
relevant
for
five
years,
because
it's
so
much
effort
to
actually
write
a
book,
but
something
like
kubernetes.
I
I
do
feel
it's
changing
a
little
bit
right,
but
something
like
kubernetes
and
containers
and
stuff
that
just
seems
to
iterate.
B
So
fast,
it's
really
hard
work.
So
I
know
when
I
first
released
the
kubernetes
book.
I
I
think
it
might
have
been
the
first
book
on
kubernetes.
I
can't
remember
it
was
certainly
first
or
second,
and
so
was
my
docker
book,
but
when
I
released
it
originally
had
fifteen
thousand
words.
So
one
five
thousand-
and
I
was
update
well
the
first
year.
I
think
I
updated
it
three
times
and
then
I
was
updating
it
twice
a
year
and
now
I'm
on
to
just
annual
updates.
B
B
Because,
again,
I'm
only
talking
about
things
that
are
stable,
I
mean
like
look,
you
would
know,
and
everybody
on
the
call
will
know
that
if
we
were
to
try
and
cover
in
books
everything
that
kubernetes
does
like.
I
don't
know
it
would
make
the
collected
works
of
shakespeare
or
whatever
looks
small
and
interesting
as
well.
B
So
yeah,
it's
fun
to
write
a
book,
because
you
know
you
get
to
interact
with
a
lot
of
people
and
you
get
to
influence
a
lot
of
people's
lives
and
careers,
and
that's
really
that's
what
it
can
be
a
special
thing
in
a
humble
way,
but
it
it
was
originally
painful.
Writing
a
kubernetes
book
and
keeping
it
up
to
date
and
it's
it
still
kind
of
is,
but
it's
not
as
bad
as
it
used
to
be.
That's
for
sure,
yeah
yeah.
C
D
C
B
Yeah
so
make
sure
I
share
the
right
screen
so
desktop
number
two
here
you
should
see
my
slide
yeah
getting
started
with
kubernetes.
Ask
me
anything,
I'm
assuming
that
we
see
that
let's
have
the
feedback.
If
you
don't
I'm
going
to
just
move
on
one
slide,
though
so,
basically
for
this
presentation
it
is
yeah,
it's
an
ask
nigel
and
thing,
but
it's
actually
adrian
doesn't
really
know
this.
It's
an
ask
nigel
and
adrian
anything.
B
Now
we
have
had
some
questions
coming
from
twitter
and
on
linkedin
already,
however,
we've
got
some
places
that
you
can
ask
more
questions
right
now
at
the
bottom,
so
I'm
going
to
move
it
on
another
slide.
So
this
is
me
I
I've
written
some
docker
and
kubernetes
books,
we've
kind
of
talked
about
them.
You
can
get
them
everywhere
that
you
would
expect
to
be
able
to
get
a
book.
I
don't
want
really
the
focus
to
be
on
that.
B
I
want
it
to
be
on
asking
the
questions,
so
I'm
just
going
to
slide
it
on
to
the
first
question-
and
I
am
like
I'm
super
interested
in
your
take
on
all
of
these
as
well
adrian.
We
can
make
it
like,
you
know,
we're
off
in
a
chat
and
everybody
else
is
involved
in
the
chat.
By
asking
the
questions,
I
know
that
you've
got
to
kind
of
monitor
the
different
channels
and
stuff,
maybe
a
little
bit
closer
than
I've
got
to,
but
we
had
somebody
ask,
will
kubernetes
be
easy.
B
I
didn't
put
who's
asked
this
one.
Actually,
maybe
I
made
a
note
of
it.
I
know
I
didn't
for
that
one.
So
I
know
when
I
talked
about
the
book
there.
We
said
that,
like
at
least
writing
the
book
is
easier
because
kubernetes
as
a
project
has
got
more
stable,
but
I
think
to
this
question,
there's
like
there's
so
many
angles.
B
The
first
one
that
I
always
used
to
sort
of
struggle
with
is
like
getting
kubernetes
like.
If
you
wanted
to
build
it
yourself,
diy
kubernetes,
that
that
was
always
really
hard,
and
I
always
felt
like
you
almost
needed
to
be
a
linux
kernel
engineer
to
be
able
to
build
like
a
production
grade,
kubernetes
cluster.
B
I
feel
like
the
hosted
options
on
all
of
the
different
clouds
that
we
have
out.
There
now
really
made
on
ramping
to
kubernetes
or
getting
it
in
the
first
place
or
getting
a
production
grade.
Kubernetes
cluster
and
I
use
I
always
use
production
grade
in
air
quotes
because
it
means
different
things
for
different
people
and,
but
I
feel
like
getting
kubernetes
now
is
way
way
easier
than
it
used
to
be.
But
I
still
feel
like
we're
not
where
we
need
to
be.
B
C
B
C
You
I
think,
you're
spot
on,
like
if
you
use
like
aws
or
gcp,
and
you
know,
they've
got
the
manage
things
like
jk
and
so
on.
It's
relatively
straightforward,
but
what's
really
hard,
it's
like
the
main,
ongoing
maintenance,
yeah,
and
that's
why
google
has
autopilot
they
called
it.
I
can't
remember
and
to
be
honest,
the
main
thing
I
see
in
the
complexity.
It's
just
kubernetes
tries
to
be
everything
to
everybody.
D
C
It's
got
so
many
use
cases
it
covers,
so
I
don't
think
communities
itself
will
ever
be
easy,
but
I
think
what
we
might
start
seeing
is
like
platforms
on
top.
So
I
think
a
lot
of
enterprises-
and
I
think
this
is
already
happening.
You
see
enterprises
with
their
own
platform
as
a
service.
Basically,
so
they.
B
B
B
This
cloud
native
way
becomes
their
way
to
write
them
and
and
they're,
not
thinking
about
like
how
do
I
hook
it
into
kubernetes
and
there's
not
like
necessarily
this
big
infrastructure
team.
That's
like
we're
constantly
managing
the
kubernetes
layer.
I
just
I
feel
like,
and
we're
really
not
there
yet,
but
we
are
aiming
to
a
point
where
maybe
it's
a
spin
on
the
you
know
and
kubernetes
needs
to
be
boring
as
in
yet
just
there
and
it
just
works,
and
it's
maybe
installed
as
part
of
something
else
or
or
what
have
you.
B
They're,
always
asking
like
you
know
what
what
what's
my
biggest
challenges
when
I
come
to
deploy
it
and
and
how
do
I
have
to
retrain
my
teams,
not
from
an
infrastructure
perspective
but
like
to
think
about
how
to
you
know,
develop
and
refactor
those
existing
applications
and
new
applications,
because
it
is
like
this
there's
an
infrastructure
side
of
it.
You've
got
to
be
able
to
to
have
like
that
high
performance,
highly
available
infrastructure
layer
that
kubernetes
is
a
big
part
of,
but
then
you've
also
got
to
be
able
to
have.
B
Your
teams
write
the
applications
to
fit
that,
because
I
know
that
docker
did
this
a
while
ago,
with
the
ability
to
or
like
a
service
to
port,
like
your
legacy,
monolithic
applications
in
place
and
run
them
on
docker
and
you've
got
like
some
benefits
doing
that,
but
to
get
the
full
benefits.
It
is
like
really
a
rethink
of
how
you
do
your
applications
and
that
that
still
seems
hard
to
me,
certainly
for
enterprises
they're
like
how
do
we
do
that?
What
what?
B
C
B
C
B
Right
so
excuse
any
potential
typos
that
come
here
right,
whoops,
wrong,
slide
yeah
and
we
got
one
on
that
slide.
Yeah,
yeah,
yeah,
you've,
okay,
see
that
I'm
not
sure
how
well
this
is
going
to
work
we're
about
to
find
out
here
we
go
right.
If
I
go
present
again,
hopefully
everybody
should
see,
then
so
what
what
kind
of
change
your
feature
would
trigger
a
2.0
release.
B
So
I'm
going
to
give
my
like
really
easy
answer
here
right
like
hopefully
nothing
ever
just
because
it
sounds
like
such
a
well
look
a
move
to
a
and
I'm
assuming
we're
talking
like.
Instead
of
going
kubernetes,
1.22
1.23,
we
decided
at
some
point.
This
is
going
to
be
kubernetes
2.0,
and
that
sounds
like
such
a
horrific
breaks.
Everything
type
release
that
I
don't
think
anybody
wants
it
and
it's
a
funny
thing
look.
I
could
be
totally
wrong
now.
B
B
I
know
it's
not
quite
the
same
right,
but
going
from
whatever
it
was:
windows,
vista
to
windows,
8
or
windows,
10
or
whatever.
I
could
never
find
the
control
panel
or
the
printer
and
things
like
that,
and
that's
a
it's
a
bit
of
a
pain.
Okay,
but
when
you're
running
line
of
business
applications
on
such
a
an
important
platform
as
kubernetes
is
becoming.
B
If
your
applications
suddenly
can't
find
the
control
panel
of
the
printer,
you
know
what
I
mean
right:
the
apis
and
things
that
have
changed
so
much
that
you
have
a
hell
of
a
lot
of
work
to
put
in
to
make
your
applications
work.
I
don't
know
what
the
appetite
is
for
that
and
I
had
you
know
I
came
into
the
world
of
containers
and
kubernetes
and
thinking
myself,
like
you
know,
when
will
we
get
a
2.0?
B
So
I
think
it's
almost
a
mindset
change
to
say
that
something
as
fundamental
as
this
for,
like
a
kubernetes,
2.0
and
look,
I
could
look
like
a
fool
here
and
we
could
get
kubernetes
2.0
next
year
and
if
that
happens
then
I'll
be
trolling
the
internet
and
deleting
every
comment
of
me
saying
this,
but
I
just
almost
feel
like
that's.
That's
just
not
the
way
we'll
go
going
forward
and
feel
free
to
disagree
with
with
me.
I
don't
know
what
you
think
on
that.
C
Yeah,
I
think,
that's
a
pretty
reasonable
point
of
view.
There's
a
couple
of
things
there,
one
I'm
not!
I
I'd
have
to
ask
a
kubernetes.
You
know
core
developer,
exactly
what
the
you
know.
The
different
releases
actually
signify,
but
at
the
same
time
we
do
want
to.
You
know,
allow
space
for
innovation
and
change.
I
suspect,
like
kubernetes
2.0
would,
you
know,
might
end
up
being
a
completely
different
product.
Yeah.
B
Can
you
imagine
see,
I
do
think
there
is
space
for
that
innovation
and
new
things,
with
the
way
that
individual
apis
within
kubernetes,
like
pods
or
services,
or
the
gateway
api,
or
things
like
that
they
can
iterate
almost
at
their
own
cadence
and-
and
we
know
that
within
kubernetes
you
can
run
different
versions
of
the
api
four
different
features
like
we
had
like.
For
instance,
I
think
that
deployment
is
a
really
common
one
as
well.
B
That's
been
v1
for
a
while,
but
it
was
like
v1
beta,
1
and
v1
beta
2
were
all
still
available
within
kubernetes
for
like
the
longest
time.
So
it's
a
it's
a
great
question.
I
I
still
hope
to.
Hopefully
nothing
will
ever
take
us
to
that
point,
but
we'll
see
if
we
could
make
it
smooth,
then
I
wouldn't
whoops.
Then
I
wouldn't
be
worried.
C
A
B
B
So
I
I
certainly
I
don't
see
kubernetes
going
away
and
I
think
that's
important
for
anybody
that
is
looking
to
get
started
like
as
an
individual
if
you're
thinking
is
kubernetes
a
good
thing
for
me
to
bet
my
career
on,
as
in
like
do,
I
want
to
put
in
the
time
and
and
potentially
money
to
invest
in
kubernetes
skills.
I
think
you're
fairly
safe
there,
because
there's
such
a
strong
ecosystem
and
all
of
the
major
cloud
providers
and
people
out
there.
B
The
major
tech
companies
are
either
offering
kubernetes
services
or
are
building
tools
that
that
hook
into
kubernetes,
so
the
future
is
bright.
If
it's,
you
know,
if
we're
talking
about
kubernetes
but
also
for
an
organization
as
well.
If
an
organization
is
saying
we're
wanting
to
make
a
technology
bet
at
the
infrastructure
layer
that
we
don't
want
to
have
to
invest
in
today
and
rip
out
or
replace
in
two
years
time,
we
want
this
to
have
a
strong
road
map.
B
I
do
feel
like
kubernetes
has
a
super
strong
road
map,
so
with
this
being
it
like
you're,
getting
started
with
kubernetes
session,
if
you're
an
individual
or
an
organization
and
you're
sort
of
bumming
and
arring
and
being
like
well,
should
we
shouldn't
we
go
down
the
kubernetes
route?
Of
course,
this
is
just
my
opinion,
and
you
know
your
career
and
your
business
units
and
stuff
way
better
than
I
do.
B
But
I
do
feel
like
kubernetes
is
a
solid
choice,
so
don't
feel
like
serverless
or
anything
else
is
going
to
wipe
it
away,
and
I
would
go
with
with
what
you
said
really
adrian,
that
kubernetes
is
going
to
manage
serverless
workloads
rather
than
serverless
workloads.
Replace
kubernetes
now
will
serverless
workloads
replace
containers.
B
My
opinion
on
that
also
is
no
and
I
feel
super
confident
on
that
in
as
much
as
like
we've
still
got
mainframes
out
there
like,
I
spent
a
lot
of
time
working
in
retail
banking
in
the
uk
and
no
joke
millions
and
millions
of
pounds
or
euros
or
dollars
were
spent
every
year
on
mainframe
infrastructure
and
not
rusty
old
stuff.
With
dust
on
on
the
top
of
it,
you
know
like
brand
new
mainframes
at
the
core
of
a
lot
of
businesses,
with
open
systems
around
that
and
virtual
machines
and
now
containers
and
stuff.
B
C
B
B
Do
you
do
you
know
what
yeah
the
look?
I
say
this
all
the
time
because
look
I
teach
people
kubernetes
and
containers
and-
and
I
do
very
much
feel
like-
and
I
apologize
for
anybody
who's
heard
me
say
this
before,
but
I
feel
like
we
live
in
a
golden
age
of
learning.
New
technologies
like
if
I
wind
the
clock
back
to
when
I
was
doing
my
mcse
and
windows
nt4
or
even
even
like
my
network
certification,
and
I
never
got.
But
I
was
working
towards
years
ago.
B
I
had
to
go
to
my
boss
and
beg
him
to
loan
me
a
spare
pc
from
work
and
the
pc.
It
was
one
of
these
massive
old
compact
things
that
had
a
monitor
that
you
almost
needed
a
forklift
truck
to
lift,
and
now
I
was
installing,
I
think
you
know,
windows
nt4,
I
might
even
have
had
it
on
floppy
disks
as
well,
but
certainly
either
floppy
disks
or
cds
and
anytime.
B
You
would
break
anything
and
breaking
stuff
is
a
great
way
to
learn
right
and
it
would
be
like-
let's
rebuild
the
nt
domain
and
that's
like
four
hours
of
waiting
for
windows
to
build
we're.
Not
there
anymore
we're
like.
If
you
want
to
learn
kubernetes,
you
can
install
mini
cube
or
docker
desktop
or
a
ton
of
different
things
on
your
laptop
boom
like
that.
You've
got.
Okay
might
not
be
a
production
grade,
kubernetes
cluster,
but
I
you
know
what
goes
so
far
as
to
say
even
with
something
like
k3d
or
k3s.
B
You
almost
can
because
you
can
have
like
a
multi-node
kubernetes
cluster,
on
your
laptop
that
you
can
trash
and
rebuild
in
like
a
couple
of
minutes,
and
even
if
that's
a
bit
too
hard
for
you,
you
can
go
to
like
most
of
the
major
cloud
providers
and
get
some
free
credit
in
most
places
to
spin
up
kubernetes
on
their
infrastructure
and
just
play
about
with
it,
tell
your
heart's
content
and
then,
of
course
like
okay.
So
I
think
that
my
kubernetes
book
back
in
2016
or
17
was
the
first
one,
but
there's
flipping
loads.
B
Excuse
me,
but
there's
loads
now,
like
you
or
you're,
almost
spoiled
for
choice
with
books
and
with
video
training
courses
with
hands-on
platforms
that
will
walk
you
through
how
to
do
it.
It's
like
today,
and
I
mean
this
respectfully
okay,
but
there
are
no
longer
any
excuses
to
not
learn
something
like
kubernetes.
It's
not
hard.
You
don't
like
that
that
pc
that
I
borrowed
from
my
boss,
literally
I
put
it
on
a
makeshift
table
in
the
corner
of
our
bedroom.
B
When
I
was
first
married
and
had
a
really
tiny
house
and
when
you
turned
it
on
the
fans
were
really
loud,
my
wife
was
like
really
do.
We
need
that?
No,
no,
but
the
world's
not
like
that
anymore.
It's
so
easy
to
actually
get
your
hands
on
and
the
resources
are
out
there
and
you
come
to
events
like
this,
and
you
do
twitter
and
stuff
like
that.
You
ask
people,
I
think
you
get
answers,
so
I
think
I'm
not
kubernetes
is
hard
to
learn,
but
the
tools
to
help
you
learn.
C
Yeah,
I
fully
agree,
I
think,
that's
a
great
answer.
It
actually
leads
on
to
a
question
from
bruno
gabriel
de
silva
and
I
think
we
can
keep
the
strikes.
That's
still
in
context,
okay
and
he
says,
what's
the
difference
for
you,
learn
it
about
learning
from
a
book
or
video
classes.
I
I
maybe
go
first
yeah.
I.
C
It's
different
strokes
are
different
folks
yeah.
I
I
actually,
I
would
have
said
like
bruno
that
I
get
more
from
books
most
of
the
time,
especially
for
going
deeper
reference,
but
I
find
myself
watching
videos
quite
a
lot
recently
and
I've
really
enjoyed
like
clustered
by
raw
code
and
so
on,
and
I've
definitely
learned
stuff
from
that.
I
don't
know
what
your
take
is.
B
B
I
would
advise
both,
but
if
you
are
preparing
for
an
exam
book
and
follow
the
examples
with
your
hands-on
and
then
either
an
audio
version
of
the
book
or
a
video
course
as
like
a
refresher
because
taking
exams-
and
I
know
the
question
wasn't
necessarily
about
that-
but
when
you
take
an
exam,
I'm
not
a
fan
of
like
really
working
hard.
The
night
before
and
in
the
car
that
I've
got
an
extra
five
minutes
before
I
have
to
go
into
the
testing
center
or
it's
in
your
room
now
at
home.
B
C
Okay,
I
think
we
should
get
back
to
an
actual
kubernetes
question,
we're
starting
to
run
out
of
time
now
all
right,
but
tim
banister
asked
on
the
kubernetes
slack
or
cncf
slack.
What
things
outside
of
kubernetes
proper
need
to
get
better
in
order
to
make
the
overall
container
orchestration
story
more
effective.
B
B
If
you
don't
think
I
I'm
answering
to
the
question,
so
I've
put
what
things
outside
of
kubernetes
need
to
get
better.
Okay,
so
I
think
right.
The
number
one
thing
outside
of
kubernetes
on
a
technology
perspective
that
you
need
to
go
into
production
as
a
service
mesh
so
and
I'm
not
necessarily
saying
they
all
need
to
get
better.
Well,
I
look
that
they
do
it
and
and
everything
look
even
if
even
if
they're
great,
we
always
want
to
be
striving
towards
getting
better.
B
Don't
we,
so,
I
would
say
you
in
production
need
a
service
mesh
and
some
of
the
service
meshes
in
particular
need
to
get
better.
But
again
it's
really
difficult,
like
we
talked
about
kubernetes
before
these
service
meshes
are
trying
to
do
a
lot
of
things
for
us
and
you
don't
just
build
that
overnight
and
make
it
simple
overnight.
B
So
I'm
I'm
not
criticizing
any
of
the
service,
mesh
communities
or
or
vendors
or
anything
like
that,
and
but
I
think
service
mesh
is
important
and
it
needs
to
get
better
if
I
could
take
like
a
non-technical
one
as
well,
but
it
is
coming
back
to
something
we
suggested
before
is
that
I
feel
like
organizations
structurally
need
to
get
better
and
so
to
be
able
to
go
cloud
native.
You
really
need
to
rethink
your
organizational
structure.
B
The
way
you
you
build
teams
of
developers
and
the
way
that
they
interface
with
each
other
and
the
way
that
they
interface
with
the
infrastructure
teams
and
other
people
like
that.
That
really
is
like
a
key
thing,
because
it's
not
just
about
technology
and
it's
about
processing
things
as
well,
so
my
two
things
will
be
service
mesh
and
then
like
organizational
structures
and
don't
get
me
wrong
like
there's
a
there's,
a
list
that
we
could
go
on
for
forever
as
well.
C
Yeah,
my
boss
would
love
to
hear
you
saying
that
about
organizational
structure,
because
that's
absolutely
what
we
sort
of
focus
on
at
container
solutions.
But
what
I
would
say
is,
I
would
actually
tie
it
into
another
question.
We
got
asked
on
twitter,
which
is
which
we
didn't
want
to
answer,
because
it's
too
complicated,
oh
yeah,
it's
like
owen,
hollins
asked
how
did
you
maintain
and
upgrade
your
clusters
and
also
it
scale
nothing
down,
and
I
think
that's
something
that
you
know
we
still
need
to
work
on.
B
Yeah,
I
I
really
don't
feel
like
we're
there
for
that
and
I'll
take
I'll,
take
two
angles
on
that,
and
they
may
be
cheap
angles.
Okay,
the
first
one
is,
I
do
feel
if
you
go
the
cloud
route
like
a
managed
or
a
hosted
kubernetes
service
like
eks
or
gke,
or
the
node
kubernetes
engine
whatever,
and
I'm
not
speaking
to
particular
hosted
services
here
right,
but
I
feel,
like
the
cloud
vendors
almost
have
those
kernel
engineers
on
staff
that
do
that
hard
work
for
you.
B
I
know,
for
instance,
with
gke
like
in
the
early
days
you
it
was.
You
didn't,
really
have
much
of
a
choice
with
regards
to
upgrades,
whereas
at
least
now
that
they
offer
you
you
can,
you
know,
go
on
the
rapid
channel
if
you
want
to,
or
you
can
go
on,
the
more
stable
channel
so
so
they're
giving
you
more
dials
and
knobs
and
buttons
to
press
and
stuff
to
help
you
with
that,
and
they
really
make
it
quite
a
lot
simpler.
B
I
think
the
other
thing
is
I
feel
like,
and-
and
I
don't
want
to
speak
out
of
place
here,
because
I
know
that
the
maintainers
in
the
community
do
an
incredible
job,
but
I
really
well,
I
feel,
like
moving
from
four
releases
a
year
to
three.
It
is
a
step
in
the
right
direction.
It
makes
it
makes
it
easier
for
people.
C
D
No,
that's,
okay,
I
think
we're
doing
okay
on
time.
I
I
I
actually
your
point
about
self-learning
actually
resonated
with
me,
nigel,
because,
obviously
that's
that's
kind
of
I've
spent
like
over
a
decade,
hunting
for
information
online
and
moving
in
and
out
of
irc
channels
very
early
on,
and
I
know
people
for
me
probably
had
to
go
fishing
on
usenet
for
information
around
around
technology.
So
it
definitely
has
gotten
a
lot
easier,
but
I
think
the
tools
are
there.
D
It's
also
a
lot
more
noisy,
though,
as
well
yeah,
so
it's
also
much
harder
to
get
people's
attention,
but
I
thought
yeah
really
enjoyed
your
past
nights
or
anything,
so
that
was
that
was
quite
good,
so
I
guess
I
you
know
typically
we'd
use
this
time
to
ask
questions,
but
the
whole
point
of
your
the
whole.
The
whole
point
of
your
session
was
always
asking
questions,
so
I
think
we
have
another
four
or
five
minutes
before
our
next
speaker
joins.
Okay,
oh.
C
A
I
have
a
question.
I
have
a
question
that
probably
is
a
bit
too
big
to
answer
so
we
might,
you
might
want
to
take
this
to
slack
or
something,
but
you
mentioned
that
service
meshes
are
essential
going
into
production.
That's
one
of
the
things
you
need,
maybe
not
said
it's
not
the
word.
Sorry.
You
said
that
service
measures
are
something
you
need
to
go
into
production
and
that's
just
an
interesting
and
interesting
thought,
because
I
don't
see
many
I
don't
see.
I
see
people
still
playing
with
service
meshes,
but
lots
of
people
already
in
production.
B
Yeah,
so
so
let
me
take
that
for
a
couple
of
minutes,
right
and-
and
I
don't
know
what
adrian's
thoughts
are
as
well
is
so
I
feel
like
what
a
lot
of
service
measures
bring.
A
production
and
installation
of
kubernetes
is
almost
crying
out
for
it
and
if
you
can
do
it
at
day,
one
then,
then
all
the
better,
for
you
excuse
me.
B
I
just
think,
like
you
know
the
whole
sort
of
micro
services
design
for
applications
where
all
of
your
different
application
features
and
now
communicating
over
a
network
and
I'm
picking
some
low
hanging
fruit
here
right.
You
know,
they're,
not
communicating
over
shared
memory
on
on
a
single
host
anymore,
it's
much
more
dangerous.
B
Now
that
all
that
chat
is
going
over
the
network,
so
the
ability
to
almost
have
visibility
into
your
network
and
the
ability
to
sort
of
have
your
network
almost
learn,
maybe
I'm
getting
towards
ebpf
here
a
little
bit
more,
but
also
that
ability
to
at
the
infrastructure,
layer,
encrypt
communication
from
pods
to
product
content
to
container.
However,
you
want
to
think
about
it
and
not
have
to
ask
your
application
developers
to
say
we
need
you
in
like
your
your
containers
that
we're
asking
you
to
build
and
make
them
single
purpose.
B
Could
you
actually
just
go
and
put
this?
You
know
encryption
decryption
stuff
in
there
as
well.
Please.
I
really
feel,
like
you
know
the
fact
that
a
service
mesh
will
offer
all
of
those
things
and
more
as
you
go
to
like
proper
production,
and
I
may
be
my
view
of
it
may
be
tainted,
but
I'm
not
a
fan
of
that
word
actually,
because
I
spent
so
much
time
in
retail
banking,
where
they're,
like
so
obsessed
about
like
security,
and
what
have
you.