►
From YouTube: CNCF TOC Meeting 11-16-2021
Description
CNCF TOC Meeting 11-16-2021
C
C
C
D
D
I'm
not
sure
whether
it's
more
like
a
solution
for
kubiage
from
my
perspective
and
I'm
not
sure
if
this
relationship
is,
is
a
good
for
an
independent
project
or
it's
more
like
a
ecosystem
project
of
kubih,
and
you
guys
may
also
check
his
documentation
at
least
at
first
glance.
It
seems
more
like
a
solution
combined
with
kubih.
B
D
Rat
hole
just
workers
on
isolating
networking,
which
is
common
in
iot
or
edge
co
user
cases.
I
believe
kubeh
has
some
native
features
regarding
to
this,
but
they're
more,
like
you
know,
specialized
focus
on
this
field.
Just
like
you
know,
kubernetes
has
flannel,
but
there
is
calico
which
can
bring
more
values
to
to
the
project.
I
think
this
is
their
focus
and
position.
C
D
F
G
B
F
C
I
I
mean,
I
wonder:
if
tag
security
might
want
to
take
a
look
too.
I
mean
it's
ipsec
channels
with
certificate-based
authentication
but
like
how
do
they
distribute
certificates?
And
I
mean
how
do
they
do
key
management?
That's
the
hard
thing
with
ipsec
is
getting
keys
to
the
right
place
and
things
like
that.
G
B
B
G
C
E
E
D
D
C
C
G
J
B
B
There's
one
sentence
in
the:
why
do
you
want
to
contribute
that
most
of
it,
I
think,
is
very
clear
and
and
sensible,
but
it
says
acunox.
The
founding
organization
behind
cubama
works
on
a
product
that
specializes
in
runtime
security
engines
for
cloud
native
environments
with
all
this
cntf
seems
to
be
the
right
avenue
for
procurement
to
reach
towards.
H
B
C
C
B
C
D
This
is
very
unclear
to
me
whether
how
he
or
his
company
can
you
know,
maintain
this
project
in
the
long
term,
at
least
based
on
its
documentation.
I
can
not
get
this
information,
I
search
it
a
little
bit.
It's
also,
you
know.
Even
in
chinese,
it's
not
very
they're.
Not.
There
are
not
not
a
lot
of
content
relating
to
that.
B
D
G
D
Think
it's
yeah.
It's
really
interesting.
We
just
want
to
make
sure
it's.
You
know
a
formal
maintenance
project
instead
of
a
personal
project.
All
right,
I
searched
a
little
bit.
I
found
some
blog
in
chinese.
It's
mentioned
that
it's
coming
from
a
company
which
named
luimon
it's
basically
a
security
company
in
china.
It's
something
it
looks
like
it's.
It
is
an
internal
tool
from
them
and
then
they
open
source
that
this
is
as
far
as
what
I
can
see,
but
not
a
lot
of
the
information.
E
Contributors
right
and
yeah-
and
I
also
think
it's
a
very
interesting
project,
but
if
they
want
to
get
more
contributors,
they
should
probably
like.
I
see
a
lot
of
issues
that
are
filed
in
mandarin,
for
example,
and
wechat
is
useful
for
communication,
so
it
should
be
probably
more
inclusive,
like
maybe
slack
and
issues
in
english
yeah.
I
wonder.
B
Whether
we
should
encourage
them
to
go
and
talk
to
taxi
security,
partly
because
I
think
there
are
probably
a
lot
of
people
in
that
tag,
who
the
same
as
me
love
the
idea
of
like
oh,
I
could
just
install
a
vulnerability
like
that.
That
would
be
so
useful
and
maybe
that
could
encourage
a
bit
more
contribution.
B
K
J
C
C
C
But
yeah,
I
think
I
think
it's
app
delivery,
but
I'm
not
sure
that's
why
the
question
of
this
planner,
because
I'm
not
sure
that
app
delivery
would
necessarily
want
to
be
involved
in
it.
I
mean
problem
yeah.
I
do
like
the
fact
that
they
want
to
build
a
community
around
supporting
people
in
their
journey
to
cloud
native,
which
I
think
is
in
scape,
but
I
don't
know
if
I
think
the
community
around
that's
more
in
scope
than
tools.
B
C
G
C
C
They've
I
mean
maybe
they've
found
things
that
work
better
than
the
customers
than
we
did.
I
mean
I'm,
which
I'm
you
know
it's
a
red
hat
project,
I'm
sure
it's
of
value
but
to
customers,
or
it
wouldn't
have
gone
to
this
stage.
But
there's
a
I
don't
know,
there's
a
lot
of
there's
a
lot
of
question
marks,
just
in
my
mind
about
this:
the
space
as
a
as
a
whole
and
the
what
and
what
you're
telling
what
what
you're
telling
customers.
That's
why?
K
H
H
C
H
I
B
K
C
H
A
B
C
G
G
B
I
feel
like
they
may
have
filled
in
the
form
in
a
bit
of
a
hurry.
They
said.
Please
explain
how
your
project
is
aligned
with
cloud
native
ecosystem.
It
aligns
very
well
with
clevernesses
and
persistent
storage
projects
and
then
explanation
of
alignment.
We
don't
see
any
overlap
with
existing
cntf
projects.
I
mean
you
could
argue.
We
asked
the
same
question
twice,
but.
H
I
C
C
H
K
I
So,
regardless
of
valero,
I
think
this
is
something
probably
worth
having
tag.
Storage
look
at
to
do
kind
of
an
assessment
on
how
it
fits
into
the
overall
ecosystem,
and
I
think,
it'll
be
similar
to
the
other
storage
projects
where
we
need
to
come
up
with
a
strategy
for
how
do
we
position
if
we
have
multiple
kind
of
projects
in
this
space?
So
far
we
don't
have
any.
So
I
think
it's
worth
at
least
talking
to
tag
storage
and
having
them
present
what
the
technology
is.
B
Any
hesitation
I'm
having
right
now
is:
we
seem
a
few
times
today
to
have
been
saying.
Oh,
we
should
get
a
tag
to
look
at
this
and
that
does
seem
like
we're
setting
a
higher
bar.
You
know
we
seem
to
be
slightly
moving
back
towards
the
you
know,
getting
the
tags
to
assess
things
before
they
go
into
sandbox.
H
C
I
C
C
B
B
How
are
we
doing
for
time?
We've
got
five
more
minutes.
I
don't
think
we're
going
to
get
through
the
whole
list,
but
yeah
no
we're
definitely
not
going
to
get
through
the
whole
list,
but
at
least
we've
made
some
progress
last
call
for
any
particular
projects
that
we
want
to
bring
up
that.
We
think
we
could
get
through
in
five
minutes.
K
So
the
background
here
is,
we
were
looking
to
start
a
client,
a
kubernetes
client.
You
know
generated
client
for
rust,
and
apparently
this
was
already
there.
So
during
the
process
of
hey,
let's
open
a
new
repository,
let's
see
who's
in
interested
in
trying
to
gather
people.
These
people
showed
up,
saying,
hey,
we
already
have
some
stuff
and
some
of
the
things
that
we
are
doing
is
already
used
by
crosslit
and
other
places.
K
K
So
they
want
to
like
bump
up
the
usage
of
rust
in
cncf
and
be
the
the
core
which
will
be
used
by
other
rust
projects
in
cncf.
Crossland
was
the
example
that
they
were
going
for,
so
they
want.
So
it's
generated
code,
kubernetes
api
plus
on
top
of
that
they
are
doing
the
controller
runtime
equivalent
as
well.
D
Yes,
we
also
use
this
project
as
well
in
our
rust
project,
so
I
I
actually
agree
with
dims.
Although
this
kind
of
thing
looks
like
it's
a
another
version
of
keiko,
but
it's
really
not
focused
on
kubernetes
api
machinery
itself.
It
focuses
more
like
the
ecosystem
benefits
and
integrations
with
the
other
existing
sunset
project
and
the
upcoming
new
project.
That's
why
I
also
think
it's
better
for
them
to
be
a
sensitive
particular
than
a
kubernetes
project.
D
K
We
are
having
a
terrible
time
getting
people
to
all
the
different
language,
libraries,
even
with
an
apa
missionary.
You
know
the
python
one
is
still
going
on
fine.
You
know
java
brendan
comes
wise
now
and
then
to
update
stuff,
but
I
think
it's
good
to
have
this
set
of
people
in
a
championing
rust
in
cncf.
I
I
think
the
only
concern
I
have
with
that
is
we
have
I
pasted
a
link
to
the
kubernetes
clients.
Github
work,
all
the
other
languages
have
something
there,
and
so,
if
we
have
like
a
one-off,
that's
completely
independent
and
a
standalone
thing
that
has
challenges
around.
You
know
discoverability
and
just
consistency.
K
I'm
not
too
worried
assad,
they
also
generate
code.
They
do
it
slightly
differently
from
the
open
api
schema
so
and
they
already
have
users.
So
it's
not
like.
We
are
starting
from
scratch
and
there
isn't
anything
existing.
In
fact,
it's
the
other
way
around
right.
If
we
start
something
and
we
don't
really
have
people
to
back
it
up,
then
it
becomes
like
a
shell
of
something
and
which
is
going
to
be
competing
with
qrs
and
kubarius
is
already
there
right.