►
Description
Interested in working on Kubernetes development? Join us on the first Wednesday of every month! https://git.k8s.io/community/mentoring/meet-our-contributors.md
A
Welcome
to
the
afternoon,
in
the
Pacific
time
edition
of
meet
our
contributors
for
June,
sorry
for
everybody
that
joined,
we
were
having
some
live
stream
issues,
but
we
are
back
up
now.
If
you
do
have
any
other
audio
issues,
please
let
us
know
in
the
meet
our
contributor
slag
channel,
and
then
we
can
try
to
troubleshoot
that,
but
this
is
a
youtube
series
that
we
do
monthly
first
Wednesday's
of
a
month
for
mentors
on
demand.
It's
a
neat
concept.
Mentoring
takes
a
lot
of
time.
A
A
So,
if
you
are
asking
questions,
answering
questions,
etc,
please
be
kind
to
each
other.
As
far
as
asking
questions
again,
we
are
taking
questions
mainly
from
the
kubernetes
slack
channel.
If
you
do
not
have
the
slack
instance,
it
is
slack
8zo
k8s,
for
your
invite,
feel
free
to
ask
questions
there.
Also,
if
you
would
like
to
be
anonymous,
feel
free
to
direct
message
me
on
that
same
slack
team
my
handle
is
paris
PA,
our
is
like
the
city
and
then
also
feel
free
to
use
twitter.
A
I'm
gonna
be
perusing
twitter
as
well
for
the
hashtag
that
is
kate,
8's
MOC.
So
if
you
have
a
question
there,
alright
and
then,
let's
get
into
quick
introductions,
I
also
realize
I
didn't
introduce
myself
the
second
time
after
the
after
the
hiccup
there.
My
name
is
Paris
I
work
at
Google
I
do
kubernetes
community
management.
Now
we're
gonna
go
around
our
panel
and
do
some
quick
introductions
there
Eric
you're
first
on
my
screen.
Why
don't
you
go
first
for
the
second
time
again.
B
Everybody
and
happy,
if
you
can
now
hear
me:
I
am
Eric
I
work
at
Google
on
kubernetes
I'm
involved
in
the
sig
testing
community
and
do
which
you
know
does
a
lot
of
testing
work.
Well,
as
a
lot
of
the
you
know,
automation
for
different
repositories
and
yeah
excited
to
you
know,
answer
any
questions
and
see
if
I
can
help
out
thanks.
C
And
I
work
at
Samsung,
where
we
basically
come
up
with
open
source
and
kubernetes
focused
solutions
for
the
cloud
strategy
for
Samsung
and,
as
for
me
personally,
I
get
to
spend
a
lot
of
time
exploring
and
learning
and
contributing
in
several
different
areas
right
now,
I'm
how
being
talked
to
very
nicely
about
possibly
joining
the
112
release
team,
and
so
so
that's
going
to
be
really
exciting.
That's
kind
of
gonna
be
my
next
step,
not
my
next
big
thing
and
I
like
owls
yeah
I
was.
E
D
A
A
George
and
I
both
do
a
career,
Denny's
community
management
and
we're
both
very
active
in
the
contributor
experience
sake.
So
if
you
need
anything
from
mentorship
to
first-time
contributions
to
how
do
I
become
a
reviewer
contributor,
experience
can
help
you
with
those
things
or
hey,
I'm,
having
a
terrible
time
with
the
actual
github
workflow
process,
etc.
So,
let's
get
right
into
some
questions.
I
actually
have
a
very
similar
question
to
what
we
had
laughing
and
this
is
most
likely
going
to
be
targeting
Eric
and
it's
do.
We
have
to
run
end-to-end
tests
for
everything.
B
So,
like
something
I
mean
if
right
now,
we
do,
or
at
least
will
automatically
run.
You
know
into
end
tests
on
when
you
create
a
PR,
we'll
run
those
for
you,
so
I.
Don't
necessarily
think
that
you
know,
depending
on
the
scope
of
your
change,
you
may
that
may
be
a
good
idea,
but
I
realize
you
know
it's
going
to
be
harder
for
some
people
to
maybe
get
a
Indian
cluster
up
and
running
to
run
that
test.
B
B
Would
be
very
interested
in
getting
that
working
and
potentially
reducing
the
amount
of
testing
we
do
on
places
like
GCP
or
you
know,
other
cloud
providers,
because
that's
slow
and
expensive
I'd
really
like
to
give
contributors
a
way
to
like
run
the
same
indian
tests
that
the
pre
submits
will
run
on
their
local
machine,
but
yeah,
maybe
head
over
to
cig
testing.
If
you
know
been
the
elder,
is
involved
a
little
bit
in
that,
so
maybe
reach
out
to
sig
testing,
and
then,
if
that
is,
if
you're
interested
in
helping
out
with
that.
D
Yeah
another
interesting
addendum
to
kind
of
what
Eric
was
talking
about
with
perhaps
getting
a
docker
in
docker
environment
going
is
that
successor,
lifecycle
recently
adopted
the
Miranda
Scoob,
ADM,
docker
and
docker
repository,
and
we
did
so
largely
in
mind
with
improving
developer
experience
and
then
also
taking
some
ownership
of
that
repo
and
getting
it
to
a
point
where
it
would
be
suitable
for
running
and
to
end
tests
in
an
automated
we're
excited
about
that.
And
so
it's
a
very
new
development.
It's
a
really
cool
project.
D
A
An
awesome
intro
for
our
next
topic.
The
member,
wants
to
know
that
they've
currently
been
doing
some
PRS.
They
have
their
membership
and
they
participate
in
a
few
SIG's.
Are
there
any
SIG's
right
now
that
are
looking
for
folks
to
become
reviewers
or
even
escalate
to
approvers
in
any
way
or
any
projects
that
are
coming
up
that
are
really
hot?
That
need
new
contributors.
B
So
I
know
from
the
I
would
assume
that
you
know
most
places.
Reviewing
is
kind
of
you
know,
challenging
and
I
think
getting
you
know,
I
would
love
to
make
sure
that
all
of
our
PRS
are
reviewed
in
a
timely
fashion,
so
at
least
on
the
test
in
for
a
repo.
If
that
is
you
know,
I
think
reviews
are
always
looked
at
favorably.
B
So
if
you
want
to
drop
in-
and
you
know
start
reviewing,
I
would
just
you
know,
encourage
you
to
find
something
that
either
looks
interesting
or
looks
comprehensible
to
you
and
provide
a
review
on
that
their
commands.
If
you
look
on
the,
if
you
go
into
the
kubernetes
tests,
infra
I
think
there's
like
a
command
CMD
link
that
shows
like
different
commands,
like
you
could.
Potentially
you
know,
assign
yourself
to.
B
Let
people
know
that,
like
hey
I
plan,
to
review
this
or
hey
I
plan
to
work
on
this
issue,
I
think
you
know,
especially
if
you
know
no,
one
else
is
doing
it.
I
think
I
would
encourage
people
to
feel
empowered
to
make
those.
You
know
to
take
the
initiative
there
and
if
you
want
to
do
it
in
the
sig
testing
test,
infra
areas
super
great
and
awesome.
A.
C
Little
bit
in
my
experience
as
a
relative
newcomer
post,
six
will
very
much
appreciate
any
help
in
in
managing
their
task
list
so
like
what
Eric
said,
you're
always
free
to
review
on
anything
you
like
and
and
the
way
that
I
would
go
about.
That
is
in
one
of
the
areas
where
I
have
worked
really
hard
contributing
to
the
code
or
to
the
documentation.
Now
I
have
a
certain
kind
of
base
knowledge
now
I'm
ready
to
review
similar
pull
requests
because
I
already
have
some
background.
Knowledge
and
I.
C
Don't
have
to
be
an
official
reviewer
to
do
that
in
one
of
the
cases,
I
actually
found
myself
and
the
owners
file
one
a
day
and
I'm,
not
sure
who
did
that,
but
I
have
definitely
also
seen
pull
requests
that
literally
just
changed.
The
owners
file
with
the
hey
I
should
be
a
reviewer
on
this
and
I.
Don't
I,
don't
actually
know
what
happened
to
it.
It
wasn't
me,
but
it
is.
It
is
always
okay
to
just
you
know,
once
you've
contributed
for
a
while
to
say:
hey,
maybe
I
should
be
a
reviewer.
D
C
Another
thing
I
wanted
to
add
that
was
part
of
the
question.
It
said
what
are
kind
of
new
hot
topics
right
now,
so
hey
I,
think
good
strategies
are
to
show
up
at
a
cig
meeting
some
area
that
interests
you
and
literally
ask
that
question
there.
That's,
basically
what
what
I
did
and
I
got
actually
so
I'm,
currently
starting
work
on
a
project
called
it's
called
customize.
It
is
not
in
the
kubernetes
kubernetes
organization,
it's
in
kubernetes
SIG's,
but
it
is
clearly
kubernetes
related
and
the
older.
The
project
gets
the
more
and
more.
C
We
it's
repositories.
Will
you
find
related
repositories
and
projects?
I
mean
helm,
literally
just
split
off
and
became
their
own
thing,
and
this
would
not
stop
me
from
sending
people
over
to
helm
and
trying
to
contribute
right
just
as
an
example,
so
that
might
also
just
be
a
really
good
area
to
be
with
a
new
project
from
the
ground
up.
That
is
always
a
great
place
for
new
people
to
start
because
there
isn't
so
much
code
base
to
learn
and
follow
through.
A
Oh
I
was
muted
good
responses.
Y'all.
Thank
you
all
right.
Let's
queue
up
the
next
question
here
all
right,
so
this
individual
says
that
they
hear
the
word
core
a
lot
when
they're
referencing
kubernetes
core.
So
what
does
that
mean
exactly
and
then
what's
the
definition
of
kubernetes
ecosystem
and
how
do
they
differ?
Oh.
C
D
A
B
Think
that
sounds,
you
know
largely
accurate
and
yeah
I
mean
I,
don't
know,
I
mean
yeah.
You
know
something
like
helm.
I
think
would
be
part
of
the
ecosystem
as
opposed
to
core
kubernetes.
You
know,
I,
don't
know
like
the
I
I
assume,
probably
the
like
PR
workflow,
stuff
I,
don't
know
if
that
would
be
either.
D
That's
definitely
the
truth
in,
in
my
opinion,
there's
a
gradient
to
core.
So,
for
instance,
the
external
DNS
controller
is
component.
You
know
that
really
a
percentage
of
users
are
going
to
run.
It
is
a
kubernetes
project
that
is
not
part
of
defaults
deployment
of
upstream
kubernetes,
and
then
somebody,
you
know,
has
the
freedom
to
bundle
a
smaller
percentage
of
core
components
into
their
own
distribution
of
you
know,
kubernetes
that
only
does
service
endpoint
service
kubernetes.
That
only
does
compute
and
networking,
but
not
you
know,
like
load
balancer
and
cloud
provider
stuff.
D
The
break
out
of
cloud
provider
is
an
example
of
something
that's
traditionally
been
bundled
into
core,
but
is
no
longer
going
to
be,
but
it's
something
that's
there.
You
know
if
you're
going
to
use
kubernetes
by
defaulting,
like
google
clock
for
some
things.
Similarly
like.
If
you
talk
about
open
shift,
OpenShift
is
definitely
ecosystem
to
cooper
nineties
core,
but
there's
components
of
open
shift
that
are
definitely
core
open
shift.
So
yeah,
it's
a
so
yeah.
Really.
I
guess
what
you
have
to
ask
yourself
is
like
where's,
the
code
live
and
then
like?
B
Think
you
know
if
you,
if
anyone
is
interested
in
helping
you
know
us
better,
define
what
is
and
is
not
core,
there's
the
conformance
testing
effort
right,
which
might
be
good
to
contribute
to
where
we're
trying
to
build
up
the
you
know
set
of
Suites
to
where
someone
wants
to
say
they
have
a
conformant.
You
know
1.11
cluster,
whatever
they
run
these
tests
and
you
know
certainly
I,
think
that
is
sort
of
a
interesting
place
to
contribute
there.
A
D
Where
I
found
the
most
like
interesting
place
to
collaborate
with
people
is
in
smaller
projects.
I
have
a
repository
that
just
is
a
web
book
for
integrating
container
builder
with
you
know,
like
github
CI
status,
notifications
on
your
pull
requests
and
like
when
you
build
like
a
little
community
of
users
around
that
you
know
and
like
the
Google
Cloud
slack
Channel
and
like
your
you
get
like
other
people,
PRA
improvements,
and
that
kind
of
thing.
It's
just
like
this
little
thing
that
you
guys
like
to
use
same
thing.
B
I
would
say
you
know
on
the
open
source
side,
the
vast
majority
of
my
contributions
have
been.
You
know
various
parts
of
kubernetes
you
know
I,
do
think
it's
interesting
since
the
sort
of
the
diversity
of
when
you
go
to
a
different
organization,
they're
gonna,
have
a
different
dialect
of
like
you
know,
Oh,
something
that
they
really
want
here.
B
Maybe
they
don't
want
over
there
or
you
know
figuring
out
like
exactly
what
do
they
expect
for
a
pull
request,
or
what
are
my
expectations
so
I
think
that's
sort
of
an
interesting
part
about
you
know,
jumping
into
a
new
community,
is
trying
to
figure
out
how
to
inter,
engage
with
that
community
and
I.
Think
that
yeah
I
don't
know
and
but
yeah.
It's
definitely
very.
You
know.
I
I,
really
I
think
it's
fun.
How?
B
If
there
is
something
that
I
want
to
change
or
if
there's
something
I,
don't
understand
how
I
can
go
dive
into
that
code
or
you
know,
send
the
pull
request
to
hopefully
make
it
slightly
better
and
I
think
something
that
I've
you
know
been
involved
with
is
sort
of
trying
to
you
know,
there's
sort
of
increasingly
there's
a
different
areas
of
Google
that
are
interested.
You
know,
other
teams
at
Google
are
exploring
open-source,
and
so
I
am
trying
to
sort
of
take.
B
C
E
B
C
B
Yes,
something
I
miss
the
insight
about
Google.
You
know
that
I'm
personally,
passionate
about
is
I
feel
like
it's
very
easy
inside
of
Google.
Since
there's
it's
more
like
a
monoculture
inside
of
the
company,
it's
easier
for
me
to
run
around
to
different
areas
of
the
company
and
send
contributions
there
and
have
a
similar
expectation
like
I'd
love.
C
It's
interesting
that
you
should
say
that,
because
so
I'm
fairly
so
I
came
to
programming
late
in
life.
This
is
it's
it's
not
just
that
kubernetes
is
new.
To
me
like
being
a
programmer,
is
also
a
new
thing
for
me.
So
and
it's
been
exciting
and
fun.
It's
been
really
great
that
my
first
open-source
community
got
to
be
the
kubernetes
community,
because
now
I
go
and
contribute
to
other
open-source
projects
and
I
mean
mostly
in
terms
of
documentation.
C
I
I
really
believe
in
documentation,
as
mentoring,
almost
just
because
often
I
run
into
things
that
don't
make
sense
to
me
and
they
hiccup
for
me,
because
I
am
not
quite
experienced
enough
to
figure
out
what
they
may
have
meant,
rather
than
what
the
documentation
actually
says.
So
I
just
walk
up
to
other
open
source
projects
and
I
almost
expect
everyone
to
act
like
they
were
in
the
kubernetes
project
and
I
behave
that
way,
and
so
far
I
haven't
really
had
much
trouble.
So
far,
it's
been
serving
me
really
well.
C
A
D
Would
ask
that
people
be
considering
the
user
facing,
and
you
know,
operator,
facing
consequences
of
their
changes
and
suggestions
and
also
being
active
in
identifying
places
where
systems
that
we
get
used
to
are
actually
pretty
creaky
or
unclear.
This
is
a
very
I
mean.
There's
there's
a
lot
of
unseen
problems
that
we
all
learn
to
accept
in
the
contribution.
Workflow
that
are
relatively
painful.
There's
a
lot
of
work
going
on
right
now
to
try
and
improve
that
same.
D
Just
using
kubernetes
or
like
I
mean
I
work
on
the
Installer
by
installing
kubernetes
is
like
not
easy
and
all
the
time
we're
getting
reports
from
the
field
was
like.
Oh,
we
tried
to
fix
this
one
thing
or
like
we
have
a
new
feature
in
the
API
server
and
this
flag
is,
you
know,
deprecated
to
viewer.
This
is
now
needs
to
be
formatted
in
this
manner
and
it
just
breaks
everybody.
You
know
thirty
percent
of
people's
stuff.
We
just
don't
know
about
it.
A
F
A
F
F
So
we
can
run
three
types
of
jobs,
ones
that
are
testing
your
PRS
ones,
that
are
testing,
urges
and
then
ones
that
are
run
on
a
schedule
and
we
run
those
all
as
pods
on
a
communities
cluster
and
that's
the
first
thing
that
does
the
other
really
important
thing
that
does
is
providing
it
have
automation.
So
all
the
bottom
ation
that
you
see
is
provided
by
munch
prowl
and
then
a
few
months
punch,
github
and
that
implements.
Although
the
slash
commands
that
you
see
as
well.
A
F
The
the
reason
we
have
the
slash
commands
for
so
many
things
is
mainly
because
of
a
lack
of
granular
permissions
and
github.
You
basically
have
to
give
people
write
access
to
the
entire
repo.
If
you
want
to
be
able
to
control
things
like
labels,
and
we
want
to
be
able
to
limit
who
has
access
to
which
labels
and
limit
who
has
access
to
emerge
PRS
in
specific
directories,
instead
of
just
giving
someone
right
access
to
everything.
So
that's
kind
of
the
main
motivations
Automation.
A
D
Whenever
I
submit
something
trivial
and
understand
that
there's
all
this
overhead
that
needs
to
go
through
its
gonna
get
tested
and
somebody
has
to
review
it,
but
I
sort
prove
it
so
I
typically
draw
a
slash
me
on
there,
just
because
somebody
deserves
a
cat
picture.
You
know
if
they're
gonna
read
my
typos
fix
or
something.
F
B
So
I
think
an
another
one.
That's
interesting
is
the
the
PR
dashboard
which
I
find
helpful,
for
you
know
figuring
out
whether
I
you
know,
if
I
have
a
bunch
of
PRS
assigned
to
me
that
I
need
to
review
or
that
I've
sent
to
other
people
and
I'm
waiting
for
review.
That
one
helps
tell
me
if
which
ones
I
need
to
respond
to
and
which
ones
I
need
to.
B
You
know
wait
for
somebody
else
to
respond
to
there's
been
talk
about,
extending
that
to
be
to
also
have
like
an
issue
dashboard
you
know
to
where
I
could
sort
of
see
like
what
are
the
you
know.
What
are
the
features
that
that
I
need
to
work
on
this
release
and
or
also
potentially
extend
it
to
SIG's?
So,
like
you
know,
what
does
what
a
cig
note
planning
or
what
you
know
things
do
they
have
that?
Maybe
I
could
jump
in
on
that
work
has
been
thought
about,
but
we
don't
have
anybody.
B
B
C
This
is,
this
is
not
really
a
kubernetes
pacific
thing,
but
it
could
have
specific
thing.
I
literally
just
have
like
bookmarks
for
for
pull
requests
on
my
browser
that
says,
review,
requested
review,
assigned
issues
assigned
so
that
I
can
keep
track
of
my
own
things
that
I'm
working
on
or
that
other
people
are
working
on
and
want
me
to
comment
on,
and
I
check
those
periodically.
D
C
B
B
B
C
It
also
helps,
if
you
with,
for
that,
if
you
collaborate
with
somebody
in
the
community
that
you
know,
then
my
default
is
often
to
just
assign
that
person
to
the
pull
request.
Just
not
let
the
bond
do
it,
because
if
I've
been
working
really
closely
with
Eric
on
something
and
then
randomly
the
bot
decides
to
assign
Col
to
it,
that's
just
not
going
to
be
great
for
anybody
right,
because
I
think
it's
it's
just
better.
It's
just
better
when
you
feel
free
to
just
use
those
commands
and
actually
assign
a
person.
F
A
D
F
F
C
F
C
F
We
do
have
some
there's,
occasionally
hiccups
and
whatnot
related
to,
for
example,
we
we
run
our
instance
using
legacy
identification
instead
of
our
back.
So
there's
some
differences
that
sometimes
cause
the
sample
versions
to
get
a
little
bit
out
of
sync.
But
that's
something
that
we
want
to
resolve.
A
And
I
don't
know
how
outdated
this
is.
I
mean
it
says,
does
some
end
of
December
date
but
been
the
older
actually
has
a
really
good
blog
post
about
prowl
I'm
gonna
plug
that
in
the
chat
and
it's
really
cool.
It's
got
a
ton
of
graphics
on
there,
but
it's
for
those
folks
listening
that
aren't.
On
slack
it's
been
the
Elder
io
/
post,
slash,
prowl,
a
very
cool
stuff.
Any
other
questions
from
the
panelists
I
am
looking
to
see
if
we
have
any
other
questions
on
the
other
mediums.
A
We're
all
good
all
right.
Well,
thank
you
so
much
to
our
panelists
today.
This
is
it
for
the
June
sessions
of
meet
our
contributors.
The
next
session
will
actually
be
in
July,
not
on
the
first
Wednesday,
that
is,
the
4th
of
July
in
the
States
will
actually
bump
that
to
the
second
week
for
more
details,
please
join
the
kubernetes
slack
channel
for
meet
our
contributors.
You
can
also
copy
the
meet
our
contributors
calendar
from
kubernetes
io
/
community.