►
From YouTube: Kubernetes Community Meeting 20190117
Description
We have PUBLIC and RECORDED weekly meeting every Thursday at 6pm UTC.
See https://github.com/kubernetes/community/blob/master
B
Alright,
welcome
to
today's
edition
of
kubernetes
Thursday
community
meeting
today
is
January
17th,
depending
on
where
you
are
in
the
world.
I
guess
most
of
the
world
today
or
right
now.
Rather,
my
name
is
Paris
Pittman
I
work
at
Google
I'm.
Also,
the
co-chair
of
the
special
interest
groups
for
contributor
experience,
I'm
bias,
it's
my
favorite
and
today
we
are
going
to
have
our
regular
show
of
amazingness.
B
We'll
have
a
demo
we'll
also
do
release
updates
we'll
go
into
a
contributor
tip
of
the
week,
and
then
we
also
have
CLI
on
the
line
and
C,
and
we
have
Sean
with
us
today.
We'll
do
some
announcements.
I
have
a
quick
steering
committee
update
and
then
also
we'll
finish
up
with
some
shout
outs.
So
first
things
first,
we
are
gonna.
B
Do
we
are
gonna,
probably
have
a
question
time
for
questions
today
on
most
sections,
if
you
do
have
a
question
and
someone
else
is
speaking,
just
go
ahead
and
either
raise
your
hand
or
let
us
know
and
chat
so
that
we
can
call
on
you
and
that
we're
not
all
stumbling
over
each
other
to
speak.
So
first
things.
First,
we're
gonna.
Do
is
the
demo
Mary
you
are
on
caboose?
Why
don't
you
kick
it
off.
C
Hi
everyone
I
want
to
share
with
you
something
we'll
build
a
new
solution
for
sorry,
it's
how
to
talk
and
question
the
right
button
today.
Okay,
yes,
I
want
to
talk
to
share
today.
Commodes
is
a
new
solution.
We
build
for
a
secret
and
keeping
the
kitchen
on
kubernetes
and
it's
available
on
github,
so
you
can
check
it
out
while
I'm
speaking,
but
first
I
want
to
answer.
C
Why
do
we
even
need
a
new
tool
like
a
lot
of
solution
existing
outer
and-
and
they
are
critical,
so
I
want
to
start
with
with
specifying
that
we
always
see
cats
on
a
regular
basis
and
usually
this
kind
of
things
highly
sensitive.
So
this
is
why
we
want
we
might
want
to
protect
them
with
one
away
in
kitchen,
meaning
once
they
get
that
they
are
now
like
to
the
kitchen
them
back.
C
The
basic
amount
is
object
that
we
just
commit
can't
commit
a
source
at
all,
because
Indiana
called
the
representation
is
in
base64.
So
this
is
why
many
people
ending
up
using
surgical,
SI
saket,
is
a
great
solution,
because
it
gives
you
a
way
to
encrypt
seeker,
so
you
can
commit
them
to
source
control
and
have
good
good,
get
ops
with
your
secrets,
but
it
has
some
challenges.
Yes,
it
has
a
challenges
for
security
point
of
view.
C
There
is
one
keeper
you
just
don't
get
all
the
secret
and
installed
on
the
on
the
cluster
itself
and
it
has
the
same
challenges
we
have
with
one
or
two
seconds,
both
with
checking
them,
which
is
can
be
a
bit
mess
like
if
you
don't
want
to
walk
with
and
go
on
to
other.
So
usually,
people
ending
up
with
checking
our
configuration
file
by
64
week,
oh
and
keep
it
with
a
ticket
and
then
have
it
in
1
km.
C
The
second
and
we
didn't
like
all
the
existing
solution,
and
none
of
them
was
a
good
and
not
something
we
feel
insecure
and
all
busting
up
watch
videos.
So
we
understand
that
we
need
to
build
a
new
solution,
which
we
call
Tomas
Tomas
is
awarded
here.
Bow
and
form
is
also
on
speaking
Hebrew,
and
it
means
something
that
is
ticket
or
hidden.
And
now
we
want
to
show
you
a
quick
demo
come
on,
saw
it
walk
today.
I
am
going
to
show
is
also
available
on
the
repository
and
under
this
path.
C
So
you
can
run
it
yourself
on
your
machine
and
so
let's
start
I
have
a
comments.
Data
on
my
machine
in
Munich,
you
and
I
have
a
five
pots
running
right
now,
if
brownie
vamos,
due
to
the
capital
to
encrypt.
Oh,
it's
two
different
api's
and
one
of
the
example.
Let's
say
good
pot
forward,
so
I
can
view
the
example
application,
and
this
is
the
example
and
I
walk
in
in
PHP
just
and
facets
that
commands
can
walk
with
any
language.
C
It's
not
capital
specific
language
and
it
was
really
easy
to
support
it,
and
basically,
this
application,
via
US
trade
secret
from
this
path
and
weight
into
skin,
because
usually
what
you
do
with
you
get
acquaint
them
to
skin,
and
so,
let's
see
how
we
can
provide
seeker
to
these
applications
using
camels
so
to
provide
a
secret
to
this
application
using
commands,
and
the
worker
must
walk.
Is
that
you
and
keep
secrets
for
a
specific
application
and
we
identify
application
using
a
service
account
using
by
the
pot
so
I'm
going
to
find?
C
Someone
say
right:
I'm,
going
to
run
it
inside
it
last
time
and
I'm
going
to
tell
it
in
shape
and
I
want
to
inject
something
like
for
a
super
secret
for
this
service
account
and
the
service
account
is
in
the
next
video
and
I'm
going
to
give
it
to
walk
you
around
and
I'm
going
to
tell
c'mon.
Let
me
walk
with
insecure
URL,
because
by
default
see
I
will
not.
Let
me
walk
with
insecure
and
what
they
are
yeah.
C
Okay,
so
this
basically
going
to
one
iPod
inside
the
cluster
and
of
course,
for
some
reason:
now
it's
not
walking
and
anyway,
if
it's
worth
walking,
what
there
was
I
think
is
something
like
that
this
is
an
Egyptian
ticket.
Can
you
still
hear
me?
Could
it
so?
This
is
an
accepted
seeker,
and
this
is
sounds
a
guy
can
come
into
hospital
and
do
whatever
I
want
with
it.
So
I
need
to
put
this
seeker,
and
the
next
thing
I
need
to
do
is
I
need
to
add
a
comma
in
each
container.
C
So
let's
uncomment
it
the
inch
maintainer,
basically
Akkadian,
captain
sig
has
found
the
config
MA
ticket.
The
kingdom
will
config
washing
fired
at
my
application,
can
mount
and
now,
after
committing
to
source
control,
I
can
do
PGD
reply
in
a
sec,
doc
and,
of
course,
I
need
to
say,
and
this
will
run
the
deployment
and
now
when
the
deployment
completed,
I
can
go
pause
forward
again.
C
C
Okay,
it
just
takes
time
to
stop
good,
so
you
can
see
that
we
get
it,
and
this
is
dedicated
version
of
this
content,
and
so
now
I
want
to
take
some
questions
and
I
figure.
It
might
be
easier
than
giving
more
content
and
don't
have
a
lot
more
time.
So
if
someone
has
question
this
is
now
a
good
time,
if
not
finish,
my
demo
and
I
will
be
happy
to
chat
with
anyone
else
after
on
traumas
and
how
it
can
help
and
how
it's
different
for
my
existing
solutions.
C
So
this
is
a
good
question,
a
chemist
and
even
kitchen,
and
it
has
support
for
pluggable
in
kitchen
and
the
kitchen
area
and
solution.
So
currently
we
are
supporting
the
option.
The
field
is
AES
with
like
in
memo
with
key,
which
is
the
most
insecure,
and
we
also
support
as
your
keyboard
and
DC
pkms,
which
are
more
secure
and
you
want
to
add
support
for
WS
kms.
C
B
E
Everybody
I'm
Aaron
of
cig
beard.
Hopefully
my
internet
doesn't
skip
out
on
me
today.
I
am
your
114
release
lead.
Today's
cat
t-shirt
is
the
many
phases
of
the
cat,
because
B
is
released,
team
go
through
many
phases
and
the
release
life
cycle.
I
will
share
my
screen,
but
you
can
follow
along
if
you'd
like
by
clicking
the
same
links
that
I
do
in
the
meeting
notes.
So
we're
gonna
share
this
screen.
Awesome
I
shared
the
right
screen,
the
first
try.
This
looks
really
tiny
to
you.
So
now
it
looks
larger.
E
E
If
you
are
interested
in
this,
please
come
on
down
to
the
Sigler
release
kind
of
tangential.
To
this,
like
we
talked
about
creating
some
sub
projects
in
cig
release
and
the
release
engineering
sub
project
is
one
of
them
so
on
the
release.
Team,
like
I,
need
a
point
person
to
cut
a
build,
but
I
think
how
we
improve
the
process
of
cutting
a
build
and
what
tools
we
use
is
something
that
a
whole
bunch
of
people
could
help
out
with.
E
So
I
appreciate
all
of
your
page
as
we
work
through
that
we
also
have
an
enhancements
tracking
spreadsheet.
For
this.
If
you'd
like
to
take
a
look
at
this,
all
of
these
are
linked
off
of
the
release
schedule
that
was
linked
in
the
meeting
notes
and
is
in
this
release.
Repo,
let's
see
here
so
just
on
the
subject
of
everything,
must
have
a
cap
if
you're
confused,
if
you
have
questions,
please
feel
free
to
reach
out
to
me,
based
on
the
feedback.
E
I
have
gotten
very
first
saying
we
talked
to
about
this
was
week
was
say,
gasps
and
filled
with
rock
asked
a
bunch
of
really
great
questions
and
then
expressed
his
feedback
in
the
form
of
the
PR.
I
love
it
when
people
in
the
open-source
community
do
this.
So
we're
gonna.
Take
a
look
at
updating
the
cap
template
to
include
these
release
checklists
and
these
graduation
criteria.
E
Chatting
with
cig
architecture
about
what
they
would
like
to
see
in
this
at
the
meeting
that
follows
this
and
I've
also
talked
with
cig
p.m.
about
them
owning
sort
of
the
stewardship
of
the
cap
process,
I
figure
a
bunch
of
project
and
product
and
program
managers,
whichever
P
you
want
to
call
p.m.
probably
all
have
a
lot
more
experience
with
being
organized
than
I
do,
and
so
there
is
a
board
out
there
that
Steven
Vestas
has
put
together
bunch
of
tasks
for
people
to
help
out
on
I.
E
E
To
move
forward
on
the
patch
release,
stuff
I'll
share
my
screen
for
this,
but
there
is
a
schedule.
That's
linked
in
the
meeting
notes.
We're
gonna.
Try
doing
this
thing
where
we
call
out
when
we
want
to
cut
the
next
patches
for
the
next
versions
of
kubernetes,
so
you
can
click
that
like
to
find
out
that
information.
There
was
also
a
lot
of
discussion
at
the
sinc
release
meeting
this
week
about
whether
it
made
sense
to
cut
another
patch
release
for
version
10.
Technically
speaking
version
10
is
beyond
the
three
supported
versions
of
kubernetes
boundary.
E
However,
we
do
just
still
happen
to
have
the
CI
infrastructure
in
place
to
allow
us
to
cut
a
release
of
110
if
there
were
a
situation
that
called
for
it,
and
so
we
talked
about
what
criteria
we
might
use
to
decide.
Yes,
it's
worth
cutting
a
release
of
kubernetes,
even
if
it's
outside
of
our
support
window,
Jordan
Leggett,
did
a
great
job
of
articulating
and
summarizing
the
discussion
that
led
us
to
agree
that,
yes,
we
should
cut
that
release.
E
B
B
We
do
have
many
many
many
mentoring
programs,
I'm,
focusing
on
the
ones
that
are
current,
that
are
live
and
it
please
feel
free
to
interrupt
me.
If
you
have
any
questions
and,
of
course,
zoom
chat
as
well.
First
one
is
meet
our
contributors,
which
is
a
monthly
youtube
series
that
happens
on
the
first
Wednesday
of
every
month.
The
link
in
there,
if
you
are
following
along
in
the
agenda,
has
the
playlist
for
our
past
series.
B
We
have
a
panel,
we
have
a
panel
of
mentors
who
are
current
contributors
of
many
different
levels,
meaning
some
of
them
just
had
a
few
PRS,
all
the
way
up
to
maintain,
errs
and
founders,
and
this
gives
us
a
really
awesome
brett's
of
experience,
and
we
take
questions
from
the
meter
contributors
slack
channel.
It's
a
really
great
time.
It's
about
an
hour.
B
The
questions
vary
from
very
specific
tool
if,
for
instance,
likewise,
my
test
flaking
all
the
way
to
extremely
broad
like
hey,
how
did
you
get
into
open
source
or
how
do
you
combat
burnout
and
some
other
really
serious
questions
that
you
would
typically
ask
a
mentor?
This
is
scalable
mentoring.
We
have
had
over
a
thousand
unique
views.
Some
of
our
more
popular
episodes
have
to
do
with
code
based
tours.
B
We
had
one
where
a
contributor
gave
a
very
quick
on-the-fly
code
base,
tour
of
kubernetes
kubernetes,
which
was
really
awesome
and
that's
our
highest
watched
video
to
date,
and
we
have
two
sessions
for
that.
That
happened
on
again
the
first
Wednesday
of
the
month.
That's
a
3:30
p.m.
and
9:00
p.m.
that's
UTC
check
your
local
time
and
we
actually
split
out
two
sessions.
One
session
is
always
a
steering
committee
AMA,
and
this
is
really
great
for
current
contributors.
Of
course,
new
contributors
too,
but
current
contributors
can
ask
questions
like
hey.
B
Why
did
the
structure
change
or
what
some
need
to
define?
What
exactly
is
a
project
is
for
me
all
kinds
of
governance
questions
how
they
got
involved.
It's
a
really
good
time
and
then
the
other
session
is
just
a
regular
panel
of
mentors.
So
that's
meet
our
contributors.
The
next
that
we
have
going
on
that
we're
currently
recruiting
for
is
Google
Summer
of
Code.
A
lot
of
our
top
contributors
have
come
from
this
program,
so
it's
very
worthwhile
and
we
have
fun
doing
it.
B
Cn
CF
submitted
our
application
and
we're
aiming
for
as
many
as
Google
will
give
us,
and
so,
if
you
have
an
interesting
project
for
your
cig
or
you
can
mentor
doesn't
necessarily
need
to
be.
Both
email
was
sent
from
nikita
to
kubernetes
the
kubernetes
dev
mailing
list
today.
Please
look
at
and
then
adhere
to
the
deadlines.
You'll
also
get
reminders
on
this
call,
as
well
as
all
the
other
800
million
bajillion
channels
that
we
have
for
you
for
communication
new
contributor
workshop.
B
This
is
an
awesome
way
for
us
to
get
new
contributors
who
are
both
new
and
not
new,
to
open
source.
We
attack
this
on
to
all
of
our
cube
cons.
Now,
specifically,
the
contributor
summits,
and
that's
also
a
way
for
current
contributors
to
see
and
talk
to
new
contributors
that
are
coming
in
the
door
as
well.
The
little
link,
that's
in
actually
I,
did
not
put
the
link
in
there.
B
B
That's
been
done
by
Gwyn,
Sanger,
Josh,
burkas,
Tim
pepper,
so
many
others
in
contributor
experience
who
have
really
just
walked,
walked
so
many
miles
to
try
to
to
have
an
interactive
experience
for
new
contributors,
because
we
do
have
automation
and
CI
that
other
projects
don't
have,
and
this
gives
them
an
experience
to
actually
go
through
their
first
PR
and
things
along
those
lines
and
the
videos
are
great
to
give
other
new
contributors.
Who
ask
you
hey?
How
do
I
start
contributing
to
kubernetes?
It's
a
great
it's.
B
So
it's
a
great
101
we're
actually
going
to
be
doing
a
sort
of
201
class
so
like
in
college
terms
like
the
next
one
over
the
one-on-one
for
some
intermediate
contributors
and
we've
all
boarded
over
200
new
contributors
last
year.
A
lot
of
those
were
also
at
Shanghai
too,
and
that
was
something
that
I
know
a
lot
of
folks
that
we're
planning
that
have
never
done
so.
It
was
a
great
experience
there
also
the
release
team.
The
release
team
is
one
of
the
backbone
mentoring
programs
that
we
have
within
kubernetes.
B
Erin
is
waving
at
you
right
now.
I
recently
the
release
team
did
put
out
a
survey.
The
survey
link
is
in
the
agenda.
It's
just
not
highlighted
as
a
hyperlink.
I
will
do
that
right
now,
and
this
is
a
way
to
get
a
unique
experience
into
the
look
of
all
of
the
moving
parts
of
kubernetes.
Many
people
release
things
on
a
quarterly
basis
here,
so
you
get
to
see
key
players,
owners
maintained
errs
and
that's
how
a
lot
of
our
contributors
come
in.
B
They
get
to
see
the
lay
of
the
land
and
they
get
to
see
where
they
can
fill
in
gaps.
So
that's
it
for
me
for
mentoring,
programs.
Next
time,
I
hope
to
talk
about
some
other
ones
that
are
being
built
that
have
to
do
with
remote
pair
programming,
new
contributor,
ambassadorship
and
many
others
that
have
issues
that
are
currently
filed
in
the
kubernetes,
slash
community
repo.
If
you'd
like
to
get
involved
and
that
wraps
things
up
for
me,
any
questions.
A
A
So
what
have
we
been
working
on
so
we've?
We've
got
several
broad
areas
that
we've
been
that
our
efforts
have
been
geared
towards.
The
first
is
extension
mechanisms,
including
plugins
and
dynamic
koop
control
commands
for
project
health.
We've
been
we've.
We've
made
a
major
effort
in
order
to
get
coop
control
out
of
kubernetes
kubernetes
out
of
communities
core
and
I'll
dive
into
that
a
little
bit
more
and
in
order
to
to
address
our
the
apply,
a
declarative
management
of
apps.
A
If
you,
if
you
put
a
binary
in
within
the
path
and
it's
prefixed
by
coop,
cuddle,
then
coop
control
that
then
that's
basically
a
binary
that
there
sorry
a
plug-in
that
coop
control
will
will
recognize
and
run.
So
if
you
have
a
coop
cuddle,
NS
like
for
namespaces
and
you,
you
actually
type
in
coop
cuddle
NS,
and
it's
going
to
invoke
that
that
plug-in
binary.
A
So
as
I
mentioned
before,
we've
refactored
poop
control
some
of
the
core
functionality
into
this
CLI
runtime
repository
I've
left
a
link
to
that
repository
so
that
plugins
can
reuse
this
core
functionality
and
some
of
that
core
functionality
includes,
like
the
resource
builder,
slash
client
and
in
printers.
But
if
you'd
like
to
know
more,
please
follow
that
link
and
and
again,
if
you'd
like
to
know
more
there's
a
really
good
video.
The
sixth
seal
I
did
a
deep
dive
with
watch
a
syllabic
and
and
Juan
Vallejo
at
the
recent
coop
con.
A
Address
the
day-to-day
three
problems
with
plugins
like
how
do
you
discover
them?
How
do
you
upgrade
them,
and
that
is
the
crew
project
and
again
there's
a
link
there
to
that
repository?
This
is
in
relatively
early
stages,
and
so,
but
you
should
expect
that
there
will
be
efforts
in
that
vein
going
forward.
A
So
in
addition,
as
I
mentioned,
we're
moving
coop
control
out
of
kubernetes
core.
We,
we
believe,
will
get
much
better
velocity
in
the
cadence
for
building
coop
control
actually
will
probably
be
different
than
kubernetes
as
a
whole.
Our
first
efforts
into
this
were
actually
fairly
close
to
moving
package,
coop
control
that
entire
hierarchy
of
code,
which
is
the
vast
majority
of
coop
control
code
into
staging,
hopefully
by
this,
this
release
in
114,
and
that
would
be
the
first
effort
into
getting
coop
control
out
of
kubernetes
core.
A
A
So
in
addition,
this
this
will
be
actually
a
major
win
for
coop
control
and
for
kubernetes
as
a
whole
by
moving
the
apply
functionality
into
the
server
so
that
other
clients
can
can
use
this
functionalities.
The
complexity,
that's
in
coop
control
that
the
apply
actually
has
a
lot
of
sharp
corners,
and
that
should
be
cleaned
up.
This
server
side
apply
should
be
alpha
by
114.
A
Okay,
so
miscellaneous
we've
merged
our
first
charter.
I
just
wanted
to
point
out
that,
in
addition
to
the
standard
rules,
we
added
a
couple
of
our
own
roles,
including
emeritus,
lead
and
another
role
called
the
test.
Health
maintained,
a
role,
somebody
who's
responsible
for
making
sure
that
all
of
our
tests
are
passing
and
and
kind
of
shepherding
the
the
test
grid
to
make
sure
that
we're
green.
A
And
if
you
want
to
look
at
the
Charter,
the
link
is
there
and
finally,
I've
included
some
links
for
our
coop
con
talks
in
Seattle
we
did
an
intro
and
a
deep
dive.
The
links
are
for
the
videos,
as
well
as
the
slides,
if
you're
interested
as
I
mentioned
before
the
deep
dive
was
a
deep
dive
into
plugins
and
so
I
just
threw
this
slide
in
just
before
the
meeting
started.
A
Fill
wit
Rock
mentioned
to
me
that
we're
soliciting
feedback
from
the
community
about
the
features
and
functionality
of
coop
control,
and
if
you
want
to
know
more
about
that
or
be
involved
in
this
survey,
please
follow
this
link
into
our
email
group
and
that's
the
reference
links.
So
that's
the
end
of
if
you
download
these
slides,
then
hopefully
you'll
be
able
to
follow
some
of
these.
If
you're
interested
to
know
more
about
6:00
Eli
and
that's
it,
let
me
unshare
this
I
wonder
how
I
do
that.
Thank.
B
B
B
We
go
all
right
now
next
week,
if
you
are
in
signals,
seeing
API
machinery
or
say
cloud
provider,
you
are
up
for
a
update
and
then
that
leaves
us
with
our
last
part.
The
announcements
yay
this
week,
the
cube
con
Barcelona,
see
if
piece
emissions
are
due.
That
is
like
24
hours,
ish
I
can't
math
from
now
aka
everybody
on
this
column.
It's
a
should
submit
a
CAF
P.
Oh
no,
everybody
on
the
program
committee
is
like.
Don't
do
that?
No,
but
anyway,
we
would
love
to
hear
what
you
have
to
say.
B
Please
submit
a
CFP
that
would
be
wonderful,
yes
and
whoever
just
put
in
the
note
for
the
six
sessions
due
February
8.
If
you
would
like
a
maintainer
track
slot,
meaning
you
are
in
a
special
interest
group
and
would
like
to
introduce
your
special
interest
group
to
this
audience
or
do
a
deep
dive.
That
information
is
in
your
email
box.
E
Everybody,
so
you
may
have
seen
a
notification
of
kubernetes
stuff
a
little
bit
ago
about
us.
Turning
on
a
tool
we
use
called
parabolas,
that's
the
thing
we
currently
use
today
too,
you
to
the
kubernetes
org
by
way
of
an
issue
or
a
poll
request,
so
that
this
process
is
more
auditable
and
more
user
friendly
compared
to
having
to
mail
random,
Google
Group.
We
would
now
like
to
do
the
same
thing
for
teams,
so
we
sent
out
a
notification.
E
We
tried
turning
the
thing
on
and
we
completely
blew
through
all
of
our
kid
hub
tokens,
some
kind
of
Brooke
CI,
it's
a
great
thing
to
do
on
a
Friday,
I
highly
recommend
it
Friday
evening.
In
fact,
so
we
think
we
have
fixed
that
I'm
actually
still
kind
of
like
trying
to
ping
people.
So
maybe
this
isn't
as
formal
of
an
announcement
as
it
should
be,
but
I'm
pretty
sure
we
turned
it
on
and
things
didn't
blow
up.
E
So,
if
not
now,
like
really
really
soon,
you'll
see
a
notification
to
kubernetes
staff
that
we
have
turned
it
on
in
our
usual
style.
Now
we
need
to
actually
document
how
he's
the
thing?
It's
probably
gonna,
look
something
like
opening
an
issue
against
kubernetes
org.
While
we
figure
out
how
to
streamline
the
process
and
maybe
eventually
we
can
get
to
the
world
where
you
PR
in
changes
to
team
membership
that
you
care
about.
E
If
you
are
used
to
doing
self
service
with
your
crowd
jobs,
you
know
how,
in
the
testing
for
repo
we
broke
up,
proud
jobs
by
save
directories
so,
like
cig
scaling,
can
change
their
jobs
without
having
to
book
people
who
are
in
the
root
owners.
Files
of
tests.
Infra
and
save
CLI
can
do
the
same
thing
and
they
don't
have
to
stomp
on
each
other's
jobs.
We're
gonna
do
the
same
thing
for
teams.
That
seems
like
a
really
friendly
self-service
model.
E
This
creates
a
brighter
future
for
everybody.
I
hope
for
the
next
step
in
an
evil
plan
is,
if
somebody
wants
to
come,
help.
Add
support
for
github
teams
in
owners
files,
so
that,
like
prowl,
could
treat
owners
files
the
same
way
that
it
treats
that
retreat,
given
teams
the
same
way
that
it
treats
owners
aliases.
We
could
start
to
have
like
centralized
management
of
the
people
in
owners
files,
so
you
don't
have
to
go
Cheney
like
if
you
change
membership
or
whatever
in
your
cig
or
sub
project
owners.
E
Whatever
you
don't
have
to
go
touch
like
20
different
repos,
you
change
the
team
via
PR
and
then
proud
picks
that
up
automatically
that's
the
bright
shiny
feature
needs
work
to
get
there
and
I'm
kind
of
busy
with
the
114
release,
but
we
welcome
any
and
all
help,
I'm
sure
if
there
isn't
a
Help
Wanted
issue
for
this,
we'll
try
and
spell
one
out,
but
you
know,
come
and
talk
to
us
sooner.
If
you
want
to
help
out
there.
The
issue
is
linked
in
meeting
notes.
E
Contact
me
about
other
release
stuff,
but
I
feel
bad.
That,
like
there
are
a
number
of
people
who
are
pinging
me
directly
for
repo
creation
and
I
am
but
one
of
six
people
who
have
the
power
to
do
this.
So
I
want
to
make
sure
that
I'm,
not
your
bottleneck,
so
full
disclosure,
the
updates,
I'm
about
to
give
you
on
the
steering
committee
meeting
we
had
yesterday
have
not
been
approved
by
any
of
the
rest
of
the
steering
committee.
E
But
I
am
just
gonna
kind
of
read
through
our
publicly
readable
agenda
from
yesterday,
so
new
year,
new
steering
committee,
we
actually
got
stuff
done
during
a
meeting
which
is
kind
of
weird.
We,
we
came
to
consensus
that
the
product
security
team
as
a
formal
entity
should
be
classified
as
a
committee
and
I
know.
E
Maybe
that's
not
such
a
big
deal
to
some
people,
but
since
security
is
really
really
important
and
we
want
to
make
sure
we're
as
professional
as
possible
on
this
sort
of
laying
down
the
rules
for
who's
allowed
in
that
and
why
and
how
does
that
fit?
The
governance
structure
of
the
project
is
itself
important.
This
was
kind
of
raised
up
by
stake
release
as
they
went
through
to
try
and
figure
out
what
some
projects
they
own
and
were
like.
Why?
Why
are
all
the
security
things
in
our
in
our
repo?
E
So
steering
committee
needs
to
approve
that
and
move
forward
on
that,
but
yeh
progress.
Another
thing
that
happened
is
the
working
group
to
help
migrate
infrastructure
away
from
Google
and
towards
the
CN
CF
for
operating.
The
kubernetes
project
has
finally
been
officially
formed.
Wg
kate's,
infra,
hooray
I'm,
an
organiser
of
that,
as
is
DIMMs.
We
have
a
slack
channel.
We
have
a
mailing
list,
all
that
good
stuff.
We
even
have
a
project
board
and
we're
definitely
looking
for
volunteers
to
come
help
out.
E
We
are
not
yet
at
the
place
where
it's
like
you
get
a
kubernetes
cluster
and
you
get
a
kubernetes
cluster
and
you
like,
we
are
still
trying
to
figure
out
the
correct
policy
and
process
for
this.
So
people
who
are
like
I
run
a
sub-project
that
lives
in
kubernetes,
6
and
I
want
some
place.
To
put
my
images
or
I
want
some
place
to
put
my
packages.
E
We
would
love
to
host
that
for
you,
but
if
you
could
kind
of
come
help
us
build
that
you'll,
probably
get
it
a
lot
faster
than
wishing
that
it
magically
appears
and
some
of
the
the
boring
work
that
we
have
to
do
up
front
before.
That
is
stuff,
like
figuring
out
the
correct
process
and
policy
for
who
gets
admin
rights
to
all
of
this
stuff.
E
Ok,
other
steering
committee
stuff.
We
have
to
review
the
code
of
conduct
committees
charter.
We
are
behind
on
that.
We
are
gonna
kind
of
be
rationalizing
or
revisiting
a
number
of
working
groups.
We
feel
like
there
may
be
room
in
this
community
for
yet
one
more
model
of
like
group
governance.
What
have
you
call
it?
A
user
group
call
it
a
support
users
group,
call
it
a
buff
or
still
don't
know
the
name,
but
things
that
are
kind
of
like
long
running.
E
There
are
a
bunch
of
people
who
are
interested
in
something
but
they're
not
actively
contributing
anything
to
the
project.
That's
not
quite
as
big
because
sakes
contribute
to
the
project
and
it's
not
quite
a
working
group,
because
that's
a
time
bound
and
effort
that
crosses
SIG's.
The
CNC
F
has
working
groups,
but
those
working
groups
are
kind
of
weird
and
open-ended.
So
like
there's
a
working
group
about
serverless
and
there's
a
working
group
about
the
Internet
of
Things
stuff
like
that,
so
we're
trying
to
figure
out
what
model
makes
sense
for
that.
E
So
if
you
are
running
a
working
group
that
expected
thing
from
the
steering
committee,
as
you
figure
that
out
and
I
think
the
last
major
thing
I
want
to
talk
about,
is
we
want
to
figure
out
how
to
get
more
participation
and
make
it
easier
to
bring
business
to
the
steering
committee?
We
don't
want
to
be
the
bottleneck,
so
we
are
considering
opening
up
our
meetings
to
public
participation.
So
you
can
come
to
the
meeting.
E
You
can
ask
us
questions
you
can
put
stuff
on
our
agenda
still
figuring
out
the
logistics
of
that
so
I
kind
of
don't
want
to
promise
anything
in
a
recorded
medium
and
then
have
to
take
it
back
later.
But
we
were
talking
about
ideas
like
maybe
as
soon
as
next
week
or
maybe
every
other
week
or
something
along
those
lines.
So
look
for
notification
about
that
to
the
kubernetes
dev
mailing
list,
because
you're
all
awesome
community
members
and
read
that
every
day,
I
hope,
I,
hope,
I
hope,
I
think
that's
it
from
the
steering
committee.
B
E
B
All
right,
another
announcement
on
that
same
tip
on
that
same
steering,
committee
tip
the
contributor
experience
charter
has
now
been
merged.
If
you
want
to
take
that,
take
that
out
for
a
spin
links
in
the
agenda,
if
you're
sig
does
not
have
a
charter
asked
chairs,
why
and
a
quick
plug
for
mentors
if
anybody
out
there
would
like
to
mentor
or
if
you
say
that
you
just
don't
have
enough
time
to
mentor,
we
have
plenty
of
opportunities
for
that
use
case,
especially
meet
our
contributors,
which
I
talked
about
earlier.
B
This
could
be
a
one-time
one
hour,
commitment
for
you
for
the
next
year
that
will
help
reach
hundreds,
please
reach
out
to
me,
or
the
contributor
experienced
cig
in
slack.
That
brings
us
to
our
very
last
section,
the
shout
outs,
which
are
also
powered
by
slack
shout
out
Channel.
Thank
you
to
everybody
that
participates
and
shouts
folks
out
on
a
weekly
basis.
It's
a
great
way
to
give
recognition
first
things.
B
First,
stephen
augustus
is
shouting
out
josh
burkas
for
putting
together
the
list
of
draft
questions
for
the
survey
that
went
out
for
the
release
team
that
we
mentioned
earlier
as
well,
and
everyone
that
was
involved
in
it
looks
like
everybody.
That's
ever
been
involved
in
the
release
team,
a
or
Maria
Jordan
matey,
Aaron,
Maria,
Ben,
Tim,
pepper,
Alexandra
and
Aishwarya
Jordan
wants
to
say
all
hail,
dims
for
running
the
zero
length
flake
to
the
ground.
Awesome
work,
Tim's
code
Ranger,
a
K
Noah,
wants
to
shout
out
the
whole
Docs
translation
crew.
There's
tons
of
work.
B
That's
feat!
That's
going
on
right
now
in
Asia
for
those
that
don't
know
multi
level
different
translation
efforts
that
are
going
on
and
he
said
that
the
special
and
a
special
mention
for
Adam
Deng
has
put
a
ton
of
work
into
it.
In
total,
the
team
has
merged
over
444
p,
o
PRS
in
the
last
two
months.
That's
amazing!
Thank
you.
So
much
for
that
team.
Aaron
wants
to
shout
out
to
a
Coates
to
for
stepping
to
take
notes
for
sig
testings
weekly
meetings.
We
go
a
mile
a
minute
and
it's
much
appreciated.
B
B
You
can
check
out
the
pool
in
the
agenda
for
that
and
for
improving
our
working
group,
Doc's
generated
from
cigs
yeah
Moe
thanks
Nikita
and
then
also
Nikita,
wants
to
shout
out
miss
sprites
for
adding
lots
of
details
to
the
code,
generator
conversion,
gen
Doc's
links
in
the
agenda,
so
you
can
check
out
that
poll
and
does
anybody
else
have
any
last
minute.
Shout
outs
that
they'd
like
to
do
verbally
over
the
over
the
call
we
have
some
time
or
any
last
minute
announcements.
B
Alright,
I
guess
everybody
wants
those
ten
minutes
all
right.
Let
me
actually
look
in
the
chat,
looks
like
we're
all
good
in
chat
alright
and
that
wraps
up
this
edition
of
kubernetes
community
meeting.
Thank
you
so
much
for
joining.
We
will
be
back
here
next
week
same
time
same
place.
Thank
you.
So
much
enjoy
a
be.