►
From YouTube: Kubernetes Public Steering Committee Meeting 20200302
Description
Kubernetes Public Steering Committee Meeting
A
A
Let
me
go
ahead
and
share
my
screen
so
that
for
those
that
don't
have
the
agenda
in
front
of
them,
you
can
have
it
virtually
in
front
of
you
and,
as
always,
we
do
have
a
code
of
conduct.
Please
be
excellent
to
each
other.
We
have
looks
like
twelve
participants
now
so
sort
of
a
large
group.
Try
to
either
use
the
hand,
hand
raise
feature
or
just
try
to
call
out
and
I
will
get
to
you.
Also.
There
is
an
agenda
if
you're
just
joining
us
in
chat.
A
Let
me
read
a
copy
and
paste
that
please
feel
free
to
add
your
name
as
a
community
member
also
staring
at
our
names.
I,
don't
know
if
I
added
mine
and
let's
hit
it
so
first
up
today
is
Zack.
Zack,
has
a
cap
open
and
has
some
open
questions
and
discussion
for
us
Zack
when
I
give
us
some
context
absolutely.
B
Thank
you
for
having
me,
so
this
is
in
reference
to
the
kept
for
third
party
and
dual
source
documentation.
The
issue
number
is
13
to
7
and
crouppen
eddie
/
enhancements.
I
had
a
chat
window
one
second
ago.
I
need
to
exit
the
seven
full
screen
right.
I've
put
the
link
in
to
zoom
chat,
so
this
campus
had
90
days
for
discussion,
and
that
feels
like
a
really
good
amount.
B
B
Also,
we
have
some
DVDs
in
the
kept
that
we
need
to
resolve
and
I
think
some
of
these
may
be
either
like
edge
cases
that
are
specific
to
Docs
or
maybe
more
common
I'm,
not
familiar
with
the
larger
landscape
of
caps,
but
our
TVB's
are
specifically
around
approvers
reviewers
and
editors
they're.
The
cap
template
specifies
that
approvers
should
be
different
from
authors.
B
C
C
Feel,
like
I
mean
it's
it's
your
call.
A
call
for
folks
listed
as
authors
have
had
authorship
in
the
doc.
That's
one
way
to
do
it.
You
can
also
say
that
somebody
from
cig
Doc's,
who's
kind
of
been
just
editing
it
or
you
intend
to
have
them.
Keep
this
kept
up
to
date,
going
forward
with
you.
That
would
be
the
person
I
would
choose.
C
D
D
If
there's
any
ambiguity
around
like
project-wide
technical
decisions,
then
sig
architecture
should
definitely
be
involved,
otherwise,
like
stuff
around
Docs,
specifically
and
like
policies
around
documentation
and
the
website
amount
kind
of
stuff
might
like
at
least
my
personal
opinion
is
that
we
take
the
lead
for
what
from
what
sig
Docs
is
recommending,
because
you
folks
are
definitely
the
the
experts
in
that
domain
and
have
been
running
or
Doc's
and
our
website
for
a
while.
Now.
B
C
Well,
I
yeah,
we
go
jumping,
say
arch,
so
he
wants
to
be
listed
as
an
approver
and
or
a
viewer.
If
you
can't
find
anybody
there
come
pumping
me
and
I
can
sign
up
to
be
a
reviewer,
because
I
appreciate
you've
had
this
out
here
for
a
while
and
want
to
make
sure
that
we
help
you
move
forward.
Expediently.
B
The
timing
lines
up
nicely
within
the
next
few
weeks.
One
of
the
provisions
of
the
cap
is
that
we
give
all
feature
owners
of
current
documentation
that
would
have
non-conforming
content
in
it
90
days
to
migrate
their
content
elsewhere
or
decide
what
to
do
with
it
and
lining
that
up
with
the
end
of
a
release,
cycle
dovetails
nicely
with
like
one
dot,
one
dot
19.
A
Does
anybody
else
have
anything
for
Zack,
either
from
steering
or
members
of
the
community,
all
right
all
right
and
then
the
next
item
on
the
list
is
steering
a
cube,
Conn
updates.
So
we
have
our
panel
and
I've
heard.
We've
heard
from
a
few
of
us
that
are
no
longer
going
so
I
wanted
to
see
a
panel
still
liable
for
us,
which
we
do.
I
gave
us
ten
minutes
to
discuss.
In
case
we
decided
to
scope
creep
into
cube
con.
D
D
Alas,
I
heard
on,
like
you
know,
like
last
I
heard
it
was
a
maybe
but
I,
don't
know
if
that
has
changed
to
either
like
a
firm,
yes
or
a
firm
no
as
of
today,
but
right
now,
if
a
panel
at
the
best-case-scenario,
if
a
panel
is
DIMMs
and
me
I,
there
is
significantly
less
value
to
that.
There
would
have
been
if
we
had
like
five
of
the
seven
steering
members
in
Amsterdam,
which
is
what
the
plan
was.
As
of
you
know,
a
few
weeks
ago,.
E
D
If
it's
just
me,
then
I'm
going
to
make
the
decision
and
say
that
that
is
definitely
not
valuable.
If
you
want
to
talk
to
me,
pinion
slack
I'm,
very
open
about
my
thoughts
and
opinions
and
having
conversations
pick
me
and
slack.
If
you
want
my
opinion
on
something
or
ask
it
here
is
another
good
option.
As
far
as
Amsterdam
I
think
we
can
safely
say
like
we
should
cancel
that
session.
All.
A
A
H
H
That
was
my
proposal.
We
got
pretty
good
amount
of
support,
and
so
the
event
sub
project
leads
are
going
to
be
getting
a
lovely
github
issue
assigned
to
them
stating
as
such
with
my
proposal.
This
is
not
something
that
I
do
lightly,
but
I
had
to
merge
my
personal
and
professional
opinions
and
now
I'm
not
going
to
answer
damn
either.
So
just
just
want
that
out.
There.
H
I'll
grab
a
link
to
my
proposal.
I
will
paste
it
in
here
for
all
of
your
lovely
eyes,
but
explicitly
it
should
go
to
the
event.
Sub
project
leads
and
I
yeah.
This
is
kind
of
a
weird
gray
area
because
this
hasn't
really
been
done
before.
So
that's
that
I
do
want
to
say
thanks
to
my
staff,
for
both
being
incredibly
open
about
their
feelings,
as
well
as
honestly
pushing
back
where
they
need
to
push
back.
So
I
am
happy
to
take
questions
about
the
ideas,
but
nothing
has
been
decided.
H
Is
honestly
again,
this
is
gray
area.
This
is
not
my
call
I
think
what
I'm
going
to
be
doing
right
after
this
is
creating
an
issue
and
assigning
it
to
the
event
sub
project
owners,
and
they
are
the
ones
that
have
to
decide
I
made
my
decision
already,
which
is
why
we've
made
the
propeller
Kai
made
the
proposal,
but
I
I
would
just
assume
it's
going
to
be
within
72
hours,
because
that's
how
things
work
around
here.
C
A
A
Yet
this
is
I'm
posing
and
quite
a
few
other
folks
on
the
line
are
in
agreement,
/ko
proposing
and
so
not
necessarily
on
me
here,
a
community
health
check
of
sorts
for
our
sakes
and
community
groups
like
other
committees,
and/or
working
groups,
things
like
that
for
various
reasons
similar
to
an
Apache
roll
call
that
they're
PMC's.
Have.
A
This
just
helps
us
check
in
on
chairs
how
they're
doing?
Also,
let's
chairs,
have
a
communication
channel
into
us
and
really
kind
of
just
open
up
some
more
communication
channels
and
seeing
how
we
a
steering
can
help
them
or
vice-versa,
etc,
etc.
Just
kind
of
like,
what's
acted
with
hey.
What's
how
do
I
do
this,
but
in
a
more
unified
fashion?
A
E
A
I
think
that
I
feel
like
our
next
steps,
would
be
just
to
put
together
a
quick
dock
of
goals
and
types
of
things,
and
then
the
mechanism,
meaning
we
go
to
them
or
they
come
to
us,
and
then
we
sort
of
have
a
level
one
program.
I,
don't
think,
there's
too
many
steps
that
we
need
to
do
to
kick
things
off.
The
ground.
I
have
also
mentioned
this
to
the
chairs
and
techniques
themselves.
Many
chairs
and
tech
leads
have
have
mentioned
that
they
welcome
this.
Others
are
just
more
concerned
about.
A
Is
this
adding
another
meeting
to
my
already
existing
calendar,
which
my
very
quick
response
was?
No,
that
was
not
the
attention.
We
already
have
a
a
meeting
here,
a
public
meeting
here
or
be
they
already
have
their
meetings.
We
can
figure
out
which
avenue
to
slot
this
into
without
creating
additional
work,
but
I
have
not
received
much
feedback
outside
so
I
feel
like
we
are
ready
to
go
ish.
If
you
will.
A
A
A
A
See
Erin
with
an
O
or
I
will
take
silence
as
a
no
all
right
and
community
members
who
are
not
interested
in
our
backlog.
This
is
I,
don't
know.
This
is
where
all
the
good
stuff
happens.
In
my
opinion,
if
you're
not
interested,
feel
free
to
drop,
otherwise,
let's
go
through
the
backlog,
all
right.
So
what
in
the
Hades
is
vol
kubernetes
and
qo
end
of
life?
Okay,
sorry.
C
Github
administration's
a
project
to
that
management,
sub-project
met
and
we
are
we're
very
close
to
having
migrated
or
retired
all
reposts
out
of
that
org,
at
which
point
we
can
decommission
the
org
the
outstanding
repos.
There
are
two
related
to
Sega,
auto
scaling
that
I
believe
are
going
to
be
in
flight
shortly.
There's
one
right
there.
C
E
So,
from
my
perspective,
I
would
weave
we
kind
of
think
that
if
a
person
really
wants
it,
they
can
take
it
out
of
the
crannies
org,
and
we
can
you
know
they
can
thicken.
They
can
be
the
maintainer,
because
they're
pretty
much
the
only
one
or
two
maintainer
that
are
actually
actively
working
with
it.
A
A
A
A
E
A
Please
we
are
sort
of
kind
of
working
on
this
right
now,
nah
nah
yeah,
not
necessarily
to
be
needed.
It's
just
kind
of
like
we
know
we
do
so
all
right,
I'll
just
go
ahead
and
leave
it
open
document
requirements,
documentation
requirements
determine
how
documentation
or
policies,
of
course,
estate
Doc's
integrate
enforcement
to
the
release
process.
E
A
C
Don't
know
that
this
has
concretely
been
addressed,
but
I
feel
like
through
the
evolution
of
caps
and
I.
Think
the
cap
that
Zak
just
submitted
kind
of
describes
how
sig
Docs
has
enforcement
for
a
particular
kind
of
content
policy
as
well
as
SATA
architectures
ridging,
you
of
caps
I,
think
we
have
the
necessary
things
that
Docs
is
like
has
the
necessary
enforcement
policies.
C
A
A
A
A
A
A
C
K
K
I'd
like
to
present
right
now,
I,
don't
know
what
pissed
off,
but
I
think.
This
is
like
a
very
long
widen
minded
discussion
that
we
should
take
to
a
country
that's
meeting
instead,
because
there
are
lots
of
folks
who
have
shared
opinions
on
this
and
I
think
it
should
be
on
the
call.
Also
I
was
like
a
dog
written
and
everything's
I
think
we
should
have
those
talk
authors
to
discuss
this.
A
A
A
K
A
A
A
A
K
K
A
A
J
C
I
A
A
E
A
You
know
mine
was,
and
all
I
did
was
just
take.
What
we
do
for
like
the
community
meeting
and
like
it
was
like
Matt
and
I,
like
Mad
Libs
did
pretty
much
like
so
yeah
I'll.
Send
it
to
you.
I'll,
take
that
offline,
but
I,
think
and
I
am
pretty
sure
in
the
in
the
in
the
host
instructions.
I
have
that
they
need
to
clear
the
comments.
So
are
we,
okay
with
closing
this.
A
A
K
E
Didn't
it
was
a
topic
that
we
wanted
to
record
this
meeting.
I
didn't
have
strong
opinions,
just
the
topic
that
was
brought
up.
I
I'm,
not
a
big
fan
separating
out
a
separate
consecutive
term
limit
from
the
left
internal.
It
I
think
lifetime
term
is
sufficient
in
my
opinion,
but
I
do
think
that
other
folks
should.
A
K
I,
don't
really
have
objections
in
the
lifetime
term
of
ten
years,
but
I
think
we
should
think
about
having
a
consecutive
term,
though
I
don't
have
too
strong
opinions
right
now.
I
just
feel
like
that.
Could
help
improve
the
like
diversity
in
genre
on
the
steering
committee,
but
I
need
to
think
more
on
this.
D
A
A
A
G
D
A
C
A
E
A
A
And
then,
as
but
as
far
as
like
future
and
I'm,
trying
to
think
a
future
like
this
year,
for
instance,
when
we
have
new
folks
come
on
board,
is
that
what
we
should
do?
Every
time
like,
we
should
just
open
up
these
like
onboarding
kind
of
issues
which
we
do
as
far
as
process
is
concerned,
for
that,
what
did
we
decide
on
I?
Think
Nikita?
You
also
I
think
you
may
have
either
PR
some
of
that
stuff.
In
already.
K
A
A
E
E
A
K
C
C
E
According
to
like
how
we
define
the
organizational
structure
like
a
while
ago,
a
part
of
us
creating
that
original
organizational
structure
was
just
so
that
we
could
find
a
happy
landing
zone.
So
we
did
you
know,
projects
didn't
want
to
just
all
come
to
the
case.
Org
we've
never
done
that.
Curation.
A
E
For
them
to
address,
do
you
think
a
steering
committee
members
should
be
on
point
to
help
drive
this
boards.
Somebody
who
interfaces
more
often
I
think
Dean's
is
a
good
person,
maybe
he's
not
here
and
someone
who
goes
to
both
state
arch
and
has
been
working
on
pruning
things.
I
don't
know
if
anyone
else
is
interested
in
this
I
can
assist,
but
I
can't
take
lead.
A
A
I
For
most
I'll
actually
defer
to
you
George
a
lot
of
us,
we
did
sort
of
hold
our
own
little
retro.
It
was
captured
on
a
retro
dock
and
I.
Think
all
the
items
have
been
completed
on
that,
except
for
possibly
one
that
was
having
a
really
style
checklist,
but
overall
I
think
it's
like
the
the
a
ice
court
had
been
done.
Yeah.