►
From YouTube: Kubernetes Federation WG sync 20180705
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
A
C
D
C
B
D
I
think
so
I
didn't
want
to
talk
about.
It
looks
like
her
funds,
not
gonna,
be
able
to
join
us
today,
but
I
didn't
want
to
talk
about
what
kind
of
multi
cluster
testing
has
been
done.
So
I
think
her
phone
was
talking
about
having
tested
on
two
clusters,
but
without
mini
cube
and
I.
Don't
think
the
doctor
and
doctor
the
cube,
ATM
doctor
and
doctor
solution
supports
multi
multiple
clusters.
Somebody
please
correct
me
if
I'm
wrong
there
so.
B
C
D
I
see
so
yeah
I
think
if
we
do
something
like
that,
that
could
work
and
then
you
can
use
any
other
1.9
or
any
other
version
of
a
kubernetes
cluster.
But
the
the
reason
I
want
to
bring
this
up
is
because
they
use
a
guide
documents.
The
walkthrough
on
testing
the
deployment
of
the
Federation
control,
plane
and.
A
C
Actually,
like
past
couple
of
days,
I've
been
working
on
this
right
now,
so
I
took
her
not
at
released
a
mini
cube,
binary
from
a
CI
bail
which
merged
that
one
dot
Levin
related
one
issue
was
there
in
mini
cube,
so
I
think
I
I
picked
that
and
then
I
brought
up
a
cluster
with
one
Levin
in
mini
cube
and
I
was
able
to
deploy
the
fetish
incre
to
plane
in
that
and
able
to
join
the
member
clusters.
So
the
only
thing
I
didn't
do
was
running
e
to
e.
C
D
D
C
It
was
one
more
issue
related
to
profile.
That
is
also
masjids.
It
looked
like
that,
whatever
you
issue
you
pointed
Ivan,
so
that
is,
must
I
believe
and
then
the
only
thing
is
now.
It
is
not
yet
released
version,
that's
it.
So
you
pick
up
some
CI
build
ocean.
I
think
it
should
be
good
enough
to
run
I.
C
C
C
Yeah
I
have
a
different
issue,
but
I
was
able
to
run
two
mini
cube
clusters.
I
ran
into
the
issue
because
I
needed
a
cluster
with
load,
balancer
service
support,
so
I
was
using
a
metal
lb
and
that
caused
some
issue
with
our
our
perp
inning.
Actually,
so
that's
a
different
issue.
Actually,
it's
not
related
to
profile,
ideally
yeah.
B
D
Let's
I.
B
Can
folks
see
my
screen?
Yes,
okay,
so
the
the
first
one
in
this
list
is
a
line
federated
cluster
with
cluster
registry
that
refers
to
a
the
federated
cluster
resource
should
become
namespace
to
match
the
cluster
registry
cluster
resource
I
know
murrow's
got
a
poll
open
for
that
one
already.
That's.
B
B
B
D
B
D
Alpha,
we
can
add
it
as
a
subsequent
plus
we're
sort
of
they're
sort
of
we're
sort
of
transitioning
to
rely
on
a
later
version
of
queue
builder,
as
well
as
the
latest
kubernetes
versions.
So
I
don't
want
to
code
something
up.
That's
just
gonna
change
in
the
follow
on
alpha
release.
I
just
don't
want
to
hold
up
the
release
for
that.
Well,.
D
B
That
was
that
was
the
original
intention,
so
I
think
that
I
do
think
this
is
pretty
important
to
have
for
the
first
alpha
release
in
the
sense
that,
like
we,
we
had
it
agreed
to
it
and
as
a
group
and
I,
if
there's
some
hurdle,
that
makes
it
hard
to
if
there's
some
hurdle,
that
makes
it
hard
to
implement
the
like
example.
As
a
script,
then
maybe
we
can
look
at
having
a
simplified
version.
D
Of
running
through
some
hoops
and
and
jumping
through
some
hoops
there
but
I
think
having
at
least
a
user
guide,
update
and
a
development
update
makes
sense,
and
then
we
can
work
on
a
test
script
that
possibly
deploys
to
one
cluster
again.
I
feel
like
it's
no
different
than
the
unmanaged
été
test.
So
to
have
it's
really
just
a
matter
of
like
running.
Go
test
against
your
your
setup.
D
B
A
I,
just
drank
back
so
I
erased
a
boat
that
renaming
is
simple.
I
did
add
a
version
also
to
queue,
Fred
and
I.
Think
the
versioning
is
something
which,
ideally,
we
should
consider
for
all
the
binaries
I
guess
the
controller
binary
and
queue
Fred
vote
ideally
should
have
similar
or
same
version
right.
A
So
so
the
one
that
is
shared
on
your
screen
right
now
is
just
the
renamed
to
you.
It's
not
to
queue
friend
that
I
have
a
full.
What
I
did
also
add
into
that
is
a
version
for
cube
friend
right
now.
There
is
no
version
option
in
queue,
Fred
or
I,
guess
in
controller
manager,
also,
although
I'm
not
sure
about
controller
manager.
But
when
we
do
release,
we
should
ideally
have
some
versioning
scheme
for
our
binaries,
the
binaries
that
are
part
of
the
release.
Oh
I.
B
A
E
A
A
A
So
what
I
have
done
right
now
is
I
mean
that
that
discussion
need
not
happen
in
the
meeting
that
can
happen
over
the
issue.
All
the
food
in
person
also,
what
I
have
done
is
I
have
put
in
a
version
named
we
to
dot
o
dot,
o
alpha
dot
zero,
so
I
mean
to
me.
It
somehow
sounds
that
this
rep,
oh
and
this
work
that
we
are
doing
is
to
dot
o
off
or
the
second
version
of
that
Federation
of
thought.
So
the
binaries
might
also
have
known.
A
B
A
A
So
I
guess
Quinton
did
raise
this
issue
so
right,
which
is
labeled
as
alpha
right
now,
which
says
that
clean
and
Q
nod
to
the
list
of
the
three
issues.
Lastly,
were
listening
prior
to
this
yeah
around
that
time,
when
Putin
did
raise
it,
we
have.
We
have
had
this
discussion
in
the
group,
and
the
plausible
suggestion
was
this-
that
we
incremental
e-version
the
binary.
The
name
could
be
same,
but
we
incrementally
versions.
And
finally,
so
to
me
that
sounds
like
a
good
good
idea.
B
A
B
A
B
B
A
So
so,
if
you,
if
you
look
at
what
I
meant,
was
like
API
evolution,
if
you
look
at
that,
so,
for
example,
auto-scaling
api
auto-scaling
api
has
a
v2
also
right
now,
so
they
started
v2
with
some
new
water
scaling
api
and
that
v2
is
alpha
right
now
we
they
have
a
mature
v1,
which
is
already
a
ga
version,
and
they
have
some
1.9
or
something
similar
with
the
caters
release
scheme
also
right,
each
new
version
can
have
alpha,
then
a
beta
and
then
something
else.
This.
B
This
is
more
than
just
like
the
release
versions,
though,
so,
if
we,
if
we
are
gonna
call
this,
the
version
of
these
API
is
to
be
B
1,
alpha
1,
it
probably
shouldn't,
have
a
version
number
that
it
starts
with
a
2.
So
we
probably
need
to
look
at
like
the
the
API
version
versus
the
release
version
and
those
should
line
up
so
like.
Maybe
that
means
that
we
should
change
things
to
meet
you
alpha,
1.
A
A
I've
put
through
two
links
in
the
chat
window:
that
is
what
my
suggestion
is.
As
of
now
like,
we
should
have
maybe
a
version
file
or
version
get
method
which
is
sort
of
a
global
right.
Now,
it's
I
didn't
limit
only
pop
you
fit,
but
that
can
be
used
across
binaries
and
that
remains
consistent
for
all
of
us.
Whenever
we
do
our
release.
B
Yeah
I
mean
your
your
suggestion
makes
sense
to
me
or
fun
I'm,
not
sure
yet
about
the
the
versioning
scheme.
So
let
me
think
about
that,
and
but
I
I
agree
that
fish,
what
you
suggested
in
terms
of
like
implement
the
the
implementation
that
you
should
seems
fine
to
me.
What
kubernetes
and
other
projects
in
the
community
do
is
load
the.
B
B
A
So
and
images
are
already
I
mean
there's
some
already
going
on
then
yeah
yeah
I
I
did
not
get
a
clear
idea
about
the
images.
So
currently
what
happens
is
or
what
I
understand
is
that
once
appeared,
merge
or
post
merge?
There
is
a
trigger
which
I
mean
trigger,
which
will
build
the
images
and
push
the
images
to
a
known
image,
location
in
the
Travis
CI
right,
yeah.
B
A
Is
this
either
you
or
didn't
say?
Are
you
going
to
update
this
to
be
based
out
of
a
tag
also
like
menu,
rather
than
pushing
each
time?
If
it
is
not
useful
for
CI,
we
don't
need
to
have
so
many
images
there
right,
yeah.
A
So
the
best
option
might
be
that,
whatever
version
we
decide
that
this
is
going
to
be.
We
tagged
that
as
a
gate,
I
mean
we
put
it
as
a
gate
tag
and
when
we
do
that,
that
is
a
trigger
to
build
the
images
and
make
the
reviews
and
this
gate
information
also
is
used
in
the
version
information.
That's
how
the
gate
is
also.
Does
it
yeah.
B
A
A
E
A
Is
this
courage
to
have
hyphens
in
the
package
names
and
all
like?
We
can
always
specify
the
output
name
of
the
binary,
but
if
you
build
as
default,
it
will
build
with
the
name
of
the
package
so
currently
it
which
is
cubic
you
floored,
but
if
you
put
the
name
of
the
packages
cube
Fred
V
I'm,
not
sure
that
we
are
following
the
guidelines
or
that
works
also
I'll
never
see
the
package
name
like
that.
I
mean
when
I'm
when
I
say
package.
It
means
that
Wolong
packages
yeah.