►
From YouTube: Kubernetes Community Meeting 20180222
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
Notes: https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
A
Early
22nd,
we
are
live-streaming
on
the
Internet's
of
and
recording
on
YouTube.
So
please
be
cognizant
of
that,
and
there
is
no
demo
for
this
week
due
to
the
home
summit.
So
we're
gonna
go
right
into
release
updates
graph
of
the
week
with
Josh
and
then
some
sig
updates
so
Jase
take
it
away
with
the
release
updates.
Alright,.
B
So
we
are
in
week
8
of
12
in
the
110
release
cycle.
Things
are
going
to
start
rolling
fast.
Now
the
full
schedule
is
linked
in
the
community
meeting
notes.
There
is
a
link
that
will
tell
you
more
about
what
the
various
things
we're
talking
about
here
mean
specifically
this
week,
we're
in
Cote,
slush
and
I'm
gonna
turn
the
mic
over
for
a
moment
to
Josh,
who
is
our
our
main
bug,
Slayer,
slash
issue
tracker
for
this
release
and
he'll
give
a
little
bit
update
on
what
we're
doing
with
that,
and
why?
Okay.
C
C
We
seem
to
have
a
lot
of
issues,
some
of
them
with
related
PRS
that
are
things
that
got
started
either.
Either
they
got
kicked
out
of
1.9
because
they
weren't
ready
or
they
got
started
right
around
code
freeze
for
1.9
and
then
have
not
had
much
in
the
way
of
activity
in
the
last
month
or
two,
the
I've
hassled
everybody
about
who's
involved
with
those
issues
about
them,
not
all
six
have
been
equally
responsive.
C
Yes,
you
have
something:
that's
open
against
the
1.10
milestone
that
isn't
going
to
be
in
1.10
I.
Please
remove
it
from
the
milestone
as
soon
as
possible.
The
and
then
as
a
reminder.
What
happens
on
Monday
is
any
issues
and
PRS
that
are
going
to
stay
in
the
milestone
need
to
have
all
of
the
things
and
by
all
of
the
things
that
means
they
have
to
have
the
required
labels
kind
and
priority,
and
a
priority
of
important
soon
well,
actually,
priority.
C
Failing
test
or
higher
and
they
also
need
to
have
approved
for
milestone
from
the
sig
leads,
or
they
will
be
removed
from
the
1.10
milestone
by
the
automation.
So
please
figure
out:
what's
actually
getting
done
for
one
flight
end,
what's
not
getting
done
and
remove
the
issues
in
PRS
that
are
not
getting
done,
so
we
can
maybe
release
one
plate
at
a
time.
B
Great,
thank
you
so
much
so,
as
Josh
mentioned,
we're
gonna
be
hitting
code
freeze
on
Monday
and
what
code
freeze
does,
as
it
allows
us
to
stabilize
the
release
branch.
It
gives
us
a
chance
for
six
to
not
necessarily
focus
on
anything
but
bug
fixes
and
making
sure
that
the
release
fidelity
is
good.
This
is
our
chance
to
continue
our
trend
of
producing
very
high
quality
releases
for
the
communities
community.
B
So
we
expect
six
to
take
this
period
of
time
very
seriously
and
not
see
it
as
a
as
a
resting
period,
but
a
time
to
really
introspect
into
code
segments
that
you
own
and
identify
key
pieces
of
functionality
that
need
to
be
addressed
or
fixed
to
improve
release
quality.
This
also
means
tests.
If
there
are
tests
that
you
have
that
are
flaky
if
you're
sick
bones,
please
make
your
best
effort
to
resolve
those
flakes
as
we
move
forward
again.
B
These
are
all
things
we're
trying
to
do
to
isolate
release
quality
because
we
have
a
very
good
track
record
and
I
don't
want
to
that.
Runt
I!
You
know,
because
that's
this
really.
It's
easy
to
lose
trust
with
the
community.
With
the
release
that
goes
bad,
so
it's
incredibly
important
for
us
to
maintain
due
diligence
and
try
and
focus
as
much
attention
on
that
as
possible
in
this
time,
so
not
to
harp
on
it.
But
please
please
make
sure
that
your
SIG's
you're
looking
at
what
open
issues
you
have
and
triaging
those.
B
B
You
can
email
me
or
hit
me
up
on
slack
at
JD,
Morris
and
I'll
be
happy
to
help
coordinate
whatever
activities
need
happen
in
order
to
get
something
into
the
release
branch
after
code
freeze
and
we
have
we're
very
relaxed
in
terms
of
if
you've
got
it
if
you've
got
a
bug
fix
that
needs
to
go
in
we're
gonna
we're
gonna,
take
it
pretty
seriously
and
see
if
we
came
in
there.
So
don't
don't
think
this.
You
know.
Code
phrase
means
that
you
know
there's
absolutely
nothing
going
in.
B
So
it's
really
about
trying
to
just
rate
limit,
what's
going
in
and
making
sure
that
we're
not
accidentally
destabilizing
the
release
branch.
Lastly,
just
if
somebody
comes
to
your
sick,
meaning
on
behalf
of
the
release
team,
please
please
give
your
best
effort
to
help
them
out.
Getting
Doc's
done
is
a
perennial
challenge
and
I
know
that
documentation
is
a
lot
of
hard
work
and
it's
sometimes
unclear
about
who
needs
to
do
it.
B
But
if
you're
sig
is
really
seeing
something
that
has
user
facing
impact,
please
make
sure
that
that
is
documented
in
terms
of
the
regular
kids,
IO
documentation
or
in
the
release
notes
themselves
again.
This
is
our
key
part
of
our
contract
with
our
community
to
preserve
vigilance
and
visibility
and
all
those
things
that
that
make
communities
so
great
from
the
user
and
community
perspective.
So
this
is
pretty
much
what
I
have
I
sincerely
appreciate
the
countless
hours
of
hard
work
that
go
into
a
release
and
the
release
team?
B
Thank
you,
and
as
a
community,
we
should
be
thinking
all
the
release
team
members
I
reach
in
to
get
because
this
is
a
very
involved
in
time
consuming
we're
working
on
making
it
less
so,
but
until
it
is
there's
a
lot
of
human
hours
and
effort
that
go
into
this
and
I
appreciate
it.
So
that's
all
I
got
George
back
to
you.
C
C
The
these
are
recent
additions
to
the
dashboards
that
I
requested
from
Lucas
at
the
CNCs.
For
a
couple
of
reasons,
reason
number
one
is
I
over
the
last
year
year
and
a
half
we've
added
a
bunch
of
process
to
contributing
things
to
kubernetes
and
anytime
that
we
add
extra
steps.
There's
always
the
concern
that
this
will
deter
new
contributors
and
new
participants
in
the
project.
The
second
reason
is
honestly:
I
went
to
somebody's
talk
about
high
episodic
contributors.
C
To
you
know,
occasional
contributors,
people
who
contribute
part
time,
might
contribute
one
thing
per
release
or
whatever
and
their
importance
as
a
measure
of
project
health.
Because
if
you're
getting
a
lot
of
new
and
episodic
contributors,
then
it
shows
it's
still
relatively
easy
to
become
a
contributor
to
your
project.
C
So
the
top
set
of
lines
are
the
number
one
way
it's
the
number
of
issues.
So
the
green,
the
green
shade.
There
is
number
of
issues
from
people
filing
issues
for
the
very
first
time
and
the
blue
line
with
brown
shading
is
number
of
issues
I
from
people
who
only
file
issues
occasionally
and
only
occasionally
is
measured
by
the
number
of
issues
that
they
filed
in
the
last
year,
the
eye
on
the
dev
stats
ticket
there's
the
actual
math.
C
C
C
Okay,
okay,
new
and
occasional
eye
contributors,
and
by
contributors
we
mean
PRS,
pull
requests.
So
now,
in
this
case,
you
know
and
again
that
bottom
one
of
the
things
that's
actually
interesting
here
is
that
the
count
of
contributors
is
higher
than
the
count
of
PRS,
which
I
need
to
actually
look
into,
but
we're
also
seeing
still
steady
growth.
Here
there
is
something
on
July
31st,
which
I
believe
is
actually
a
data.
Artifact
I've
been
trying
looking
into.
Why?
C
Because
there's
no
particular
reason
why
the
number
of
PRS
that
we
have
would
triple
on
July
31st
of
last
year,
so
I've
been
trying
to
trace
down
where
that
came
from
so
ignore
that
spike
for
now,
because
I
don't
believe
it's
real
data,
but
for.
C
This
again
we're
looking
at
people
who
are
contributing
their
very
first
PR
people
who
are
contributing
a
PR
who
don't
tend
to
who
don't
contribute
more
than
3
PR,
3
or
4
PRS
per
year,
and
you
know,
and
what
the
contribution
trend
with
that
and
again,
it's
still
looking
pretty
good
just
by
the
process
that
we've
added
to
the
PR
process,
etc.
Despite
the
the
growth
of
regular
contributors
to
the
project,
we
are
also
still
gaining
quite
a
number
of
new
and
occasional
PR
contributors.
C
So
this
is
a
graph
to
watch,
as
we
add
other
things
like
if
we
were
looking
at.
Finally,
for
example,
breaking
up
the
repositories
breaking
up
kubernetes
kubernetes,
which
has
been
discussed
if
we
were
to
do
that.
This
would
be
one
of
those
graphs
that
we
would
want
to
watch
and
see
whether
that
increase
the
number
of
new
and
occasional
contributions
or
whether
there
decreased
it.
Because
it's
one
of
the
things
that
in
fact
so.
A
A
Awesome
great
any
questions
for
Josh.
I
can't
actually
see
the
chat
window
now
so
isn't
it
there's
nothing
in
chat.
Okay,
awesome,
alright!
Moving
on
to
sig
updates
Robert
were
you
able
to
make
it
I
know
he
was
on
the
way
to
the
office
and
he
might
or
might
not
be
able
to
make
it
today
before
he
said,
cluster
lifecycle
update.
A
A
Moving
on
to
announcements,
just
a
quick
reminder:
the
contributor
summits
happening
on
May
1st,
that's
the
day
before
keep
Kahn,
and
you
can
find
that
information
at
the
link
provided
Josh
and
I
kind
of
bashed
out
a
draft
schedule
that
we'll
be
landing
on
that
github
page
this
week
and
will
be
reminding
you
basically
every
week
from
now
on
until
cube
God
shoutouts
for
this
week.
So
this
is
a
little
program
that
we
started
anytime.
A
A
A
This
was
at
a
face-to-face
meeting,
so
a
lot
of
developers
weren't
chased
down
and
things
like
that,
but
just
a
reminder
that
we
always
need
help
from
existing
kubernetes
developers
to
answer
user
questions
it's
one
hour
a
month,
and
it
makes
me
sad
that
we
only
got
one
person
in
Europe
or
one
person
in
the
u.s.
there
by
themselves,
swap
with
user
questions.
So
shout
out
to
that
for
doing
a
great
job
in
soldiering
on
if
you're,
interested
or
your
organization
is
interested
in
helping
us
kind
of
commit
to
this
more
and
give
us
help.
A
We
would
really
appreciate
it
and
just
reach
out
to
me
or
follow
the
link
which
has
the
contact,
information
and,
lastly,
meet
our
contributors,
which
is
basically,
we
have
existing
kubernetes
contributors
there
and
new
people
who
are
interested
in
participating
can
ask
them
questions
about
workflow
or
about
contributions,
and
it
goes
on
March
7th,
which
is
the
second
Wednesday's
of
every
month
that
I
get
that
right,
Parris,
I
think
so
the
second
one's
days
of
every
month.
We
have
basically
developer
office
hours
and
third
Wednesday.
We
have
user
office
hours.
A
A
You
know
how
to
URL
hack
to
find
the
exact
thing
you
need
and
github
things
like
that
and
that'll
be
in
hash
meat,
our
contributors
and
slack,
and
we're
also
looking
for
people
to
do
a
real
live
peer
code
review
as
part
of
a
session
there,
so
that
we
can
record
that
and
capture
it
and
make
some
documentation
out
of
that,
and
with
that,
that's
all
the
announcements.
I
have.