►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Homebrewing a Kubernetes Bootcamp: From College to K8s Support Engineer - Alice Wasko, Ambassador Labs
Alice Wasko is a Support Engineer at Ambassador Labs who started her career not knowing anything about Kubernetes or the CNCF Landscape. In this talk Alice will share how she has learned about the many different cloud native topics that seemed overwhelming at first glance to someone without experience. Alice will also explain how she has taken part in helping to improve the learning and onboarding process for new hires and community members. Her “homebrewing” of a Kubernetes bootcamp has been both a great teaching tool and also a great learning tool. She aims to share her experience as a developer who recently learned Kubernetes and other technologies in the cloud ecosystem with others who are beginning their learning journey or are interested in educating others.
A
A
This
talk
is
about
my
experiences,
transitioning
from
a
college
graduate
with
a
limited
experience
in
cloud-native
technologies,
to
a
support
engineer
working
with
users
who
are
running
kubernetes
and
many
other
cncf
projects
and
tools.
I
learned
almost
everything
I
know
about
these
technologies
from
working
on
the
job.
A
One
nice
thing
about
being
fresh
from
college
is
that
I
wasn't
expected
to
be
very
experienced
with
these
tools
and
systems
right
after
joining,
I
was
put
through
a
boot
camp
of
a
bunch
of
different
materials,
reference,
docs
videos
and
blog
posts
to
learn
about
kubernetes,
networking
architecture,
containerization
and
stories
about
businesses
that
were
transitioning
into
running
their
services
in
a
distributed
cloud
environment.
To
help
me
pick
up
these
skills
quickly,.
A
I
was
completely
overwhelmed
at
first,
I
went
from
thinking.
I
would
never
understand
as
much
as
my
senior
colleagues
now
being
very
proud
and
confident
of
the
skills
that
I've
learned
since
then,
not
only
that,
but
I
now
believe
that
anyone
with
enough
interest
motivation
can
learn
these
things
as
well.
Even
if
you
don't
have
a
background
in
computer
science
or
networking
and
you've
never
experienced
any
sort
of
kubernetes
or
cloud
native
technologies.
A
A
I'm
really
glad
that
it
was
exposed
to
it,
and
now
I
appreciate
its
usefulness,
a
lot
more
and
looking
back.
I
think
that
the
goal
of
adding
it
to
my
college
courses
was
likely
just
to
make
us
aware
of
it
and
introduce
us
to
the
topic,
instead
of
being
a
comprehensive
guide
to
all
the
things
container
and
cloud
related.
A
A
Having
some
knowledge
about
docker
gave
me
a
big
head
start
in
learning
kubernetes
and,
as
I
completed
the
boot
camp
and
familiarized
myself
with
kubernetes
and
how
to
use
it,
I
began
working
with
users.
I
started
thinking
about
how
a
handful
of
topics
like
containerization,
kubernetes,
pods
and
kubernetes
services
kept
popping
up
to
me
as
things
that
were
really
important
to
really
fully
understand
how
having
an
understanding
of
some
of
these
topics
can
really
help.
You
learn
other
skills
and
technologies
by
having
a
solid
understanding
of
some
of
these
core
topics.
A
I
mentioned
with
the
help
of
our
boot
camp,
to
teach
me
them.
In
our
last
eight
months,
I've
learned
more
than
I
ever
thought
possible
in
such
a
short
period
of
time,
working
with
so
many
different
people
and
having
to
familiarize
myself
with
the
technologies
they're
using
that
I've
never
heard
of
before
has
exposed
me
to
so
many
new
topics.
A
I've
learned
all
about
how
networking
works
and
the
various
ways
that
machines
communicate
with
each
other,
such
as
http
headers,
tls,
tcp,
grpc,
websockets
and
certificate
management.
I've
set
up
distributed
tracing
systems
zipcan
and
datadog,
and
I've
learned
how
to
interpret
the
information
that
those
wraps
provide
when
I
receive
them
so
that
it
can
help
troubleshoot
problems.
A
A
I
just
mentioned
so
many
different
topics,
and
if
you
didn't
know
what
they
were,
that's
fine.
Neither
did
I
eight
months
ago,
the
technologies
that
I
just
mentioned,
most
of
which
I
didn't
even
know
existed,
and
let
me
tell
you
when
I
first
started
learning
and
saw
how
many
more
advanced
topics
I
would
need
to
learn.
I
should
be
getting
really
worried
and
overwhelmed.
A
The
one
thing
that
I
can
say
about
learning
all
of
these
things
is
that
learning
is
a
process.
It
doesn't
happen
overnight.
You
do
it
one
piece
at
a
time
it
seems
impossible
at
first
when
you're
just
getting
started,
but
just
like
I
mentioned
when
you
have
a
solid
understanding
of
a
few
foundational
concepts.
A
A
There
are
strategies
that
you
can
use
to
help
build
a
collection,
learning
materials
to
help
teach
yourself
for
others
and
get
set
up
with
the
skills
and
knowledge.
You
need
to
learn
any
number
of
those
advanced
topics
in
the
cloud
native
landscape.
So
I'm
going
to
share
some
advice
about
how
to
build
your
own
boot
camp.
We're
learning
similar
things
with
those
strategies
that
I've
learned
after
having
gone
to
a
rapid
pace,
boot
camp
myself
and
working
with
others
to
help
improve
it.
A
A
I
think
that
this
is
a
really
good
place
to
start.
If
you
don't
already
have
something
specific
in
mind,
I
strongly
feel
that
having
an
in-depth
understanding
of
these
concepts,
how
they're
related
and
how
they
work
before
moving
on
with
your
learning
journey,
can
greatly
impact
your
experiences
and
more
advanced
topics
that
you
learn
as
well
as
your
personal
enjoyment
and
satisfaction.
A
One
of
the
reasons
I
recommend
structuring
the
start
of
your
learning
around
the
process
of
getting
code
to
run
in
the
cloud.
Is
that
understanding
how
a
project
goes
from
code
to
container
image
and
is
then
shipped
and
run
in
containers,
as
well
as
the
impacts
that
packaging
dependencies
into
those
images?
A
A
A
Next,
I
recommend
covering
what
kind
of
communication
between
those
different
kubernetes
objects
happens
within
a
cluster
learning
about
how
clustering
networking
works,
given
the
ephemeral
nature
of
pods
and
how
a
kubernetes
service
selects
and
talks
to
pods
will
help.
You
start
thinking
about
how
these
parts
work
together
as
a
whole.
A
A
A
A
A
If
you
aren't
familiar
with
building
container
images
and
deploying
them
to
kubernetes,
we
have
a
great
open
source
demo
service
called
quote
that
we
use
for
this
exact
purpose.
You
can
see
an
example
of
it
right
here.
All
it
does
is
serve
a
random
quote
in
the
time
of
day,
as
well
as
a
server
id.
So
things
like
this
that
are
easy
to
set
up
and
test
with
are
preferable.
A
We
have
instructions
for
building
the
project
into
a
container
image,
as
well
as
kubernetes
manifests
for
deploying
it
and
instructions
for
making
requests
to
it.
If
you
need
an
example
for
how
to
set
up
your
own
simple
service
and
get
it
deployed
to
kubernetes,
you
can
find
these
on
the
ambassador
website
to
get
started.
Documentation
that
will
link
to
the
github,
where
you
can
view
all
the
source
code
manifests
for
the
project.
A
I
highly
recommend
building
your
own
simple
service,
once
you're
familiar
with
the
projects
and
processes,
so
that
you
can
tweak
it
to
best
serve
your
environment
and
learning
needs,
since
adding
to
it
over
time
is
a
fantastic
way
to
learn
once
you're
comfortable
with
all
of
that.
A
good
next
step
is
to
consider
the
architecture
of
your
kubernetes
cluster
and
how
you'll
be
using
it
learning
how
traffic
gets
into
and
out
of
the
cluster,
frequently
called
ingress
and
egress
or
north
south
traffic.
A
It's
important
to
cover
will
likely
be
one
of
the
first
things
you
want
to
play
around
with
once.
You've
got
a
cluster
running
and
a
service
or
two
deployed
while
learning
about
getting
traffic
into
your
cluster.
You
should
familiarize
yourself
with
load
balancers
how
they're
created
and
how
different
load
balancer
configurations
can
affect
traffic
going
into
your
cluster.
A
A
A
A
Reading
about
how
someone
put
into
practice
or
explains
the
things
that
you're
trying
to
learn
about,
might
answer
your
questions
or
help
put
together
pieces
of
information
that
you've
learned
about
maybe
even
reveal
new
topics
that
you
want
to
add
to
your
bootcamp
that
you
didn't
know
about
visual
guides
and
diagrams
can
also
help
you
emphasize
the
connections
between
different
topics.
They'll,
give
you
a
memorable
way
of
internalizing
and
remembering
how
things
work.
A
A
great
example
of
where
a
visual
diagram
would
be
helpful
is
breaking
down
the
insides
of
a
cluster
from
the
pod.
The
containers
within
the
pod
services,
sending
traffic
to
the
pods
name,
spaces
and
other
information
about
a
cluster,
but
all
this
is
great
and
easily
visualized
to
help
show
the
distinction
between
different
things,
how
they're
related
and
how
they
interact.
A
You
have
a
misconception
about
a
topic
or,
if
they're
able
to
provide
information
that
you're
missing
from
a
given
topic.
That's
also
a
huge
plus
hands-on
experience
can
be
one
of
the
most
effective
ways
to
solidify
information,
but
it
should
always
be
given
as
a
follow-up
to
that
information
itself.
A
Finally,
stories
such
as
like
an
individual's
experiences
working
on
a
project
or
a
company's
description
about
transitioning
from
a
monolithic
application
to
a
cloud-native
implementation
of
it.
It
really
helps
to
tie
together
a
lot
of
the
details
that
you
learned
about
make
you
consider
the
reasons
why
you're
learning
all
these
technologies
in
the
first
place,
you
don't
spend
all
this
time,
building
out
complex
systems
and
learning
about
them,
just
for
the
fun
of
it.
A
I
think
that
having
a
good
mix
of
these
different
types
of
learning
materials
in
your
boot
camp
is
really
important,
because
each
serves
a
purpose
that
is
not
entirely
met
by
the
others.
You
can't
just
have
a
book
of
documentation
and
call
it
a
boot
camp
any
more
than
you
consider
mindlessly
copying.
Lots
of
demo
exercises
to
make
programs
that
work
without
bootcamp,
either
different
types
of
learning
materials
also
cater
to
people
with
different
learning
styles.
A
Just
like
how
I
describe
how
an
understanding
of
the
details
of
containers
helps,
you
learn
the
working
parts
of
a
cluster
reading,
a
company's
testimonial
for
a
certain
project
in
architecture
or
use
of
a
specific
technology
won't
be
as
helpful
or
impactful
to
you.
You
read
it
before
you
understand
what
the
underlying
parts
are
and
how
they
work
constantly
think
about.
A
A
Lastly,
if
you're
building
a
boot
camp
for
your
organization
or
for
others
to
follow,
set
up
a
meeting
with
everyone
who
goes
through
the
boot
camp
to
get
their
feedback
about,
it
ask
questions
to
make
sure
that
the
goals
of
your
boot
camp
are
being
met.
If
everything
that
you
hope
for
people
to
understand
is
covered
by
it,
feedback
is
critical
to
improving
any
learning
resource.
A
You
want
to
make
sure
that
you
not
only
accomplish
the
goal
of
teaching
others
something,
but
that
you
also
continue
to
make
it
better
for
everyone
who
continues
to
use
it
after
working
through
the
bootcamp
ambassador.
My
manager
set
up
a
few
meetings
with
me
to
figure
out
what
worked
about
it.
What
resources
I
liked,
which
ones
I
didn't
like
and
what
was
the
most
and
least
impactful
as
well
as
what
I
would
change
about
it.
A
After
getting
my
feedback,
we
work
together
to
take
that
feedback
and
make
improvements
to
the
boot
camp
for
the
next
person
to
go
through
it
by
constantly
getting
feedback
and
improving
it.
You
also
gain
perspective
about
how
different
and
effective
it
is
for
a
general
learning
resource
to
different
people.
A
A
You
can
use
this
strategy
to
help
eliminate
any
bias.
The
boot
camp
has
the
more
feedback
that
you
get
on
it.
For
example,
when
I
gave
my
initial
feedback,
I
recommended
removing
a
certain
visual
diagram
that
I
thought
was
not
a
very
effective
learning
material,
but
the
next
person
who
went
through
the
boot
camp
gave
feedback
that
it
was
very
happy
that
it
was
included
and
that
they
got
a
lot
of
value
from
it
and
again
after
that,
another
person
mentioned
that
they
wish
there
had
been
more
hands-on
exercises
to
try.
A
This
is
an
idea
of
how
you
can
figure
out,
if
you're,
covering
different
learning
styles
effectively,
and
it's
going
to
be
just
as
good
of
a
resource
for
everyone
who
goes
through
it.
The
goal
is
to
create
a
living.
Boot
camp
should
always
be
changing
and
adapting
to
new
information
shifts
in
technology
and
feedback
for
more
people
to
make
sure
that
anyone
can
spend
the
time
following
it
is
not
left
feeling
confused
or
like
they're,
not
in
a
good
position
to
learn
more
advanced
topics
in
their
own.
A
You
can
even
take
this
one
final
step
further
and
create
opportunities
for
your
team
members
to
contribute
the
things
that
they've
learned
to
the
boot
camp.
So
you
create
a
pool
of
shared
knowledge
that
is
relevant
and
useful
to
your
team
if
you're
successful.
In
doing
so,
you
can
create
a
system
where
every
new
member
to
your
team
helps
expand
the
collective
knowledge
of
the
group,
and
none
of
that
knowledge
is
lost
when
a
team
member
leaves
you
never
want
to
end
up
in
a
scenario
or
a
team.
A
Wrapping
up
I'd
like
to
give
a
bit
of
partying
advice
for
everyone,
regardless
of
whether
there's
someone
who's
just
recently
started
their
career.
Like
me,
they've
had
years
of
experience
or,
if
they're,
just
someone
trying
to
figure
out
how
to
help
train
other
people,
and
they
need
to
pass
this
information
on
to
them.
A
A
A
I
thought
there
was
only
no
way
that
I
could
ever
know
enough
about
these
different
tools
that
they
were
using
and
how
to
help
them
fix
their
issues.
I
don't
consider
myself
an
expert
about
any
of
the
topics.
I've
just
talked
about
and
there's
still
a
wealth
of
information
that
I
don't
have
yet
after
eight
months
of
experience
in
this
world,
though,
I
have
confidence
now
not
confidence
that
I
know
everything
I
need
to,
but
confidence
that
I
have
the
ability
to
learn
anything
that
I
will
need
to
to
solve
a
problem.