►
From YouTube: CNCF CNF WG Meeting - 2022-10-10
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
Foreign
greetings,
we'll
give
it
until
five
after
to
see
who
shows
up.
A
A
A
Rich,
are
you
gonna
be
making
it
to
either
of
those
the
Cloud
native
taco
day,
co-located
event
or.
B
So
I'm
not
sure
I'm
going
to
be
able
to
make
it
there
in
person.
You
know
I
know
Phil
platy
from
our
group
is
going
and
speaking
but
I
don't
know
if
I'm
going
to
be
there
in
person.
A
All
right!
Well,
if
you
are
please
reach
out,
of
course,
if
you're,
if
you
see
it
we'll
be
at
Cloud
native
Telco
day
for
the
whole
half
day,
event
reach
out,
if
you're
going
to
make
it
and
let
Bill
know
so,
I'd
like
to
meet
up
with
y'all.
B
B
I
need
to
check
and
I
I
might
come
up
for
that,
but
I
don't
know
if
we're
gonna
have,
who
else
is
going
to
be
there
at
one
Summit.
A
Okay,
we're
planning
on
attending
one
Summit
and
the
Elephant
developer.
Forum
we're
gonna
have
a
Workshop
during
the
lfn
developer
testing
forum
for
using
the
test
suite
and
focused
on
certification,
trying
to
make
it
an
interactive
session
where
we
can
try
to
help
work
through
any
issues
and
maybe
make
improvements
right
there
and
cubecon
EU.
A
We're
looking
for
sponsors
for
the
Cloud
native
Telco
day
in
Amsterdam,
we
had
a
lot
of
feedback
that
would
like
to
have
a
live
stream,
so
we
need
to
get
some
sponsors
to
be
able
to
do
that.
If
there's
interest.
A
A
Do
not
run
containers
of
privilege
flag,
that's
one
that
I'm
working
on
and
we
have
a
lot
of
content.
So
if
there's
anybody,
that's
interested
in
the
security
best
practices,
this
is
probably
one
of
the
areas
where
you
can
look.
I
mean
there's
a
lot
of
other
content
out
there,
kubernetes
security.
At
this
point,
it's
picked
up
a
lot,
but
we've
done
a
lot
of
research
around
the
least
privileged
ones.
B
A
So
there's
a
lot
of
content
here
going
over.
A
Least
privileged
related
best
practices
and
deviating
for
CNF
development,
and
it
links
back
to
content
that
we
have
been
also
Upstream
into
other
areas,
but
it
covers
a
lot
of
stuff
down
to
low-level
things
and
the
packet
filtering
and
the
higher
level
this
particular
issue
is
I
would
call
it
a
higher
level,
but
a
pretty
straightforward
containers
running
with
the
privileged
flag
is
what
this
one's
about
and
we've
had
it
open
for
a
while.
So
I
want
to
try
to
get
this
through.
A
There's
tests
already
on
it,
I
think
we
have
duplicate
tests
even
across
different
Upstream
tools.
A
We're
I
think
we're
just
running
one
at
this
point,
but
I
think
that
one
is
a
pretty
well
covered.
Do
this
as
a
default.
B
And
Taylor
I
I
remember
that
one
of
the
no
roadblocks
but
one
of
the
points
that
especially
with
privilege,
was
generated
with
the
attaching
with
special
devices
like
sriob
or
things
like
that.
Or
are
you
covering
that
part
in
the
document?
I
haven't
read
it
but
I,
don't
know
if
you
have
mentioned
something
like
that
or.
A
Well,
this
document
is
covering
a
lot
of
different
things,
I
think
for
the
the
actual
best
practice
Reddit
for
this
one
which,
and
this
one
was
assigned
immediately
some
Google
doc
I
want
to
try
to
get
it
out.
We
we
should
mention
that
I
I
think
that's
a
general
thing
as
far
as
like
the
SRV
this
you
know
we
have
some
content
around
here
for
that
the.
A
B
No
no
at
least
like
I
I,
haven't
read
that
so
probably
I
need
to
take
a
look,
and
probably
what
you
have
is
is
enough
for
clarifying
those
those
or
how
developers
can
use
it
as
an
exception,
maybe
or
or
another
workarounds.
If
they
need
to
interfacing
with
these
particular
requirements,
how
can
they
use
it
or
I?
Don't
know
like,
but
importantly,
I
need
to
I
read
it
I
need
to
read
it.
A
Yeah
I
I
mean
I'd,
be
happy
to
chat
with
you
about
it.
Work
on
this
I
know
you're
working
on
the
the
networking
best
practice
with
multiple
interfaces.
Maybe
we
could
have
some
working
sessions
to
go
through
breath
of
this,
but
the
I've
we've
started
covering
some
of
this
as
far
as
exceptions
in
different
ways.
A
The
document
that
Ann
put
forward
for
listing
any
exceptions
to
following
best
practices
and
the
guidelines
commit
you
know
so
that
you're
communicating
from
a
someone
creating
CNS
and
where
they
don't
follow,
exceptions
and
it
could
be
op,
seems
and
aggressions
anytime
you're
not
following
and
communicating
that,
so
that
the
the
people
that
are
using
those
and
managing
them
won't
understand
where
the
exceptions
are
so
that's
one
side
on
the
testing
side,
we've
been
thinking
about
it
from
how
to
validate
best
practices,
and
we
have
the
concept
of
exceptionless.
A
Specifically
around
this,
so
if
you're
running
privileged
containers
and
other
things-
and
you
know
that
you
need
them
so
you
know
one
example
is
there's
privileged
containers,
privileged
pods.
That
may
be
running
already
as
far
as
kubernetes
core
pods
or
you
may
have
some
other
one
that
you're
running
that
everyone
knows
and
it's
okay,
so
that
I
think
is
something
that's
going
to
keep
coming
up.
A
A
Keep
I'm
just
saying
that
so
that
we
keep
putting
it
forward
and
don't
say
because
we
have
an
edge
case
or
because
sometimes
there's
reasons
to
go
around
doesn't
invalidate
having
the
best
practice
which
I
I
know
you're,
not
saying
Victor.
But
if
you
have
some
time,
maybe
we
can
go
over
that
together.
Yep.
A
B
A
Right
so
Daniel
Bernier
from
Bell
Canada,
created
this
issue
several
months
back
to
talk
about
the
different
aspects.
A
So
this
is
multiple
interface,
but
you
could
also
I
mean
I,
think
it's
important
to
think
multiple
interface
or
multiple
connection
network
connections
that
are
segmented,
so
there's
different
ways
of
of
solving
the
underlying
problem
and
multiple
interfaces
would
be
one.
So
if
you're
going
down
the
path
of
multiple
interfaces.
So
how
are
you
going
to
do
this
in
a
cloud
native
way
and
what
are
the
different
aspects
here
and.
A
Victor
broke
out
one
part
of
this
multiple
interfaces.
This
is
talking
about
being
more
declarative
as
far
as
how
your
implementing
this
so
using
annotation.
So
he
has
a
document
here
which
you
can
check
out.
It's
linked
into
the
issue.
To
start
the
conversations
about
using
annotations
to
communicate
the
networks
need
the
devices
the
need
for
different
devices
in
a
bunch
of
different
aspects.
A
Yeah
I
think
this
is
maybe
the
the
core
thing
to
keep
in
mind
with
this
particular
part
of
that,
so
they
the
issue
itself.
You
know
if
you're
looking
at
this
and
again,
this
was
something
that
CSP
they're
bringing
forward
to
talk
about,
and
this
aspect
is
about
trying
to
be
neutral
toward
the
cni
specific
parts
to
make
sure
that
you're
more
portable.
A
So
if
you
may
be
on
a
if
you're
wanting
to
be
able
to
work
with
any
of
the
different
cnis
and
especially
move
between
Cloud
providers,
I
think
is
probably
going
to
be
the
bigger
thing
which
is
what's
being
asked
or
I
should
at
least
say
the
a
kubernetes
distribution
where
they
may
have
multiple
cnis,
depending
on
where
they're
running
I.
Think
one
of
the
things
similar
to
lease
privilege
is
trying
to
make
sure
that
a
application
can
degrade
gracefully.
A
And
this
would
go
along
with
that
Victor.
So
if,
if
you
have
a,
if
you
can
support
specific
cnis
in
your
application
great,
but
if
they
don't
have
the
cni
that
you
were
expecting
then
being
able
to
communicate
like
with
annotations
here's
what
I'd
like
and
then,
ideally
the
platform
can
say:
okay,
well,
here's
what
we
can
provide,
and
so
you
can
degrade
from
best
possible
case
where
you
have
very
specific
things
for
a
the
cni
to
a
less
specific.
A
All
right,
that's
I,
think
some
of
these
others
are
more
documentation.
Specific
I,
don't
think
they're
spending
any
updates
on
this.
C
Sort
of
been
like
this
is
something
that's
been
rumbling
around
internally
for
a
while,
so
I
think
everyone
kind
of
agrees
on
the
the
target
state
for
the
software
life
cycle,
Management
in
terms
of
making
it
more
Cloud,
native
and
rolling
updates,
and
so
on
and
I
think
the
CNF
test
suite
deals
with
that
as
well.
C
I,
just
I
do
I,
don't
know
whether
this
is
the
right,
Forum
or
not,
and
it's
more
of
an
open
question
of
whether
it's
something
we
should
discuss
here
or
take
to
us
somewhere
else
of
where
we
have,
in
inverted
commas,
Cloud
native
platform,
vendors
supporting,
let's
say
the
last
or
the
latest
three
versions
of
kubernetes,
for
which
you
know
gives
us
a
year
of
support.
C
C
And
you
know
so
on
so
I
think,
there's
part
part
of
the
problem
we
have,
anyway
is
about
internal
kind
of
acceptance,
testing
and
onboarding
process,
but
part
of
the
problem
is
you
know
if
it's
taking
I
don't
know
six
months
to
upgrade
a
platform,
then
basically
we're
going
to
be
continuously
upgrading
the
platform
because
of
the
the
Cadence
of
when
things
are
supported
and.
A
C
Just
wonder
whether
there
needs
to
be
something
a
bit
more
explicit,
written
down
as
a
best
practice,
as
well
as
the
things
that
are
tested.
Like
you
know,
can
your
CNF
do
your
rolling
update
in
kubernetes
something
writing
down
the
the
kind
of
rationale
the
you
know
how
we
should
approach
it
so
that
you
know
when
we're
getting
a
new
version
of
a
CNF
or
a
new
version
of
a
bunch
of
CNS,
maybe
from
different
vendors.
C
The
upgrading
them
in
you
know,
in
a
coordinated
way,
isn't
a
huge
operational
headache.
It's
a
series
of
changes
in
git
that
are
tested
and
then
deployed
to
a
production,
Network,
so
yeah
I,
don't
know
whether
this
is
the
right,
Forum
or
not,
but
I
I
thought
I'd,
raise
it
and
see
what
people
thought
there.
C
A
I
would
think
so
if
it
gets
down
to
implementing
the
platform
in
a
like
suggestions
or
whatever
I,
don't
while
we're
not
focusing
on
on
that
specifically
I,
don't
think
we
should
stop
from
writing
up
information.
That's
you
know
related
to
what
we're
currently
doing
and.
C
C
Not
just
you
know
it's,
you
know
it's
as
an
example.
I
won't
know
many
vendors,
but
you
know
we've
got
some
applications
where,
if
you
want
to
upgrade
them,
it's
a
redeployment
activity
instead
of
a
kind
of
rolling
update
approach
and
I
know
I
know:
we've
got
a
test
in
the
CNF
test.
Suite
that
tests
can
you
do
a
rolling
update,
but
I
don't
think
we've
got
anything
but
I'm,
not
saying
anything.
That's
been
written
down
as
a
best
practice
yet
to
explain.
A
So
the
I
mean
the
the
concept
I
think
you're,
referring
to
like
the
concept
of
a
kubernetes
ruling
update
or
the
or
the
very
generic
term
rolling
up
day.
A
A
I
think
one
of
the
underlying
pieces
that
people
aren't
that
are
not
as
far
along
is.
A
It
doesn't
mean
that
a
maybe
a
in
a
consumer
of
outside
of
the
CSP
Services
may
not
be
able
to
get
their
service.
That's
not
the
point!
It's
that
each
one
of
them
comes
to
some
type
of
variety
State
and
says:
hey
I'm,
I'm,
waiting
for
something
to
connect,
and
then
I
can
move
to
the
next
state
and
each
one
of
them
are
autonomous
and
that's
their.
The
design
is
more
procedural
I.
Even
if
you
you
know
your
language
is
object,
oriented
or
you
talk
about
modularity.
A
When
you
look
at
how
it's
run,
it's
a
procedural
set
of
services,
nothing
is
going
to
move
forward
and
I
think
that's
a
lot
of
what's
happening.
So
when
you
look
at
the
rolling
updates
in
kubernetes,
you
actually
will
have
new
Services
a
a
pod
come
up.
That's
a
new
version
and
it's
going
to
take
over
the
services,
will
now
point
and
I'm
talking
kubernetes
services.
A
So
connections
will
be
redirected
to
the
new
pod
running
the
new
version
and
when
you're
talking
about
rollback
and
all
the
versioning,
it
has
to
do
with
redirecting
your
connections
between
different
pods
running
different
versions
and
that
capability.
So
a
lot
of
it
has
to
do
with
architecture
and
design
and
I
I.
Think
that's
going
to
be
an
important
part.
If
we're
going
to
bring
people
forward
to
support
those
sort
of
things.
It's
going
to
be
understanding.
You
know
the
importance
of
some
of
the
architecture,
changes
that
are
needed.
A
C
A
A
A
A
There
for
the
some
of
those
tests
that
you
were
talking
about
that
are
related
to
the
life
cycle,
management
and
releases
and
stuff.
There
should
be
documentation
in
the
test
suite
for
those
that
could
go
along
with
whatever
you
write
up.
I
think
one
of
the
areas
would
be,
let's
see.
A
And
then
there's
in
the
test,
Suite,
specifically
it's
broken
out
across
different
documents,
but
I
think
some
of
this
will
be
related
to
what
Shane
and
we
could
pull
some
of
that
into
a
document
and
foreign
I
feel
like
there
may
be
something
linked
out
of
the
discussions
like
a
Google
talk
or
something.
A
A
I
would
like
to
come
back
to
yours.
Set
of
questions.
Also,
that's
driving
from
the
opsides
I
still
think
that
one's
a
good
set
of
questions
that
could
help
Drive
some
of
this.
So
at
least
link
to
that
you
know
what
I'm
talking
about
the
spreadsheet
shared
about
spreadsheet,
yeah,
yeah
I
think
that's
related.