►
From YouTube: Kubernetes SIG Multicluster 20180508
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
A
D
A
A
Okay,
so
with
respect
to
multi
class
sir,
my
take
was
that
there
is
a
lot
of
interest
in
particular
use
cases
still,
because
there
were
a
lot
of
people
who
did
attend
the
deep
dive
and
pinko,
and
there
were
a
lot
of
questions
around
the
maturity
when
we
are
going
to
actually
have
v2
Federation's
Altaf
or
some
maturity.
Questions
about
the
pleasure
industry
also
and
the
replies
to
which
were
paid
forward.
The
reply
to
maturity
of
b2
Federation
was
a
little
tricky.
A
A
Operator
concept
probably
has
been
there
since
one
and
a
half
two
years
and
classical
example
is
e,
XE
d.
So
if
you
user
wants
to
install
XE
d
across
multiple
clusters,
so
there
is
operator
for
that,
and
there
are
many
other
similar
operators
out
there.
The
operator
framework
that
was
disclosed
I
didn't
go
through
it
in
detail,
but
what
I
understood
is
that
they
have
probably
published
I
am
NOT,
also
not
sure
how
much
of
that
is
open
source.
A
Yet
they
have
published
as
degree
which
enables
users
to
develop
such
operate
operators
more
easily
for
comparatively
easily
how
it
was
earlier
to
develop
an
operator
or
develop
on
the
concept
of
the
operator.
So
that
seemed
to
be
a
big
announcement,
because
it
was
announced
as
part
of
a
kilo
and
I
did
attend
one
of
the
one
of
the
talks
by
one
core
over
sky,
which
actually
was
titled,
as
particular
operations
using
operators
or
operator
feel
or
something
like
that.
A
But
apart
from
that,
I
had
a
chat
with
him.
What
he
mentioned
was
that
he's
in
his
slice
itself.
He
did
present
about
cluster
registry
also.
He
would
present
one
slide
about
Federation
v2,
also
and
end
of
it.
I
had
a
short
chat
with
him
he's.
His
point
was
that
probably
it
is
still
to
be
concluded
or
or
evolved
as
to
how
both
can
coexist
or
how
both
can
interact
with
each
other,
like
with
respect
to
the
multinational
operations.
Okay,.
D
A
A
B
D
It
out
in
public
it
can't
possibly
work
for
them,
not
in
the
current
state
but
I
guess
these
people
were
represented
in
the
crowd.
Okay,
I'm
just
hopeful
the
annotation
be
have
that
you
added
to
the
documentation,
or
at
least
enough
to
steer
people
away
from
it.
Well,
actually
see
and
probably
see
him
a
slight
channel.
That
was.
C
A
Also
sort
of
inferred
that
people
who
are
interested
in
Federation
or
trying
out
or
or
a
waiting
for
it
to
evolve
into
something
more
more
production-ready.
They
already
are
aware
of
all
the
developments
and
whatever
changes
that
has
happened
in
last
six
months
or
so
so
that
might
be
one
reason
that
we
did
not
see
any.
You
know
and
Shias
questions
in
infidelity
date,
I,
don't.
A
A
D
B
B
D
B
A
D
A
B
A
Okay,
I
remember
questions
in
the
deep
dive
more
than
one
in
fact,
centered
around
our
back
support
and
how
like,
what's
the
plan
about
supporting
the
are
back
API
a
which
can
be
committed
to
the
clusters
and
what's
the
plan
around
segregating
the
access
control
of
each
of
the
federated
API?
So
so
that
is,
that
seems,
seemed
like
it
did
stem
from
people
trying
to
use
it,
and
they
already
know
that
that's
an
that
is
aggregated
right
now
properly
and
that
doesn't
work.
D
A
Actually
talking
about
both
questions
for
around
both,
so
there
was
a
question
which
mentioned
that,
what's
your
plan
about
federating
the
artifact
API,
so
that
the
same
thing
is
duplicated.
So
if
a
user
wants
to
create
a
back
resource,
the
resource
should
be
created
in
each
of
the
questions
of
a
committed
into
each
other
process.
And
there
was
a
question
around
this.
A
Also
that
how
are
you
planning
to
have
access
control
in
the
Federation
control
so
for
each
of
the
APA
that
you
I
actually
have
intentions
and
Coltrane
I
mean
odd,
that
that
tells
me
that
people
probably
are
aware
about
that.
We
have
the
admin
privilege
or
we
have
to
have
that
Mister
place
to
do
current
operations
in
citation,
and
this
solution
is
not
there.
Yet
that
might
be
one
reason:
stopping
them
from
the
amusing
edition,
b1
or
b2.
B
B
What
I'm
one
of
the
points
they
raised
in
there
was
that
the
access
control
and,
like
you
know
if
your
cluster,
like
control
plane
of
the
Federation,
is
compromised
and
basically
all
the
memory
clusters
are
compromised.
All
right,
you
know,
access
to
one
gives
you
access
to
all
of
them,
so
that's
sort
of
what
the
same
vein
of
the
are
back
there
clusters.
B
F
F
D
A
D
D
D
E
I
think
that
about
covers
it
with
cube
con
last
week
there
was
not
necessarily
as
much
much
progress
made
and
any
other
technical
things.
We
had
made
a
decision
a
few
weeks
ago
to
move
to
a
CRT
into
namespace
the
object
but
I
believe
that
was
already
brought
up.
I
can't
remember
that
had
been
brought
up
in
the
city
yet
or
if
that
meeting
was
after
the
last
sick
meeting,
but
in
any
case
that
work
is
moving
and
will
hopefully
move
a
bit
faster.
Now
that
Kubik
on
is
over.
D
G
I'm
sorry
hi
I'm,
Meghan
I
can
interject
here
so
I'm
Cisco
and
some
team
on
our
floor
has
also
worked
on
some
of
the
multi
cluster
to
see
of
stuff
and
we're
gonna
be
talking
to
them
this
week.
So
as
those
conversations
develop,
I
can
post
to
the
slack
channel
this
with
some
intro
yeah.
Okay,.