►
From YouTube: 20191008 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
A
Hopefully,
folks
can
see
my
screen
right.
If
you
could
add
your
details
to
the
attending
list
of
both
would
be
useful
as
part
of
the
standard
call
for
the
larger
call.
There's
a
couple
of
PSAs
I
have
one
PSA
and
if
you
have
other,
if
other
folks
have
other
PSAs,
please
feel
free
to,
and
the
first
piece
that
I
wanted
to
highlight
was
that,
please
add
your
details
to
the
contributor
summit,
which
is
basically
talking
about
the
future
of
our
projects
and
the
sub
projects.
A
So
if
you
can
add
details
there,
also
the
ask
will
be
that
you
have
some
representative
that
can
explain
the
details
of
why
these
things
are
important.
I,
don't
just
want
to
like
regurgitate
like
a
generic
roadmap,
because
this
is
part
of
like
getting
new
contributors
involved,
so
I'd
like
to
outline
one
of
the
the
primary
user
stories
and
why
it's
important
to
your
roadmap.
A
So
that
way
it
kind
of
can
if
people
are
new
to
the
community,
which
you
know
the
contribute
someone
is
is
a
large
swath
of
folks
who
are
relatively
new,
didn't
get
an
understanding
of
like
okay.
This
project
is
going
in
this
direction.
That
sounds
kind
of
cool
to
me,
because
I
I
can
resonate
with
that
user
story.
So
that's
kind
of
my
ask
and
I
figured
by
next
time.
Next
thing
meeting
we
can
walk
through
the
details,
but
we're
going
to
definitely
have
a
hard
stop
not
by
the
next
seed
meeting.
B
A
There's
one
of
the
general
PSA
that
I'll
mention
is
that
I
am
doing
a
lot
of
owners
files
pruning,
so
I
was
going
to
update
and
see
if
I
can
centralize
aliases
for
cluster
lifecycle
and
the
main
KK
repo
and
see
if
we
can
resonate
that
back
into
the
key
org
stuff
too
so
I'll
be
doing
that
I,
don't
think
it'll
affect
anybody.
This
is
going
to
be
shuffling
things
around,
so
it
uses
more
aliasing.
So
that's
just
a
PSA.
C
It
is
release
I,
hope,
117
is
going
to
be
a
lot
shorter
than
usual
because
of
holidays
and
conferences,
and
all
that,
so
they
enhancements
deadline
is
going
to
be
October
15
a
little
less
and
I
forget
what
it
is
about
about
a
week
or
only
April
enhancements
to
be
in
and
other
than
that
we
Joey.
We
just
want
to
make
way
to
release
team
and
they
hold
release
lead
team
want
to
make
ourselves
available
or
anything
that
you
all
need
any
questions
and
yeah
and
that's
it
for
me.
Thank
you.
A
D
Yeah
I'm
still
working
on
the
intent
test.
I'm
just
figuring
out
prowl,
been
trying
to
test
a
pro
job
locally,
ran
into
a
couple
couple
issues
around
there,
but
I
hope
to
I
got
some
help
in
the
in
the
channel.
Hopefully
I
get
that
get
that
going
today.
So
that's
really
the
that's.
The
hard
part
I
think.
D
D
A
F
So
I'm
just
gonna
give
a
quick
update
on
the
clips
that
we
merged
or
we
are
still
about
to
March.
So
the
first
one
is
a
something
about
company
config
management
changes
in
cube,
ADM.
It's
nice
discussion.
This
one
is
very
rusty.
The
second
one
is
by
head
bartosz
this
about
machine,
readable
output.
We
finally
managed
this
campus,
yes,
implementable,
possibly
alpha
117.
It's
not
still
not
clear
what
Canadian
commands
are
going
to
support
machine,
readable
output.
G
Gonna,
do
it
I
wrote
this
I
can
do
it,
so
we
have
a
lot
of
releases
here
so
make
sure
to
update
to
get
all
the
bug
fixes
that
we
fix
in
this
cycle.
We
have
copied
zero
to
four,
which
has
like
a
lot
of
bug,
faces
and
I'm
breaking
change,
and
this
breaking
change
actually
changes
the
leader
election.
So
you
will
need
to
do
an
action
which
is
detailed
in
the
release.
Notes
same
goes
for
the
cube
idiom
provider.
G
We
have
some
bug,
fixes,
lined
up
and
also
the
same
breaking
change
for
reelection
and
kappa
as
well
same
things
for
the
next
cycle
update.
So
we
have
a
lot
of
proposal.
There
are
working
progress
and
we're
looking
to
have
a
PR
is
open
by
the
end
of
the
month.
We're
working
on
control,
planes
up,
raise
the
testing
framework,
machine
pools
and
remediation,
and
there
are
also
other
things
that
are
in
flight,
like
making
the
cluster
object
required
and
so
on.
A
G
A
B
Absolutely
sure
so,
I
think
Lee
put
in
the
notes
that
we
had
a
great
discussion
last
to
some
time
last
Tuesday
I
guess,
which
was
so
there's
some
work
to
figure
out
how
cube
ATM
is
going
to
or
how
cuvee
them
could
consume.
These
add-ons
I
would
actually
highly
encourage
people
to
look
at
the
video
because
it
is
really
interesting
to
see
and
to
think
about
and
if
I
recall
correctly,
Lee
was
pulling
from
get.
B
So
that's
really
interesting,
as
well
as
like.
Potentially
what
other
sources
like
image
repositories
to
say
is
a
common
one
that
keeps
coming
up,
so
we're
really
I
guess
trying
to
get
those
add-ons
into
a
couple
of
key
users,
cops
and
cube,
ATM
or
the
to
which
we
are
focused
on
primarily,
but
that
is
mostly
because
those
are
the
two
which
the
people
are
most
familiar
with.
So
if
there
are
others,
we
would
love
to
speak
to
them.
B
A
F
I,
don't
think
we
should
even
include
it
until
we
start
until
we
have
a
clearer
picture
around
upgrades,
because
that's
one
of
the
aspects
of
missile
aspects
on
this,
we
have
to
include
information
in
the
cap
on.
How
are
we
going
to
manage
underneath
with
this
tool
we
promise
that
is
going
to
do
it.
A
F
Mean
I
think
both
Michael
and
Lee
cannot
join
today.
I
can't
give
a
quick
update.
Basically,
let
me
check
what
the
road
first
so
they're,
enabling
strict
codecs
in
cue,
proximate
couplets.
It
seemed
similar
to
our
strict,
the
serializer
in
qadian
that
feeds
warnings.
You
know,
but
they
attempted
to
enable
this
in
API
machinery,
and
this
saw
some
opposition
in
terms
of
enabling
it
for,
for
example,
on
the
Q
proxy
V
1,
alpha
1
or
the
Kubla
T
1
beta
1,
because
even
if
these
configs
are
not
final,
they
are
still
used
to
production.
F
So
there
is
discussion
around
that.
Jonathan
has
comments.
Maybe
a
mailing
lead
discussion.
Mailing
lists
discussion
is
going
to
spawn
pretty
soon
because
they
want
to
get
more
feedback
from
that
from
folks
in
the
community
like
what
is
the
policy
around
strict
codecs
in
general,
they
also
started
a
mentorship
program
and
now
nowadays
I'm
seeing
more
people
joining
the
which
is
great,
but
I
really
don't
have
more
details
from
the
program
itself.
A
H
H
H
H
B
Cups,
yes,
thank
you.
Nothing
too
surprising,
I,
hope
we're
a
star
114
s
hero,
and
so
we
should
be
at
this
place.
Caught
up
at
committee's
117.
Caught
up
is
releasing
the
alpha
at
the
same
time
as
as
the
or
making
the
alpha
or
beta
available.
At
the
same
time
as
the
kerbin
news
release,
we
are
enjoying
our
multiple
branch
strategy,
where
we
have
like,
like
the
114,
139,
1:16
branches,
all
open
and
separate.
B
That
seems
to
work
really
well
for
ensuring
that
the
actual
release,
although
trailing
is,
is
a
is
a
good
one,
and
it
also
lets
people
get
their
changes
in
quickly.
It's
not
it
be
great
to
be
able
to
continue
that
when
we
catch
up,
but
we're
not
really
sure
exactly
how
we
would
do
that,
but
in
general
we
are
like
agreeing
our
releases
every
two
weeks
and
more
or
less
sticking
to
them.
B
A
I
Yeah
I
just
wanted
to
spread
this
out.
I
sent
this
to
the
Cates
requester
lexical
mailing
list.
It's
it's
a
proposal
for
moving
to
major
versions
for
the
go
libraries
in
cluster
API
using
major
sub
directories.
But
that's
not
really.
That's
not
really.
A
sticking
point
we
can.
If
we
decide
branches
are
better
than
no
branches
are
fine
too,
but
there
is
a
discussion.
Current
discussion
going
on
about
which
makes
more
sense,
branches,
subdirectory
and
just
kind
of
the
whole
topic
in
general
is
up
for
debate
any
input
there
would
be
really
cool.
A
Any
other
topics,
urgent
items
or
questions,
comments,
complaints,
concerns
that
folks
wanted
to
discuss
the
guy
right
here.
Otherwise
we
get
it
whopping
before
you
minutes
back,
come
on
once
Oh
cameras
off
twice
three
times
alright.
Well
that
ended
early
thanks
for
the
updates.
Again,
as
our
PSA
reminder,
please
add
in
your
roadmap
ideas
in
details,
but
again
try
to
stress
the
why
it's
important,
what
are
the
user
stories
behind
it?