►
From YouTube: Kubernetes SIG Multicluster 2020 August 04
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).
B
Good
good
nice,
nice
seattle
day
here
did
you
get
hit
by
that
storm.
A
I
think
I
mostly
slept
through
it.
We
we
got
some
heavy
rain
last
night
and
my
wife
said
it
got
way
heavier
after
I
went
to
to
bed,
but
it's
a
nice
clear
sunny
day
here
today.
A
Cool:
do
you
find
that
it's
tiring
for
your
arms.
A
C
Well,
why
do
you
think
why
do
you
think
foot
pedals
are
a
thing
with
flying
in
in
the
early
biplanes?
Most
of
the
controls
were
foot
pedals
because
you
needed
your
leg
strength
to
actually
operate
them.
C
Yeah,
I
mean
basically
the
stick
actually
just
controlled
the
small
flaps,
because
that
was
the
only
thing
you're
going
to
be
able
to
manipulate
with
the
stick.
All
of
the
big
flaps
will
control
the
foot
pedals
interesting.
A
All
right:
well,
why
don't
we
get
started?
Welcome
everybody
josh!
I
think
that
you
have
the
first
agenda
item.
C
Yup,
so
we
have
the
results
of
the
survey
here.
You'll
have
to
look
at
it.
Google
docs
is
freaking
out
on
me,
but
I
did
already
paste
it
in,
I
believe
hopefully
is.
Can
you
see
the
survey
results
in
the
agenda
here.
D
C
C
C
Yep
yeah
and
that's
also
in
the
agenda,
if
you
want
to
get
a
close-up
to
it,
but
we
got
like
another
seven
votes
since
we
had
our
conversation
over
email,
but
those
were
really
consistent
with
everything
else.
So
the
votes
seem
pretty
clear.
Cluster
set
is
both
the
least
hated
and
the
most
liked
option
by.
C
Margin,
yes,
the
out
of
the
additional
suggestions,
because
we
did
leave
the
additional
suggestion.
Question
on
the
survey,
the
only
one
that
looked
at
all
plausible,
particularly
because
two
different
people
suggested
it
is
cluster
pool.
C
A
A
C
B
B
C
A
Well,
thank
you
thanks
a
lot
josh
for
all
the
help,
facilitating
that
determination,
process.
A
All
right,
so
I
guess
we
should
make
the
result
known
in
a
public
message
to
the
list
right.
C
C
D
A
Speaking
of
that,
I
have
just
plus
one
the
the
pr
and
said
that
I
preferred
a
shorter
name,
but
you
know
I'd,
I'm
totally
fine
to
talk
about
it.
If
we
want
to.
If
we
want
to
debate
it
a
little
bit.
B
Yeah,
I
don't
have
a
strong
preference.
I
started
with
mcs
api.
I
think
you
know
kind
of
short
is
nice
and
as
soon
as
you
click
in
you
know,
there's
enough
context,
and
I
know
we've
been
using
mcs
a
lot
if
anyone
feels
like
it
needs
to
be
longer.
It
should
be
something
else,
though
I
think
again,
I
don't
have
a
real,
strong
preference.
A
The
only
the
only
thing
that
I
can
think
of
really
in
favor
of
making
it
longer
is
disambiguation
with
the
se
linux
multi-category
security
concept,
which
is
probably
what
many
people
would
think
of
when
they
heard
the
acronym
mcs.
A
But
it
seems
to
me
like
it,
you
go
short
or
you
go
really
really
long
with
this
name.
D
I
was
I
was.
I
was
actually
also
wondering
if-
and
maybe
there
was
past
conversations
about
this,
but
why
we
want
to
make
the
repo
specific
to
multicultural
services
like
do
we
see
value
in
just
calling
it
multi-cluster
apis
and
then,
if
there
are
future
apis
that
aren't
related
to
services,
we
would
put
it
in
there
as
well.
A
So
I
would,
I
would
prefer
to
avoid
doing
that
and-
and
the
reason
for
that
is
because,
in
my
experience
like
there
is
a
great
fragmentation
in
what
people
actually
want
to
do
in
this
space
in
different
functional
areas,
and
I
would
I
would
be
concerned
about
like
a
perception
that
we
would
be
creating
a
monolith
if
we
have
an
api
repo
with
a
ton
of
very
different
apis.
B
Yeah
I've
been
thinking
about
this
recently
too,
and
I'm
kind
of
in
the
same
boat
like
separate.
Is
nice,
it's
isolated.
In
fact,
I
I
think
we
probably
even
want
the
api
group
eventually
to
be
something
like
services.multicluster.com
instead
of
just
multi-cluster,
because
multi-cluster
is
big
and
there's
going
to
be
a
lot
of
different
things,
and
I
think
we
just
yeah
like
keeping
it
focused
is
is
good,
especially
if
you
know,
I
think
we're
still
entertaining
the
end
goal
of
this
might
end
up
needing
to
be
staging
as
we
approach
beta.
B
If
we
do
that,
having
it
just
be
like
the
mcs
part,
instead
of
everything
else
makes
that
a
nice
easy
transition
as
well.
A
So
one
thing
that
I
wonder
as
we're
talking
about
this
is
whether
it
is
really
just
going
to
be
an
api
or
whether
there
may
ultimately
be
some
degree
of
like
universality
in
the
controller
implementations
that
accompany
the
api.
I
wonder
if
maybe
multi-cluster
services
might
be
a
better
name
for
the
repo.
B
Yeah,
I
think
I'm
I'm
curious
what
what
others
think
I
think
you
know.
Currently
it's
headed
as
as
just
an
api.
I
mean
with
the
caveat
that,
because
we're
doing
this,
this,
like
derived
service
hack
for
alpha
there
is
a
there
is
a
small
controller,
but
I
don't
know
if
we
currently
plan
to
have
a
like
standard
or
you
know,
canonical
implementation
of
the
api.
B
I
know
there's
a
few
in
the
works
like
submariners
made,
made
some
progress
implementing
it,
but
yeah
that
that
is
a
good
point.
B
Yeah,
okay,
yeah,
so
the
the
next
thing
was
just
I
put
up
a
basically
what
I
what
I
hope
to
be
the
mcs,
the
sigs
mcs
api
repo
under
my
github
and
I'll
move
it
over
once.
We
have
that,
take
a
look
and
and
play
around
there's
a
demo,
so
you
can
play
with
the
controller
and
see
how
it
works
and
basically,
there's
some
some
tools.
B
A
A
All
right.
I
think
that
was
all
the
agenda
items
today,
but
let
me
go
double.
A
A
Yeah,
that's
all
the
agenda
that
we
have
for
today.
If
there's
nothing
else,
we
can
end
it
here
and
everybody
can
get
a
little
bit
of
time
back.