►
From YouTube: Kubernetes SIG On-Prem Meeting 20170426
Description
Kubernetes Special Interest Group On-Prem Bi-Weekly meeting
Agenda/minutes:
https://docs.google.com/document/d/1AHF1a8ni7iMOpUgDMcPKrLQCML5EMZUAwP4rro3P6sk/edit#heading=h.nrh4k3ck5icu
Mailing list:
https://groups.google.com/forum/#!forum/kubernetes-sig-on-prem
A
A
It's
hard
for
him
to
find
time
to
actually
help
the
chief
we're
looking
for
some
other
members.
So
initially
we
had.
We
have
declarations
from
bottom
with
Nagin
is
here
and
from
here,
but
since
order
is
also
kind
of
engaging
outside
of
on
premise
issues,
we'll
need
to
look
for
some
other
people,
so
I
got
out
yeah
boy
either.
B
A
A
Then
that's
all
practical
side.
I
things
like
from
what
I've.
Obviously
apart
from
the
ink,
is
actually
two
to
four
hours
per
or
two
weeks
right.
So
it's
not
that
much,
but
since
we're
all
busy,
it's
a
lot
of
time
really
so
so
I
think
that
we
still
want
to
run
them
off.
So
there
will
be
some
job
to
do
to
identify.
You
know
me:
certain
projects
talk
to
the
guys
lemma
we
contracted
with
great
lease
that
actually
each
other
prepared
I
think
is
curated
by
James.
A
A
B
A
A
We
get
we
can
actually
offline
both
ideas
and
learn.
Why
for
Marco's
Marcos
also
engage
so
so
even
a
chance
to
speak
out
and
all
I
was
hoping
that
Joseph
will
provide
some
equals,
but
yeah
he's
going
to
be
deep.
I
try
to
get
him
on
the
next
meeting,
alright,
so
yeah.
This
is
business
on
house
for
these
two
weeks
now
so
56
meditation.
So,
unfortunately,
I
was
hoping
to
work
on
the
I.
Had
some
idea.
I.
B
A
Where
we
decided
actually
sync
up
with
the
seat
doc,
so
the
question
is:
is
there
anyone
from
you
know
anyone
familiar
with
the
seat,
doc
work
clothes,
how
they
work,
because
I
at
least
know
that
there
are
some
requirements
for
the
docs
for
the
duplication
right,
it's
not
that
another
spike
or
just
remove
stuff
or
on
which
around
so
anyone.
Anyone
familiar
with
that
workflow.
D
A
A
B
A
A
D
A
D
A
A
Yeah
yeah
so
I
advise
everyone
to
look
at
that
and
think
how
we
could
structure
that
yeah,
it's
a
figure.
The
heart
is
not
here,
because
I
hope
you
already
have
some
idea,
but
we
were
discussing
last
last
week.
You
know
what
should
be
doing
a
nice
healthy
right,
how
you
actually,
how
you
start.
What
is
it
when
you
start
using
the
dog
and
what
we
were
losing
all
right?
A
A
lot
of
people,
the
first
chest
they
do
is
actually
do
brains,
I'm
still
wondering
if
this
is
a
good
approach
to
kind
of
start
with
operating
system.
So
I
believe
that
we
could
kind
of
nice
dive
a
little
bit
and
keep
this
structure
like
on
process
for
all
crime
in
terms
of
assessment.
Oh,
oh
yeah,
that's
like
anything,
let's
think
about
it
and
in
the
meantime,
let's
look
into
the
documentation,
team
workflow
and
try
to
try
to
understand.
H
A
B
H
A
H
G
H
H
H
Know
from
what
I
last
time
I
talked
to
somebody
in
depth
about
this,
which
was
a
plus
six
months
ago.
Now
they
were
doing
exactly
that
markdowns
with
templates.
And
then,
if
you
wanted
specific
types
of
documentation,
you
would
have
to
conform
to
the
templates
and
decompose
the
docs
into
smaller
units,
which
sounds
awesome.
It
just
presented
more
work
than
we're
ready
to
do
so.
When
woo-wee
word
of
Doc's,
we
just
did
it
in
a
big
Google
Doc
quickly.
Recap
percent
was
not
particularly
helpful,
but
that's
sort
of
the
that
was
how
we
started.
A
H
The
promise,
then
you
end
up
with
with
a
vendor.
You
can
end
up
with
a
vendor
dumping
ground,
which
is
we
were
trying
to
avoid.
With
cluster
ops,
we
were
trying
to
write
vendor
neutral
in
small
small
material,
but
the
community
is
not
vendor
neutral
right.
Now,
it's
everybody
installs
using
some
targeted.
You
know,
even
if
it's
I
consider
cargo,
even
those
community
in
some
ways
of
endor
thing,
because
it's
an
opinionated
approach
and
snow,
sorry
I'm,
giving
you
guys
a
whole
bunch
of
size
and
the
audio.
A
Yeah
I
hope
you
have
the
best
name
again,
Lego
of
the
vague
rule
we
could
take.
You
know
we
can
describe
community
support
this
project
or,
like
even
you
know,
that
our
approach
Google
page
projects
about
that
this
will
rule
out
some
of
the
cool
stuff
I
care
about
the
title
or
this
kinda
stuff.
So
yeah
it's
usually
hard
and
it
will
be
hard
I
mean.
Will
they
come
so.
H
H
H
H
A
H
A
A
B
H
A
H
H
We
started
building
and
even
the
title
was
contentious.
We
started
building
this
reference
architecture
document
with
the
idea
that
we
wanted
to
have
it
be
generic,
and
then
we
one
of
the
things
we
did.
Oh,
my
god,
it's
been
in
a
while,
not
bad.
This
January
we
built
an
outline
based
on
the
discussion
of
different
items
that
we
thought
needed
to
be
discussed,
and
so
this
type
of
outlines
pretty
pretty
effective
from
an
architecture.
What
is
production,
the
sense
of
being
a
lot
of
discussion?
H
B
H
So,
there's
a
ton
of
good
graphics
that
we
resolve
it
took
us
a
team
effort
to
resolve
the
graphics.
I'll
show
you
one
of
them.
Oh
no.
This
is
networking.
I
was
still
in
that
one.
We
made
some
progress
on
the
thing,
so
this
this
ended
up
being
an
example.
Nobody
does
it
this
way
anymore,
but
this
is
generic.
So
what
we
would
do
is
we
would
have
a
node
whose
cluster
we
show
how
things
were
connected
either
you
could
see
what
things
were.
H
Services
were
had
ended
up
being
super
helpful
as
a
rallying
point
for
writing
the
docs,
sorry
I'm
back
to
the
wrong
page
and
then
what
we
did
was
we
decided
to
only
document
production
clusters.
So
we
said
you
know
what
we're
not
worried
about
pilots.
If
we
write
documentation,
we
always
target
what
a
production
cluster
is
with
assumptions
and
then
we
went
through
and
said.
These
are
the
things
that
we
expect
in
a
production
cluster.
H
So
we
were
documenting
objectives
for
that
we
started
building
a
lexicon
and
then
the
layers
ended
up
helping
describe
what
things
were
happening
in
each
place.
So
what
we
found
was
we
were
arguing
about
line,
control,
nodes
and
worker
nodes,
and
things
like
that.
It
is
not
being
that
when
you
layer
two,
it
became
much
more
straightforward
for
what
that
meant
boy
and
then
yeah
we
collected
you
know
we're
starting
to
collect
management,
best
practices.
H
We
started
to
build
documentation
at
each
layer
and
then
we
we
put
together
a
template
for
each
section,
so
the
API
service,
which
we
were
going
to
document
we
started
having
a
standard
template.
This
is
where
we
ran
out
of
gas
and
we
were
going
to
try
and
dock
like
port
service,
a
inscriptions
about
each
one
of
those
pieces
years
layer.
Three,
here's
some
configuration.
H
H
H
H
H
Would
if
they
were
attending
so
we
were
doing
some
vlogs
about
it
and
we
were
doing
the
in
cluster.
Ops
was
talking
about
every
week,
so
we
were
taking
about
half
of
every
meeting
to
talk
through
that
those
types
of
changes,
so
a
traditional
cluster
ops
meeting,
would
be
a
certain
amount
of
like
background
business,
hot
bugs
things
like
that,
and
then
we
would
transition
into
trying
to
move
the
docs
a
little
bit
forward.
So
you'd
get
something
like
this,
and
this
evolved
out
of
a
of
a
couple
of
months
of
work.
H
Actually,
we
started
with
some
face-to-face
meetings
and
then
we'd
review.
What
this
looked
like,
it's
all
I
mean,
is
all
give
Cooper
Nettie's
community
property,
so
adding
to
it
and
extending
it
makes
a
lot
of
sense.
We'd
love
to
have
these.
The
graphics
are
still
useful
and
there's
no
reason
that
not
to
use
at
the
climbing
community
so.
A
H
B
H
B
H
H
A
To
have
to
work
with
the
graphics
end
of
the
q-tip
in
biomass,
but
you
cannot
really
pressure
them
whatever
it's
just
much
harder,
so
here's
something
people
avoid
it
right
anyway,
I
agree
with
Matt
that
you
know
the
exposure
for
this
is
critical
and
I
drop
the
seat
on
the
on
the
under
some
committee.
The
documentation
pages
no
I'm,
not
sure.
What
is
that?
What
are
the
rules
to
allow
documentation
to
be
accepted?
A
C
H
H
H
A
I
never
need
it,
but
I
did
a
quick
search
and
it
looks
like
it
has
some
pretty
decent
each
this
option.
Right,
I,
don't
know
you
know,
I,
don't
know
where
the
thing
is
used
to
be
asked
or
whatever,
but
it
looks
like
visually
looks
interesting,
so
I
think
for
doing
the
the
charts
and
dropping
the
set
right
and
we
can
be
useful.
So
you
know
at
least
it
wouldn't
be.
The
blogger
I.
B
A
A
So
so
what
I
think
is
that
we
we
want
to
take
a
look
at
the
documentation,
workflow
processes
procedures
will
ever
so.
We
will
know
a
little
bit
more
next
week.
I
think
we
can
use
it
for
for
all
the
dogs.
For
the
doctor,
you
guys,
you
know,
work
on
asteroids
and
for
the
tree
handle
you
want
to
do
from
on-premise
perspective,
yeah,
so
child
volunteers,
to
kind
of
check
the
process
for
health.
We'll
have
we'll
hear
some
more
on
the
next
week,
cool.
E
A
No
I
think
one
wants
to
knowledge.
Actually
was:
what
are
the
limitations
for
now
across?
We
want
to
something
up
for
the
off-premise
dog,
so
we
need
to
know
what
we
can
do
out
what
we
can
also
because
you
know
there
are
those
deprivation.
All
of
these
I
think
not
only
using
are
pretty
strict
work
calls
for
that.
So
we
just
you
know
we
just
need
someone
that
would
be
kind
of
familiar
with
this
with
this
product.
Okay,.
F
So
do
I
want
to
define
what
we
want
to
put
into
the
dogs
like
I,
think
in
part,
erectus
I,
don't
think
I,
don't
think
we
just
made
a
matrix
or
what
we
can
do
with
people
and
distributions
of
many
pieces.
I
think
we
also
need
something
like
what
works
in
unclaimed
and
what
works.
What
works
under
God
was
an
emblem
or
what
color
we
do
of
the
text
are.
That's
something
I
think
we
should
also
diagram
yeah.
A
D
Think
it
might
be
valuable
to
go
through
actually
all
the
things
that
the
club
provider
integrations
do
currently,
because
you
know
they
provide
a
number
of
different
integrations
or
features
on
AWS
or
Google
cloud,
but
actually
a
lot
of
those
problems.
People
are
solving
in
one
way
or
another
for
very
mental.
You
know,
like
everybody,
is
doing
something
for
ingress
and
that's
because
we
don't
live
by
themselves.
D
Big
I
think
once
we
have,
that
idea
of
you
know,
usually,
storage
integrations
and
ingress
are
the
two
that
come
to
mind
for
what
the
cloud
provider
integrations
are
offering
that's
like
Casa
provider
on
all
the
keywords
and
stuff.
It
might
be
interesting
to
document
first,
just
the
areas
that
the
areas
that
you
don't
get
for
free
on
bare
metal.
Just
because
you
don't
have
those
integrations
and
then
follow
up
with
what
we
would
do
about
it.
Yeah.
A
A
B
D
G
A
H
B
H
D
G
G
D
B
G
B
G
We
have
some
interesting
flakes
better
that
are
currently
being
flying
as
well.
I'd
have
to
go
back
through
and
aggregate
results,
but
I
believe
that
there's
only
three
or
four
that
are
that
are
consistent,
flaky
regarding
like
downward
API
and
some
of
which
require
privileged
container
access,
which
is
interested
in
well
actually
configurable,
but
now,
as
far
as
I
got
the
top
of
my
head,
I,
don't
have
anything
specific,
but
I
think
that
there's
definitely
refers
to
talk
about
that
in
and
continue
down
that
path.
Okay,.
A
G
Now
Thomas
I'm
going
to
help
before
the
Leadership
Committee.
If
it's
like
you
know
not
one
do
doing
leadership
I'd
be
happy.
If
there's
like
a
group
of
us
because
I
it's
to
be
completely
honest,
I'm
just
kind
of
tight
right
and
I'm
trying
to
spread
myself
across
a
couple
things
so
I'm
sure
that
there
are
others
in
this
meeting
that
can
relate
yeah.
A
That's
that's
actually
the
idea
that
was
also
always
so
the
jealous
ideas,
beginning
in
Wilson
talking
about
I
know.
You
know
regular
changes.
Well
then,
where
we
I
will
probably
do
that
so
yeah
that
point
on
I
think
for
marker,
which
is
mark
offending
the
effect
size
is
sweeping
right
now.
Yes,
she
will
be
there.