►
From YouTube: Keynote: Getting Started in the Kubernetes Community - Lucas Käldström & Nikhita Raghunath
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Keynote: Getting Started in the Kubernetes Community - Lucas Käldström, CNCF Ambassador, Independent & Nikhita Raghunath, Software Engineer, Loodse
Kubernetes is its community. Kubernetes is where it is today only because of the people behind it. The foundation of this thriving community lies on the Kubernetes Community Values. In this talk, we will take a look at what they are, why they are so important and how they shaped our growing ecosystem. By first focusing on the core values, we’ll give the audience an idea of *what* it means to be involved and *why* they should contribute. After that, we will talk about *how* they can get started with contributing, move up the contributor ladder and become a regular contributor who serves the project. Lastly, we’ll look at some stories about how the existing contributors got started with their journey.
https://sched.co/MRdg
A
B
A
B
A
One
example
of
this
is
diversity.
Scholarships,
in
fact,
both
Lucas
and
I
got
a
scholarship
for
a
first
coupon,
something
we
really
appreciate.
It
allowed
us
to
connect
with
the
community
on
the
next
level
and
contribute
back
cm.
Cf
has
been
world
leading
in
getting
voices
from
all
around
the
world
represented
during
their
events.
During
the
last
seven
coupons,
seven
hundred
and
seventy
thousand
dollars
has
been
spent
on
getting
three
hundred
and
nine
existing
and
new
community
members
to
join
us
here.
A
And
you're
at
cube
con.
There
are
also
many
dedicated
events
for
sharing
stories
and
getting
up
to
speed
in
the
community
through
mentoring.
There
is
the
diversity
lunch
where
anyone
can
join
for
discussions
and
pair
programming.
There's
also
the
networking
and
mentoring
session
where
mentees
are
paired
with
mentors
for
onboarding
discussions.
B
Really
successful
projects
like
kubernetes
require
different
perspectives
and
different
skill
sets,
and
these
voices
can
only
be
heard
in
a
welcoming
and
respectful
environment.
Hence
we
show
respect
for
the
time
and
effort
put
into
each
contribution
regardless
or
where
this
contributor
is
on
the
growth
path
and
community
leadership
is
earned
through
quality,
quantity
and
duration
of
contributions.
But
respect,
however,
is
belongs
to
everybody
all
the
companies
and
individuals
using
kubernetes.
B
A
In
other
words,
individuals
gain
reputation
through
the
work
that
benefits
everyone
and
companies
through
their
commitments
and
resources,
provided
we
have
two
examples
of
this,
so
something
we
see
over
and
over
again
in
this
community
is
contributors,
switching
companies
yet
continuing
to
work
on
kubernetes
just
as
before-
and
this
is
important
because
it
allows
for
individuals
to
grow
and
that
helps
the
project
succeed.
Long
term.
B
Companies
investing
heavily
in
making
the
open-source
code
rock-solid
are
rewarded
in
media
and
broader
ecosystem
for
their
commitment.
In
this
slide,
for
example,
we
see
how
examples
of
how
the
two
currently
highest
contributing
companies
to
kubernetes,
Google
and
Red
Hat
are
rewarded,
but
there's
also
the
other
project.
If
you
want
to
see
more
company
and
community
statistics
as
you
navigate
this
ecosystem
and
make
choices,
you
should
check
out
dev
stats,
the
CNCs
project,
dev
stats,
we're
also
trying
to
grow
the
next
generation
of
leadership
and
distribute
this
leadership
across
the
community.
A
One
example
of
growing
next
leadership
positions
is
by
shadowing
someone
on
the
release
team.
The
relief
team
is
responsible
for
making
sure
that
a
kubernetes
really
is
a
stable,
secure
and
functional,
and
by
shadowing
such
a
member,
you
can
get
to
follow
the
process
and
you
can
even
step
up
the
next
time
if
you
like.
A
We
also
like
to
avoid
the
behavior
that
we
want
to
see
in
the
community.
We
want
people
we're
willing
to
do
the
non-glamorous,
yet
that
very
important
work,
that's
needed
to
keep
our
project
healthy
or,
as
sorry
know,
what
we
call
it
chopping
word
and
carrying
water.
Examples
of
this
include
facilitating
meetings,
issue,
triage
refactoring
and
community
management.
B
B
So
now
we've
got
a
glimpse
into
what
it
means
to
be
in
the
convenience
community
and
the
values
that
tie
us
together.
But
why
really
should
you
contribute
contributing
to
Grannis
gives
you
personal
throats?
It
gives
you
friends,
it's
really
exciting,
but
also
it
can
be
a
bit
overwhelming.
That's,
okay,
and
in
this
talk
we
would
like
to
show
you
why
it
doesn't
have
to
be
through
both
of
our
own
personal
stories.
So.
A
B
Lucas
I
just
graduated
from
high
school
going
to
university.
This
fall
in
Finland
I'm
running
six
last
lifecycle
as
a
chair
and
I'm,
a
CNC
F
ambassador
doing
the
meetups
in
Finland
I'm
also
have
I.
Also
have
my
own
company
looks
as
labs,
which
performs
contracting
for
we
works
so
I
get
to
work
on
upstream
kubernetes.
B
The
gubrious
consists
of
multiple
groups
of
people
that
are
collaborating
together
with
a
specific
focus
area.
The
main
and
the
most
common
one
is
a
special
interest
group
or
cig.
For
short,
here's
a
map
of
the
different
community
groups
currently
I'm,
mostly
active
in
cyclist
lifecycle
and
work
group
component
standard,
whereas
Nikita
is
active
in
sig
contributor
experience
and
cjp
amateur
next,
let's
hear
Nikita's
inspirational
story
about
how
she
got
started
so.
A
I
graduated
from
college
last
year
and
when
I
was
in
college,
I
wanted
to
get
started
with
open
source.
I
was
somewhat
familiar
with
go
and
this
thing
called
kubernetes
and
I
saw
that
CN
CF
was
participating
in
this
internship
program
called
Google
Summer
of
Code
I
applied
got
selected
under
the
internship
program.
If
mentorship
like
this
sounds
exciting
to
you,
you
can
even
apply
next
year
or
participate
in
our
tree
tree.
A
So,
coming
back
to
my
story,
when
I
was
applying
to
the
internship
I
wanted
to
get
to
know
the
community
better,
so
I
went
to
the
community
repo
on
github
and
learned
more
about
the
six
that
I
wanted
to
work
with
sick
API
machinery.
You
can
find
all
details
about
how
the
community
is
structured
in
this
repo
I
got
the
six
contact
details
from
the
repo
and
joined
the
slack
Channel
and
introduced
myself
when
I
wanted
to
get
involved
by
the
way.
If
you're
not
already
on
the
kubernetes
lag,
you
can
join
63,000.
A
Others
adds
a
number
of
people
that
are
there
on
the
kubernetes
slack
right
now,
but
getting
an
invite
at
slack
that
cait's,
that
IO
and
in
our
community
we
love
using
emojis,
so
feel
free
to
unleash
that
in
her
emoji
power-
and
you
turn
slack
after
conversing
with
people
on
Sonic
I
was
intrigued
and
I
wanted
to
know
more
so
I
joined
their
meetings,
all
six
have
public
meetings
and
anyone
is
welcome
to
join.
There
are
also
public
meeting
notes
on
Google,
Docs
and
recordings
on
YouTube.
We
also
have
fun
in
these
meetings.
A
So
I
got
familiar
with
the
sig
and
I
submitted.
My
first
PR
I
had
a
lot
of
questions
while
getting
started,
but
everyone
was
super
friendly
and
answered
everything
in
a
really
friendly
way.
So
please,
please
don't
hesitate
to
ask
questions
at
all.
I
also
want
to
give
a
big
shout-out
to
dr.
Stefan
skinsky,
who
was
a
wonderful
mentor
and
helped
me
grow
a
lot.
A
Next
I
wanted
to
write
a
feature
for
kubernetes
for
C
IDs
in
kubernetes,
so
I
started
sketching
the
design
and
wrote
it
down
in
a
cap.
A
cap
is
kubernetes
enhancement
proposal.
The
cap
documented
the
motivation
and
implementation
plan
for
validation
of
custom
resources
after
contributing
code
for
some
more
time
I
applied
to
become
a
member
of
the
kubernetes
github
organization.
You
can
become
a
member
when
you're
an
active
contributor
and
are
sponsored
by
to
existing
members.
A
Then
I
started
reviewing
PRS
and
became
a
reviewer
being
a
reviewer
requires
that
do
you
have
reviewed
PRS
for
consistently
over
some
time,
and
you
know
the
area
pretty
well,
as
I
got
involved
in
the
community.
More
and
more
I
thought
to
myself:
hey
I
really
enjoy
working
with
this
community,
so
I
joined
the
contributor
experience
and
started
helping
with
improving
automation
to
make
contributors
lives
easier,
I
started
doing
other
things
like
issue
triage
and
like
triage
ring,
not
all
forms
of
contributing
have
to
be
about
code.
A
A
Then
I
was
about
to
graduate
from
college,
so
I
started
looking
for
jobs
and
being
a
part
of
this
community
opened
a
lot
of
doors
for
me
and
I
joined
Lutzer,
where
I
got
to
work
with
kubernetes
every
day
and
to
this
day,
I'm
still
contributing
and
over
time,
as
I
did
more
of
the
seemingly
unglamorous
tasks.
Like
writing.
Dogs
writing
tests.
Refactoring
issue,
triage
I
became
an
approver
and
doing
these
tasks
consistently
over
time
and
taking
responsibility.
A
A
particular
area
I
became
a
sub
project
owner
and
eventually
a
technical
lead
so
well.
This
was
my
story:
I
got
involved
in
the
community
in
2017
and
since
then,
I
have
learned
so
much
made
friends
from
all
around
the
world.
I've
been
exposed
to
countless
opportunity
is
something.
I
would
have
truly
never
imagined
Peter
but
I'm,
not
even
exaggerating
a
single
bit
here,
and
it
truly
truly
transformed
my
life
and
I'm
pretty
sure
it
change
Lucas's
life
too.
So,
let's
hear
his
amazing
story
about
how
he
got
started.
B
Thanks,
so
my
story
started
with
the
help
of
raspberries
in
May.
2015
I
wanted
to
run
kubernetes,
but
the
only
spare
hardware
I
had
was
stack
of
raspberry
PI's
at
home,
and
there
was
some
problems
in
doing
this,
though,
because
combination
didn't
work
on
arm
and
hardly
had
any
documentation
on
how
to
run
it
on
bare
metal
at
the
time
of
like
zero
point
something
releases,
but
I
think
this
is
a
challenge
and
after
some
time
I
actually
succeeded.
B
Porting
Grenada
storm
I
wanted
to
share
this
breakthrough
with
the
wider
community,
so
I
created
my
first
open-source
project
on
github
simply
called
kubernetes
and
arm.
This
was
a
huge
milestone
for
me,
because
this
was
the
first
time
somebody
else
could
like
see
the
code
I've
written
and
as
it
happened,
cos
Penniston
and
Martin
Jensen
used
my
project
in
the
master
thesis
called
cube
cloud
while
I
was
in
high
school,
but
it
was
really
fun.
This
is
great
great
teases,
however.
I
didn't
want
it
to
stop
there
and
have
this
as
a
standalone
project.
B
Instead,
I
wanted
kubernetes
to
work
on
multiple
platforms
by
default.
In
order
to
make
this
happen,
I
wrote
a
kept
saying,
where's
Nikita,
describing
how
it
should
be
done
to
achieve
this
and
I
started
coding.
After
this
implementation
plan
was
merged.
However,
my
first
PR
was
actually
rejected
so
well
through
this
process.
I
got
to
know
more
about
how
to
contribute
in
a
more
efficient
way.
This,
however,
the
one-line
change
you
see
over.
There
is
my
first
beer
that
got
merged
in
late
2015
and
I
mean
it's
literally.
B
A
one-line
change,
I
just
remove
a
hard
coding
for
the
interval
AMD's
architecture,
but
it
was
the
first
of
many
more
changes
to
come
and
in
the
same
way
after
contributing
for
a
while
I
applied
to
become
a
member
of
the
kubernetes
github
organization
and
then
a
reviewer
after
some
time.
In
this
multi
platform
area,.
B
B
The
later
this
month,
probably
in
the
same
way
as
Nikita
I
also
got
a
diversity
scholarship
to
cube
Khan,
so
I
could
meet
this
community.
That
I've
been
working
with
online
was
my
first
conference
ever
side
didn't
know
real
attack
what
to
expect,
but
I
really
liked
what
I
saw
and
I
set
my
mind
to
contributing
back
during
these
conferences.
So
one
of
the
two
CFDs
I
submitted
for
cube
Cumberland
two
years
ago
here
in
Europe,
was,
was
actually
accepted.
B
So
I
held
my
first
talk
ever
at
that
time
it
was
called
auto-scaling
multi-platform,
kubernetes
cluster
built
with
Q
Batum.
It
was
son
after
working
on
kubernetes,
besides
high
school
for
more
than
a
year.
Just
like
just
for
fun
is
my
hobby
project
I
started
getting
job
offers,
but
the
only
company
that
offered
something
that
was
suitable
to
my
situation
like
living
at
home
and
all
that
in
Finland
was
we
works.
B
Lastly,
we
have
the
notion
of
servant
leadership,
which
means
that
those
in
leadership
positions
serve
the
people
around
them
with
what's
required.
So
what's
one
of
the
most
important
things
with
leading
it's
making
others
succeed,
collaborating
with
people
and
following
them
on
the
growth
path
has
been
definitely
the
most
inspiring
experience
for
me
personally,
so
I
tend
to
say
that
I
came
for
the
tech,
but
I
stayed
for
the
people.