►
From YouTube: KCP-Edge Community Meeting, December 15, 2022
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
Hi
everybody
and
welcome
this
is
the
December
15
22
Sig
kcp
Edge
community
meeting.
Today
we
don't
have
a
lot
on
the
agenda
to
discuss.
I
think
this
is
mostly
just
a
vote
on
whether
or
not
we
should
have
any
more
meetings
for
the
rest
of
the
year
just
to
go
over
really
quickly.
The
contributor
code
of
contact
that's
contributing
maintainers
in
the
cncf
community.
A
In
the
interest
of
fostering
an
open
and
welcoming
committee,
we
pledge
to
respect
all
people
who
contribute
through
reporting
issues,
posting
feature,
requests,
updating,
documentation,
submitting
pull
requests
or
patches
or
in
other
activities.
So
basically,
please
everybody
just
be
nice
to
each
other
on
the
call,
that's
the
the
real
resounding
message
I'd
like
to
get
across
anyway.
So
with
that
we
did
have
a
couple.
Things
in
the
agenda.
First
is
to
vote.
A
A
Secondly,
we
were
going
to
look
over
an
RFC.
The
document's
been
posted,
it's
inside
of
Google
Docs.
It's
specifically
on
policy
distribution
and
bringing
policy
and
workload
distribution
together
as
one
or
at
least
that's
the
aim
of
the
document
to
move
in
that
direction.
A
There's
a
lot
of
initial
things
that
have
been
reviewed
by
the
team
outside
of
the
community
meeting
that
need
to
be
cared
for
so
they're,
not
quite
ready
yet
to
talk
about
it
here
in
the
in
the
public
forum,
but
you're
free
to
join
and
use
the
doc,
as
you
see
appropriate,
to
make
updates
and
changes.
I
encourage
you
all
to
take
a
look
at
it
and
at
that
point,
when
we
do
review
it
in
January,
I
guess
we'll
go
over
and
assign
the
issues.
A
B
No
I
I
think
we
so
just
to
give
a
quick
background.
So
what
we
try
to
do
is
usually
we
would
start
with
a
design
document.
So
here
we're
working
on
on
a
request
for
comment
which
is
like
the
the
stadium
before
the
design
document
that
we're
trying
to
basically,
you
know
solve
the
I
mean
describe
the
problem
that
we're
trying
to
do
agree
that
this
is
a
problem
that
we
want
to
solve,
Define,
clearly
the
space.
What.
C
B
The
things
that
need
to
be
you
know
addressed,
and
then
the
next
stage
for
this
would
be
to
to
create
a
you.
D
B
B
A
B
Yeah
but
I
I
just
want
to
mention
that
right
now
this
is
work
in
progress,
so
I
would
definitely
I.
Would
you
know
it'll
change,
even
if,
if
you
guys
are
reviewing
it
right
now,
it'll
it'll,
you
know
it'll
still
change,
and
it
will
not
be
necessarily
in
this
format.
By
the
time
we
we
meet
next
time.
A
All
right,
okay,
so
does
anybody
have
anything
else,
they'd
like
to
add
to
the
agenda
or
discuss
today?
I
know
that
there's
been
some
activity
that
June's
had
we'll
go
through
the
items
that
have
not
yet
been
assigned
status
or
to
to
anyone
in
particular
in
just
a
minute,
but
I
want
to
make
sure
that
we're
okay
with
all
the
items,
if
we've
exhausted
all
the
items
in
the
current
agenda,.
A
E
I
think
this
is
just
about
some
plumbings
we're
going
to
use
to
further
development
right
now
when
I
decouple
the
controller.
It's
just
is
a
simple
main
file.
Mind.Gov
doesn't
even
accept
Flags
Etc.
We
want
to
use
the
the
well-known
Library
which
is
Cobra
to
to
implement
the
plumbing
for
the
future
development.
E
A
E
61.
one.
A
E
I
just
closed
one
I
think
it's
59
I,
don't
know
if
you
look
at
the
thumb
column.
E
Yeah
59,
since
in
the
community,
I
asked
NDG
and
eagle's
name
for
help.
We
always
with
regard
to
the
listing
problems,
listing
the
placement
and
locations
and
if
we
scale
down
scale
down
or
we
can
see
that
the
root
reason
AB.
Yes,
the
rotation
is
being
the
version
of
the
kcb
server
I'm,
using
in
my
code.
E
E
So
when
I
switch
to
the
main
the
main
branch
it
works
as
expected.
So
that's
actually
the
reason
on
the
controller
doesn't
list
placement
and
locations.
I
put
my
the
output
of
my
terminal
here,
so
you
can
see
clearly
what's
happening
with
this
issue.
A
C
Thanks
just
a
quick
note:
Yuji
there's
an
outstanding
or
pending
invite
to
the
kcp
dev
GitHub
org.
Hopefully
you
got
it.
If
not,
let
me
know
and
I
can
try
and
resend
it,
but
everybody
else
that
Andy
that
you
had
me
invite
has
accepted.
F
I
have
a
question
since
we
are
here,
I
think
what
requirement
that
came
out
of
I
think
was.
The
policy
work
that
qg
was
working
on.
I
was
about
this
idea
of
upsyncing
policy
report
that
is
generated
on
the
physical
cluster,
for
example,
for
Kevin
right,
so
you
basically
submit
a
policy
on
the
kcp
side.
This
is
propagated
to
the
physical
cluster.
F
The
controller
on
that
side
will
create
a
policy
report
and
the
idea
was
to
be
able
to
somehow
think
that
back
to
kcp,
so
I
saw
that
there
is
some
work
going
on
for
think
persistent
volume
currently
to
do.
Upsyncing
I
was
wondering
there
is
any
plan
on
kcp
to
somehow
generalize
this
ability
to
upsync
resources.
D
Yes,
at
least
we
envisioned
the
app
thinking
not
only
for
the
PVS,
even
if
it
was
the
you
know,
starting
use
case.
We
already
have
requirements
of
for
app
syncing
for
pods
in
a
limited
way,
of
course,
or
at
least
controlled
way
and
as
well
for
endpoints,
because
you
need,
for
example,
for
K
native.
You
need
to
check
endpoints
to
know
if
a
given
application
is
is
effectively,
you
know,
start
up
and
running
and
for
ports
as
well.
D
In
order
to
be
able
to
do,
you
know,
put
logs
or
put
exec,
you
need
at
least
to
have
some
sort
of
pod
proxies.
Are
you
know
limited
version
of
of
PODS
absynced
to
to
kcp,
so
the
mechanism
is
is
designed.
No
no.
There
is.
There
is
an
ongoing
work
here,
not
finished,
but
it's
it
has
been
designed
to
be
really
generic,
though
Limited
in
the
application
of
it.
D
Mainly,
we
don't
want
obviously,
to
completely
open
the
door
to
let
any
you
know,
thinker,
sync
anything
you
know
in
in
kcp,
so
for
now
it's
it's
I
think
there
is
probably
a
hard-coded
list
of
things
that
can
be
absinct,
but
once
again
it's
it's
completely
managed
in
the
app
thinker
virtual
workspace.
There
is
the
same
way
as
for
the
thinking
there
is
a
dedicated
virtual
workspace
for
upsyncing,
and
so
here
we
could
think
about.
You
know
adding
some
way
to
configure
that
to
allow
other
objects
to
be
absinct.
D
But
apart
from
that,
absyncing
is
really
a
generic
mechanism.
You
just
have
to
add
a
given
level
on
the
downstream
object
with
a
namespace
locator,
which
is
an
annotation
which
defines
where
you
want
your
object
to
end
up
on
kcp
side
in
which
kcp
workspace,
in
which
case,
in
which
case
and
based
on
this
the
upsyncing
occurs.
So
there
is
nothing
that,
in
theory,
would
prevent
you
to
obsync
some
other
type
of
of
objects.
F
Right,
but
who
has
this
label
on
the
downstream,
for
example,
if
I
have
suppose
I'm
integrating
with
some
open
source
approach
like
I,
don't
know
Kevin
or
even
cross-plane?
There
are
similar
use
case
where
there
are
connection
sequence
being
created,
so
I
was
gonna
put
that
label
on
that
Downstream
object.
D
Yeah,
so
the
labels
on
the
I
mean
for
I
mean
for
The
Limited
use
cases
we
had
until
now.
The
level
on
the
downstream
object
is
mainly
just
the
same
level
as
what
you
have
on
the
Upstream
objects
when
you
want
to
sync,
but
instead
of
the
sync
value,
it
has
the
upsync
value,
so
the
request
State
level
that
so,
if
it's
a
thing,
then
the
object
will
be
taken.
D
Downstream
and
absinct
Upstream
with
this
level
as
well,
which
allows-
and
it
will
be
created
with
this
level
Upstream,
which
allows
you
know
as
defining
rules.
That
are
quite
important-
that
if
you
have
an
object,
that
is
at
least
in
appsync
mode
of
sync
mode
for
at
least
one
sync
Target.
It
should
not
be
synced
to
any
other
SIM
Target
at
the
same
time,
because
that
means
that
this
object
is
effectively
owned
by
the
physical
cluster
who
created
it,
who
absent
it.
D
D
Yes,
obviously
because
because
this
is,
you
know
the
the
the
really
limited
cases
where
the
initial
I
mean
the
origin
of
kcp
object
is
Downstream,
so
you
need
to
have
some
process
that
will
Express
this
intent.
I
want
to
bring
a
downstream
object,
absync
it
Upstream,
so
I
mean
in
any
case
you
need
to
express
this
intent,
and
so
you
have
to
have
some
sort
of
agent
Downstream
to
to
look
like
this
I.
D
But
of
course,
if
you
have
some
more,
you
know
use
case
specific
relationships,
you
know
owner
refs
or
some
other
type
of
relationships
between
objects.
Like
you
know,
PV,
PVC
and
PV
through
the
claimeriff
for
example,
then
you
would
have
a
dedicated
controller
Downstream
that
will
follow
those
rules
and
flag
the
the
a
corresponding
object
and
label
the
corresponding
objects.
Accordingly,
the
objects
that
should
be
absinct,
so
we
really
try
to
to
decorate.
D
F
F
D
Yes,
it's
in
I
mean
this.
Is
these
are
work
in
progress
requests,
but
not
you
know
United
States,
you
know,
maybe
that
we
can
share
them,
but
I
think
one
or
two
weeks
after
after
you
know
the
beginning
of
the
year.
We
should
it
should
be
much
much
clearer
here,
but
obviously
you
know
it's
clear
that
in
our
cases
the
absinct
objects
are
mainly
really
basic:
Cube
objects
like
PVS
PVCs
puts
or
endpoints.
F
D
I
assume
we
could
do
you
know
this
way,
sure
this
would
make
sense
and
possibly
just
a
configuration
in
your
workspace
or
in
a
namespace
or
on
kcp
itself
on
a
kcp
flavor
to
say
the
appsync
virtual
workspace
will
accept
also
this
type
of
object,
in
addition
to
the
limited
subset
of
objects
we
support
today,
but
that
could
be
configuration.
I
think.
D
Yes,
that's
why
you
know
I
think
as
soon
as
we
envision
app
thinking
as
a
not
only
a
generic
mechanism
for
internal
needs
for
internal.
You
know
TMC
needs,
but
mechanism
that
would
be
opened
to
external
third-party
components.
D
Then,
obviously,
we
will
have
to
think
about
this
permission,
things
that
you
mentioned,
but
for
now
it's
it
would
probably
be.
You
know
some
additions
into
into
the
Sinker
airbag
rules.
For
now
we
already
have
some
some
rules
that
you
know
only
allow
the
Sinker
service
account
to
access
the
virtual
workspace,
the
Synchro
virtual
workspace.
F
D
E
A
Okay,
all
right,
everybody
thank
you
for
joining
I.
Think
I'll
take
a
look
at
the
results
of
the
poll
in
just
a
few
minutes
and
plan
and
schedule
accordingly.
A
Thank
you
very
much
for
all
your
contributions
this
year
and
if
I
don't
see
you
before
the
the
New
Year
everybody
enjoy
the
rest
of
your
your
month
of
December,
happy
holidays
and
happy
New
Year.