►
From YouTube: SIG Cluster Lifecycle 2020-06-30
A
A
All
right
so
I
got
the
first
group
topics
PSAs.
This
is
a
writer
about
Keep
Calm.
As
you
may
know,
the
keep
Khan
is
web
virtual.
This
August.
This
is
a
link
that
explains
how
this
is
going
to
happen.
If
you
are
existed,
you
should
have
received
an
email
from
Nancy
explaining
some
details
about
your
specific
presentation.
But
basically
the
story
here
is
that
we
have
to
record
the
the
sessions
that
we
have
for
this
week
and
we
have
to
prepare
the
slides
and
submit
those
tomorrow.
A
Sending
the
deadline
is
the
divided
31st
and
basically,
if
you
come,
if
you
have
a
session
for
the
Austral
project,
you
also
have
to
do
this
for
them.
The
sig
intro
Justin
I'm,
going
to
ask
him
if
he
can
send
me
the
old
slides.
So
potentially
we
can
recycle
some
of
the
existing
diagrams
and
things
like
that
yeah.
So
I'm
going
to
start
working
on
the
slides
and
made
at
some
point.
We
can
record
the
session.
B
A
B
A
A
A
A
A
So
after
the
recent
events
in
the
United
States
and
across
the
world
with
no
alteration
process,
protests
and
things
like
that,
some
people
in
the
software
world
decided
that
it's
a
good
idea
to
go
over
some
of
the
big
projects
out
there
and
start
removing
potentially
offensive
language
such
as
the
word
master
slave
whitelist
blacklist.
You
know
this
particular
meeting
is
not
the
forum
to
discuss
whether
this
is
so.
A
These
terms
are
offensive
or
not
we're
just
going
to
have
to
comply
with
the
wider
projects
and
basically
kubernetes
is
creating
a
new
working
group
that
is
going
to
be
in
charge
of
potentially
removing
offensive
language.
So
I
think
I
have
a
link
for
the
exact
PR
that
for
the
creation
of
the
group,
so
basically
they
are
still
in
the
state
of
you
know.
Even
deciding
the
name
of
the
working
group
is
going
to
be
called
something
like
not
working,
protonate
naming,
but
rather
working
group,
inclusive,
naming
Co-
something
like
that
and
from
my
understanding.
A
Basically,
what
I'm
anticipating
here
is
that
our
of
volunteers
are
going
to
start
opening
repositories
and
looking
for
offensive
terminology
and
they're
going
to
start
creating
ticket.
We
also
don't
have
a
list
of
offensive
terms
yet,
but
you
know
the
ones
that
I
listed
earlier,
like
master/slave,
whitelists
and
blacklists
aren't
for
sure
for
sure
dog
those
are
going
to
be.
You
know
required
for
removal
replacing
replaced
by
something
else
now
how
much
of
this
is
breaking
it's
absolutely
the
uppers.
It's
also
clear:
what
is
the
timeline
like?
Should
we
follow
ga
duplication
policies?
A
Is
it
up
for
us
to
decide
how
much
time
we
have
to
duplicate
something
sensitive
or
is
it
up
to
this
group
to
give
us
the
their
perspective
may
be
telling
us
hey?
You
have
to
remove
this
next
month
and
you
have
to
bark
upon
the
change
to
all
the
prior
releases.
We
don't
have
the
answers
for
that.
So
just
so
you
know,
I
were
to
join
this
working
group
meeting
when
they
have
it
and
get
some
more
detail.
But,
prior
to
that,
you
can
just
you
can
start
doing
some
pre-emptive
work
to
start
learning.
A
How
are
going?
How
are
you
going
to
transition
from
this
terminology
if
you
have
it
in
the
project?
What
is
the
code
change?
What
is
a
user
facing
change?
In
the
incubator
case?
In
particular,
we
have
a
label
that
we
have
to
change
and
it's
going
to
be
very
breaking
for
some
users.
Our
plan
is
to
include
so
basically
include
this
label,
but
also
add
another
label
that
is
slash,
control
plane,
make
the
two
labels
live
by
each
other
for
a
period
of
time
and
then
remove
the
mass
the
label
support.
A
We
also
have
some
applications
where
we
use
this
particular
key
for
attaint,
which
is
also
we.
We
have
a
master
tape,
basically,
which
is
which
prevents
schedule
on
this
particular
note.
Josh
has
a
plan
so
how
to
approach
this
problem,
but
basically
it's
modest
area.
All
consumers
of
qadian
in
the
ecosystem
have
to
adapt
and
you
know
we
have
to
proceed
with
the
requested
changes.
Just
said.
I
know
the
cops
also
uses
the
same
label
but
you're
not
using
Canadians.
You
just
have
to
think
about
how
to
approach
the
problem.
B
A
So
so
for
sure
the
change
is
going
to
have
them
like
this.
The
usage
of
master
is
going
to
be
removed.
In
any
case,
this
is
full
tsardom
who
is
going
to
stuff
the
world
like
for
cube
idea.
The
Canadian
project
wants
to
stop
the
work
for
other
projects.
Maybe
they
are
going
to
have
people,
but
I
will
not
rely
on
that.
Well,.
B
I
mean
this
is
not
a
cuvette
DM
label.
This
is
a
its
comp.
This
particular
label
is
complicated
because
it's
it's
sort
of
by
consensus
label
and
I
agree.
The
naming
is
unfortunate,
the
we
don't
well,
we
don't
want
the
various
projects
to
do
this
totally
independently.
I
agree
so
like
this
is
a
great
thing
to
do
in
this
cig.
B
A
Should
help
them
yeah
in
this
project
in
this
particular
meeting,
you
know
for
all
the
Supraja
projects
of
sequence,
life
cycle.
What
we
can
do
is
agree
on
the
replacement
label
and
my
proposal
is
to
just
replace
master
with
ctrl
plane,
which
is
something
we
have
been
using
it.
Thank
you,
baby
I'm
already.
B
Let's,
let's
can
I
suggest
that
we
not
worry
about
the
new
name,
the
new
words
that
that
100%
is
there
like
that,
that
committee's
expertise,
let's
suppose
we
decide
the
new
one
is
yes,
control
plane
sounds
good.
How
do
we
propose
to
do
this?
We
would
we
would
label
for
a
period
of
time,
control,
plane
nodes
with
both
labels.
B
We
would
expect
add-ons
to
target
the
new
label
in
their
node.
They
would
switch
to
the
new
label
in
their
node
selector
and
they
would
tolerate
both
the
old
and
the
new
label
for
a
period
of
time
if
they
needed
to
explicitly
tolerate
it
or
they
could
switch
to
just
tolerating
all
taints,
which
is
actually
a
very
common
thing
anyway.
Yeah.
A
A
Once
the
this
period
of
time
passes,
we
should
remove
the
old
label
in
terms
of
taint,
is
slightly
more
complicated.
I
think
the
consensus
was
that
we
should
preemptively.
Add
colorations,
tell
everybody
to
our
donations
for
the
for
this
new
paint
that
still
doesn't
exist
with
the
same
key.
Basically,
you
should
creatively
add
lotro
kubernetes,
you
know
slash
control,
plane
in
the
list
of
donations
and
was
this
period
passes.
We
should
introduce
the
taint
at
least
Wikipedia.
We
should
introduce
the
new
taint.
B
C
If
I
get
what
they
were
Pretender
it
is,
it
may
have
a
comment
here.
I
think
that
okay,
the
the
the
working
group
is
not
yet
organized
the
so
now
we
are
kind
of
speculating
about
I
do
expect
that
each
project
is
is
kind
of
responsible
for
the
target
solution
and
the
working
group
is
kind
of
responsible
for
making
this
happening
in
a
coordinated
way.
C
So,
if
Cooperman
is
going
to
replace
this
label,
though,
we
should
pick
up
a
name
and,
and
all
the
projects
should
a
crayon
down
underneath
me
basically,
and
then
it
is
up
to
Google
mean
to
propose,
are
possible
a
roadmap
to
to
do
the
replacement
like
like
we
are
trying
to
do,
and
then
in
this
case
we're.
Basically,
this
label
is
used
across
many
project.
It's
up
to
the
working
group
to
check
if
this
approach
can
be
a
setter
for
everyone,
so
it
is
definitely
a
team
effort.
I!
A
B
Yeah,
I'm
very
glad
that
we
are
to
taking
it
seriously,
I'm
very
worried
about
the
idea
of
a
non-technical
group
trying
to
make
these
decisions
without
any
ability
to
implement
them,
like
it's
good
that
we're
gonna
help
them,
but
I
yeah,
I
guess
my
concerns
around
that
product
further
or
different
cuz.
We
want
to
succeed
and
it
doesn't
sound
like
they're
being
set
up
to
succeed.
B
A
I
definitely
have
a
lot
of
concerns
about
this
like
if
we
get
a
lot
of
users
that
are
complaining,
we
might
receive
some
hate
email.
You
know
about
breaking
changes
and
I
wanted
to
ensure
that
this
new
working
group
has
communication
channels
established
where
we
can
direct
users
and
I
see
that
they
are
going
to
have
an
email
mailing
list
and
they
are
going
to
have
a
slack
channel.
This
is
one
of
my
major
concerns
like
I
also
have
the
same
concern
like
it's,
not
a
technical
group.
A
So
if
you
want
to
stop
some
of
the
work,
people
might
need
help
with
understanding
the
projects.
So
it's
like
there
are
some
uncertainties,
certain
uncertainties
here,
but
if
you
have
comments
like
you,
can
pretty
much
comment
on
this
PR
I'm
going
to
share
it
in
chat
again,
is
you
know
the
group
is
still
being
formed?
So
if
you
have
comments,
just
comment
on
this,
Bri
I
think
it
already
has
something
like
200
comments.
B
A
At
this
faith,
could
controversy
from
people
that
are
going
to
poke
at
the
meaning
of
some
of
the
words,
because
for
some
people,
master
is
all
exactly
offensive
term
and
they
can
prove
to
from
their
perspective.
That
is
not
so.
If
you
get
the
complaints
like
that,
in
our
six
two
projects,
we
have
to
be
able
to
handle
them.
A
D
D
You
know
to
go
through,
you
know
to
go
through
this
process
of
changing
a
label,
because
this
is
something
that
you
know
we
may
have
to
do
for.
For
other
reasons,
and
or
you
know,
labels
paints
whatever
I
mean
it's
like
to
go
through
the
process
of
making
these
kind
of
changes,
it
seems
like
it's
kind
of
a
healthy
I.
Don't
anything
to
do
whatever
the
motivation
is.
D
You
know
it's
sort
of
a
anty,
anty
entropy,
maybe
and
I
I-
am
I
kind
of
you
know
picked
this
up
from
the
conversation
that
you
know
we'll
be
making
the
changes
with.
In
the
you
know
the
regular
sort
of
project
constraints,
so
you
know
we're
we're.
We
have,
you
know
deprecation
policies.
I,
may
you
know
I
will
be
following
those,
so
it
it
it
seems
it
seems
like
it.
You
know
it's
going
to
be
a
change
similar
to
you
know
similar
to
other
changes.
D
D
A
B
A
A
B
Well,
I
mean
the
source
code
is
very
easy.
It's
kind
of
comparatively
easy
to
change
right.
That's
just
a
PR
that
doesn't
require,
like
that's
very
back,
I'm,
happy
to
change
the
code
right.
That's
not
a
problem
at
all
like
it's
the
we
can
do
that
almost
overnight,
it's
the
it's
anything.
User-Facing
has
to
go
through
the
longer
deprecation
or
where
we
have
to
debate
the
longer
deprecation
period.
B
A
D
A
Also
about
crowdsourcing,
to
my
knowledge,
they
they
plan
to
stuff
the
the
work
in
terms
of
investigating
what
the
whole
cooperate
is
accumulated.
Sick
organizations
is
have
currently
in
terms
of
offensive
terminology.
So,
like
I
said
earlier,
you
might
get
people
poking
at
your
repository
in
a
log
in
a
ticket
at
some
point
that
you
have
this
in
this
and
you
we
have
to
comply
with
the
demand.
A
E
C
D
D
Just
looking
I
didn't
see,
I
just
did
you
know,
I
did
a
search,
I
didn't
see
any
any
use,
for
example
master
except
I,
think
in
in
some
code
that
was
I
think
originally
from
kuba
ATM,
so
that
that's
source
code
so
I
can
I
open
an
issue
we
can.
We
can
definitely
change
that,
but
I,
don't
I,
don't
I,
don't
see
anything
user
facing.
A
A
Derek,
a
BOSU
project
results
added
by
forestry,
doubtful,
cubed
yeah,
but
we
don't
have
any
major
updates.
We
spent
a
lot
last
meetings
minutes
discussing
this
topic
from
earlier
about
the
master
taint.
We
also
like
preparing
for
the
190
release,
pretty
much
getting
the
state
of
committee
I'm
ready
for
this
release.
That's
all
I
have
any
questions
for
comedian.
D
I
cut
a
relief
and
finally
a
binary
with
a
with,
without
with
a
digest
it.
It
is
a
hand-rolled
binary,
but
it's
it's
been.
It's
been
yeah,
there's
been
requests
for
her
having
having
a
binary
and
since
ICD
ADM
today
is
only
compatible
with
with
Linux
and
the
majority.
I
think
of
users
are
you're
running
on
on
Intel
64
bit.
That's
what
I
have
I
yeah
I
think
I
think
in
the
future
probably
want
to
build
them
for
arm
as
well.
I
think
that's
becoming
more
more
popular.
A
Yeah
I
was
in
the
Secretary's
meeting
today
and
they
we
had
armed
representatives
from
the
company
there.
They
apparently
added
recently
good
and
20
signal
for
armed
64
I.
Don't
think
we
have
signal
for
other
arm
variants,
but
464
I
think
we
are
getting
to
a
place
where
we
can
claim
good
support
for
this
architecture.
A
A
B
Yes,
just
on
that
topic,
a
community
member
is
working
on
support,
4k
ops
for
arm
64,
so
we
may
actually
able
to
get
some
tests
up
there
as
well.
I
think
they're,
focusing
on
the
non
control
plane,
nodes
first,
but
I,
think
the
that
this
person
is
also
going
to
look
at
the
control
plane
in
due
time.
B
F
Yes,
so
we
had
a
the
CLI
merge
a
few
minutes
ago.
So
it's
a
very,
very
alpha
at
the
moment,
with
with
primary
support
for
Cubase
building,
but
it's
extended.
It's
got
the
framework
in
place
for
qmu,
docker
and
and
Peka
Peka,
based
also.
We
have
a
good
base
to
iterate
on
now
and
we
should
be
able
to
speed
up
a
little
bit
there.
A
F
A
A
C
Can
give
you
a
brief
update,
so
we
are
working
to
cut
the
V
zero
three
seven
Mariza
and
we
are
trying
we
cut
on
alpha
zero.
One
week
ago
we
are
trying
to
cut
an
alpha
one
today,
so
we
all
know
the
provider
to
build
on
top
of
the
new
changes,
and
hopefully,
in
a
week
or
or
so
we
get
out
to
the
release.