►
From YouTube: SIG Cluster Lifecycle - Office Hours - 20230221
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,
everyone
today
is
February
21st
2023.
This
is
the
say,
cluster
lifecycle
meeting.
As
a
reminder,
we
adhere
to
the
kubernetes
code
of
conduct.
So
if
you'd
like
to
speak
up,
please
use
the
brace
and
feature.
A
If
you
have
any
topics,
please
add
them
to
the
agenda.
I
posted
in
chat
and
let's
get
started
new
meeting
participants
mg
root.
I
assume
it's
matte.
B
I
may
be
in
the
wrong
place,
so
I'm
trying
to
get
some
answers
about.
My
proposal
might
be
working
on
with
between
cluster
Auto
scalar
and
gappy.
I
just
saw
that
there's
a
meeting
for
Kathy,
specifically
I,
think
tomorrow.
So
if
that's
the
right
place
to
bring
that
up,
then
I'll
move
it
over
there
yeah.
B
Okay,
so
in
that
case
hello,
but
I'll
move
my
topic
for
tomorrow,
though
that
sounds
good.
A
Anything
any
other
I
guess
like
you.
Are
you
moving
this
one
too
I
assume.
B
Yeah
yeah,
that's
my
question.
So
that's
about
yeah
that
whole
thing
yeah
all.
A
Right
so
I
guess
I
did
have
a
topic
or
BSA.
We
have
a
new
tech
lead
for
the
for
the
Sig
cecio
has
agreed
to
step
up.
There
is
two
PRS
that
actually
need
an
otm
on
it
from
this
group,
first
of
all,
congrats
to
seal,
and
thank
you
for
stepping
up
to
develop
this
group
I've
sent
that
an
email
or
a
couple
emails
to
the
mailing
list,
announcing
the
nomination
and
ultimately
also
getting
it
through
with
the
PRS
to
that
are
LinkedIn
here
and
yeah.
C
Yeah
I
just
want
to
say
thank
you
and
thank
you
Vince
for
like
pushing
to
do
this.
I
think
this
is
a
really
great
opportunity
for
me
and
yeah
I.
Look
forward
to
helping
out
I
really
want
to
know
where
you
all
need
to
help
right
now
and
what
you
know
I
can
do
because
I've
been
mostly
active
in
cluster
API
and
subproject
so
far,
but
I
want
to
also
take
a
look
at
the
other
projects
in
this
egg
and
see
where
I
can
help
so
yeah.
C
You
can
expect
me
to
just
pop
up
in
office.
Hours
of
you
know
random
projects
in
the
next
few
weeks
and
just
listening
to
learn
more
yeah
and
I
also
haven't
been
doing
a
very
good
job
at
attending
this
meeting
because
it
conflicts
with
one
of
my
internal
meetings
where
I'll
make
enough
with
to
prioritize
it.
You
know
going
forwards,
so
I'll
try
to
be
here
most
of
the
time.
A
I,
don't
see
lubemere
Justin
did
you
have
anything
top
of
mind?
I
know
that
we
have
the
six.
What
was
it
called?
D
I
hadn't,
you
mean
that,
do
you
mean
couponers,
you
mean
the
report
to
the
steering
committee
thing.
The
I
think
it
was
the
report.
Okay,
I
haven't
seen
anything
about
that.
Yet
on
the
previous
I'll,
just
heal
congrats.
Thank
you,
Cecile
I,
put
I
think
we're
all
like.
Are
we
ready
to
plot
to
lgtm
it
like,
or
are
we
waiting
for
someone
else
to
like
win
for
lubemate
or
someone
I?
Don't.
E
D
A
Think
so
I
think
I
think
we're
good
to
go.
Okay
in,
in
general,
like
we
have
sent
out
the
email,
the
list
you
know,
we've
done
all
the
due
diligence,
so
we
should
be
good.
Okay,.
D
All
right,
I'm
pushing
the
buttons
awesome
all
right
good.
Then
we
can
get
that
done
because
I
think
everyone's
just
like
not
sure
whether
we
were
actually
ready
to
push
the
button
just
who
was
who
had
the
right
to
push
the
button?
Yes
and
then
I
haven't
seen
anything
on
the
on
the
report.
I,
don't
know
if
you
got
an
email
or
something
or
if
you're
just
expecting
it.
E
It
was
discussed
in
in
the
recent
yeah,
so
it's
exactly
the
stuff,
so
it
has
to
start
soon.
E
I
have
a
question
about
Donald
report.
Last
year
we
did
the
kind
of
survey
to
get
a
grip
on
projects
on
some
projects.
I,
don't
know.
Maybe
this
year
we
can
Skip
and
do
every
and
to
do
next
year.
Again
at
least
my
feeling
is
that
he's
interested
to
get
some
answers,
but
not
sure
if
we
really
need
it
for
the
annual
report.
A
Okay,
yeah,
we
can
talk
number
one
and
see
you
say
I'm
like
we
should
just
skip
this
year,
all
together.
E
Yeah
I
think
that
we
can
write
as
a
single
list.
Eventually
we
can
ping
a
project
if
we
need
clarification,
but
I
think
that
we
can
decouple
the
survey
from
answering
to
this
request.
Okay,.
A
I
guess
one
of
the
things
that
came
up
regarding
cubecon
icq
I
saw
that
qbdm
actually
got
accepted.
So
that's
good,
but
it
seems
like
either
something
has
changed
that
like
they're
now
doing
one
Talk
per
seg,
including
the
Sig
intro,
which
I
feel
it's
a
little
low
like
there's,
not
enough
opportunity
for
maintainers
to
actually
show
up
and
talk
about
their
project
if
they
want
to.
A
So
that's
that's
a
little
concerning
and
like
I
I
sent
out
an
email
to
the
cncf
about
it.
So
I
just
wanted
to
make
you
all
aware
as
well.
Let's
go
ahead.
C
Yeah
I
was
asked
by
someone
if
cluster
API
was
going
to
be
represented
in
the
expo
hall
as
a
kiosk
at
kubecon,
which
I
said
I,
don't
think
so,
because
it's
only
for
our
cncf
projects,
not
kubernetes
of
projects,
but
it
seems
like
the
rules,
may
have
changed,
and
this
year
it
said
any
like
Sig,
sandbox
incubating
or
graduated
projects
is
welcome
to
have
a
kiosk
which
I
I
didn't
ask
for
clarification.
So
it's
possible
that
that
is
misleading
and
doesn't
actually
mean
what
I
think
it
means.
C
So
for
this
coupon
it's
too
late.
The
application
was
closed
a
month
ago,
but
I'm
just
wondering
if
that
is
like
an
option
now
that
we
have
in
general,
maybe
yeah.
A
Maybe
maybe
we
could
we
could
do
that.
It's
still
like,
though,
like
having
one
talk
per
Sig.
It's
very,
very,
limiting
right,
like
I
mean
this
sake
like
we
have
like
a
lot
of
sub
projects
specifically
and
then
we
have
I
guess
some
projects
in
those
sub
projects
like
close
trip.
It
has
like
a
lot
of
different
things
going
on
as
well,
and
then
you
know
this
qbdm
cops
and
others
so
yeah
I
don't
want
it
to
be
the
case.
A
It's
like
okay,
let's
just
the
first
egg
goes
goes,
but
I
feel
like
cncf
should
revisit
that
limitation.
Honestly,
fabricium.
E
Yeah
I
I
kind
of
forget
it
so
so
I
was
not
aware
of
the
kiosk
thing.
I
never
saw
communication,
at
least
in
the
Secret
Lead
channels
about
this,
but
yeah
I
have
the
same
feeling
that
the
cncf
is
is
a
little
bit
unbalanced
because
it
trade
clients
kubernetes,
like
any
other
and
coveting
projects,
while
kubernetes
is
many
things
and
seek
are
really
different
between
them
so
and
they
they
then
came
off.
E
These
approach
is
that
sub-project
really
has
low
chance
of
visibility
and
with
regards
to
other
stuff
so
yeah,
it
is
a
good
discussion
to
have
with
cncf.
C
Yep
I
think
posting
to
what
Justin
is
saying
in
the
chat
about
applying
to
be
a
sincere
project
and
also
favorite,
so
I
wonder
if
it's
it's,
it's
not
that,
like
we
as
a
sick,
don't
really
fit
the
I.
Guess
the
pattern
that
other
six
follow.
C
More
than
that
you
know,
because
I
think
the
one
talk
per
Sig
makes
sense
for
a
lot
of
sigs,
where
they
are
special,
focusing
on
a
specific
area
within
the
kubernetes
and
the
people
who
are
chairs
and
tech
leads,
are
involved
in
that
whole,
like
code
base
and
as
approvers,
and
there
isn't
as
much
of
a
concept
of
thought
projects
that
have
their
own
governance
and
their
own.
C
You
know
owners
so
I
think
it's
just
the
way
that
cluster
life
cycle
is
structured
is
maybe
not
what
they
had
in
mind
when
making
that
decision.
A
Yeah,
let's
see
what
they
say
and
then
you
know
we
can
still
go
back
like
in
a
couple
of
weeks.
A
D
I
mean
I,
would
imagine
you
just
go
through
the
normal
process
right
like
I
was,
it
would
be,
it
would
be.
It
would
continue
to
be
a
sub-project
of
six
cluster
lifecycle,
but
it
would
also
apply
I
guess
to
the
sandbox
right
and
I,
like
I
was
looking
like
k3s's
in
the
sandbox.
I
was
like
well.
If
k3s
is
in
the
sandbox,
then
should
kuberian
be
in
the
sandbox.
Should
Cube
spray
be
in
the
sandbox?
Should
chaos
be
in
the
sandbox
right,
like?
Should
cluster
API
be
in
the
sandbox
right
I?
D
It's
I
feel
like
that
yeah.
This
is
the
this
is
the
fundamental
disconnect
I
think
that
that
maybe
we
are
like
a
lot
of
our
projects
are
comparable
and
complexity.
If
not
more
com
like
complex
and
widely
adopted
than
sandbox
projects
or
projects
that
have
been
except
into
the
sandbox.
So.
A
A
It
seems
like
a
little
unfair
to
push
this
on
us
like
completely,
especially
because
the
maintenance
track
has
been
very
lightweight
in
the
past
as
well.
So
we'll
see,
let's
have
a
opening
conversation
with
them
and
with
cncf,
and
maybe
we
should
also
reach
out
to
steering
to
just
understand
why
they
made
the
decision.
And
what
can
we
do.
A
All
right,
Justin
I,
think
you
have
the
only
sub
project
update
for.
D
A
D
You,
yes,
that's
that's
great,
because
I
have
to
go
in
a
minute
in
playoffs,
we
are
generally
working
on
improving
the
security
of
the
no
bring
up
to
protect
against
hostile
workloads.
Like
someone
filed
an
issue
a
couple
of
I
guess
months
ago,
now
about
like
the
fact
that
on
digitalocean,
for
example,
digital
ocean
doesn't
have
as
strong
a
notion
of
node
identity
as
you
get
like
on
AWS
or
gcp
or
I'm
sure
as
you're
not
familiar
with
it,
and
so
like.
D
You
basically
have
to
put
the
token
onto
the
node
and
that
becomes
very
easy
for
a
hostile
workload
to
get
access
to,
and
so
that's
something
we're
trying
to
fix
in
chaos.
I
bring
it
up
here
because
it
would
be
great
I
think
across
the
board,
in
all
of
our
future
sandbox
projects
or
sub-projects
to
to
like
establish
like
what
we
want,
the
behavior
to
be
like
what
we
think
is
okay
and
what
we
think
is
not.
Okay
and
yeah.
D
I
was
generally
talking
with
the
security
folk
and
like
we
don't
really
have
that
guidance
anywhere
about
like
as
far
as
I
know.
What
like,
which
like,
is
this
a
good
idea?
Is
this
a
bad
idea
like
and
so
I
think
it
would
be
great
to
as
a
Sig
figure
out
what
what
we
should
try
to
establish
a
sort
of
best
practice,
a
combination
of
best
practice
with
like
actually
working
because
I
think
that's
the
tricky
thing
here
for
how
you
bring
up
notes.
E
Definitely
plus
one
to
make
this
shared
knowledge
in
cluster
Pi.
We
have
a
long-standing
issue
about
creating
a
boost
or
a
project
or
an
odd
agent.
It
comes
with
various
name,
but
the
tldr
is
that
we
we
want
these,
no
one
really
committed
to
do
it.
So
if
we
can
make
this
common
beats
that
the
seek
offers
and
then
cops
consumes
copy
consumers,
this
will
be
a
huge
win.
D
That'd
be
awesome,
yeah,
I,
think
I.
Think
in
general
we
need
to
establish
what
we
want
to
do
like
I.
Don't
think
we
even
know
like
what
we
want
to
do
yet
so
I,
I,
I'm
I,
will
try
to
reach
out
to
I.
Guess
we'll
figure
out.
What's
how
sensitive
is
it
how
sensitive
it
is,
but
we
can
talk
about
it
at
kubecona
in
future
meetings,
but
yeah
I'd
love
to
collaborate
with
people
on
this.
A
Awesome
any
other
question
comments,
concern
thoughts,
last
minute
topics.