►
Description
Check out information on this program and other mentorship programs here: http://git.k8s.io/community/mentoring/meet-our-contributors.md
A
All
right
welcome
to
our
second
edition
today
of
meet
our
contributors
for
another
time
zone.
Today
we
are
joined
by
four
awesome
contributors-
five,
including
myself,
and
we
are
taking
questions
from
the
meet
our
contributor
slack
channel
on
the
kubernetes
instance
as
well
as
twitter,
with
the
hashtag
of
Kate's
MOC,
we'll
do
some
quick
introductions
and
then
we'll
get
right
into
the
questions
for
folks
following
along.
A
These
can
be
general
questions
about
the
contributors
themselves,
how
they
got
into
open
source
general
contribution
questions
to
kubernetes,
as
well
as
specific
questions
about
the
process
itself,
for
instance,
Edie,
testing,
etc.
So
we'll
start
with
introductions
Solly.
Why
don't
you
start?
First,
alright,.
B
D
Hi
I'm
Jeff
Grafton,
github,
username
and
slack
XD.
I've
been
working
on
companies
for
probably
about
3
years
or
so
as
well.
I
think
and
lately
I've
been
working
on
building
test
infrastructures.
So
a
lot
of
the
stuff
going
on
and
tested
in
front
and
the
testing
for
repository
also
work
on
Basel
stuff.
I
know.
If
I
mentioned
they
work
at
Google,
so
I'm
working
with
the
Google
engineering
productivity
team.
For
all
these
improvements
as
well-
oh
yeah,
I.
A
All
right
for
real
question
all
right,
so
the
first
question
was
directed
towards
Chris,
but
I'd
also
like
to
hear
some
responses
from
the
rest
of
the
crew,
but
Justin
in
the
flat
chat.
I
would
like
to
know
how
did
you
get
from
where
you
are
in
tact
before
being
a
contributor
kubernetes
and
it
looks
like
they
are
inspired
by
a
lot
of
awesome
folks
who
are
building
great
open
source
tech,
but
keep
the
persons
coming
from
a
very
non
open
source
industry.
So
it's
hard
to
know
where
they
start
so
Chris?
C
Okay,
so
I
started
off
like
pulling
wire
in
a
datacenter
like
in
the
long
long
ago,
and
that
turned
into
bash
scripts
and
that
turned
into
Python
and
then
that
turned
into
Scala,
and
then
it
turned
into
Scala
sre
work,
which
made
me
DevOps
and
throughout
this
whole
journey
I.
Like
always
envied
people,
an
open
source
like
my
github,
had
like
one
follower
and
I
never
had
any
commits
like
I
would
have
like
one
green
square
and
I
would
like
always.
C
They
dreamed
about
being
like
more
involved
in
open
source
and
so
I
just
started
writing
tools
just
like
randomly
just
stuff
around
my
life
and
eventually
that
landed
me
a
job
where
they
were
like
you're
gonna
go
work,
open-source
a
lot,
and
it
was
really
scary
at
first,
because
I
thought
I
was
cheating
all
the
time
at
work.
I
was
like
what
a
Miss
is
like
open
source.
C
C
I
think
it's
a
little
bit
of
like
you
got
to
kind
of
take
a
risk.
Like
you,
gotta
take
the
jump.
You
just
got
to
kind
of
go
for
it
and
know
that
people
are
gonna.
Look
at
your
code,
that's
like
the
point,
and
if,
if
you
can
find
somebody
on
the
inside
to
like
help,
you
navigate
the
waters
at
first.
That
will
probably
help
a
lot.
C
There's
been
a
couple
of
people
who
I've
kind
of
like
given
a
little
bit
of
guidance
to
and
like
for
a
couple
of
weeks
and
like
now,
they're
contributing
to
kubernetes
full-time.
Just
you
know
helping
get
them
over
that
first
little
bump,
so
I
can
volunteer
Ian
if
I
can
help
anyone,
yeah
I,
would
say,
find
somebody
on
the
inside.
If
you
officially
have
100
new
emails
and
your
email
pad
I
haven't
yes
problem.
I
always
do
that.
People
like
pick
me
up
and
then
I'm
like
I,
would
swish
there's
more
hours
in
the
day.
A
D
A
D
A
D
The
various
infrastructure
that
developers
need
to
sort
of
be
productive
and
kind
of
get
things
out
of
their
way,
so
they
can
write
code,
that's
hopefully
bug
free
or
at
least
fewer
bugs
and
works
well
as
performant
all
these
sorts
of
things,
and
so
basically
cover
days
when
it
was
still
sort
of
a
younger
project
three
years
ago,
or
so,
there
was
not
really
anyone
from
Testim
or
anything
really
was
kind
of
focusing
on
testing.
There
were
a
few
squeeze
on
the
from
Google
that
were
kind
of
starting.
A
D
Into
running
some
tests
and
things
like
that,
but
there
wasn't
really
a
lot
kind
of
there,
and
so
they
were
starting.
They
were
starting
the
stuff
of
a
team,
so
it
was
kind
of
something
new
and
exciting.
I
was
looking
for
like
new
and
I
hadn't
really
done
a
whole
lot
of
open-source.
Before
you
know,
I
consumed
a
lot
of
one
source,
hadn't
really
contributed,
so
that
was
really
exciting.
D
Know
I
was
doing
necessarily,
so
we
really
need
to
kind
of
get
a
chance
to
actually
work
in
the
open-source
community
and
it's
been
it's
been
a
lot
of
fun,
getting
to
kind
of
work
with
people
across
all
sorts,
different
regions
and
companies
and
cultures
and
backgrounds,
and
it's
been
a
lot
of
fun,
just
kind
of
getting
a
very
different
perspective
from
other
places
and
I
think
the
communities
community
has
been
very
good
at
being
supportive
of
all
of
those
everyone
contributing
I.
Think
it's
been
a
very
healthy
community,
which
is
great.
A
B
B
You
know
cool
pieces
of
software
because
kids
don't
have
access
to
$2,000
budgets
to
buy
a
more
expensive
software,
and
so
I
was
kind
of
familiar
with
open
source
a
bit
and
started
doing
it
more
in
college
and
then
got
hired
at
Red
Hat
out
of
an
internship
College
and
that's
when
I
really
started
I
think
like
just
embracing
open
source.
The
whole
heartedly
and
I
worked
on
OpenStack
a
bit
before
before
coming
to
work
on
kubernetes.
B
But
you
know,
I
was
looking
for
a
little
bit
of
a
change
of
pace
and
one
of
my
co-workers
was
like.
Oh
there's
this
really
cool
project.
You
should
you
know
you
should,
if
you're
interested
in
working
on
something
new,
you
can
work
on
it
and
time
for
the
Nettie's.
It
was
like
this
is
awesome
and
that's
where
I've
been
ever
since
so.
E
Towards
you
and
how
your
story
sure
so
I
was
getting
out
of
the
army,
it
didn't
really
know
what
to
do
with
the
rest
of
my
life.
So
I
ended
up
at
like
a
traditional
IT
place.
It
was
like
a
defense
contractor
doing
like
how
it
looks,
support
and
I
one
day.
I
realized
I'm
gonna,
do
the
source
of
my
life,
a
final
figure
on
computers
and
at
the
time
Linux
was
kind
of
a
new
thing.
E
E
Eventually,
I
knew
enough
to
like
snag
a
sysadmin
job
at
a
university
and
once
I
got
exposed
to
students
that
need
a
bunch
of
stuff
we're
able
to
do
a
lot
of
experimentation
and
then
one
thing
led
to
another.
I
worked
at
a
district
for
a
while
and
then
ended
up
here.
The
thing
I
wanted
to
tell
everyone
who's.
Listening
to
all
this
I
remember,
I
was
getting
out
and
back
then
Mozilla
was
kind
of
like
the
one
open
source
project
that
people
kind
of
understood,
because
the
kernel
was
still
like
those.
E
This
weird
thing
that
came
out
floppies,
you
didn't
understand
and
I.
Remember
just
randomly
mailing
people
there
saying
hey.
You
know,
here's
my
resume.
How
do
I
get
into
this
I
remember
just
showing
up
at
a
built
at
a
sub
building
in
California,
with,
like
my
resume,
be
like
I
want
to
UNIX,
but
I
didn't
know
what
to
do
like.
So
one
thing
I
would
encourage
people
that
are
listening
to
this
is
like
those
days
are
kind
of
gone,
and
these
days
having
this
experience
is
actually
really
really
high
in
demand
so
like.
E
A
A
B
There
you
go
so
I
have
there
were
some
questionable,
API
decisions
that
were
made
over
the
course
some
things
where
we
didn't.
We
didn't
end
up
understanding.
We
didn't
foresee
how
API
aggregation
would
work,
and
you
know
how
how
much
we
would
be
focused
on
extending
things,
I
think-
and
there
were
some
just
some
little
things
over
the
course
of
time
that
have
just
become
a
pain
in
the
butt
I.
B
Actually
I
have
to
say,
like
I,
really
like
a
lot
of
good
minetti's
architecture
and
I.
Think
it
does
a
lot
of
things
right.
I
might
also
make
more
use
of
self
links.
I
think
self
links
are
are
kind
of
cool
concepts
that
could
be
used
to
make
things
easier
to
interact
with
the
API
in
certain
cases
that
we
we
haven't.
A
D
A
D
Hard
debug
and
all
sorts
of
things
where
there
are
going
to
be
certain
classes
of
tests
that
actually
interact
with
providers
that
are
going
to
require
real
clusters,
but
I
think
there's
a
lot
of
tests
where
we
wrote
the
A
to
B
framework.
It
was
easy
to
write
tests
in
that
they're
kind
of
functional
tests
that
are
just
doing
sort
of
testing
very
small
parts
of
the
system,
and
you
know,
would
probably
be
better
for
integration
test
or
something
that
runs
on
a
local
machine.
D
A
A
D
All
admit,
I
haven't
actually
really
worked
on
the
e2b
tests
in
a
while,
so
I,
you
know,
I
help
get
some
of
them
going,
but
I
haven't
really
done
a
whole
lot
of
that
and
I
haven't
involved,
didn't
open
too
often.
Actually,
writing
the
tests,
so
I
don't
have
the
best
advice,
but
I
mean
I.
Think
it's
kind
of
the
question
I
mean
it's
sort
of.
D
If
it's
something
that
really
require
that
you
know
depends
on
actual
implementation,
details
of
the
providers
or
you
know
you
like,
if
you
actually
need
to
like
test
the
network
or
actually
need
to
test
disk
functions
or
volumes
or
things
like
that.
Those
are
probably
examples
where
you
actually
require
you
to
retest,
whereas
if
it's
kind
of
a
functional
aspect
of
the
cluster
itself,
like
scheduling
or
something
like
that,
then
maybe
didn't
media
to
you
know.
D
Maybe
it's
not
something
that
you
need
to
stand
up
an
entire
cluster
to
make
sure
that
your
pods
get
rescheduled
properly
or
something
like
that.
So
the
more
that
you
can
kind
of
again.
You
know
we
I,
don't
think
there's
been
a
great.
You
know
the
frameworks
for
writing
integration
test.
Is
it's
not
as
not
as
well
developed?
I
know.
People
are
working
on
this
and
I'm
not
fully
up-to-date
with
all
the
details,
but
that's
kind
of
where
the
breakup
happens.
D
I
think
there's
also
efforts
to
be
able
to
run
the
e2b
tests
more
as
integration
tests
on
your
local
machine,
so
I
know.
Dimon's
and
similar
people
are
working
on
some
stuff,
Tim's
and
I.
Think
Clinton
and
know
people
are
working
on
kind
of
different
approaches
and
I
know
there's
some
other
existing
ones
on
running
local
clusters
and
so
that
I
think
helps
writing
being
able
to
run
some
UV
tests
and
write
then
test
them
yourself
without
having
to
necessarily
pay
Google
or
Amazon
or
Microsoft
or
whoever
to
actually
create
a
cluster.
A
Tim's
and
Aaron
worm
the
session
earlier
and
most
of
the
questions
that
we
received
for
actually
testing
related
and
they
did
for
those
that
are
watching
right
now
and
want
more
info
on
testing
I'd,
say
the
first
20
minutes,
we're
mostly
testing
related
and
didn't
share
the
screen
with
a
bunch
of
dashboards
and
cool
tools
that
you
can
use
so
definitely
check
that
out.
Alright
Chris
said
was
that
good
for
Sully?
Did
you
have
something
bad
I.
B
Was
just
gonna
say,
as
a
general
testing
comment
like
if
you
find
your,
if
you
ever
find
yourself
saying,
I
can't
test
this
as
a
law,
it
has
to
be
a
block.
That's
probably
a
good
indication
that
you
need
to
rethink
how
you've
actually
written
your
code.
So
if
you're
like
oh
well,
I
can't
I
can't
write
this
as
a
unit
test.
I
need
to
write
it
as
an
indent
test,
like
maybe
go
back
and
think
is
there
something
I
can
break
up?
C
Grace
just
a
comment
since
we're
talking
about
testing
and
I'm
gonna
do
a
shameless
hefty
Oh
plug,
really
quick,
but
we
have
Sunnah
boy,
which
is
conformance
testing,
which
is
the
layer
above
testing
the
kubernetes
components,
but
that's
modular
as
well.
So
as
soon
as
you
are
in
a
situation
where
you
want
to
validate
like
do
a
sanity
check
on
your
actual
cluster,
there's
a
lot
of
work
going
on
with
conformance,
which
is
the
layer
above
as
well.
A
C
So
right
now,
my
least
favorite
mountain
is
probably
also
my
most
favorite
mountain,
which
is
right
over
there
I'm,
actually
looking
at
it
right
now.
It's
not
Rainier
and
the
reason
I
kinda
am
really
pissed
off
at
that
mountain
right
now
is
because
I've
tried
to
climb
it
twice
and
failed
both
times
so
I'm
like
on
this,
like
I'm
gonna,
go
get
it
can't,
but
it's
like
I
know.
I
can't
swear
on
this
call
because
we're
streaming
right
now,
but
I
would
be
using
swear
words
if
possible,
to
describe
how
I
feel
about
this.
A
Yeah
only
when
we
allow
for
so
much
silly
yeah
good
all
right.
The
next
question
is:
are
there
any
best
practices
when
asking
questions
as
a
contributor
and
getting
feedback?
You
know
like
I
feel
like
this
might
also
go
into
what
chris
said
earlier
about
finding
someone
like:
what's
the
best
way
of
just
getting
the
detention
that
you
need,
you
know
whether
it's
on
a
PR,
whether
it's
just
general
questions
from
either
a
contributor
or
a
group
of
contributors,
whoever.
C
Wants
to
go
just
jump.
I
feel
like
this
is
like
such
a
great
question
for
so
many
reasons,
because
one
every
person
who's
requesting
help
is
different
and
every
person
they
would
potentially
be
requesting
help
from
is
different,
so
I
think
there's
a
little
bit
of
an
exercise
of
understanding
the
inputs
and
outputs
of
both
yourself
and
the
people.
You're
working
with
and
I
think
like
you're
gonna,
see
just
be
ready.
You
know
like
be
prepared
to
see
everything
from
I
want
to
do
things
like
buy
the
second.
C
It
run
time
in
slack
and
that's
how
we
work
or
like
we're
very
concurrent
team
here
and
everything
needs
to
be
documented
and
github,
so
that
we
can
all
read
things
and
contribute
concurrently
because
of
different
time
zones.
So
I
think
for
me,
it
was
like
learning
the
scale
of
it
either
is
like
super
super
quick
right
now
or
it's
like
takes
like
a
couple
of
days,
and
you
just
have
to
like
document
everything
you
think
and
just
knowing
that
every
contribution
is
going
to
be
somewhere
in
that
scale.
B
I'd
say
don't
like:
if
you're
not
getting
traction
on
github
issue,
don't
be
afraid
to
like
bug.
People
in
the
appropriate
slack
channels
see
if
you
can
figure
out
like
what
the
appropriate
slot
channel
is.
If
you
can
find
a
person
that
you
think
might
be
relevant
and
like
don't
be
afraid
to
bug
that
person
just
like
the
worst,
the
worst
that's
gonna
happen
is
they're
gonna,
be
like
well
I'm,
not
responsible
for
that,
but
you
should
probably
go
ask
this
other
person.
B
You
know
so
like,
if,
if
you
have
a,
if
you
think,
you're
getting
ignored,
you're,
probably
not
getting
ignored
intentionally,
it's
probably
just
like
there's
a
lot
of
there's
a
lot
of
bugs
there's
a
lot
of
issues,
there's
a
lot
of
PRS
and
it's
hard
to
keep
track
of
them
all.
And
you
know
so.
It's
like
personally
I
guess
aguado
is
killing
me
sometimes,
and
it's
soft
on
github
and
people
ping
me
and
we
all
usually
try
to
be
quick
to
respond
to
those
five
I
would.
C
Really
want
it
that
goes,
don't
be
afraid
to
bother
people
since
I'm
in
here,
like
I've.
Had
a
few
people
pay
me
for
something
and
it
like
it
comes
through
at
like
4:00
in
the
morning.
My
time
and
I
completely
forget
about
it
and
then
I
find
out
later
that
they,
like
felt
you
know
they
were
abandoned
or
their
their
contribution
wasn't.
Welcome
and
really
it's
like.
Please
continue
to
ping
us
continue
to
message
us
we're
not
ignoring
you,
we're
busy
and
like
we're
in
meetings
and
doing
calls
like
this.
B
D
I
think
I
think
both
what
Sally
and
Chris
were
saying
is.
You
know
very
much.
The
I
think
accurate.
You
know
a
lot
of
us,
you
know
we
are
drowning,
an
email
there's
constantly
things
going
on
constantly
issues
and
PRS
and
other
things,
and
so
often,
if
there's
something
urgent
or
like
you
think,
you're
getting
forgotten.
You
know
I
ping
in
slack.
If
you
know
somebody's
actually
sign
is
reviewer
is
totally
reasonable.
I
know,
you
know.
D
One
of
the
questions
I
feel
like
is
also
how
do
I
even
necessarily
know
like
if
you
just
create
an
issue
or
a
PR,
it
may
or
may
not
actually
get
a
sign
into
somebody
or
the
right
person
or
automation
tries
to
like.
If
you
create
a
peer
review,
it
tries
to
assign
to
somebody
that
thing's
owns
that
code
and
hopefully
they
look
at
it
and
reassign
and
so
forth.
Sometimes
that
doesn't
work,
so
you
may
need
to
ping
them
in
some
cases.
D
Those
are
good
ways
to
do
it
I've
also
in
some
cases,
done
a
lot
of
get
archaeology
kind
of
try
to
figure
out
okay,
who,
if
I'm
like
trying
to
modify
some
farther
understand,
why
something
was
chosen
if
you're
lucky,
somebody
actually
documented
this
and
there
was
assigned
ocular
or
something
like
that.
If
you're.
D
Was
maybe
discussed
in
the
PR
at
some
point,
so
you
can
kind
of
try
to
go,
find
the
original
PR
where
something
was
added,
and
you
can
sometimes
find
some
discussion
there.
That's
one
of
the
advantages,
I.
Think
of
a
lot
of
the
code
review
process
is
that
you
know
people
will
often
kind
of
discuss
like
oh.
We
did
this
way
because
something
something
something
it's
not
always
documented,
necessarily
why
that's
happening,
which
is
unfortunate,
but
that's
kind
of
one
way
I've
been
able
to
track
down.
You
know:
why
is
this
done
this
way?
D
B
B
This
is
kind
of
like
something
that
develops
over
time
as
you
work
in
the
communities
project,
but
like
have
a
good
mental
model
of
like
just
like
a
couple
people
from
each
area
that
you
can
ask
about
questions
like
you
know,
if
you're,
if
you're
like
I,
have
absolutely
no
idea
where
to
start
you
know
get
flame
is
not
being
helpful
or
it's
more
of
an
abstract
thing.
Like
you
know,
just
try
to
you
know,
keep
in
mind
like
okay,
who
answered
my
questions
in
the
past,
and
you
know,
because
they
might.
D
D
React
reiterate:
what
toy
was
mentioning
like
those
of
us
who
have
been
on
the
project
for
three
years
probably
know
a
lot
of
people
who
work
on
the
project
or
at
least
kind
of
big
ideas.
So
if
somebody
were
to
ask
me
like
hey,
I,
have
this
problem,
something
I
probably
don't
know
how
to.
Actually
you
know
how
that
part
of
the
system
works
but
I
probably
know
a
few
people
who
work
on
that
and
I
can
I'm
happy
to
sort
of
bouncing
in
that
direction.
I
think
a
lot
of
contributors
are
like
that.
C
Also
I
just
want
to
+1
documentation
like
if,
if
you
want
to
help
out
and
help
write,
Docs
or
fix,
spelling
errors,
or
even
if
just
a
sentence
seems
like
it's
worded
funny
like
that
is
a
great
way
to
get
involved
meet
the
people.
You
need
to
meet
start
working
with
them,
understand
the
process
and
we
desperately
desperately
need
all
the
documentation
help
you
can,
plus
one
from
Paris
plus
ten
from
Chris,
Nova
and
George.
You
had
something
to
add
to
oh.
E
It's
what
I
do
have
one
thing
to
add
just
to
those
are
submitting
pull
requests
a
lot
of
things
that
you
think
would
work
on.
Other
projects
won't
work
in
kubernetes,
so
kubernetes.
Currently
right
now
is
a
thousand
sixty-seven,
open,
pull
requests,
so
things
like
github
notifications
and,
oh
that
person
should
have
gotten
an
email.
When
I
responded,
you
know
with
with
their
review
and
stuff
like
that,
generally
speaking,
that
just
doesn't
work
you
almost
kind
of
have
to
actively
ping
the
person.
B
Basically,
and
the
first
hour
at
least
of
Lake
I'll
sit
down,
I'll
have
my
morning
stand-up
or
whatever,
and
then
I'll
spend
an
hour,
sometimes
more.
Just
like
checking
my
github
notifications
on
the
interface
and
like
going
through
and
doing
a
quick
like
you
do,
I
need
to
pay
attention
to
this
or
not,
and
then
I'll
go
through
and
do
a
second
pass
of
like
actually
actively
interacting
with
it,
and
that
workflow
is
a
little
bit
time-consuming
but
yeah.
The
the
email
notifications,
just
like
I
could
not
do
that.
I.
D
D
Results
have
come
in
or
comments
and
we're
certainly
working
on
trying
to
improve
this,
make
this
more
useful,
but
it's
at
least
one
way
to
kind
of
try
to
help
triage.
You
know
you
know
when
I
like,
for
example,
as
a
reviewer
as
a
maintainer
and
Michael
review,
a
bunch
of
cars
and
I'll
send
off
comments
and
then
I
need
to
know
when
I
actually
need
to
look
them
again.
When
somebody
has
come
back
and
applied
or
fixed
things,
and
so
it
tries
to
solve
help
with
that
problem.
Do.
B
E
A
D
Gonna
say
I'll
pass
along
that
feedback
about
having
Lincoln
Pro
I
know.
There
also
is
some
more
changes
coming
in
prowl
for
a
user
dashboard
there,
which
will
show
your
like
for
your
PRS,
what
the
test
status
everything
is,
and
it
might
someone
also
integrate
with
you
but
I
think
there's
possibly
some
women
can
prove
that
so
I'll
be
sure
to
pass
that
feedback
along.
So.
B
So
related
to
prowl
quick
comment,
pro
tip.
If
you
are
new
to
kubernetes
and
are
confused
by
the
bajillion
difference,
flash
commands
that
we
use
there
is
now
a
handy-dandy
slash
command,
cheats
he
built
into
Prowse.
If
you
go
to
prowl,
hates
that
IO
click
on
the
hamburger
menu
and
click
on
the
the
commands.
That
will
explain
to
you
like
what
they
all
do
and
like
what
the
arguments
for
are
them
and
like
who
who
is
allowed
to
do
them,
and
so,
if
you're
like,
what
does
the
status
command?
B
D
A
D
Application
that
schedules
all
sorts
of
various
test
jobs
and
has
various
things
to
report
back
to
github
and
interact
with
github,
so
that
you
know
it
both
reports
back
your
test,
statuses,
but
also
handles
all
the
labels
and
other
things,
there's
also
a
new
part
of
power
called
tied
which
actually
handles
our
merged
automation.
So
if
you
are
human
communities,
you'll
see
the
main
companies
requester
would
still
have
an
older
system
called
munge
github
or
the
submit
queue,
but
in
behemoth
all
the
other
repositories.
D
There's
like
basically
automation
such
that
contributors
never
actually
manually
merge
any
PRS.
We
basically
acquire
all
PRS
to
be
tested
and
approved
and
LG
before
they
merge,
and
then
there
is
a
system
which
will
ensure
that
everything
still
passes
test
before
it
merged.
So
you
don't
have
two
things:
they
could
click
the
break
tests
and
break
the
queue.
There's
a.
A
Awesome,
alright
next
question
I
have
to
scroll
up
here.
Alright,
when
you
were
learning
kubernetes,
how
did
you
go
about
learning
the
api's
and
the
design
in
the
design
decisions
that
went
into
them?
I.
B
You
know
like
how
the
rest
mapper
works
and
just
like
spend
time
going
through
and
being
like.
Alright
I,
don't
understand
how
this
works.
Let
me
see
if
I
can
add
some
debugging
statements
and
strategic
use
of
panics
and
maybe
Dell
and
and
see
if
you
can,
like
you
know,
just
gradually
like
expand
what
your
knowledge
is
of
a
particular
area,
and
you
know
I
find
it
slows
me
down.
B
Sometimes
right,
but
like
I
end
up
having
like
a
much
better
knowledge
of
like
some
like
little
nitty
gritty
bit
of
kubernetes,
which
comes
in
useful
in
Hindi
the
next
time
that,
like
you
know,
I,
have
an
issue
that
you,
like.
Oh
I
think
I
remembered
seeing
that
while
I
was
trying
to
figure
out
how
exactly
discovery
information
gets
turned
into
gets,
turned
in
for
recommendations
for
converting
resources
into
kinds.
C
Anyone
add
it
up:
yeah
I
can
tell
my
story
of
how
I
started
doing
started.
Learning
the
api's
I
also
enjoy
kind
of
like
going
this
slow
and
dig
through
the
code
route
with
bigger
projects.
So
my
first
like
big
learning
experience
I
went
through
in
kubernetes,
was
I
thought
it
would
be
really
simple
to
add.
A
field
to
I
think
it
was
I
was
working
on
deployments
at
the
time
it
was
like.
Oh
I'm,
just
gonna,
add
a
field
and
then
try
to
like
read.
C
Let's
see
this
in
the
cluster
real
time
and
that
exercise
should
demonstrate
everything
I
needed
to
learn
like
six
months
later,
I'm
still
working
on
that
and
I
mean
not
really
six
months
didn't
see
how
long,
but
it
was
a
good
learning
exercise
and
taught
me
like
how
the
api's
work
all
the
different
components
of
the
control
plane
and
eventually,
ultimately
was
able
to
do
like
a
an
edit
on
a
deployment
and
see
my
new
field
that
I
had
added,
and
that
was
how
I
started
learning
about
these
things.
I
don't
know
if
that.
D
A
D
To
reiterate,
I
came
over,
who
was
it
said
this,
but
you
know
allocating
time
to
learning
is
totally
something
you
should
do.
You
know
everyone
has
kind
of
I
take
time
to
learn
that
you
know
gonna
just
like
immediately
know
everything
it's
going
to
take
time.
I
think
is,
of
course
you're
saying
and
that's
okay.
D
C
I
want
to
pull
on
that
and
then
just
share
like
my
first
year
of
contributing
and
helping
to
maintain
various
parts
of
kubernetes.
I
never
went
above
the
API,
like
literally
my
whole
workflow
was
just
infrastructure
and
and
cube
admin
and
getting
everything
up
and
running,
and
then
it
was
like.
Oh
this
magical,
API
I
know
nothing
about
is
up.
You
guys
go,
do
all
your
fancy.
Application,
land,
stuff
and
I
was
still
like.
It's
super
valid
member
of
the
community,
so
plus
one
of
that
and.
B
Don't
be
like
you
know,
also
don't
be
afraid
to
learn
a
new
part
and
like
feel
like,
oh
I,
think
this
thing
is
fixing
I'm
gonna
figure
out
how
to
fix
it
and
post
a
PR
like
I.
My
path
through
kubernetes
has
bounced
around
so
many
places.
I
think
like
my
first
PR
was
about
DNS
and
then
you
know,
I've
had
PRS
for
like
some
API
machinery
and
Clank,
oh
and
and
API
creation
and
auto
scaling,
obviously
and
whatnot
like
don't
be
afraid
to
like
be
like
I.
B
Think
this
thing
is
broken
or
doesn't
quite
do
what
I
needed
to
you
know
and
and
try
to
figure
out
how
it
works
and
maybe
post
a
fix
or
ask
someone
like
hey.
You
know
was
this
intentional?
Do
you
mind
if
I
you
think
this
would
be
a
good
idea
for
me
to
post
a
fix,
I've,
definitely
seen
new
contributors.
Do
that
and
it's
really
awesome
because
I'll
be
like
ya
know
you
have
a
great
point.
B
C
You
mentioned
your
first
command,
I
start
thinking
about
mine
and
that
maybe
you
think
that
this
is
another
great
thing
that
people
who
are
interested
in
getting
making.
So
the
project
should
know
is
my
first
commit
to
kubernetes
was
putting
a
flog
and
two
years
later,
I'm
still
making
those
commits
about
two
flags
to
kubernetes,
so
adding
flags
and
like
even
if
it's
as
simple
as
looking
a
bit
and
not
in
if
statement
somewhere
further
downstream
in
the
program.
Those
are
really
great
ways
to
get
your
foot
in
the
door
as
well.
Jeff.
D
D
A
B
There's
definitely
like
a
bunch
of
different
editor
program,
plug-ins
for
doing
stuff
like
that
they're
not
identical
to
cscope,
but
I.
Think
actually,
some
of
the
go
like
go
has
a
series
of
like
ancillary
tools
that
are
designed
to
help
with
some
of
that
stuff
and
I.
Think
a
bunch
of
the
plugins
actually
pulled
from
some
of
those.
So
if
you're
using
them
a
lot
of
the
plugins
collected
and
then
go
do
that
kind
of
stuff
and
if
you're
not
using
them,
I
think
you
can.
B
C
Is
goal
and
usually-
and
that
has
like
a
declare-
declaration
lookup,
which
you
can
specify
to
either
go
to
your
local
copy
or
to
the
copy
that's
in
vendor
and
it's
in
a
different
package
and
then
I
also
use
Emacs
and
I
base.
My
Emacs
I
had
I
had
to
bring
it
up.
I'm
sorry
configuration
on
space
max
and
I
use
help
the
package
manager
and
that
how's
it
go
plug-in,
not
helm.
B
A
F
E
C
Pronunciation
I
started
out
saying
cube
cuddle
a
long
time
ago,
and
a
lot
of
people
gave
me
help
for
that.
So
I
decided
to
start
saying
cue,
Bechdel
to
troll
people
and
I've
been
saying
that
for
so
long
that
I
actually
use
it
now
like
in
the
wild
all
the
time,
and
it's
gotten
to
the
point
where
the
joke
is
kind
of
faded
off
into
the
distance
and
now
I
just
genuinely
say
key
back
to
all
the
time
and
it's
hilarious.
So.
B
I
say:
cube
control,
but
I
find
that
typing
cube
control
is
really
long,
and
so,
if
you
or
find
yourself
working
with
a
lot
of
kubernetes,
especially
if
you
like
testing
a
feature
pro
tip,
Elias
cube
control,
Kay
and
then,
if
you
find
yourself
working
with
the
playing
system,
components
add
another
Elias.
On
top
of
that,
that
Elias
is
KS,
Kay
and
huge
system,
and
so
on
and
so
forth,
and
those
speed
up
my
typing
a
lot.
A
A
Pronunciations,
alright
I
think
we
should
wrap
this
up.
Actually,
no
I
think
somebody
is
typing.
George's
right,
Georgia
just
got
a
plus-one
all
right
last
questions
for
each
of
you
anything
all
right.
Well,
this
is
a
wrap
for
today's
sessions
for
meet
our
contributors.
Thank
you
so
much
to
Solly,
Chris,
Jeff
George
on
the
ones
and
twos
on
YouTube
Luna,
who
is
not
in
the
background
anymore,
die
Luna
and
I
hope
that
we
can
have
you
all
on
another
episode
and
thanks
again
appreciate
your
time.
I
owe.