►
From YouTube: CNCF TOC Meeting - 2019-09-03
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
Yeah
all
right
and
I
think
actually
before
we
start
on
to
the
agenda,
I
wanted
to
acknowledge
something
that
came
up
in
a
private
call
with
the
TRC
members,
which
is
about
the
usefulness
of
some
of
these
calls.
I,
we
haven't
figured
out
exactly
what
the
solutions
are
here,
but
I
wanted
to
at
least
acknowledge
that
yeah.
There
are
folks
who
are
seeing
this
as
not
a
great
forum
for
interaction.
I
would
like
to
encourage
more
interaction.
B
A
A
You
know
diversity
of
projects
and
so
on.
So
we
plan
on
doing
these
for
all
of
our
graduated
projects
over
time.
If
you
have
any
input
on
the
layout
of
the
report,
let
us
know,
but
we
plan
to
kind
of
use
the
kubernetes
project
journey
report
as
a
template
for
for
other
projects.
Any
questions
here,
I.
A
Could
have
to
email,
email
me
email
us,
so
the
best
way
to
kind
of
do
it
right
now.
There's
no
kind
of
you
know
issue
tracker
for
this,
but
we're
happy
to
take
suggestions
over
over
email
and
if
there's
types
of
data
that
people
want
to
see,
there's
always
Deb
stats
available,
and
you
could
file
issues
there.
If
there's
a
specific
type
of
you
know
a
piece
of
data
that
you're
looking
for.
C
I'm
gonna
insert
my
standard
grant
here
that
I
think
counting
sort
of
code
contributions,
doesn't
capture
all
activity
and
like
it's
the
thing
we
have
not
necessarily
the
right
thing
and
I.
Don't
have
a
better
idea
so
like
to
like
make
pretty
graphs,
but
it
always
bothers
me
when
we
focus
on
that
stuff.
So
you
know
in
speech
you.
D
E
I
wonder
if
there's
not
a
way
that
we
could
amend,
that
sides
may
be
distracting
everything
that
have
sort
of
an
opt-in.
I
did
other
things
in
the
sense
of
like.
Could
you
say,
hey
I
did
a
meet-up
I
mean
it's
unlevel,
it's
it's
dark,
not
accurate
data,
but
it
might
be
a
way
to
capture
some
of
the
non
github
things.
B
E
D
Mention
that
we
actually
are
working
on
the
same
challenge
right
now
for
the
CF
ambassador
program,
where
we
want
to
automatically
move
people
to
emeritus
status
if
they
don't
touch
the
community
in
four
months
or
something
so
we
are
investigating
essentially
an
API
for
some
of
those
other
engagements.
So.
F
We're
big
fans
of
dead
stats,
I
came
in
late
to
the
conversation,
but
we're
big
fans
of
dead
stats
over
the
FACA
project
and
we're
trying
to
use
it
more
to
kind
the
gauge
our
project,
health.
Of
course,
you
know
any
data
is
not
necessarily
perfect.
I,
like
the
idea
of
meetups
and
blog
posts
and
being
able
to
find
a
way
for
us
to
track
those
because
right
now
what
you
can
do
in
dev
stats
is
overlay
releases
and
so
it'd
be
really
nice.
F
B
F
A
D
D
I
B
C
Be
clear
here,
though,
well,
the
larger
question
Brian
that
we
were
talking
about
is
the
fact
that
we
focus
on
dev
stats,
because
that's
what
we
have
and
that
you
know
is
there
a
way
to
capture
a
better
picture
of
contribution
beyond
just
what
shows
up
and
github,
and
so
whether
it's
def
stats
or
something
else.
The
idea
of
having
some
way
to
track
other
types
of
day.
But
data
self-reported
or
you
know,
is
the
is
the
ongoing
discussion
here.
C
H
J
C
A
B
Be
really
interested
to
you
know,
get
a
picture
of
like
how
do
you
meet
ups
other
kind
of
activities
around
the
other
project?
You
know
we
all
probably
have
a
gut
feel
about
our
own
cities
around
kubernetes,
but
you
know
what
are
people
having
n
join
meetups?
You
know,
I
go
just
picking
a
random
project.
K
A
Yeah
there
its
survey
season
time,
so
you
know
we're
basically
doing
a
couple
things
here.
One
is
asking
for
input
from
folks
on
this
call
and
the
TOC
on
kind
of
questions.
We
ask
maintain,
errs
they're
all
on
github
now,
so
it
should
be
very
easy
to
add
or
modify
any
questions
there
and
then
we're
also
looking
to
kind
of
do
a
survey.
You
know.
G
B
B
N
N
N
Thanks
tool
is
for
kick-starting
that
initially,
so
we
got
in
total,
then
in
toto
is
primarily
done
by
just
in
Capel's,
then
just
in
Cormac
helped
out
on
that
as
well.
So
thanks
to
them-
and
it's
been
a
full-on
team
effort
of
assessment-
and
then
there
is
like
many
of
assessments
coming
through
like
opus
this
next
one
that
I
think
they
are
starting
to
take
a
look
at.
N
There
is
a
heavy
planning
for
cloud
native
security
day.
That's
going
on
kuddusi
from
sustained
kills
start
of
helping
a
shepherd.
That
thing,
along
with
amy,
has
been
tremendously
full
on
that
with
Emily
and
Emily.
So
that's
that's
as
far
as
the
activity
goes,
and
there
is
an
assessment
guidelines
that
Sarah
had
helped
Shepherd
in
craft.
It
is
it's
pretty
detailed
and
there
is
a
little.
There
is
a
lot
of
inputs
that
we
could
get
from
this
community.
This
group
in
general,
in
terms
of
Rick's,
how?
N
How
does
it,
how
to
stay
in
neutral,
while
still
being
affiliated
with
with
an
organization
I
think
the
and
neutrality
is
a
question
that
everybody
struggles
with
in
terms
of
like
wanting
to
do
the
right
stuff
versus
still
having
a
job
and
being
affiliated
with
some
company
right.
So
we've
tried
listing
out
guidelines
just
in
campuses
help
from
his
perspective
of
how
academics
do
this.
So
any
inputs
there
and
it's
it's
open
for
review,
so
I
put
the
links
there.
N
B
K
N
L
N
B
We
in
last
week's
discussion
raised
the
point
that
we
would
like
to
be
more
strategic
about
this
and
be
more
cognizant
of
gaps
in
the
landscape
and
be
reaching
out
for
projects,
rather
than
necessarily
just
taking
things
in
the
order
in
which
they
come
to
us.
So
one
of
the
things
that
we
will
expect
shortly
be
reaching
out
to
the
six
around
is
to
ask
you
to
the
prioritizing
thoughts
around
the
landscapes
in
your
areas
and
what
gaps
you
see
missing
in
those
landscapes.
B
M
O
One
of
the
one
of
the
asks
that
we
have
from
the
from
six
origins,
you
know
are
these
questionnaires
that
we're
trying
to
put
together
useful
in
recording
the
information
that
you
needs
to
help
make
you
know
sponsorship
decisions
or
you
know,
ultimately,
decisions
as
to
as
to
whether
they
join
sandbox
or
not
so
so
far.
It's
it's.
You
know
specifically
for
the
sandbox
projects.
We
need
to
put
something
else
together
for
for
incubation
projects.
O
So
I'd
love
I'd
love
to
hear
any
feedback
from
from
sort
of
team
members.
It's
to
understand
that
there,
if
they're,
finding
this
useful,
is
there
something
with
left
out?
Are
there
other
things
you'd
like
us
to
cover
when
we're
doing
reviews
with
projects
before
we
send
the
information
over
to
the
TOC?
O
We
just
started
following
the
TOC
project,
call
where
dragonfly
was
proposed
to
to
incubation
and
then
handed
over
to
the
storage
sake,
to
do
to
do
a
bit
more
of
an
in-depth
review.
We've
just
started
that
that
process.
We've
we've
had
a
project
presentation
from
the
team,
but
we
need
to
go
through.
O
We
need
to
go
through
the
process
in
a
little
bit
more
detail,
as
this
is
our
first
incubation
process,
incubation
level
project
that
we're
about
we're
reviewing
so
we'll
be
putting
we'll
be
putting
some
templates
together
around
around
that
for
for
other
incubation
projects
to
in
terms
of
contents
that
we're
putting
together
we're
putting
together
a
set
of
content
which
we're
hoping
to
launch
in
in
time
for
cube
con
in
November.
The
first
bit
of
content
is.
O
Augment
the
existing
storage
landscape
white
paper,
which
which
we
launched
at
last,
cube
con
in
that's
white
paper.
We
kind
of
covered
all
the
different
attributes
of
storage
and
various
terminologies
and
and
different
systems
from
sort
of
you
know
all
the
way
from
block
file
systems,
object,
stores,
key
value
stores,
etc.
O
But
we,
we
thought,
databases
probably
deserved
a
bit
more,
a
bit
more
focused
and
we
didn't
have
the
skills
and
team
at
the
time
to
draw
that
up,
so
we're
putting
together
a
an
update
to
the
to
the
white
paper
to
cover
the
the
database
landscape
as
well,
and
then.
Similarly,
one
of
the
one
of
the
things
that
came
out
of
the
white
paper
was
people
asking
us
about.
You
know
how
do
we
measure
the
different
attributes
of
storage
systems?
O
These
are
some
options
that
you
can
use
for
different
types
of
use
cases
or
saw
some
storage
options
that
you
can
use
for
different
use
cases.
So
the
proposal
at
this
stage
is
the
kind
of
build
out
I
get
repository
of
sort
of
marketing
documents,
peri
use
case.
That
would
cover
a
number
of
different
use
cases
and
for
each
use
case
there
would
be
one
or
more
options
of
of
sort
of
storage,
solutions
or
storage
recommendations
for
that,
for
that
particular
project
or
use
case,
and
we're
hoping
to
to
do
some.
O
O
At
the
end
of
that
we've
set
up
from
a
logistics
point
of
view,
we've
set
up
an
emailing
list
and
we're
just
porting
people
over
from
the
old
working
group
Manliness
to
the
new
CN
CF
mailing
list,
and
we've
also
spent
some
time
to
put
together
a
storage
survey
to
kind
of
help
us
guides
guide
us
in
terms
of
you
know
what
the
end
users
paying
point
so
I
would
what
information
and
users
would
would
like
to
see.
After
the
cig,
we
haven't
had
a
fantastic
response
rates
so
far
only
about
20
people
have
responded.
J
Gonna
be
a
little
bit
more
more
blunt
than
Alex
was
so
so
we've.
We
really
really
really
need
end
user
feedback
and
we
put
a
lot
of
trouble
interpreting
the
survey
together
and
we
did
go
through
the
CNC
F
in
user
groups
and
various
mailing
lists
and
the
response
rate
to
be
perfectly
blunt,
was
shockingly
low
if
you're
an
end
user
and
you
and
you
want
to
give
some
input.
This
is
a
really
good
opportunity
to
do
so
so
yeah.
Let's
please,
rally
behind
this.
E
E
B
P
Do
you
have
I
mean,
do
you
have
a
targeted
list
of
actual
individual
users
that
you
want
to
feedback
from,
because
often,
if
it's
a
personal
request,
like
you
know,
we're
specifically
requesting
feedback
from
this
particular
user?
You
know,
instead
of
a
blasts
of
trying
to
get
a
lot
that
that's
probably
more
effective
as
well
its
target,
a
few
specific
users
that
you
would
have
yeah.
J
Yeah-
and
we
didn't
do
that-
we
we
actually
discussed
this
when,
when
trying
to
sort
of
analyze
where
we
went
wrong
and-
and
definitely
you
know,
quality
rather
than
quantity
is-
is
valuable
here,
I
think
having
you
know,
a
relatively
small
number
of
high
quality
feedback
from
from
important
users
is
more
arguably
more
important
than
having
in
a
hundred
thousand
hundreds
of
of
much
more
superficial
responses
from
you
know.
Mom-And-Pop
shops,
obviously
both
available,
but
but
yeah
quality
rather
than
quantity.
I
think
is
the
key.
B
J
Just
put
a
lot
of
effort
into
that
sorry,
Alex
I
didn't
mean
to
hijack
your
presentation
feel
free
to
take
over,
but
yes,
we're
into
figuring
out
how
to
you
know,
be
able
to
analyze
the
data
afterwards.
So
so
you
know
how
big
is
your
company?
What
what
kinds
of
things
are
you
using
or
all
that
kind
of
stuff,
is
in
the
survey,
so
the
intention
being
that
we
can
differentiate
the
big
users
from
the
small
users
and
the
experienced
users
from
the
inexperienced
users
etc.
Great.
C
So
a
couple
of
things
I
mean
you
know
looking
through
these
and
I'd
love
to
hear
what
the
other
TOC
members
think
I
think
having
some
sort
of
qualitative
judgments
on
stuff,
like
I,
think
you
know
across
a
couple
of
different
lines.
You
know
in
terms
of
you
know,
do
we
feel
like
this?
Is
you
know
an
architecture
that
has
legs?
Do
we
feel
like
this?
Is
you
know
how
cloud
need
a
visit?
How
much
of
a
gap
does
it
fill?
C
You
know,
community
I
think
we
can
find
a
bunch
of
different
sort
of
qualitative
things
to
actually
ask
and
talk
about.
Obviously,
you
know,
as
you
move
from
sort
of
you
know,
data
to
sort
of
analysis
and
opinion
things
get
a
little
bit.
Hairier
and
I
think
you
know
it
gets
harder
to
be
candid
about
that
stuff.
But
from
the
TOC
s
point
of
view,
that's
you
know,
that's
the
real
expertise
there
versus
just
looking
at
collecting
facts.
O
Understood
so
so
we
thrive,
so
we
try
it's
so
the
first
three
projects
we
looked
at
where
our
sandbox
projects
so
we'll
be
trying
to
capture
where
things
like
how
its
fit
in
with
other
CN
CF
projects.
Is
it
sort
of
deployed
in
a
client
native
way,
and
also
there
were
a
bunch
of
questions
to
help
with
sort
of
IP
policy
type
decisions
like
you
know:
where
are
the
Reapers?
What
licenses
do
they
have?
Are
there
tests
processes
in
place
and
all
that
kind
of
stuff?
So
I
completely
agree?
O
We
we
we
we
do
need
to
have
more
qualitative
information
or
judgments
in
there,
especially
as
we
go
into
into
reviewing
creation
level
projects.
I
think
that
the
bar
was
obviously
a
little
lower
for
the
sandbox,
but
yeah
we
can.
We
can
definitely
add
more
of
that.
That's
a
great
point,
thank
you,
and.
C
Then
what
comment
on
the
whole
end-user
survey
in
engagement,
just
in
general,
I,
think
you
know
people
respond
to
these
things
when
they're
unhappy
I
mean
there's,
definitely
a
bias
towards
that
I
mean
there's
a
lot
of
like
most
people
using
open-source.
It
works
fine
for
them.
They
never
bother
talking
to
anybody
and
so
I
think
a
big
part
of
this
is
how
do
we
make
people
care
and,
like
you
know,
you
can
always
give
them
free.
C
Q
Q
Away
something
and
whatever
motivates
people
I
just
feel
like
we
don't
get
enough
visibility,
maybe
from
storage
as
well.
Maybe
maybe,
if
we
had
a
user
group,
something
else
that
if
anyone
else
had
it
on
the
scene,
see
if
this
tried
to
do
a
survey
and
had
better
luck
than
we
had
luck
here.
What
we
use
to
make
that
happen,
I
think.
C
Especially
like
sakes,
it's
especially
hard
because
it's
not
a
single
project
and
I
think
you
know,
users
definitely
feel
affinity
to
projects
more
than
they
do
to
the
CN
CF
in
general,
and
so
you
know
maybe
finding
ways
to
actually
you
know
have
the
projects
you
know
activate
their
communities
to
spread
this
stuff
around.
Instead
of
just
focusing
on
sort
of
the
CNCs
community.
P
And
one
thing
I
would
like
to
see
in
Iran
in
a
you
know
in
all
these
types
of
surveys
is
some
type
of
net
promoter,
score
product
recommendations
for
kind
of
questions,
to
get
a
little
bit
of
that.
Give
that
qualitative
thing
that
you're
talking
about
Joe?
Is
you
know
how
likely
would
you
recommend
this
to
a
you
know
to
a
friend
or
a
colleague
kind
of
question?
I
mean
we
found
that
a
lot
in
in
and
just
and
user
products?
P
P
You
wind
up
getting
a
a
score
like
like
50
or
34,
or
negative
10,
and
it's
it's
a
it's
a
trailing
indicator,
but
it
gives
you
an
idea
of
how
you
know
just
how
how
over
all
you're
doing
you
know
how
useful
this
particular
project
or-
or
you
could
even
ask
this
in
the
maintainer
survey
as
well-
not
might
be.
Might
feedback
on
the
maintainer
survey
is
like
you
know
how
like
how?
J
Jeff
one
one
keV
it
they're
just
we
did
bear
this
in
mind
when,
when
putting
that
some
of
those
surveys
together,
but
we
have
in
the
past
seen
you
know
competitive
projects
and
competitive
products,
you
know
bad-mouthing
their
competitors
in
those
kinds
of
forums,
so
we're
certainly
very
careful
what
we
use
that
data
for
and
and
how
we
interpret
it
and
to
what
extent
we
can
actually
mitigate
those
kind
of
things,
because
there
is
a
lot
of
potential
for
misinformation
there.
If
we're
not
careful.
B
So
now
you
need
to
take
myself
off
meat
and
Alex.
I
also
noted
your
question
about
more
broadly
whether
the
TOC
field,
that
the
sinks
are
providing
this
with
useful
information,
I'm
going
to
note
that-
and
it's
probably
something
some
people
would
rather
discuss
offline
and
consolidate
thoughts
and
rather
than
thinking
out
loud.
So,
yes,
I,
think.
R
Hello
mat
foreigner
you're
on
too
right.
Yes,
I
am
yeah,
so
we
want
to
give
our
our
annual
update
on
the
project.
Matt's
gonna,
kick
it
off
by
just
sharing
kind
of
the
current
overview
of
the
project
and
then
I
will
go
into
the
status
of
the
project
and
tell
you
about
some
of
the
things
we're
really
excited
about,
and
then
we'll
kind
of
wrap
up
by
talking
about
how
we
are
on
the
status
of
graduating
from
incue
bation.
So
go
ahead.
Matt
all.
S
Right
so
under
the
helm,
github
organization,
we
actually
have
about
20
active
projects.
Now
this
ranges
from
the
helm,
client
to
helm
hub
and
the
software
powering
it
to
charts
and
then
a
number
of
supporting
projects
to
help
make
everything
work
of
that
we've
been
looking
at
the
contributors
in
just
the
past
year
and
we
pulled
these
numbers
from
dev
stat.
S
It
came
in
at
over
700
companies
contributing
to
helm
one
of
the
numbers
that
we
we
saw
Rison
when
we
switched
over
to
get
not
home
dot
SH.
That's
the
new
download
location
where
you
can
get
the
helm
binary
from
is
we
have
eight
hundred
and
seventy-five
thousand
downloads
a
month
is
what
it's
saying
right
now
and
this
is
globally
and
the
biggest
reason
was
the
US
and
we
think
the
biggest
growth
region
is
China.
S
When
we
first
launched
the
betas,
we
had
a
large
download
contingent
coming
from
China
for
the
helm,
v3
betas,
which
was
a
fantastic
thing
to
see
the
previous
download
location
that
were
migrating.
Everyone
off
from
was
in
Google's
cloud
in
a
bucket,
and
it
was
back
from
when
helm
was
part
of
kubernetes
before
the
CNC
F
existed.
So
it's
a
really
old
bucket
and
that's
obviously
not
available
in
China,
and
so
when
we
first
saw
lots
of
Chinese
downloads
coming.
S
It
was
really
incredible
to
see-
and
this
is
also
I-
went
back
and
I
looked
at
numbers
from
about
a
year
ago
for
home
downloads,
and
this
is
up
about
50%
on
monthly
downloads
from
a
year
ago,
and
then,
of
course,
homebrew
format
gives
us
some
wonderful
statistics.
You
could
go
digging
for
them
and
we
have
about
85,000
installs
a
month
over
and
home
bro,
which
was
another
nice
statistic
to
see.
S
Now
these
numbers
are
not
pulled
from
the
helm
global
because
they're
built
by
homebrew
and
cached
in
their
own
system,
and
so
this
is
an
entirely
separate
installation
set.
Can
you
go
to
that
site
Thanks
when
it
comes
to
charts?
We
have
about
300
main
chain
charts
in
the
chart.
Repository
we're
slowly
migrating
everyone
over
to
self
hosting
their
charts.
So
that
way,
the
charts
maintain
errs,
don't
get
in
the
way
of
the
development
cycles
or
merging
it.
S
There's
there's
actually
a
lot
going
on
there
and
so
we're
trying
to
get
set
up
folks
to
be
able
to
be
self-sufficient
with
that,
and
so
the
helm
hub
is
a
place
where
they
can
list
their
charts.
They
can
be
publicly
searchable,
and
so
we've
had
some
of
the
charts
go
inactive
and
become
deprecated,
because
people
are
hosting
their
own
and
so
we're
we've
got
about
300
maintained,
charts
in
the
chart
repository
right
now
that
the
community
is
maintaining
and
numerous
charts
have
moved
over
to
be
maintained
by
organizations.
S
R
R
Beta
3
is
due
out
this
week
and
unless
the
blood
count
is
low
enough,
that
we
actually
go
to
rc1
this
week,
so
we're
very
very
excited
about
the
the
tremendous
amount
of
work
that's
gone
on
in
home
3
over
the
last
month
or
so
to
really
kind
of
batten
down
the
hatches
and
get
that
closed.
The
very
last
lingering
DEET
of
the
transfer
of
all
the
IP
over
to
CN
CF
was
the
trademark
on
the
helm,
logo
and
that
was
transferred
over
finally
about
two
weeks
ago.
R
So
we
believe
we
are
completely
done
on
all
the
IP
transfer
work
and
then
next
week
we
are
super
excited
because
helm
summit
is
happening
in
Amsterdam.
So
a
big
group
of
the
core,
maintainer
x',
will
be
heading
out
there
late
this
week
early
next
week
to
meet
with
people
all
from
all
over
Europe
helm.
R
The
three
is
due
for
its
final
release,
so
that's
helm,
300
late
in
September,
we're
excited
about
using
helm
summit
is
basically
a
way
for
us
to
to
collect
a
lot
of
last-minute
kinds
of
opinions
and
and
tests,
and
things
like
that
from
people
in
the
community,
and
then
we
should
have
hung
three
out
in
plenty
of
time
to
talk
about
it
at
coop,
con
and
cloud
native.
So
and
then.
Finally,
the
one
thing
we
couldn't
quite
schedule.
The
way
we
wanted
was
the
security
audit.
We
couldn't
quite
get
the
audit
in
before
helm.
R
Threes,
final
release,
however,
we
do
have
it
scheduled,
so
the
security
audit
will
be
done.
We'll
kick
off
the
the
official
process.
We've
already
met
with
the
security
researchers,
but
we'll
kick
off
the
official
process
early
in
October
and
I
believe
the
audit
itself
begins
somewhere
around
is
that
the
14th
or
15th
mat
that
it
officially
kind
of
I.
Don't.
R
I,
don't
remember
if
we
have
an
exact
date
on
that
one:
okay,
you
can
move
on
to
the
next
one.
We
are
excited
one
of
the
things
we
really
wanted
to
do
with
the
release
of
helm,
3
was
to
do
a
branding,
update
the
helm,
logo
and
design
design
has
remained
largely
unchanged
since
we
introduced
it
at
the
very
first
coup,
Khan
and
Ronin.
Our
designer
took
the
opportunity
here
to
make
up
a
bunch
of
changes.
Important
to
us
was
a
change
in
color
scheme.
That
brings
us
closer
to
the
CN
CF
color
scheme.
R
We
wanted
to
very
much
indicate
to
the
community
visually
the
transfer
of
everything
from
the
older
kubernetes
org
into
the
CN
CF
org
Vernon's
done
a
great
job,
assembling
a
style
sheet
and
there's
a
link
down
there
at
the
bottom
or
you
can
go
and
check
out
the
new
logos
fonts.
Any
official
usage
guides
on
everything.
R
Okay,
so
graduating
from
incue
bation
is
one
of
our
major
goals.
Right
now,
so
we've
been
carefully
going
through
all
the
steps
we
need
to.
We've
got
multiple
companies
contributing
as
matt
shared.
We
have
passed
at
silver
level,
the
best
practices
audit
we
have
had
code
of
conduct
and
governance
talks
and
a
logo
wall,
and
all
that
kind
of
stuff
around
for
a
long
long
time.
So
really
we're
down
to
just
the
security
audit
is
our
last
major
milestone
before
we
can
consider
beginning
the
process
of
the
toc
vote
for
graduating
from
incue
bation.
R
So
we're
really
excited
about
all
of
that.
If
there's
any,
if
anybody
has
guidance
or
or
advice
that
you
want
to
share
offline
or
some
in
slack
or
something
on
making
sure
that
any
of
these
other
ones
that
we
think
are
checked
off,
actually
need
a
little
more
work.
Please
share
that
with
us.
We'd
like
for
this
to
be
as
frictionless
as
possible.
R
R
Perkins
has
been
helping
out
a
lot
on
helping
us
revise
the
helm,
documentation
and
we're
excited,
because
this
new
change
in
the
documentation
opens
us
up
to
being
able
to
do
internationalization
very
easily,
which
is
good
because
in
the
past,
like
the
Chinese
localization
has
been
done
entirely
in
China
by
Chinese
engineers
and
is
exposed
through
their
own
websites.
Now
we'll
finally
be
able
to
roll
some
of
that
back
into
the
official
documentation.
R
The
newly
structured
documentation
resembles
the
way
that
it
was
done
with
with
kubernetes
itself,
and
so
we're
very
happy
about
that,
because
it's
important
to
us
to
have
parity
with
the
rest
of
the
ecosystem,
so
I
think
that's
all
we
have
on
the
agenda
today.
We're
really
excited
about
the
status
of
things
and
optimistic
about
the
what's
really
an
extraordinary
community
that
has
collaborated
with
us
to
get
this
long
transition
from
home
to
to
helm
three
done.
B
Guess
I
kind
of
have
a
question
and
it
might
actually
be
something
that
we
unfortunately
skipped
over
at
delivery
and
we'll
come
back
to
them
and
I'm
not
sure
whether
this
is
a
question
for
helm
at
delivery
or
both.
What
other
mechanisms
are
people
using
when
they're
not
using
helm
and
what
proportion
do
we
think
of
users?
I,
don't
know
quite
how
to
measure
this
you
know
are
using
helm
to
deploy
their
applications
so.
T
At
least
I
think
the
answer
and
the
other
one.
Yes,
there
should
be
a
question
for
AB
delivery.
Do
we
have
to
answer
this
question
now?
I
think
we
should
exactly
be
part
of
the
work
that
we
were
engaging
with
right
now,
because
application
packaging
and
management
is
is
one
of
them
and
that's
like
one
of
the
topics
we
should
be
discussing
as
of
today.
I
can't
provide
an
answer
given
that
we
were
just
formed
last
week,
so
so.
R
We
have
some
preliminary
indications
that
we're
not
sharing
publicly
but
that
we've
seen
install
for
helm
for
tiller
in
helm,
2
at
somewhere
pushing
70
percent
of
production
grade
clusters,
with
no
attempt
to
capture
what
development
clusters
look
like
and
that's
about
the
best
we
can
do.
We
haven't
really
tried
to
kick
off
any
sort
of
formal
thing.
We've
just
done
some
some
audits.
C
Real
quick,
sorry
I
think,
as
we
see
helm,
3
make
its
way
to
production.
I'd
love
to
break
out
some
of
these,
like
logos
and
usage
numbers
across
helm,
2
and
hump.
3
really
understand.
You
know
how
fast
of
an
uptake
are
we
talking
for
for
how
three
and
I
think
you
know
you
know,
especially
considering
you
know
the
security
audit
I,
assume
it's
being
is
being
run
against
help
three
is
that
is
that
the
case?
Yes,.
L
C
Just
don't
want
users
to
be
confused,
that
hey
we're
giving
helm
three
a
blessing,
but
then
we're
you
know
confusing
that
with
home
too
and,
like
you
know,
they're
very
different,
you
know
architecture
ISM,
you
know
obviously
all
have
been
super
super
hard
at
work
at
helm,
three
but
I
think
really
understanding
sort
of
the
the
uptake
and
and
making
sure
that
that
there's
no
confusion
there
does
that
make
sense.
Yeah.
S
And
and
given
that
the
release
of
helm
three
is
coming
in
the
fall
right
and
there's
a
lot
of
people
use
this
in
companies
and
things
like
that
going
into
the
holiday
season.
I
will
be
curious
to
see
how
the
uptake
is
both
before
and
during
the
holiday
season
versus
afterwards,
when
people
have
a
chance
to
breathe,
depending
in
some
of
these
organizations.
So
I
don't
know
if
we
should
expect
a
massive
uptake
just
given
the
time
of
the
year
and
the
kinds
of
changes
people
make
it
that
time
of
year.
S
C
B
T
Okay,
we
just
got
Michelle,
has
posted
slides
so
just
very
quickly
updated.
The
sig
was
just
formed
last
week,
so
not
a
lot
of
extra
work
to
report
on
just
very
high-level,
absolutely
see
it's
working,
that's
what
the
name
indicates,
everything
from
an
end
user
perspective,
the
deals,
mr.
delivery
of
applications
always
tell
native
applications,
everything
from
like
design
considerations,
but
big
topic,
being
packaging
delivery
of
applications,
testing
operations,
pretty
much
everything
you
have
like
all
of
these
projects
available
and
I
want
to
start
build,
run,
manage
your
applications.
How
do
you
do
it?
T
T
We
had
our
charter
defined
so
far.
First
officer's
meeting
with
in
September
11th
goal
as
a
first
step,
really
formal
landscapes
back
to
your
questions
list.
What
do
people
use
instead
of
helm
covering,
is
always
in
the
broader
scope
for
all
of
the
other
areas
where
it
makes
sense
that
we're
touching
which
tools
are
out
there?
B
Super
excited
to
see
lacking,
you
know,
coming
into
place,
that's
fantastic!
That's
our
third
seek,
seek
provisionally
entitled
core
and
applied
architectures
and
then
there's
a
draft
hot
off
the
presses,
a
draft
that
Quinton
and
others
have
been
working
on
so
I'm
sure
they
would
welcome
input
into
that
document.
U
V
Yeah
I'll
just
jump
in
here
for
everyone
who
doesn't
know
we
just
select
the
chairs
for
state
absolutely
a
Louis
just
so
Brian
miles
and
we
from
Alibaba
are
our
three
chairs
and
if
you
want
to
get
involved,
this
is
a
great
time
to
do
so.
Since
we
just
completed
the
formation
stage,
please
join
our
mailing
list
and
we
have
meetings
every
other
Wednesday,
like
Ellis,
mentioned
we're
also
organizing
to
meet
at
coupons.
So
lots
of
really
good
things
to
look
forward
to.
Thank
you.