►
Description
Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Effective Kubernetes Onboarding - Kathleen Juell, DigitalOcean
Kubernetes has a steep learning curve, but many teams need to learn Kubernetes – quickly. This talk will cover strategies for onboarding developers to Kubernetes, taken from DigitalOcean's Developer Education team – the producers of DO's Community tutorials – and the Community Platform team, which develops the Community application. It will include 1. Core concepts and insights from DO's new Kubernetes for Full-Stack Developers curriculum; 2. An on-the-ground perspective taken from the Community Platform team's migration from a traditional VM environment to Kubernetes. Key concepts the talk will cover: 1. How to onboard teams successfully by establishing knowledge baselines and effectively organizing, structuring, and delivering Kubernetes concepts. 2. How to situate Kubernetes in a larger arc of application development and integrate it into an existing development workflow.
https://sched.co/Zeso
A
A
So
I'll
just
say
a
quick
word
here
to
plug
our
community
writing
program
in
case
anyone
wants
to
share
any
of
the
great
things
that
you're
working
on
with
the
digital
ocean
community.
We
do
accept
submissions
from
community
external
authors,
so
please
definitely
feel
free
to
get
in
touch
with
me.
If
you
want
to
learn
more
about
that.
A
A
A
so
leading
up
to
and
following
the
release
of
that
product.
The
core
contributors
on
the
community
content
team
were
tasked
with
the
following
project:
teach
the
world
kubernetes,
so
the
push
to
develop
content
began,
and
here
in
the
screenshot
you
can
see
one
outgrowth
of
that
push
for
content,
which
is
our
kubernetes
for
full
stack
developers,
curriculum
which
I'm
going
to
discuss
in
more
detail
later
so
teach
the
world
kubernetes
seems
like
a
straightforward
ask
right,
except
where
do
you
begin?
A
A
Basically,
we
were
in
the
process
of
moving
our
staging
and
production
pipelines
and
environments
to
our
internal
kubernetes
clusters.
Prior
to
this
transition,
we
have
been
relying
on
some
trustee,
reliable
but
ultimately
outdated.
Ubuntu
servers
like
the
97
corolla
that
I
drove
until
a
few
years
ago.
These
servers
had
brought
us
far,
but
it
was
time
to
make
the
change
so
the
principles
that
I
want
to
discuss
for
onboarding
teams
and
individuals
to
kubernetes
also
stem
from
the
work
that
the
community
development
team
was
doing.
On
the
platform
side.
A
So
in
working
through
these
principles
with
you,
I'm
going
to
combine
insights
from
both
the
content
and
the
development
side.
As
I
had
the
good
fortune
of
both
contributing
content
to
the
kubernetes
curriculum
and
also
working
on
the
development
team
that
finalized
community's
transition
to
kubernetes.
A
A
A
Members
of
this
group
also
need
to
be
able
to
deploy,
or,
if
they're,
not
doing
that
themselves,
they
need
to
be
able
to
get
things
up
to
a
point
where
deployment
can
happen
so
for
our
team
deployment
on
kubernetes
would
mean,
involving
you
know,
would
be
a
process
that
involved
different
processes
from
what
we
had
been
using
on
vms.
So
no
more
capybara,
for
example,
so
we
needed
to
bring
people
up
to
speed
on
how
moving
to
kubernetes
would
affect
the
deploy
process.
A
A
A
At
first,
the
team
considered
using
different
tracks
right
only
presenting
material
to
certain
members
of
certain
groups,
but
ultimately
they
decided
that
that
was
somewhat
limiting.
So
they
opted
for
more
of
a
choose.
Your
own
adventure
style
of
approach
to
presenting
the
material,
so
tutorials
were
organized
in
such
a
way
that
users
could
select
what
was
most
relevant
for
them.
A
A
A
So,
even
in
the
case
where
logging
and
monitoring
are
handled
by
other
teams,
application
developers
could
still
be
responsible
for
things
like
making
sure
health
and
or
readiness
endpoints
exist.
So
understanding
the
need
for
those
is
important
next
containers,
what
do
they
mean
for
your
application?
One
way
of
covering
this
in
practical
terms
could
be
setting
up
a
local
development
environment
with
docker
and
compose
to
get
folks
familiar
with
what
goes
into
an
image
and
how
the
containerized
stack
behaves
as
a
whole.
A
A
So
ostensibly
your
team
is
spending
work
hours
on
this
transition,
so
you
want
to
help
them
avoid
any
blockers,
so
one
blocker
could
be
something
like
well.
Why
is
this
necessary?
Why
are
we
doing
this
now?
You
know
what
are
the
foundational
components
of
a
distributed
architecture?
What
does
that
really
mean?
A
How
do
containers
differ
from
vms?
What
does
that
mean
for
me
and
then?
Finally,
what
what
are
the
differences
in
the
tools
and
systems
that
I'm
used
to
am
I
going
to
have
access
to
those
things
is
using
them
going
to
be
different
and
so
on
so
depending
on
where
your
developers
are
coming
from
and
what
their
experiences
are.
It
may
be
helpful
to
think
about
covering
some
meta-level
topics
in
your
onboarding
process.
A
So
one
helpful
way
to
approach
this
might
be
to
separate
out
larger
topics
like
what
is
kubernetes,
what
are
containers,
what
are
components
of
a
distributed
architecture,
from
what
I'm
going
to
call
operational
topics
like
how
do
I
extract
my
application
configuration?
How
do
I
ensure
that
the
app
is
stateless
and
so
on?
A
So
for
the
kubernetes
curriculum,
for
example,
the
team
decided
to
address
the
need
for
a
meta-level
overview
by
having
an
introductory
topic
section
that
readers
could
opt
into
if
they
wanted.
So
this
section
covered
things
like
basic
system,
architecture,
core
objects
and
other
key
foundational
topics.
A
So
since
the
audience
for
the
curriculum
was
theoretically
everyone,
the
team
thought
this
made
the
most
sense.
They
assumed
that
this
could
be
helpful
for
many
people,
but
it
wasn't
necessarily
reading
for
everyone,
so
it
made
sense
to
include
it
as
optional
and
for
everyone
for
folks
who
were
new
and
then
also
folks
who
wanted
a
refresher.
A
We
also
created
some
internal
documentation
to
give
a
kind
of
high
level
overview
of
where
information
was
now
going
to
be
located
in
the
application.
So
things
like
deployment
manifests
and
pipelines
concourse.
We
also
created
detailed
guides
on
how
to
deploy
to
staging
and
production,
as
well
as
how
to
roll
back
redeploy
and
troubleshoot.
A
Some
of
the
key
learnings
that
we
took
away
from
this
were
it's
definitely
okay,
to
break
folks
out
in
terms
of
operational
responsibilities,
so
having
a
dedicated
group
dealing
with
infrastructure
in
a
granular
way.
For
example,
it's
also
perfectly
fine
to
organize
information
around
operational
goals,
things
like
app
development
deployment
and
so
on.
A
A
They
also
offer
a
great
way
of
creating
self-selecting
pathways
through
a
body
of
material
which
can
be
super
handy
if
you
have
a
lot
to
cover
so,
for
example,
the
kubernetes
curriculum
offers
a
topical
and
self-selected
path
through
a
lot
of
different
tutorials
and,
as
I
mentioned,
each
cluster
of
tutorials
in
a
section
of
the
curriculum
rolls
up
to
a
particular
audience
developers.
Operators
with
topics
that
pertain
to
the
goals
that
these
users
might
have.
A
A
A
Another
great
format
for
onboarding
is
a
recorded
talk
so
at
digital
ocean.
We
do
a
munch
and
learn
series
every
wednesday
with
topics
like
ceph101
writing,
kubernetes
controllers
and
concourse
best
practices
and
more
so
these
are
really
great
ways
to
scope,
a
topic
down
and
focus
it
on
developers
and
operators.
A
Finally,
though,
I
hesitate
strongly
suggesting
adding
meetings
to
anyone's
calendar
when
approached
strategically.
They
can
really
be
a
great
time
saver.
Speaking
from
our
experience
on
community,
I
would
say
that
it's
handy
to
have
an
agenda
for
these
meetings,
particularly
if
you're
getting
people
acquainted
with
kubernetes
for
the
first
time.
A
Also,
your
approach
doesn't
need
to
be
one
of
these
things
right
in
general.
I
would
say,
though,
as
you
move
through
these
different
formats,
your
scope
will,
in
you
know,
inevitably
narrow,
so
talks
vary,
of
course,
but
in
the
format
that
I'm
describing,
which
is
a
kind
of
like
quick
half
hour
onboarding
session
to
a
particular
topic,
you're
going
to
want
to
limit
your
scope
by
den
of
necessity,
making
sure
that
your
topic
is
something
that
you
could
cover
in
a
half
an
hour
for
a
fairly
well-defined
audience.
A
However,
finally,
in
meetings
you
know
you're
going
to
be
speaking,
presumably
to
a
group
of
people
who
share
your
context,
so
you're
probably
going
to
be
highly
specific.
However,
you
can
make
more
assumptions
in
a
meeting
like
that
about
shared
knowledge
and
context.
Since
you're
speaking
to
your
teammates
and
colleagues,.
A
In
retrospect,
I
would
say
that
the
team
has
adapted
really
well
to
the
changing
environment.
Everyone
knows
what
they
need
to
get
their
job
done
and
they're
getting
it
done.
People
also
feel
really
positively
about
the
move
to
kubernetes.
Since
you
know
for
an
application
that
serves
about
four
million
visitors
a
month,
kubernetes
definitely
gives
us
security
in
scale.
Among
many
other
things,
did
we
make
everyone
a
kubernetes
power
user?
I
would
say
no,
but
we
didn't
really
feel
that
that
was
the
requirement.
A
All
right
welcome
to
q,
a
for
folks
who
are
asking
about
the
slides
I
apologize.
They
are
on
the
sketch.
I
haven't
been
able
to
send
any
replies
here,
so
I'm
gonna
be
doing
that
verbally.
We
do
have
a
link
out
to
the
slides
in
the
community
in
the
kubecon
slack
and
they
are
on
the
sketch.
They
have
been
uploaded
there,
but
you
know
that
link
also
that
direct
link
is
in
the
community
slack
channel.
A
A
Hi
vitor
asks
any
surprising
issues
you
found
through
the
process.
Thanks
for
the
talk
so
yeah
I
mean
I
I
think
I
was
a
little
surprised
by,
and
maybe
this
is
not
something
I
should
have
been
surprised
about,
given
the
journey
I've
described,
but
you
know
it's
easy
to
lose
sight
of
the
basics
when
you're
sort
of
already
well-versed.
So
I
think
that
moment
that
I
described
it
we're
like.
A
Oh,
we
need
to
pull
back
and
have
like
a
metal
level
discussion
of
some
like
kubernetes
core
concepts
before
we
kind
of
like
move
forward
with
you
know.
The
rest
of
this
process
was
a
bit
of
a
surprise
and
that's
why
I
wanted
to
like
highlight
that
here,
because
you
know
it's
something
that
you
know
might
not
be
intuitive
or
obvious
that
you'd
need
to
like
take
that
step
back
lawrence
asked.
A
How
did
you
help
convince
devs.org
that
their
app
wasn't
anything
special
and
that
it
would
work
on
kate's?
So
I
think
we
have
a
deal
like
a
pretty
robust
internal
culture
around
kubernetes.
You
know.
Obviously
we
have
our
own
product
and
then
we
also
have
an
internal
kubernetes
product
that
we
use.
So
I
think
that
that
the
kind
of
like
the
going
standard
is
kubernetes,
so
that
was
a
pretty
easy
sound
just
because
that's
the
culture
of
the
org.
A
So
I
think
if
you
want
to
move
the
needle
on
that,
it
seems
like
you
know,
for
I
don't
I
you
know,
I'm
not
sure
how
you
would
you
know
do
that
from
the
ground
up,
we
were
just
sort
of
norming
ourselves
with
the
rest
of
the
org.
Jaymon
asks
what
are
some
good
approaches
for
creating
a
video
presentation,
so
I
I
like
the
format
of
the
munch
and
learn.
A
I
think
it's
I've
seen
that
you
know
if
you
kind
of
pick
your
scope
really
specifically
like
concourse
best
practices.
Obviously
that's
broad
but
you're,
probably
gonna
hit
on
like
three
or
four
best
practices,
maybe
more
or
if
you're.
You
know.
Your
topic
is
basics
for
deploying
an
application
on
kubernetes
at
your
company.
That
will
also
be
like
super
scoped.
So
I
think
it's
just
like
deciding
what
the
topic
of
the
video
is
going
to
be
and
then
kind
of
scoping
that
and
and
also
obviously
your
time
frame.
A
Let's
see
what
methods
did
we
use
to
gather
information,
so
we
actually
do
do
user
research
fairly
robustly
at
dio,
so
in
some
ways
we're
able
to
capitalize
on
information
that
was
already
being
circulated
through.
You
know
the
company,
via
like
research
initiatives
that
were
already
underway.
So
I
would
say
you
know
a
quick
way
to
get
some
research
might
be
like
a
in-app.
A
A
You
know
inviting
me
to
reflect
on
the
culture
at
dio.
No,
because
people
like
this
is
what
people
wanted,
and
so
you
know
I
I
described
that,
like
our
core
team
working
on
community
were
kind
of
like
more
traditional
web
dev,
you
know
vm
folks
and
but
they
weren't
resistant
because
they
they,
like
kind
of
you,
know
we're
situated
in
that
broader
culture.
So
I
think
it's
like
you
know
if
you're
in
a
culture
where
people
are
like,
you
know,
this
is
how
we've
been
doing
it.
A
A
You
know,
industry,
research
and
you
know
it's
kind
of
like
where's
that
change
coming
from,
as
I
was
talking
about
when
you're
thinking
about
audience.
It's
like.
If
those
are
business
decision
makers,
that's
one
kind
of
argument
and
if
it's
devs
like
it's
another,
so
I
think
it's
like
deciding
like
who
do
you
need
to
persuade
like
who's
resisting
and
then
like?
What
are
the
arguments
that
are
going
to
be
most
persuasive
to
them
specifically
and
then
trying
to
think
about
how
you
could
you
know
make
inroads
with
those
arguments?
A
I
mean
it
definitely
depends
on
like
what
your
end
goals
are,
but
I
I
love
that
idea
that
and
we
actually
do
offer
a
kubernetes
workshop
like
an
introduction
to
kubernetes
workshop
that
some
of
my
colleagues
have
given,
and
you
know
it's
the
same
kind
of
idea
in
that
workshop.
We
have
a
way.
You
know
where
we
kind
of
explain
like
a
pod.
We
explain
service
objects
and
then
we
kind
of
do
a
quick
demonstration
or
demo.
So
I
think
that's
a
great
approach.
A
I
think,
if
you're
dealing
with
like
a
dev
team,
where
you
have
an
objective
which
is
like
moving
an
application
to
kubernetes,
I
might
kind
of
cram
some
of
those
things
into
like
a
kind
of
meta-level
session,
but
I
think
in
a
workshop
setting
it's
a
little
different,
so
it
kind
of
depends
on
like.
Are
you
gonna?
A
Take
your
team
if
you're,
if
you're
kind
of
doing
it
like
in-house
with
your
team,
are
you
gonna
take
that
team
through
you
know
a
kind
of
like
workshop,
you
know
itinerary,
or
are
you
gonna,
like
kind
of
keep
it
focused
on
okay?
We
have
this
one
session
where
we
need
to
get
everybody
like
up
to
speed
on,
like
the
kind
of
broad
level
implications
of
what
we're
about
to
do
so,
it's
kind
of
like
a
call
and
like
what
what
you
are
doing
with
your
team.
A
A
Other
people,
you
know
working
with
different
use
cases
would
maybe
have
like
a
different
approach
to
this,
but
for
us
it
was
like
fairly
straightforward
and
then
also
you
know
with
some.
You
know
relevance
to
like
what
other
rails
you
know,
apps
were
be,
were
currently
deployed
at
dio
and
like
what
they
were
doing
as
well.
A
So
adam
asks:
did
you
ask
to
get
folks
certified,
so
the
certified
kubernetes
application
development
certificate?
I
think
that's
a
great
idea.
We
did
not
do
that
just
because
you
know
for
the
folks
who
are
on
the
team.
Their
work
was
really
going
to
be
around
still
on
the
app
dev
side
rather
than
the
kind
of
deployment,
and
you
know
operational
side.
I
think
that's
an
awesome
idea,
though,
and,
like
you
know,
I
would
totally
if
you
can
like
support
that.