►
From YouTube: CNCF CNF WG Meeting - 2022-02-14
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
Hi
and
good
evening
to
you
are,
are
you
actually
hold
on?
Where
are
you
located?
Is
your?
Are
you
pleased
yeah
yeah,
I'm
in
virginia,
oh
you're,
in
virginia
yeah?
Oh
well,
then,
good
morning
as
well
yeah
good
morning,
all
right.
C
A
A
B
A
Hello,
please
add
your
name
and
any
agenda
items
to
the
meeting
notes.
C
C
Oh,
is
it
me
yes,
I
can
do.
Let
me
just
try
and
fix
something
else.
I
was
trying
to
make
work.
Sorry,
my
laptop's
having
morning
problems.
C
Right
taylor,
are
you
leading
mri?
A
C
It,
I
guess
one,
it
was
you
all
right,
fine!
No!
It's
probably
my
turn.
You
picked
up
my
mine
last
week
anyway.
Okay
right
so
next
week
is
a
federal
holiday.
Should
we
cancel
this
group
next
monday.
In
my
experience,
it's
not
a
terribly
consistently
observed
federal
holiday,
but
I'm
certainly
not
around
next
monday.
So
my
vote
is
for
let's
skip
it
next
week.
Any
other
preferences
one
way
or
the
other.
B
C
A
C
Right
so
we
still
have
the
cloud
native
telco
eu
open
papers.
C
I
won't
go
through
all
the
events
this
week
because
there's
a
lot
of
them
and
they've
been
on
here
for
ages
at
this
point,
but
since
that
one's
got
a
an
open
request
for
papers
called
papers,
then
you
might
want
to
go
and
have
a
look
see
if
there's
anything
that
you
feel
you
want
to
talk
about
any
of
your
experiences
any
of
your
thoughts
or
ideas
and
put
a
presentation
in
there
and
don't
forget
as
well,
to
tell
us
of
the
exciting
presentations
you've
put
in
and
also
anything
else
that
you've
seen
on
on
record
that
other
people
are
putting
in
as
well.
C
For
any
of
these
events,
it's
all
worth
worth.
Knowing
what
what's
coming
up?
That's
worth
worth
actually
spending
the
time
to
go
in
here,
so
they
won't
go
through
the
upcoming
events,
but
the
there
is
an
important
pair
there,
which
is
that
the
time
zone,
changes
and
taylor
are
we
basically
stuck
with
the
ucc
time
so
we're
our
meeting
will
move
an
hour
in
that
places
which
change
their
time
zone.
Is
that
how
we're
playing
this.
A
That's
how
we've
been
doing
it
just
keep
it
at
1600
utc
and
that
stays
time
time
daylight
savings
changes.
Then
we
still
stay
at
16..
If
we
want
to
shift
that
in
the
future,
I
think
we
should
have
more
input.
C
C
Yes,
it
was
a
little
bit
of
carelessness
that
it's
not
that
air
earlier
as
well:
okay,
again
you're
all
capable
of
reading.
There
are
a
list
of
other
events.
Here
you
can
go
and
double
check.
As
you
can
see,
there
isn't
just
the
one
call
for
papers
open,
it's
just
the
first
one,
that's
coming
up.
C
There
are
a
few
others
worth
considering
to
submit
to,
but
none
of
them
are
exactly
imminent
at
this
point
in
time,
I'm
going
to
skip
the
old
skip
the
first
one
for
a
moment
because
we'll
get
there
shortly
and
it
will
eat
towards
the
end
of
the
meeting
lightly.
C
But
I
would
just
point
out
that
your
your
friendly
neighborhood
co-chairs-
that's
me,
taylor
and
jeff
have
a
one-year
term
and
we
were
elected
about
11
months
ago
at
this
point,
so
it
will
imminently
come
around
that
we
need
to
open
nominations
for
the
next
year's
co-chairs
to
do
the
work
of
organizing
you
all
and
hosting
these
meetings,
sending
out
the
occasional
sort
of
request
to
you
and
yes,
you're,
I'm
not
quite
sure
when
we
will
open
the
the
nominations,
but
you're
welcome
to
self-nominate,
and
I
encourage
you
to
do
so,
but
just
I
didn't
want
to
get
that
lost
it's.
C
I
think
it's
about
two
months
out
at
this
point
in
time,
maybe
a
little
less
and
I
wanted
to
make
sure
everybody
had
their
opportunity
to
to
suggest
themselves
for
a
co-chair
if
they
want
to
have
a
go
next
year.
Right,
not
quite
sure
what
this
one
means
who
wrote
this
yeah.
D
B
D
So
it
was
the
document
I
started
write
about.
You
know
different
security,
best
practices
and-
and
you
know
I
really
try
to
write
up.
You
know
the
first
few
points
here.
D
Okay,
just
to
get
a
sense
of
you
know
what
do
you
think
what
we
think
as
a
group
of
about
things
that
that
are
useful
and
can
be
added
as
back
best
practices,
recommendations
to
our
agenda
and
and
since
I
didn't
really
get
any
inputs
on
it
and
the
small
inputs
I
got
I
already
incorporated,
so
I
simply
continue
to
write
and
and
again
I
I
just
simply
get
to
a
point,
okay,
but
I
think
that
I've
in
a
very
high
level,
but
I've
covered
some
most
important
things.
D
I
think
that
that
that
that
are
important
for
for
the
for
the
api
server
configuration
for
a
security
perspective,
and
you
know-
and
I
would
just
you
know
us-
okay-
you
guys
here
that
that
how
do
you
see
this
okay?
What
should
we?
What
should
I
add?
D
Should
we
move
this
to
to
the
github
repo?
Should
the
should
I
correct
word
thing
or
really,
I
would
be
happy
to
get
into
here.
C
Well,
this
should
go
to
the
the
the
github
repo,
because
it
is
a
best
practice.
I
mean
easily
justified.
It
doesn't
need
a
use
case
to
go
with
it.
You're,
basically
saying
that
it
is
a
good
idea
for
kubernetes
to
be
under
control
and
not
hacked.
I
think
you'd
want
to
spell
that
out
in
relatively
simple
words
at
the
top
to
give
a
reason
for
it.
But
aside
from
that
yeah
fine,
there
are
perhaps
one
or
two
of
these
that
I
wonder
about
in
a
an
nfe
context.
C
D
Yeah,
so
so
I
think
the
client
authentication
part
is,
is
you
you
know?
D
Most
of
the
things
are
okay
from
a
security
perspective,
and
this
is
what
I
wrote:
okay,
that
I'd
be
trying
to
little
emphasis
on
all
these
alternative
options
that
where,
where
the
security
issues
can
lie,
okay-
and
there
is
no
clear
best
practice,
I
think
the
only
thing
which
was
being
from
my
point
of
view
was
big,
no,
no
static,
token
files-
which
I
I
think
in
general,
is
not
a
good
idea,
but
client
certificate,
authentication,
opel,
open
id
connect,
tokens
and
web
based
authentications,
but
also
spread,
can
be
fine
as
the
authentication
mechanism.
C
C
If
you
know
what
you're
looking
for,
then
you
can
say
why
these
things
are
good
or
bad,
whether
they
cover
all
of
the
needs
you've
made
notes,
for
instance,
like
friends
like
the
static
token
files
have
a
problem
with
rotation.
So
my
question
to
you
is:
do
we
need
rotation
because
we
don't
need
rotation
that
isn't
a
problem
for
us
in
our
use
case,
and
if
we
do,
then
it
kind
of
rules
it
out.
C
So
that's
the
question
right
you
rather
than
list
these
things
list.
What
your
perfect
solution
would
include
and
then
score
these
things.
According
to
that
list,.
C
But
yeah
I
mean
other
than
that
I
mean
there's.
I
think
nothing
too
contentious
here,
just
a
list
of
things
that
you
should
check
you've
remembered
to
do
and
that
would
seem
like
a
perfectly
reasonable
thing
for
a
best
practice.
I
don't
think
anyone
would
have
any
specific
arguments
with
any
of
the
things
you're
suggesting
people
do
again,
with
the
single
exception
that
this
section
at
the
bottom
is
a
choice
of
four
and
you
aren't
making
a
recommendation.
C
So
if
you
can't
make
a
recommendation,
you
could
detail
how
the
choice
is
made.
If
you
can
choose
one
and
say
this
is
best
or
maybe
two
and
say
they
have
different
strengths,
then
that
would
make
things
better.
If
you
just
list
all
four,
then
you're,
not
it's
not
best
practice,
because
you're
telling
them
what
they
could
do,
you're
telling
them
all
of
what
they
could
do.
D
D
Okay
to
choose,
you
know
open
id
or
choose
some
kind
of
weapon-based
authentication,
because
you
already
have
some
kind
of
authentication
system
in
place
and-
and
you
want
to
stick
with
it
and
therefore
I
I
feel
that
I
cannot
make
this
decision,
but
I
can't
tell
that
within
that
decision,
okay,
what
to
look
for
what
can
be
the
pro
the
problems
and
what
should
be
the
best
way
to
use
it.
If
someone
decides
to
use
it.
C
Yeah,
I
I
mean
from
that
perspective,
you
could
say
you
know
you're
going
to
need
an
authentication
mechanism,
it's
a
good
practice
to
have
one
yeah.
It's
good
practice
to
have
one
that
doesn't
require
restarting
the
api
server
every
time
the
credentials
change.
It's
good
practice
to
have
one
where
your,
where
credentials
can
be
revoked,
should
they
be
problematic
and
so
on
and
so
forth.
Those
are
good
practices,
even
if
you
can't
necessarily
make
the
choice
on
somebody
else's
behalf
right.
C
E
I
just
joined
like
two
minutes
ago,
because
I
was
on
another
call.
I
need
more
context
in
order
to.
A
C
So
the
conversation
here
so
far
is
that
ben
is
proposing
this
as
api
security
for
the
kubernetes
api.
These
are
the
things
that
you
should
do.
I
think,
speaking
personally,
that
about
90
of
this
document
is
perfectly
good
common
sense
things
that
nobody
would
argue
with
right.
It
have
audit
logs
disable
anonymous
requests.
This
is
all
sensible
stuff.
There
really
isn't
anything
to
quibble
about.
C
They
just
need
writing
down
and
as
such,
this
is
basically
a
best
practice
in
the
making
and
just
writing
up
in
the
best
practice
and
committing
it
would
be
most
of
the
work
that's
left
here.
The
only
thing
that
remained,
that
was
an
exception,
is
that
this
section
of
the
document
about
client
authentication.
C
It
makes
a
strong
argument
earlier
that
client
authentication
is
necessary,
but
here
it
doesn't
list
a
way
of
doing
the
right
way
of
doing
client
authentication,
which
is
fair,
because
I
don't
think
you
would
get
everybody
to
agree
on
that.
But
I
think
maybe
the
best
way
is
to
say
what
the
strengths
of
what
strengths
of
authentication
you
are
looking
for,
because,
rather
than
basically
listing
under
each
of
these
categories,
this
is
good,
because
this
is
bad
because
just
say
good
authentication
will
include
the
following.
You
know
checklist
items.
D
I
mean
sorry,
go
ahead,
yeah!
Just
sorry.
I
just
don't
want
to
tell
you
that
I
think
I
I
get
what
it
means
by
that,
like
totally.
If
we.
E
I
just
wanted
to
ask
if
it
would
maybe
make
sense
to
call
these
common
practices
if
we
say
that
these
are
items
that
are
that
we
are
listing
here
that
that
are
commonly
used
and
therefore
they
are
considered
good
practices,
as
opposed
to
saying
these
are
best
practices
to
outline
the
scope
of
what
the
information
is
here
and
what
we're
shooting
for.
Unless
we
want
to
go
into
further
evaluation
and
say
that
this
is
good.
This
is
bad.
C
Yes,
I
mean
it's
a
wording
issue,
but
yes,
I
can
see
that
I,
I
think
it's
fair
to
say
that
we're
going
to
run
into
this
problem,
in
other
circumstances,
where
what
we
would
like
to
be
listing
is,
I
have
done
a
lot
of
nfv.
I
have
run
a
lot
of
these
things
and
my
my
recommendation
of
everything.
I've
tried
that
this
is
the
best
thing
to
do
is
x.
C
What
we're
saying
here
is,
I
have
studied
the
security
implications
of
choices
here,
and
this
is
my
recommendation
of
what
is
the
best
based
on
industry
practice
in
related
areas,
which
isn't
quite
that
thing
so
yeah
if
you've
got
any
suggestions
on
that,
stick
them
in
the
meeting
notes.
But
I
I
appreciate
your
point.
E
No
make
sense,
I
just
I
just
also
know
a
few
people
who
have
reservations
with
saying
best
practices,
so
I
just
partially
driven
by
that
experience.
I
I
wanted
to
throw
that
in
as
well
just
in
case.
E
Well
then,
I
could
also
say
maybe
recommendations.
C
Yeah,
no
that's
fair
and
then
don't
don't
sort
of
worry
too
much
about
that
write.
Your
use,
user
story,
ildico
will
review
it
and
indico
will
figure
out
whether
there's
a
good
way
of
changing
the
terminology.
If
it
matters
that
much
but
yeah,
as
I
say,
I
I
feel,
like
sorry
use
your
best
practice.
Actually,
your
writing,
but
I
feel
like
you're
most
of
the
way
there
with
this.
D
Yeah,
okay
and
after
you
know,
I
I'm
doing
the
corrections.
Okay,
obviously
I
will
have
it's
for
reviewing
okay.
I
will
open
a
pull
request
and
we'll
do
the
same
for
the
other
for
for
the
other
control,
plane,
components
or
cubelets
and
stuff
the
same
ideas
yep.
That.
C
Sounds
great
you're
also
welcome
to
rest
refer
to
external
as
long
as
they're
well
recorded
and
the
link
isn't
likely
to
break
refer
to
external
instances
of
best
practices
nobody's
pretending.
We
have
to
write
a
copy
of
this
for
ourselves,
something
outside
sure.
D
C
Okay,
I
rearranged,
because
that
was
a
specific,
and
now
we
can
go
on
to
the
general,
which
is
the
pull
requests
which
I
always
hate
so
right,
starting
from
the
oldest.
C
Taylor,
you
went
through
these
extensively
last
week.
Do
you
have
anything
to
add
to
what's
on
here
in
terms
of
comments
or
expected
activities?
No,
I
think
that
one
stalled.
A
We're
waiting
primarily
on
on
jeffrey
to
get
through
it,
which
he
had
said
in
the
last
couple
of
weeks.
He
was
going
to
start
working
through
this.
C
Yeah
I
mean
I
can
see,
there's
a
bunch
of
open,
discussed
but
unanswered
comments.
So
it
looks
to
me
like
we're
looking
for
for
a
change
that
takes
them
into
account.
Okay,
you
and
I
will
take
it
on
our
own
task
list
to
go
and
corner
jeff
and
make
him
do
some
work
then
sounds.
C
Yeah,
I
I
know
he's
found
it
rather
difficult
to
make
meetings
in
recent
times
and
hopefully
the
time
shift
will
will
basically
make
this
slot
free
for
him,
where
otherwise
he's
a
bit
busy.
But
yes,
and
now
I
have
the
guilty
conscience,
because
the
next
one
is
mine-
and
I
see
it
has
29
comments
and
I
can
tell
you,
I
have
not
read
29
comments.
C
Oh
yes,
and
that's
right,
there's
a
couple
of
odd
grammatical
bits
as
well,
but
yeah,
so
I'm
still
reasonably
comfortable
with
this.
I
do
think
just
skimming
this
that
he's
talking
about
format
rather
than
content,
which
is
sort
of
helpful,
because
it
means
that
we're
in
roughly
the
right
direction.
I
would
welcome
anybody
else's
comments.
C
C
Which
is
the
stateful
user
stories
and
use
cases?
As
I
recall
and
again
I
have
a
guilty
conscience
because
I
was
stuck
not
being
able
to
press
the
magic
approve
button
on
this.
But,
as
I
recall
you
taylor,
you
were
looking
for
five
approvals
here.
A
Yeah
we
had
a
few
people
saying
that
they
would
approve
offline.
Yes,
including
me,
can
you
does
your
aunt?
Does
it
work
right
now
for
putting
a
thumbs
up
on
it.
C
Anyone
else
who
wishes
to
express
their
approval
now
would
be
a
good
moment,
or
at
least
after
this
meeting,
if
you
want
five
minutes
to
actually
work
out
what
you're
looking
at
again,
what
we're
looking
for
here
is
good
enough,
not
perfect,
so
you
know
it's
once
it's
in
there.
C
It
can
be
fixed
and
changed
and
reworded,
but
it's
never
going
to
get
in
there
until
until
we
get
as
we
currently
want,
five
reviewers
and
taylor,
you
were
talking
about
reducing
the
number
of
reviewers
down
to
three,
and
I
think
we
have
somewhat
less
of
an
active
chord
quorum
at
the
moment.
So
maybe
that
would
be
a
good
idea
if
you
want
to
propose
that
change
to
the
governance
file.
A
C
Yeah,
because
we've
just
set
the
bar
a
bit
too
high
for
ourselves,
you
finding
five
active
people
to
give
these
documents
for
once
over
every
week
is
a
little
bit
too
difficult.
So
yeah
we
just
don't
come
down
a
bit,
but
other
than
that
I
mean
you're
after
one
review.
I
I
I
noticed
watson
hasn't
said
yes,
so
you
can
go
and
conor
watson
if
he's
anywhere
handy
to
be
found,
but
yeah.
A
A
Can
we
get
anyone
else?
Have
you
all
had
anyone
else
had
time
to
write
through
this.
D
C
I
I
am
happy
to
take
an
order,
a
verbal
approval
as
an
approval
for
what
it's
worth.
It's
it's
on
record,
but
that
said,
chase
taylor.
You've
got
you've,
got
two
failing
unit
tests,
so
I
would
rather
you
fix
those
before
we
actually
committed
it,
or
else
we
break
the
trunk
and
then
break
them
past
the
branch
all
right,
I
think
I'll,
and
if
you
fix
them
and
there's
no
material
differences,
then
I
promised
I
will
press
the
approve
button
for
you.
A
C
Sorry
you
oliver
sorry,
I
was
forgetting
this
wasn't
yours
for
whatever
reason
but
yeah
I
I
would
imagine
that
there
are
two-minute
jobs
so
actually.
A
C
C
C
Right,
okay,
I
have
now
officially
run
out
of
pull
requests,
so
any
other
business.
C
C
All
right
well,
thank
you
for
your
time.
It
is
8
35
ish,
so
we've
managed
that
in
half
an
hour
all
good-
and
I
will
see
you
all
again
next
week-.