►
From YouTube: CNCF CNF WG Meeting - 2023-08-28
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
A
All
right,
I,
don't
know,
is
today
a
special
holiday.
C
It
is
a
bank
holiday
in
the
at
least
what
UK
I
know.
C
I
think
it
was
being
called
I'm
trying
to
figure
well
yeah.
Give
me
a
second
here:
I
was
just
trying
to
look.
C
C
A
C
C
I
do
know
that
I
have
some
colleagues
out
today
in
the
UK,
so
I
agree
probably
should
just
cancel
that
one
and
then
in
advance
I
did
intend
to
last
week.
Victor
was
on
vacation
and
I
did
want
to
set
something
up
for
us
to
continue
on
the
single
concern.
Draft
I
didn't
get
anything
scheduled
there,
so
I
will
reach
out
to
him.
D
C
A
I'm
up
for
this
afternoon,
after
after
3
P.M
Central,
4,
P.M
Eastern
same
thing:
Tuesday
3,
P.M,
Central,
okay.
C
I'll
ping,
upping
Victor.
A
All
right,
let's
see,
do
we
have
any
do
we
have
a
PR?
What
is
this,
what
is
something
I
updated?
Oh,
this
is.
A
C
Yeah
I
can
get
in
there
as
well
didn't.
A
All
right,
moving
on
I,
don't
think
there's
any
new
issues.
I
think
right
now,
we're
need
to
close
out
some
of
the
existing
nothing
new
yeah.
C
Week
I
have
not
looked
I
had
a
little
busy
week
last
week.
B
A
Muhammad
I
don't
know
if
y'all
saw
but
I
dropped
a
pull
request
and
please
review
this
PR.
It's
very
small
about
the
definitions
on
goal
and
motivation
going
into
the
proposal.
A
A
Oh,
maybe
making
this
little
seen
us
scene
of
consumers
challenged
with
complex
and
Telecom
cnfs.
Okay,.
A
A
So
turning
this
into
a
challenge,
seeing
us
challenges
complex
so.
C
A
B
Sorry
I
had
to
look
away
for
a
second
I
didn't
know
what
section
you're
under.
A
A
And
then
this
is
a
motivation.
This
is
the
goal,
so
the
motivation
is
that
we
have
reduced
efficiency
of
resources
and
increased
scaling
time
since
you're
doing
everything
at
once,
rather
than
specific,
smaller
components,
your
response,
time
increase,
scaling
time,
increased
scaling,
I
want
to
say
and
response
time.
D
You
didn't
shouldn't
be
the
goal
to
scale
to
reduce
the
response
time
in
this
case.
D
A
That's
what
this
part
is:
oh
okay,
I
got
you
when
loading
so
scaling
specific
Pro.
So
here's
this
is
the
motivation
I'm
going
to
put
it
like
this,
so
it
makes
more
sense.
So
the
motivation
is
this
line.
This
is
the
bad
thing
that
we
don't
like.
So
we're
calling
out
the
problems
and
pain
points,
challenges
that
people
are
facing
and
then
what
are
we
trying
to
do
to
solve
it?
So
here's
the
goal.
D
C
D
A
Well,
the
solution
that
we're
giving
is
all
the
same.
It's
one
process,
type
per
container
and
the
goal
for
that
solution
is
what
we're
writing
here
so
right
now,
all
we
have
is
one
solution.
A
I
think
part
of
our
problem
is
all
of
this
is
separated
and
it
might
actually
be
it.
May
you
know,
help
it
okay,
so
it's
possible
that
just
because
we
dig
into
it,
then
it
becomes
more
confusing,
but
we
could
think
about
the
whole
format
if
it
would
be
better
to
have
like
motivation
and
goal
and
every
time
you
put
something
you
would
want
to
have
have
it
all
together.
A
A
A
How
to
manage
them
any
issues
whatever,
but
that's
also
true
for
the
CNF
developers,
if
they're
leveraging
the
capabilities
of
the
of
the
platform,
instead
of
trying
to
run
a
monolith
and
do
their
own
orchestration
within
a
a
large,
complex
CNF,
then
you
can
focus
on
other
things.
You
leverage
the
platform's
capability
and
then
you
focus
your
feature
development
elsewhere.
A
If
all
your
cnfs
are
following
my
service
practices,
then
as
a
consumer,
the
operator,
your
whole
team
can
be
trained
to
manage
the
the
cnfs
using
those
patterns
and
practices
rather
than
having
lots
of
different
ones
and
then,
similarly,
the
CNF
developer
would
be
better
utilizing.
Those
practices
when
they're
doing
development
and
whatever
else.
A
To
speak
up
if
y'all
object
or.
D
I
was
thinking
to
include
their
the
they're
all
in
the
the
the
phrase
like,
for
example,
that
one
reduced
the
attack
surface
and
just
associate
with
the
security
engineer.
So,
for
example,
saying
like
security
Engineers
can
reduce
attack,
surface
area,
multiple
processes
or
something
like
that
like
I,
just
just
including
the
role,
and
that
way
we
can
remove
all
the
the
roles
from
from
all
the
sections.
A
D
A
And
I
don't
know
that
we
need
to
say
the
operations
team.
Let's
just
who
is
it?
You
just
get
support,
scaling
individual
processes.
D
D
A
A
A
D
One
of
the
things
is
like
the
troubleshooting
and
probability
of
the
lock
output,
and
the
left
thing
is
simplifying
the
scaling
process.
B
A
A
Now
these
are
like
benefits,
so
it
should
probably
be
goals.
The
best
practice
benefits,
seeing
if
consumers
and
following
ways,
okay,
improve
security
through
isolation,
I,
don't
know
how
this
is
relevant,
use
the
container
name
system,
okay,
so
I
guess
they
are.
If
you
split
the
processes-
and
you
don't
have
the
same
process
type
in
the
same
container
so
now
you've
split
them
into
different
pods
in
their
own
container.
A
Unless
we're
gonna
say
something
like
in,
let's
say,
security
bugs
and
one
process
type
effect,
all
other
processes
in
the
same
container
does
that
make
sense
as
a
problem
when
you
have
a
bunch
of
different
processes
together.
A
And
if,
if
one
of
those,
let's
just
call
it
different
applications
to
make
it
simpler,
if
you
have
a
bunch
of
different
applications
in
one
container
and
then
you
have
a
security
bug
in
one
of
those
applications.
Well
then
it's
now
caused
a
security
problem
for
all
the
other
applications.
C
A
Let's
do
the
like
Apache
and
postgres
postgresql.
A
D
So
so,
what
about
just
instead
of
books,
we'll
narrate
these
in
general.
A
All
right
vulnerabilities
in
one
process
and
then
we
have
the
goals:
let's
see
reducing
attack.
Okay,
when
we
do
that
now
we
have
this.
A
A
Sources,
Source
yeah
I
was
going
to
say,
process
type
sources
instead
of
a
single
process
type
all
right.
A
And
really
I
guess
I'm,
saying
log
messages
from
a
container,
so
we're
not
saying
this
whole
CNF,
because
the
whole
CNF,
you
know,
maybe
there's
something
or
the
product
or
whatever
I'm,
going
to
say
that,
so
you
have
a
product
that
maybe
have
multiple
components
and
everything.
But
this
the
product
is
broken
up
into
microservices
in
each
of
those
microservices
you
know,
is
a
single
process
type
in
a
container.
A
D
So,
regarding
logs
well,
there
are
a
lot
of
local
aggregator
tools
in
like
block
size
and
all
of
these
so
I
guess.
The
major
advantage
is
that
you
know
you
don't
need
to
to
rely
on
those
tools.
Right,
like
I
mean
you
have
like
a
if
you
want
to
troubleshoot
something.
D
So
so
you
can
go
directly
to
the
container
and
you
will
see
only
one
unique
block
instead
of
like
having
to
correlate
all
this
yeah
instead
of
writing
or
like
putting
things
in
many
many
places
or
or
like
I,
mean
mostly
like
the
simplification
right,
like
the
the
fact
that
you
have
multiple
logs,
it's
not
affecting
the
the
the
operation
of
the
containers,
yeah
the
CNF
right.
So.
D
What
I
mean
is,
is
you
can
you
can
get
the
similar
benefit,
but
you
have
to
rely
on
additional
tool
like
a
longer
grader
to
to
collect
all
the
logs
and
put
in
a
single
centralized
place
and.
A
A
Gather
and
label
everything
from
oh:
this
is
a
multi-process.
Oh,
these
are
different
Apache.
This
is
postgres,
even
though
it's
in
the
same
container,
all
of
it
becomes
simpler.
If
you
follow
the
same
standard,
so
you
some
of
those
tools
that
you're
talking
about
have
become
very
advanced
in
their
capabilities
because
nobody
was
following
standards,
so
they
just
had
to
add
more
and
more
ability
to
reception,
identify
things
right.
A
But
if
you
are
following
like
just
the
very
first
standard
of
you
know,
this
related
12,
Factor
apps,
but
everybody
print
their
logs
to
standard
Out
start
there.
You
know,
then
immediately
you're
going
to
have
you're
going
to
have
the
container
plus
a
lock
and
then,
if
you
have
one
process
per
container,
then
we
immediately
know
that.
Okay,
that's
the
whatever
process,
that's
the
Apache
container,
so
all
logs
from
that
are
the
Apache
logs.
A
Now,
whether
you
end
up
using
something
external
and
you're
pulling
it
in
and
have
like
some
external
monitoring
and
observability
system
that
may
like
give
alerts
and
Page
people
and
everything
else,
that's
something
else,
but
you
could.
When
you
do
that
alert,
you
could
Point
everybody
right
to
it.
This
container,
this
container
gave
the
alert
it's
an
Apache
alert.
We
know
that
there's
no
other
processors,
no
database,
there's
nothing
else.
A
So
the
whole
thing
becomes
easier.
So
now
someone
like
the
admin
or
someone
jumps
in
and
goes
oh
yeah.
We
need
to
restart
those
they're
having
problems
or
they
go.
Oh,
let's
escalate
that
to
the
vendor
and
it
points
it
right
down
and
you
know
they
have
VPN.
They
can
go
in
and
connect
and
work
on
it
whatever
it
is.
The
whole
the
whole
procedure
becomes.
D
A
A
Let's
see
so
we
only
have
a
couple
more
here:
improvements,
life
cycle
management,
deployability
when
a
process
binary
or
deploys
a
container.
It's
coarse
grain
relative,
the
rate
of
change
of
the
binary
and
container
but
fine-grained
relative,
the
rate
of
change
of
other
processes
and
their
dependencies.
A
A
A
So
we
talk
about
the
orchestration
part,
increase
the
use
so
there's
something
here
with
the
orchestration.
So
maybe
those
need
to
be.
A
A
A
A
We
could
do
the
same
thing
that
we
did
in
goals
and
just
merge
it
all
and
not
have
different
sections.
I
can
see
that
someone,
that's
a
con
operator
or
someone.
That's
a
developer
may
want
to
go
to
the
different
sections,
but
we
may
be
breaking
it
down
more
than
needed.
Maybe
they
just
look
and
find
the
bullet
points
that
matter
them,
and
we
don't
worry
about
making
sections.
B
A
A
A
B
A
A
A
D
A
D
I
guess
the
the
major
differentiator
in
the
fio
is
the
scale
like
everything
is
sinking
in
the
scale
like
to
deployed
thousands
of
CNF.
So
that's
probably
the
major
difference
anyway.
B
D
Or
do
you
need
more
approvals?
No.
A
C
Yeah
I
will
send
a
message
over
and
you
guys,
let
me
know,
I'll
mainly
direct
it
to
Victor
and
and
to
you,
Taylor
and
see
if
we
can't
set
up.
You
know
at
least
the
session
today,
if
not
today,
tomorrow,
you
know
I'll
I'll
fire
off
a
suggestion,
and
if
that
works
for
you
guys
we'll
meet
otherwise
we'll
just
move
it
until
we
figure
something
out
and
then
I'll
share
I'll
share
in
case
there's.
Anyone
else
who
wants
to
join
I'll
share
that
on
the
slack
Channel.