►
From YouTube: Kubernetes Community Meeting 20170928
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
A
B
B
More
your
grandmother
to
hear
all
right
so
to
get
started
a
first
announcement,
the
kubernetes
1.8
release
burndown
meeting
is
going
on
right
now,
so
all
the
release
team
are
over
there.
If
that
is
important
to
you,
you
should
probably
go
attend
that
so
moving
on
the
release
has
been
delayed,
24
hours
due
to
a
critical
issue
that
was
discovered
for
release.
One
point:
that
is
why
the
burndown
meeting
is
going
on
all
right.
Let's
see
for
the
next,
for
the
other
releases
see
we
have
updates
for
1.7
and
1.6.
D
Right
now,
the
release
team
is
for
anybody
or
anything
I'm
here,
I
just
report
about
it.
We
with
a
face
addition.
We
are
ready
so
it's
Fred
today
and
where
did
you
ship
under
release
today?
I
hope
nothing
will
happen
that
will
make
us
do
the
way
to
unseal
in
so
we're
waiting
for
all
the
final
release
got
at
6
p.m.
Pacific
and
another
announcement.
We
are
going
to
have
one
at
a
trade
from
next
week,
instead
of
the
community
median
on
Thursday.
D
D
D
Thank
you.
Thank
you.
Just
like
security
so
feel
free
to
open
their
Anyang
on
your
local
machine.
So
six
pm
has
been
established
in
the
in
the
first
few
months
of
the
current
year.
It
hasn't
been
absolutely
brand-new.
Six
that
has
been
started
from
scratch.
It
has
been
a
successful
successor
to
the
previously
existing
product
management
group.
This
has
befallen
a
bit
more
than
a
year
ago,
in
the
summer
of
2016,
but
you're
recover
year
that
the
neuron
and
product
management
working
group.
D
C
D
Next
slide,
please
it's
it's!
The
slides
then
can
brain
drain
from
making
it.
Probably
it
can
be
outfitted
and
prepped
it
from
a
from
the
presentation
that
then
has
been
presented
at
the
to
the
next
Leadership
Summit,
a
June,
so
some
pieces
of
this
should
be
a
bit
updated,
but
generally
that
you
can
see
our
place
in
the
general
kinetise
community
ecosystem.
So
beyond
group
is
the
community
wild
group
and
the
project
wild
group.
D
We
are
mostly
we're
not
different
us
as
like
technical
group,
but
we're
working
mostly
on
the
on
the
workplace
on
the
white
project.
Scope
together
is
realistic.
This
country
works
sigdoc,
suggesting,
together
with
newly
formed
I,
think
it's
a
group
and
we
put
on
the
governance,
but
we
actually
are
closely
working
with
with
all
our
six
yeah
and
the
next
slide
please
so
speaking
about
who
we
are.
We
have
three
lives,
actually
being
the
people
who
have
formed
this
group
as
a
sick.
D
It's
a
foreigner
from
Google
help
from
Corizon
myself,
and
we
also
have
a
list
of
seeker.
Presentative
amend
the
list
of
them
on
github
under
the
link.
That's
currently
shared
in
the
slide.
The
sec
representatives
are
people
who
are
actively
participating
in
one
of
multiple
six
and
actually
acting
as
a
bridge
between
our
second
ethics,
so
they're
performing
reporting
on
behalf
of
their
six
over
six
and
also
messaging
from
6:00
p.m.
D
D
Yes,
so
what
do
we
do?
We
were
managing
to
the
edges
as
a
project
and
we
are
managing
to
the
next
as
a
product.
I
will
define
what
they
exactly
do
whiskey
negative
project
a
bit
later
when
well
I
collect
what
we
done
very
little
do
but
initially,
whether
in
cabinet,
this
is
a
product
and
it's
actually
highlighted
in
the
name
of
music,
we're
primarily
private
management,
stick,
that
is
from
primarily
from
people
who
is
product
management
background.
We
are
actively
working
on
cabinet,
Astro
programs.
D
You
may
find
the
links
to
our
last
roadmap
discussions
at
developer
summit
last
year
and
leadership.
Silence.
Half
a
year
ago,
we
were
working
on
the
futures
management
food
ribbon,
edges
I've,
been
a
release
manager
responsible
for
the
feature
for
the
last
few
releases
and
together
with
apartment,
Caleb
and
other
people.
D
We
are
working
on
making
features,
delivered,
discussed
derivative
releases
in
the
community
and
so
on,
and
we
are
probably
one
of
the
main
six
who
is
kind
of
interacting
with
the
marketing
area,
we're
primarily
interacting
with
CN
CF
marketing,
with
the
renders
marketing
with
third-party
marketing
initiatives,
organizations
and
so
on.
So
if
you
may
see
any
information
about
kubernetes
roadmap
to
be
honest,
terminate
this
product
strategy
to
be
latest
features.
You
may
give
me
notice
our
names
there
next
slide,
please.
So
what
do
we
are
primarily
do
not
contribute
code
to
kubernetes.
D
It
doesn't
mean
that
we
don't
deliver
anything
technical
to
the
nest
at
all.
All
of
us
have
some
technical
background
or
to
describe
images,
but
our
primary
primary
responsibilities
managing
these
things,
and
we
would
like
people
with
deeper
technical
knowledge
and
deeper
technical
experience
to
do
coding,
but
at
the
same
time
it
doesn't
mean
that
we
don't
do
anything
technical
for
communities.
We
do
not
manage
the
venegas,
as
a
community
organization
will
be
like
steering
committee.
That
is,
this
selection
is
ongoing
and
real
soon
until
the
front
would
like
certain
committee
to
do
this.
D
We're
like
also
people
who
are
designated
for
the
Scrolls
to
directive,
an
intercessor
community
community
people,
community
organizations.
So
we
don't
manage
cabinets
as
a
group
of
people.
We
are
managing
to
Panetta's,
primarily
as
technical
technical
product,
and
we
don't
manage
to
the
next
release
itself,
because
we
have
the
designated
secret
list
for
managing
release
cycle,
deletes,
whose
process,
but
again
we're
actively
involved
into
the
release
process,
especially
from
the
features
perspective
from
the
release,
notes
perspective,
interacting
with
marketing
people
and
so
on,
and
a
few
links.
D
D
But
unfortunately,
sometimes
our
meetings
were
overlapping
with
CMC
FTO
city
meetings,
and
so
many
people
had
to
decide
which
meeting
to
attend
and
it
was
it
was
not
so
good
for
football
meetings
for
CN,
CF
TOC
and
for
our
meetings
so
since
since
sometimes
EMC
FDIC's
meeting
Everest
and
such
Tuesday
of
Mansouri.
So
we
are
meeting
every
second
and
first
reason.
It's
exactly
the
same
time
same
place.
You
might
find
a
meeting
notes
an
agenda
right
here
in
the
slides
together
we'll
is
there
a
record
recordings
going
to
hit
you?
D
E
D
Welcome
terrific
for
us,
actually,
we
are
going
to.
There
has
been
a
proposal
for
us
to
run
some
very
great
respect
for
the
implement
and
probably
reformatted
it's
what
they're
currently
doing
the
same
time.
Any
any
suggestions
regarding
how
to
drive
to
the
native
to
the
product,
how
to
directly
next
to
the
project
and
and
institutions.
From
from
your
personal
experience,
exactly
welcome.
So
our
agenda
is
open
to
prepare
us
and
we'll
discuss.
D
The
end
of
the
grade
is
great:
cool
thanks,
Judith
is
needs
to
learn,
are
the
meetings
now
meetings
are
happening
exactly
at
the
same
time
in
the
same
place
on
Tuesdays,
it's
8
a.m.
Pacific
time,
but
we
are
now
eternity
in
our
CN
CF
GOC
meetings.
So
every
second
and
every
first
used
eight
months,
there's
double
check
your
calendar.
If
you
subscribe
to
keep
in
ssbm
group,
you
should
receive
feel
you
like.
If
you
haven't
closed
to,
do
acceptance
and
it.
B
Great,
thank
you
very
much
Igor.
If
you
have
any
further
questions
or
post
them
in
the
chat
later
yeah,
all
right
so
on
to
me
for
sig
auto-scaling.
So
for
1.8,
we
successfully
managed
to
graduate
auto-scaling
version
to
a
pi/2
beta.
So
there's
now
be
two
beta
one
that
will
be
on
by
default
data
and
the
related
metrics
API
is
the
custom
metrics
API
and
the
master
metrics
API.
C
B
B
C
A
And
then
I
dropped.
One
more
note
in
announcements,
which
is
the
coop
con
schedule
with
a
naps
today
and
cloud
native
con
schedule
is
announced
today
so
share
that
content.
However,
you
share
content.
Get
people
excited
about
it.
I
hope
you're
excited
on
it
already,
but
if
you're
not
get
excited
about
it,
because
it's
coming
and
we're
gonna
have
tons
of
special
interest
group
work
associated
events,
the
is
there's
going
to
be
an
sto
day,
there's
going
to
be
the
communities
dev
summit,
Tuesday
Tuesday
kubernetes
dev
summit.