►
From YouTube: CNCF TOC Meeting 2021-09-14
Description
CNCF TOC Meeting 2021-09-14
A
A
D
D
F
B
B
I
I
Worker's
own
abstraction
of
devices
instead
of
a
age
platform,
so
I
mean
that
this
project
ideally
can
work
with
edge
platform
to
provide
attraction
for
edge
devices.
So
this
is
something
I
can
figure
out
from
their
documentation,
but
I
I
actually
asked
several
maintainers
are,
for
example,
kobe
age,
so
they
mentioned
that
they
do
have
intention
to
have
this
into
integration
with
this
project,
but
still
there
require
a
lot
of
effort,
so
they
still
have
no
plan
to
begin
to
put
effort
to
implement
that.
But
ideally
I
think
that's
the
relationship
of
those
projects.
D
G
D
B
F
D
B
K
D
D
D
L
Yeah
my
two
senses
from
everything
I
hear
it
is
a
popular
project
in
terms
of
usage,
but
I
think
I
share
the
same
set
of
concerns
around
adoption,
but
given
kind
of
sandbox,
one
of
the
purposes
to
encourage
more
contribute
contributors
and
allow
folks
to
collaborate.
I
think
I
I
would
give
it
a
thumbs
up.
D
So
I
did
find
the
current
list
of
maintainers.
There
are
four
maintainers
it's
in
in
the
metal
lb
repository
under
code
owners,
so
they
have
four
people
right
now
already
and
they
have
a
dock
that
has
a
you
know
how
what
do
they
look
for
when
adding
new
maintainers
and
removing
old
maintainers,
so
they
have
some
some
of
these
already
set
up.
G
A
D
D
E
H
C
D
H
D
A
D
I
D
Cube
both
q
fed
one
and
two
were
kind
of
like
huawei
projects.
One
you
know
was
really
bad
and
two
was
slightly
better
but
nobody's
taking
care
of
cube
fed
anymore
once
the
huawei
folks
stepped
away.
I
think
you
know
we
are
in
the
process
of
mothballing
it.
The
sig
multi
cluster
is
not
even
looking
at
q
fed
for
the
for
the
longest
time.
So
you
know,
I'm
I'm.
Okay,
with
the
concepts
that
they
had
in
v2
ended
up
in
karmarta
is
what
I
got
from
reading
through.
E
G
F
L
L
D
D
D
C
D
C
A
G
G
It's
a
applica,
you
know
application
developer
framework.
I
mean
there's
a
little
over
looking
at
it
there's
a
little
bit
of
it
does
generate
qpml
files
for
deployment,
but
it's
primarily
developer
focused.
It
mentions
go
micro
as
it's
kind
of
closest,
similar
thing,
which
I've
looked
at
a
little
bit
a
while
back.
G
E
I
B
I
I
B
A
G
G
H
I
D
I
G
I
I
I
G
B
E
I
Users
are
diverse
from
intel
alibaba,
multiple
companies,
so
I
personally,
my
personal
feeling
of
this
project
is
good.
It
actually
involves
a
lot
of
companies,
including,
I
think,
vmware,
a
lot
of
folks
who
are
working
on
this
era.
I
think
the
only
issue
is
better.
We
believe,
for
example,
intel
interns
technology
is
industry
standard,
or
it's
not
right.
So,
besides
that,
I
think
the
project
itself
is
quite
open
and
have
a
very
straightforward
user
value
to
me.
H
I
I
think
that
is
a
good
sign.
It
means
that
anybody
who's
working
on
this
kind
of
technology
are
for
are
trying
to
work
in
collaboration
trying
to
collaborate
on
this
project.
This
is
a
good
side
to
me,
so
I
think
the
only
issue
is
for
whether
we
want
to
you
know,
adopt
a
project
which
targets
specifically
on
intel
sgx.
J
J
G
Nitro
isn't
actually
in
hard
and
isn't
a
hardware
trusted
execution
environment
per
se
or
well
or
partly
it
is,
but
in
I
think,
mostly
it's
not
an
ncpu
one,
because
it's
not
yeah,
I
am
amd
and
arm.
Obviously,
yeah
arm
is
working
on
this
stuff
as
well
and
they're
all
yeah
they're,
all
currently
independent.
G
J
C
G
K
K
G
I
I
think
one
thing
that
I'm
have
concern
is
that
this
project
is
not
as
active
as
a
database
should
be,
it
seems
very
required
in
terms
of
the
committee's
issue.
The
pro
request,
which
I
do
you
have
concerns
things
like
I
I
worry
about
this-
could
be
or
is
maybe
a
you
know,
just
a
project
that
opens
source
code
without
a
very
active
and,
and
you
know,
healthy
community
behind
it.
This
is
one
thing
that
currently
loves
me
most.
B
D
E
G
D
D
D
K
When
we
send
a
sandbox
application
over
to
one
of
the
tags,
oftentimes,
what
I'm
hearing
us
say
is.
We
have
specific
concerns
that
we
would
like
to
have
have
the
tag
help
us
flesh
out.
Do
we
provide
that
level
of
detail
over
to
the
tag
and
say
here's
some
concerns
that
we're
looking
at
or
because
I'm
concerned
that
they
go
and
present
and
if
they
haven't
addressed
the
concerns
that
we're
talking
about
then,
are
we
back
to
square
one
and
they've
done
what
we've
asked
them
to
do
and
now
we're
still
like?
E
D
G
L
Yeah,
it
sounds
like
they're
trying
to
bite
off
a
lot
and
you
know
having,
I
think
one
of
the
areas
they're
talking
about
is
like
object,
storage
and
having
worked
with
a
cozy
project.
That's
trying
to
do
that.
Just
for
object
and
seeing
how
difficult
it
is.
I
kind
of
question
how
viable
it
is
to
tackle
even
more
than
that.
A
F
I
I
personally
all
think
that
I
think
we
should
for
now
hold
for
this
kind
of
phoenix
logic.
Workflow,
I'm
not
sure
if
it
actually
alive
is
the
cnc
project,
the
directional
goal.
For
now.
We
may
want
to
discuss
that
about
this.
I
I
so
this
is
actually
another
workflow
workflow
engine
for
developers
to
build
a
phoenix
logic
thing
like
that.
D
A
Right
in
the
interest
of
time,
I
am
not
going
to
try
to
move
us
on.
We
will
pick
up
with
open
elb,
which
is
a
reapplication
in
our
next
meeting.
Two
months
from
now
is
going
to
be
november,
9th,
yes
november
9th,
so
we
will
come
back
to
this
november
9th
and
go
through
the
rest
of
the
list
in
here.
Thank
you
all.
We.