►
From YouTube: Kubernetes Public Steering Committee Meeting 20190313
Description
SC Repo https://github.com/kubernetes/steering
Agenda and Notes http://bit.ly/k8s-steering-wd
A
A
So
first
off
there
was
a
email
sent
about
the
contributors
of
it
for
Cook
County,
looking
soliciting
feedback
from
the
steering
committee
with
regards
to
what
we
wanted
to
do.
If
there's
any
modifications
or
suggestions,
questions
comments,
complaints
concerns
that
we
should
feedback.
I
did
have
some
initial
questions
about
the
contributor
summit
for
coop.
Con
tu
outlines
basically
new
contributors.
We
already
have
a
large
contributor
pool.
I,
don't
know
if
folks
have
any
quick,
hot
takes
or
thoughts
on
this
or
do
they
want
to
folks
want
time
to
review.
B
A
There's
there's
a
missing
aspect
of
that
we
traditionally
had
with
the
the
contributor
so
that
where
we
had
experienced
contributors
or
sinks
sessions
or
something
something
akin
to
that,
this
is
kind
of
missing
from
this
document.
They
do
have
this
optional
portion
here,
where
they
say
it's
an
optional
succession
for
a
face-to-face
meetings,
I'd
almost
like
just
nix
the
optional
piece
and
call
it
good
enough
in
my
opinion,
but
I
don't
know
if
other
folks
have
thoughts
there,
I.
B
And
so
we
can
either
do
it
as
it
sounds
like
there's
already
a
section
like
a
plan
session
for
face-to-face
meetings,
and
then
maybe
we
could
facilitate
like
hallway
track
a
little
better
as
well,
by
saying
like
hey.
If
your
interest
in
this
topic,
like
this
part
of
the
hallway,
is
a
good
place
to
head
or
something
like
that.
C
Do
we
have
a
good
idea
about
how
many
contributors
from
each
sig
are
going
to
Barcelona?
Paris
is
commenting
in
the
chat
that
we
need
contributors
and
time
zones
outside
the
u.s..
That
also
implies
we
don't
have
enough
or
that
many
in
some
SIG's
contributors
outside
the
US,
so
I
wonder
if
that
should
affect
our
goals
and
expectations
for
the
summit.
In
terms
of
you
know
how
much
work
will
get
done,
or
you
know,
communication
amongst
existing
contributors
versus
just
focusing
on
ramping
up
some
new
serious
contributors
in
European
time
zones.
B
D
D
D
D
F
A
Okay,
as
long
as
there's
an
easy
means
for
the
SIG's
to
be
able
to
request
a
face-to-face
session
or
to
get
that
ramped
up
hidden
in
a
reasonable
time
frame,
I
think
that
seems
that
seems
like
a
reasonable
way
to
meet
all
the
criteria
that
you
know
all
the
requests
that
people
have
had
one.
We
focus
a
lot
on
the
community
and
trying
to
grow
the
community,
but
we
still
have
the
exit
path
or
existing
contributors
able
to
talk
about
road
maps
and
other
detailed
discussions.
Tim.
A
Decisions
don't
actually
facilitate
conversation
right,
they're,
more
of
like
they're,
a
point
for
us
to
discuss
a
high
level
of
roadmaps
and
here
the
intricate
details
of
a
project
or
sub
project.
But
they
don't
actually
facilitate
like
broader
discussion
amongst
contributors
to
for
us
to
like
needle
on
details
of
what
it
means
to
execute
on
on,
say.
Some
roadmap
item.
E
A
Great,
so
next
up
before
we
go
into
the
actual
backlog,
I
did
a
bunch
of
triage
across
the
whole
backlog
because
it
looked
hopefully
out
of
date.
I
use
the
standard
pattern
that
we
use
in
sick
poster
life
cycle
for
triage
in
the
backlog
and
I
used
a
little
bit
of
my
own
jurisprudence
on
understanding
which
ones
I
thought
were
critical
and
which
ones
are
important
and
I
was
going
to
update
the
project
board.
A
Maybe
after
we
had
a
conversation,
but
the
first
thing
I
wanted
to
do
is
actually
to
create
like
a
target
milestone
for
something
I
just
put
April
29
earth,
April
2019
as
it
as
an
arbitrary
milestone.
The
reason
I
did
this
was
because
a
lot
of
times
in
their
steering
conversations.
We
talked
about
things
but
I
wanted
to
actually
get
like
traction
of
execution
to
burn
down
our
backlog.
Is
there
a
time
frame
or
do
folks
have
thoughts
about
this.
B
H
It
might
be
good
to
do
May
if
we're
gonna
start
or
maybe
like
early
May
or
something
aligned
with
a
meeting
the
our
first
meeting
in
May
or
something
I
think
it's
gonna
get
to
him.
I
I
think
it
got
into
the
devolution
stuff
where
we
were.
We
were
iterating
more
in
the
SIG's
and
now
we've
built
up
more
of
a
backlog
here.
Having
a
concrete
mouth
is
helpful.
B
A
All
right
to
walk
through
the
the
current
milestone,
there's
a
bunch
of
things
that
I
have
marked
as
like
I've
wanted
all
over
the
place,
because
not
all
of
them
require
us
to
be
involved
in
they
can
be.
You
know,
delegated
out.
There's
a
couple
of
items.
I
didn't
want
to
address
first
kind
of
in
a
priority
order,
because
they've
been
sitting
for
a
long
time
and
I
think
we
should
probably
figure
out
ways
to
close
them
out.
A
Like
a
long
time
ago,
the
original
spreadsheet
that
we
created
just
seems
to
have
stalled
right
and
there
were
PRS
to
the
main
repository
to
update
these.
Do
folks
know
if,
if
this
is
still
a
thing,
just
that
we
still
need
to
address,
are
there
still
legacy
of
working
groups
that
should
be
pruned
or
updated
or
collapsed?
We
we.
H
G
B
A
H
F
C
A
The
next
one,
I
head
up
is
critical
or
urgent
to
address
in
sort
of
a
priority.
Fashion
was
the
Charter
Maeda
issue.
This
is
let
the
long-standing
issue
we've
had
since
forevers
I
wanted
I
wondered
whether
or
not
it
made
sense
to
keep
this
open,
because
we
have
a
bunch
of
the
charters
already
merged
and
I
wondered
whether
or
not
we
should
just
open
per
issue
or
issues
for
the
individual
charters
that
you
think
need
to
be
find
and
I
can
happily
go
through
and
take
a
look
at
what
currently
exists
in.
C
A
And
I'd
even
talked
with
Andres
I
came
on
this
and
it
helped
helped
him
with
his
charter
a
little
bit
on
the
language
and
vernacular
and
also
talked
with
me
she's
about
her
proposal
to
collapse.
Things
and
things
are
moving
along
smoothly.
There
so
I
think
we're
making
good
they're
making
good
progress.
A
B
So,
according
to
the
process
we
have
documented,
this
is
just
gonna
get
merged
next
week.
If
that
one
does
anything,
I
think
there's
a
leg
up.
Three
three
weak
lazy
consensus,
sort
of
thing
built
in,
but
if
three
people
want
LG
TM
it,
then
we
can
just
merge
it
maybe
guilty.
Just
by
being
on
this
call,
you
can
look
and
see
if
there's
a
checkbox
next,
your
name
yeah.
A
G
So
here,
like
the
community
rebuild,
we
already
have
like
a
working
group.
Lifecycle
document
I
think
Paris
that
some
refactoring
on
that.
So
the
document
how
to
form-
and
this
land
part
is
done.
The
only
budget
remaining
here
is
a
mapping
from
working
groups
to
fakes.
There
is
an
open
issue
on
community.
We
go
I.
Think
it's
like
the
last
issue.
A
G
B
A
Well,
I
just
made
it
so
there
was.
There
was
a
couple
things
that
I
think
also
fall
into
the
category
of.
We
just
need
some
finalization
on
the
details.
Formalized
sub
projects
I
did
give
some
feedback
to
Nikita,
I.
Think
you're
in
the
call
right
now
and
I.
Think
Brian
also
gave
some
feedback
to
you
as
well.
G
A
I
think
this
one
is
kind
of
important
because
as
we're
starting
to
collapse,
SIG's
into
larger
umbrella,
SIG's
that
have
many
sub
projects
and
Ethan
I
do
think
this
is
important
for
us
to
to
keep
a
hold
up
just
so
that
we
have
some
level
of
understanding
of
where
it's
at.
So,
if
people
ask
us
questions.
C
And
just
connecting
the
dots,
so
Nikita
I'll
answer
the
latest
questions
and
try
to
move
it
forward.
I,
don't
know
how
much
time
we
want
to
spend
on
it
now,
but
the
high-level
idea
is:
we
were
organizing
the
people
of
the
project
in
terms
of
SIG's
and
we're
organizing
code
in
terms
of
repos
and
sub
directories
and
owner's
files,
and
there
was
no
direct
linkage
between
the
two
and
sub
projects
are
the
linkage.
C
E
C
So
one
issue
is:
should
we
change
the
terminology
which
has
been
used,
but
someone
inconsistently
four
years
and
I'm
fine
with
that?
If
we
come
up
with
a
better
term,
another
is
do
we
need
to
find
more
roles
for
sub
projects
and
in
some
cases
the
answer
may
be
yes
depends
on
how
large
and
how
active
the
sub
projects
are
for
the
specific
proposed
duties,
I.
Think
of
that
as
more
of
project
management
like
a
lot
of
the
sub
projects,
don't
have
their
own
meetings.
C
They
just
report
back
in
the
cig
meetings,
so
I
think
in
general
they'll
be
helpful
to
take
some
of
the
learnings
from
SiC
cluster
lifecycle
and
some
of
the
other
SIG's
with
many
sub
projects
like
Cigna
working
and
try
to
distill
some
best
practices,
and
one
of
these
best
practices
might
be
certain
types
of
roles
that
the
sub
projects
should
have
and
how
they
should
report
back
to
this
thing
as
a
whole,
how
they
should
groom
issues.
Maybe
we
need
labeling
for
each
sub
projects
and
so
on.
I.
A
F
G
F
A
Yeah,
just
just
for
a
concrete
example
if
I
go
to
community
and
the
reason
why
I'm
matters
trust,
because
people
always
ask
questions
to
suit
cluster
lifecycle,
particularly
about
cluster
API
sub
project,
and
it
just
points
to
the
corners
file.
Right
and
people
need
to
know
that
there's
a
slack
channel
for
this
and
that
there
is
a
there
are
points
of
contact
that
we
can
put
inside
of
here.
Yeah.
C
B
A
A
To
do
I
think
as
long
as
the
metadata
exists
for
us
to
populate
inside
of
the
community
repo
inside
sixteen
yellow
I,
don't
know
whether
no
expert,
whether
or
not
it's
a
requirement
as
Brian,
that
should
not
call
sub-projects
meet
all
the
time
or
may
not
have
their
own
slack
channel.
So
I
don't
know
if
it's
a
requirement
whether
or
not
to
have
that,
but
so
long
as
that,
we
have
the
ability
to
add
that
field
or
set
of
fields
to
the
60ml
file.
I,
think
that
is
sufficient,
plus.
E
E
C
A
A
G
So
they
support
you,
user
groups
have
been,
has
been
added
to
six
tatiana,
so
you
can
actually
create
a
user
right
now.
There
is
a
PR
open
to
add
big
data
as
user
growth,
but
there
is
no
governance
document
for
it,
so
this
issue
is
mainly
to
process
and
how
this
is
important
instrument
for
user
base.
I.
A
C
D
C
F
C
Yeah
I
mean
whoever
pokes
that
that
should
probably
ASCII
what
is
being
done
in
that
area
and
what
the
current
status
is.
There
are
various
kinds
of
support
like
materials
they
can
use
to
present
about
different
ciencia
projects
and
I
think
the
scenes
yet
code
of
conduct.
The
event
code
of
conduct
does
apply
yeah.
A
A
Next
up
our
elections,
meta
issue,
the
reason
I
added
this
too
important
soon
the
reason
I
prioritize.
Some
of
these
things
was
because
a
we've
talked
about
it,
be
it's
been
stale
or
or
C.
We
we
took
too
long
last
time
in
the
past,
and
this
is
C.
So
I
was
wondering
whether
or
not
there
we
wanted
to
at
least
initially
assign
a
group
of
folks
to
start
thinking
about
elections
early
well
ahead
of
the
actual
election
process.
So
that
way
we
can
address
some
of
the
common
concerns
from
consider
X.
A
C
D
A
Are
there
volunteers
who
want
to
least
start
to
initially
have
the
discussions
around
this
because
last
time,
I
think
we
waited
too
long
and
I
know
that
I
got
feedback
from
Chris
rebec's
about
some
of
the
issues
that
that
they
had
run
into
along
the
way
and
some
feedback
that
they
had
gotten
so
I
thought
about
at
least
starting
the
conversation
early
and
maybe
get
some
assignees
and
then
I.
Don't
expect
that,
obviously
to
be
done
in
this
milestone,
but
at
least
to
have
the
initial
people
who
want
to
work
on
this,
assign
you.
C
A
There
are
a
couple
other
things
that
we
talked
about
recently
that
might
be
worthwhile
to
discuss
as
a
group
seeing
how
it's
drew
me
into
other
conversations
that
are
ongoing
and
other
documents
that
have
seen
flowing
through
the
CNC
f
right
now
that
the
CNC
F
Charter
is
kind
of
like
lacking
with
regards
to
other
responsibilities
that
we
see
flying
across
other
projects
and
I
do
know
that
people
are
updating
it
and
there's
a
bunch
of
documentation.
That's
in
flight
here,
but
there's
a
bit
of
open
issue.
A
We've
had
on
our
backlog
for
a
while
with
regards
to
funding
and
budgeting,
and
it's
a
very
generic
statement
which
is
like
fund
requested
and
budgeting
process
needs
formalized
to
be
formalized
and
documented.
I,
don't
know
if
there's
anyone
who's
been
involved
in
those
conversations
at
the
CN
CF
level.
That
might
also
be
interested
in
documenting
how
how
we,
as
a
organization,
underneath
the
CNC
F
sort
of
do
formalized,
requests
for
funding,
etc,
etc.
C
Yeah
I
think
we
discussed
this
at
a
previous
steering
meeting,
also
with
the
idea
that
you
know
if
it's
under
a
certain
dollar
amount,
we'll
just
let
people
directly
file
an
issue
with
the
Service,
Desk
and
otherwise
we'd
ask
them
to
bring
it
to
the
steering
committee
and
we'd
either
approve
it
or
we'd
file.
The
service
desk
issue
so
I
think
that's
the
main
thing.
C
What
this
came
out
of
originally
was
a
lot
of
people
involved
in
the
project
were
going
directly
to
people
like
Dan
in
the
scenes
yes
and
asking
for
money,
and
there
is
no
tracking
where
we
could
even
tell
what
funding
was
being
requested
and
since
they've
sort
of
consolidated
on
the
service
desk.
That
is
less
of
an
issue,
but
it
is
still
an
issue.
So
Paris
has
been
I,
think
recently
filed
a
request
for
I,
know
something
I'm
sure
and
which
is
probably
fine.
C
You
know
because,
for
example,
I
get
CCD
and
I
assume
other
steering.
Members
do
also,
when
anything
related
to
kubernetes
gets
filed
right
so
that
at
least
creates
a
notification
mechanism
and
paper
trail
where
we
can
tell
what's
going
on,
and
you
know
certainly
for
the
people
who
would
normally
do
that.
It's
a
big
ticket
item
like
tens
of
thousands
of
dollars
or
something
then
people
would
normally
ask
us
so
I
think
this
is
more
or
less
a
solved
problem,
except
it's
not
really
officially
documented.
A
Is
there
is
there
anything
related
to
hire
or
capabilities
such
as
like
automation
and
testing
things
like
the
the
slack
problem
right?
We
we
have
no
funding,
or
we
have
no
funding
to
devote
towards
development
efforts
to
do
bot
creation
and
automation.
People
are
doing
it
of
their
own
volition
right
now,
and
the
reason
why
I
put
this
on
the
near
term
to
talk
about
was
because
that
was
one
of
those
issues
where
we
don't
actually
have
an
owner
right.
C
So
Michelle
and
Brandon
gave
a
great
presentation
to
the
GB
and
TOC
on
Monday,
with
some
common
needs
of
projects
and
honestly
it
is
like
deja
vu
with
some
of
the
things
that
envoy
project
is
going
through
that
kubernetes
went
through
a
couple
of
years
ago,
so
the
visibility
of
this
is
being
raised
with
the
GB,
and
it
is
a
priority
area
of
the
TOC
in
both
Michelle
and
Brandon
are
very
active
on
that.
So
I
suggest
that
they
kind
of
be
the
point.
People
on
that
effort,
I.
F
Mean
just
to
to
put
a
finer
point
on
that
I
think
you
know
we
have
essentially
a
whole
new
TOC
of
the
CNC
F
and
there's
a
renewed
focus
in
figuring
out.
What
are
the
services
and
the
support,
materially
that
the
CNC
F
can
offer
projects,
and
how
can
we?
How
can
you
up
level
that-
and
so
you
know
it's
up
to
us,
to
figure
out
what
what
we're
looking
for
and
what
we
wanted
to
sort
of
tee
it
up,
so
that
it's
actionable
yeah.
C
The
previous
in
the
previous
to
see
most
of
the
TOC
members
were
not
directly
involved
with
foundation
projects,
and
now
that
has
totally
changed
now
that
we
have
new
people
on
board
and
Matt
is
the
first.
That
Klein
is
the
first
contributor
from
outside
kubernetes
who's
on
the
TOC.
So
he
brings
a
little
bit
of
a
separate
perspective.
I
mean
even
the
both
contributor
or
maintainer
representatives
to
the
GB,
Michelle
and
Brandon
are
both
heavily
involved
in
kubernetes.
So.
A
What
I
can
do
is
I
will
articulate
some
of
the
things
that
we
talked
about
in
this
issue
and
then
a
sign
and
talk
with
Brandon
and
Michelle
for
a
follow-up,
and
potentially
we
can
close
this
as
an
external
thing
being
done
by
the
C&C
F,
but
we
still
need
to
have
some
documentation,
at
least
on
our
site,
to
be
able
to
outline
what
is
the
the
process?
Greed.
C
A
A
This
has
been
a
legit
problem
for
quite
some
time,
and
it
was
also
a
recent
topic
in
sig
arch
with
regards
to
like
having
enough
people
working
in
a
Content
area
that
needs
help
right,
so
this
sign
has
been
open
for
a
while
says
document
resources
that
the
community
has
and
make
sure
that
they
have
a
home
release
trigger,
but
also
I
think
this
was
also
about
documenting
areas
that
need
assistance
and
how
to
when
I,
when
I
read
it
I
thought
ever
it
it
is.
We
also
need
areas
that
you
know:
how
do
we?
C
We
have
a
mechanism
now
we're
just
not
executed
exercising
it
effectively
yet,
which
is
the
role
board
for
the
project.
So
we
need
to
maybe
just
do
some
campaigning,
like
I'm
even
guilty
of
that
in
Sagarika
texture
and
we
need
to
actually
go
identify
the
work
that
needs
to
get
done
and
define
a
role
around
it
and
then
actually
try
to
solicit
help
on
the
role
board
and
then
mentor
someone
into
a
position
where
they
could
execute
on
that
yeah.
A
F
D
F
D
So
I
guess
what
I
take
from
it.
As
far
as
like
a
community
management
is
concerned,
but
like,
for
instance,
like
identifying
what
the
community
has
like
what
Jason's
pulling
out
in
the
issue,
we
definitely
already
have,
and
it's
a
major
Excel
document
that
I
can
share
with
everybody
and
that
Excel
document
is
going
to
get
turned
into
a
mega
communications
and
Dean.
A
B
B
B
B
A
D
A
D
A
A
A
A
C
So
I
Paris
commented
in
the
chat
that
context
and
networking
are
active,
I
attended.
A
recent
contributes
meeting
where
they
discussed
roles
and
contributes
I
believe
is
coming
to
city
architecture,
to
talk
about
mentoring
and
I've,
been
looking
at
the
sequester
lifecycle
practices,
I
think.
If
we
can
distill
a
few
best
practices
and
examples,
then
we
can
present
it
in
a
community
meeting
and
try
to
evangelize
it
a
little
bit
more.
A
A
A
From
find
homes
for
unknown
areas
of
the
project,
this
is
kind
of.
This
is
one
of
those
things
that
fell
into
the
languishing
category
for
a
long
time.
I,
don't
necessarily
know
if
it
needs
to
be
addressed
in
the
near
term
or
if
we
just
want
to
find
somebody
who
wants
to
start
to
tackle
these
problems.
I
think.
C
A
A
A
Just
to
give
folks
a
meta
point,
this
is
this
is
typically
how
we
roll
it's
a
cluster
lifecycle.
This
is
we
break
it
down.
We
have
a
milestone.
We
break
down
the
issues,
we
prioritize
them.
We
greet
them
and
we
constantly
iterate
on
them
and
by
doing
this
process,
we
kind
of
constantly
get
an
update,
interaction
and
roll.