►
From YouTube: Kubernetes Community Meeting 20160225
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Redspread demo, 1.2 release watch, 1.3 planning, newbie introductions, SIG-networking and a shout out to CoreOS blog post.
A
This
off
so
this
is
the
februari
25th
edition
of
the
cover
Nettie's
community
meeting.
It
is
public,
it
is
recorded
and
it
will
be
posted
on
YouTube
notes
will
be
posted
on
posted
on
the
Guru
Nettie's
blog,
and
we
have
quite
a
fun
agenda
ahead
of
us
today
which
just
dropped
back
into
the
document.
Thank
you.
So
much
to
first
up
is
going
to
be
a
demo.
I
read,
spread,
Mackenzie
Burnett
is
going
to
be
leading
that
we
have
any
quick
one
point
right:
release
TJ
ultimen
he'll
be
joining
at
about
ten
fifteen.
A
So
if
we're
any
ahead
of
schedule,
we
may
have
to
move
the
agenda
around
slightly.
If
anyone
has
a
use
case
or
any
wants
to
introduce
themselves,
we
can
do
that
for
a
few
minutes,
then
we
have
a
networking
cig
update
and
just
it
looks
like
a
cluster
ops,
short
deployment
or
short
update
here.
That
I,
don't
think
I,
don't
think
Rob
is
going
to
be
able
to
join
us.
So
we
will
move
through
this
Mackenzie.
Are
you
on
the
line.
B
So
well
well
we're
waiting
for
that.
I
just
want
to
do
a
quick
call
out.
I
gave
a
sort
of
Coober
Nettie's
101
presentation
the
other
day
and
I
put
the
slides
up
on
github
with
a
Creative
Commons
license,
and
so
how
could
the
pointer
for
that?
In
the
notes,
anybody
who
has
to
sort
of
give
a
soft
intro
feel
free
to
borrow
steal,
adapt
that
stuff.
You
know
for
kids.
Send
me
some
PRS
if
you
like
that
type
of
thing,
so
very.
A
C
That
same
topic,
I'm
trying
to
get
some
time
to
publish
our
we
call
our
uber
deck,
which
is
our
starting
point
for
most
of
our
presentations.
If
anybody's
seen
me
or
our
core
team
present,
they
probably
seen
slides
from
this
day,
I'd
like
to
make
that
something
that
people
can
use
as
a
starting
point
too.
A
Ok,
so
we
can
see,
says
she's
on
the
video
here
everyone
there.
We
go
excellent
thanks
Tim,
and
this
will
be
super
exciting
to
get
a
bunch
of
a
bunch
of
content
that
people
can
use
a
starter
content.
It's
gonna
be
really
helpful.
Ok,
so
let's
jump
to
the
Reds
red
demo.
So
Mackenzie
do
you
want
to
go
ahead
and
introduce
yourself
and
your
demo
I
heard
good
things
about
it
from
the
Wednesday
night
meet
up
yeah.
D
Sure
and
Danis
here
is
manager-
oh
my
co-founder,
so
yeah
hi,
everyone,
I'm
Mackenzie's
dan,
we're
building
red
spread,
which
is
a
command
line
tool
to
deploy
her
to
keep
Nettie's
in
one
command,
with
the
idea
of
building
out
a
suite
of
collaborative
deployment
tools
on
top
of
granny.
Why
and
my
guess,
I'll
share
my
screen
just
feel
a
little
bit
into
I've,
some
slides
of
talk
through
like
what
we
did
and
and
I
can
go
into
a
demo
as
well.
So
so
let
me
just
share
my
screen.
D
So
this
is
who
we
are
trying
to
find
us
email
us
just
our
first
names
at
Red,
Square
com,
so
spread
is
a
tool
to
build
an
image,
push
to
the
registry
and
deploy
to
keep
an
eye
to
use
in
one
command.
And
when
we
built
this
to
enable
rapid
iteration
with
Cooper
Neddy's,
it's
adana
top
of
it
through
like
why.
The
workload
through
Brandis
just
wasn't
something
that
he
yeah
just.
E
D
Yeah
yeah
totally,
and
so
we
just
wanted
to
be
like
the
easiest
way
to
play:
dr2
production,
so
road
map
we
have
the
deploy
to
keep
anything
on
command.
Next
thing
we're
doing
is
doing
the
building
and
pushing
with
that
and
then
the
third
thing
that
we're
looking
toward
is
offline
development.
The
local
Cooper
days,
cluster
and
I
can
I'm
going
to
go
to
the
demo
now.
So
you
can
see
that
so
we
set
up
something
where
you
just
deploy
a
matter
most,
which
is
open
to
our
slack.
D
D
So
it's
a
little
bit
of
how
it
works
its
client
side,
only
we
don't
wanna
server
component
to
it.
It
uses
a
very
large
portion
of
you
cuddle
code.
The
idea
is
to
allow
people
Cooper
nice.
We
could
rent
even
a
scrap
it
as
little
as
possible
inability
to
most
directory
convention.
So
we
have
there's
really
a
standard
nail
for
building
characters
and
love
to
get
feedback
on
this,
but
basically
have
soccer
file.
D
You
have
your
pond,
your
RC
and
a
job
cute
border,
which
holds
your
other
two
brandies
objects
and
we're
also
introducing
on
this
idea
of
a
dot
CTR
file,
which
is
where
your
container
lives.
You
can
still
put
containers
in
pods
in
our
seas,
and
but
the
idea
with
the
container
file
is
that
you
can.
It
enables
eventually
you
to
be
able
to
reuse
containers
across
an
application.
D
We
can
talk
a
little
bit
about
how
we're
thinking
about
like
embedding
different
objects,
so
you
can
build
sort
of
a
application,
just
screwing
links
if
something's
interest
in
that-
and
this
is
our
console
with
that.
So
I
talked
a
little
bit
the
idea
of
building
an
application
through
linking
between
cube
objects.
Second
thing
we're
thinking
about
is
parameterize
and
configuration
so
that
common
config
value
should
be
parametrized.
D
You
have
to
manually
go
into
yellow
file,
to
change
them
and
the
third
thing
that
we're
really
excited
about-
and
this
is
where
we
really
see
what
we're
building
going
toward-
is
versioning,
so
both
application,
versioning
and
deploying
versioning.
So
you
should
be
able
to
access
revisions
across
an
object
and
config
history.
D
In
an
appointment,
and
yesterday
we
talked
a
little
bit
at
the
sig
config
hang
out
about
how
and
1.2
you
can
do
this
a
little
bit
with
our
season,
pods
and
sort
of
have
access
to
that
the
entire
revision,
and
what
we're
thinking
is
that
there's
a
lot
of
instances
a
lot
of
these
phases
for
having
to
track
individual
objects
and
configurations
and
of
the
versions
of
those
across
the
entire
application.
I
needs
to
be
able
to
roll
back
till
early
revisions.
This
is
where
we
see
the
future
of
sprat.
D
Is
this
idea
of
get
for
Cooper
Nettie's,
a
unix-like
minimal
version
continue
our
workflow
for
the
command
line,
so
it's
like
how
could
I
contribute,
I'm
sure
you're
asking
so?
First,
you
can
install
spread
with.
We
have
a
root,
app
and
install,
and
linux
and
windows
is
coming
very
soon.
Sorry,
guys
and-
and
you
can
check
out
our
github
repo,
like
would
love
to
have
discussion
and
of
these
concepts,
so
we're
talking
about
in
our
issues
really
just
us
like
talking
to
ourselves
a
lot
of
the
time.
D
F
Right
thanks
I'll
just
make
a
pitch
for
the
configuration
and
deployment
sig.
If
you're
interested
in
this
kind
of
stuff,
please
do
come
and
participate.
You
know
it's
great
to
see
red
spread
and
other
people
try
interesting.
New
forms
of
deployment
on
burnet
ease
the
yeah.
There
are
a
lot
of
things
coming
in
this
space
in
1-2
and
those
are
also
under
discussion
in
the
sig.
F
D
A
Totally
very
cool:
well,
thank
you
both
for
joining
us.
So
we
have
a
couple
of
minutes.
I
haven't
seen
TJ
join
yet
so
TJ
jump
up
and
down
and
wave
if
you
have
joined
otherwise,
I
will
respond.
Oh
he
did
to
shine
fantastic.
Then
I
won't
reply.
My
item
ahead
so
go
right
ahead.
What's
the
one
point
to
you?
What's
the
word
on
1.2
yeah.
G
G
Some
of
that
due
to
tests
that
were
written
for
new
1.2
features,
there
now
running
all
the
time
in
the
queue
instead
of
just
running
occasionally
before
they
got
flipped
on
so
good
good
feedback
in
something
to
keep
in
mind
for
the
same
period
of
1.3,
so
I
think
that's.
Basically,
no
new
data
still
sort
of
in
a
slip,
I
would
venture
to
say.
G
As
always,
any
help
appreciated
with
any
bug
labeled
with
the
flake
label
or
in
the
v
1.2
milestone,
especially
if
it's
unassigned
or
if
it
has
been
stagnant
for
for
more
than
a
few
days.
You
know
poke
your
nose
in
there
if
you
can
help
out
and
ask
to
take
it
or
or
whatnot.
That
would
be
great
yeah.
F
A
Awesome
we
are
still
pushing,
not
surprisingly-
and
the
other
thing
of
note
is
just
to
remind
people-
we
will
bring
a
list
of
features
from
the
Google
team
to
the
meeting
on
a
march
third,
that
which
isn't
to
say
it's
a
list
of
absolute
features
that
are
completely
committed.
It's
the
list
of
features
we
expect
to
work
on
and
are
committing
resources
to.
We
will
then
share
that
with
you
all.
A
A
E
A
Also
have
an
open
chat
from
seal
because
I
mean
he's
new
and
have
attended
quite
a
few
meetings.
So
here's
hoping
that
they're
hopeful
and
useful
Ilan
robbed
her
shield
is
not
on
the
call
right
now
and
but
he
is
running
the
sig
cluster
ops.
We're
monitoring
is
working
on
right.
We're
monitoring
is
now
I
think
did
I,
do
an
introduction,
an
email
in
there
yeah.
A
A
A
Fantastic,
we
also
have
joe
thompson
from
core
OS
and,
yes,
we
can
put
a
pitch
in
for
the
quran,
the
upcoming
fest
there's
an
upcoming
core
OS
fest
and
I
believe
the
data
dog
is
sponsoring
it
and
michelle
from
babli
drawing
this
is
super
exciting.
We've
got
a
lot
of
new
people
today
and
I'll.
Let
the
chat
window
continue
on.
If
anybody
else
wants
to
do
the
video
intros,
we
can
do
that.
Otherwise
we
can
continue
having
little
new
introductions
in
the
chat
group,
which
is
great,
alright,
no
more
videos.
A
C
Everyone
so
update
on
the
networking
sig
we
actually
meet
today
later
today.
So
this,
this
update
is
a
couple
of
weeks
old.
We
have
been
working
primarily
on
a
specification
or
a
proto
specification
for
a
third-party
resource
to
describe
network
policy.
Specifically
micro
segmentation
is
what
most
people
are
calling
it.
The
ability
to
say
you
know,
pod
X
can
talk
to
service.
Why
but
not
serve
as
Z
or
then
all
my
front
ends
can
talk
to
the
back
ends,
but
not
to
each
other.
In
case
of
compromise
those
sorts
of
things
we
have
arrived
at.
C
What
we
think
is
a
spec
that
most
people
agree
has
the
semantics
that
we
want
we're
going
to
iron
out
a
few,
the
details
around
naming
and
structure
still,
but
the
semantics
is
there
and
in
fact,
the
same
day
we
sort
of
put
a
bow
on
that
the
folks
over
at
calico
who
I
don't
know
if
anybody's
on
this
call
its
moment,
but
the
folks
at
calico
raced
to
put
their
calico
demo
up
online.
So
they've
got
a
running
demo.
You
know
an
animated
gif
that
you
can
look
at.
C
Which
is
pretty
neat,
it
was
really
the
the
thing
that
most
people
have
been
asking
for
around
networking
and
so
I'm
happy
that
we
have
this
proto
spec
in
terms
of
in
time,
for
one
that
too
I
keep
saying
proto
spec,
because
there's
actually
nothing
in
the
spec.
That
requires
changes
in
the
one
not
to
code,
it's
all
based
on
annotations
and
a
third
party
resource
which
existed
already.
So
we
don't
need
to
actually
make
any
changes
in
12
to
start
people
playing
with
it.
A
K
Hey
Bob
wiser,
just
based
mostly
on
one
dot
to
overhead.
We
decided
to
postpone
our
meeting
for
this
week,
but
I
didn't
want
to
take
a
moment
and
recommend
everyone.
Who's
interested
in
scalability
take
a
read
the
excellent
core,
OS
blog
post
on
Ischia
skipper,
scheduler
scaling!
So
can
shout
out
to
those
guys
thanks.
That's
it
awesome.
A
All
right,
any
other
cigs
want
to
do
a
quick
report
out
all
right.
We
got
a
request
for
an
update
about
sig
off,
which
is
now
scheduled
for
March.
Third
and
I've
got
another
space
for
another
cig.
Does
anybody
have
any
partition,
particular
special
interest
groups
they'd
like
to
hear
from
next
week,
you're
really
in
terested
in
AWS,
OpenStack
networking
notes
all
right?
A
Well,
you
can
drop
your
notes
in
the
dock
if
in
the
community
meeting
doc,
if
you
have
suggestions
for
particular
sig
sig
report
outs
or
on
the
wiki,
you
can
find
all
the
information
about
cigs
as
well.
I
mentioned.
There
were
a
little
bit
of
notes
from
the
cluster
ops
sig
this
week,
which
are
in
our
notes.
The
meeting
last
Friday
went
really
well
discuss
the
Charter
and
working
deployment.
There
is
a
cig
cluster
ops
meeting
this
afternoon
at
one
p.m.
A
pacific
time,
so
that's
in
three
hours
and
rob
is
going
to
make
an
announcement
about
the
cluster
ops
sig
on
the
new
stack
to
recruit,
recruit
more
people
so
more
places
that
we
will
be
finding
more
users
of
Cooper
Nettie's,
which
is
super
exciting,
alright.
So
the
last
thing
that
I
had
this
morning
was
I.
A
I
talked
a
little
bit
about
the
google
Summer
of
Code
and
made
a
big
call
for
volunteers
last
week
in
the
mailing
lists
on
slack
and
here,
and
we
didn't
get
a
lot
of
people
jumping
up
to
be
mentors,
so
we
didn't
apply.
We
have
the
opportunity
to
do
this
again
next
year.
If,
by
some
chance
the
google
Summer
of
Code
team
comes
to
us
and
says
we
really
really
really
want
to.
A
Then
I
will
come
out
with
some
screws
and
come
looking
for
mentors,
but
we
had
only
one
person
say
that
he
was
interested
in
being
a
mentor
and
that's
just
not
enough
to
maintain
a
real
core
group
for
google
summer
of
code.
That
was
my
last
update
for
this
morning.
Does
anybody
have
anything
else
they
want
to
do,
or
is
this
going
to
be
the
world's
shortest
goober
Nettie's
community
hangout.
C
D
C
Can
get
update
on
that?
It
there's
a
very
rudimentary
form
of
dynamic
provisioning
in
12,
but
it
turns
out
to
be
at
odds
with
the
uber
Nettie's
work
we
didn't
realize
there
was
a
sort
of
collision
of
interests
there
and
we
both
ended
up
doing
something
that
don't
aren't
compatible.
So
we've
got
a
PR
in
flight
to
make
it
work.
It's
not
something
we're
super
happy
with
and
it
will
be
resolved
in
the
13
cycle,
but
it
should
be
enough
to
make
it
work
in
12.
A
Andrew
is
that
enough
information
for
you
sweet
thanks,
fantastic!
Alright.
Did
anybody
dig
up
PRS
for
1.2
that
you
want
to
hit
Bryan
with
I,
wasn't
really
trying
to
avoid
that
question?
I
was
really
trying
to
give
you
all
time
to
dig
out
what
the
PR
numbers
were
all
right.
Well,
you
know
where
to
find
them
on
github,
on
slack
in
the
ether,
probably
by
email.
It's
their
myriad
ways
to
find
us.
A
Thank
you
all
for
joining
and
unless
somebody
puts
their
hand
up
right
now,
really
quick,
then
I
think
we're
done
for
the
week,
and
we
will
see
you
next
week,
March
third
to
talk
about.
We
do
a
quick
pitch
of
this.
March
third
is
going
to
be
a
demo
of
Cooper
nidhi
anywhere,
which
is
the
weave
works.
Team
is
working
on
that
will
do
another
one
point
to
release:
watch
I'm
go
either.