►
From YouTube: CNCF CNF WG Meeting - 2022-07-11
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
So
co-chair
results
we
were
able
to
complete
the
elections.
Finally,
thanks
for
putting
yourselves
forward
and
going
through
the
process
and
final
results
so
for
the
service
provider
representative
tom
kiplin
from
vodafone,
hey
tom,
congratulations.
A
Cnf
developer,
so
this
is
representing
vendors
and
network
equipment
providers
and
anyone
creating
cns,
victor
morales
from
samsung,
and
then
the
cncf
kubernetes
community
co-chair
taylor
carpenter.
That's
me
so
our
term
would
have
started
earlier
in
the
year,
but
because
the
elections
were
this
far
out,
we've
adjusted
the
terms
to
first
of
july
through
june
30th
2023.
A
So
a
few
events
folks
are
probably
aware
of
mostly
so
upstairs
summit
cubecon
a
in
october,
I'm
currently
planning
on
going
to
that
myself,
we'll
see
how
things
are
going
as
far
as
covet
spikes
and
all
of
that
for
in-person
events.
But
if
it's
looking
good,
then
I
plan
on
being
there
anyone
else
on
the
call
planning
on
being
at
kubecon
earthware
in
person.
A
A
A
Another
thing
that
needs
to
happen
is
sponsorship,
so
if
anyone
your
company's
interested
or
whatever
you
want
to
help,
I
need
to
get
get
that
going
and
the
on-e-s
there's.
I
guess
it's
still
open
right
now
through
the
29th
for
submissions,
and
there
are
some
panels.
I
don't
know
who
all
has
been
looking
at
the
different
things
there,
but
there's
a
panel
that
we
may
be
talking
on
for
regarding
these
cncf
telco
initiatives,
including
the
working
group
essay,
but
primarily
around
the
cnf
certification
and
aniket.
I
know
that's
one
of
them.
A
C
C
You're,
referring
to
the
are
you
referring
to
a
specific,
the
specific
conformance,
cnf
conformance.
A
C
Yeah
I've
actually
myself
taking
some
con.
You
know
I'll
be
having
some
conversations
this
weekend.
You
know
internally
here
in
my
company,
just
to
figure
out
whether
or
not
we're
attending
so
I
haven't
been
on
top
of
this
too
much,
either
until
just
recently
there's
some
things
that
caught
my
attention.
But
let
me
find
the
link
and
I'll
share
that
on
the
chat
here.
A
All
right
so
does
anyone
have
anything
else.
I
don't
see
anything
written
out
on
the
agenda.
C
Well,
I
I
wouldn't
mind
adding
something
to
the
agenda
taylor
or
maybe
just
bring
it
up
for
discussion
here
I
with
with
the
new
newly
elected
chair
and
co-chairs,
I'm
wondering
if
you
know
and
again
I
don't
want
to
preempt
anything.
You
guys
are
already
planning,
so
I
mean
one
of
the
things
that
would
be
interesting
is
just
kind
of
you
know.
A
year
has
ended
in
terms
of
you
know
the
chair
and
co-chairs
what
what
is
our
thinking
going
forward?
C
C
D
Good
question
my
point
of
view:
I
think
the
cns
certification
program
has
got
to
be
the
main
focus.
It
seems
to
be
the
flagship
thing
without
this
working
group,
but
I
I
agree
with.
I
can't
remember.
C
Yeah
I
appreciate
that
tom
I
I
would
also.
I
agree.
I
think
you
know
certainly
seeing
the
cncf
cnf
conformance
program
is,
is
certainly
focused.
I
I
have
some,
you
know
questions
I
guess
still
on
ways
of
working
around
you
know.
C
In
the
past
we
have
submitted,
you
know
we
kind
of
open
up
to
user
stories
and
and
use
cases,
and
I
I'm
guilty
as
charged,
but
I
you
know
I
have
submitted
use
cases
and
use
stories
and
really
not
figured
out
how
to
take
it
from
there
to
the
next
step,
which
is
really
you
know,
a
discussion
around
best
practices,
and
I
I
mean
I
obviously
know
I
could
go
away
and
I
could
write
some
best
practices
and
air
them
with
this
group,
but
I
don't
know
if
there's
a
better
way
to
do
it,
where
you're
more
engaged.
C
B
B
So
I
don't
know
if,
following
or
like
encouraging
to
use
more
something
more
informal
or
something
more
light
in
that
way
could
be
to
increase
the
collaboration
or
something
like
I
don't
know
like,
but
definitely
we
have
to
to
to
encourage
others
to
participate
and
make
easier.
The
the
collaboration.
A
One
of
the
things
that's
been
suggested
is
around.
A
How
I
guess
the
process
for
getting
things
through
pull
requests
quicker
and
we
may
have
had
some
of
the
items.
A
Where
it
takes,
you
know
more
people
than
are
actually
working
are
willing
to
put
in
the
time
right
now
and.
A
A
So
how
do
we?
How
do
we
actually
get
a
lot
of
the
content
that
we
already
have
written?
It's
not
coming
right,
brand,
new
content,
but
content.
That's
already
there
like
around
the
least
privileged
principles,
there's
a
large
amount
of
content
that
we
actually
have
in
a
document
tied
in
with
working
group.
A
I
mean
it
was
directly
related,
so
I
don't
know
if
it
means
something
related
to
getting
the
content
into
the
format
that
we
already
have,
or
if
that
is
maybe
there's
a
problem
with
the
process
and
and
the
requirements
to
actually
get
it
to
a
point
where
we're
willing
to
publish
something
on
the
use
cases
and
user
stories.
A
We're
able
to
put
a
lot
more
of
those
forward,
probably
because
the
requirements
on
the
amount
of
information
about
them
was
lower
and
our
best
practice
template
is
pretty
large
not
to
say
that
those
things
aren't
important
but
like.
If
we
want
to
move
things
forward,
then
we
may
need
to
re-examine.
A
Anyways
but
I'd
I
would
like
to
get
the
best
practice.
More
best
practices
actually
put
out
and
probably
from
a
working
group
standpoint,
and
maybe
this
can
be
with
co-chairs
looking
at
the
cns
certification
and
what's
there
and
what
that
relates
back
to
stuff
we've
already
been
talking
about.
We
already
have
content
and
try
to
get
best
practices
out
of
that
actually
published.
D
I
was
just
wondering
if
that,
that
kind
of
rationale
for
what
we're
doing
or
the
mission
statement
or
whatever
you
want
to
call
it.
If
that's
does
that
already
exist,.
A
Yeah
I
mean
a
lot
of
this:
is
we've
kind
of
been
going
down
the
same
general
path
and
it's
continued
to
get
a
little
bit
a
little
bit
more
specific,
I'm
trying
to
look,
oh
I'm
in
governance!
That's
why
I'm
having
a
hard
time!
D
A
D
How
will
they
help
that
yeah
or
something
yeah,
okay,
I'll,
follow
up
in
the
chat,
because
I
think
I
think
the
the
link
with
the
cnf
certification
program
and
test
suite
is
quite
clear.
I
think
the
link
with
other
sigs
and
tags,
whatever
they're
called
nowadays,
is
less
clear
or
how
we
could
achieve
that.
A
C
Taylor
at
the
risk-
you
know,
I
don't
know
again
just
kind
of
time
back
to
what
I
was
saying
earlier,
and
I
don't
know
if
it's
just
me
so
again
by
all
means.
If
anyone
has
you
know
a
different
opinion,
please
let
me
know,
but
one
thing
that
I
think
still
is
helpful
is
just
to.
I
think
this
page
is
useful,
but
I
think
it
it's
also
for
those
of
us
who,
may
you
know
not
be
clear
from
you,
know
how
we
are
achieving
our
goals
right.
C
C
I
guess
I
just
sometimes
lack
the
view
of
how
do
we
go
from
start
to
finish,
because
then
that
kind
of
makes
it
more
obvious
in
terms
of
how
or
you
know
what
kind
of
effort
any
individual
will
have
to
make
in
this
work.
So,
for
example,
all
right
use
cases.
There's
been,
you
know,
generated
or
use
cases,
users
or
stories
all
right.
What's
next,
is
it
because
it
can
feel
a
bit?
You
know
lonely
for
lack
of
a
better
term.
You
know
I
write
the
use
cases.
I
write
the
use
user
stories.
C
I
write
the
best
practices
I
bring
them
to
the
group.
I
ask
you
to
review
them.
That's
one
way
to
do
it
and
I
don't
know
if
that's
the
optimal
path
or
if
there's
something
else
which
says
once
you've
done
that,
then
you
know
you
should
be
raising
your
hand
asking
for
people
who
want
to
work
together
in
terms
of
drafting
best
practices
or
writing
a
white
paper
or
whatever
it
might
be.
So
I'm
not
sure
if
that's
clear,
but
just
trying
to
to
elaborate
a
little
bit.
C
A
Okay,
good
questions
comments.
I
I
think
we
actually
addressed
that
in
the
past.
I
don't
know,
but
I
presume
that
it's
probably
a
recorded
call,
but
the
I
don't
know
what
was
documented
around
it
so
related
would
be
this
contributing
document.
A
As
far
as
actually
saying
here
is
step
one
and
here's
the
last
step,
I
don't
know
if
we
have
a
document
I
feel
like
we
may
have
a
document
or
it
may
be
written
out
in
the
meeting
notes
further
down
or
if
we
have
an
archive
version
that
actually
went
through.
What
you're
saying
like
here
is
the
steps.
A
From
I
think,
one
of
the
things
and
the
other
other
markdown
was
talking
about
brainstorming
and
ideas
and
what
are
the
types
of
basically
building
for
the
context,
so
you
want
the
ideas
on
that
user
stories
and
use
cases
are
probably
a
good
place
to
go
from
that
high
level
like
a
here's,
a
user
story
or
use
case
name,
and
you
just
say
in
this
type
of
scenario.
A
Now
you
actually
need
to
write
it
out
and
then
you're
probably
going
to
end
up
with
well
do
we
have
all
the
definitions
around
those
things
and
then
eventually,
when
you
have
the
use
case
and
user
story,
what
you
can
look
at
well,
what
are
what
are
the
different
problems
that
we're
looking
at
in
that?
If
you
break
down
the
individual
pieces
and
what,
how
can
we
deal
with
each
of
those?
A
A
The
reality
is
no
one
always
starts
at
step
one
and
goes
forward.
You
may
already
have
an
idea
and
you're
part
way
in
and
so
you're
going
to
go.
I
already
know
some
best
practices
at
work
in
this
other
use
case.
A
Do
they,
where
do
they
apply,
rather
than
coming
up
with
them
from
scratch?
Let's
try
to
figure
out
some
new
ones,
because
we
have
experience
in
other
areas,
but
writing
out
the
different.
You
know
steps
all
the
way
through
oliver,
so
that
people
can
see
here's
how
it
ties
together
sounds
helpful
and
then,
wherever
someone
wants
to
contribute,
they
can
jump
in.
A
A
A
A
A
A
So
it's
a
similar
thing,
you're
going
to
implement
something
you're
going
to
put
it
out
there
you're
going
to
examine
it
and
see,
you
know,
did
it
work
or
do
we
need
to
make
changes
and
then
we're
going
to
go
back?
Okay,
so
the
use
case
or
user
story
is
still
the
same.
So
what
are
the
other
practices
to
meet
the
gaps.
C
So,
just
out
of
curiosity
taylor's,
so
is
this
we're
basically
saying
that
if
I'm
looking
at
this
contributing.md
document,
when
it
says
what
to
contribute,
you
know
you
can
contribute
a
best
practice.
Are
you
and
to
your
point,
you're
saying
you
don't
necessarily
want
to
force
everyone
to
start
at
step,
one
if
you're
somewhere
else?
So
are
you
suggesting
that
if
I,
if
I
think
I
have
a
best
practice,
I
can
just
start
straight
in
and
saying
here's
here's
the
best
practice.
I
think
that
I'd
like
to
submit
and
there's
no
real.
C
I
mean
if
I
look
at
that
template,
you
know
you
have
or
we
have.
I
should
say
you
know
the
the
user
stories
is
optional,
so
I'm
not
required
to
provide
a
work.
You
know
any
context.
I
can
just
say
here's.
You
know,
here's
a
good.
What
I
think
is
a
good
working
best
practice.
C
How
does
that
you
know?
I
guess
I'm
just
trying
to
understand
how
does
that?
How
what?
What
is
the
criteria
for
that
to
be
considered
as
a
best
practice
versus
something
else
that
there's
more
meat
or
more,
you
know
context
provided
for
it?
Do
you
understand
what
I
mean?
In
other
words,
I'm
just
curious.
I
mean
I
may
have
a
good
idea,
but
it
may
not
have
a
lot
of
underlying
support.
A
Sure
so
I'll
try
to
answer
those
several
questions.
Someone
could
go
right
to
saying
I
have
a
best
practice,
so
the.
A
And
try
to
think
of
another
one
than
the
one
that
we
publish
the
non-root
is
what
came
to
my
mind,
but
not
using
privileged
mode
for
your
containers.
You
know
so
they
go.
This
is
a
best
practice.
A
Where
is
that,
coming
from
it's
not
out
of
the
air,
we're
not
talking
about
people
just
making
up
stuff?
That's
fine!
If
someone
wants
to
make
up
something,
nobody's
heard
of
they'll
still
need
to
communicate
why
they
think
it's
a
best
practice.
So
that
goes
into
what
is
the
acceptance
criteria,
so
the
template-
and
I
believe
the
process
version
have
stuff
listed
here
like
what
is
required.
A
We
can
come
and
adjust
this.
You
know
talk
about
it
as
a
group
and
everything
and
say
if
we
think
differently
so
approver,
so
that
what
is
this
implementable
implementable?
A
So
someone
comes
up
with
some
idea,
but
maybe
kubernetes
doesn't
even
have
some
feature
functionality.
Currently
that
works
with
it.
It's
fine,
but
I
wouldn't
call
it
a
best
practice.
If
it's
not
implementable
on
kubernetes,
you
could
say
it's
a
best
practice
on
another
platform.
That's
totally
fine,
but
trying
to
say
it's
a
best
practice
that
can
be
implemented
on
kubernetes
is
a
totally
different
thing
and
that's
what
we're
trying
to
do
in
the
group
like?
What
can
you
do
right
now?
A
If
you
need
to
use
external
tools
and
have
a
second
platform
that
should
not
be
that's
out
of
scope,
let's
just
say
that's
how
the
scope,
so
that's
why
this
one
is
there
and
so
it's
required
the
motivation
did.
Did
you
provide
a
summary
and
motivation?
I
should
probably
pull
up
one
of
the
existing
ones.
A
Let's
just
do
this
no
root
so
summary
and
motivation.
So
what
do
you
actually?
What
summary
is?
What
is
this
actual
best
practice?
Tell
me
what
your
what
the
best
practice
is.
Okay,
so
it's
saying
you
shouldn't
run
as
this
privileged
user.
Probably
if
we're
talking
unix
based
kernel,
then
uid
0..
So
that's
that's.
What
we're
talking
about
the
user
itself,
not
container
privileges,
nothing
else.
This
is
specifically
about
the
kernel
user.
A
A
A
If
you
don't
have
a
summary-
and
you
don't
have
your
motivation,
then
the
best
practice
is
not
going
to
be
accepted
and
then
from
there
you
know
we
start
providing
more
details
beyond
that,
like
it
talks
about
a
testing
plan.
So
this
is
not
that
tests
are
completed,
they
might
be,
but
is
it
testable
so
some
best
some
implementations
are
harder
to
test
than
others.
A
I
don't
think
anything
you
would
call
it
impossible,
but
if,
if
we
can't
communicate
here
is
how
you
test
the
best
practice,
then
we
can't
verify
the
best
practice.
So
at
least
some
type
of
communication
around
here
are
the
different
things
in
it.
This
isn't
the
test
case
and
spec
and
everything
else
right
now,
but
there
needs
to
be
something-
and
this
is
probably
input
when
you're
talking
with
different
folks
to
whoever
can
help
with
that
so
from
the
I'll
just
bring
up
anika
the
rc
team.
A
So
if,
if,
if
there's
something
there
and
people
are
like
yeah,
we
don't
know
how
to
test
that,
then
that's
going
gonna
be
a
problem
to
at
least
highlight
scoring
this
one's,
probably
something
that
we
should
remove
and
let
or
we
need
to
modify
this
could
tie
into
if
it's
specifically
for
the
cns
certification.
How
that
would
tie
in
would
be
in
my
mind
right
now.
This
is
talking
off.
You
know
just
on
the
fly,
is
it
an
essential
type
of
best
best
practice?
A
Would
we
say
everyone
should
absolutely
do
this
so
non-running
processes?
Non-Root,
I
think,
is
a
pretty
essential,
but
you
have
may
have
others
that
we
go.
No,
absolutely
everyone
should
do
this.
There's
no
questions
now
it
doesn't
mean
that
there's
no
exceptions,
but
we're
saying
this
is
very
strongly
recommended
best
practice.
A
A
I
don't
think
we
actually
highlight.
Actually,
let
me
see
up
here.
User
stories
say
optional,
that's
optional.
References
are
not
optional.
A
So
the
use
cases
and
user
stories
are
highly
recommended
right
now
we
don't
have
the
marked
required,
maybe
because
I
you
know,
I'm
not
sure,
but
maybe
because
there
may
be
something.
That's.
A
Obviously,
a
agreed
on
best
practice
and
there's
a
lot
of
references
like
this
one,
even
if
you
didn't
have
our
own
user
stories
for
this
no
root
and
containers
best
practices,
the
reference
links
would
cover
more
than
what
we
have
in
that
context
to
provide.
A
If
it
makes
if
it's
needed,
though
we
can
go
through
and
adjust,
you
know
what
do
we
think
are
required
and
optional
and
what
we
may
add
or
modify
for
this
particular
set.
But
I
would
say
this
is
the
end
goal.
Oliver
for
a
lot
of
the
content,
maybe
it's!
The
end
goal
is
to
have
a
a
list
of
best
practices
that
people
can
reference
with.
A
You
know
all
the
content
within
each
best
practice
that
helps
them
understand
why
you
know
why
each
one
of
us
important
is
it
relevant
to
them
and
and
enough
information
that
they
can
go
off
and
you
know
figure
out
how
to
implement
it
for
themselves.
We're
not
implementing
it
for
everybody,
but
if
they
can
understand
enough
and
there's
enough
references,
then
they
can
say
yep.
This
is
relevant
to
me.
I'm
gonna
try
to
do
this.
A
If
we
take,
I
guess
if
you
know,
if
everyone
agrees,
that
that's
a
good
goal
like
a
list,
a
list
of
best
practices
that
people
developing
cns
or
validating
that
cns
are
following
a
set
of
best
practices.
If,
if
the
goal
is
we're
going
to
have
this
list
and
it's
going
to
have
relevant
information,
then
how
do
we
make
that
process
easier
to
follow
so
that
we
can
publish
more,
and
you
know
what
is
actually
required
and
not
required
as
relevant?
I
think
would
go
into
that.
Oliver.
C
Yeah,
I
I
appreciate
that
taylor
and
I
guess
it
was
implied,
but
I
think
to
your
I
mean
for
me.
The
end
goal
has
been
fairly
clear,
wanting
the
best
practices
and
a
list
of
those
so
that
that's
not
been
so
much
of
a
question
for
me
but
to
your
point,
maybe
also
part
of
the
end
goal.
Is
this
published
best
practices
or
you
know
you're
talking
about
cnf
vendors?
C
You
know
being
able
to
look
upon
them
and
say
whether
or
not
this
is
you
know
valid
or
not
valid
or
something
they're
going
to
use
or
implement,
and
I
guess
it's
also.
This
is
also
feeding
into
other
work
streams
like
the
cnf
test,
suite
so
and
the
conform,
and
thus
the
conformance
program
as
well.
So
it's
you
know,
there's
a
chain
of
things
that
are
taking
place.
C
One
very
quick
question:
victor
taylor:
when
you
were
showing
the
contribution
page
there,
there
was
a
point
about
implementable
and
it
looks
like
this
label
or
something
I
I
you
can't
click
on
it.
Where
do
we
get
a
definition
of
that?
C
C
C
A
Sure
I
think
we
should
expand
on
it.
You
know
the
simplest
would
be
implementable.
A
Add
a
add
a
message:
you
know
you
can
link
to
this
all
right.
C
A
Yeah
sounds
good,
so
we
can
get.
You
know
what.
Maybe
one
of
the
things
that
we
can
do
is
go
through
these
documents
and
see
yeah
good
idea
create
an
issue
that
when
you
get
a
chance
oliver
can
you
please
create
an
issue
for
that?
It's
in
the
document
for
any
of
the
ones
where
you're
thinking
I
don't
know
what
this
is
or
can
we
adjust
or
add.
A
And
then
we
can
go
through
and
look
at
any
of
these
and
decide.
A
B
B
I
don't
know
like
provide
more
use
cases
or
less
practices
in
this
case,
so
maybe
we
should
plan
in
the
next
session
to
to
think
about
more.
B
How
can
we,
if
we
need
to
modify
something,
I'm
not
talking
about
moist
and
emission,
probably
the
way
to
achieve
that
mission,
maybe
while
brainstorming
and
suggesting
new
ideas
or
something
like
that.
A
A
We
have
a
lot
of
it
so
already
written.
So
when
I'm
saying
this,
it's
okay
to
say,
we
already
haven't
pulled
the
content.
The
idea
would
be
to,
I
think,
which
goes
along
with
what
you're
seeing
victor.
A
B
B
So
probably
we
can
provide
decent
a
space
for
others
to
share
ideas
and-
and
I
mean
not
necessarily
to
to
to
have
to
write
it
down,
use
cases
or
best
practices,
because
at
least
sharing
what
they
have
done
in
their
own
companies
for
their
own
projects,
to
provide
cnf
and
just
trying
ideas
like
to
specific
topics
or
specific
problems
that
they
face.
B
Just
use
this
as
a
space
and
and
just
explain
or
put
some
or
just
sharing
chain
ideas.
I
guess,
and
that
way
we
can
use
it
and
not
wait
until
the
next.
You
know
talk
today
and
for
for
having
the
opportunity
to
share
all
these
things,
because
also
we
have
that
limited
time
in
the
particular
days.
So
probably
you
can
use
this
as
an
opportunity
for
for
all
them.
A
All
right
y'all,
if
there's
nothing
else,
we'll
stop
here
and
maybe
come
back
next
time.
Do
we
want
to
start
with
documenting
the
process
to
have
a
best
practice
published
like
from
start
to
finish,
and
then
we,
after
that,
we
can
decide
if
we
have
time
to
start
examining
any
gaps
or
stuff
like
definitions
that
are
not
there.
A
A
I
would
say
that
we
have
some
best
practices
as
forward,
but
we
don't
have
them
in
a
list.
We
don't
have
them
where
we're
saying
here
is
the
the
ones
that
we're
saying
are
essential
and
you
know
very
important,
so
that
would
be
another
one.
Oliver
like
what
is
the
different
levels
of
contribution
of
a
best
practice
before
it's
production,
ga
ready
or
whatever,
so
we
can
communicate.
I
think
all
of
that
can
be
part
of
this,
so
the
process
from
where
it
goes
from
an
idea
all
the
way
until
it's
probably
you
know.