►
From YouTube: CNCF CNF WG Meeting - 2022-03-07
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
B
C
B
B
C
Right,
okay,
let
me
get
the
meeting
minutes
up
and
we
will
begin.
A
C
Right
so
good
morning,
welcome
to
the
cnf
working
group
for
those
of
you,
who've
come
which
seems
like
six
of
us,
so
not
a
huge
meeting
and
probably
not
a
very
long
one
this
morning
right.
The
upcoming
events,
the
reason
the
date
light
saving
is
in
there
is
our
meeting
is
tied
to
utc,
so
it
moves
when
daylight
savings
strikes
so
come
march.
The
13th
the
meeting
will
shift,
I
believe,
to
9am
pacific
as
opposed
to
eight.
C
As
you
know,
that
is
how
it
works
when
utc
is
what
we're
tied
to
and
similarly
it
will
shift
the
same
way
when
europe
moves
on
the
27th.
We've
got
that
funny
two-week
period.
When
we
don't
everything
doesn't
work
together.
We
have
a
set
of
upcoming
events.
The
usual
rules
apply
cfps.
If
you
want
to
put
a
paper
in
then
there
are
a
few
there.
The
open
source
summit
and
well
both
of
the
open
source
summits,
have
cfps
open.
C
If
you
think
you
would
like
some
help
with
that,
then
obviously
we're
always
there
ready
to
help
if
you
need
some
need,
someone
to
bounce
ideas
off
of
or
you
want
your
write-up
to
be
approved,
but
we're
quite
happy
to
help
you,
along
with
that
we'll
do
the
poll
requests
in
a
moment,
but
I
just
wanted
to
mention,
because
we
haven't
got
there
yet,
and
it's
been
on
my
mind
for
a
few
weeks
at
the
moment,
the
chairs
are
me
taylor
and
jeff,
who
unfortunately
hasn't
been
able
to
make
it
for
a
few
weeks,
because
he's
got
a
conflict
for
the
three
different
domains
me
from
the
cnf
creators
developers,
taylor
for
the
community
and
jeff
for
the
cnf
users.
C
Our
term
is
coming
to
an
end
in
about.
I
think
it's
four
or
five
weeks
at
this
point,
so
we
should
probably
send
an
announcement
out
and
make
it
clear
to
everybody
that
if
you
would
like
to
stand
for
the
one
of
the
co-chair
seats
for
next
year,
your
moment
is
here
now.
Is
your
chance
we'll
get
the
details
of
that
sorted?
I
don't
think
we've
actually
planned
it
out.
Just
yet,
but
we
will
get
the
process
in
place.
C
C
Okay,
that's
an
auto-generated
one.
I
see
we
do
have
a
couple
of
phalae
failures
going
on
so
that
will
need
checking
before
we
merge
it.
But
I
don't
imagine
anybody's
got
too
much
of
an
objection
to
that.
It's
just
a
bot
coming
in
and
telling
us
we've
got
our
ci
to
sort
out
because
it's
out
of
date,
so
I
guess
taylor
and
I
will
go
and
double
check
that
and
see
what
we
have
to
do.
C
C
Yeah,
I
don't
see
anything
to
I
don't
I
wouldn't
call
this
comprehensive,
but
I
don't
think
there's
any
particularly
objectionable
elements
in
here.
I
don't
see
much
in
the
way
of
sources
in
the
sense
of
this
is
why
we
should
be
doing
it.
When
was
this
one
created
in.
A
About
seven
days
ago,
all
right
yeah
exactly
seven
days
ago,
so
when
ben
added
these,
he
talked
a
little
bit
last
week
and
I
went
through
the
best
practice-
I
guess
spec
or
template
or
whatever,
that
we
have
and
talked
with
them
a
little
bit
about
references
and
everything
and
if
you
notice,
this
is
also
under
the
user
stories
yep
so
it'll
need
to
move
over.
I
think
it's
a
good
start
for
the
conversation
around
this
particular
best
practice.
C
Yeah
I
mean
I'm
not
sure
this
needs
a
user
story.
I
think
we
all
accept
that
there
are
certain
things
that
are
considered
to
be
good,
that
you
should
do
with
kubernetes
right
and
I
wouldn't
worry
terribly
much
about
justification,
but
if
we
did
have
some
degree
of
sourcing
to
say
this
is
why
we
think
these
are
the
best
practices
we
have
and
why
we
haven't
bothered
to
put
others
in
then.
C
That
would
certainly
help,
but
I
would
rather
we
committed
it
before
much
longer
than
made
it
completely
comprehensive,
because
something
is
better
than
nothing
and
again
I
don't
see
anything
terribly
objectionable
here.
So
that's
a
good.
A
Point
so
I
would
say
it:
it
should
be
moved
over.
It's
one
of
the
things
which
I
already
told
them,
and
then
the
related
thing
is.
We
should
probably
review
and
update,
what's
required
in
the
proposals
best
practice
proposals
area,
because
we
do
have
some
things
that
are
required
that
we
may
not
care
about.
At
this
point.
C
C
At
least
yes,
absolutely,
I
know
we've
got
a
document
in
the
format
that
we
should
be
using.
I
don't
think
that
changes
very
much
of
what
he's
written.
I
think
it
just
means
we
cut
and
paste
over
to
the
format
we'd
like,
but
yeah
particularly
hard
job.
C
But
yeah
I
mean
in
general
what
is
there
to
object
to?
This
all
looks
like
fairly
sensible
stuff.
C
Okay,
so
that's
job,
one
is
a
formatting
problem
and
then
references
if
we
can
find
them.
C
I
think
actually,
I'm
not
so
bothered
about
that,
but
if
we,
if
there
are
any
obvious
ones,
we
can
at
least
ask
him.
A
C
Well,
yeah
I
mean
iteration
is
effectively
a
pull
request
on
the
existing
best
practice,
so
that
should
be
having
a
best
practice
to
iterate
on
having
this
committed
would
would
solve
a
bunch
of
problems
for
that
givers
working,
okay,.
A
I
think
one
thing
that
maybe
this
one
needs
is
to
be
a
more
explicit
name,
because
it's
can
you
go
back
into
the
file
changes,
so
I
think
it
just
says
configuration.
Is
it
configuration.
C
Best
practices
of
kubernetes
system
components,
yeah
best
practices,
so
I
guess.
A
A
C
I
don't
think,
there's
necessarily
a
problem
that
a
best
practice
has
checklist
items.
You
know
more
than
one
checklist
item.
I
I
unless
there's
a
reason
to
separate
them
out
into
multiple.
I
wouldn't,
but
I
mean
the
synopsis
needs
to
be
a
little
more
explanatory.
C
Shall
we
say
nearly
all
of
this
is
best
practices
for
the
purposes
of
security,
from
what
I
can
read
here,
which
makes
which
he's
managed
to
put
in
there
but
he's
put
in
there
as
a
subtitle
as
opposed
to
the
actual
title.
C
So
if
we,
I
imagine,
that's
because
he
was
thinking
this
would
want
to
be
broadened
out,
but
if
we
actually
get
ahead
of
that
and
just
say
no,
this
will
be
the
security
best
practice
part,
and
if
there's
more
than
you
know
for
efficiency
for
reliability,
then
we
keep
those
independent.
C
Then
we
would
basically
be
good.
That's
how
I
would
do
it.
B
A
Agree
to
that,
but
they
are,
they
don't
agree
to
that
one,
but
they
agree
to
everything
else.
So
they
don't
turn
that
on
and
then
what
do
we
say
that
they're
not
following
which
pri
I'm
I'm
getting
to
the
point
where
if
a
service
provider
is
looking
and
saying
which
best
practices
are
you
following
and
they'd
say?
Oh,
we
follow
the
configuration
best
practices
except
they
didn't
follow,
one
of
them
disabling
anonymous
request
or
api
authorization.
C
Configuration
yeah,
but
the
compliance
document
would
say
not
only
that
they
aren't
following
it,
but
specifically
how
they're
not
following
it.
So
again,
we
would
be
covered
in
that
circumstance
it
would
be
written
down
as
to
what
they
were
doing.
It
wouldn't
just
be
a.
I
haven't,
checked
this
box.
It's
I
haven't,
checked
this
box
because
so
I
think
I
see
where
you're
going.
A
For
me,
this
seems
like
a
list
of
best
practices
that
someone
could
implement
each
piece
independently
and
then
within
each
of
those,
like
enable
audit
logging,
there's
actually
a
lot
of
different
aspects
that
you
could
change
on.
That
and
people
may
have
different
preferences
that
are
like.
Where
are
you
going
to
put
your
audit
policy
file
well,
make
sure
that
it
doesn't
stay
on
the
host,
because
then
it
can
be
accessed
if
someone
gains
or
it
can
disappear.
C
A
I'm
saying
that
each
of
these
potentially
should
be
their
own
document
versus
having
them
all
listed.
When
you
go
and
look
at
the
user
story
section
like
the
supply
chain
attack,
it
seems
fine
to
have
them
all
split
out
until
someone
goes.
Oh
this
one's
really
important.
Let
me
do
a
bigger
write-up,
but
this
one
seems
like
they're.
A
C
Yes,
they
could
absolutely,
but
my
question
with
that
is:
is
the
effort
of
breaking
it
down
and
the
spreading
of
the
information
into
multiple
files
actually
making
this
more
useful
to
us?
Or
is
it
just
basically
burying
the
information
making
it
a
little
more
complicated
to
use?
Because
I
think
the
result
works
out
the
same?
You
would
have
to
comply
with
all
of
these
or
you
would
have
to
detail
why
you
weren't
complying
with
some
of
them.
C
A
A
If
we're
gonna
say
that
people
should
do
references,
which
I
think
references
should
be
a
part
of
any
of
the
best
practices
put
forward,
then
it
would
be
good
if,
if
there,
if
you're
going
to
have
multiple
practices
included
in
one
document,
to
make
sure
that
you
have
a
reference
for
each
of
them.
Ideally.
A
I'm
still
good,
even
though
I
I
kind
of
lean
towards
splitting
it
up,
I'm
good
with
having.
If
that
happens,
it
could
happen
after
the
first
iteration,
where
we
get
this
in
with
references
in
the
correct
area
and
not
under
user
stories
yeah,
and
then
it
can
be
decided
to
be
split
up
or
added
to
does.
Anyone
else
have
thoughts.
There's
a
lot
for
me
and
I.
A
All
right,
everyone
can
look
at
this.
One
add
comments
I'll
remind
ben
that
we
want
to
move
it
over,
although
I
guess
that
could
happen
after
the
fact,
but
we
do
want
references.
I
think.
C
Yeah,
I
mean
well,
actually,
if
it
comes
down
to
it,
I
would
want
it
to
be
moved
as
a
first
step,
the
references
I
would
take
as
a
wish
list
item
that
we
can't
have
straight
away.
I
can't
see-
I
I
think
one
or
two
of
these
things
could
do
with
a
more
detail
like
the
credential
type
and
detail,
because
this
one
seems
to
be
asking
for
you
know.
C
Yeah,
that's
that's.
That
seems
to
go
through
things
without
actually
saying
you
must
do
x.
It's
simply
saying
here
are
some
notes
that
you
might
want
to
give
consideration
to
so
we
can
actually
set
it
if
we
can
set
a
threshold
against
it
that
that
would
be
maybe
a
little
more
useful.
C
You
know
there
are
notes
here
that
you
could
do
x
that
in
the
passive
voice
it
is
very
important.
We
just
need
to.
You
know,
bring
that
back
to
a
threshold.
You
have
done
this
or
you
are
not
in
compliance,
but
anyway
all
right.
Well,
I
mean
again,
I
I
like
that
it's
a
good
first
start.
I
I
think,
obviously
I
I
have
some
preferences
for
making
it
better,
but
I
wouldn't
necessarily
want
to
see
all
of
those
preferences
dealt
with
before
we
let
it
in.
C
Okay:
next,
oh
yes,.
C
Yeah
this
one's
on
my
homework
thing.
It's
been
sat
here
for
a
month
plus,
and
I
need
to
do
my
homework
on
it.
So,
but
I
don't
see
that
it's
getting
more
comments.
Let
me
take
that
and
run
with
it.
I
will
put
another
pull
request
out
and
and
get
the
comments
that
pankaj
dealt
with
and
and
deal
with
it
most
of
what
he
said.
I
believe
we
agreed
was
recommended
rewording
to
make
it
more
understandable,
but
I
didn't
see
anything
in
there.
C
That
was
desperately
needed
to
improve
the
content.
It's
really
just
the
comprehensibility
that
seems
to
be
in
debate
so
with
a
few
rewordings.
Then
I
would
hope.
That's
ready
for
commit.
C
Which
means
I'll
take
the
work
in
progress
label
off
of
it
as
well.
This
is
jeff's
story,
which
apparently
is
now
some
getting
old,
so
probably
in
need
of
actual
committing.
A
C
Yeah,
I'm
not
seeing
again
huge
objections
to
the
content,
just
niggling
reword
stuff
again,
so
if
we
can
persuade
him
to
do
his
homework
like
I'm
any
better,
but
if
we
can
persuade
him
to
do
his
homework
and
do
a
rewrite
on
this,
then
I
would
like
to
think
that
we
could
actually
be
in
a
position
to
approve
it
next
week
rather
than
debate
it.
That
would
be
good,
but
it
doesn't
again
look
like
anyone's
got
significant
objections.
C
But
yeah
best
held
until
jeff
himself
has
a
opportunity
to
comment
on
that
is
jeff
running
tomorrow.
Next
week's
meeting
as
well.
A
C
Doesn't
it
doesn't
matter,
but
anyway
yeah
we'll
get
him
to
do
a
rework
and
if
we
can
get
him
to
give
it
the
once
over
before
next
week's
meeting,
then
it's
another
one
that
should
be
ready
for
approval,
so
in
terms
of
homework,
then
I
have
my
pull
request
to
update
we'll
see
if
we
can
get
jeff
to
do
this.
C
B
B
Okay,
yeah,
I
can,
let's
take
a
look
at.
B
Well,
I
guess
my
my
comments
were
regarding
other
tools
that
I
discovered
I
mean
nothing
besides
having
new
references,
so.
C
So
this
one
here
is
jeff
talking
about
how
you
do
license
management,
the
applications
on
top
and
that's
gonna,
be
a
little.
C
Difficult
and
asking
for
a
definition,
which
I
think
is
obviously
worthwhile.
It's
like
it's
like
saying
what
is
edge,
what
is
air
gap,
so
I
can
see
where
that
one
takes
us.
B
C
C
If
you
think
it
involves
clarity
in
the
glossary,
then
please
stick
a
pull
request
on
the
glossary
and
then
we
can
get
that
in
first
and
then
jeff's
got
more
to
work
with
whichever
you
like
to
do,
but
the
you
know,
let's
just
try
and
have
this
ready
for
approval
by
the
end
of
the
week
and
again
we
will
go
chase
jeff
and
you
can
certainly
communicate
with
him
in
the
channel
and
get
that
done.
C
C
C
C
This
one
has
no
thumbs
up.
I
don't
think
it's
that's.
A
C
C
A
All
right,
if
you
get
the
little
circle
for
han
kai
and
victor,
I
guess
bill
as
well
a
little
spinning
circle
by
their
names,
the
recycle
button
or
whatever
that
is,
it
should
re-request
yep
there
we
go,
then
they'll
all
get
notices
and
if
they
come
back
and
want
more
changes,
they
can
request,
and
otherwise
we
can
move
forward
all
right.
C
Well,
we'll
call
that
dealt
with
that
is
the
last
whole
request.
So
I
can
I
I
will
work
my
way
back
up
the
stack
of
what
we
were
talking
about
right,
so
that
is
the
end
of
what's
been
put
down
in
the
agenda.
Does
anyone
have
anything
else
they
would
like
to
raise
while
we're
all
basically
meeting.
B
A
And
you
can
move
that,
maybe
the
very
last
beyond
elections,
the
I
will
not
be
I'll
be
out
for
spring
break.
C
Okay,
I'm
not,
but
that
doesn't
mean
to
say
I
wouldn't
like
a
day
off,
so
I
will
take
the
judgment
of
the
majority.
Anyone
else
with
preferences.
C
Looks
to
me,
like
we
haven't,
got
that
many
americans
here
so
spring
break
may
not
be
a
concern
to
everybody,
but
I
think
if
we
march
the
14th
is
literally
next
week,
isn't
it
yeah?
Okay?
So
let's
take
that
to
the
channel
and
make
sure
we
actually
have
everybody's
consensus.
C
My
answer
here
is:
I
don't
care
either
way.
I'm
not
gonna
say:
if
there's
not
enough
people
coming,
then
I
would
obviously
cancel,
but
I'm
perfectly
capable
of
coming
along.
So.
A
C
Let's,
let's
go
with
well:
if
lucina
does
it
then
lucina
does
it
if
not
one
of
the
rest
of
us
needs
to
jump
in
but
but
yeah.
So
we
will
double
check
on
that.
It's
not
quite
the
same
as
president's
day,
but
you
never
know
all
right
and
again,
unless
anyone's
got
anything
more
to
raise,
then
that
would
seem
to
be
the
end
of
today's
work.
A
No
and
lucina
and
chat
said
she'll
take
care
of
it,
so
I
think
we're
good
thanks
dan
thanks.
Everyone
else.