►
Description
Kubernetes Public Steering Committee Meeting for 20221205
A
A
A
B
A
A
So
the
sorry,
the
cat,
the
the
one
of
the
biggest
issues
that
we've
had
with
the
annual
reports
previously
has
been
like
templating
things
out
everyone's
filling
out
stuff
differently
and
without
subbing
things
out.
A
lot
of
things
get
missed,
and
it's
also
a
big
headache
on
us
to
put
things
together
when
we're
trying
to
assemble
the
giant
report.
A
But
even
outside
of
you
know
that
report
and
everything
it
is
probably
time
to
at
least
start
paying
the
leads
to
have
them.
You
know
start
thinking
about
things
that
they
might
want
to
put
in
there
we
sent
a
or
we
set
a
General
reminder
in
the
last
chair
and
TL
meeting,
but
I
think
it's
time
for
us
to
reach
out
to
our
various
sigs
as
Liaisons
to
just
start
like
pinging
them
like
hey,
just
a
reminder,
start
thinking
about
this.
A
It's
it's
going
to
be
coming
up
then,
as
far
as
the
tools
go,
something
we
have
been
talking
about
with
our
contributes
hat
on
is
potentially
X.
We
have
some
we're
running
a
leadership
cohort
right
now
for
new
chairs
and
TLS,
and
potentially
pulling
some
of
them
in
to
help
with
the
task
of
improving
the
tooling.
B
C
D
B
A
A
B
E
A
E
E
E
E
G
Mentioned
this
yeah
I
was
gonna,
say
in
a
burn
like
I'll,
be
taking
point
on
that
one
and
I'll
I'll.
We
can
speak
with
the
the
rest
of
the
cohort
and
stuff
about
that.
But
yeah,
that's
that's
one
thing:
I
I
definitely
want
to
try
and
help
push
forward
because
having
the
generator
last
year
made
a
big
difference,
but
there's
still
a
bunch
of
gaps
where
it
could
do
a
whole
heck
of
a
lot
better.
E
So
the
tooling
apart
since
we
have
a
very
strict
timeline,
can
we,
before
everyone
goes
out
on
vacation
at
least
start
over
with
the
issues
in
k,
Community
for
the
reports
and
start
bringing
our
license
six
and
working
groups,
at
least
to
the
initial
round
of
things
before
the
vacation
and
then
expect
and
then
come
back
from
the
vacation
and
then
ask
people
like
hey?
Did
you
have
a
chance
to
talk
about
it?
If
not,
please
do
in.
A
G
A
Okay,
are
there
there
any
other
annual
report?
Let's
see,
do
we
get
the
same
questions
for
the
report
right
now?
Yes,
it's
mostly.
We
want
to
stub
out
a
lot
of
the
things
that
was
a
lot
of
hand
like
people
having
to
go
generate
their
list
of
caps
put
stuff
in
there
and
and
things
like
that,
I,
don't
think
our
questions
are
going
to
be
changing
too
much
from
last
year,
because
we
already
paired
them
down
significantly
Kristoff.
G
A
Yeah
I
would
say:
yes,
it's
it's
revisiting,
so
we
do.
We
steering
collectively
also
want
to
take
the
AI
say
by
the
end
of
the
week,
or
you
know
this
time
next
week
to
at
least
look
at
the
Retro
and
review
the
questions
to
see.
If
things
are
good,
that
way,
we
can
sort
of
give
the
heads
up
to
our
sigs
that
hey
any
reports
are
coming
up
and
then
at
least
have
have
sort
of
the
the
idea,
the
the
at
least
the
questions
we
want
to
ask.
A
A
A
A
H
H
It's
about
basically
the
signature
for
binaries
for
Mac
OS.
So
we
talk
about
this
in
May
and
it
was
like
legalized
related
to
this,
and
it
came
out
back
last
week
during
relationship
with
this
meeting.
So
asking
again,
if,
like
there's
an
update
about
this,
do
I
needed
do
we
need
to
do
something
so.
A
C
Well,
we'll
try
to
check
in
on
it
yeah
we'll
check
in
on
it,
because
we
have
a
we
have
an
AI
for
it.
We
also
need
to
I
would
say,
on
the
Sig
release
side,
we'll
plan
to
check
in
with
Muhammad
who
has
been
working
on
some
of
the
the
sick
release
case
in
for
stuff,
because
I
believe
he's
set
up
a
workflow
for
binary
signing
on
on
the
K
native
side.
H
H
How
we
get
that
account
is
now
we
can
as
I,
don't
I
think
last
time
we
we
said
something
about
not
basically
not
allow
individual
get
the
account
so
I'm
like.
If
steering,
can
request
to
cncf
to
ask
to
Linux
foundation
and
talk
to
Apple
about
this,
we
can
try
to
get
that
and
unblock
release
engineering.
C
Yes
and
part
of
yeah
part
of
what
I
was
was
the
reason
I
mentioned
the
the
K
native
stuff
is
they
may
have
gone
through
exactly
this
kind
of
scenario,
figuring
out
the
individual
versus
so
I'd
like
to
to
sync
with
Mohammed.
First,
at
least
on
the
Sig
release
side,
we
can
chase
it
on
the
cncf
side
too,
but
there
is.
There
are
questions
around.
You
know
that
the
the
the
the
the
the
company
account
group
account
organization
account.
What
have
you
may
be?
G
G
D
B
So
I
just
I
dropped
a
link
in
to
the
the
Apple
developer
program,
enrollment,
where
it
gives
some
information
on
individuals
and
organizations
I'm
or
Stephen
had
mentioned
like
we
may
have
to
be
a
legal
entity.
It
gives
some
words
around
what
that
is,
and
to
me
I
mean
not
a
lawyer,
not
a
apple
certified
developer
anymore
I
think
I
used
to
have
one
of
these,
but
plain
English
of.
B
What's
on
that
page
reads
like
something
that
could
not
apply
to
kubernetes
today
and
would
have
to
come
from
the
cncf,
so
I
I
think
we
need
to
go
talk
to
the
cncf
about
that,
and
also
it
is
part
of
what
is
in
the
cncf's
charter.
This
is
going
to
be
something
new,
but
it
starts
to
feel
like
what
Apple
might
require
from
us
here
is
that
the
cncf
runs
a
signing
service
for
its
project
binaries.
B
B
A
A
F
We
had
to
go
through
something
related
to
this
for
the
registry,
because
we
kind
of
inherently
collect
like
any
anything
that
we
log
as
all
the
traffic
is
coming
in
it
is.
It
is
for
anybody
using
the
Upstream
distro.
It
sort
of
is
a
a
live
endpoint
that
they're
all
pulling
from,
and
we
have
a
past
history
with
people
analyzing.
F
This
data
I
wasn't
involved
at
that
point,
but
it
might
be
worth
following
up
with
Kate's
infra
how
the
pii
analysis
was
done
for
determining
like
which
six
or
which
companies
were
driving
the
traffic.
That
sort
of
thing
I
believe
that
was
done
with
II
Co-op
and
like
they
had
some
kind
of
agreement
to
access
the
data
as
cncf
contractors.
F
D
H
I
think
the
real
issue
here
is
where
to
store
the
data,
because
you,
if
they
use
the
third
party
to
store
that
data,
then
we
need
to
check
the
privacy
policy
related
to
that,
but
collection
is
related
to
is
covered
by
Linux
Foundation
privacy
policy.
Now,
where
we
keep,
that
data
is
like
a
different
conversation,
I
think
this
is
the
one
thing
we
need
to
share.
A
G
Is
this
something
that
we
even
want
to
get
into
like
I
I
understand
from
a
very
high
level
like
looking
at
the
issue
wanting
to
know
whether
certain
drivers
and
stuff
can
be
deprecated,
but
I
would
question
if
this
is
a?
If
this
is
a
topic
that
as
an
open
source
project,
we
ourselves
want
to
get
into
because
there's
just
as
soon
as
you
start.
G
So
like
that
that'd
be
at
least
the
question
that
I
would
just
in
general
throughout
there
is
like
is
telemetry
a
thing
that
we
want
to
even
get
into
as
an
open
source
project.
Is
this
something
that
we
want
to
invest
in,
especially
considering
mini
cube,
is
saying:
look
we
don't
really
want
to
invest
in
making
a
framework
for
for
Telemetry
collection
of
storage?
We
would
just
be
a
consumer
of
it.
G
A
C
A
C
F
You
and
Tim
hockey
would
know
more
about
that
I
mean
so
I
I.
Having
worked
on
a
very
similar
tool,
I,
don't
think
that
I
will
just
make
it.
Pluggable
drivers
is
a
super
great
answer,
and
that
will
be
a
lot
of
work
and
make
it
a
lot
actually
make
it
harder
to
maintain,
because,
like
the
interface,
what
you
need
across
those
things
isn't
necessarily
stable.
I.
F
Do
think,
though,
that
if
you
look
at
the
rest
of
cluster
life
cycle,
they've
relied
on
polls
and,
and
that's
one
potential
answer,
but
I
had
some
sympathy,
for
there
are
a
number
of
reasons.
It
would
be
really
useful
to
let
a
component
like
this
phone
home,
a
common
one
I
get
when
trying
to
fund
work
on
like
kind,
is
attempting
to
qualif
attempting
to
quantify
how
much
usage
it
has,
which
is
really
hard
when
people
are
doing
things
like
go,
get
or
Homebrew
or
whatever
I.
F
Don't
have
a
good
way
to
get
an
idea
like
how
many
users
it
actually
has
and
doing
things
like
sending
out
a
poll
doesn't
really
give
you
the
that
that
picture.
So,
besides
deprecation
like
for
a
couple
of
these
projects,
I
know
right
now,
they're
going
through
Staffing
questions
on
the
Google
side.
For
this
project
having
having
metrics
is
one
way
that
some
other
open
source
projects
are
able
to
like
show
their
success,
and
we
wouldn't
I
mean
we
certainly
wouldn't
be
the
first
open
source
project
with
something
like
this.
F
For
example,
if
you
wanted
to
know
at
the
core
level,
you
could
look
at
something
like
the
image
pulse
for
the
container
images
and
see
like
which
are
most
heavily
used,
or
something
like
that
and
like
that.
Data
is
available
and
we
have
looked
at
it
before,
but
we
don't
have
this
for
some
of
the
other
projects.
B
F
E
F
B
A
Like
if
you
know
the
the
project
or
the
subproductive
owners,
aren't
necessarily
distorts
of
the
data
like
if
the
the
cncf
LF
is
willing
to,
you
know
be
sort
of
that
entity
that
holds
it,
you
know,
and
they
have
their
privacy
policy
and
everything
there
I
think
there
would
be
a
bit
more.
You
know
trust
in
it,
especially
if
there
was
like
a
nice
codified
way
of
like
requesting
this
in
the
future.
B
C
B
Documentation
on
where
the
data
is
held
and
stewarded
and
if
ultimately,
the
output
is
a
public,
anonymized
and
useful
piece
of
data,
aggregation
I
think
that
there
are
plenty
of
places
in
open
source
where
this
seems
to
be
happening
and
people
appreciate
it's
not
just
instantly
like
pitchforks
and
Flames
like
oh,
my
gosh.
This
is
terrible,
there's
a
huge
benefit,
especially
for
something
our
size
and
complexity.
To
being
able
to
get
this.
A
H
I
think
I
think
there
is
I,
don't
I,
don't
want
to
say
ultimate
answer
to
discussion
more
like
what
exactly
they're
trying
to
collect,
because
if
they're,
basically
trying
to
collect
information
back
downloads,
versioning
and
stuff
like
that,
I
think
it's
fine.
But
if
we
end
up
in
a
situation,
they
basically
try
to
collect
personal
information.
It's
different
conversation
because
they're
also
the
perimeter
of
gdpr
in
light
European.
My
want
to
request
pulling
out
the
data
from
that
data
set
they're
trying
to
build.
A
A
F
I
mean
you
still
have
to
be
careful
because
for
a
platform
like
this
to
work,
to
collect
things
like
downloads,
you're-
probably
going
to
want
to
look
at
some
kind
of
identifier
just
to
duplicate
the
data,
so
you
do
still
need
to.
We
do
still
need
to
consider
all
this
I
think
it's
worth
asking
the
Linux
Foundation.
If
they
have
any
precedent,
they
have
a
lot
of
sub
projects.
F
It's
the
policy
to
the
user,
but
it
doesn't
cover
things
on
the
implementation
end
of
like
you
know
how
long
should
we
retain
data
or
like
should
we
have
a
mechanism
for
purging
or
there's
some
mentions
of
like
you
know
how
Europe
views
us
data
collection
like
do
we
have
to
make
sure
that
European
users
have
their
data
stored
out
of
it?
This
is
where
I
think,
probably.
Actually,
instead,
like
some
off
the
show
platform,
another
thing
that
came
to
mind
is
I.
F
F
So
if
there's
something
like
that,
where
can
deem
that
this
is
approved
and
just
say
you
know,
here's
what
you
use
and
how
you
use
it
that
that
seems
like
a
fair
ask
but
I
feel
like
we
should
probably
go:
ask
the
Linux
Foundation
to
cncf,
because
we
we
can't
be
the
first.
This
can't
be
the
first
ask
yeah.
A
F
Yeah
and,
and
also
just
to
clarify
what
we've
been
doing
at
the
registry
so
far
with
the
current
work,
we're
just
not
doing
any
permanent
stories.
We
have
like
ephemeral,
log
storage
and
you
could
pull
pii
from
that.
But
I
think
at
some
point.
We'll
want
to
do
more
permanent,
like
analysis
again
like
I
did
previously
and
I
I
wouldn't
know
how
to
advise
the
group
on
doing
that,
because
I
don't
think
we
have
strong
enough
policies
outlined
on
they're,
actually
doing
it
site,
as
opposed
to
like
here's
the
contract.
F
Right
so
right
now
we
can
only
use
those
logs
for
like
debugging.
We
don't
actually
use
them
for
analysis
at
the
moment
and
when
we
want
to
do
something
like
that
again
in
the
future,
I
think
we'll
have
to
be
careful.
This
kind
of
policy
and
I'm
sure
the
Project's
going
to
want
to
do
that
down
the
line.
C
A
H
A
B
But
I
don't
know.
Perhaps
I
know
that
I
understand
I
have
some
type
of
a
backlog
established
of
features.
What
was
present
for
the
project?
Isn't
anything
we'd
particularly
use
at
the
moment,
but
maybe
this
is
something
that
we
could
feed
there
as
a
abstracted
requirement.
They,
they
have
a
huge
platform
of
tooling
that
they're
trying
to
integrate
and
to
live
project.
Telemetry
data
feels
like
it
would
be
a
useful
part
of
that
and
the
LFX
platform
already
has
to
deal
with
privacy
and
pii.