►
From YouTube: Kubernetes Community Meeting 20160811
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Demo: OpenID Connect backed by a third party resource; Kubernetes Bootcamp and docs surge; 1.4 features update; incubator process; SIG instrumentation proposal; SIG cluster-ops
A
Good
morning
all
and
welcome
to
the
Cooper
Nettie's
community
meeting
on
Thursday
August
eleventh
this
morning.
We
have
actually
quite
a
bit
of
fun
ahead
of
us,
as
always
I,
or
at
least
I
try
to
make
the
agendas
fun.
We
are
starting
it
with
a
demo
from
40
s,
talking
about
open,
ID
connect
and
having
that
backed
by
a
third-party
resource.
So
Eric
are
you
game
to
get
started
and
then
we'll
jump
on
with
the
rest
of
the
agenda
following
you,
oh.
A
C
So
so
high
first
off
on
on
Eric
I
work
at
core
OS
and
have
been
trying
to
contribute
to
upstream
sig
off
as
much
as
possible
for
Cuban
at
ease,
and
recently
we've
been
working
on
trying
to
basically
get
one
of
our
10
dog
services
running
on
top
of
Cooper
Nettie's.
So
I'm.
Just
to
back
up
a
little
bit,
I
explained
in
detail
about
what
I'm
going
to
be
demoing
in
Coober,
Nettie's
guru,
Denny's
doesn't
have
a
concept
of
the
user
or
built
into
it.
You
can't
coop
CTL
create
a
user.
C
C
So
we've
been
working
on
revamping
decks
a
little
bit
to
basically
run
better
on
committees
and
a
big
problem
with
Dex
is
that
Oh
off
to,
and
things
like
that
require
some
degree
of
state
right.
So
if
somebody
has
an
oauth2,
client
I
need
to
track
that
client
somewhere.
If
somebody
has
a
if
someone
has
a
client
has
gotten
a
refresh
token,
I
want
to
be
able
to
revoke
that
at
some
point.
So
at
some
point
we
need
some
state.
C
C
Another
service
account
a
third-party
resource,
so
Cooper
Nettie's,
the
API
generally
has
API
groups
things
like
extensions
or
are
back
or
just
the
v1
and
within
those
there
are
a
bunch
of
these
objects
and
eventually
all
those
things
are
doing
is
being
stored
in
SED,
but
in
Coober
Nettie's
you
can't
create
your
own
objects
and
even
though
that
would
be
really
nice
too.
So
the
concept
of
the
third-party
API
is
saying:
hey,
Cooper,
Nettie's
I
want
to
go,
create
that
myself.
C
So
if
I,
I
have
my
sort
of
dex
repo
here
and
in
this
development
version
of
dex,
that's
sort
of
experimental
and
working
on.
We
have
a
bunch
of
third-party
resources
that
we've
defined,
so
third-party
resources
have
a
couple
of
fun
little
bugs
that
cause
of
this
to
be
a
little
bit
ugly.
But
basically,
what
you
can
see
is
that
I
can
go
ahead
and
define
and
say:
okay,
ready,
I
want
to
define
an
oauth2,
client
and
you're
going
to
understand
this
concept.
C
When
I
put
an
oauth2
client
that
you
will
actually
be
able
to
store
that
data,
or
importantly,
open
ID
connect,
its
flavor
of
aura
has
a
signing
key.
So
I
can
actually
put
something
like
a
signing
key
into
group
of
Eddie's.
So
I
have
a
single
node
urban
Eddie's
instance
right
here,
and
what
I
can
do
is,
I
can
just
say,
coupe
CTL,
create
beats,
boop,
CTL,
create
and.
C
What's
what's
cool
about
that
is
that
then
I
have
a
flavor
of
dex
right
here
that
actually
uses
these
third-party
resources,
so
I
can
do
dex
serve
and
if
I
give
it
a
configuration,
that's
wired
to
talk
to
my
cooper,
Nettie's
cluster
and
I
go
ahead
and
press
enter
then
immediately.
What
it
will
do
is
will
try
to
sort
of
start
rotating
keys
in
cooper,
nutty's
and
you'll
see
all
these
errors.
C
C
Also,
the
pluralization
for
their
pretty
resources
is
a
little
bit
ad-hoc,
so
we
have
like
a
misspelling
of
keys,
but
that's
okay
and
I
actually
are
now
storing
all
of
my
state
here.
So
the
way,
of
course,
that
a
lot
to
works
is
that
you
can
have
some
client
app
that
redirects
you
to
a
provider
like
Facebook
and
in
this
case
Dex
is
my
actual
provider.
C
So
I
can
go
ahead
and
run
a
example
app,
alright,
quite
a
client
application,
but
I
don't
have
any
clients
registered
and
again
because
I'm
using
third-party
resources,
I
can
actually
just
go
and
create
a
client
so
its
client.
So
this
is
what
a
third-party
resource
looks
like,
whereas
the
other
ones
I
created,
which
descriptions
this
is
actually
a
full-fledged
object,
incur
benetti's
that
I
cannot
create
and
you'll
see
that
I
now
have
a
kind,
oh
off
to
client
that
is
completely
different
from
actual
from
the
fee.
C
C
So
I'm
going
to
hit
login
Dex
is
going
to
give
me
a
couple
login
options
again.
The
UI
is
a
little
messy,
but
I
can
go
ahead
and
say,
like
oh
I
want
to
log
in
with
github,
so
I'm
at
dex
right
now,
I
log
in
with
github
I
logged
in
correctly
and
github,
because
I've
logged
in
before
it
didn't
prompt
me
and
then
I
can
say:
ok
I'm,
going
to
approve
my
example
app
and
now
I'm
back
at
my
example
app
with
I'm
actually
requested
gotten
a
token
from
dex.
C
So
if
you,
if
I
go
back
to
my
terminal
over
here,
you'll
actually
see
all
right
if
I
keep
CTO
get
like
refreshed
it.
Oh
yeah
refresh
tokens
again:
we've
stored
all
the
state
in
Cooper
Nettie's
and
are
now
running
that
out
there,
so
I
can
go
ahead
and,
like
redeem,
my
refresh
token
and
get
a
new
token
and
so
on
and
so
forth
and
again,
the
important
part
about
this
is
that
hoe
IDC
is
the
flavor
of
0.
F
provides
tokens
that
Cooper
Nettie's
understands.
C
So
I
could
go
ahead
and
post
this
into
a
poop
CTL
like
coups
TL,
config
and
then
be
able
to
authenticate
with
the
communities
cluster
using
it,
and
the
big
advantage
of
using
third-party
resources
here
is
that,
rather
than
you
having
to
provide
your
outside
data
store,
we
hope
to
just
be
able
to
very
a
very
low
and
a
very
low
overhead
way,
just
run
this
application
on
Cooper
at
ease
and
provide
a
lot
more
options
that
we
can
maintain
how
to
French.
So
that's
pretty
much
my
entire
demo.
C
We
have
some
other
cool
features
in
here
that
and
be
more
full-fledged
if
I
wired
up
crew
benetti's
to
talk
to
this.
But
that's
what
we've
been
working
on
with
Dex
these
days,
there's
a
development
branch
open
that
has
a
lot
of
these
changes.
So
if
you
come
over
to
the
repo
and
look
at
the
dead
branch,
there's
this
experimental
branch
that
we're
working
on
to
make
this
a
little
bit
more
possible
in
full
fledged.
So.
C
A
C
So
we
have,
we
have
two
branches
these
days
one
is
master
and
one
is
dev
that
we've
been
working
on
and
the
dev
has
all
of
the
examples
that
we
I
just
showed
there.
So
examples
crouppen
at
ease
and
there's
some
more
full-fledged
examples
for
running
decks
on
top
of
kerbin
at
ease
and
also
as
the
authenticator
for
proven
at
ease,
and
to
allow
you
to
use
a
lot
more
options
to
log
into
your
cluster.
So.
A
C
I,
definitely
it.
It
doesn't
necessarily
matter
to
me
for
my
use
case
for
this
particular
one
you're
only
ever
going
to
be
18
but
you're
only
ever
going
to
be
running
when
Dex
in
the
cluster.
So
theoretically
it
should
be
clustered
names
a
scoped,
but
you
would
I,
don't
ideally
want
to
be
setting
up
ackles
around
it
anyway,
and
you
can
do
that
regardless
of
where
it
is
in
the
cluster.
So
ideally,
yes,
I
mean.
Maybe
not,
though,
because
then
I
could
run
multiple
decks
in
multiple
namespaces.
A
C
C
A
B
Right,
hi,
everyone
see
I'm
going
to
talk
about
some
exciting
things.
We've
been
doing,
&
sig
docs
from
a
high
level.
You
may
have
noticed
we
did
a
big
surge
on
Doc's
PRS
weirdness
there
studying
get
out
of
hand,
and
so
few
of
us
I
did
a
lot
of
reviewing
there
and
we
are
not
at
a
point
where
we
have
a
bot
that
auto
assigns
docs
PRS.
So
if
you
see
a
doc
PR
getting
assigned
to
you,
there
might
be
some
metadata
at
the
top
of
the
dock,
with
your
name
on
it.
B
One
thing
we
notice
when
you're
doing
the
docs
PR
is
there's
a
number
of
docs
in
our
repo
that
the
most
of
the
expertise
lives
outside
the
core
project,
for
example
specific
cluster
setup
guides
and
as
a
result,
this
ends
up
delaying
how
long
it
takes
the
doc
to
actually
get
merged,
because
some
docs
writer
within
the
organization
needs
to
review
it
and
comment
on
it
and
then
that
just
blocks.
What
probably
we
don't
need
to
review
necessarily
and
the
primary
maintained
errs
can
own
and
host.
B
So
we
are
putting
together
a
plan
for
trying
to
encourage
people
to
move
that
stuff
out
and
figure
out
exactly
what
what
should
live
in
the
repo
and
what
shouldn't
live
in
the
repo
but
the,
but
the
the
main
key
is
going
to
be.
If
the
primary
people
maintaining
it,
the
content
doesn't
relate
to
the
core
repo.
Then
it
probably
should
live
somewhere
else
and
then
I'm
going
to
give
a
quick
demo
of
some
fun
stuff.
We've
been
working
on.
B
B
B
So
this
is
we're
calling
a
boot
camp,
though
the
names
still
under
discussion
right
now,
but
the
goal
is
to
just
provide
a
quick
introduction
to
Cooper
notice
that
removes
as
much
friction
as
possible
and
gets
used
your
successful
using
the
product,
so
I'll
just
I'm
not
going
to
walk
through
the
whole
thing,
but
I'll
just
give
you
a
flavor
of
it.
It
has
these.
Some
text
has
some
nice
diagrams
and
explanation,
and
then
it
has
this
interactive
tutorial,
part
where
you
can
go
in
and
actually
type.
B
B
We're
really
looking
to
give
feedback
by
end
of
today
and
now
it's
a
quick
turnaround,
but
the
people
are
we're
working
with
that's
going
to
be
the
timeline
where
we're
needing
on
this
to
get
the
feedback
in
and
then
one
last
thing
is
sig
docs
is
going
to
start
having
meetings,
so
we
can
all
get
together
and
chat.
I
think
there's
a
critical
mass
of
us
now
and
we'd
all
like
to
see
each
other
at
least
over
BC,
so
we're
planning
on
having
a
meeting
next
week.
B
B
You
can
you
can
even
ping
me
on
slack
I'm,
always
in
the
sig
docs
channel,
and
you
can.
If
you
at
mentioned
me,
it'll
go
to
my
phone,
so
I
don't
have
to
pull
the
slack
channel
so
yeah.
I
can
follow
up
with
you
offline
on
that,
and
this
is
phil.
My
handle
is
p
wittrock.
It's
all
added
to
the
community
notes
stock.
So
you
can
see
it
there.
A
A
F
Sos,
most
of
you
may
remember,
the
spreadsheet
and
collecting
floor
from
the
actual
release
and
I
have
a
better
date
with
the
actual
data
data,
forgetting
the
features
the
target
we
added
wonderful
I
have
highlighted
them
with
yellow
color,
so
these
features
are
like
in
the
actual
state
of
fried
and
some
code,
and
most
of
them
are
expected
to
be
finalized
before
the
some
cut
fries.
That
will
happen.
The
next
Friday
I
was
19,
so
we
expecting
these
things.
We
discover
to
the
coordinates,
s0
functionality.
F
It
doesn't
mean
that
all
the
rest,
we
just
won't
be
headed,
but
the
actual
status
on
the
github
can
provide
us
like
they're
real
estate.
Is
that
early
ready
or
expected
to
be
ready?
So
if
someone
a
few
tests
has
any
feature
on
the
features
repo
is
in
communities.
Optimization
and
you'd
like
to
see
you
feature
as
amended
to
wanted
for
lace
on
your
edge
department.
F
A
F
F
General,
that
means
that
this
this
feature
is
has
been
added
to
the
featuring
as
a
feature,
so
it
has
been
defined
and
all,
and
we
have
proposed
a
speech
should
be
to
be
ready
one
day
for
for
this
release,
but
at
the
same
time,
the
speech
is
not
actually
rated
now
calling
as
we
started
a
strong.
So
if
you
can
see,
for
example,
support
this
feature,
you
may
see
the
progress
started
that
describe
the
actual
status
of
this
ankle
feature.
So
we
have
this
brief.
Brief
should
describes.
F
Disparity
have
to
follow
the
four
submitted
this
feature,
and
in
this
case
this,
which
hasn't
like
fall
upon
steps
and
like
before
often
instead.
This
feature
has
been
submitted
this,
which
we
propose
to
have
an
idea,
and
it
would
be
great
if
some
days,
which
will
be
added,
but
no
real
progress
has
been
trapped
for
them
in
this
one.
A
F
Yes,
I
see
the
note
from
from
Justin
did.
That
means
that
might
may
mean
that
deep
sea
creature
won't
be
added
for
wonderful,
because
Noel
Nora
welcomed
it
has
been
started.
Well,
sometimes
it
may
mean
that
only
the
feature
own
and
hasn't
hasn't
pushed
the
real
progress
report
on
decision
to
this
tracker,
so
I'd
like
to
ask
again
for
all
their
future
owners
to
update
the
actual
status,
the
officials
to
be
to
be
really
up
to
date
with
Deb,
very
clear
information
or
getting
their
states.
Yes,.
A
The
whole
idea
of
doing
the
feature,
recoil
and
and
pulling
together
this
product
screen
was
so
we
can
get
better
visibility
but
that
better
visibility
has
to
bubble
up
from
the
people
who
are
writing
the
features,
pushing
features
leading
them
and
then
summarizing
data
so
that
we
can
share
it.
Yes,.
F
A
Thank
you
for
the
update
you
are
and,
of
course
there
is
a
call
out
to
everyone
to
make
sure
that
if
you
are
working
on
a
feature
that
you
are
updating,
github
and
making
sure
that
your
feature
tracking
issue
in
your
faucet
or
is
up
to
date,
all
right
today
is
the
11th.
So
we
have
two
proposals.
One
actually
is
not
in
here
at
the
moment.
So
Brandon
are
you
game
to
talk
about
the
incubator
proposal
for
a
moment
sure.
C
So
what
the
incubator
proposal
is?
Is
it
talks
through
how
to
add
a
new
repository
into
Cooper
Nettie's,
particularly
new
repository
that
aren't
related
to
code,
that's
already
merged
into
into
the
kubernetes
git
repo?
So
we've
had
a
couple
of
swings
at
this.
So
far,
we've
had
the
contribute
repo.
We
have
the
right.
Now
we
have
the
randomly
people
who
have
owners
on
Cooper,
Nettie's,
org,
add
new
repos
methodology
and
it's
kind
of
breaking
down.
C
So
the
proposal
essentially
defines
a
little
process
to
circulate
what
you're
trying
to
do
and
then
get
some
a
couple
of
folks
that
are
trusted
in
the
communities
community.
Is
there
either
a
reviewer,
an
approver
to
kind
of
Shepherd
the
shepherd
the
new
incubated
project
through
the
process?
So
the
whole
thing
you
can
find
on
communities
dev?
It
was
posted
yesterday
evening,
under
a
thread
that
was
called
process
for
adding
and
removing
github.com
/
Cuban
at
e3
pose
it's
the
very
last
century
in
the
thread
and
it's
google
doc.
C
D
A
We'll
put
it
in
the
notes
and
then
after
it
gets
finalized
it'll
actually
go
up
into
the
community
repo
as
a
how
this
actually
happens.
Whoops
I
swore
okay
moving
on
so
up.
Next
is
another
proposal
which
is
super
awesome.
Stuff
fabian
has
proposed
a
cig,
instrumentation
group,
and
so
that
has
been
a
thread
out
in
cooper,
Nettie's,
devs
baby.
You
know
you
came
to
talk
for
a
minute
or
two
about
it
and
see
if
anybody
has
any
questions
or
feedback
sure.
E
So,
basically,
I'm
working
on
prometheus
upstream
and
I'm
also
working
Scaurus,
I'm
actually
I'm
interested
in
basically
giving
proven
its
best
possible
strategy
board
and
we
can
and
our
time
we
sort
of
realized
that
there's
just
some
stuff
missing
and
also
we
get
user
reports
manhua
on
the
premises,
community
channels
about
installation
being
wrong
missing.
And
how
can
we
solve
this
and
and
I
know,
I?
E
Think
that
these
two
external
tools
to
extract
data
from
the
API
and
and
itself
not
the
way,
how
insolent
a
trip
girl-
and
so
we
figure
to
just-
might
form
an
interest
group
that
just
cares
about
whatever
instrument
and
which
other
an
interest
group
needs
which
metrics
for
which
boxes?
And
where
can
we
basically
join
efforts?
E
Where
should
we
make
separations-
and
this
is
sort
of
just
idea-
to
get
a
process
started
to
figure
out
what
improve
the
whole
situation
and
also
there's
the
issues
by
now
regarding
exploitation-
and
this
seems
to
be
like
sort
of
an
ownership
problems-
everybody
often
agrees
they
should
be
done
and
how
to
be
done,
but
nobody's
actually
willing
to
take
the
lead
on
that
and
so
yeah.
That's
something
this
group
could
take
up
as
well
and.
A
Push
things
forward
because
one
of
the
things
we
keep
finding
is
everybody's
got
lots
of
great
ideas
and
if
we
don't
have
people
pushing
them,
then
and
championing
them
separating
them.
I
used
a
lot
of
different
words
in
this
or
in
this
group,
but
if
we
don't
have
someone
who
is
on
the
hook
for
them,
then
we
have
a
hard
time
actually
delivering
them,
which
fits
with
the
way
people
work
as
it
turns
out
so
fabian.
Thank
you
for
proposing
this
and
there's
been
a
fair
bit
of
discussion
about
it
on
the
mailing
list.
A
A
No
questions
no
hand
raising
damn,
I'm
always
trying
for
the
hand
raising
all
right
people
will
be
conscripted,
then,
okay,
not
really,
but
all
right.
Thank
you
baby
in
for
the
updated
info,
and
we
will
try
to
get
this
get
all
the
feedback
incorporated
and
get
you
guys
started
on
a
sick,
I,
don't
hear
anyone
saying
no!
This
is
terrible
or
no
it
overlaps
with
this.
The
Charter
some
other
group
starter
in
a
big
way,
so
I
think
we're
well
on
our
way
to
tuning
it
up
and
getting
it
out
the
door.
A
Maybe
all
right
perhaps
are
having
technical
issues
with
rob.
His
notes
say
that
there
are
new
drawings
for
the
docs,
showing
the
different
layers
of
Cooper
Nettie's,
some
functional
services
and
some
sequence.
Swimlanes
I
will
have
to
look
at
what
the
sequence
fun
lanes
picture
looks
like
and
then
there
is
also
some
work
done
on
a
cluster
fitness
course
that
has
been
sourced
from
Deus
and
there's
a
demo
series
spending
the
next
few
meetings
with
demos
and
discussions.
A
That's
going
to
be
kicking
off,
and
this
is
sick,
cluster
ops
and
perhaps
we
have
audio
now
Rob
or
maybe
not
there's
the
swim
lanes,
and
there
is
a
thursday
meeting
every
afternoon.
I
believe
it
is
1
p.m.
pacific
time
that
that
this
that
sequester
ops
happens
all
right.
If
you
have
questions,
then
I
would
recommend
they
go
to
sequester
office
this
afternoon
Thank.
Perhaps
the
audio
issues
will
be
sorted.
A
No
further
topics
all
right:
well,
we
don't
have
a
cig,
instrumentation,
sorry,
plat
group
and
mailing
list
up
by
the
end
of
the
week.
There
is
a
tune-up
on
docs.
We
will
have
the
docks.
The
new
docks
Zig
me
next
week
and
we
will
continue
to
push
this
all
forward.
This
is
a
lovely
in
short
meeting,
guys.