►
From YouTube: CNCF TOC Meeting - 2018-04-03
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
D
D
All
righty,
Jonathan
or
Solomon
on
alcohol,
I,
don't
see
them
all
right.
Cool
I'll
get
started
so
yeah.
We
have
a
lot
of
TFC
members
that
are
currently
you
know
traveling
or
have
conflicts
that
have
come
up
so
we're
a
little
bit
like
today,
but
no
reason
for
us
not
to
hold
the
meeting
since
alexis
is
not
here.
I
will
drive
the
meeting
this
time
around
terms
of
the
agenda.
I'm
gonna
go
through
a
little
bit
of
an
update
in
terms
the
election
schedule,
a
little
discussion
on
working
group
process.
D
D
D
Look
forward
to
making
that
announcement
slide
7,
so
project
review
backlog.
You
know
we
try
to
link
everything
off
the
spreadsheets
that
are
linked
off
here,
but
really
the
main
things
that
I'd
like
to
mention
is
like
to
kind
of
you
know
publicly
shame
some
TOC
members
to
kind
of
get
their
votes
in
for
the
link
or
D
sandbox
incue
bation
votes,
so
far,
Brian
grant
has
voted
so
I'm
waiting
for
other
TOC
members
to
send
their
votes
in.
D
D
D
Essentially,
you
know
getting
accepted
into
the
sandbox
there's
telepresence
and
open
messaging.
You
know
I'd
like
to
call
upon
our
TOC
contributors
and
community
members
to
take
a
look
at
these
issues
before
they
present
and
feel
free
to
make
any
comments
there
or
ask
questions
to
the
teams
before
they
formally
present
to
the
TOC
in
wider
community.
D
Moving
on
to
slide
9
there's
been
a
few
folks
that
have
approached
the
TOC.
In
a
particular
me
of
setting
up
some
new
working
groups,
we
essentially
had
a
informal
process
of
doing
these
and
I'm
just
trying
to
codify
a
more
formal
process
on
how
to
propose
these
similar
to
kind
of
how
we
handle
projects
where
people
just
send
a
a
pull
request
with
their
proposal,
and
we
get
community
discussion
and
on
github
and
have
a
presentation
from
them.
D
So
I'd
ask
the
TOC
in
the
community
to
take
a
look
at
that
pull
request
and
hopefully
by
the
next
TOC
meeting.
We
could
get
that
solidified
and
and
kind
of
move
forward.
So
folks
from
the
community
could
propose
some
some
new
working
groups
that
they're
interested
in
exploring.
Does
anyone
have
questions
on
on
that
from
the
TOC
or
the
community?.
D
We
can
hear
you
Chris,
we
just
don't
have
questions,
know
where
it
is
I,
like
you
I,
like
a
very
non-controversial
TOC
amazing.
This
is
this
is
good
news
to
me
thanks
all
right,
yeah,
so
look
forward
to
that.
Please
take
a
look
at
it.
I
mean
where's.
This
is
exactly
what
we're
doing
anyway
for
working
groups.
I
just
need
a
mechanism
for
people
that
are
interested
in
proposing
new
ones
to
provide
an
avenue
for
community
discussion.
So
there's
some
really
cool
stuff
coming
in
the
pipeline.
People
will
be
excited
all
right.
D
B
B
B
C
Okay,
so
it's
been
a
good
while,
since
we
presented
to
the
TOC-
and
some
of
you
all
may
have
seen
some
updates
earlier,
but
we'll
do
kind
of
an
overview
of
everything
and
see
where
we're
at
now.
So
it's
a
crosscut
CI
project
and
here's
the
frost
cloud,
CI
team,
some
of
the
folks,
Denver
and
Lucene,
are
on
the
call
and
I
think
Watson
as
well.
C
So
a
quick
overview
of
why
we're
here,
everyone
knows
the
CNC
F
is
growing
like
while
lots
of
new
projects,
new
clouds
partners,
everything
else
and
we'd
like
to
see
the
projects
working
well
together
and
validating
that
they're.
Looking
great
on
all
the
cloud
providers
supporting
their
cloud
native
features,
so
this
project
is
trying
to
its
goal
is
to
test
the
projects
on
the
cloud
providers
and
the
interoperability
between
all
the
projects
themselves.
The
backend
testing
system
is
composed
of
a
built
cross
cloud
provisioning
stage
and
an
across
projects.
C
C
C
It's
updated
daily
at
3
a.m.
Eastern.
It
shows
the
different
stages
of
the
build
system,
the
deployment,
the
ad
testing
kubernetes
provisioning
and
the
status
of
this.
It's
testing
the
stable,
as
well
as
the
head
release
of
the
projects
in
later
phases.
On
some
other
screens,
we
may
be
showing
some
of
the
other
stable
Lisa's
right
now.
This
is
the
overview
screen
and
we
have
kubernetes
Prometheus
core
DNS
20
linker
Dino
net.
On
the
cloud
providers.
You
can
see
AWS
as
your
Google
clouds,
IBM
clout,
bare
metal
and
OpenStack.
C
If
we
click
through,
you
can
go
to
the
commits
out
on
github
for
the
various
projects.
On
the
build
side,
we
can
go
through
to
see
the
backend
build
system
for
onap.
This
actually
ties
in
with
their
CI
system
they're,
using
Jenkins
and
Nexus
for
container
repository
I'm,
going
to
go
ahead
and
start
off
a
deploy
to
see
this
running.
C
C
This
is
call
NASA,
API
and
triggering
that,
and
what
this
is
going
to
do
is
start
the.
We
can
see
it
here,
it's
starting
the
pipeline's
that
will
deploy
each
of
the
apps
to
kubernetes
across
every
flout,
so
there's
quite
a
bit
that
are
going
to
run
through
right.
Now,
it's
getting
some
of
the
software
found
and
the
containers
the
container
that
actually
does
the
deploys,
ready
and
then
it'll
move
on
to
the
app
deploy
face
here
and
we
can
see
it's
starting
to
run
across
each
of
these
for
prometheus.
C
C
Want
to
go
through
a
quick
timeline
where
we've
been
so
in
February
2017,
the
project
started
and
then
June.
We
had
our
first
image
of
the
CI
working
group
that
was
showing
primarily
the
CI
system
and
the
how
the
different
pipelines
worked
to
build
provision
and
deploy
in
August.
We
demoed
to
the
TOC
shed
some
of
the
designs
for
the
dashboard,
as
well
as
the
API
status
SAS
repository,
and
then
we
had
the
green
light
on
the
design
in
September.
B
C
Repository
as
well
as
a
reworking
of
the
backend
to
use
the
different
components
independently,
like
provisioning,
can
be
used
independently
for
the
app
deployment
in
AD
phase
in
March,
we've
had
quite
a
few
new
releases,
including
adding
some
new
projects,
new
clouds
like
IBM
cloud,
we
added
OpenStack,
as
well
as
the
own
app
project,
which
was
our
first
external
integration
with
the
CI
system
outside
of
get
labs.
So
that
was
pretty
great.
C
C
Eventually
we're
going
to
be
adding
armed
support,
starting
with
kubernetes
on
arm
and
going
forward
inside
the
project
itself.
Some
of
the
updates
that
we're
going
to
be
doing
would
be
automating
the
updates
of
the
releases
from
projects
upstream
and
testing
those
and
then
pushing
them
out
to
the
dashboard
right
now.
The
process
is
a
couple
of
steps
to
get
them
out.
C
We're
also
planning
on
having
the
history
in
the
API
for
all
of
the
tests
and
the
artifacts
and
everything
else
to
be
available
in
the
status
repository
so
that
it
can
be
queried
externally,
and
you
can
look
up
stuff
like
a
version
of
kubernetes,
with
what
version
of
prometheus
worked
on
that
and
use
those
externally
to
the
dashboard.
This
also
helped
us
to
do
roll
back
to
previous
releases.
C
So
if
we
had
a
failure
on
196
on
a
deploy
or
maybe
an
app
wasn't
running,
then
we
could
point
that
out
in
the
dashboard
with
pool
tips
or
whatever
else
and
that'll
tie
in
with
some
of
the
next
screens
that
we're
doing
like
probably
on
a
kubernetes
project
screen
for
that
filter.
We
may
be
showing
1.8
and
other
stable
releases.
C
For
the
collaboration
side,
working
with
other
groups,
we're
working
with
the
open
CI
community
that
came
about
from
a
face-to-face
before
ons
this
past
week
and
working
on
a
collaborative
white
paper
together
for
how
that
should
look.
We've
also
been
working
on
an
RFC
for
pipeline
messaging
protocol
have
the
link
here.
Anyone,
let's
check
that
out,
going
to
be
working
with
VMware
and
IBM
club
talking
about
their
provisioning,
we're
looking
at
spinnaker
as
a
option
or
doing
some
assesses
to
do
with
get
left.
C
Now
that
the
Cross
lab
system
has
a
layer
between
the
back-end
platform
that
has
workers
and
runners
as
well
as
some
of
the
projects
themselves
for
their
end
to
end
test
prometheus
is
working
on
a
lot
of
their
end-to-end
tests,
including
performance
and
statically
running,
to
tie
in
and
try
to
see
where
we
can
complement
directly
and
reuse
this
for
DNS
as
well.
We're
also
looking
forward
to
talking
about
the
get-ups
and
how
we
use
it
and
where
we
could
improve
and
tie
that
into
the
project.
C
The
next
guy
working
group
is
April
10th,
we're
planning
on
being
at
Q,
Khan
cloud
native
Khan
and
Copenhagen,
and
we're
going
to
have
an
intro
as
well
as
a
deep
dive
for
the
project
and
how
folks
can
get
started,
whether
you're
a
project
or,
if
there's
any
quad
providers
that
want
to
talk
to
us
and
OpenStack,
was
really
great
on
Chris
hipes.
You
want
to
call
out
for
helping
well
as
Melvin
trying
to
work
with
us.
Add
OpenStack
support,
so
we'll
be
there
to
try
to
show
how
folks
can
do
that
and
contribute
directly.
C
Here's
where
you
can
join
the
CI
working
group
mailing
list
and
if
you
have
any
more
questions,
feel
free
to
jump
on
there.
If
you
check
out
the
github
cross
cloud,
CI
we've
been
updating
the
readme
zazz
overview
in
the
main
and
the
different
components
like
cross
cloud
or
cross
project
we're
trying
to
update
those
readme
so
that
you
can
use
the
components
directly
independent
of
the
cross
flow
CI
project.
C
So
we
are
trying
to
use
kubernetes
conformance
test
for
our
conformance
on
all
the
cloud
providers.
There
is
a
conformance
egg
and
we're
trying
to
follow
some
of
the
things
that
are
happening
there
like
feature
flags
that'll,
be
able
to
test
various
features
on
cloud
providers.
It
could
be
used
and
Danny
are
you
here
on
the.
G
But
that
really
is
a
super
new
effort
and
and
it's
just
it's
a
proposal-
the
codes
open
source,
it's
available
to
the
cloud
providers
and
something
I
mentioned
on
a
stick
architecture
call
but
we'll
see.
If
that
actually
goes
forward
or
not
Albin,
do
you
want
to
maybe
specify
your
question
a
little
bit
more
or.
H
G
Certainly
great
I
would
love
to
just
hear
other
feedback
on
the
cross
clouds
stuff
I
mean.
Are
there
people
on
the
call
who
this
is
new
to
and
who
think
this
is
either
kind
of
cool,
or
you
know
they
might
be
interested
in
looking
at
the
terraform
recipes
that
we're
using
again
everything's
under
Apache
2.0
or
do
flip
see.
This
is
duplicative
with
with
other
projects
out
there.
G
F
B
G
I
It's
it's,
this
is,
this
is
really
cool.
Could
you
comment
maybe
a
little
on
you
know.
Some
of
these
questions,
I
think
are
I
would
like
to
see
something
happen.
Like
adds
some
additional
thing
here
and
I
think
you
understandably
concerned
about
explosion
of
Commodore
combinatorial
explosions.
But
let's
say
someone
did
want
to
I.
Don't
know,
add
tests
for
different
distro
as
the
as
the
other,
as
the
other
caller
was
mentioning.
Is
there?
Is
there
a
way
for
someone
to
you
know,
volunteer
effort
or
effort
group
resources
to
make
that
happen
I?
B
Yeah,
definitely,
the
changes
should
be
pretty
easy
to
integrate
and
it's
just
expands
the
matrix
the
only
so
it
would
just
be
a
poor
question
to
the
code
that
deals
with
the
provisioning.
The
only
thing
that
might
be
a
little
bit
of,
if
it
were,
we
haven't
quite
got
to
get
as
showing
matrixes
on
the
dashboard.
I
B
C
A
C
And
then,
as
Dan
said,
anyone
could
run
the
dashboard
and
the
status
repository,
but
any
of
the
components
can
be
split
off
and
the
dashboard
is
actually
all
configuration
driven
so
that
if
you
spin
up
the
code,
then
you
can
point
to
whatever
your
configuration
is
and
say:
I
only
want
these
projects
to
show
whatever
that
may
be,
then
that
could
be
is
so.
Someone
may
want
to
use
it
just
for
their
project,
which
should
be
fine
right.
I
I
mean
I
understand
the
the
possible
utility
of
using
this
to
do
some
other
kind
of
testing,
but
I
think
I,
know
I,
guess
for
this
on
this,
for
the
sake
of
the
community,
I'd
rather
see
more
people
contribute
to
this
set
of
tests,
then
split
it
off
and
run.
It
separately
feels
like
it
without
more
value
in
the
long
run.
As
long
as
we
can
support
that.
C
Core
DNS
is
a
great
example
they're
trying
to
make
sure
all
of
their
tests
will
run
independently
for
an
end
user,
and
then
it
doesn't
depend
on
a
specialized
CI
environment
and
that's
how
we've
tried
to
do
the
test
examples
and
we're
trying
to
help
so
any
project
that
can
do
that
or
if
someone
wouldn't
contribute
to
say,
fluid
D
and
help
provide
those
end
user
integration
tests.
Then
that
would
be
great
a
good
way
to
help
and
there's
a
lot
of
new
projects
will
be
adding.
B
At
the
moment,
there's
it's
a
three
multi-master
notes
and
we're
only
using
one
worker
at
the
moment
because
of
the
way
we
had
to
shrink
because
of
the
way
own
apps
being
deployed
at
the
moment,
own
app
doesn't
isn't
able
to
use
two
single
volume.
It's
got
a
beat
on
one
host,
so
it
was
either
set
up
in
FS
across
all
the
nodes
or
just
use
one
worker,
so
we're
just
on
one
scheduler
at
the
moment
until
the
Beijing
release
comes.
H
B
I
I
A
H
At
the
moment,
I'm,
there
are
a
lot
of
areas
where
the
tests
are.
We
started
with
the
test
that
we
so
we're
looking
at
places
where
the
tests
need
to
be
expanded.
This
is
definitely
one
of
the
areas
it
looks
like
so
I
had
a
question
which
is
have
the
folks
working
on
this
I'm
poking
around
the
github
repo.
Looking
at
the
terraform
have
you
talked
to
the
communities
cluster
lifecycle
special
interest
group
about
what
you're
doing,
because
I
think
you
know
reinventing
how
to
deploy.
B
I,
don't
believe,
please
pedicle
with
cluster
lifecycle.
Yet
we
did
have
a
few
calls
with
Aaron
from
cig
the
infrastructure,
sig
testing.
H
G
Right
and
so
we
looked
at
cops
and
look,
both
the
terraform
was
going
to
be
a
more
general
purpose,
but
essentially
we're
willing
to
transition
off
of
all
this
terraform
onto
whatever
the
official
way
of
doing
it
is,
if
there's
a
recommendation
on
this,
so
I
think
starting
with
maybe
a
presentation
to
cluster
life
cycle
would
be
a
good
next
step.
Yeah.
H
I
think
that
would
be
a
good
next
step.
Yeah
we're
discussing
how
to
what
our
reference
implementation
be
for
running
our
own
into
end
tests
as
we
replace
the
existing
deprecated
cube
up
mechanism,
so
I
yeah
I,
just
think.
If
you're
maintaining
your
own
on
several
different
cloud
providers,
that's
going
to
be
hard
hard
to
do
as
this
system
continues
to
evolve.
E
B
At
the
moment,
we're
just
running
the
conformance
subset
and
what
the
packets
so
I
believe
conformist
is
some
storage,
but
it's
not
extensive.
That
we'd,
like
like
it,
took
to
a
point
where
we
can
profile
and
be
like
we're
on
this
cluster
AWS
to
us
absurd
of
the
AWS
integration
include
storage
right.
D
D
B
C
B
D
D
A
D
Alrighty,
so
moving
on
next
up
slide
28.
So
as
you're
aware
scene,
CF
helps
put
on
events
for
our
community
and
projects.
We
have
a
big
event
coming
up
in
Copenhagen
in
an
early
May
May
2nd
to
24th.
I
will
just
remind
people
that
please
book
your
hotels
early,
we
are
gonna,
sell
out
of
that
event
and
hotel
space
is
going
to
be
a
bit
of
a
challenge
so
the
earlier
the
better.
We
also
have
two
other
events
that
we're
hosting
in
a
year.
D
Our
first
event
in
China
and
an
event
in
North
American
Seattle
in
December,
so
sponsorships
are
available
for
Shanghai
in
Seattle,
and
you
know,
we'd
love
to
you
know
have
a
huge
presence
in
China,
given
that
it's
our
first
event,
so
please
submit
talks
and
consider
sponsoring
the
event
dan.
You
have
any
other
thoughts
on
call
for
action
here.
D
G
D
D
We
will
also
at
that
time,
have
two
new
toc
members,
so
look
forward
to
that
announcement
other
than
that
any
other
questions
slide.
30
is
basically
open.
Q&Amp;A
we've
got
about
15
or
so
minutes
left.
So
if
anyone
has
time
to
ask
questions
to
the
TOC
or
the
wider
community
or
CNCs
staff,
we'd
love
to
we'd
love
to
hear
it.
J
Chris
I
have
a
question
sure
Dan
saw
I'm
actually
from
the
the
safe
group
and
I
was
just
wondering.
You
know,
saw
the
working
group
process,
you
know
kicking
off.
Do
you
have
any
expectation
about
how
long
that
that
process
is
going
to
take
to
land?
You
know
I
see
the
discussion
is
getting
to
not.
D
They're,
like
yeah,
it's
it's
hard
to
say
my
assumption
is
just
follow.
The
proposed
template
I
actually
have
a
meeting
with
some
other
folks
from
from
the
safe
group
today
and
I'll
guide
them
through
the
process.
So
in
general
you
have
the
slot
to
present
to
the
TOC
you
next
week
or
sorry
in
two
weeks
and
will
kind
of
follow
the
template,
as
dictated
in
kind
of
at
PR
I.
Don't
think
we're
gonna
far
very
far
from
from.
What's
there
they
says
cool.
Thank
then
any
other
questions
out.
H
D
D
Please
consider
throwing
down
a
vote
before
the
end
of
this
week
and
I
hope
to
see
many
of
you
in
a
couple
weeks
where
the
telepresence
project
and
the
safe
WG
will
be
presenting
and
then
hopefully
we'll
see
many
of
you
in
Copenhagen
in
May
so
enjoy
the
rest
of
your
day
and
here's
15
minutes
back
take
care
everyone.
You.