►
From YouTube: CNCF CNF WG Meeting - 2021-11-15
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
C
I
trust
you
haven't
been
up
to
anything
to
untoward
while
I've
been
on
holiday.
A
A
A
A
C
Right,
we
might
be
a
minute
earlier,
but
I
think
it's
worth
getting
moving
so
welcome
everybody
to
the
regular
cnf
working
group
meeting
and
I'm
out
of
touch
because
again
I've
been
away
on
holiday
for
a
couple
of
weeks,
so
I
haven't
been
in
been
to
the
last
couple
of
meetings,
but
I'm
just
catching
up
with
what
we
have
in
the
agenda.
C
A
I
did
participate
in
a
panel,
that's
that
first
one
there,
the
etsy
nfv
panel
discussion.
A
C
Okay,
all
right
beyond
that,
we
have
so
that's
the
yeah,
the
chinese
kubecon
effectively.
I
don't
think
we've
got
very
many
people
from
the
asian
side
of
the
world
with
us
this
morning.
We're
not
exactly
set
up
very
well
for
timing
on
that
anyway,
but
again,
any
recommendations
I
see.
We've
got
one
mentioned
in
there,
which
is
an
edge
computing
discussion
which
actually
proved
quite
interesting.
I
would
think.
C
Fair
enough
so
yeah
mobile
world
congress,
obviously
about
the
biggest
event
of
the
year.
I
don't
know
what
papers
anyone
might
have
filed,
or
you
know
requested
there,
but
obviously
that
can
be
quite
difficult
to
get
anything
with
anything
accepted
simply
because
it
is
such
a
large
event.
C
I
see
we
have
a
european
networking
edge
summit,
which
will
be
nice,
although
god
knows
whether
or
not
how
how
actual
physical
attendance
will
work
out
for
that
you
never
know
and
then
we're
off
into
the
distance,
although
that
kubecon
deadline,
I
recognize,
is
what
four
weeks
out.
I
guess
at
this
point.
So
if
we
want
to
actually
get
any
anything
into
kubecon
eu,
then
now
would
be
a
good
moment
to
get
it
sorted.
B
I'll
mention
the
oran
community
is
talking
about
a
face-to-face
meeting.
I.
A
B
Probably
in
coordination
with
mobile
congress,
I'm
not
sure.
C
Both
oh
yeah,
the
mwc
and
yeah.
That's
what
you
mean!
Yeah
that'll,
be
interesting,
so
you've
got
your
ear
to
the
ground.
On
that
side
of
thing
you
can
keep
us
up
to
date,
then.
C
Good,
okay,
reviewing
the
open
pull
request
is
going
to
be
really
really
easy
because
we
don't
have
any
open
pull
requests,
so
I
I
think
we're
doing
very
well
at
the
moment.
I
don't
quite
understand
how
we've
got
that
clear.
It
got
the
backlog
cleared,
but
very
promising
which
taylor
leaves
you
to
your
best
practice.
Category
updates.
A
All
right
all
right,
let's
focus
on
my
screen,
yeah
yeah.
We
see
all
right.
So
this
is
what
we
have
now,
the
one
category,
that's
I
guess
not
showing
on
the
working
group.
It
is
in
the
test
suite
and
it's
something
we've
talked
about
for
a
while.
I
think,
there's
a
issue
is
a
resilience.
A
We
just
haven't
ever
done
a
pull
request
to
add
it
after
getting
feedback
for
a
while
on
the
different
categories
and
where
best
practices
could
go
testing
the
different
concerns-
and
I
guess,
focus
on
areas
that
would
be
relevant
to
what
we're
focusing
right.
Now,
we've
looked
at
making
some
updates
and
possible.
A
The
idea
was
to
shrink
it
down
a
little
bit
with
some
of
the
overlap,
but
not
the
ones
that
were
still
talked
about
a
lot.
So
here
is,
if
I
can
move
forward-
and
let's
see
this
is
where
we're
looking
to
go
right
now,.
A
So
from
this
10
down
to
7.,
the
configuration
life
cycle
would
be
one
where
it's
somewhat
split
up
and
merging
with
others.
It's
such
a
large
area
that
you
could
put
a
whole
lot
of
things
under
it,
so
the
configuration
is
now
which
may
get
a
new
name.
A
The
idea
is
to
focus
on
the
declarative,
configuration
aspects
for
best
practices,
whether
that's
apis
or
the
deployment
configuration
or
tying
in
with
whatever
else
there
and
some
of
the
parts
of
life
cycle
where
you
look
at
best
practices
or
tests
that
already
exist
and
there's
already,
I
don't
know
what
the
total
number
is.
I
think
it's
over
30
something
tests
that
are
live
in
the
test.
Suite
would
get
merged
over
into
different
places
like
this
compatibility
and
solubility
and
upgrade
ability
which
used
to
be
installation
upgrade.
A
A
A
We
did
keep
security
separate
because
it
seems,
even
though
it
could
go
into
every
part
of
the
process
from
initial
design
all
the
way
through
the
production,
operation
management
right
now,
it's
such
a
big
focus
that
we've
kept
it
separate.
A
C
So
this
is
mainly
from
the
testing
that
you're
re-categorizing.
Is
that
what
you're
saying
that
that's
what
made
you
has
made?
You
rethink
the
categories
right.
A
Yes,
so
the
the
test
suited
as
I
guess
it
still
has,
because
it
hasn't
changed
yet
ten
categories,
the
cnf
working
group
categories-
has
nine,
it
doesn't
have
the
resilience
yet
so
the
test
suite
is
looking
at
merging
and
making
it
a
little
bit
easier
to
see
where
the
different
tests
are.
There's
a
lot
of
information
that
would
be
related.
I
guess
documentation
related
to
each
test
about.
Why
is
this
tested?
That's?
Why
is
it
important
how
it's
related
to
a
best
practice?
A
A
And
I
think
it
was
might
have
been
ravi
who
did
this
originally
like
a
this,
was
kind
of
an
initial
structure
for
the
best
practice
we
haven't
put
anything
in
here
yet,
but
I
guess
we
could
update
it
to
have
the
the
non-root
that'd
be
under
the
security.
We
don't
have
that
listed
here,
but
yeah,
but
that
would
be
related
to
how
it
relates
here.
So
the
test
categories
and
try
to
have
them
in
sync,
with
the
best
practice
categories.
C
Okay,
well,
I
think
the
easiest
way
to
do
that
would
be
for
you
to
try
and
pro
pro
propose
a
pull
request
for
the
document
that
you
just
had
on
screen.
If,
since
that's
the
major
place
where
the
categories
are
used,
and
we
can
see
if
we
like
the
result
of
it,.
C
And
I'm
presuming
that
this
is
still
open
for
debate
on
both
sides,
that
if
we
had
some
suggestions
on
how
those
categories
could
be
done
slightly
differently,
we
could
go
back
to
the
testing
group
and
talk
with
them
about
alternatives
as
well.
A
What
are
the
concerns
and
what
type
of
attributes
or
behavior
at
the
highest
level
like
reliability,
resilience
availability
right
where
state
this
is
about
handle,
handle
state
in
the
blood
anyway.
But
what
are
the
things
that
speak
to
a
service
provider
and
do
these?
Do
we
need
to
adjust,
maybe
just
descriptions
and
then
from
the
creator
side
what
things
are
relevant
right
now
that
are
when
adopting
cloud
native
practices?
What's
something
that's
relevant
to
keep
in
mind.
A
And
if
there's
feedback
on
that,
whether
it's,
let's
make
sure
and
describe
it,
you
know
robbie
put
in
some
stuff
here
that
they
get
these
started,
that's
fine
or
if
there's
like
different
names
or
wordings
like
configuration,
I
was
mentioning.
Maybe
that
may
need
to
say
declarative
configuration
or
you
know
some
other
thing:
we've
adjusted
state,
I
think
three
times
or
four
times
trying
to
get
it.
What
okay
there
but
yeah
love
to
hear
any
feedback
that
folks
have
including
now,
if
anyone
has
anything.
E
E
So
does
that
mean
I
need
to
read
the
set
of
best
practices
cover
to
cover
before
I
even
attempt
to
design
my
cnf
or
or
can
we
come
up
with
some
kind
of
a
flow
chart
or
cookbook
or
like
a
step-by-step
saying,
okay,
start
here,
look
at
those
best
practices.
First,
then,
as
you
start
implementing
look
at
those
I
mean,
I'm
not
sure
it
can
be
done.
E
I'm
saying
it
would
be
nice
if
we
can
do
something
like
that,
I
might
give
it
some
more
thought
and
come
up
with
some
initial
proposal
for
it,
but
I
don't
know
what
other
folks
think
if
something
like
that
would
be
necessary,
or
is
it
possible
to
create
something
like
that
in
addition
to
this
set
of
categories,
I.
A
I,
I
guess
is
my
personal
view
on
it.
I
would
hesitate
to
say
someone
needs
to
start
in
one
specific
place
before
they
get
going.
If
there's
a
lot
of
it's
going
to
be
based
on
how
you
became
a,
I
guess,
developer
creator,
you
know
your
background
on
that.
So
your
approach
can
be
very
different
and
you
may
have
you
know
different
things
within
a
an
organization
where
they
say
we
do
this
first
and
I
I'd
say
probably
the
first
thing.
A
The
only
thing
I'd
say
is
it's
good
if
you
try
to
figure
out
who
your
end
users
are
and
then
work
backwards
from
their
needs
to
how
you're
going
to
do
it.
As
far
as
the
best
practices
goes,
when
we're
saying
like
cloud
native
best
practices
for
networking
applications,
which
is
what
we're
talking
about
proposing,
I
would
say
you
look
for
those
whenever
you're
building
out
your
your
application.
That
would
be
my
approach.
Someone
else
may
say:
I'm
going
to
go,
learn
the
best
practices
and
know
them
before
I
start.
A
For
getting
started
use
cases
user
stories,
any
documentation
that
helps
people
build
applications
is
going
to
be
a
good
thing.
E
Yeah,
I
I
see
your
point
and
I'm
still
a
little
bit
concerned
about
how
do
we
help
people
not
miss
any
of
the
best
practices
or
overlook
things
and
discover
them
too
late
in
the
game.
As
I
said,
I'm
not
sure
I
have
a
very
good
solution
for
that.
I
I
had
this
kind
of
walk
through
flow
chart.
Whatever
checklist,
I
don't
know
I'll,
give
it
some
more
thought
and
if
I
can
come
up
with
a
good
idea,
I'll
share
it
with
the
group.
A
Imagine
if
it's
for
me
it
would
be
easier
to
start
with
a
specific
problem
and
work
backwards.
So
if
I'm
trying
to
create
an
application
that
needs
to
handle
state
like
a
some
type
of
I'll,
just
say
database
for
not
having
a
better
word
and
my
there's
a
core
part
of
the
application
that
needs
to
store
data,
and
I
need
to
keep
track
of
it.
And
I
need
that
to
be.
You
know
resilient
redundant
and
everything
else.
A
Well,
then,
I
could
start
looking
at
what
are
practices
for
running
something:
that's
storing
data
on
a
kubernetes
platform.
A
I
guess,
outside
of,
like
anything
with
regard
to
best
practices
we
do
need
them
published,
I
think,
for
people
to
be
able
to
find
them.
So
that
would
be
one
thing.
So
if
anybody
wants
to
help
on
publishing
best
practices
based
on
your
experience,
then
please
just
jump
right
in
or
reach
out
to.
A
You
know
one
of
us
and
ian
or
myself
or
anyone
else,
that's
actively
working
on
these,
and
we
can
try
to
start
drafting
and
get
some
out
so
we'll
have
to
have
that
other
than
other
than
the
work
here
like
as
far
as
a
tool,
if
you're
building,
if
you're
creating
applications
and
you're
wanting
to
try
to
follow
best
practices.
The
cnf
test
suite
is
specifically
designed
to
help
with
that,
like
it's
we're
trying
to
create
it
as
a
tool
to
help
a
developer
to
catch
things.
A
So,
there's
a
lot
of
stuff
that
so
ben
he's
on
the
call
as
part
of
a
cubescape
project
and
that's
a
security
focus
tool
and
there's
direct
integration
into
the
test,
suite
that
uses
kubescape
and
it
can
do
scanning
for
various
vulnerabilities
or
essentially
best
practices.
Some
are
around
the
nsa,
kubernetes
hardening
guide.
A
We
have
stuff
from
litmus
chaos
for
doing
resilience,
type,
testing
and
a
bunch
of
others
configuration
and
other
things.
So
some
of
these
are
more
on
the
implementation
side
versus
the
documentation
that
the
working
group
does
documenting
a
lot
of
content
to
have
a
deeper
understanding.
A
But
if,
if
you're,
if
you've
had
any
experience
with
test
driven
development,
then
the
test
suite
can
be
a
good,
a
good
tool
in
your
toolbox
for
helping
to
check
things
as
you're
moving
along,
and
I
think
you
might
have
been
speaking
and
I've
been.
If
you
wanted
to
respond
and
go
ahead.
C
No,
I
haven't
been
speaking.
I
was
listening
along
with
that.
I
think
it
would
be.
I
mean
this
is
personal.
This
is
not
meeting
issue,
but
I
think
I
have
kind
of
lost
touch:
how
to
apply
the
the
test
kit
that
we
you
you've
got
and
and
exactly
how
it
would
help.
So
I
suspect
I've
got
some
personal
research
to
do
on
that
side
of
things.
C
Other
than
that.
I
believe
this
was
the
last
topic
I'm
here
on
the
list
and
unless
anyone's
been
doing
updates,
which
I've
just
checked
for
then
we're.
Basically,
we
have
nothing
else
to
talk
about
at
this
point,
so
anyone
else
got
anything
else.
They'd
like
to
raise
today.
C
Okay,
well,
in
that
case,
you
get
half
an
hour
back.
Thank
you.
Everybody
for
your
time
have
a
think
about
what
you'd
like
to
talk
about
next
week.
What
wants
to
go
on
the
agenda
and
I'll,
see
you
again
in
a
week's
time.