►
From YouTube: 20180424 sig cluster lifecycle
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
Hello
today
is
April
24th.
This
is
the
broader
Sigma
and
lifecycle
meeting,
and
we
don't
really
have
a
lot
of
agenda
topics
for
today,
but
we'll
feel
free
to
the
free
forum.
If
you
have
things
want
to
discuss,
I
was
going
to
give
an
overview
of
some
of
the
at
least
stick
from
the
comedian
perspective.
Some
of
the
1:11
updates
of
where
we're
at
and
I
would
also
like
to.
A
Is
there
anyone
else
from
cluster
API
here
I,
don't
see
other
cluster
API
folks
here
I'd
like
to
get
a
tldr
from
those
folks
too,
at
some
point
in
time
to
get
a
summary
and
synopsis
of
what's
going
on
there,
we
do
have
a
lot
of
broader
sub
projects.
I,
don't
know
if
other
folks
wanted
to
give
other
updates
for
other
sub
projects
too
as
well.
A
It
might
be
more
broadly
useful,
so
my
update
for
for
111
is
we're
kind
of
burning
down
the
backlog,
discovering
some
things
that
were
kind
of
unexpected
items
with
configuration
and
unexpected
items
with
upgrades,
but
I
think
we
have
a
bearing
on
fixes
for
the
upgrades
to
back
port
for
110.
They
should
be
coming
soon.
We
already
have
some
of
it
birch
to
the
other
ones.
The
PRS
are
up.
A
B
A
Do
we
need
to
write
up
caps,
for
them
are
the
biggest
ones
are
I
would
call
them.
I
will
dub
them
grand,
unified,
config
and
add
the
second
one.
I
will
dub
as
as
a
sentinel
for
self
hosting,
so
I
need
to
do
the
signal.
First
self,
hosting
one
and
I
know
that
Liz
was
working
on
the
grand
unified
config
one
and
we're
going
to
talk
about
that.
Probably
tomorrow
the
reason
for
grand
unified
config
is
we
don't
really
have
it
all
documented?
It's
not
been
all
pushed
to
beta.
A
We
should
do
this
and
we
should
vet
it,
and
we
should
make
sure
that
we're
addressing
all
the
concerns
that
can
occur
for
configuration
for
all
the
multiple
incantations
that
we
can
do
for
deployment.
So
my
goal
is
to
have
the
caps
in
place
this
release
cycle,
as
well
as
like,
as
well
as
all
the
people
who
are
starting
to
burn
into
this
area,
to
understand
the
entire
state
space
and
how
we
want
to
refactor.
It
wait
for
words.
I
know
that
Fabricio
is
doing
a
lot
of
work
on
the
master
join
stuff.
A
That
was
from
last
cycle
into
the
cycle,
but
some
of
that
grand
unified
config
will
be
affected
by
master
join
right.
There
they'll
be
linked.
I
know
that
Matt
had
a
proposal
there,
but
we
need
to
suss
out
the
configuration
problems
that
are
currently
occurring
because
they
kind
of
they're
not
isolated
to
one
space.
They
occur
across
the
whole
upgrade
scenario
and
they
would
they
would
affect
H
a
master
join
scenarios,
we're
close.
A
A
A
Don't
think
we
are
I,
purposely
kind
of
avoided.
The
whole
feature
process
thing.
This
release,
I,
look
because
we
have
so
many
open
feature
issues
that
kind
of
all
percolate
to
pieces
that
we've
been
working
on
for
several
releases,
that
I've
I'm
just
punting
on
the
notion
of
creating
new
features
in
the
features,
repo
and
I'm,
going
to
focus
instead
on
just
writing,
proposals
that
are
executable,
tangible
and
that
people
couldn't
understand.
Okay,.
B
A
C
A
It's
true
the
I'm
gonna
talk
with
the
cig
release
team
I
have
some
choice,
words
about
what
it
means
to
have
a
release,
because
we've
been
releasing
a
bunch
of
stuff
that
has
never
passed
all
the
tests
and
we
always
get
into
these
weird
scenarios.
Where
right
now,
we've
spent
a
lot
of
1/10
the
first
weeks
of
1/10,
basically
fixing
bugs
from
the
release
that
we're
users
have
come
back
and
they've
been
like
these
things
are
broken
and
I
want
to
prevent
that
from
occurring
again.
A
The
problem
with
this,
the
big
upgrade
ones,
the
ones
that
we
dealt
with
this
cycle,
were
a
result
of
the
up
screen,
the
upgrade
test
suite
for
qadian
being
totally
busted,
and
it
wasn't
with
cuvee
diem
itself.
It
was
with
it
was
the
entire
jiggery
and
no
one
owning
it
and
my
goal,
this
cycle
is
to
basically
have
to
fall
on
the
sword
and
own
it,
at
least
for
at
least
until
we
have
a
replacement
I,
don't
particularly
like,
what's
there
and
it's
very
difficult
to
debug,
but
it's
what
we
have
for
the
time
being.
A
D
D
Have
found
cube
test
itself
to
be
fairly
easy
to
understand.
It's
the
mechanics
around
cube
tests
that
I
found
more
complicated
but
I
think
that's
Lily's
mechanics
around
cube
tests
are
being
simplified
or
rationalized.
So,
if
you
want
to
run
it
on
your
own
yeah
I'm
trying
I'm,
also
trying
to
like
make
get
more
testing
in
like
I'd
love
a
you
know
like
a
cops
roaming
update
tests
and
yeah
I
figure.
How
to
get
that
into
the
EDM
structure
is
indeed
tricky.
Yeah.
A
A
B
A
We
talked
about
it
originally,
but
the
only
times
we
could
actually
get
a
separate
meeting
room
was
during
the
evening
and
it
was
really
difficult
for
us
to
kind
of
rationalize
people
wanting
to
come
back
in
the
evening
to
want
to
do
this.
But
what
I
was
proposing
to
was
to
do
an
informal
type
of
thing
during
that,
if
you're
going
to
be
there
for
the
contributor
meetings
that
possibly
just
do
a
hallway
talk,
you
know
for
whatever
time
period
that
we
think
is
reasonable.
A
You
know
and
just
find
a
separate
room
to
discuss.
That's
probably
the
best
time
to
suss
it
out
cuz
a
lot
of
times
that
you
know
I've,
I,
won't
say
disparaging
things
and
menu,
but
the
contributor
somebody
has
it's
questionable
content,
and
sometimes
the
hallway
banter
is
a
higher
value.
I
found
I'm.
B
B
A
It
is
all
day,
I
believe,
there's
a
morning
track
in
an
afternoon
track.
So
if,
if
we
want
to
like
have
a
informal
sort
of
sing,
Questor
life
cycle
gathering
in
the
afternoon
time
for
me,
I'd
be
happy
to
do
that.
I'm
sure
I'll
probably
prefer
to
talk
about
things
that
we
can
do
at
that
point
versus
the
paint
shades
and
the
the
bike
shed.
I
know
how
we
can
make
things
more
better
in
the
community.
A
B
A
B
D
D
You
know
we
grapple
with
them
in
cups,
but
they're
not
really
cups
issues,
things
like
sed
management,
add-ons
management
or
those
so
I
think
it's
I
think
it's
primarily
on
me
to
get
it
to
a
point
where
I
can
bring
it
to
the
sake,
but
I
would
love
to
Wow
or
anyone
else
obviously
wants
to,
but
I
mean
I'm
voting
myself
rather
than
opposing
the
city,
but
I
would
love
to
have
you
know
the
opportunity
to
discuss
some
of
those
items?
It's
like
you
come
and
then
going
forwards
at.
A
Playbooks
is
an
actual,
like
you
know,
step
by
step
process,
not
an
actual
like
ants,
the
PlayBook
itself.
So
that
way,
it's
at
least
documented.
So
folks
can
recreate
it
without
ever
truly
and
they
decide
is
a
legit
thing.
I,
don't
know
if
you
I
know
you're
out
for
a
while
Jamie,
but
basically
the
the
sed
operators
dead
beef.
So
we
are
not
a.
A
Yep
but
I
think
a
lot
of
the
configuration
details
will
actually
live
on
inside
of
the
the
grand
unified
config
in
other
places.
Right
so
I
think
the
idea
of
having
you
know
having
the
conversation
about
what
it
means
to
have
the
configuration
for
some
of
this
stuff
in
a
CRD
or
in
some
unified
config
map
is
a
totally
worthwhile
effort
because
that
will
live
across
deployments
and
have
support
ability
for
that
stuff.
So
so
that
grand
unified
config
thing.
A
That's
because
I've
said
it
like
four
times
now,
but
no
we
are.
We
are
gonna,
try
and
come
up
with
a
proposal,
hopefully
this
cycle
for
it
we
basically.
Basically
what
happened
is
we
had
bunch
of
upgrade
issues?
The
upgrade
issues
dealt
with
config
and
then
we
were
talking
about
what
a
master
joins
scenario
meant
and
what
it
meant
for
multiple
sed
members
to
be
supported.
And
how
do
you
do
the
upgrades
across
that
and
all
of
that
boiled
down
to
like
our
config
structure,
is
kind
of
a
little
broken.
A
A
A
C
So
I
missed
the
last
cig
meeting
for
su
class
device.
Oh
I'm,
sorry
for
coaster,
API
or
the
working
group
meeting
I
should
say
current
status
is
that
we
there's
been
a
lot
of
work
migrating
the
repo
and
I
meet
them.
The
repo
migrated
just
last
week,
I
think
was
last
week
or
the
week
before
so
I
think
it's
about
getting
the
poll
requests
kind
of
lined
up
for
the
new
repo
and
whatnot,
but
that's
I,
don't
know
there
was
any
major
change
to
the
API
at
this
point.
Okay,.
A
All
right
is
there
I'll
ask
one
last
time:
if
there's
any
other
group
topics
for
folks
to
discuss,
otherwise
we
can
get
a
whole
bunch
time
back,
so
we
can
execute
on
111
agenda
items
so
on
the
backlog
once
twice
three
times.
Alright.
Well,
thanks,
everybody
and
again
feel
free
to
next
meeting
feel
free
to
percolate
the
backlog
of
things
you
want
to
discuss
during
the
sig
meeting
and
for
folks
who
are
traveling
safe,
travels
and
we'll
see
you
potentially
a
coupon.