►
From YouTube: 2017-04-11 17.00.46 SIG-cluster-lifecycle 166836624
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
D
C
E
C
A
C
So
you
can
see
we
can
see
the
containers
from
here
so
very
important
that
you
get
a
good
view.
The
conveyance
on
your
office
there's
memory
near
nice.
Oh
yeah,
hi
I,
like
that
yeah
I'm,
a
33rd
floor,
see
that
that
20
building
there
that's
Bob
wises
office
over
there.
He
has
one
office
over
there,
hi
mom.
This
is
the
black
one.
There
is
the
columbia
tower,
which
is
the
tallest
building
west
of
the
Mississippi
and
north
of
San
Francisco.
So
there
you
go
very
cool.
F
F
So
I'm
a
are
we
the
solid
we've
done
many
people.
Ok,
so
I've
got
a
draft
out
for
the
post-mortem
of
16
s
released
for
cube
admin,
and
I
only
added
this
to
the
agenda
like
yesterday.
So
I
doubt
anyone
had
time
to
read
it.
So,
just
a
broadcast
I'm
looking
for
more
feedback,
I
got
feedback
on
the
initial
notes
and
timeline
that
I
had
thanks.
F
People
provided
feedback
there,
and
so
now
it's
I
wouldn't
say
it's
close
to
a
final
draft,
but
I'm
there's
still
some
sections
need
to
be
fleshed
out
of
World
War,
but
I
think
it's
to
the
point
where
I'd
like
more
eyes
on
and
get
more
feedback
on
it.
Although
Robert
did
a
drive-by
last
night
and
gave
me
kind
of
the
feedback
and
I'm
already
trying
to
pack
comfort
now
and
that's
it.
B
F
Some
of
it
is
I
mean
some
people
can
bring
the
bring
the
aspect
of
making
sure
that
it's
accurate,
but
also,
even
if
you
weren't,
involved,
looking
at
the
timeline
and
the
what
went
wrong
and
reasoning
about
what
our
reasonable
action
items
is
also
really
important,
especially
since
we're
going
to
need
cig
owners
for
them
we're
actually
going
to
try
to
follow
through
on
them.
So
even
if
you
didn't
have
a
hand
in
it,
even
if
you
weren't
a
part
of
that,
you
could
still
give
it
back
on
great.
B
That's
a
bit
more
consumable
by
people
who
weren't
in
the
meeting
I've
also
drafted
a
very
rough
sketch
of
what
see
you
I
might
look
like
or
UX
for
the
CLI
at
least
and
I
literally
just
made
this
up.
So
please
take
a
look
and
give
early
feedback
on
the
on
the
drafts
and
it
really
isn't
finished
yet.
There's
the
the
documents
are
a
local.
A
Just
want
to
mention
that
I've
been
brainstorming,
some
ideas
about
high
availability
in
the
KU
bed
and
world,
with
a
bunch
of
changes
that
we
have
been
percolating
across
the
community
and
try
to
get
them
distilled
into
what
we
would
want
to
do
reports.
Is
it
possible
for
us
to
kind
of
separate
out
high
availability
in
two
separate
respect
that
you
get
happy
to
work
on
it
together?
It
just
seems
like
those
are.
Two
very
large
pieces
should
probably
be
disentangled
absolutely.
B
So
the
goal
with
the
h,
a
design
section
of
this
document
was
just
to
convince
ourselves
that
there
was
a
path
forward
with
the
design
that
we
have
planned
for
self-hosting
and
upgrades.
It
wasn't
to
design
the
ultimate
a
che
implementation
for
cube
admin
and
it's
a
specific
non
goal
to
actually
deliver
that
in
17.
B
A
C
Do
we
want
to
go
through
the
17
planning
stuff
so
so,
prior
to
this
meeting,
there's
a
cig
p.m.
meeting
I
wasn't
able
to
attend,
but
there's
a
it
looks
like
things
are
getting
more
formal
in
terms
of
proposing
features
and
actually
having
those
things
locked
down.
You
know
on
a
timeline
and
then
have
that
stuff
be
recorded
up
through
cigs,
so
just
to
to
sort
of,
you
know
make
sure
that
we
get.
You
know
eyes
on
stuff.
That's
going
to
impact
lots
of
folks,
so
that
doesn't
sound
like
dad.
C
Comfrey
head
tends
to
happen
with
these
things,
so
I
think
it
may
make
sense
for
us
to
sort
of
call
our
shots
in
terms
of
the
stuff
that
we
want
to
try
and
get
done
for
17.
We
can
take
that
document
and
then
and
then
you
know
just
make
sure
that
that
anything
that
anybody
wants
to
get
done,
we
get
the
right
stuff
into
the
feature
repo
in
time
to
be
able
to
make
it
happen.
B
B
C
B
C
C
The
one
thing
I
do
want
to
do
myself
is
get
some
of
the
release
stuff
into
shape
so
that
we
can
build
our
own
releases
so
that
we
can
test
this
stuff
out
truly
end
and
before
release
time,
so
that
can
help
you
offer
it
out
and
and
tin
can
sign
ups
it
to
at
least
I'm
not
going
to
put
words
in
his
mouth
but
but
drive
towards
the
design
doc
for
4h.
A
that's
great
awesome.
B
C
Well
and
I
think
there
might
be
something
like
a
dark
in
terms
of
the
texts
that
like
architecture
of
how
a
che
works
and
then
what
is
the
u.s.
that
we
want
to
really
present
to
users,
and
we
may
find
that
there's
other
stuff.
We
need
to
do
to
be
able
to
make
the
UX
really
work.
Yeah
I
am
worried
about
things
like
certificates
and
stuff,
and
you
know,
are
we
going
to
stick
those
in
SCD?
C
That
seems
like
a
bad
idea,
especially
the
certificates
that
you
use
to
talk
to
SCD
or
not
gonna
put
those
in
that
CD.
So
that's
that's
something
that
we're
going
to
have
to
that.
We're
going
to
have
to
figure
out,
and
that's
mainly
aux
thing
I
think
I
mean
like
in
the
design
we
can
say:
hey.
You
must
have
certificates
on
each
machine
right.
Okay,
like
that,
that's
a
good
technology.
You
know
sort
of
forward
thing
but
from
a
UX
point
of
view
that
it
subpoena
pain.
B
A
C
I
think
you
know
it's
just
a
matter
of
of
you
know.
If
there's
not
a
name
on
it,
then
it's
out
its
kind
of
how
things
work.
Let's
see
the
first
thing
on
the
list
is
component
in
fig
and
mike
has
his
name
next
to
that,
Mike
are
you
you
know?
Obviously
this
is
going
to
be
a
group
effort,
but
are
you
up
for
driving
this?
C
Yes,
production-ready
cube
admin
I'm,
not
sure
that
this
is
a
feature
in
terms
of
sort
of
a
long-term
goal.
C
B
C
C
C
C
C
C
A
feature:
okay,
okay,
so
I
think
I
think
one
thing
that
might
be
interesting
here
is
to
really
get
crisp
about
what
the
stories
are
in
terms
of
how
images
get
to
machines
and
make
sure
that
we
have
a
good
way
of
testing
that
so
I
feel
like
we're
not
quite
to
the
level
where
we
have
a
feature
here.
But
we
have
to
do
some
design
work
for
figuring
out
what
the
features
might
be
to
get
crispier.
That
kind
of
where
we're
at
sounds.
G
C
The
cube
admin
guide,
I
hate
that,
though,
I
got
to
be
honest,
because
it
means
that
we
have
to
do
a
doc's
thing
every
time
and
you
have
to
copy
and
paste
that
stuff.
I
think
the
tools
should
be
able
to
report
itself.
What
is
the
manifest
of
images
that
it
needs,
but
I
get
down
as
much
can
I
might
be
able
to
actually
sort
of
sneak
in
I.
Don't
think
that
sort
of
full
feature
level
I'd
think
oh
yeah.
B
B
C
G
C
I
saw
I'm
some
issue
that,
or
maybe
I
forget,
where
I
saw
some
really
interesting
ideas
about
sort
of
you
know:
version
dependency,
management,
strings
and
predicates
sand.
All
that
are
you
going
to
put
that
together
into
something
that
looks
more
like
a
design
doc
that,
like
more
folks,
can
get
their
eyes
on
if.
G
B
Thing
on
on
a
che
is
that
like
I,
while
I,
do
think
it's
sensible
to
have
it
as
a
non
goal
for
17.
If
it
turns
out
that
the
self
hosting
stuff
lends
itself
to
this
being
easy
and
it's
possible
then-
and
you
can
have
some
instructions
for
how
to
do
it
than
like
happy
days.
I.
C
My
guess,
though,
is
that
there's
going
to
be
a
lot
of
nitty-gritty
sort
of,
like
you
know,
ux
thing
that
we're
going
to
want
to
work
through
there
to
really
make
that
scenario
where
we
want
it
to
be
so
maybe
we'll
be
able
to
have
some
sort
of
like
rola
fiercely
it's
alpha
type
support
in
17.
If
things
come
together
great,
but
but
we're
not
going
to
get
it,
my
gut
is
we're
not
going
to
get
it
where
we
want
it
to
be
yeah
I,
agree.
C
C
H
B
I
H
H
I
think
that
the
there
was
an
email
thread
going
around
with
other
sig
leads
and
they
had
agreed
previously
requested
insane
cluster
life
cycle,
so
I
think
it.
It
is
up
to
whoever
I
don't
think
we're
planning
on
implementing
any
of
these
and
other
components.
I
think
the
plan
is
to
write
a
guideline
on
how
to
implement
and
hopefully
get
it
ratified
by
other
cigs
and
have
other
states
implement
that.
So
we
have
a
consistent
view
of
how
contagious
manages
across
career
noise
components.
Yes,.
A
C
C
C
C
C
Okay,
so
and
there's
nothing
you
don't
accept,
it
I
mean
eyes
just
a
matter
of
making
sure
that,
if
somebody's
doing
work
we
don't
want
them
to
not
have
a
home
and
feel
like
they're,
not
getting
the
support.
They
need
to
get
their
work
done
right.
So
I
think
you
know,
I
think
it's
reasonable
or
it's
a
show
up
here,
I
mean
as
much
as
anything
else.
G
C
C
G
B
C
G
C
G
B
Yeah,
so
can
we
can
I
suggest
that
the
target
of
this
exercise
to
begin
with
the
choosing
a
solution
page
on
the
given
issue
stock.
B
B
B
Think
that
the
actually
just
looking
at
this
page,
looking
at
the
docs
homepage,
it
seems
like
people
like
well
as
a
selection
of
projects
here
that
I've
at
least
wanted
like
wanted
to
be
visible
enough,
that
they
have
put
themselves
on
this
list.
So
there's
mini
cube,
cops,
ki,
beti
m
and
cargo,
and
then
picking
the
right
solution
is
like
a
graveyard
everything
else.
The.
G
B
C
G
It
you're
joking,
but
like
the
ideas
that
we
would
have,
one
page
which
is
like
here
is
the
universe
of
everyone
no
bar
to
getting
onto
it,
and
then
here
is
the
ones
which
are
like
more
maintained.
I,
don't
know
more,
whatever
is
I
would
love
it
to
be
as
they
pass
conformant
stats,
because
that
feels
objective
and
fair.
B
C
B
The
criteria
we
were
going
to
use
was
like
has
upgrades,
I.
Think,
okay,.
J
B
C
Here's
what
I'm
going
to
say
is
that
as
I
think
the
first
step
here
is:
let's,
let's,
let's
discuss
what
we
think
the
criteria
are
in
terms
of
like
I
would
view
this.
Sig
is
owning
that
part
of
the
docks-
okay,
let's
just
let's
just
put
that
out
there,
like
we
own,
like
as
users,
come
on
board.
How
do
we
steer
them
in
terms
of
how
do
they
create
manage
a
a
cluster
right?
I
think
the
first
thing
is
for
us
feeling
like
we
actually
have
the
authority
to
go
in
and
cure
rate.
C
C
Like
I
think
just
of
the
gate,
I
think
that
that
you
know
having
a
couple
of
solutions
for
super
easy
to
get
up
and
running,
but
not
necessarily
production-ready
and,
I
would
say,
mini
cube
and
cube.
Admin
right
now
are
sort
of
in
that
and
that
layer
I
think
pointing
at
the
the
you
know.
C
Cloud
providers
like
gke
an
azure
makes
a
ton
of
sense
because
that's
super
easy
to
get
people
up
and
running
also
and
then
and
then
essentially
you
know
systems
that
have
wide
wide
support
and
then
have
and
then
have
a
list
of
like,
but
you
know
current
Eddie's
a
super,
flexible
tiers
of
laundry
list
and
I'm
sure,
whatever
we
do
we're
going
to
piss
people
off
and
so
I
think
a
good.
You
know.
A
good
way
to
start
here
is
to
have
a
is
to
have
a
some
sort
of
rules.
B
B
G
C
C
I
signed
myself
up
for
that:
okay,
yeah,
that's
a
hot
potato,
but
I'll
start
a
doctor.
I'll
work
with
Justin
on
this
because
I
think
he's
a
he's.
Passionate
also
I
was
like
a
hold
Justin
consult.
C
C
Apart,
we
just
both
like
to
argue
yeah.
That's
just
okay,
okay,
put
me
down
for
it
it's
a
short
week
for
me.
That's
why
I
have
a
hard
time
signing
up
for
it,
so
I
may
not
get
it
done
before
next
week,
but
at
least
as
well-
and
this
is
me
paying
my
pendant
by
actually
helping
to
make
the
docks
better,
because
I
bitched
loudly
and
now
I
got
I
know
I
got
to
actually
follow
through
right.
B
I
responded
to
you
Joe
arm
and
then
the
last
one
is
in
actually
before
we
move
on
to
this.
One
I
was
reminded
by
the
extract
cloud
provider
code
of
a
question.
I
have
a
question:
I
saw
a
user
asking
earlier
today,
which
was
how
do
I
get
this
cube,
ATM
stuff
to
work
with
a
cloud
provider.
They
took
away
the
cloud
provider
flag.
What
do
I
do?
G
C
Even
if
it's
not
about
setting
the
cloud
provider
flags
but
there's
also
some
other
level
of
stuff
and
I
could
see
us
having
something
like
oh
you're,
running
on
eight.
You
know
you
specify
the
AWS
will
let
us
do
a
quick
probe
to
see.
If
you
have
you
know
sufficient
I
emerald
set
up
so
that
things
will
work
so
you're
not
going
to
have
a
bad
time
in
the
future.
Right
like
like,
we
can
build
that
into
the
prereqs
I.
C
Think
the
question
here
is:
how
do
we
do
that
in
a
way
that
is
doesn't
turn
into
a
big
kitchen
sink
like
the
cloud
provider
is
right
now
Cooper
Nettie's
right,
because
I
don't
think
we
want
to
get
ourselves
into
that
into
that
bucket.
So
I
think
we
can
do
cloud
provider
integrated
things
without
doing
provisioning.
Does
that
make
sense,
yeah.
B
C
I
mean
like
at
the
very
least
we
can
take
like
I
give
this
for
the
AWS
stuff.
You
know
help
you
know
work
with
the
cloud
provider
stuff
to
actually
document
what
are
the
requirements
for
using
this
cloud
provider?
How
do
you
set
it
up
that
type
of
thing,
even
if
we
don't
actually
have
code,
having
some
good
docs
about
how
you
actually
go
through
and
do
this
is
not
crazy,
yeah
I.
B
G
C
C
C
C
B
B
B
I
B
B
C
I
haven't
quite
oh,
I
just
realized.
Okay,
you
can
see
the
light
bulbs
go
off
right
above
my
head
chris,
who
spend
like
working
so
hard
on
the
AWS
stuff.
Now,
if
it
works
for
Microsoft
I'm
sure
this
has
occurred,
everybody
else,
but
that
just
sub
Solarius,
okay
I'm
sure
we
can
find
somebody
from
let's
get
some
of
that
stuff
in
and
then
will
lob
a
grenade
it
Brendon
and
see
what
he
does.
B
F
F
Know
who
tagged
my
name
on
that,
but
what
I
had
done
is
it
started
documenting
all
of
the
nitty
gritty
details
that
I
think
we
kind
of
I.
Don't
think
anyone
really
dug
into
the
ramifications
that
happen
when
you
move
into
your
own
repository
so
like?
How
do
we
handle
just
getting
the
release
notes
working?
What
box
do
we
need
to
enable?
What
do
we
do?
Thank
you
all
that
stuff,
so
I
started
looking
into
it
and
then
I
think
what
things
mean
a
few
people
kind
of
said.
You
know
cute
cuddle.
F
It
has
a
superset
of
the
problem
that
we
do
and
they're
already
trying
to
move.
So
we
should
really
put
the
brakes
on
this
and
figure
out
what
they
can
do.
I
still
want
to
figure
out
how
will
be
affected,
and
then
we
might
have
problems
that
aren't
solved
by
Cupid.
Well,
with
your
mark,
these
articles
expect
to
cuddle
to
solve
and
maybe
help
drive
some
of
those
things,
but
it's
definitely
a
nominal
to
actually
execute
the
move.
The
17
time
frame,
I,
don't
good
breather
before
cube
puzzle.
F
The
second
one
I
think
Derek
Mackay
I,
think
he's
online
because
we
have
here
excellent,
so
I
don't
know
if
it's
going
to
continue
to
drive
this,
but
I
also
expect
us
to
have
more
items
here
that
our
action
items
from
the
post
mortem
that
we
just
kind
of
have
to
have
consensus
and
better
safety
mechanisms
going
forward,
making
sure
it's
much
easier
to
do.
Anyone
Testament
it's
actually
enforced
and
we
have
release
process.
We
don't
just
kind
of.
Let
it
release
happen.
B
Okay,
so
there's
some
other
items
here,
continue
improving
unit
and
integration
test
coverage
and
make
end-to-end
testing
it
over
developer,
build
trivial
anyone
signed
up
for
either
of
those
items
invitation.
J
So
I've
been
continually
working
on
the
unit
and
integration
test.
I
I
kind
of
have
been
swamped
the
last
couple
weeks
with
some
changes,
but
the
with
end-to-end
testing
I
know
I,
actually
haven't
even
hooked
up
with
Jacob
to
see
what
happened
with
his
intend
test,
I've
been
kind
of
out
of
it,
but
to
move
forward
and
start
doing
the
Q
admin
specific
end-to-end
test.
So
that's
not
something
that
I'm
working
on
I
have
lots
of
PR
its
open
and
merged
for
just
adding
unit
tests
and
whatnot
and
integration
tests.
J
F
Yeah
so,
and
and
I
put
the
idea
of
trying
to
make
it
completely
trivial
to
run
the
NN
test.
I
love
that
I
think
it's
a
very
noble
goal:
I,
don't
know!
If
we'll
get
there
this
release,
you
can
certainly
put
my
name
next
to
it,
because
I've
been
working
on
those
I'm
still
still
figuring
out
if
I
have
other
obligations
within
google.
So
I
don't
know
if
I
can
sign
up
14
delivered
in
won't,
tell
me,
but
certainly
going
to
try
to
get
incremental
e
better
with
everything
go
right
to
end
to
end
testing.
C
So
I
I,
just
want
to
echo
I
mean
in
my
mind
and
I.
Don't
want
to
be
a
broken
record
here
is:
is
that
to
a
lot
of
folks
outside
of
Google?
The
end
end
stuff
and
just
see
feels
so
big.
It's
just
not
really
clear
where
to
catch
a
corner
and
start
getting
involved
in
that
also
within
google,
and
I
know
I
mean
I'm
not
sure
how
to
solve
that,
but
I
think
you
know
anything
we
can
do
to
start.
C
H
Love
some
records
there,
I
just
I,
want
to
find
a
way
to
help.
What
do
you
say:
Mike,
I'm,
sorry,
Oh,
we'd,
love
suggestions
on
how
to
improve
this.
We
also
have
federated
testing.
So
if
you
guys
can
get
funding
to
run
your
own
ends
and
testing
I
think
the
ownership
project
ownership
is
look
really
hardest
right
now.
That
would
be
great
and
yeah.
C
J
I
G
Some
great
changes
made
their
recently
choice.
It
is
easier
to
run
the
test
and
it
also,
I
think,
correct
me
if
I'm
wrong
people
to
know
much
better,
it
feels
like
we're
moving
towards
running
things
in
bear
cooper
and
eddies,
rather
than
jenkins.
I've
seemed
like
PRS
at
point
in
that
direction.
Yes,
yes,
we
are.
C
H
C
I
guess
what
I'm
thinking
about
is
it's
like
very
simply,
is
there
a
page
someplace
that
actually
has
pointers
to
prowl
and
an
urban?
You
know
ruminator
and
tested,
you
know
and
the
you
know
the
test
grid
and
then
actually
talks
about
what
purposes
behind
each
of
these
things
so
that
users
can
find
these
dashboards.
That's
a
good
question,
I'm
not
sure
so.
G
C
Would
be
that
would
be
awesome?
Okay,
so
Allah,
okay,
okay,
very
cool,
oh
she's!
At
kora
lesson,
that's
the
kala
the
same
yes,
because
as
we
bring
new
people
into
hefty,
oh
it's
like.
How
do
you
find
me
think,
then
it's
all
word
of
mouth
right,
so
I
think
trying
to
kind
of
bring
that
together.
It'd
be
great,
very
cool.
B
B
B
So
just
a
reminder
them
everything,
everything
that
we
actually
do
want
to
get
into
17
if
you're
signed
up
as
an
owner.
For
that,
please
get
features
into
the
features
repo'd
before
April
26
and
we
need
to
get
code
and
tests
and
docs,
presumably
into
the
repo
by
during
first.
So
that's
not
long
now
so.
C
B
E
B
E
B
E
B
C
Was
going
to
say,
like
you
know,
if
it
doesn't
touch
sort
of
the
corcoran
Eddie's
repo,
then
we
have
a
lot
of
freedom
to
experiment
and
see
what
works
and
I
don't
think
we
have
to
follow
a
very
formal
process
around
this
I
think
the
more
we
move
this
into
the
Gubru
Nettie's
Rico
proper,
the
more
we
expect
this
to
line
up
with
the
Cooper
Nettie's
release
timeline
the
more
we
expect
this
to
be
sort
of
official
and
and
part
of
the
relief
packages.
Then
the
more
formal
things
need
to
be.
G
I
can
just
mention
so
in
carson
is
we
are
obviously
working
on.
I
am
that's
not
really
particularly
relevant,
I
think
to
life
cycle
other
than
that
were
worth
going
to
be.
The
other
thing
which
is
coming
up,
but
I,
don't
really
want
to
deal
with,
is
like
management.
The
best
TV
clicking
the
system
operator
like
one
it
doesn't
depend
on
communities.
G
We
are
not
putting
33
in
cops
because
the
upgrade
is
problematic
and
we
need
backups
and
we
need
all
those
things.
Let's.
It's
certainly
something
that
we
really
need
the
F
to
the
operator
to
work
without
requiring
crib
amenities
and
I.
Don't
know
if
I'm
gonna
have
time
to
work
on
that,
but
it
does
feel
like
very
much
a
cig
cluster
life
cycle,
there's
only
well
relax
with
the
list
of
York
you're
doing
is
a
cluster
life
cycle
or
I
want,
is
to
need
to
customize.
B
B
B
All
I
was
going
to
say
was
just
that
I
think
it's
great
I
think
it's
a
really
useful
thing.
I
think
you
should
make
a
PR
into
the
key
baby
em
repo
Oh,
like
ideally
with
a
go
line
version
if,
if
you're
working
on
that
and
I
would
be
supportive
of
it
I
but
I,
don't
think
it
needs
a
feature
in
the
features
repo,
because
it's
not
really
user
facing.
It
could
be
something
that
some
users
might
want
to
use
for,
like
local
development
and
well.
B
E
Yeah,
it's
useful
for
Cuba
latest
development
that
can
also
be
useful
for
projects
that
extent
q
Burnett
is
because
it
runs
easily
or
say
on
Travis
CI
I'm,
like
mini
cube,
it
does
not
need
Method
visualization,
it
quite
lightweight,
and
the
idea
is
that
I
discussed.
It
is
look
Lucas
during
cube
com.
The
idea
is
that
I
submitted
this
proposal
and
someone
please
review
it
because
I'd
like
to
see
whether
what
features
are
really
necessary
before
actually
writing
the
same
thing
go
and
make
and
a
PR
for
you
by
diem
with
the
code
cool.