►
From YouTube: CNCF CNF WG Meeting - 2022-03-21
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
Hello
folks,
we'll
get
started
in
just
a
minute
here:
meeting
notes
or
ends
zoom.
B
A
C
C
Nice
to
be
back
sorry
for
the
absence
now
that
daylight
savings
time
is
rolled
around,
I
don't
have
a
standing
conflict
like
I
did
before.
C
And
I
guess
it
was
cancelled
I
jumped
on,
but
nobody
else
was
there
and
then
I
saw
in
the
notes
that
it
was
pushed
a
week.
A
Well,
we
had
elections
close
to
this
time
last
year
and
we
need
to
look
at
elections
for
chairs.
A
And
we
got
some
rules
here
around
it,
but
anybody
can
submit
their
selves
if
you
think
someone
else
is
a
would
be
a
good
chair
for
this
group
then
talk
to
them
and
have
them
submit
for
themselves,
but
you
can
feel
free
to
recommend
people.
We
just
want
people
to
have
the
time
and
want
to
do
it.
If
they're
going
to
be
a
chair.
A
B
A
A
A
Cfps
are
open
for
open
source
summit
eu
and
I've.
I
go
ahead.
B
So
taylor,
I
just
wanted
to
ask
it
turned
out
that
I
will
be
in
valencia
for
for
kubecon
europe,
and
will
we
have
some
kind
of
an
event
okay,
which
is
like
for
this
working
group
or
someone
else
will
be
there
outside
of
me
physically.
A
I
I'm
not
sure
if
there'll
be
an
event
or
any
session,
we
have
had
them
in
the
past.
The
cloud
native
telco
day
is
kind
of
the
biggest
thing
related
to
telecom.
That's
for
cncf.
At
the
event.
A
A
Down
this
is
just
a
submerge,
just
a
pull
request
to
change.
A
D
Well,
it's
just
like
a
tradition
of
the
recent
numerity
discover
so
obviously
in
the
non-root
best
practices
that
we
have
just
adding
more
material
for
supporting
that
case.
B
I
looked
at
it,
I
saw
it
and
I
I
thought
it
was.
You
know
it's
it's
a
great
pointer.
I
think
we
had
like
not
just
the
cv,
but
we
had
like
right
like
three
others
within
like
a
month
which
had
the
same,
I
would
say
the
same
root
cause,
but
they
had
the
same
attack,
angle
and
and
all
of
them
would
have
been
prevented
if
the
container
was
not
running
in
root
mode.
B
Therefore,
the
new
these
are
all
things
which
are,
you
know
just
confirming
the
what
we
say
that
running
is
non-root.
Containers
is
the
best
practice
practice.
A
Sounds
good,
would
you
add
a
review
or
a
plus
one
on
that
sure
yeah
sure.
B
D
I
think,
in
order
to
see
him
in
that
list,
he
has
to
only
make
a
quick
comment.
A
Yeah
I
got
it,
the
problem,
is
you,
don't
have
access.
A
E
Can
you
give
a
thumbs
up
or
do
you
object,
yeah
all
right,
yeah,
I'm
sorry!
I
was
just
I'll
give
a
thumbs
up.
I
just
couldn't
get
myself
off
a
mute
there.
A
A
A
A
A
All
right
ben
we're
back
to
one
of
yours:
yeah
configuration
best
practice
for
kubernetes
system
components.
What
do
we
have
new
that
hasn't
been
addressed
yeah
so.
B
There
is
so
I
and
I
told
I
wrote
here
in
one
of
the
notes
that
I
know
that
I
need
to
move.
You
know
this
to
another
place:
okay,
another
format,
okay,
to
be
in
the
same
format
as
all
the
other
best
practices.
I
just
wanted
to
finish
all
the
you
know,
all
the
comments
and
close,
the
all
the
content
related
stuff,
okay
and
and
the
formal
things
I
I
want
to
leave
at
the
end.
Okay,
because
just
I
don't
want
to
you-
know,
break
the
comments
and
stuff.
B
So
so
I
think
that
yeah
I
haven't.
I
haven't
seen
the
latest
comment
on
on
this
question
of
the
apec
questions.
Okay,
I
really
wanted
you
know
just
to
highlight
here
in
this
part
the
the
differentiation
from
my
point
of
view
between
abec
and
rbac,
okay,
that
that
in
abec
you
need
to
you
know,
configure
things
through
files
and
and
in
our
back,
you
can
configure
it
through
the
api.
B
B
A
A
B
Yeah
again,
I
know
I
need
to
move
the
file
itself,
okay,
because
it
wasn't
in
the
right
place
and
right
format.
Okay,
I
actually
I
haven't
done
this
before,
but
I
think
that
if,
if
I'm
moving
the
file
and
then
I'm
going,
I'm
afraid
I'm
going
to
lose
all
these
inline
comments
is
that
this
is
the
reason
why
I
haven't
moved
it.
Yet
you
won't
lose.
A
The
inline
comment,
and
if
anyone
makes
a
suggest
change-
and
you
accept
them,
then
it'll
also
be
fine,
so
these
will
stay.
You
need
to
make
sure
that
you
work
on.
Do
your
changes
in
your
branch
here
yeah.
So
if,
if
you
go
in
this
one
and
you
move
the
file,
when
you
do
a
commit
after
the
move
and
push
it
up,
it
will
automatically
update
the
pull
request.
Yeah,
that's
right.
I
already
think
I'd
already
did
a
file
directory
change
shouldn't
affect
the
comments.
A
C
Just
go
in
move,
it
commit
your
changes
to
your
branch
and
it's
just
tracked
as
one
of
many
changes
right.
So
it's
not
gonna
move
like
relation.
If
you
like
completely
like
started
a
new
branch
and
just
copied
and
pasted
a
file
in
there,
but
you
just
need
to
like
actually
go
into
how
it's
committed
and
change
the
directory
like
that
and
then
it'll
all
be
tracked.
C
B
C
Yeah,
so
I
just
had
a
couple
questions.
I've
got
some
things.
It
seems
like
mostly
some
misunderstanding
of
certain
definitions,
so
I'm
gonna
go
in
and
create
those
I
guess,
like
the
main
thing
is,
is:
should
I
put
like
a
glossary
at
the
bottom
of
this
or
just
kind
of
weave
the
definitions
throughout
and
then
there
was
one
comment
by
pankaj.
If
we
go
down
to
that,
I
don't
know
if
people
want
me
to
remove
some
of
the
additional
context
or.
A
The
ones
that
have
had
some
extra
information
it
was
at
the
top.
A
C
I
might
pick
and
choose
some
of
it
then
like
because
the
use
case
it
has
a
substantially
bigger
assumption
of
like
what's
going
to
be
put
into
it
where,
like
we
said,
user
stories
were
kind
of
supposed
to
be
short
and
sweet,
so
people
can
get
stuff
in,
but.
A
Yeah,
whatever
is
causing
problems,
just
add
it
to
the
top,
and
of
course,
if
there's
anything
see
this
one
also
hasn't.
A
C
Yeah
there's
a
few
things
like.
I
was
kind
of
surprised
I
needed
to
add
definitions
for,
but
I'll
do
it.
C
I'll
just
put
a
little
glossy
at
the
top
and
then
see
if
there's
things
I
mean
air
gap
probably
should
be
added
to
the
bigger
glossaries
and
then
just
link
to
just
because
that's
a
common
thing,
but
I
feel
like
upstream
and
source.
Most
people
know
what
that
means.
So
I'll
just
add
something
for
context
into
the
specific
user
story.
D
Well,
jeff,
you
don't
have
to
worry.
I
mean
I'm
going
to
propose
that
definition
in
the
grocery,
so
yeah.
We
can
resolve
that.
C
Most
of
it
was
from
like
pankaj's
questions
so,
but
I
mean
anybody
should
be
able
to
come
and
read
these.
So
if
people
in
our
own
group
are
like
what
does
it
mean
you
say
upstream,
then
I
should
assume
other
people
will
have
those
questions
so,
but
I
don't
think,
like
you
know,
defining
upstream
in
one
of
the
bigger
glossaries,
probably
makes
a
lot
of
sense
just
what
it
means.
Specifically
in
this
use
case,
our
user
story.
I
mean.
C
A
Well,
I
guess
that's
it
the
other!
Well,
I
guess
we
can
go
through
this
one,
but
top
you're
at
half
an
hour.
So
we'll
see
what
you
have
next
week,
jeffree
and
sure
we'll
be
following
up
some
this
week
to
catch
up
on
things.
A
The
idea
is,
we
want
to
communicate
to
them
anything,
that's
an
exception
and
why
it's
an
exception
so
that
they
can
make
adjustments
on
their
side.
A
A
Okay,
victor,
you
have
a
small
edit.
Oh
that's
that
sounds
good
to
me.
D
And
also
taylor,
can
you
re-title
that
pr,
I
mean
at
least
remove
the
working
in
progress
label.
It
seems
like
it's
raised.
The
reviews,
though,.
A
A
If,
if
there
it
could
be
clarified,
then
I
think
I'd
rather
funcai
do
a
suggest
at
it,
and
this
has
been
said
a
few
times
yep
and
again
there
and
again
there.
What
do
we
have
here.
A
A
A
A
A
D
Well,
I
just
left
a
few
comments
directly
to
then
so
that's
regarding
because
they
changed
that
he's
meeting
is
required
to
have
another
additional
words
in
the
workplace.
So
don't
forget
to
do
them
in
your
vr.
D
In
in
this
vector,
no
just
just
put
those
comments
directly,
so
ben,
if
you
haven't
seen
them
in
the
chat,
so
I
I
mean
it's,
I
don't
know
if
I
have
to
put
them
as
well
in
the
the
pr
so.
D
Oh
well,
if
it
is
in
the
zoom
chat,
so
I
send
a
private
message
but
yeah
I
can
also
let
me
include
it
in
the
vr
to
just
keep
it
everything
open.
A
A
All
right,
y'all
is
there
anything
else.