►
From YouTube: KBE Insider (E6) - Kaslin Fields
Description
This is the last KBE Insider episode of the year! We talk to Kaslin Fields about her role as Developer Advocate at Google Cloud and CNCF Ambassador. We’ll learn how Kaslin makes technology, such as Kubernetes, more accessible to a broader audience through various mediums, including comics. Also, as a member of the Kubernetes SIG for Contributors, Kaslin will share her experience contributing to the Kubernetes community and share how you can get involved.
A
Well,
hello,
everybody,
I'm
not
sure
if
that
was
quite
the
right
bumper
as
we
went
in,
but
this
is
actually
the
kbe
insider
show
and
we
are
just
starting
we
air
this
show
about
once
a
month
and
we
so
we
normally
do.
A
I
think
it's
the
last
tuesday
of
the
month
is
the
normal
idea,
but
the
goal
of
the
show
is
to
talk
to
various
people
who
are
what
we
refer
to
as
insiders
in
the
kubernetes
community,
and
the
reason
we
like
to
talk
to
them
is
because
it
gives
us
a
good
idea
of
what
the
what
the
people
who
are
actually
doing
the
work
are
thinking
is
going
to
be
happening
soon
in
the
kubernetes
space
and
that
way
as
a
audience
member
as
a
you
know,
attendee
or
whatever.
A
Here
you
can
try
to
get
a
better
sense
of
what
will
be
happening
so
that
you
can
have
a
better
sense
of
what
you
will
be
doing
soon
so,
but
we
always
like
to
kick
it
off
with
first.
You
know
I'm
langdon
white.
I
am
currently
a
professor
at
boston
university,
I'm
formerly
with
red
hat,
and
I've
been
involved
in
the
kind
of
container
space
for
many
many
years
now
and
I'm
joined
here
with
steve,
speicher
and
I'll.
Let
you
introduce
yourself.
B
Yeah
thanks
langdon
to
mention
steve
spiker.
I
work
at
red
hat,
I've
been
a
product
manager
and
then
the
kubernetes
space,
pretty
much
since
2015
I'd,
say
so
seen
a
lot
of
changes.
I'm
the
director
of
the
developer
tools,
space
and
a
cncf
ambassador
so
help
run
a
local
lead
up
here
in
the
research
triangle
park
area
in
north
carolina.
A
Nice
and
our
other
regular
on
the
show
is
mina
and
I'll.
Also
let
her
introduce
herself
before
she
helps
us
out
with
the
news.
C
Yeah
definitely
hi
everyone,
I'm
mina,
I'm
pretty
sure
if
you've
seen
this
show
before
you've
seen
my
face
before,
like
langdon
said
we're
here
once
a
month,
although
right
now,
obviously
this
is
a
little
bit
out
of
our
usual
timeline
due
to
the
holidays
and
thanksgiving.
So
this
is
actually
our
last
show
of
the
year.
We're
very,
very
excited
to
be
with
you
guys.
C
I
work
at
red
hat
as
well,
I'm
on
the
product,
marketing
team
and
I
do
kbe
news
on
the
kbe
website,
so
I'm
excited
to
share
you
guys
share
with
you
guys
some
highlights
from
this
past
month.
Should
I
go
ahead.
Langdon.
C
Sounds
good,
so,
let's
start
out
with
some
announcements
from
the
linux
foundation,
kubecon
north
america,
2022
will
actually
be
on
october,
25th
and
28th
in
detroit
michigan.
I
will
be
putting
all
the
links
to
some
of
the
announcements
or
the
articles
that
I
mention
here,
so
you
guys
can
always
go
ahead
and
look
at
those.
After
after
I
talk
and
then
one
important
one
is
that
kubecon
eucfp
closes
on
december
17th.
C
As
a
reminder,
kubecon
eu
will
be
an
in-person
event
from
may
17th
to
may
20th.
So
don't
forget
that
submissions
must
be
received
by
11
59
pm
pacific
time
on
friday
december
17th.
With
that,
we
can
highlight
some
of
the
articles
that
we
shared
on
kbe
news
this
past
month
with
fintech
on
the
rise.
We
have
an
article
talking
about
how
kubernetes
simplifies
the
operation
of
fintech
apps.
Currently
kubernetes
is
used
by
over
45
percent
of
companies.
C
The
convenience,
speed
and
reliability
of
this
solution
has
been
appreciated
by
finance
companies
like
hsbc
capital,
one
starling
and
ing,
and
there
are
some
of
these
are
the
reasons
why
large
corporations
and
fintech
startups
choose
kubernetes
one
data
security
and
fail
safe
operations.
Two
automatic
and
safe
scaling,
three
fast
and
economical
operation
of
apps,
four,
no
downtime
and
convenient
interface,
five
simpler
to
develop,
update
and
rollback
apps.
C
Then
we
have
jonathan
katzen,
discussing
the
nine
open,
open
source
developer
tools
for
kubernetes.
The
community
surrounding
kubernetes
is
constantly
sharing
new
tools
and
features
to
help
help
developers
run
test
and
code
cloud
native
services
within
kubernetes,
while
2021
was
a
massive
year
for
this
kind
of
involvement.
There's
definitely
a
lot
more
to
come.
Here
are
some
additional
emerging
open
source
tools.
C
So
again,
while
2021
was
a
pretty
big
year
for
open
source
extensibility
with
kubernetes,
a
high
number
of
a
number
of
high
quality
products,
there's
still
plenty
of
opportunities
for
new
innovation
in
the
future
and
then,
according
to
matt,
say
in
his
article
enterprises
get
closer
to
the
app
store,
app
store
experience
with
kubernetes
and
git
ops.
The
big
enterprise
problem
isn't
running
hundreds
of
apps
across
multiple
clouds.
The
big
problem
is
running
the
same
app
consistently
on
just
one
cloud
or
data
center.
C
This
is
definitely
a
really
interesting
opinion
piece,
so
definitely
go
and
check
it
out.
I
had
a
really
really
good
time
reading
it
personally
and
then
we
have
a
couple
announcements,
humber,
bake,
hamburg-based,
kubramatic,
a
company
that
automates
operations
of
kubernetes
clusters
across
multi-cloud,
on-prem
and
edge
environments,
announced
that
it
has
raised
about
six
million
dollars
in
its
seed
round
of
funding.
C
I
think
it's
definitely
very
cool
to
see
smaller
startup
stage
companies
innovate
in
this
busy
space,
as
as
we
have
seen
over
the
last
couple
of
months
and
over
the
past
couple
years
as
well,
and
then,
as
always,
we
cannot
close
out
this
new
section
without
mentioning
security,
somehow
kubernetes
default
configurations
don't
always
provide
optimal
security
for
all
workloads
and
microservices
deployed,
plus
today,
you're
not
only
responsible
for
defending
your
environment
against
vicious
cyber
attacks,
but
also
for
meeting
a
wide
variety
of
compliance
requirements.
C
So
we
have
an
article
that
helps
you
understand:
kubernetes
compliance
and
security
frameworks.
Jonathan
captain
examines
five
major
frameworks
and
how
they
can
help
your
business
use
kubernetes
more
securely,
again,
security,
one
of
the
biggest
issues
that
we've
seen
lately
so
definitely
recommend
you
to
go
and
check
this
article
out
and
while
compliance
may
take,
some
upfront
work,
the
payoff
in
resilience
and
long-term
business
continuity
will
be
worth
it.
In
many
cases,
organizations
discover
additional
benefits,
such
as
optimization
and
eliminating
inefficiency,
inefficient
processes
and
services.
C
I
do
want
to
end
here
with
a
blog
post
from
our
guest
today,
castlin
fields,
as
I
mentioned
earlier,
kubecon
eucfp
closes
on
december.
17Th.
Caslin
has
been
part
of
nine
sessions
at
six
different
cube
cons
and
served
as
a
track
chair
and
cfp
reviewer
in
this
post.
She
goes
over
things.
She
thinks
you
should
know
about
the
cubecon
cfp.
C
This
is
a
really
timely
post
and
I
highly
suggest
you
go
check
it
out
on
her
blog
I'll,
be
posting
all
the
links
so
I'll
make
it
easy
for
you
guys
to
review
some
of
the
stuff
I
highlighted
here,
but
thank
you
and
back
to
you
and
back
to
you,
langdon
and
steve.
A
Thanks
mina,
as
always,
it's
it's
a
good
idea
to
try
to
keep
up
with
the
current
events,
and
I
know
for
me
it
can
be
a
whirlwind
to
try
to
keep
track
plus
you
know
obviously
like
many
of
us.
We
do
a
lot
of
things
that
are
not
just
kubernetes
and
so
keeping
track
of
this
particular
space.
I
think
it's
really
helpful
to
have
kind
of
a
review
there.
A
Definitely
and
a
phone
that
I
don't
even
know
didn't
even
know
worked,
is
currently
raining,
so
that's
kind
of
annoying
all
right.
So
today
we
would
like
to
welcome
our
guest,
and,
let
me
see
oh
there.
It
goes
okay,
we'd
like
to
welcome
our
guest
castlin
fields,
and
thank
you
thank
you
and.
A
As
a
as
kind
of
a
pretty
strong
member
of
the
community
and
pretty
visible
in
that
community,
we
would
like
to
talk
to
you
about
kind
of
what's
going
on
and
in
particular
I
think
we
could
kind
of
start
off
with.
I
know
when
you
were
at
kubecon,
you
gave
you
know
a
keynote
about
multi-cluster
and
obviously
we
would
recommend
people
going
and
you
know
checking
out
the
video
of
of
the
recording,
but
the
I
would
like
to
ask:
why
are
you
interested
in
that
space?
A
What
is
what's
you
know
what
why
are
in
general?
Why
is
the
kubernetes
community
kind
of
interested
in
multi-cluster?
What's
the
what's
the
big
deal
there.
D
D
D
So
I'm
a
contributing
member
of
the
community
and
as
part
of
contributor
comms
in
the
upstream.
Well,
oh
gosh.
We
call
ourselves
a
couple
of
different
things:
contributor
comms
in
the
upstream
marketing
team,
which
is
part
of
the
contributor
experience
team
anyway.
D
That
being
said,
I
also
made
a
blog
post
of
my
kubecon
north
america
keynote.
So
if
you
haven't
seen
it
and
you'd
like
to
check
out
the
content,
you
can
check
it
out
there,
and
I
also
have
the
link
to
the
recording
on
there.
But,
as
you
said,
it's
about
multi-cluster
and
I
think
from
a
variety
of
perspectives.
That's
an
interesting
topic
to
do
a
kubecon
keynote
on
from
the
contributor
community's
perspective.
D
It's
interesting
because
I
mean
kubernetes
came
about
in
2016-
was
the
very
first
commit
to
the
open
source
repo
on
github
june
14th
of
2016,
or
something
like
that.
I
have
it
on
my
wall
usually,
but
I
took
it
down
today,
and
so
it
hasn't
been
around
for
all
that
long
like
it's.
It's
been
around
for
a
few
years,
but
it's
been
steadily
growing.
The
contributor
community
has
grown
immensely.
Of
course,
the
user
community
has
grown
immensely
so
for
the
first
several
years
that
kubernetes
existed.
D
It
was
you
know,
first,
this
new
technology
that
there
was
some
buzz
about,
and
there
were
these
early
adopters
and
now
it's
kind
of
gotten
to
a
point
where
there
are
a
lot
of
companies
using
kubernetes
in
production
today
and
kubernetes
is
a
tool
for
running
workloads
and
applications
at
scale.
So
a
lot
of
these
companies
are
very
large
and
when
you
have
companies
that
are
very
large,
just
one
kubernetes
cluster
will
not
do
so
early
on
in
kubernetes
existence.
D
Multi-Cluster
wasn't
that
big
of
a
deal
because
it
was
already
handling
like
you
could
handle
a
lot
with
a
single
cluster,
but
now,
with
these
really
large
companies
often
very
distributed
companies
using
kubernetes.
There
are
a
variety
of
reasons
why
they
need
to
have
multiple
clusters,
and
so
that
makes
them
ask.
How
do
I
manage
all
of
these
multiple
clusters,
where
kubernetes
is
a
tool
for
managing
the
applications?
Now,
how
do
I
manage
the
clusters
themselves?
D
D
More
folks
are
starting
to
get
involved
with
contributing
to
multi-cluster
workloads,
because
more
companies
need
it.
There's
more
information,
more
customer
use
cases
to
work
off
of
to
build
tools
for
multi-cluster
and
then
from
the
user
perspective.
Of
course,
a
lot
more
people
are
using
it,
so
they
need
those
tools,
so
it
was,
I
think,
a
very
timely
thing
to
talk
about
in
the
cubecon
keynotes.
A
Yeah
definitely
interesting,
and
particularly,
I
think
the
the
challenge
with
multi-cluster
right
is
that
you
don't
always
want
it
to
feel
like
multiple
clusters,
but
then
sometimes
you
do,
and
you
know
so
I
think
that's
a
particularly
challenging
space.
I
think
that's
been
an
interesting
model.
I
think
it
also
plays
into
a
lot
of
these
ideas
of
kubernetes
as
a
control
plane.
A
We've
we've
actually
talked
about
on
the
show
before,
but
you've
also
seen
you
know,
various
people
in
the
community
kind
of
talking
about
this
idea
of
you
know
kubernetes
can
maybe
be
a
back
plane
for
for
lots
of
different
things.
So
I
think
it's
a
it's
a
really
interesting
and,
as
you
say,
kind
of
timely
topic
I
know
steve.
Did
you
want
to
ask
more
about
the
multi-cluster.
B
Yeah,
I
mean,
I
think,
it's
a
really
interesting
space
because,
like
we're,
we've
done
a
lot
of
experience
in
large
clusters,
but
the
way
we
hit
limits
with
our
customer
base
is
it's.
I
think
you
talked
about
it
in
your
keynote.
There's
like
10
000
nodes
within
the
cluster,
but
I
think
back
like
in
the
news
around
gta
and
running
pokemon
go
and
it's
like
one
application,
scaled
really
large.
B
Where
we
get
a
lot
of
tenants
on
our
clusters,
we
typically
run
so
our
customers
run
it
and
so
the
scale
kind
of
breaks
down
more
because
of
a
number
of
name
spaces,
a
number
of
secrets,
per
name
space
and
sed
limits,
and
the
watches
all
the
controllers
just
tend
to
struggle
a
bit
when
you
get
to
a
certain
size.
So
I
guess
I'm
not
asking
a
question,
but
I
was
just
kind
of
curious.
B
Your
thoughts
too,
when
you've
seen
that
explosion
of
you
know
where
it's
a
multi-use
kind
of
cluster,
where
I
think
you
talked
about
the
importance
of
segregation
also
for
security
reasons
between
those
organizations.
So
I
know
if
you've
you've
run
too
much
about
that,
where
it's
packing
a
bunch
of
people,
if
you
will
into
a
cluster
and
then
the
problems,
that's
caused.
D
Yeah
in
my
keynote
I
mentioned
a
few
different
use
cases
where
companies
come
up
against
this
and
they
need
to
have
multiple
clusters,
and
I
love
that
you
pointed
out
several
that
you've
seen
in
real
life,
so
one
of
them
was
multiple
regions
or
environments.
If
you're
running
in
different
regions
or
environments,
then
of
course
you're
going
to
have
to
have
different
clusters,
and
one
of
them
was
this
security
consideration
of.
D
If
you
have
multiple
tenants
that
you
need
to
keep
separate,
what
tools
do
you
have
and
at
what
point
do
you
have
a
separate
cluster,
because
in
a
regular
just
a
single
kubernetes
cluster,
there's
a
concept
of
namespaces
and
role-based
access
control
and
by
using
namespaces
and
role-based
access
controls
together,
you
can
create
a
pretty
solid
structure
for
multi-tenant
use
cases
a
lot
of
them,
but
there
are
still
some
cases
where
businesses
feel
more
comfortable
just
having
workloads
on
separate
clusters,
sometimes
for
compliance
reasons,
sometimes
for
extra
security
just
having
the
whole
cluster
boundary
as
a
security.
D
Boundary
can
sometimes
just
make
things
simpler,
and
sometimes
you
need
that.
So
there
are
a
variety
of
security
reasons.
Why
folks
approach
multi-cluster
and,
like
you
said
it's
also
it's
about
managing
all
these
kubernetes
clusters
together.
I
often
think
about
it
as
kubernetes
for
kubernetes,
because
people
come
to
kubernetes
as
a
management
tool
for
managing
applications
that
scale
across
many
different
computers
of
varying
sorts
and
so
having
a
concept
of
that,
but
for
whole
kubernetes
clusters
is
often
what
people
are
looking
for.
I
find.
B
That
that's
interesting,
because
one
thing
I
was
going
to
ask
about
is
one
of
the
coolest
names
I
think
of
a
sub
project
at
kubernetes
was
uber
nettie's
early
on
what
they
did
the
first
kind
of
wave
at
multi-cluster,
and
then
there
was
cube,
fed
2
kind
of,
and
so
I
was
kind
of
curious
in
the.
What?
Because
there's
been
a
lot
of
learning,
that's
going
on
in
the
community
about
what
to
do
with
multi-cluster.
And
how
do
you
think
you
know
those
lessons
have
played
into
the
current
approaches
of
multi-cluster.
D
Yeah,
the
state
of
the
art
I
used
to
talk
about
cube,
fed
quite
a
lot
because
that
was,
I
think
it
was
a
pretty
interesting
attempt
by
the
community
to
address
this
challenge.
But
when
I
interviewed
the
the
chairs
of
the
special
interest
group
for
multi-cluster
use
cases
within
the
open
source
project,
the
folks
working
on
it,
there
told
me
that
cubefed
was
mostly
informed
by
what
the
contributors
thought
was
going
to
happen.
D
So
they
didn't
have
good
user
data
to
build
these
tools
off
of
so
cube.
Fed
was
very,
and
it
made
a
lot
of
recommendations
about.
This
is
how
you
do
this,
and
this
is
how
you
do
this,
but
over
time
they
found
that
those
were
maybe
a
little
too
rigid
and
they
needed
some
different
solutions
to
actually
solve
the
problems
that
are
happening
with
multi-cluster
today.
D
So
in
the
talk,
I
talk
about
a
couple
of
different
solutions
that
the
folks
in
open
source
are
working
on.
The
main
one
is
the
multi-cluster
services
api,
which
is
new,
and
it
is
a
api
standard
that
the
sig
multi
cluster
is
coming
up
with.
The
interesting
thing
about
api
standards
is
that
they
are
not
implementations,
so
this
multi-cluster
services,
api,
isn't
something
that's
going
to
be
in
kubernetes
itself.
It's
something
where
you're
going
to
have
to
be
using
some
sort
of
environment
that
implements
this
standard,
that
the
open
source
group
came
up
with.
D
But
the
concept
here
is
for
different
kubernetes
clusters
to
be
able
to
share
what
services
they're
running
with
other
clusters
so
that
you
can
log
into
one
cluster
and
that
cluster
can
know
about
all
of
the
services
it
needs
to
know
about,
even
if
they're
running
on
a
different
cluster,
and
that
gives
you
some
really
interesting
capabilities,
which
pairs
really
nicely
with
something
that
the
networking
open
source
group
sig
networking
within
kubernetes
has
been
working
on,
which
is
gateway.
Api
that's
been
around
a
little
bit
longer.
D
There
are
more
implementations
of
that,
but
it's
also
an
api
standard,
so
the
concept
of
gateway
api,
which
I
often
hear
referred
to
as
ingress
v2,
which
I
find
interesting,
but
the
concept
is
basically
to
give
users
better
tools
for
connecting
their
kubernetes
clusters
together.
So
ingress
in
kubernetes
is
a
tool
for
managing
incoming
traffic
to
your
services
from
outside
of
the
cluster
and
so
gateway
api
takes
that
concept
a
bit
further.
It
was
pretty
basic
in
the
initial
implementations
of
kubernetes
and
gateway.
D
What's
going
on
in
other
clusters,
we
start
to
get
a
really
nice
solution
here
for
multi-cluster
environments,
where
you
can
actually
do
more
things
with
managing
multiple
clusters
that
are
not
completely
native
to
kubernetes,
but
at
least
from
the
kubernetes
open
source
project
designed
for
how
they
see
it.
Being
used.
A
Yeah,
I
mean
one
of
the
things.
I
think
that
is
really
you
know
kind
of
interesting
about
how
we
do
development
a
lot
these
days,
which
is
so
much
better
than
it
was
when
I
certainly
got
into
it.
A
Is
you
know,
kind
of
the
idea
of
you
know
approaching
a
problem
once
there
are
users
who
are
actually
experiencing
that
problem
so
that
you
can
kind
of
get
feedback
and
actually
build
on
and
build
what
they
actually
are
looking
for,
rather
than
you
know,
trying
to
build
something
that
you
theorize,
that
they
may
need
right.
You
know,
I
think
a
lot
of
this
has
to
do
with
the
technology
changes
right.
A
It's
so
much
easier
to
you,
know
kind
of
build
something:
that's
incorrect
in
python
and
tear
it
down
and
build
it
again
that
has
made
that
kind
of
style
of
development
significantly
simpler,
but
it
really
it
does
change
things
right
and
I
think
that's
part
of
why
it's
kind
of
important
to
kind
of
follow
the
you
know
the
news
as
it
were
in
in
you
know
your
open
source
projects
or
whatever,
because
you
you
know
people
that
it
is
adapting.
There
is
no
big
massive
road
map
for
the
next
20
years.
A
A
You
know
which
you
know
can
be
a
little.
You
know
a
little
scary.
You
know
you
know
thinking
of
like
mesos
versus
kubernetes.
You
know
a
while
back,
for
example,
but
there
have
been
many
many
others,
but
so
that's
another
reason.
Why
kind
of
keeping
tight
with
the
community
or
you
know
and
and
the
project
itself
is
a
really
good
thing
and
being
honest
within
the
community
about
what's
happening,
I
think
is
also
really
important.
A
You
know
that
you,
you
know
that
it's
not
you
know
it's,
not
some
seeker
cabal,
making
a
decision,
nor
is
it
every
solution.
Is
the
right
answer
right?
It's
that
you
know,
there's
certain
use
cases
and
that
kind
of
stuff.
So
I
think
that's
a
really.
A
This
is
the
multi-cluster
stuff,
I
think,
is
a
really
important
thing
to
watch
as
well
as
the
fact
that
I
think
that
when
you
hear
multi-cluster,
I
think
a
lot
of
people
aren't
thinking
of
what
the
kubernetes
community
really
means
and
what
I
mean
by
that
is,
like
you
know,
when
you
say
multi-cluster,
usually
it
just
means
like
some,
you
know
interface
or
some
ui
or
something
that
you
know
goes
and
triggers
them
independently.
A
B
For
it
yeah
the
similar
that
was
thinking
through,
like
the
use
cases
around
this
networking,
the
gateway
api,
and
it
made
me
think-
and
I
think
landon
touched
a
lot
too.
It's
like
this
just
choices:
the
community,
because
we
heard
some
news
about
istio
and
I
started
thinking
people
here
just
do
on
some
of
these
cases
and
what
that
does,
and
it
solves
some
multi-cluster
mesh
issues
and
people
saw
mesh
there,
and
I
don't
know
what
you
could
say,
maybe
a
little
bit
about
the
different
use
cases
between
the
two.
B
Why
they're
different
how
they
come
together,
or
I
think
that
would
be
that
would
be-
would
help
me.
D
D
I
love
that
you
made
that
connection
between
the
gateway,
api
and
service
mesh.
It's
not
something
that
I
had
thought
much
about,
but
I
talk
about
service
mesh
quite
a
bit
as
well
and
yeah.
There's
a
lot
of
kind
of
parallels
there
in
this
concept
of
managing
ingress,
as
well
as
kind
of
managing
the
networking
of
your
cluster
in
between
your
clusters.
D
D
I
tend
to
try
to
avoid
that,
but
I
think
with
service
mesh,
it's
hard
to
avoid
saying
that
they're
pretty
complex.
They
have
a
lot
of
moving
pieces
and
a
lot
of
things.
When
I
first
started
talking
about
service
meshes,
I
thought
of
them
as
like.
You've
got
your
kubernetes
cluster,
that's
running
all
of
your
applications
and
it's
doing
a
lot
of
really
nice
management
stuff,
but
once
you
start
to
get
into
it,
you
start
to
see
these
gaps
of
things
that
aren't
really
in
scope
for
kubernetes.
D
Things
like
observability
is
something
that's
kind
of
missing
there
and
some
ingress
controls
like
proxies
having
a
proxy
there
with
your
application
that
can
maybe
manage
permissions
for
what
can
talk
to
your
application
at
a
more
granular
level.
Some
logging
and
monitoring.
D
So
there's
a
variety
of
tools
here
that
aren't
really
within
the
scope
of
kubernetes,
but
you
really
need
in
order
to
run
kubernetes
effectively
and
so
service
meshes
came
in
and
they
just
kind
of
had
all
of
these
tools
as
part
of
them,
and
they
were
kind
of
trying
to
fill
all
of
these
gaps,
which
naturally
made
them
sort
of
complex
to
understand
and
to
use
so
they're
trying
to
solve
a
lot
of
different
problems.
D
I
think,
whereas
the
gateway
api
is
really
focused
on
this
problem
of
gateways
and
networking
of
making
sure
that
things
can
communicate
effectively.
So
it
does
address
some
of
those
challenges
that
I
think
that
service
meshes
also
address,
but
it's
much
more
limited
in
scope.
That's
how
I
think
about
it.
That
makes
sense.
A
So
kind
of
maybe
changing
directions
a
little
bit.
You
know
I
I
I
kind
of
you
know
in
the
research
for
kind
of
doing
the
show
right.
There's
you
have
a
lot
of
kind
of
involvement
in
you
know,
kind
of
new
contributor.
A
A
Why
you
know
why
do
you
feel
like
that's
really
important
to
kubernetes
and
or
you
know,
is
it
a
gap
or
what?
And
why
might
do
you
think
it's
a
gap?
You
know
if,
if
that
makes
sense
as
a
question.
D
Yeah
yeah,
that
makes
sense
to
me,
so
it
depends
on
what
perspective
you're.
Coming
from
how
you
see
non-code
contribution
for
the
kubernetes
community,
we
have
this
gigantic
project,
it's
one
of
the
largest
open
source
communities
in
the
world.
Second,
only
to
linux.
I
think,
if
that's
still
the
case.
D
Yeah,
it's
huge
and
it's
got
this
huge
user
base
as
well.
So
there's
always
new
requests
coming
in
there's,
always
new
features
that
need
making,
but
something
that
you
might
not
think
much
about
with
an
open
source.
Technical
project
like
this
is
there's
a
lot
of
behind
the
scenes.
Work
that
does
not
involve
coding
that
keeps
this
project
running.
Some
of
it
is
creating
documentation,
that's
a
form
of
non-code
contribution
for
writing
documentation.
D
Basically,
that
have
to
happen
because
there's
a
lot
of
different
features
of
kubernetes
there's
these
special
interest
groups
which
have
chairs
who
kind
of
manage
what's
going
on
in
those
groups,
but
at
some
point
you
have
to
like
I'm
part
of
the
release
team
right
now,
there's
a
lot
of
non-code
contribution
in
the
release
team
because
we
have
to
I'm
in
I'm
part
of
the
comms
group
for
the
release
team
this
time.
D
So,
for
example,
we
have
to
create
blog
posts
about
here
are
the
different
features
that
are
going
to
come
out
with
the
new
release,
here's
kind
of
an
overview
of
what's
going
on
with
the
release,
there's
a
lot
of
communications
that
have
to
happen
to
make
sure
that
the
user
community
and
the
contributor
community
are
aware
of
what's
happening
in
the
release
and
there's
all
sorts
of
communications
that
go
on
in
the
meantime
about
changes
and
discussions
that
are
happening
in
contributor
communities.
D
Maybe
a
new
feature
came
out
a
while
ago
and
nobody's
really
using
it.
Nobody
seems
to
know
it
exists.
How
do
we
get
people
to
know
that
exists?
So
I
spend
a
lot
of
my
time
on
like
communications
and
marketing
type
non-code
contribution,
so
there's
all
of
these
different
activities
that
have
to
happen
for
the
project
to
be
successful,
that
don't
involve
code
and
I
think,
when
you
think
about
contributing
to
open
source.
That's
not
the
first
thing
you
think
about
usually.
A
Yeah,
I
mean
the
the
documentation
question.
I
always
think
is
really
interesting.
For
many
years
whenever
I
was
leading
a
dev
team,
if
I
got
a
new
person
on
the
team,
their
first
job
was
to
update
all
the
docs
for
the
onboarding
right.
So
you
know
usually,
usually
somebody
did.
You
know
a
half-baked
attempt
at
at
least
initially
right,
but
then
every
time
you
get
a
new
person
right
things
are
new
and
because
they're
new
to
them
it
makes
a
big
difference
and
there
was
a
point
it
was
made
in
the
panel.
A
I
don't
remember
who
exactly
made
it,
but
that
you
know,
as
as
a
newcomer
to
the
community,
you
have
a
lot
of
you
know
kind
of
experience
with
not
kubernetes
that
that
you
can
help
with
things
like
communications
right
where
you
can
kind
of
say:
hey.
Can
you
read
this
over?
Does
it
make
sense
to
you
as
somebody
who
is
not
embroiled
in
this
all
the
time
you
know
or
docs
as
well
right?
A
You
know
kind
of
the
onboarding
content
so,
like
I'm
a
big
fan
of
that
as
well
and
then
what
I
think
is
interesting
about
it,
too,
is
that
non-code
contributions
doesn't
mean
you
aren't
a
coder
necessarily
either
right
is
that
when
you're
approaching
a
project
or
you're
approaching
getting
involved
in
a
community,
you
know
even
as
a
coder
for
many
many
years
now.
You
know
one
of
the
things
I
do
look
at
is
I
look
into
the
documentation.
I
look
at
the
open
issues.
I
look
at
who's
involved
in
the
project.
A
I
look
at
you
know
all
these
kinds
of
different
things
and
I
try
to
give
back
there
for
one
thing,
I
spent
too
much
time
as
a
as
a
college
newspaper
editor
and
as
a
result,
I
you
know
I
fix
grammar
by
default,
so
you
know
so
I
try
to.
I
try
to
contribute
in
little
bits
as
we
go
along
and
I
think
it's
really
really
important.
You
know
whether
you're
a
coder
or
not
a
coder.
I
mean
there's
all
these
kinds
of
things
that
need
to
happen.
A
One
of
the
things
I
wanted
to
also
kind
of
ask
in
a
related
way
about
that
was
it
came
up
a
few
times,
and
I've
heard
it
elsewhere
as
well,
is
that
the
kubernetes
community
is
very
social
compared
to
many
open
source
communities.
Can
you
elaborate
on
what
that
means?
You
know
and
and
like
why,
as
like
somebody
who
is
a
consumer
of
kubernetes,
why
does
that
matter
to
me.
D
Yeah,
I
love
that
question.
That's
really
fun!
Phrasing
too.
I
don't
think
I've
ever
heard.
Someone
refer
to
the
kubernetes
community
as
social,
but
I
think
it's
absolutely
accurate
and
makes
total
sense,
and
I
think
people
should
say
it
more,
but
so
the
concept
here,
I
think,
is
this
actually
reminds
me.
I
was
looking
at
the
the
game
awards
last
night
and
one
of
the
categories
for
the
game
awards
is
games
where
the
developers
of
it,
the
creators
of
the
game,
are
very
engaged
with
the
community
and
the
community
is
very
engaged.
That's.
D
What
kind
of
we
have
going
on
here
with
kubernetes
is
the
folks
who
are
making
kubernetes
the
open
source
contributors
we
have
slack.
We
also
have
the
cncf
slack
that
a
lot
of
us
are
in.
I
have
a
lot
of
people
who
we
chat
with
each
other
and
we
end
up
on
the
cncf
slack
talking
about
a
kubernetes
issue
or
vice
versa,
and
so
we
we're
very
communicative
in
that
respect.
D
We
have
all
these
challenge
chat
challenges,
channels
for
the
different
special
interest
groups
like
contributor
experience,
networking
multi-cluster
they
all
have
their
own
channel.
So
if
you
had
a
question
for
the
people
who
work
on
that
specific
thing,
you
could
go
to
that
channel
and
ask
and
there
they
are
so
that's
really
important
for
end
users,
but
also
we
have
our
own
blog.
So
for
external
communications
that
the
kubernetes
community
is
just
pushing
out
there,
we
have
a
blog.
D
Also
everything
we
do
on
github,
of
course,
is
open
and
available,
and
you
can
look
at
it
all
of
our
meetings,
like
sig
controbex,
even
the
steering
committee
of
the
whole
kubernetes
project
itself.
A
lot
of
those
meetings
are
recorded
and
put
on
youtube.
If
you
ever
want
to
know
what
happened
and
who
was
in
the
room
when
it
happened,
you
can
find
out,
because
all
of
that
stuff
is
open
and
available,
and
you
can
see
it.
A
Yeah,
I
mean,
I
think
you
know,
like
you
kind
of
raise
a
good
point
right,
it's
like
if
you're,
if
you're,
not
sure
about,
what's
going
on
or
like
why
a
decision
was
made
or
what
you
know
whatever
going
back
and
actually
hearing
the
argument
right
really
can
help
a
lot.
You
know
sometimes
it
it
reinforces
the
reason
why
you
disagree
with
them,
but
you
know
it
can
also
you
know,
kind
of
educate.
A
The
you
know
give
you
a
little
bit
of
background
and
tell
you
why
you
know
the
choices
were
made
and
whether
it's
a
good
you
know
and
and
maybe
where
it's
going
to
go
in
the
future.
You
know
because
I
I
think
you
know
rarely
does
it
occur-
that
you
know
when
you
make
a
decision,
for
example,
to
drop
a
feature.
It's
not
that
the
feature
is
completely.
A
You
know
useless,
quote
unquote
as
much
as
it
is
the
approach,
maybe
isn't
the
right
one
or
you
know,
and
so
there's
a
plan
to
do
something
else
or,
as
we
were
kind
of
talking
about
earlier,
the
users
aren't
there.
So
we're
not
getting
good
feedback
on
the
features.
So
we
don't
necessarily
want
to
support
it,
because
we
don't
know
that
it's
actually
working.
You
know,
then
it
gives
you
an
opportunity
as
a
user
right
to
say:
oh
wait.
A
No,
I
am
here,
you
know,
please,
you
know,
please
bring
it
back
or
please
let
me
how
can
I
contribute
so
that
I
can
help
you
bring
that
you
know
feature
or
whatever
it
is
back
yeah?
So
I
think
I
thought
that
was
an
interesting
remark
like
I
said,
I've
heard
it
in
kind
of
a
couple
different
contexts.
A
A
It's
a
minute,
but
one
of
the
things
it
comments
on
is
that,
while
that
role
is
kind
of
new
as
a
job
title,
the
role
has
actually
existed
for
a
very
long
time,
and
I
know
I
played
it
in
a
lot
of
different
projects.
You
know
well
before
I
had
it
as
a
title,
but
I
think
kubernetes
you
know
kind
of
the
cncf
ambassador
community,
as
well
as
there's
a
lot
of
developer
advocacy
type
people
in
the
community.
A
I
think
that
has
really
increased
that
communication
and
that
social
aspect
of
it,
because
you
have
you
know
developer
advocates
generally
speaking-
are
kind
of
good
communicators
by
default
right.
So,
as
a
result,
I
think
that's
really
improved
the
communication
within
that
community
and
you
know,
there's
a
number
of
other
communities.
We
can
mention
that
you
know
don't
have
similar
or
have
kind
of
the
reverse
challenge
that
you
know,
but
we
won't
talk
about
those
today.
Yeah.
B
That
was
gonna
yeah.
I
was
gonna
notice
because,
like
the
the
social
part
was
an
interesting
way
to
phrase
it
too,
because
I
think
it
goes
a
little
bit.
What
castle
has
said
is
it's
a
very
welcoming,
very
helpful?
It's
very
inclusive
group,
so
it's
like
that's
the
thing.
Everyone
feels
welcome,
so
they're
willing
to
feel
more
social
kind
of
about
it
as
a
way
of
not
just
going
to
it
for
the
social
aspects,
but
really
it's
that
really
kind
of
feeling
of
community
and
belonging.
B
So
it's
really
been
interesting
to
see
what
I've
seen
as
everyone
get
involved
in
those
that
I
follow.
So
I
think
it's
really
and
and
langdon's
point
it's.
You
know
kind
of
refreshing
from
some
of
the
other
projects
that
have
existed
and
how
they've
been
run,
and
I
think
it
goes
to
the
early,
the
originators
and
the
way
they
wanted
these
to
be
accepted
and
grown,
and
so
I
think
it's
it's
really
stuck
to
its
roots.
B
So
it's
really
been
been
helpful
to
see
another
and
not
trying
to
make
a
complete
transition
from
there,
but
I
think
it
might
be
a
natural
one
is
because
of
the
cultural
papers,
things
we
talked
about
and
you're
working
towards,
and
that's
that's
that
date's
coming
up
as
far
as
that
deadline
and
that's
a
great
way
for
people
to
share
their
experiences,
whether
it's
at
any
level,
whether
they're
a
lead
in
it.
But
also
you
know
what
that
process
looks
curious.
B
If
you
have
any
kind
of
quick,
helpful
hints
of
what
it
means
to
write,
a
good,
abstract
and
and
that
whole
process.
D
Absolutely-
and
I
want
to
also
make
a
comment
on
something
you
were
saying
there.
I
recently
read
nadia
eggball's
book
on
open
source
working
in
public,
which
is
here
on
the
shelf
behind
me,
the
red
one
and-
and
she
makes
a
really
great
comment
in
there-
that
the
reason
that
a
lot
of
folks
don't
contribute
is
not
because
it's
technically
difficult
or
they
don't
have
the
skills.
D
D
A
A
I
have
a
19
year
old
son
and
his
approach
to
doing
things
in
public
is
very
different
than
my
traditional
approach
of
doing
things
in
public
right,
and
so
I'm
really
curious
to
see
how,
when
we
as
we
see
more
of
them
kind
of
move
in
to
you
know,
positions
of
of
you
know,
visibility
in
a
sense,
you
know,
are
they
more
willing
and
more
open
to
doing?
That
is
that
is
that
maybe
the
positive
side
of
you
know
the
the
very
much
drop
in
general
privacy.
You
know.
A
Maybe
there
maybe
there
are
some
upsides
to
to
all
of
that,
but
going
back
to
steve's
question,
you
know.
A
A
A
I
I
have
run
many
a
conference
as
well
and
yeah
the
the
pile
you
get
on
cfp
announce
day
and
the
pile
you
get
on
cfp
close
day
is
is
really
kind
of
hilarious.
D
Yeah
and
also
it
looks
like
we
have
a
really
interesting
question
from
the
audience
which
we'll
get
to
in
a
minute,
but
talking
about
abstracts
for
kubecon.
First,
so
in
my
blog
post
I
go
over
a
lot
of
information.
It
was
really
hard
to
figure
out
what
to
fit
into
the
blog
post.
I
realized
that
there
are
a
lot
of
things
that
go
into
a
kubecon
call
for
papers,
and
I
want
people
to
know
about
how
that
process
works
and
what
the
meaning
of
it
is
and
what
it
means
for
you.
D
So
it
was
hard
to
figure
out
all
the
pieces
to
put
in
there,
but
the
blog
post
goes
over
the
timeline
of
here's.
The
the
date
that's
coming
up,
of
course,
is
the
close
of
the
cfp
and
for
most
folks,
that's
kind
of
where
your
work
ends.
D
For
now,
is
you
submit
something,
and
then
you
kind
of
throw
it
into
the
void
and
wait
for
judgment,
but
in
the
blog
post
I
go
over
all
the
steps
that
happen
in
that
waiting
period
so
that
you
understand
what
you're
waiting
for
and
it's
actually
they
get
the
the
judging
done.
D
D
This
is
a
good
opportunity
for
that
and
there
are
a
variety
of
different
types
of
talks
at
kubecon,
so
it
doesn't
have
to
just
be
a
25-minute
talk.
There's
also
panels.
I
think
this
year,
they're
doing
lightning
talks.
They
don't
always,
but
I
have
to
check
on
that.
I
think
there
might
also
be
some
concept
of
workshops,
but
so
kubecon
has
a
variety
of
different
ways
that
you
can
communicate
your
expertise,
your
knowledge,
your
experiences
using
not
just
kubernetes.
We
talk
about
kubecon,
mainly,
but
it's
also
cloud
native
con.
It's
the
whole
cncfs
conference.
D
So
if
you
have
experiences
contributing
to
open
source
projects
or
working
with
open
source
projects,
preferably
that
are
part
of
the
cncf,
those
are
also
really
valuable.
Experiences
to
share-
and
the
important
thing
to
keep
in
mind
here
is
the
audience
of
kubecon,
the
folks
you're
talking
to
are
going
to
be
contributors
to
these
projects,
they're
going
to
be
users
of
these
projects,
and
that
consists
of
a
variety
of
roles.
It's
not
just
technical
folks
who
are
doing
coding
or
running
these
projects.
D
There's
also
a
lot
of
folks
there
from
organizations
that
you
might
not
normally
think
of
like
sales.
Of
course
there
are
program
managers
or
project
managers,
so
there
are
folks
who
aren't
directly
working
with
these
things,
who
need
to
know
how
they
work.
So
the
variety
of
different
kind
of
these.
D
To
appeal
to
and
there's
so
much
information
that
you
might
have,
that
would
be
valuable
to
share
and
the
kubernetes
community
really
encourages
new
folks
if
you've
never
given
a
talk
like
that
before,
but
you
have
something
that
you'd
really
love
to
share
with
those
types
of
communities.
D
We'd
love
to
have
your
cfp
well
cfp
by
the
way
call
for
papers
is,
like
I
said,
just
an
application
to
speak.
It's
saying:
here's
the
topic!
I
want
to
talk
about,
here's,
how
it's
relevant
to
the
community
and
here's
some
supporting
resources.
My
number
one
tip
for
anyone
doing
this
provide
any
supporting
resources.
You
have
about
what
you
want
to
talk
about
if
you've
written
a
blog
post
on
the
topic.
If
your
company
posted
something
about
your
project,
if
there's
anything
out
there.
A
I
might
even
go
further
in
the
sense
that,
if
you
want
to
propose
an
abstract,
go
write
a
blog
post,
so
that
you
can
include
it
as
supporting
resources
like
if.
A
B
Tell
them
what's
in
it.
That
was
interesting
because
I
was
gonna.
I
was
gonna
ask
about
that,
like
you
said
they're
looking
for
new
speakers,
but
you
know
going
through
the
submission
process
and
and
the
kind
of
selection
rating
voting
there's
a
little
bit
of
like
making
sure
people
have
some
speaking
experience
like.
Sometimes
they
want
to
make
sure
that
you
know
it's
going
to
be
a
quality
style,
but
you
talk
about
like
sort
of
have
a
little
bit
of
history.
B
If
you
will,
which
is
you
know
hard
to
say,
to
do
now
on
december
7th,
but
just
so
people
can
set
their
expectations
on
whether
they
can
just
first
time
ever
speaking,
submit
one
versus
you
know:
go
through
a
meet
up
or
two
and
then
kind
of
say.
Well,
this
is
getting
good
retraction.
So
I
was
curious
if
you
could
coach
a
little
bit
of
that
yeah.
D
Yeah,
of
course,
if
you
have
an
idea
and
you've
never
spoken
ever
anywhere
before
it's
a
great
idea
to
try
to
get
that
talk
in
at
something
like
a
meet-up.
Of
course,
a
lot
of
those
are
virtual,
these
days,
or
maybe
even
just
present,
to
your
team
internally.
You
can't
like
put
a
link
to
that
recording
in
your
your
submission,
but
you
can
say
hey.
I
gave
this
presentation
to
my
team
and
I
got
this
feedback
so
that
the
judges
know
that
it's
real,
so
it
doesn't
just
have
to
be
public
public
speaking.
D
It
can
also
be
to
smaller
groups
as
long
as
you're
practicing
what
you're
doing
and
you're
showing
that
you
are
putting
thought
into
the
process
of
developing
yourself
as
a
public
speaker
that
can
help
to
show
that
you're
going
to
give
a
good
talk
and
there
are
occasional
instances
where
someone
who
doesn't
really
have
any
visible
references
for
public
speaking
ends
up
speaking
at
kubecon
or
other
events.
D
If
you
just
have
a
really
good
idea
that
you
explain
really
clearly-
and
you
demonstrate
your
communication
capabilities-
maybe
through
blog
posts-
maybe
through
other
mediums-
that
can
also
help
the
the
reviewers
to
know
that
you're
going
to
give
a
good
talk.
A
I
would
also
kind
of
throw
you
you
kind
of
said
meetups
on
kubecon
right,
but
there's
there's
also
an
in-between
there
of
the
smaller
conferences
and
not
to
you
know.
You
know
pitch
my
own
show
too
much,
so
we
actually
do
a
conference
here
called
dev
conf
us
there's
another
one
devconf
cz,
but
devconfus.
A
Actually
all
of
them
are
specifically
targeting
new
speakers
as
a
as
a
way
to
say:
hey.
Never,
given
a
speech,
you
know
a
talk
before
we
do
speaker
coaching.
We
do
abstract
coaching.
We
do.
We
actually
do
attendee
coaching
as
well,
so
that
you
know
as
a
way
to
kind
of
break
into
maybe
something
a
little
smaller
before
you're,
going
to
something
quite
as
big
as
as
kubecon
or
cloudnativecon.
A
A
In
seattle,
that's
that's
smaller
than
a
seagull.
That's
it
seagull.
D
A
D
B
D
A
Fringe,
which
I
also
think
is
a
hilarious
concept,
so
we
don't
have
a
ton
more
time.
If
you
don't
mind,
I
kind
of
want
to
move
on
a
little
bit
and
kind
of
ask
something
that
I
haven't
seen
you
talk
very
much
about
before,
but
one
of
the
things
that
I
think
has
been
really
interesting,
particularly
during
the
pandemic,
is
the
kind
of
growth
of
twitch,
for
example,
as
places
to
learn
about
how
to
do
tech.
A
You
know
not
just
play
video
games,
you
know
we
don't
pull
the
minecraft.
You
know
player
million
views,
you
know
million
concurrent
users
at
the
same
time,
but
there
is
a
you
know
very
quickly.
Growing
consumption
there,
the
other
one
that
I
think
is
really
hilarious,
is
learning
tech
stuff
on
tiktok,
which
I
find
really
interesting
and
really
hard
and
I'm
just
kind
of
curious.
What's
your
opinion
there?
What
are
your
thoughts
there?
I
don't
know
if
you're
a
video,
medium
kind
of
person.
I
know
I'm
not
particularly.
D
Yeah
I
have
some
similar
eccentricities
where
I
produce
some
types
of
content
that
I
don't
consume
as
much.
I
always
feel
a
little
odd
doing
this,
but
I'm
really.
C
D
Yeah,
I'm
really
excited
for
the
huge
variety
of
different
types
of
content,
though
that
are
coming
out
these
days,
whether
it's
live,
streams
or
videos
or
tick
tocks,
like
you,
said,
there's
some
really
interesting
coding
and
technology,
tick,
tocks,
podcasts
blogs
I
like
to
do
art
and
comics,
which
I
guess
that
we
haven't
mentioned,
but
my
my
keynote-
I
illustrated
my
whole
keynote,
so
the
blog
post
is
all
illustrated.
D
I
have
a
lot
of
fun
with
that
and
I
think
that's
a
big
part
of
making
technology
accessible
is
having
it
in
a
lot
of
different
forms.
It's
really
tough
to
learn
technology,
sometimes
because
it
doesn't
really
apply
to
our
everyday
lives
in
a
lot
of
ways,
especially
something
like
kubernetes
and
these
technologies
that
are
really
meant
for
operating
at
scale
and
large
companies
and
helping
them
to
do
the
work
that
they
need
to
do
for
a
lot
of
folks,
that's
not
part
of
their
daily
life.
D
A
Right,
yeah
yeah,
I
think
that's
the
the
part
that's
been
particularly
interesting.
One
of
the
things
I
really
find
interesting
about
the
streaming
in
particular.
Is
it's
not
edited
normally
right,
so
you
you
can
watch
an
expert
fail
and
how
they
recover.
But
the
really
hard
part
to
learn
right
is
how
do
you
recover?
A
How
do
you
debug,
which
is,
I
think,
one
of
the
things
that's
really
difficult
to
learn
without
just
straight
up
experience,
so
I
think
that's
one
of
the
things
that
I
find
really
interesting
about
twitch,
so
you
brought
up
the
comics
right,
and
so
I
wanted
to
bring
that
up.
I
mean
I'm
so
jealous.
You
know
I've
seen
your
talks
right.
I've
seen
there's
another
guy.
A
I
know
just
pavlin
who
also
illustrates
his
own
talks,
which
I'm
like
I
just
you
know
whatever
and
then
there's
mo
duffy
of
the
fedora
community
who's
been
doing
comic
books
to
explain
tech
they're,
currently
working
on
one
about
k-native.
So
I
think
that's
a
really
interesting
model.
D
A
Right
right,
yeah,
it's
kind
of
crazy,
the
you
know
becoming
a
college
professor
right.
I
know
way
more
about
the
stuff
I'm
teaching
now
than
than
I
ever
did
before.
Right.
The
ins
and
outs
really
really
deeply.
So
it's
been
really
interesting.
So,
let's
see
do
we.
A
D
D
I
don't
always
know
their
role
titles,
so
it's
possible
that
I've
met
folks
who
were
doing
that
for
the
cncf
before,
but
this
person
was
kind
of
new
to
the
role,
and
so
we
spent
quite
a
good
amount
of
time
talking
about
what
does
developer
advocacy
mean,
especially
with
the
cncf
and
kind
of
exploring
what
the
community
was
doing
and
all
sorts
of
devrel
type
things.
So
I
it
appears
that
the
cncf
is
has
at
least
hired
one
developer
advocate
or
developer
relations
person.
D
I
don't
think
that
they
will
ever
do
it
on
the
scale
of
like
every
project
gets
their
own.
I
mean
maybe,
but
if
they
did,
it
would
only
be
for
like
graduated
projects.
So
for
anyone
not
very
familiar
with
the
cncf,
there
are
so
many
open
source
projects
that
are
part
of
the
cncf
and
cncf
is
a
non-profit
organization.
D
That's
goal
is
to
benefit
open
source
cloud
native
technologies,
and
so
they
provide
a
lot
of
really
nice
tools
like
a
code
of
conduct
that
applies
across
all
of
their
projects,
some
varying
management,
tooling,
and
capabilities
and
processes
that
they
give
to
their
projects
and
also
some
marketing
that
they
do
for
the
various
projects
and
projects
usually
come
in
around
the
sandbox
or
incubating
stage.
D
Sandbox
is
something
that
you
maybe
has
a
small
contributor,
maybe
not
a
whole
lot
of
end
users
incubating
you
start
to
get
a
bit
bigger.
Your
contributor
group
is
more
diversified
across
a
variety
of
companies,
maybe
across
a
variety
of
locations,
you're
starting
to
get
more
end
users,
and
then
graduated
are
projects
like
kubernetes,
where
has
huge
user
base
and
a
huge
contributor
community,
that's
very
robust
and
likely
to
keep
going
for
a
long
time.
D
A
Well-
and
I
mean
you're,
because
it's
an
open
source
project
involved
with
a
lot
of
you-
know
very
large
companies
involved.
There
are
a
lot
of
developer,
advocates
being
provided
to
quote
unquote
the
cncf
right.
You
know
I
can.
I
can
name
at
least
one
at
google.
You
know
I
can.
I
can
name
a
few
at
red
hat,
you
know
so
so
there's
there
are
a
lot
of
those
opportunities
as
well.
You
know,
usually,
but
to
kind
of
your
point
right,
they're,
usually
a
little
broader
than
than
one
project.
A
You
know,
or
you
know,
actually
one
of
the
chats
in
the
in
or
one
of
the
conversations
in
the
chat
is
talking
about.
You
know
kind
of
platform
as
a
whole
kind
of
advocates.
You
know
it's
funny,
because
I
read
that
and
I
immediately
think
linux,
but
we
also
were
talking
about
kubernetes
here
too
right
as
the
platform
itself,
and
you
know
so.
I
know,
for
example,
I
know
red
hat.
A
Has
that
or
or
did
when
I
left
right,
you
know
and
I
don't
what's
what
is
your
platform
or
what
is
your
kind
of
advocacy
like
focus
quote
unquote?
Is
it.
D
It's
a
variety
of
things
for
there's
always
kind
of
the
the
business
side
of
it,
at
least
for
my
work.
There's
the
business
side
of
it
and
there's
the
community
side
of
it.
That's
true
for
any
developer
advocate,
because
our
goal
by
the
way
for
developer
advocates
is,
we
are
advocates
for
the
developers
or
or
users
generally
of
these
technologies.
It
doesn't
just
have
to
be
developers,
even
though
we
use
that
term.
D
It's
very
very
broad,
so
my
work
and
one
thing
that
I
tell
a
lot
of
folks
who
are
interested
in
the
field
of
developer,
advocacy
and
developer
relations-
is
that
some
companies
have
developer
advocates
or
developer
relations
as
part
of
their
sales
groups,
and
that
can
be
really
tough
for
the
developer
advocate
to
do
the
work
they
need
to
do
because
you
come
in
and
you
have
to
be
like
well.
I
am
part
of
sales
so
and
that
instantly
any
community
that
you're
talking
to
any
user.
That
you're
talking
to
is
like.
D
Yeah,
it
changes
the
relationship.
I
don't
know
if
I
want
to
talk
to
you
about
my
problems,
because
then
you're
going
to
try
to
sell
me
something
so
that
just
makes
our
job
as
developer
advocates
really
hard
because
our
goal
is
to
advocate
for
you.
We
want
to
hear
about
your
problems
so
that
we
can
make
our
products
better
and
if,
if
you're,
not
willing
to
communicate
with
us,
then
that's
not
helping
us
so.
A
Yeah
one
of
the
things
I
did
at
red
hat.
Actually,
when
I
first
started
there
was
you
know
my
first
role,
there
was
a
developer
advocate
and
I
was
like
well
now.
I
need
to
meet
all
of
the
engineers
right,
and
so
I
started
what
I
referred
to
as
the
sticker
depot,
and
so
I
started
keeping
stickers
on.
We
had
really
big
deaths
in
our
office,
so
I
had
kind
of
this
empty
area
on
my
desk.
I
would
keep
stickers
there
and
I
had
a
take.
A
A
sticker
leave
a
sticker
policy
and
I
got
to
know
everyone
right,
because
that
worked
really
well
to
get
people
to
drop
by
and
say
hi,
and
so
I
got
to
know,
lots
and
lots
of
engineers
see
it's
even
harder
than
now
than
it
was
then,
because
I
think
that
red
hat
was
about
5000
people
that
then
you
know
maybe
half
or
something
being
programmers,
and
you
know
now
it's
12
000
plus
you
know
so
so
it's
a
little
bit
more
difficult
but
yeah
getting
to
know
all
the
engineers,
because
you
want
to
be
able
to
communicate.
B
A
You
want
to
be
able
to
communicate
well
yeah
if
you
include
ibm,
if
you
want
to
be
able
to
communicate
kind
of
both
outbound
and
inbound
about
what
is
going
on
with
their
experience.
You
know
what
a
developer's
experience
is.
I
I
thought
it
was
a
really
interesting
job.
You
know,
but
I
I
left
it
because,
as
I
joke,
they
got
tired
of
me
complaining
and
made
me
come
and
fix
stuff
in
engineering.
So
so
that's
what
I
went
and
did.
B
Even
look
at
like
I
forget
which
kubernetes
it
was
like:
60
percent
of
the
attendees
were
developers
in
seattle
and
I'm
like
it's
like,
but
then
you
look
at
the
technologies
you
use
these
terraforms
and
like
some
of
the
things
so
like
a
lot
of
them,
are
kind
of
some
people
would
call
infrastructure
here,
but
really
they
see
themselves
as
developing
for
the
infrastructure,
as
well
as
representing
their
developers.
In
the
end,
you
know
helping
them
be
productive.
D
A
D
A
A
Right
right
right,
so
that's
a
problem
when
you're
doing
like
surveys
right
if
you're
handing
them
out
you
know
it
obviously
tends
towards
bias.
We
are
just
about
out
of
time,
so
I
don't
want
to
you
know
kind
of
go
over
too
much.
I
did
want
to
get
to
my
final
final
question,
which
was
that
we
saw
your
git
cheat
sheet,
what
you
know
and
I've
been
working
on,
trying
to
actually
have
a
location
where
I
could
like
stick
cheat
sheets.
What
any
other
cheat
sheets
you!
You
strongly
recommend.
D
Oh
yeah,
you
mean
this
one.
D
Documentation,
I
love
fun
fact:
style
learning,
yeah.
C
D
I
think
putting
them
on
walls
putting
them
as
mouse
pads.
All
sorts
of
places
is
a
great
great
place
for
fun
fact.
Cheat
sheets.
A
Right
right
exactly
well,
thank
you
so
much
for
coming,
you
know,
and
you
can.
You
can
find
caslin
on
her
blog
at
caslin,
rocks
or
clutchline.rocks
and
on
twitter
as
your
caslin
fields
right
on
twitter,
and
you
know,
obviously,
and
speaking
at
lots
of
conferences,
and
you
know
going
and
advocating
for
kubernetes
and
cncf
all
over
the
place.
So
thanks
so
much
for
coming
and
giving
us
a
little
insight
into
how
you
see
what's
happening
at
kubernetes.