►
From YouTube: CNCF TOC Meeting - 2019-03-19
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
A
A
Cool
we'll
get
started
and
we
have
a
fairly
you
know
somewhat
packed
agenda
today.
We're
gonna
be
welcoming
some
new
toc
members,
notifying
folks
about
a
chair
election
that
will
hold
now
that
we
have
a
full
toc
roster,
we'll
discuss
kind
of
the
project,
presentation
meetings
that
happened
last
week
and
how
that
went
talked
a
little
bit
about
CN
CF
cigs.
We
have
a
annual
review
presentation
from
the
spiffy
community
since
it's
about
a
year
since
they
entered
the
sandbox
and
then
we'll
kind
of
open
up
for
any
community
discussions,
backlog,
etc,
etc.
A
So,
let's
get
going
next
slide
Taylor.
So
just
the
heads
up
on
some
new
projects
that
have
entered
the
sandbox,
both
Brigade
and
cube
edge,
came
in
so
great
to
see.
Those
come
in
I
kicked
off
the
vote
for
creo
to
enter
incubation
this
morning
and
we're
still
waiting
on
a
little
bit
more
due
diligence
on
OPA
before
moving
to
an
incubation
vote,
so
I
think
we're
waiting
on
mr.
Brendan
burns
to
put
in
his
due
diligence
there,
and
anyone
in
the
community
is
welcome
to
provide
input
there.
If
they
have
had
success
using
OPA.
D
E
D
A
Go
next
slide
most
important
news.
So
we
have
two
new
TOC
members
that
have
joined
us
today.
So
Liz
rice
has
come
on
board
and
has
taken
Kelsey's
slot
after
he
stepped
down
due
to
commitments
and
then
Michelle
nur
Ali
has
taken
the
TOC
selected
slots.
So
I'm
super
excited
to
welcome
them
both
and
I've,
been
really
think
of
Kelsey
and
Quinton
for
all
the
kind
of
amazing
work,
they've
done
and
I've
added
them
to
the
emeritus
thing.
F
Thanks
Chris
yeah
hi
I
am
this
is
Liz.
I
am
super
excited
to
be
part
of
this
I,
because
I've
inherited
Kelsey's,
chair
I
have
somewhat
less
than
a
year
and
I'm
quite
keen
to
make
sure
that
you
know
things
have
happened
in
that
slightly
less
than
a
year,
so
yeah
I
hope
that,
with
the
rest
of
the
amazingly
smart
people
on
this
team,
we
can
make
some
things
happen.
As
far
as
the
TOC
is
concerned,
I'm.
G
Also
really
excited
to
be
here
so
yeah.
Thank
you.
Everyone
for
the
opportunity
I've
been
hanging
out
doing
CNCs
stuff
for
a
few
years
now,
and
so
I
just
feel
really
grateful
for
to
be
a
part
of
this
particular
group
of
people
and
I
think
I'm,
most
looking
forward
to
the
CNC
f6
and
that
being
formed.
I
think
that's
gonna
provide
a
great
venue
for
a
lot
of
really
interesting
conversations
around
cloud
native
sac,
so
just
really
pumped
thanks.
A
Awesome
glad
to
have
you
both
just
an
order
of
kind
of
governance
related
things.
We
are
seeking
nominations
for
the
TOC
chair,
which
will
close
at
the
end
of
this
week
and
then
we'll
do
the
formal
election
I
believe
Liz
and
mr.
Joe
betta
has
volunteered.
So
if
there's
any
other
TFC
members
that
are
interested
and
that
slaw
feel
free
to
make
a
comment
on
on
the
issue
posted
supposed
to
blow
cool
next
slide.
Just
reminders
on
our
wonderful
cute
cons
coming
up.
A
So
Barcelona
is
the
one
that's
kind
of
immediate
on
attention
that
everyone
should
look
at.
We
published
this
schedule,
which
is
great
thanks
for
your
patience
on
there
and
it
was
a
little
bit
delayed,
but
it's
a
bits
packed.
Some
sponsorships
are
available
towards
the
end
of
this
month
and
now
terms
of
attendance,
we're
tracking
for
probably
somewhere
around
a
little
over
10,000
folks
attending,
which
is
a
little
bit
wild
we
had
about
3,000
or
so
signed
up
before
the
schedule
was
Eva
was
even
live.
A
So
after
that
we
have
China
and
North
America
coming
up.
So,
if
you're
very
interested
feel
free
to
reach
out
and
we're
happy
to
have
a
conversation
around
any
views
bets
next
slide.
Another
kind
of
shameless
final
call
for
summer
code,
if
you're
interested
in
mentoring
projects,
we
have
an
amazing
kind
of
set
of
ideas
already
there,
but
if
you're
interested
feel
free
to
reach
out
to
me
or
me
or
anyone,
that's
part
of
the
JSOC
admin
list
slide.
A
So
you
have
project
presentations,
so
we've
recently
moved
to
this
model
where
every
second
Tuesday
of
the
month
we're
kind
of
going
through
the
backlog.
Last
week
we
had
a
three
present
project
presentations,
which
kind
of
worked
pretty
well
I,
don't
know
how
people
feel
about
it,
but
I
think
it
kind
of
went
pretty
well.
We're
gonna
continue
to
do
this
if
there
are
particular
projects
that
the
TOC
wants
to
see
slotted
for
the
next
one
around
next
month.
H
Yeah
crystal
I
was
just
wondering
I
think
we
originally
planned
to
do
this
every
other
week
as
all
the
in-between
weeks
between
the
TOC
meetings.
My
thinking
is
that
we've
got
a
ton
of
existing
projects
up
for
annual
review
and
they've
got
an
additional
backlog
of
you
know.
Projects
wanting
to
come
in
so
I
think
we
probably
need
two
of
these
a
month,
not
one
the
general
consensus.
I
don't
want
to
overload
everyone
with
presentations
either
I
think
we're
gonna
end
up
with
this
never-ending
backlog.
Again,
I.
F
A
You
you
could
build
that
basically
from
if
you
go
to
the
github
repo
for
the
CNC,
f
TOC
and
if
you
look
they're,
basically
all
the
sandbox
projects
and
their
entry
date,
you
could
kind
of
see
when,
when
they're,
when
they're
due
I,
don't
think
we're
too
crazy
for
the
next
few
months.
Maybe
maybe
a
couple
but
I'll
see
if
I
could
kind
of
go
build
out
that
that
list.
A
H
A
I
Yeah,
my
feeling
is
that
if
we,
if
we
do
a
bunch
of
presentations
where
we're
just
never
going
to
get
to
any
of
the
other
work
that
we
would
like
to
do
so
I
think
my
personal
preference
would
be
to
try
to
do
the
project
stuff.
Probably
async
like
is
it
possible
that
we
could
look
through
github,
PRS
and
different
Docs,
and
then,
if
people
feel
that
we
that
we
need
a
presentation,
we
could
do
one
yeah
I.
A
F
I
I
mean
that's,
that's
that's
my
feeling.
Is
that
I
think
if,
if
people
would
have
presented
previously,
we
could
just
ask
them
to
send
us
collateral,
whether
that
be
slides
or
a
doc
or
or
a
github,
PR
and
then
I
think.
Maybe
there
could
be
some
some
reasonable
review
period
where
we
look
at
everything
and
then
you
know
if
it
seems
like
we
want
a
presentation,
we
could
ask
for
one
I.
G
Can't
wait,
Quentin
is
saying
I,
just
think
that,
maybe
for
the
time
being,
we
should
continue
one
meeting
a
month
since
I
mean
for
me
I'm
still
getting
on
board
and
I
know.
There
are
several
other
new
members
on
the
TOC,
so
I
would
love
to
revisit
this
idea,
maybe
like
next
month
or
the
month
after
once,
we've
got
her
feet,
wet
Liz,
I
cut
you
off
apologize,
no.
I
C
Actually
I
was
just
going
to
second
Matt's
idea,
because
I
think
when
we
faced
a
similar
situation,
the
steering
committee
was
chartered.
This
sort
of
divide
and
conquer
approach
works
pretty
effectively
for
burning
down
the
back
load
of
big
charters,
and
you
know
yes,
we
won't
get
a
presentation
from
every
project,
but
that's
it's
probably
better
that
we
don't
have
that
and
we
cover
the
backlogs
and
we
wait
for
nine
months
together.
The
backlog,
the.
I
E
I
could
chime
in
I
think
it's
really
important,
though,
that
we're
communicating
to
these
projects
just
because
I've
had
a
couple
projects
that
have
been
in
the
queue
close
to
nine
months
and
they're,
reaching
out
weekly
every
two
weeks
wondering
what
is
going
on
and
I.
Don't
think,
that's
a
good
spot
to
put
a
lot
of
these
projects
in
and
this
weird.
What
are
we
waiting
for
we're
on
the
backlog?
Are
we
ever
gonna
get
scheduled?
E
You
know,
I,
think
it's
only
fair
that
if
we
don't
feel
like
some
of
these
projects
are
going
to
be
reviewed,
that
we're
prompt
about
letting
those
people
know
we're
asking
them.
You
know
for
more
information
upfront
and
trying
to
get
them
on
a
schedule,
so
they
understand
where
they
stand,
because
that's
just
been
my
feedback
I've
gotten
from
a
couple
different
projects.
They
feel
like
they're
kind
of
just
hanging
out
waiting
and
they
don't
know
what's
going
on
so
maybe
we
could
improve
our
communication
out
to
those
people.
H
H
Last
very
brief
comment,
so
it's
because
I
was
the
one
who
put
the
proposal
forward
to
to
have
these
meetings.
The
intention
is
not
that
there
be
mandatory
for
all
TRC
members
or
anything
like
that,
that
they're
just
a
forum
where,
if
people
want
to
find
out
about
a
project
that
is
wanting
to
get
into
the
CNC
F
they
they
there
is
a
place
they
they
happen.
H
If
the
TOC
member
or
anyone
else
in
the
community
is
interested,
they
attend
that
meeting
and
if
not,
they
don't,
and
obviously,
if
there's
a
TRC
member
who
would
really
like
to
find
out
and
interact
with
the
team,
they
can.
Just
you
know
request
that
that
that
presentation
be
postponed
until
some
date
when,
when
they're
able
to
attend
so
yeah,
don't
think
if
this
is
extra
workload,
its
its
additional
optional
information
available
to
everyone
and
they're
all
recorded,
so
you
can
watch
them
afterwards
as
well.
A
Alright
okie
dokie:
let's
move
on
on
this
topic,
CN
CF
cigs,
just
a
reminder
that
the
vote
is
out
really
looking
forward
to
kind
of
getting
this
improve
than
just
a
reminder
that
will
be
bootstrapping
this
process,
with
kind
of
the
governance
security
focus,
stick
who's
kind
of
been
a
great
kind
of
beta,
slash
pilots
kind
of
customer
for
this,
so
vote
is
out
to
check
out
the
CN
CF
TOC
mailing
list,
for
it
so
keep
going,
go
and
alright.
Now
we
have
the
annual
review
for
one
of
our
sandbox
projects.
A
A
B
This
star,
six,
okay,
calm.
B
Everybody
I'm
the
car
I'm
driving
like
that
I'm
happy
to
talk
to
who
talks
with
the
slides
and
give
you
guys
all
quick
up
dawn
on
the
15
spire
projects.
I
can't
this
wise
I
can
go
by
slide
number
number
five
numbers
symbolize
516
to
the
O,
3
slide
and
I'll
start
from
there.
So
as
a
reminder
for
those
of
you
who
are
new
to
the
scene
staff
around
necessarily
reading
attention
to
the
world
of
authentication
security.
In
this
case
you
have
certificates.
B
Fire
are
two
who
project
lucien
staff
that
are
designed
to
effectively
provide
and
promote
a
way
to
secure
identify
software
services,
integrated
emic
and
heterogeneous
environments.
Spiffy
this
two
levels
ban
across
the
board
is
really
a
set
of
specifications
right
and
it's
actuated
within
within
three
elements.
First,
is
something
that
alleged
fine.
You
know
how
is
serve
especially
identify
yourself.
You
call
that
it's
machete
second,
is
a
way
to
encode.
Those
IDs
do
some
sort
of
graphical
EP,
verifiable
documents.
We
have
two
forms
of
that.
I
B
Spire
is
the
one
people.
Mutations
are
stiffy,
basically
losted,
it's
those
three
standards
and
lets
you
actually
do
something
with
those
in
an
environment
without
having
to
do
too
much.
Whichever
the
say,
some
of
these
cases
that
come
up
are
inspired
by
the
areas
of
sure
I've
been
efficient,
the
most
services
another
one
that
showing
up
a
blast
here.
B
A
Think
we
lost
SUNY
illness
going
a
little
crazy.
D
D
B
B
Location
here
yeah,
so
let
me
go
to
slide
17,
which
is
the
timeline
slide.
So
if
you
remember
from
the
time
that
we
brought
this
project
in
the
history
of
spooky
inspire,
it
can
be
routed
back
to
almost
2,000
to
go
back
to
some
of
the
work
that
was
happening
inside
of
plan
9,
which
was
in
Bell
Labs.
A
lot
of
the
learnings
that
I
think
community
has
thanks
to
work.
My
job,
ADA
and
others
stems
from
the
initial
implementation.
B
If
you
go
to
the
next
slide,
you'll
see
that,
since
that
time,
we've
had
really
interesting
uptake
in
terms
of
our
overall
community,
we've
got
four
or
three
two
participants
in
the
slack
Channel.
Not
all
of
them
are
actively
participating
day
in
and
day
out,
but
yeah.
We
are
seeing
slow
and
steady
up
into
the
right,
both
in
terms
of
active
participants
as
well
as
active
messaging
across
the
board.
How
our
community,
our
conversation
happens,
is
one.
B
We
have
a
mailing
lists,
I'd
be
used
to
excuse
to
hackle
documents
or
to
communicate
face
to
people
at
yours
because
I'd
say
would
you
think,
like
most
in
a
day,
is
happening
inside
of
slack
and
work?
It's
pretty
excited,
in
particular
by
the
most
recent
uptick
in
activity.
So
it's
going
to
slide
slide.
B
19
you'll
see
that
across
the
board-
and
this
is
just
a
representation
of
some
of
the
companies
that
have
really
been
jumping
in
here,
including
Square,
VMware
uber
in
particular,
Tulio
Pinterest,
a
few
others
who've
all
showed
up
and
have
been
spending
time
with
the
project
I
tried
to
understand,
you
know
how
can
they
actually
align
their
use
cases
with
what
these
building
blocks
allowed
for
them
to
do
inside
their
organizations?
All
some
organizations
like
Pinterest
are
very
much
the
mindset
to
be
able
to
stare
eyes
around,
especially
in
this
50
identity
format
itself.
B
They
already
had
the
machinery
and
the
equipment
to
be
able
to
do
secure,
authentication
based
on
technology
that
they've
been
working
off
the
last
number
of
years.
Other
organizations
like
swear
an
uber
are
looking
at
being
able
to
replace
the
existing
forms
up,
services
system,
authentication
across
infrastructure
all
along,
and
so
what
that's
translating
into
is
just
a
myriad
of
capabilities
that
are
finding
its
way
into
both
the
standards
and
sniffy,
as
well
as
within
the
open-source
code
base
and
self
inspires
a
whole.
B
You
know
the
numbers
of
these
projects
in
terms
of
stars
and
commits
and
contributors.
These
are
nice.
These
are
interesting.
We're
working
very
hard
as
community
continue
to
continue
to
drive
that
we
become
really
just
one.
We've
always
been
fairly
disciplined
in
terms
of
how
we
engage
our
community.
B
We
have
regular
community
days,
one
Supporter
now
to
bring
the
community
and
together
the
next
one's
happening
in
May
and
so
being
able
to
use
that
as
a
way
to
continue
to
promote
not
only
spiffed
inspire
but
to
promote
Jason's
ecosystem
of
technologies,
whether
it's
public
or
anything
else
in
between
top
and
notary
and
things
of
that
sort.
So
we've
been
pretty
excited
by
and
a
pull
from
other
communities
got
into.
B
You
know
learning
more
about
if
you
inspire
as
a
whole,
if
you
go
to
the
next
slide,
slide
number
20
to
see
here
some
of
the
features
that
we've
been
working
on
as
a
community.
So
on
the
left
side,
what
we
consider
to
be
some
of
that
the
core
building
blocks
of
spire
from
the
codebase
as
I
as
I
mentioned
before
John
as
a
as
a
transport
mechanism,
is
something
that
came
about
very
early
on.
A
lot
of
folks
said
that
we
needed
a
mechanism
Cypress
5:09,
that
a
lot
for
you
know.
B
These
guys
then
needs
to
find
their
way
through
some
sort
of
a
middleware
surprise
when
there's
an
hie
way
or
load
balancer,
something
along
those
lines.
So
very
quickly
heard
that
to
move
forward
and
build
out
the
stack
as
well
as
implementation,
support
with
inspires
infrastructures,
a
hold
work
board,
API
work
to
use
to
develop
we're
working
with
a
number
of
participants
on
that.
B
So
we're
pretty
excited
about
some
of
the
work
that
we've
seen
as
well
as
some
of
the
foundational
engagement
from
our
partners,
like
Google
from
thought
work
so
as
a
consultancy,
who's,
bringing
a
lot
of
companies
into
the
fold
and
teaching
them
about
what
the
value
of
inspire
is
and
there's
a
lot
more
down
the
path
as
well,
and
we
working
to
on
the
left.
On
the
right
hand,
side
you'll
find
basically
a
listing
a
snapshot
from
our
website
about
the
number
of
plugins.
B
So
as
you'll
remember,
one
of
the
key
features
of
spire
is
the
fact
that
we've
built
very
extensible
fairly
easy
to
consume
plug-in
framework
that
allows
for
people
using
spire
to
write
their
own
plugins.
So
if
you
want
to
be
able
to
do
no
activation,
if
you
want
to
be
able
to
use
your
own
upstream,
CAS,
can
one
use
your
own
key
management
systems
or
going
use
your
own
back-end
data
store.
B
B
I
expect
to
see
more
happening
on
the
world
of
CAS,
in
particular,
I
expect
to
see
more
happening
in
the
world
of
more
traditional
identity
and
access
management
systems
as
well.
You've
got
a
number
of
folks
in
between
the
asking
us
about
our
ability
to
plug
into
technologies
like
verify,
cyber-ark
and
octa,
and
others
along
those
lines
that
are
already
embedded
within
the
large
enterprises.
Oh,
so,
we
expect
to
see
more
work
coming
with
those
communities
over
the
coming
year
as
a
whole
if
you
go
to
the
next
slide.
B
Lastly,
just
really
kind
of
you
know
focusing
on
our
roadmap
over
the
next
year.
Yeah,
you
can
read
a
slide
for
yourself
and
I.
Want
you
the
details
there,
but
it's
just
going
to
be
a
very
great
year
for
us
to
start
sorry
way
to
kind
by
Barcelona
just
happening
in
just
a
few
months.
Yeah
I
believe
five
presentations
from
side
to
and
from
other
community
members,
including
uber
and
others.
Talking
about
the
work
that
we're
going
to
be
doing
around
skippy
inspire.
B
Some
of
that
work
is
going
to
be
highlighted
around
things
like
high
availability.
We've
already
got
each
a
built
in
in
terms
of
being
able
to
run
multiple
servers,
fire
service
deliver,
but
we're
looking
at
beyond
that
we're
looking
at
load
testing
we're
looking
at
kind
of
integrations
with
systems
like
this
view
as
well.
We're
also
looking
at
trying
to
make
spire
just
a
heck
of
a
lot
more
turnkey
with
kubernetes.
B
We
had
quite
a
bit
of
pee
back
in
q4
last
year
about
the
fact
that
our
documentation
or
examples
our
libraries
were
really
not
well
built
for
somebody
who
was
struggling
through
nineties
and
once
we
started
with
inspire.
We
took
that
as
a
challenge
and
over
the
last
two
and
a
half
months,
but
turn
through
and
really
been
a
180
in
terms
of
our
footprint
controlling
the
story
of
how
to
people
how
to
help
people
use
communities
inspire
us
all.
B
Most
folks,
don't
and
most
folks
shouldn't
really
act
right
and
so
I
think
what
we're
really
hoping
to
do
is
work
with
the
community
to
build
more
examples,
to
build
more
case
studies,
to
build
more
webinars
and
to
continue
to
drive
and
showcase
why
this
is
support
not
only
for
their
infrastructure
but
had
they
moved
towards
the
cloud
native
growth.
So
with
that
I'll
put
put
myself
on
pause
and
happy
to
take
any
questions,
anybody
might
have.
B
Right
now,
but
I
hope
you
can
hear
me
right
now-
the
production
users
that
we
have
closest
to
this.
Yes,
we
expect
you
people
to
organizations
by
actually
three
organizations
by
q3
of
this
year
to
be
moving
into
to
be
moving
into
production.
I
want
to
share
those
names
caught
yet
because
I
don't
want
to
set
those
expectations
for
them.
B
Well,
I'm
not
here
to
tell
you
guys
that
we're
all
ready
to
go
and
that's
fires.
If
you
are
ready
to
make
their
move
forward,
we're
not
we're
still
building
our
community.
It
is
nice
to
see
the
progression.
It
is
nice
to
see
the
engagement.
We
still
have
a
lot
more
work
to
do
to
get
this
into
the
hands
of
more
production
environments.
All
are.
J
B
Think
a
service
that
comes
about-
and
this
might
be
a
broader
conversation
with
other
projects
that
are
not
necessarily
backed
by
a
larger
enterprise
and
large
enterprise
footing-
is,
you
know,
there's
always
war
around.
How
do
you
make
this
content
accessible
to
audiences,
right
and
so
part
of
it,
for
us
is
getting
our
getting
the
opportunities
to
work
with
great
technical
writers
going
to
work
with
great
content
producers,
whether
it's
video
or
audio,
and
just
trying
to
promote
more
of
the
story
through
better
storytelling
in
the
whole
storytelling
is
hard
and.
G
B
Expensive
for
the
best
ones
out
there
and
so
opportunities
where
we're
able
to
tap
into
the
sea
MGF
collectively
I
know,
there's
a
service
that
has
a
lot
of
great
features
which
we
have
been
taking
advantage
of,
but
particularly
around
the
storytelling
nature's.
When
icons
and
marketing
the
project
a
material
way
would
be
helpful.
Now.
I
understand
that
yeah
we're
we're
a
sandbox
project
means
a
sandbox
project.
B
J
B
Yeah
I
think
some
of
the
feedback
that
we're
looking
for
is,
if
we
build
interconnect
this
between.
You
know
the
de
ciencia
project,
so
this
is
one
set
of
organizations
they're
really
being
able
to
showcase
and
have
engagement
with
more
of
the
broader
swath
of
kubernetes
users.
Now
we
might
have
a
bit
of
a
mismatch
right.
The
kubernetes
user
base
might
be
different
than
those
that
are
looking
at
inspire,
Oro,
Pacific
right,
but
I
think
being
able
to
have
different
vantage
points
through
which
people
can
give
us
feedback
on
50
inspiring
its
accessibility.
B
You
know
what
does
specially
inspired
me
to
music
urban
entities
or
what
does
it
mean
to
me?
Is
it
gr
pcs,
or
what
does
it
mean
to
me
as
a
as
a
as
a
you
know,
as
a
as
a
top
or
a
notaries,
er
I,
think
being
able
to
have
perspective
from
different
communities
means
the
project
is
always
helpful,
but
then
again
we're
one
of
melts
and
multiple
projects
in
here
and
so
I'm
not
going
to
say
here
that
you
know
we
have
the
exciting.
B
You
know
the
time
to
be
able
to
work
with
all
them,
but
kubernetes
as
a
community
is
a
first
community.
Among
you
know
the
others
in
this
in
this
ecosystem,
I
think
it's
one
where
we're
looking
to
actively
engage
way
more
because
of
apart
the
work
we've
done
over
the
last
quarter
as
a
community,
but
also
because
we
think
there's
a
lot
more
to
go
beyond
that
as
well.
So.
B
Have
yeah
so
we
in
2018,
we
spend
quite
a
bit
of
time
working
in
concert
with
what
was
happening
in
cigars
around
trying
to
identify
mechanisms
around
you
know
workload,
identity
that
was
going
to
be
needed
to
not
only
schematics
but
also
useful
tissue
and
useful
off
of
communities
as
a
whole.
I
think
that
there's
there's
a
wiggle
room
and
space
for
you
know
different
ideas
to
exist
in
there
as
there
should
be,
but
it
seems
as
though
you
know
aiming
what's
up
with
our
project.
B
We've
had
to
focus
much
on
on
really
kind
of
driving
where
a
lot
of
the
interest
had
been,
which
you
know
for
the
most
part
of
2018
until
we
started
hearing
about
this
is
a
back
half
of
18
I'd
really
been
coming
off
of
committees,
and
so
that's
where
a
lot
of
our
effort
and
time
was
spent
really
optimizing
around
what
50
was
and
what's
fire
needs
to
be
able
to
deliver
for
per
se.
That
said,
though,
I
think
it's
a
great
opportunity
for
us
to
reengage.
B
That
group
I
think
there
might
be
some
some
learnings
there
and
someone
is
both
ways.
Even
with
this
year,
for
example,
I
think
we
can,
we
went
down
to
Google
about
a
month
ago
or
so,
and
we
had
great
conversation.
I
think
you
know,
both
of
us
were
heads
down
working
on
our
projects,
and
we
picked
our
heads
up
for
an
hour
and
a
half
and
really
gosh.
You
guys
are
doing
this
and
doing
this
thing,
there's
just
so
much
more
overlap
in
terms
of
the
world
and
rather
than
create.
G
First
of
all,
I
really
enjoyed
your
presentation.
I
feel
like
you're,
saying
all
the
right
things
and
focusing
on
really
awesome
things
like
working
on
community
building
and
making
your
Doc's
more
approachable
and
going
in
depth
and
having
these
conversations
with
its
potential
end
users
and
kind
of
seeing
what
features
thoughts
they
need
at
all
sounds
great
I'm.
Just
really
curious.
I
actually
talked
to
some
of
the
house.
She
core
people
about
how
and
why
they
ended
up
using
I.
G
B
Yeah
cool
it's
nice
to
meet
you
by
the
way
we
never
met
before
Matt
nice
to
meet.
You
I
see
the
communities
that
we
have
engaging
with
us
that
the
personas
inside
organizations
that
show
up
and
I'm
curious
about
to
expire.
Let
me
give
you
one
one
way
of
looking
at
segmentation.
You
have
a
lot
of
organizations
that
a
lot
of
startups
probably
are
not
finding
their
way
to
do.
Speaking
per
se.
B
I
think
that
for
many
folks,
stiffie
as
a
concept
is
particularly
valuable
and
particularly
useful
when
you
are
a
hybrid
cloud,
adopter
of
some
form
or
fashion,
if
you're
born
in
Amazon
or
if
you're,
born
in
Google,
if
you're
born
in
Azure
the
tooling
the
security
you
know
constructs
for
the
most
part
are
good
enough,
I
think
for
a
lot
of
folks,
so
we're
not
seeing
that
kind
of
engagement.
Just
you
know
the
honesty
and
fear
of
complete
transparency.
B
We're
not
seeing
that
kind
of
engagement
from
those
sorts
of
teams
in
part,
because
this
isn't
a
high
order
bit
for
them
to
worry
about
where
we
do
have
engagement
is
in,
let's
call
it
to
costs
of
a
large
enterprise.
One
is
all
called
nouveau
enterprise
organizations
that
are,
you
know
less
than
15
20
years
old.
B
Management
engineering
teams
start
to
show
their
wear
and
tear
a
little
bit,
and
so
we
oftentimes
will
find
ourselves
engaging
with
folks
that
are
in
those
two
types
of
organizations
currently
explain
to
them.
How
we
look
at
spiffy
inspire
as
a
potential
next
step
in
your
journey,
as
you
become
a
cognitive
organization
as
a
whole.
Now
you
brought
up
kasha
Corp,
which
is
you
know
in
all
these
organizations
that
we're
talking
to
some
great
company?
It's
great
piece
of
technology
around
balls,
specifically
here,
but
I.
B
Think
one
of
the
things
that
we
hear
from
folks
is
this
idea
that
we
want
to
evolve
beyond
the
model
of
utilizing
some
sort
of
a
secret.
You
recognize
that
secrets
are
important
and
they
are
the
way
in
which
we
do
business
today,
but
I
think
when
people
look
at
PKI,
they
look
at
it
as
a
black
box.
They
look
at
it
as
a
dark
art.
B
It's
completely
accessible
and-
and
you
know,
could
never
possibly
utilize
this
thing
at
scale
and
I
think
when
they
look
at
50
inspires
anything
realize
that
there
is
a
lot
here
to
offer.
There's
a
lot
in
terms
of
being
able
to
use
if
you
aspire
conjunction
with
Faulks
today,
trying
to
be
able
to
deliver
value
for
near-term
use
case
and
in
long
term
use
cases
as
they
move
into
the
cloud.
The
other
set
of
customers
that
we
have
are
their
fortune
5,000.
B
You
know
core
security,
engineering
teams
that
have
been
building
out
their
own
Kerberos
based
authentication
infrastructure
and
look
at
this
as
a
successor
to
a
lot
of
the
work
that
they've
been
doing
there
as
well.
So
in
some
ways
in
one
of
their
heart,
the
head,
these
constructs,
the
ideas
are
not
too
dissimilar
from
things.
They've
worked
on
for
almost
30
years,
going
back
to
the
Athena
project,
MIT
going
back
in
1980-81,
and
so
we're
we're
engaging
with
those
folks
as
well.
B
The
last
thing
I'll
say
is
that
we
also
have
a
set
of
stakeholders
in
enterprise
architecture,
so
the
number
of
enterprise
architects
aligns
the
business
across
the
prototypical
fortune.
You
know
500
enterprises
that
show
up
and
say
we
have
a
mandate
to
move
X
percent
of
our
infrastructure
into
Microsoft
Azure,
and
some
percentage
of
that
is
going
to
run
on
kubernetes
to
figure
out
how
we're
going
to
make
that
happen.
B
G
It
does
I
definitely
got
a
good
sense
of
what
kinds
of
people
and
teams
are
reaching
out
to
you
to
talk
about
these
kinds
of
things
in
mind.
So
thank
you.
Are
there
any
big
challenges
like
this
is
a
lot
of
stuff
you're
working
on?
How
big
is
your
team
and
do
you
have
any
big
challenges
and
a
Brian
grant
already
asked
this
question,
and
you
mentioned
technical
writing
is
an
area
that
you'd
like
some
help
with,
but
is
there
anything
else?
That's
concerning
well.
B
I
think
I
mean
you
can
answer
your
question.
So
I
tell
it's
a
company,
a
five
people
we're
through
Dresden
running
out
hits
around
the
world
always
be
bigger,
like
any
company
could
be,
but
I
think
we
read,
we
do
really
good
work
besides,
oh
cab,
we
also
have
a
really
engaged
community,
there's
a
set
of
individuals
that
are
probably
on
this
call
and
beyond
that,
are
really
really
passionate
about
being
able
to
breathe
life
into
these
kinds
of
concepts
to
be
useful
to
kubernetes,
off
kubernetes
and
well
beyond
that
as
well.
B
You
know,
I
worry
that
you
know
we
don't
we're
not
doing
enough
to
make
sure
that
there
are
forums
or
mechanisms
to
people
to
participate,
not
only
in
the
code
but
in
the
design
right,
we're
still
in
the
design
phase
of
some
of
these.
You
know
aspects
about
the
code
base
and
the
specifications
as
well,
so
you
know
making
sure
that
it's
not
just
an
eye
tells
perspective.
B
That's
that's
represented
here,
trying
to
be
intellectually
honest
about
the
fact
that
we're
not
necessarily
the
owners
of
a
project
with
the
stewards
of
a
project,
and
we
have
some
perspective,
but
there's
a
heck
of
a
lot
more.
That's
out
there
so
identifying
ways
of
getting
more
feedback
earlier
on
the
design
process.
I
think
is
something
that
will
always
always
be
great
to
see.
But,
aside
from
that,
you
know,
you
know,
we've
got
roadmap
items.
We've
got
we'll
work
to
get
done
with
that
code
to
get
built.