►
From YouTube: CN Network Function (CNF) WG: K8s Best Practices for Telco Apps - Taylor Carpenter & Bill Mulligan
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Cloud Native Network Function (CNF) WG: K8s Best Practices for Telco Apps - Taylor Carpenter, Vulk Coop & Bill Mulligan, Cloud Native Computing Foundation
The Cloud Native Network Function (CNF) Working Group is focused on identifying cloud native best practices for networking applications in order to help CNF Developers and telco operators best utilize the capabilities of Kubernetes. In the session, attendees will get an overview of the working group, updates since its kick-off at KubeCon NA 2020, what’s next, and how to get involved. Ready to get started now? Join the CNF WG mailing list at https://lists.cncf.io/g/cnf-wg or talk to us in the #cnf-wg channel of the CNCF Slack. Recordings of previous CNF WG meetings are available at https://youtube.com/playlist?list=PLj6h78yzYM2PyMYvw5wiH01hthFb0qrOn.
A
A
A
A
So
it's
created
the
telcom
user
group,
where
you
can
help
provide
feedback
from
your
experience
and
area
like
a
service
provider
and
developers,
creators
all
coming
together
and
the
cnf
working
group.
What
we're
going
to
mainly
focus
on
today
and
looking
to
create
and
find
best
practices
for
networking
applications.
The
cnf
test
suite
and
cnf
testbed
two
tools
to
help
with
these
best
practices.
A
A
A
There's
different
tests
focused
on
best
practices,
there's
minimal
instructions
for
getting
started
as
an
end
user
or
developer,
as
well
as
more
extensive
instructions
for
both
prereqs
and
other
things
are
outlined.
It
runs
on
your
own
kubernetes
cluster.
You
can
use
kind
or
bare
metal
type
environments
and
there's
configuration
and
other
examples
to
help
you
get
started
if
you
would
like
to
contribute
check
out
the
contributing
guide
and
you
can
download
the
this
software
from
the
github
repository.
A
A
So
if
you're
familiar
with
those,
then
you
should
be
able
to
hop
in
and
start
using
those
and
contribute
new
use
cases
and
examples
out
of
the
box.
It
works
on
equinix,
bare
metal
and
you
can
download
it
and
use
it
right
here
on
the
cncf,
cnf
testbed
repo,
all
right,
if
you'd
like
to
get
involved
in
either
of
those
there's
two
channels
on
the
public
slack
and
there's
also
a
contributor
meeting
on
thursdays
at
14
15
utc,
which
you
can
join
to
talk
about
either
of
those
initiatives.
A
So
those
build
into
what
we're
here
today
to
talk
more
about
the
cnf
working
group.
So
the
cnf
working
group
has
the
goal
of
making
it
easier
to
produce
and
consume
networking
applications
through
the
adoption
and
development
of
cloud
native
best
practices
for
these
networking
applications.
Specifically,
it's
a
collaborative
effort
with
service
providers,
cnf
developers
and
kubernetes
community
working
on
definitions
and
use
cases
best
practices
in
the
process
around
finding
these.
A
We
have
the
mission
of
making
the
to
increase
interoperability
and
standardizations
for
these
cloud
native
and
kubernetes
native
workloads,
with
the
aspirational
goals
of
making
things
more
portable,
extensible,
automatable
and
flexible,
whether
that's
deployments
development
management.
We
want
to
meet
users
where
they
are
so.
We
know
there's
a
lot
of
brownfield
deployments
already
there
and
and
technology
that
we
would
like
to
be
able
to
try
to
see
how
you
can
do
integrations
while
advancing
the
state
of
the
art
and
methodologies
new
processes,
as
well
as
the
technology
itself.
A
We
want
to
determine
which
of
these
best
practices
are
going
to
help
the
applications,
the
cns
to
most
effectively
utilize
existing
services
and
capabilities
in
kubernetes.
When
you
look
at
it
as
a
framework
at
a
building
block
and
then
provide
feedback
to
improve
projects
and
other
specifications
working
with
groups
to
improve
their
use
cases
and
the
applications
themselves,
we
have
over
27
organizations
and
individuals.
A
But
specifically
here
we're
talking
about
the
telecom
user
group
and
how
it
comes
together
and
provides
feedback
from
the
different
users
and
then
taking
those
and
building
into
recommended
best
practices
of
different
types,
whether
that's
design
and
development,
type
of
things,
a
different
type
of
testing
that
we
can
do
potentially
conformance
wise
operations,
life
cycle
management
practices
that
are
going
to
help.
These
can
all
come
to
creators
as
well
as
end
users
that
are
actually
using
the
cnfs
or
those
networking
applications
and
used
in
different
places
like,
of
course,
the
test.
A
All
right.
Let's
look
at
how
you
can
get
involved
and
contribute
many
different
ways.
Documentation
is
a
great
place
to
get
started.
A
specific
area-
and
there
would
be
providing
definitions,
actors,
roles,
expanding
on
acronyms,
within
the
glossary,
helping
to
conduct
gap,
analysis
in
different
areas
and
suggesting
new
networking
applications
or
cns
helping
to
define
or
contribute
to
existing
use
cases
and
user
stories,
and
then,
of
course,
getting
to
our
end
goal
of
contributing
more
cloud
native
best
practices.
Let's
take
a
look
more
at
those
best
practices.
A
So,
if
you'd
like
to
propose
a
cnf,
we
want
to
make
sure
that
others
are
would
like
to
help.
So
we
want
to
socialize
the
idea
in
different
places.
You
could
put
this
in
a
new
github
discussion
or
send
your
idea
to
the
mailing
list,
come
and
talk
at
one
of
the
upcoming
meetings,
and
then
you
want
to
talk
about
different
aspects
of
the
best
practice
whenever
we
have
a
full
proposal,
we're
going
to
actually
go
through
a
checklist.
So
why
do
we
need
it?
A
Well,
we
want
to
tie
it
to
a
use
case,
so
we
have
context
which
we'll
talk
about
more
in
a
little
bit.
What
makes
it
best?
What
are
the
circumstances
around
it?
Is
it
even
implementable?
This
could
be
limitations
in
the
platform
or
technology
and
how
you
may
work
around
those.
Do
you
have
a
test
plan?
Can
you
test
it
so
start
with
a
short
description.
A
A
What
are
the
goals
and
non-goals
so
limiting
the
scope
and
the
type
of
workloads
so
that
we
have
a
context
of
when
it
may
work
and
when
it
may
not
least,
privileges
may
be
great
most
of
the
time
but
doesn't
fit
some
specific
occupations
at
least
one
documented
use
case.
So
where
would
we
use
these
privileges,
who's
involved?
We
need
some
context.
That's
why
we
document
this
and
then
the
test
plan
for
checking
metrics
and
what
are
the
results.
A
A
They're
talking
they're,
showing
us
how
a
best
practice
will
help
get
work
done,
how
the
application
is
going
to
be
utilized
and
what
we
expect.
As
far
as
the
end
results,
one
example
would
be
a
transparent
firewall.
This
is
more
of
a
hello
world
type
of
networking
application
or
cnf
representing
the
bump
in
the
wire
pattern
for
how
to
run
an
application.
That's
just
passing
traffic.
As
far
as
most
of
the
time,
this
could
be
rewritten
showing
a
story
for
different
things.
A
A
Such
as
the
different
types
of
traffic
that
you
may
need
to
handle,
normally
you
would
think
of
a
transparent
firewall
being
on
a
second
interface
for
taking
in
traffic
about
management
or
metrics
for
what
it's
found.
It
doesn't
have
to
go
this
way,
but
this
type
of
idea
shows
us
where
we
may
need
to
work
on
solutions
where
you
need
multiple
interfaces,
one
of
them
out
there
is
multis,
and
we
dan
m
would
be
another
one
so
c
and
I's
that
give
us
multiple
interfaces.
A
A
A
A
We
want
to
try
to
have
our
technical
terms
and
acronyms
fully
defined
so
provide
a
glossary
and
if
there's
other
use
cases
or
best
practices
that
have
a
term
that
matches,
then
let's
try
to
use
those
and
have
consistency,
add
any
other
information
about
involved
processes,
the
actors
or
who's
who's,
the
target
audience
like
operations,
team
and
maybe
life
cycle
management.
How
they're
managing
that
and
then
any
type
of
entities
involved.
The
cloud
native
platform
is
this:
kubernetes?
Is
this
a
specific
provider,
the
data
center
network?
A
But
on
the
use
case,
we
can
go
a
little
bit
higher
level
and
look
at
the
whole
situation
and
say:
what
are
we
our
expectations
at
a
high
level
before
we
then
dive
down
in
and
talk
about
a
more
technical,
focused
and
expected
behavior
out
of
the
different
components
and
then
talk
about
any
challenges
and
limitations
that
you
may
see
and
how
you
could
overcome
them,
whether
that's
following
existing
standards
or
potentially
new
ideas?
If
there's
no
standards
around
the
problem
as
of
yet
all
right,
so
you
want
to
get
involved.