►
From YouTube: Why is Anyone Using Kubernetes Anyway? - Tasha Drew & Josephene Pynadath, Gaby Cesar, Carl J Pearson
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.
Why is Anyone Using Kubernetes Anyway? - Tasha Drew & Josephene Pynadath, VMware; Gaby Moreno Cesar, IBM; Carl J Pearson
Have you ever taken a step back and wondered, what is up with this whole Kubernetes thing? Why are people using it all over the place? Is it becase of Phippy and Captain Kube? The Docker whale being so cute and retro? Or is there something else going on? The team at SIG Usability had these questions too, and we have embarked on a two year user research study to find out what exactly is going on. Our goal is to make sure the upstream Kubernetes' community deeply understands the needs and goals of the users of Kubernetes, and how they are met and not met today. Join this talk for a deep dive into our study and data, and what we're learning about our users. Spoiler: getting started with Kubernetes is real hard, and we should fix our on-ramp. Learn more at our talk!
A
B
C
A
Cool,
so
a
quick
introduction
to
our
special
interest
group,
so
we
are
part
of
the
upstream
community
in
kubernetes
sig
usability,
and
we
are
tasked
with
the
mission
to
look
at
core
and
user
usability
of
the
kubernetes
project.
So
this
ends
up
covering
topics
like
user
experience,
accessibility
and
the
goals
of
our
sig
are
to
ensure
that
the
kubernetes
project
is
maximally
usable
by
users
of
a
variety
of
different
backgrounds
and
abilities.
I'm
one
of
the
co-chairs,
gabby
is
the
other
co-chair.
A
Currently,
the
main
project
we've
been
driving
as
a
sig
is
a
jobs
to
be
done.
Study
that
we've
presented
on
at
previous
kubecons
and
are
continuing
to
drive,
gather
data
for
with
the
goal
to
eventually
be
able
to
release
all
of
this
data
and
use
it
as
a
foundational
open
source
block
that
we
can
then
drive
additional
studies
into
user,
behavior
and
user
needs
from.
We
do
have
monthly
meetings
of
our
upstream
group.
They
are
tuesday
at
10
a.m.
A
Pacific,
if
you
want
to
engage
with
us,
some
of
the
easiest
ways
are
via
these
links
at
the
bottom
of
this
slide.
So
you
can
join
our
slack
group.
We're
in
the
kubernetes
slack,
and
then
we
have
a
channel
called
sig
usability
that
we
all
are
in.
We
have
a
github
page
where
we
store
project
information
and
then
finally,
we
have
a
google
group
and
if
you
join
our
google
group,
you
will
automatically
get
the
calendar
invitations,
including
the
zoom
information.
So
you
can
attend
our
meetings
and
you.
A
A
B
Sure
tasha,
so
there's
kind
of
like
a
term
in
the
user
research
field
called
jobs
to
be
done,
research
that
is
really
cool
because
it
takes
kind
of
like
the
best
of
qualitative
research
which
we
think
of
in
terms
of
you
know,
I'm
gonna
go
interview
users,
so
it
takes
qualitative
and
then
the
best
of
quantitative,
because
what
you
do
is
when
you're
interviewing
people,
sometimes
they
say
things
that
you're
like.
Oh,
that's
super
interesting,
but
I
wonder
how
many
people
like?
Is
it
a
real
market?
D
D
A
C
So,
what's
interesting
about
this
is
user
research
in
a
more
formal
process
isn't
often
applied
in
the
open
source
space
people
get
tons
of
user
feedback,
but
applying
this
more
kind
of
structured
user
research
approach,
I
think,
is
kind
of
a
new
thing
that
we
see
in
the
developing
the
open
source
world,
especially
so
one
thing
that
we've
had
to
figure
out
that's
a
little
different
than
the
rest
of
the
kubernetes
contributors
is
something
around
security.
Of
course,
security
is
really
big
in
kubernetes.
C
Overall,
that's
obviously
a
huge
priority
across
a
bunch
of
different
working
group
areas,
but
for
us
the
domain
of
security
looks
a
little
different,
so
we're
like
gabby
mentioned
actually
interviewing
people,
so
we
have
videos
and
recordings
of
them
talking
about
the
way
their
organizations
work
and
one
way
to
get
the
best
findings
from
people
is
to
make
sure
they
feel
comfortable
to
share
anything
that
they
might
want.
So
we
have
to
make
sure
that
those
findings
are
anonymized
and
their
identities
are
protected
from
their
actual
findings.
So
you
know
they
can
speak
freely.
C
So
that's
one
thing
we've
had
to
figure
out.
Is
you
know
how
do
we
protect
our
users
and
their
identities
and
and
keep
that
information
secure
and
in
the
open
source
world?
You
know
we
have
a
lot
of
really
interested
and
excited
people
that
are
kind
of
jumping
into
the
project,
so
we
have
to
come
up
with
some
more
rigorous
processes
to
figure
out.
You
know:
where
are
we
going
to
store
these
videos
who
has
access
to
them?
C
How
are
we
going
to
keep
these
videos
over
time
and
you
know
discard
them
eventually?
Where
are
we
keeping
the
findings
who
has
access
to
them?
So
we've
had
to
come
up
with
some
more
operational
components
to
figure
out.
You
know
how
we
protect
the
users
that
are
ultimately
serving
this
research
project
so
a
little
bit
of
a
different
take
on
security
than
I
think
most
people
when
they're
thinking
about
kubernetes
working
groups.
A
A
You
know
that
you're
thoughtful
about
it,
but
at
the
same
time
we're
balancing
that
with
the
needs
to
be
open
and
share
things
with
upstream,
so
others
can
leverage
them,
and
so
that's
kind
of
the
line
that
we've
been
walking
and
really
kind
of
carving
out
for
ourselves.
Since
it's
a
different
use
case
than
many
of
the
other
cigs
and
working
groups
in
upstream
are
dealing
with
so
yeah,
it's
cool.
A
B
Do
it
in
an
open
source
type
of
environment,
but
if
you
haven't
done
it
before
one
of
the
opportunities
that
we
offered
was
for
people
to
shadow
these
interviews,
just
to
kind
of
learn
how
they're
conducted
the
opportunities
that
we
have
available
now
are
more
around.
Now
that
we
have
actually
finished
our
phase
of
interviews
now
we're
going
through
and
analyzing
them.
So
we're
looking
for
things
like
what
are
people
specifically
doing,
and
so
you
know
that
can
be
a
little
bit
time
intensive.
B
But
one
of
the
things
that
we
are
offering
is
you
know
just
training
up
people
and
or
just
giving
tons
of
examples
on.
How
do
you
go
through
a
transcript
of
an
interview
and
highlight
or
identify
behaviors
and
so
again,
like
the
the
tagging
contributor
role
and,
ultimately,
that
will
be
reviewed
by
by
my
josie
carl
myself,
just
to
kind
of
like
have
some
type
of
quality
review
to
the
process,
so
so
yeah.
C
C
I
think
there
have
been
more
research
contributions
in
other
projects
that
are
more
usability
focused
or
it's,
like
you
know,
fix
this
button.
This
is
very
concrete.
What
we're
doing
is
a
little
bit
higher
level,
hopefully
a
little
bit
more
influential,
where
you
can
really
reshape
strategies
and
make
sure
that
you're
kind
of
pointing
the
ship
in
the
right
direction.
C
So
I
think
that's
one
thing
that
remains
to
be
seen.
I
think
a
big
thing
will
be
socializing.
The
findings
make
sure
that
we
really
get
to
share
them
widely
and
make
people
understand
just
how
we
came
to
the
conclusion
that
you
know.
We
don't
just
think
these
are
fun
they're
like
good,
that
we
actually
have
a
pretty
rigorous
empirical
process
to
get
there.
A
D
So
keep
in
mind
we're
still
synthesizing
this
research,
and
this
is
like
what's
on
top
like
at
top
of
mind
right
now.
Maybe
when
we
do
the
full
research,
the
findings
might
be
a
little
bit
different.
But
a
number
of
folks
mentioned
hype
and
they've
spoken
about
the
fact
that
the
decision
was
sort
of
made
because
the
market
is
moving
in
that
direction
and
they
didn't
want
to
be
left
behind.
D
C
Now,
as
it
gets
more
mature
and
get
into
a
new
place
and
say,
I
think
we
could
set
this
up
in
a
way
that
you
know
might
serve.
Xyz
need
a
little
bit
better.
So
there's
a
little
bit
more
kind
of
institutional
knowledge.
Now
that's
moving
across
companies,
although
I
would
say
that's
more
rare
now,
I'd
be
curious
to
see
if
it
gets
more
common
later
down
the
road.
B
B
You
know
just
having
that
community
and
also
just
generally,
you
know,
for
the
people
that
do
kind
of
like
start
trying
to
put
together
like
proof
of
concepts
for
kubernetes,
and
they
just
kind
of
discover
the
api
and
just
kind
of
like
how
well-formed
it
is.
I
think
that
can
be
really
exciting
for
a
company
that
has
done
all
of
this
kind
of
like
manually
and
now
they're
discovering
that
they
can
just
think
about
it
in
terms
of
software.
A
D
So
those
companies
that
were
talking
about
the
hype
around
kubernetes
a
lot
of
the
challenges
that
these
organizations
deal
with
is
the
fact
that
an
upfront
cost
has
been
made
in
order
to
transition
to
kubernetes.
But
then
there's
no
runway
for
onboarding
developers
or
rewriting
applications
so
that
they
can
best
utilize
kubernetes.
D
A
When
we
do
speak
to
users
who
do
manage
to
make
that
full
evolution
into
writing,
kubernetes
native
applications
versus
perhaps
cloud
or
container
native
applications,
what
then
do
they
or
do
they
not
find
beneficial
about
kubernetes?
At
that
point,
when
they're
really
trying
to
adopt
it,
you
know
holistically.
C
Part
of
it
is
just
like
you
know,
spin
something
up
and
see
how
it
breaks
and
figure
it
out
from
there
and
that
they're
really
quick
to
be
able
to
do
that.
I
think
the
other
side
of
that
is
the
kind
of
developer
kind
of
like
what
the
end
user
of
the
kubernetes
might
be.
Is
it's
kind
of
a
different
story.
It
can
be
a
bit
more
more
challenging
for
someone
that
isn't
as
infrastructure
oriented
to
to
get
on
board
and
learn
kind
of
the
unique
ways
that
kubernetes
will
interact
with
their
applications.
C
So
that's
something
that
it
seems
like
a
big
job
of
the
more
administrator
role
is:
is
helping
developers
on
board.
So
you
know
they
can
get
their
hands
dirty
really
quickly,
but
then
they
have
to
bring
those
developers
up
to
speed,
which
can
be
a
big
challenge.
There
aren't
as
many
formal
resources
for
that
partially
because
a
lot
of
that's
very
idiosyncratic
for
how
their
organization
works,
but
that
is
kind
of
there's.
There's
two
sides
of
that
bitcoin
for
who
finds
it
easier
to
get
started
with
kubernetes.
A
Our
team
start
to
kind
of
crystallize
is
like
what
could
we
invest
in
to
make
this
easier,
and
I
think
that
there's
a
debate
going
on
too
about
do
developers
need
to
care
that
they're
running
on
kubernetes
right
like
where
does
that
line
have
to
live
for
the
infrastructure
team
to
be
able
to
use
it
incredibly
impactfully,
but
the
devs
to
just
be
like
here's,
a
docker
container,
I'm
moving
on
with
my
day,
you
know
so
yeah.
What
do
people
love
about
kubernetes
gabby?
What
have
you
found.
B
Yeah
I
mean
I
would
kind
of
like
go
back
to
like
the.
I
think,
what
we
hear
again
and
again
and
again
is
people
saying
that
they
love
the
api,
like
they
see
the
api
and
they
see
these
abstractions
like
infrastructure,
abstractions
and
they're,
just
kind
of
amazed
that
they
wrote
this
themselves
before
and
that
now
it's
like
you
know,
I
don't
ever
have
to
write
this
or
even
maintain
this
again,
unless
you
want
to
contribute
to
like
the
open
source
project.
B
C
C
The
idea
is,
to
you
know
patch,
more
security
vulnerabilities,
but
there's
a
lot
of
little
things
that
can
kind
of
break
along
the
way
and
to
keep
your
eyes
peeled,
for
you
know,
changes
to
the
api
or
anything
like
that,
and
you
just
people
are
never
quite
sure
how
it's
gonna
interact
with
everything
they've
built
on
top
of
it.
So
it's
still
kind
of
a
careful
careful
process
for
people
and
they
are
very
strategic
and
when
they
choose
to
do
it,
some
people
are
faster.
C
B
C
B
Because
I
mean
then
environment
is
also
a
thing
like
if
you're,
if
you
have
something-
that's,
maybe
like
latency
sensitive,
so
you
might
be
doing
something
on
prem
versus
something
like
in
like
the
nearest
like
cloud
region.
So
I
don't
know.
I
think
it's
also
like
upgrading
your
own
version
of
kubernetes
has
its
own
like
hoops
and
hurdles
to
run
through,
as
opposed
to
upgrading
something
that's
like
managed.
A
C
D
C
C
So
it's
kind
of
like
get
out
of
the
way
as
much
as
possible
for
these
developers,
and
you
know
so,
I
think
that's
kind
of
an
interesting
dichotomy
because
we're
mostly
talking
infrastructure
people
but
at
the
very
end,
it's
kind
of
in
service
to
these
developers
and
the
like
business
critical
applications
that
are
are
running.
On
top
of
the
platform.
A
Yeah,
absolutely
so,
how
do
we
optimize
an
experience
for
a
tool
set
that
on
a
user
base
that
basically
doesn't
want
to
know
that
it
exists
right
like
it's
like
yeah,
exactly
kind
of
fascinating
cool?
Does
anyone
have
any
last
thoughts
you'd
like
to
put
on
the
board?
No
cool,
okay?
Well,
thank
you,
everybody!
So
much
for
participating
in
this
panel
and
we'd
like
to
just
really
welcome
the
community
to
join
sig
usability.
We
will
be
working
continuing
to
do
these
jobs
to
be
done.
A
Studies
with
a
future
goal
of
being
able
to
wrap
this
up
with
enough
data
for
us
to
make
some
really
nice
conclusions
and
then
share
that
anonymized
data
that
we're
going
to
go
through
a
really
strong
sort
of
sanitation
process
on
before
we
serve
it
back
up
to
everybody.
So
you
can
do
your
own
reporting
and
learn
from
it
as
well.
So
thanks
and
we'll
be
chatting
with
you
soon,.