►
From YouTube: CNCF CNF WG Meeting - 2022-09-26
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
A
A
A
So
a
note
so
I've
moved
this
had
the
main
coupon
as
it
in
person
only
which
is
not
it's
just
the
Colo
events
that
are
in
person
so
I've
just
update
that
and
we've
seen
us
shared
a
link
in
slack
which
I've
put
on
here
about
the
marketing
prospectuses
for
color
events.
The
coupon
bu23
is
a
interest
form.
If
you
wanna
fill
that
in
and
find
out
how
much
it
is
to
sponsor
a
color
event.
A
A
A
A
A
For
two
of
them
for
Victor
and
Taylor
to
start
drafting
something
I,
don't
know
if
that's
been
completed
since
or
whether
they're
still
okay,
I,
don't
expect.
This
is
for
these
two,
these
two
yeah
yeah
having
it
started
like
the
document
yet,
but
that
should
be
a.
A
That
document
for
multi-industries
best
practice
this
one:
okay,
cool,
okay,
yeah,
it's
signed
here,
that's
good
and
the
next
one
I
think
was
assigned
to
Taylor
yeah
cool.
B
Recently,
this
one's
a
new
one
on
the
CNF
Dev
yeah,
the
other
one,
was
a
single
category,
but
now
it's
pretty
far
out
of
sync
overall,
so
I
need
to
review
and
and
look
at
the
test
categories
from
the
test,
suite
and
and
then
looking
at
the
best
CNF,
which
was
something
I
think
Robbie
put
together
at
the
start
as
just
a
here's,
a
idea
for
what
we
could
do
so
I
think
this
should
be
more
in
sync,
especially
for
being
able
to
maintain
them.
B
Okay
and
I
think
most
of
the
contents
available
to
to
copy
over
into
those
areas
like
there's
some
stuff
that
was
TBD,
but
there's
a
lot
more
over
in
the
on
the
test.
Suite
side,
so
I
think
it's
more
of
a
like
yeah
compatibility
and
solubility
upgradability
is
a
it's
a
somewhat
collapsed
category.
Instead
of
having
stuff
split
out
so
microservices,
those
are
normal.
Reliability
results,
availability,
I
think
that
one
is
the
same
type
of
category.
Maybe
just
the
naming
was
different.
A
So
I
should
probably
know
this,
but
for
some
of
these,
for
example,
you
know
it's
fairly
clear
what
the
best
practice
is,
and
you
know
what's
being
tested
and
therefore,
what's
plugged
as
being
not
the
best
practice
for
things
like
Network,
latency
or
I,
don't
know
the
increasing
decreasing
capacity.
B
The
different
descriptions
and
informations
about
why
things
are
tested
is
available,
and
so
the
content's
there,
but
it's
it's
going
to
be
in
different
places
on
the
test:
Suite
side
yeah,
so
why
it's
tested
there's
a
a
document
just
for
that
in
the
test.
Suite,
that's
focused
on
the
Y
and
then
the
what
and
the
house.
So
all
of
that's
kind
of
split
out.
B
And
this
is
really
just
talking
table
of
contents.
That's
what
that
tick
was.
It
was
related
to
another
ticket
that
was
about
adding
one
category
to
this
whole
thing
and
that's
been
done.
The
resilience
category
was
added
at
number
10
right,
but
the
reworking
of
the
table
of
contents
is
why
there's
a
new
ticket
and
then
I
think
beyond.
B
That
would
be
probably
a
lot
of
other
tickets
that
need
to
happen
to
to
break
down
the
the
work
on
what
you
were
talking
about,
what
should
be
good
and
take
the
different
tests
and
then
and
then
we're
adding
them
in
as
best
practice.
Now.
What
I
would
say
is
we
start
with
the
ones
that
we
have
one
published
I
there's
we
need
to
publish
the
best
practices
and
then
that
can
be.
You
know
brought
into
that
document
that
document
supposed
to
reference
each
of
the
best
practices.
B
A
B
Right
and
so
he
could
have
us
a
short
little,
some
at
least
reference
the
no
root
in
in
within
the
category
area
of
the
dev
doc.
B
B
B
I
mean,
if
you
know,
ideally,
we
get
some
help,
but
eventually
we
want
it
to
reflect.
That's
you
know.
The
idea
is
to
have
all
of
these
things
tied
together.
We
could
definitely
use
help
the
review.
You
know
reviewing
and
saying.
Okay
can
we
is
it
okay
to
just
match
the
categories
and
if
it
is
then
that'll
make
it
a
little
bit
easier?
B
A
A
B
Implemented
or
anything
is
it
tested?
Would
if
we're
going
to
do
that,
then
we
could
link
over
like
runtime
analysis.
This
has
a
section
referencing
Falco,
but
it
doesn't
it
I,
don't
think
it
links
directly
to
the
no
rooting
containers
test
over
there,
but
we
could
do
that
would
be
a
cross
cross
length
on
that.
A
I
think
it
would
be
useful
just
to
kind
of
get
a
clearer
view
on
the
link
between
the
working
group,
best
practices
and
the
test
Suite
tests
and
then
and
then
we
can
over
time,
probably
more
clearly
delineate
having
the
the.
Why
on
in
the
working
group
and
the
how,
in
the
test,
Suite
I'm
not
having
to
overlap
and
repeat
ourselves.
B
Yeah,
the
main
thing
is
having
enough
people
to.
Are
we
going
to
have
people
to
maintain
yeah?
If
I,
then
it's
kind
of
been
as
the
tests
were
written,
make
sure
that
there's
some
right
up
in
the
as
the
as
the
why?
But
we
could
split
things
off
if
it
makes
sense
and
there's
a
collaboration
and
ownership
better,
which
we
want
it.
We
want
better
collaboration,
ownership,
yeah
sure
so,
the
the
before
we
go
into
that,
though
the
and
that
should
be
a
new
ticket.
B
Like
add
for
this
one
non-root
add
links
to
the
test
suite
for
the
the
test.
That's
checking
for
non-rit
and
I.
Think
there's
maybe
a
couple
of
variations
so
we'll
need
to
figure
that
out.
A
B
B
Update
this
one
to
to
match
so
the
question
is:
can
we
match
the
categories
in
the
test
Suite
in
this
document?
That's
showing
yeah.
A
B
I
think
it's
probably
a
couple
of
documents
to
look
at
one
is
like
list
of
tests
it
might
be
under
the
is
it
under
the
docs
directory.
Let's
see
test
categories,
oh
there,
it
is
so
open
that
one
and
then
the
other
one
was
called
and
there's
a
link
in
that.
So
you
could
go
to
the
one,
but
there's
rationale.
B
So
if
you
find
the
one
called
root
and
you'll
see
it,
it
goes
to
it.
So
these
are
more
minimal
gotcha.
Can
you
test
Suite,
so
I'm
not
trying
to
duplicate
entire
Focus
document
on
a
best
practice
within
the
thought
Suite,
because
that
the
idea
is
the
working
group
would
have
those
larger
documents
yeah,
but
the
rationale
has
the
short
version
and
a
link
to
more
content
for
each
of
those
that
non-root
link.
Do
you
see
that,
in
the
title
this.
A
B
Is
yeah,
yeah
I
think
you
might
go
to
the
yeah
the
list
of
tests
is
that
what
it
is
yeah
yeah.
A
A
B
Yeah
and
then
you
know
that
provides
more
info,
there's
usage
link
that
link
that
did
the
non-root
go
to
the
code.
Just
the
title.
B
So
we
I
mean
you
know
we
don't
have
to
focus
on
this,
but
that's
there
was
a
question
earlier
about
what
what
are
they
for
that
one
test?
Do
we
have
the
information
on
the
limits
or
whatever
it
was,
and
some
of
them
are
in
the
docks
and
they
keep
being
adjusted
so
we'll
need
to
you
know
if
it
becomes
a
best
practice.
B
We'll
need
to
decide
like.
Is
this
something
that
we're
specifying
and
for
some
of
them
I
anticipate
that
it
may
be
a
range
or
you
know
some
type
of
guideline
yeah?
Here's!
What
he's
saying
and
that's
sort
of
thing
may
change
like
the
startup
time
as
as
more
applications
move
over
and
there's
improvements
and
other
things
then
it
may
reduce.
B
You
know
size
of
applications
what's
reasonable
on
other
things.
Yeah
we'll
have
to
keep
that
in
mind
that
we're
we're
writing
living
documents.
We
don't
expect
them
to
be
set
and
stunned
for
forever,
not
for
18
months
or
a
year.
It's,
however,
long
that
they're,
realistic
and
we'll
update
them.
Otherwise,.
B
Yeah,
and
so
we
can
I
would
probably
say,
link
to
the
list
of
tests
rather
than
the
code,
because
we'll
update
the
the
code
links
in
this
document
anytime
and
yeah
anytime,
that
changes
in
the
code.
So
if
a
test
is
updated,
modified,
sometimes
replaced
because
it's
refactored
out
and
we
get
like
a
a
totally
new
version
from
someone
Upstream
yeah
and
those
will
update,
but
from
the
scene
of
working
group.
If
we
link
to
the
list
of
tests,
then
that
that'll
be
fine
and
then
people
can
click
through
for
more.
A
And
so
not
to
the
rationale,
you
know
keep
that
as
it
is
as
well.
That
makes
sense.
A
A
B
Don't
know
I've
I
think
he's
been
taken
away
from
a
lot
of
this
he's
just
sent
the
first
response
last
week
to
a
totally
different
question
that
Jeffrey
had
and
I
think
he's
probably
not
going
to
be
available.
So
we
want
him
to
just
take
it
on
ourselves.
Yeah.
A
A
Good
okay,
foreign.
A
A
Not
sure
it's
not
in
my
calendar,
it
might
have
just
been
me.