►
From YouTube: SIG Cluster Lifecycle 2022-01-25
A
A
So
the
first
group
topic
that
we
added
is
it's
about
the
annual
reports
that
special
interest
groups
have
to
do
every
year.
It
was
a
change
that
was
introduced
last
year.
We
did
a
report
and
the
basically
the
theodr
of
these
of
these
types
of
reports
is
that
you
have
to
summarize
what
is
the
health
of
the
group
like?
What
is
the
health
of
the
soup
projects
like?
Do
we
update
donor
files?
A
A
A
You
might
have
seen
an
email
that
I
sent
to
the
mailing
list
with
a
summary
of
what
is
happening
in
124.
We
are
making
a
number
of
changing
a
number
of
changes.
Unfortunately,
I
think
this
landed
in
the
same
cycle,
which
is
not
ideal,
but
also
the
cycle
is
so
low
now
that
it's
four
four
months
like
it's
really
difficult
to
spread
the
work.
At
this
point
I
had
concerns
at
the
beginning,
but
I
guess
nobody
complained,
so
we
proceeded
with
the
all
the
changes
that
we
planned.
A
So
you
can
check
these
out.
I
think
we
are
going
to
repeat
them
in
this
meeting
if
we
read
the
email
again,
but
I
want
to
highlight
the
first
one,
which
one
of
these,
I
guess
is
that
the
master
two
control
plane
level
intent
migration
is
in
flight
and
we
noticed
that
this
broke
immediately.
Some
aspects
in
kind
well
can't
use
kubernetes,
because
kind
was
waiting
for
the
master
label
on
a
node.
A
A
Instance,
like
the
kite
project,
did
it's
a
breaking
change
for
them?
Then
again
in
one
120,
we
already
announced
the
plan
and
everything
break
break.
Breaking
users
is
inevitable
around
this
change.
Somehow
I
anticipate
users
log
in
tickets
and
that's
why
we
have
the
cap
ready
to
with
a
very
clear
plan,
to
install
them
how
to
adapt,
and
also
I
saw
that
so.
The
second
point
here
is
that
I
saw
the
entrance
sweet
in
kubernetes
only
tolerated
the
master
taint
as
a
non-blocking.
A
So
there's
a
bit
of
a
design
problem
in
the
suite
where,
if
you
have
taints
on
some
nodes
that
are
with
no
schedule,
this
means
that
the
the
switch
will
walk
on
these
stains
until
the
no
schedule
is
removed.
Like
the
the
effect-
and
I
disagree
with
this
design
and
the
the
way
the
way
the
suite
is
dealing
with,
it
is
how
it
has
a
flag
where
you
can
specify
which
taints
you
want.
D
A
D
A
Key
yeah,
yes,
which
is
a
little
weird,
but
yes,
it's
very
weird
yeah.
I
know
this
yeah
yeah
just
this
is
a
basically
a
concern
about
this
change
with
the
tents
is
that
it
probably
will
need
an
action
required
in
the
release
loads.
Whenever
we
do
that,
because
the
framework,
the
the
suite
will
block
on
conformant
tests,
conformance
tests
in
user
questions
and
production
questions,
but
you
know
it's
part
of
the
rename
effort
and
it
has
to
go
away.
D
A
I
guess
I
can
also
notify
kdf
when,
when
we
are
actually
going
to
introduce
the
removal
of
the
master
teams
at
some
point,
another
side
notification
of
the
site
is
that
I
said
appear
to
improve
the
strict
validation
of
component
configs.
We
have
in
cubanium,
which
is
only
a
little
bit
of
an
improvement.
We
already
had
warnings
for
fields,
fields
that
are
duplicated
by
the
user
by
mistake
or
for
fields
that.
A
Are
unknown
in
the
conflict,
so
the
user
passes
a
field
that
is
with
a
typo
and
they
get
no
indication
of
the
mistake,
and
this
is
something
we
already
had
these
two.
But
I
read
with
this
change
about
in
a
third
one,
which
is
a
case
sensitivity,
so
it's
actually
important
to
pass
the
right
case:
sensitivity
for
a
particular
field.
A
A
So
sorry,
jordan
took
basically
created
a
like
a
fork
and
api
machinery
accepted
the
project
and
I'm
using
this
now,
or
rather
I'm
not
using
it
directly
because
it's
not
possible
to
use
it
directly.
I'm
using
api
machinery,
the
api
machinery
repository
that
renders
this
particular
repository
yeah,
I
mean
it's.
A
A
B
B
A
B
B
A
A
Problem
one
is
that
we're
probably
going
to
get
a
lot
of
outputs,
because
we
have
many
other
files
in
different
repositories
and
I
don't
think
it's
feasible
for
the
leads
of
this
group
to
be
able
to
like
address
all
the
owner
files.
We
can
log
issues
in
the
respective
repositories,
but
you
know
I
don't
think
yeah
we
can
do
the
cleanup
ourselves.
B
B
B
B
B
A
E
A
D
B
Yeah
and
also
I
participated
at
the
first
office
hour
of
this
project,
and,
and
there
is
a
interest
from
red
that
as
well,
they
have
a
similar
provider
and
they
are
discussing
with
the
team
about
how
to
merge
the
two
effort
together
and
those.
So
if
I
remember
where
new
relic
force,
no,
not
new,
nearly
so
yeah.
B
B
A
A
E
A
B
D
B
Okay,
I
I
I
will
raise
the
point
tomorrow
in
the
copy
office
hour,
because
it
is
a
a
good
place
to
raise
many
sub
projects
to
to
reach
menisca
project
and
see
if
someone
want
to
propose
their
own
projected
dive.
They
have
to
reach
out
to
the
leads
that
that's
the
procedure
but
yeah.
That's
basically
what
I'm
going
to
tell
that.
A
B
A
B
A
B
A
I
wanted
to
ask
somebody
asked
me:
you
know
with
my
team
at
vmware,
they
wanted
to
use
quest
api,
but
they
asked
me
the
naive
question:
is
there
going
to
be
a
v1
which
I
didn't
have
the
response
to
like?
Do
we
have
a
rough
like
timeline
for
everyone?
Maybe
two
years
one
year
or
something
in
the
future.
B
A
E
D
A
Yeah,
I
I
think
it's
a
great
idea
for
a
talk,
because
if
you
have
this
title
in
the
talk
like
ipv6
with
aws
and
chaos,
you
are
going
to
potentially
attract
all
those
people
that
understand
and
you
want
to
use
ipv6
and
you
can
have
a
bit
of
a
conversation
like.
What
is
your
current
adoption
like?
What
is
the
infrastructure?
D
Exactly
yes,
it
would
be
very
much
a
like
a
practical
talk.
I
think
one
of
the
things
that
at
least
the
people
that
are
adopting
it
in
the
chaops
community
are,
I
think,
finding
is
that
you
know
a
big
part
of
the
appeal
of
ipv6
is
pure
ipv6,
like
not
dual
stack,
because
dual
stack
means
you
still
have
to
manage
ipv4.
So
what's
the
point
that
sort
of
thing,
so
that's
that's
a
big
now
that
it's
realistic
to
do
that.
F
F
It
was
just
a
bunch
of
sort
of
random
odds
and
ends
from
the
end
of
last
year
that
were
that
was
released,
and
so
some
of
the
some
of
the
groundwork
was
laid
for
vm
drivers
for
arm64,
which
seems
to
be
more
and
more
of
a
thing
that
people
need
so
yeah.
So
126
is
going
to
be
a
lot
of
things.
It
should
be
an
arm.
64
compatible
vm
driver
for
kvm
for
linux
and
with
some
of
the
work
for
a
mac,
a
mac
os
arm,
64
vm
driver
as
well.
F
A
Yep,
the
the
cuba
migration
from
ambassador
to
bait
was
pretty
straightforward.
We
just
wanted
to
synchronize
everything
with
a
push
of
a
bottle
to
happen
at
once.
You
know
it
was
fairly
simple.
We
just
had
the
prs
ready
and
somebody
did
the
rename
of
the
repository
with
administer
administrator
writes
you
know
just
do
the
rename
then
merge
the
prs
immediately
and
we
didn't
actually
see
any
errors
in
the
enter.
F
A
B
A
A
F
Option:
yeah
yeah,
that's
so
many
people,
so
many
like
mini
cube
users
expected
though,
and
more
and
more
people
are
using
mini
cube
as
a
replacement
for
docker
desktop
on
non-linux
machines,
and
so
for
us,
it's
really
like
container
d
as
a
default
is
would
be
challenging
in
terms
of
it.
Would
we
wouldn't
be
able
to
make
that
change
soon?
So
that's
the
that's.
That's
the
only
reason
we're
sort
of
backed
into
this
corner.
F
That's
the
biggest
thing
is
bill
is
building
images
and
we
have
our
own.
We
have
our
own
sort
of
mini
cube
image,
build
tag
whatever,
but
it's
not
fully
feature.
It
doesn't
have
any
sort
of
feature
parody
with
the
docker
yet
and
that
will
that
works
with
container
d
and
cryo.
So
eventually,
that's
probably
what
we're
gonna
have
to
point
people
to,
but
it's
not
ready
yet.
A
A
F
D
F
D
F
So
the
only
the
only
other
so
parallels
we
don't
have
any
licenses
for
parallels,
and
I
have
no
idea
if
that
supports,
arm64
or
not
parallels
in
minicube
has
always
been
like
a
best
effort
on
anybody
who
wants
to
continue
maintaining
it
can,
but
none
of
the
core
maintainers
have
ever
maintained,
parallels
and
virtual
boxes.
Virtualbox.
D
Yeah
I'll
put
a
link
in
the
chat
or
something
on
the
chat
in
the
in
the
doc
that
that's
the
one
I'm
thinking
of,
and
there
are
some
examples
out
there
where
people
have
it's
like.
It's
like
a
very,
very
high
level
one.
So
I
don't
know
I
was
just
wondering
whether
you
were
aware
of
it
and
I
would
have
been
wanting
to
try
it
out.
So
I
was
wondering
whether
you
tried
it
out,
never
saying
it
doesn't
work
or
something.
D
Yeah,
this
is
not
something
I'm
aware
of
personally:
okay:
cool
cool,
that's
good,
because
yeah
well,
yeah.
I
agree
that
we
should
try
kumu,
because
it's
very
universal,
it
might
even
work
on
windows.
But
this
one
seems
like
a
good
choice
on
mac
os
they're.
They,
I
think
you
can
use
it
from
like
the
app
store
as
well.
So
you
don't.
B
F
B
C
D
D
A
A
A
C
E
C
E
D
I
think
I
think
it
goes
in
fits
and
starts
right
like
we
have.
I
certainly
personally
have
times
when
we
do
more
on
it
and
times
we
do
less
on
it
and
often
around
like
around
like
new
lcd
versions
or
trying
to
like
converge,
but
I
need
to
get
more
consistent
on
on
contributing
to
it
and
and
doing
all
the
reviews
and
things
like
that
as
well.
A
Yeah,
if
there's
a
company
that
really
wants
to
use
it
and
change
it
in
a
certain
way,
they
will
have
to
invest.
So
that's
how
it
works.
Basically,
if
it's
currently
usable
for
certain
parties,
if
somebody
wants
changes,
they
should
invest
the
human
resource,
that's
how
it
works
in
all
consoles.
Basically,.