►
From YouTube: Kubernetes SIG Multicluster 2021 Dec 14
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
B
A
A
To
me
last
week,
actually,
I've
also
had
a
little
cold
and
I
haven't
had
a
cold
in
years.
B
Yeah,
I
know
I
think
some
co-workers
were
talking
about
it
too.
So.
B
Okay,
I
think
I
did
it
very
cool.
Sorry,
I'm
a
little
scratchy
today
I
caught
a
little
cold
here.
So
I'll
keep
this
a
little
brief,
but
very
cute,
because
it's
the
end
of
the
year.
So
we
should
be
excited.
D
B
Cute
slides
go
theme,
so
please
enjoy
yeah
just
wanted
to
give
a
few
updates
since
the
end
of
the
year
on
some
of
the
keps.
Basically,
as
listed
here
in
the
agenda,
it's
the
end
of
the
year.
What
is
even
going
on.
I
just
want
to
update
everybody
and
confirm
the
next
steps
for
any
open
items.
B
B
Okay,
briefly,
let's
all
look
at
this
adorable
penguin,
who
is
drinking
a
latte,
but
this
is
the
status
overview
for
the
mcs
api
graduation
criteria,
so
there's
an
emoji
based
rating
system.
Here
I've
highlighted
these
four
in
the
next
slide
that
don't
have
just
plain
old
check
marks.
B
Next
to
them
we
did
have
a
meeting
on
the
same
topic
in
april,
so
the
check
marks
are
generally
things
that
are
already
check,
marked,
are
kind
of
similar
from
then
highlighting
that
we
did
talk,
then
about
the
beta
to
ga
graduation
and
felt
good
about
them.
At
that
point,
I
made
some
updates
and
a
pr
from
those
kind
of
stations
and
again
boosting
the
mcs
dns
implementation.
B
That
I
mentioned
last
time
too
thanks
again
jeremy
for
contributing
to
that.
So
the
other
leftover
items
right
now
that
don't
have
full
check
marks,
I'm
just
gonna,
feel
free
to
jump
in.
If,
if
you
have
something
to
say
on
any
of
these,
but
I'm
gonna
kind
of
walk
through
what
I
think
is
going
on
and
just
confirm
we're
on
the
same
page
so
yeah
for
a
detailed
dns
spec
for
multi-cluster
dns.
B
B
So
now
that
I've
cleared
a
few
other
things
off
my
plate,
I
can
actually
focus
on
this
again
and
incorporate
that
feedback
and
actually
get
the
lgtms.
So
I
think
that's
all
there
is
for
that
one
for
api
group
chosen
approved.
We
did
talk
about
this
in
april
and
we
were
like
yes,
but
I'm
bringing
it
up
again
kind
of
spoilers
for
later
a
cluster
id,
but
I'm
in
the
process.
B
I
just
opened
a
pr
requesting
cluster
id
api
review,
which
is
like
a
formal
process
that
involves
like
this
label
and
like
a
subset
of
people
who
are
allowed
to
give
api
reviews
to
like
put
lgtms
on.
C
B
B
C
Yeah
and
actually
we
have
done,
we
should
it's
like
more
of
a
check-in.
I
think
at
this
point
because
nothing's
really
changed.
D
C
Actually
did
do
an
api
review
back
like
pre-alpha
okay,
so
we
should
just
make
sure
everything's
still
good
there
and
yeah
choosing
the
api
group
as
well.
I
think.
B
Okay,
cool,
that's
fine!
I
mean
I'm
in
the
middle
of
this
process
now
or
I
don't
know
beginning,
but
I
actually
pressed
like
did
the
slash
label
for
cluster
id.
So
it's
convenient
for
me
to
do
that
for
this
too.
At
the
same
time,
if
we
want
to
check
it
again,
it
seems
to
me
that
there
isn't
really
like
a
dedicated
artifact
that
gets
made,
unlike
pr
reviews
so
yeah,
it's
kind
of
hard
to
tell
like
when
that
happened,
without
digging
through
a
bunch
of
pr's.
D
B
Oh
cool
cool
yeah:
we
can
talk
about
that
one
next,
but
yeah.
Okay,
just
to
close
out
this
one
sounds
like
there
was
an
api
review
in
pre-alpha,
but
we
can
hit
it
again
for
fun
and
I'll
go
ahead
and
do
that
since
I'm
already
handling
it
for
cluster
id.
C
No,
it
was
before
this
process,
it
was
just,
it
was
a
meeting.
B
C
D
C
C
D
C
B
Yeah,
I
mean
that's
the
direction
that,
like
cluster
id,
is
going
to
that's
case
studio,
which,
in
all
these
conversations,
was
one
of
the
reasons
why
api
review
was
prioritized
too
just
to
make
all
of
these.
You
know
interconnected
here,
but
yeah,
and
when
we
did
talk
on
the
in
april
about
this
last,
all
the
examples
in
the
sigs
repo,
I
put
a
note,
are
all
multicluster.kates.io.
C
Yeah,
actually,
the
only
place,
I
think,
we've
ever
not
used
case
studio,
is
in
the
in
the
current
like
repo
implementation.
So
should
we
just
go
ahead
when
we're
doing
the
api
review,
calling
it
multicluster.com
and
assume?
That's
that's
the
way
we're
headed.
B
D
I'm
still
thinking
about
it,
I
like
here
is
here's
what
I'm
asking
myself
yeah.
I
I
believe
there
is
a
well.
Let
me
put
it
to
you
this
way.
I
would
bet
a
nice
crisp.
One
dollar
bill
that
there
will
be
a
cost
associated
with
you
know,
discussion
and
consensus
building
around
kate,
stott
io.
D
C
B
Cool
cool,
okay,
so
that's
that's
this
one!
All
right,
end-to-end
test
exists
for
mcs
services,
so
I
briefly
brought
this
up
in
april.
We
didn't
really
talk
about
it
that
much,
but
since
the
list
is
getting
shorter,
well
spoilers
on
my
raccoon,
since
the
list
is
getting
shorter,
it's
highlighted
now
so,
according
to
like
cross-referencing,
the
end-to-end
test
package
in
the
actual
six
repo
and
what's
listed
in
the
cap,
it's
missing
some
test
cases.
So
I
think
that's
like
the
first
thing.
B
C
For
that
that
was
actually
added
as
a
criteria
back
when
we
thought
that
this
was
going
to
be
entry.
B
C
C
Less
sure
that
we
need
e
to
e
test
cases,
given
that
or
at
least
the
way
that
it
was
originally
intended,
because
there
is
no
implementation.
So
what
would
be
what
would
be
eating
instead?
I,
I
wonder:
should
we
rephrase
this
to
be
e
to
e
tests
that
an
implementation
can
use,
but
that
becomes
conformance
tests
and,
honestly
right?
That
seems
more
nice
to
have
than
certainly
not
a
beta
blocker,
not
even
sure
it
would
be
a
ga
blocker,
but
I
do
think
it's
something
we
should
pursue.
D
Right
so
independent
of
independent
of
like
maturity,
level
of
the
api,
like
a
conformance
type
test
suite,
I
think,
will
help
implementers
yeah
right
so
like
yeah,
I
I
think
it
is
a
worthy
thing
to
invest
time
in
and
I
wouldn't
necessarily
block
beta
on
it,
but
I
think
it
makes
a
like
a
beta
version
api
like
much
more
compelling
from
like
a
vendor
standpoint,
if
you
can
prove
to
yourself
that
your
implementation
is
conformant
with
the
spec.
D
C
Yeah,
I
agree.
I
think
we
definitely
want
to
build
a
conformance
test,
given
that
we
haven't
provided
an
implementation,
but
I'm,
I
think,
I'm
pro
decoupling
from
graduation.
B
Okay,
I
have
a
boring
project
management
question
then,
but
outside
of
like
caps
and
graduation
criteria
like
I
guess
this
is
just
a
github
issue
right
against
the
if
for
conformance
tests,
since
it's
outside
of
this,
like
formal
kept
process
like
it's
just
work,
we
want
to
do.
B
B
D
I
think
it
is
kind
of
a
no-brainer
for
graduation
to
ga,
but
I.
D
I
don't
think
we
need
to
block
on
it.
I
do
think
that,
like
it
might
be
a
very
useful
thing
in
like
the
next
couple
days
to
for,
like
the
three
of
me,
jeremy
and
laura,
to
put
our
heads
together
and
see
if
we
can
figure
out
like
exactly
what
kind
of
level
of
effort
it
would
take
to
implement
and
like
which
test
cases,
but
I
don't
currently
feel
a
need
to
have
beta
block
on
it.
C
B
Yeah
there's
some
nuance:
yeah
there's
some
nuance
in
here
of
like
exist
and
then
like
do
we
need
to
be
equivalent
to
what
this
cap
says?
Is
this
what
the
cap
says
now
out
of
date
with,
like
all
the
changes
of
being
out
of
tree,
and
then
it
sounds
like
this
conformance
test
is
like
this
total
other
potential
project.
C
Yeah
well
so
maybe
maybe
move
it
to
ga
criteria
and
reword
it
to
be
more
specifically
about
conformance
as
well,
because
the
original
like
it
really
is
about
ed
test
for
an
entry
implementation
right
now.
B
B
B
B
C
B
B
So
maybe
we
can
get
the
same
reviewer
for
both
if
that
even
makes
sense,
but
yeah,
and
then,
after
that,
I
think
it's
a
matter
of
building
the
crd
into
this
repo
that
we
made
a
while
ago
about
api
again
naming
tpd
on
api
review,
but
it
exists
right
now
temporarily
and
then
the
beta
blockers
for
cluster
id
was
the
to
crd
or
not
to
crd
question,
which
I
think
we've
generally
tabled
at
this
point
and
to
decide
if
cluster
ids
need
to
be
valid.
Dns
labels,
sub
labels
or
not.
B
B
B
B
If
we
feel
like
that's
dragging
on
for
a
long
time,
we
can
re-evaluate
if
we
want
to
fight
for
the
case.io
or
not
make
a
copy
of
this,
the
crd
as
finalized
in
the
api
review
in
this
repo,
and
then
we
don't
have
any
pending
beta
blockers
at
that
point.
So
then
come
back
to
this
forum
and
ask
when
the
time
is
that
we're
ready
to
go
to
beta.
D
D
Thanks
for
all
the
hard
work
that
you've
done
on
this
stuff
this
year
and
all
the
decks.
D
Well,
everybody
have
a
great
rest
of
your
day
and
rest
of
your
year.
Hope
you
have
a
joyous
and
safe
holiday
season,
and
new
year's
celebration
with
your
friends
and
family
take
care.
Everybody
bye.