►
From YouTube: CNCF CNF WG Meeting - 2023-07-31
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).
B
I
was,
hopefully
so
I
wasn't
sure
like
a
Steve
Taylor
just
and
the
meeting
or
like
I,
don't
know.
C
Yeah
that
was
strange,
I
had
I
had
to
meet
and
run
over,
so
I
didn't
I
couldn't
get
to
it
any
sooner,
but
yeah
that's
kind
of
interesting
I.
Don't
know.
Let's
see.
A
C
B
Well,
I,
don't
know:
do
you
want
to
take
advantage
of
this
time
or
like
discuss
something
or
like
or
talk
about
something
I
mean
nothing
have
to
be
like
with
a.
C
Yeah
I
know
what
you
mean:
I
know
what
you
mean.
Well,
let
me
let
me
say
this.
C
I'm
just
trying
to
go
to
our
I'm
going
to
the
repo
there,
where
we
have
our.
C
Yeah
I
I
think
one
of
the
best
practices
that
I
think
you
know
we've
been
talking
about
for
a
while
and
I.
Don't
know
how
we
get
past.
You
know
how
I
know
it
needs
some
work
and
I've
been
trying
to
make
some
comments,
and
you
know
you
know,
make
some
contributions
to
it.
I'm
I
find
a
little
hard
to
navigate
it.
The
best
practice
document
itself
right
but
I
in
that
for
the
CNF
container,
should
have
one
process
category
there's
a
draft
proposal
and
so
I
started
putting
some
things
in
there.
C
I
I
I
would
be
I,
don't
know
if
you
know
it's
that
common,
but
I
mean
I
would
be
happy
to
like
set
aside
some
time
and
work
together.
If
that
would
be
a
way
to
do
it,
maybe
even
with
Taylor.
You
know
just
because
I
feel
like
before
we
get
this
one
finished
we're
talking
about
different
ones
and
I.
Don't
know
it
just
feels
like
for
and
I'm
I.
C
Don't
I'm
not
pointing
criticism
or
anything,
but
it
just
feels
like
we
start
something
and
then
before
we
know
it
nothing
happens,
and
then
we
start
a
new
one
and
then
kind
of
the
same
thing
happens
with
that.
It
feels
like
we
need
an
effort
to
get
this
one
over.
The
you
know
push
it
to
the
finish
line
and
then
you
know
be
done
with
it
and
then
pick
up
the
next
one
or
or
is
that
just
me
I
mean?
C
Do
you
know
what
I
mean
it
feels
like
if
I
think
of
just
like
using
nephew,
you
get
something
you
work
at
it,
you
get
it
done,
and
then
you
say:
okay!
Well,
what's
the
next
one
coming?
It's
not,
we
don't
have
obviously
a
formalized
release
for
our
best
practices
but
I.
Maybe
that
wouldn't
be
a
bad
idea.
You
know,
like
pick
two
pick,
two
best
practices
or
pick
you
know,
have
a
collection
and
say
which
ones
do
we
want
to
have
you
know?
C
B
Yeah
I
know
what
what
do
you
mean,
like
that's
true,
like
it's
very
redundant,
perfect,
so
yeah,
let's,
let's
try
to
just
release
something
but
just
release
it.
Instead,.
C
C
I,
don't
I
mean
I,
don't
have
as
much
you
know,
I
don't
have
as
much
experience
in
the
open
source.
You
know
I
mean,
as
I
mentioned
to
you,
since
you
know,
I
really
only
started
working
in
open
source
since
I
came
to
Matrix
about
three
years
ago
and
and
there's
a
different
mix
of
the
areas
that
I'm
involved
in
where
you
know
some
of
it
looks
like
nephew.
You
know
which
very
structured,
very
coordinated
release.
You
know
it's
obviously
creating
software,
which
you
know
this
is
I
mean
our
best
practices.
C
Don't
directly
result
in
software
that
we're
creating
right
here
in
the
working
group,
but
it
does
have
it
does
feed,
for
example,
the
the
CNF
test
Suite,
so
I
would
just
think
you
know
I
I
just
think
it
would
be
interesting
to
sort
of
have
a
a
think
about.
C
You
know
how
are
we
working
in
terms
of
structure
because
and
I
know
you
and
I
talked
about
this
a
while
ago,
where
you
know
if
I
knew
what
topic
we
were
planning
to
talk
about,
then
you
know
I
might
bring
somebody
who
I
felt
could
contribute,
but
I
can't
just
have
them
come
and
listen
and
see.
If
we
maybe
talk
about
it,
you
know
what
I
mean
and
I
know.
Sometimes
it's
just
like.
Okay,
we
have
a
draft,
let's
review
it
and
then
you
can
sit
down
and
have
a
comment.
C
But
it's
that's
why
I
still
think,
maybe
rethinking
how
we're
working
in
terms
of
you
know
almost
like
a
release.
Schedule,
I
I,
don't
know,
maybe
that's
stupid
or
maybe
there's
Alternatives,
but
something
okay
for
this
quarter.
You
know
our
intention
is
to
work
on
two
best
practices.
These
are
the
candidates,
let's
work
on
them
and
let's
get
them
done
and
then
you
know
you
do
the
next
quarter
and
you
can
constantly
be.
C
You
know,
let's
open
source,
we
vote,
you
know
which
ones
which
ones
are
the
ones
we
want
to
work
on,
so
that
we're
not
forcing
anything
but
then
I.
Think
and
then
people
know
okay
for
the
next
quarter,
I'm
not
interested
in
those
best
practices.
I
won't
be
part
of
it
and
the
ones
who
really
are
interested
in
it
can
be
could
be
there
working
together
to
try
to
make
it.
You
know
possible
to
finish.
B
Yeah
yeah
like
like,
has
it
I
mean
but
I
like
that,
by
the
way
like
putting
like
a
deadline
or
short
commitment,
yeah.
A
B
C
Think
we
I
think
we
like
and
I
think
you
mentioned
it
last
time
and
and
I.
Don't
it's
not
a
bad
idea.
I
mean.
Obviously
all
these
we
do
spend
time
on,
highlighting
all
the
upcoming
events
and
I
think.
That's
all
really
good,
but
you
know
I
think
this.
It's
taken
that
takes
more
of
the
a
lot
of
the
attention
on
this
meeting.
It's
like
okay,
because
I
know
it's
one
of
the
more
concrete
things
we
have
right.
C
B
D
B
Really
surprised
me
is,
like
I
mean
the
the
interest.
Is
there
like,
of
course,
because
when,
when
we
are
doing
those,
these
events,
like
the
the
CNN
GNC,
have
a
working
group
got
an
event
and
in
Amsterdam
people
were
showing
off
like
a
the
target?
Is
the
same
the
same
thing
people
like
to
consume
the
the
the
information
participle
or
get
something
about
like
all
these
Trends
in
the
Telecom
industry,
but
I
feel
like
when
it's
time
to
collaborate
and
start
like
submitting
ideas
like
putting
things
on
paper
or
sharing
or
just
simple.
B
The
fact
is
to
sharing
things
this
one
when
the
things
get
in
exchange
right
because
they're,
like
a
for
example
in
this
case,
like
a
most
of
the
people
who
are
attend,
those
meetings
are
expecting
to
consume
and
to
consume,
to
resolve
issues
or,
but
they
are
not
willing
to
exchange
ideas
or
to
propose
ideas
even
when
they
are
crazy
or,
like
so
yeah.
It's
kind
of
crazy,
like
yeah,.
C
I
I
I
I
I'm,
not
saying
that
it
would
be.
You
know
it
would
solve
everything,
but
I
do
feel
like
if
we
were
just
a
step
back
almost
and
say:
okay,
how
many
people
are
attending
this
meeting?
And
you
know
we
know
that
it's
less
than
10
people
that
you
know
it
regularly
attend
it's
a
fairly
small
group
at
the
moment-
and
you
know
maybe
just
think
about
I
mean
maybe
have
a
session.
C
C
E
C
Document,
for
example,
how
to
collaborate
and
I
think
again,
you're
we're
asking
a
lot
of
people
to
invest
time
when
they
don't
really
understand
how
we're
you
know
how
we
work
right.
It's
like
okay,
we're
going
to
make
some
best
practices
and
I
I
know
I'm,
being
very
you
know,
I'm
almost
being
very
negative
and
I
don't
mean
that,
but
it's
like
I
I
think
it
would
be
more
obvious
if
we
said
okay
here
is
our
plan,
for
you
know
2024.
C
each
quarter.
We
think
it's
realistic
to
introduce
or
to
specify
at
least
you
know,
one
to
two
best
practices.
I,
don't
know,
I
mean
I'm
just
making
numbers
up.
Therefore,
then
we,
you
know,
we
have
a.
We
have
a
repo
that
has
a
bunch
of
issues
and
things,
and
maybe
from
that
we
can
have
a
you
know,
kind
of
a
a
running
list
of
best
practices
that
that
you
know
we
believe
their
topics
right.
Their
issues
that
we
believe
could
in
could
result
in
a
best
practice.
And
so
then
we
try
to
look
at.
C
You
know
two
or
three
of
those
per
quarter,
but
actually
not
keep.
Switching
and
looking
at
new
things,
but
just
say:
let's,
where
we're
at
now
last
week,
there
was
no
collaboration
with
nothing
happened.
Okay,
guys
we're
not
going
to
make
our
goal,
you
know
how
do
we,
how
do
we
and
and
sort
of
just
focus
on
how
do
we
get
those
three
two
or
three
or
whatever
it
is
per
quarter
over
the
finish
line
and
I
think
it
might
find
it's
like
well,
I
need
to
talk
to
somebody
I'm,
not
just
you
know.
C
Maybe
we
should
set
up
a
meeting.
You
me
and
somebody
else,
and
we
work
on
a
section
and
then
next
week
we
review
it
together.
You
know
and
I
think
that
would
be
me.
It
might
help
people
to
understand
because
I
don't
I
have
a
feeling.
Sometimes
people
just
don't
know
how
to
really
contribute.
Still.
They
don't
feel
comfortable
just
going
into
the
document
and
starting
to
write.
B
Yeah,
no
no
I
definitely
agree
with
what
you're
saying
is.
Is
I
mean?
That's
that's
a
way
to
describe
commitment
right
like
a
our
commitment,
is
to
release
at
least
one
or
two
or
three
best
practices
per
quarter
per
month
or.
C
Week
or
yeah
sure
exactly
just
something
that
we
can
agree
on,
I
I
totally
agree
with.
You
I
think
that
that
would
help
people,
because
otherwise
it
is.
If
you
were
to
ask
somebody
right
now:
I
mean
it
doesn't,
and
you
know
what
is
the
ambition
of
the
you
know.
You
know
what
is
the
ambition
of
our
of
our
working
group
to
develop
best
practices?
Okay,
how?
How
many
have
you
done
so
far
or
how
many
do
you
plan
to
you
know
we
don't
have
any.
We
don't
have
anything
set
like
that.
C
So
I
think
we
we
struggle
to
articulate
whether
we
are.
Are
we
progressing
well
or
we're,
not
progressing?
Well,
you
know,
I,
don't
I,
don't
think
we
have
anything
to
measure
against
and
and
therefore
I
don't
it
doesn't
really
allow
us
to
make
any
corrections
or
changes.
That
would
maybe
help
us
be
more.
You
know
more
productive
or
more.
You
know
successful.
B
The
other
thing
that
I
was
thinking
is
like,
usually
when
the
people
say
like
I,
don't
have
time
for
this
or
for
there
or
whatever.
Usually
that
reflects
that
the
fact
that
you're
saying
this
is
not
my
priority
right.
It's
basically
that
like
because
all
of
us
have
the
same
hours
of
the
day.
So
it's
just
my
life
just
choosing
or
picking
the
tasks,
and
there
are
different
types
of
priorities.
B
So,
for
example,
if
we
don't
set
the
right
priority,
if,
if
our
cooperative,
for
example,
for
us
to
be
releasing
best
practices,
I
can
guarantee
that
we'll
release
a
lot
of
him,
because
that
that
was
our
appropriate.
But
in
this
case
I
I
know
we
have
a
lot
of
different
things.
I
mean
those
things
are
volunteer
and
probably
it's
pretty
hard
to
like
printings
in
order
yeah
I
guess
we
have
to
change
that
like
I
think
well,
this
is
going
to
be
our
topper.
It
is
just
these
are,
or
major
metrics.
A
A
B
A
F
Hello
good
morning,
yeah.
A
F
Already
started
and
then
ended
the
call,
since
what
he
was
on
earlier
I
think
the
recording
on
YouTube
will
show
that
I
don't
know
if
it's
going
to
include
this
or
not,
but
this
might
be
like
a
separate
recording,
yeah.
F
B
Well,
actually,
I
think
that
we
were
talking
about
like
a
ways
to
the
Livermore
things.
Probably
if
we
can,
we
can
switch
Dynamics
or
to
something
because
yeah
I
mean
we
have
a
lot
of
drafts
which
are
good,
but
at
the
end
of
the
day
or
one
of
them
are
left.
So
we
have
this
and
she
does
push
it
to
the
latest.
Step
like
and
and
Oliver
was
just
in
like
like
a
a
try
to
focus
in
a
single,
a
single
best
practice
per
month
required
whatever
and
just
release
it.
B
Because
I
mean
it's
not
going
to
be
perfect,
but
we
have
to
do
something
because
otherwise
we
are
still
accumulating
things
and
birthdays.
First
and
yeah,
it's
not
going
to
show
what
we
have
been
doing,
because
the
end
of
the
day
we
are
still
working,
we're
still
investing
time
and
these
meetings
discussing
ideas
but
yeah.
The
final.
The
final
step
is
it's
not
showing
those
those
efforts.
C
Yeah
well,
I
think
we
we
just
you
know
we
we
were
just
you
know
again,
just
brainstorming
some,
you
know
mostly
just
having
a
conversation
just
catching
up
a
little
bit,
but
I,
don't
I
I
mean
if,
if
we
just
kind
of
back
up
and
say
okay,
so
when
do
we
start?
And
you
know
we-
we
I
think
we
all
recall
at
least
to
kick
off,
and
you
know
we
started
off.
We
had
a.
It
was
a
huge
like
anything,
new
and
shiny.
There
was
a
lot
of
people
joining
in
the
very
beginning.
C
Today,
I
think
a
number
you
know
we're
probably
less
than
10
people
who
are
regularly
attending,
but
I
think
you
know
just
from
a
perspective
of
so
what
it.
What
is
the
stated
objective
and
of
this
group
and
I
think
we
have
that
I.
Think
then,
though,
in
terms
of
practice
in
terms
of
way
of
working,
it's
a
little
less
unclear
what
our
Ambitions
are
in
terms
of.
Are
we
on
track
or
are
we
not
on
track?
C
In
other
words,
you
know
we
don't
have
anything
to
quantify,
not
not
that
I
know
of
that
says.
We
have
an
intention
to
release,
you
know
X
number
of
best
practices
per
year,
and
maybe
that's
not
even
realistic.
So
then
there
should
be
something
else,
but
I
think
it's
very
difficult
for
people
to
you
know
and
I'm
I'll
say
myself,
it's
difficult
to
know,
shouldn't
we
be
creating.
You
know
two
best
practices
every
three
months
or
something
or
you
know
six
or
six,
six
and
a
half
every
half
a
half
a
year.
C
Something
that
you
know
then
helps
us
to
understand
all
right.
So
are
we
are
we
meeting
that
or
not
and
if
I
just
take
the
we're
not
meeting
it
just
for
the
sake
of
argument,
you
know
saying:
okay,
we're
not
meeting
it.
Then
you
stop
and
you
go
okay.
So
why
is
that?
What
is?
Is
it
just
no
nobody's
attending
and
nobody's
helping
out?
Okay?
So
how
do
we
make
them
attend?
Or
how
do
we
help?
You
know
what
is
it
that
that's
causing
us
not
to
get
across
the
finish
line,
and
we
were.
C
We
were
just
talking
a
little
bit
about
it
feels
like
you
know,
people
come
with
new
ideas
before
we
even
finish.
Some
of
the
old
ideas
that
you
know
got
progress
so
and
I
know
right
now.
If
we
just
use
a
concrete
one,
we
have
the
the
best
practice.
For
you
know
we
have.
The
draft
for
CNF
containers
should
have
one
process.
Category
and
I
know
you
know:
I
I,
I'm,
not
I,
haven't
been
a
major
contributor
to
that.
I've
started
putting
some
things
in
trying
to
make
some
con.
C
You
know
ads
and
things,
but
even
there
I'd
almost
prefer
to
be
able
to
work
with
someone
like
yourself
or
like
Victor
and
just
sort
of
say.
Okay
and
I
can
maybe
get
an
action
point
say:
oh
Oliver
go
away,
you
need
to
get
some.
We
need
something
here
and
I
think
by
doing
that,
you're
kind
of
assisting
and
helping
each
other
and
we
get
it
across
the
Finish
Line.
C
Otherwise
the
risk
is
this
sits
here
and
draft,
and
we
start
looking
at
a
new
one
and
then
we
end
up
with
a
lot
of
those.
You
know
kind
of
partially
finished.
So
that's
that
was
basically
as
far
as
we
went
and
I'm
you
know,
I,
don't
know
that
we
have
all
the
answers,
but
it
feels
like
we
there's
knowledge,
there's
people
who
could
help
us
get
us
things
across
the
finish
line
and
and
I
think
that
would
be.
You
know
success.
You
know
help
to
the
success
of
this
group.
F
We've
set
numbers
before
I
guess
as
far
as
goals
yeah,
we
can
adjust
goals
and
I.
Don't
know
that
we
need
to
set
any
goals
for
the
well.
Maybe
I
should
just
say:
I,
don't
know
what
goals
were
set,
but
it
should
probably
be
set
based
on.
What's
realistic,
we're
not.
F
Definitely
different
from
a
company
where
you're
trying
to
have
a
service,
a
new
feature
product
or
whatever,
and
you
know
you
need
to
get
that
done-
is
different
from
an
open
source
project
where
you
may
have
people
working
on
something
and
towards
the
release.
But
it's
a
little
bit
close
to
that
in
that
in
an
open
source
project.
It's
what
do
people
want
to
work
on
and
if,
if
it's
of
interest
to
them-
and
they
have
the
time,
then
they
may
do
it
well.
I
I
agree
with
that.
F
We
can
say
that
we
would
like
to
release
this
many
best
practices
in
a
quarter
and
then
try
to
you
know
whatever
we
want
to
do,
publish
or
something
on
this,
whatever
we
want
to
do,
but
it's
how
people
are
willing
to
put
time
into
it
and
what
time
they
have
available.
I've
been
saying
for
a
while
that
I'm
available
to
do
like
a
working
session
on
any
that
people
are
passionate
about,
but
there's
nobody
being
forced
to
do
it
so.
B
What
is
through
Taylor,
we
are
all
agree
about
like
definitely
we
have
to
do
some
I
mean
something
different
because
the
formula
we
having
a
plan
for
a
while
has
been
give
us
good
or
bad
results
like
I,
don't
know
like,
but
but
now
like,
it
seems
like
the
trend
as
we
are
taking,
is
important
to
do.
B
F
B
The
thing
right,
it's
pretty
hard
like
that,
because
I'm
I'm
sure
like
I,
don't
know
why
why
I
don't
know
what
this
adjustment
is,
what
Oliver
was
saying
it
makes
sense,
make
make
sense,
like
I
start
trying
to
focus
on
a
single
thing
for
per
week
or
like
try
to
be
more
like
a
less
less
disperse
I.
Guess
like
just
picking
one
single
thing
and
just
going
there
until
the
end.
Probably
that
could
be
a
a
good
alternative.
C
I
I
feel
like
it's
almost
just
and
I,
don't
know
Taylor
I
mean
well
both
of
you
and
and
I'm,
not
sure
you
know.
Maybe
it's
a
conversation
I'm
happy
to
be
part
of
that.
But
if
you
know
this
as
a
as
a
three
co-leads,
maybe
just
as
a
we
could
have
a
conversation
right.
So
let's
just
have
an
open
conversation.
How's
this
going
or
do
we.
You
know
we
feel
like
this
is.
Are
we
successful
at
the
moment,
or
you
know,
and
I
and
I'm
sure
we
probably
align
them?
We
could
be
doing.
C
We
could
be
making
some
better
progress.
Okay,
what
ideas
do
we
have
and
maybe
between
us
we
could
come
up
with.
You
know
a
couple
options
that
we
could
then
share
with
back
to
the
group
and
I
I.
Don't
necessarily
think
they
have
to
be
huge
changes,
but
I
mentioned
this
before
Taylor
as
an
example,
I
mean
I.
You
know
that
within
Matrix
there
are
people
who
are
much
closer
to
the
code.
C
You
know
and
the
real
world
challenges
that
we
face,
but
their
time
is
extremely
limited,
so
I
can
bring
them
in
for
specific
topics
when
I
have
a
chance
to
say
on
Monday
we're
going
to
be
talking
about
this,
and
this
is
important
to
us.
I
want
you
know,
someone
from
you
know
from
our
engineering
team
someone's
seeing
you
from
there
who
can
you
know,
articulate
some
of
the
things
that
that
are
important
and
and
hopefully
contribute
also
back
in
terms
of
you
know.
So
what
would
be
the
best
practice
right?
C
I
have
a
hard
time
doing
that
if
I
can't
just
invite
them
to
join
the
meeting
to
see
if
a
topic
is
going
to
be,
you
know
relevant
to
us
and
I,
don't
know
if
any
other
companies
are
the
same
way
and
I
think
you
know
we
might
have
people
who,
if
they
knew
that,
there's
a
topic.
The
topic
right
now
is
we're
going
to
finish
this
CNF
container,
and
you
know
maybe
we
bite
off
chunks
of
the
document
right.
Okay,
the
first
section
we're
comfortable
with
this.
C
The
two
three
people
who've
been
working
on
it.
Let's
walk
through
that
we're
good.
This
is
what
remains
we're
asking
specifically
for
this
from
any
vendor
or
any
participant
here.
In
other
words,
it's
a
little
bit
of
hand
holding,
but
it's
it's
guiding
and
saying,
and
then
we
will
have
a
conversation
on
this
on
the
following
Monday.
So
in
other
words,
we're
working
very
much
with
one
of
these
items
that
we've
picked
out
until
we
actually
get
it
done
now.
C
C
People
can
come
in
with
a
new
idea
and
say:
hey
I
have
a
new
idea
for
new
best
practice.
So
that's
what
I'm
trying
to
get
you
know,
at
least
in
my
head,
I,
think
that
might
help
people
to
be
a
little
more
prepared,
for
you
know
the
way,
we're
working
and
what's
the
topic
that
we're
we're
working
with
a
little
more
consistently.
C
It's
just
an
idea,
I
mean
I'm,
sure,
there's
many
others,
some
other.
You
know
other
options,
but.
F
So
the
only
difference
that
I'm
seeing
right
now
with
what
we
have
is
we're
not
explicitly
saying
we
are
absolutely
going
to
work
on
the
a
single
best
practice,
the
next
time
or
whatever
the
topic
is
and
nothing
else.
That's
the
only
thing
we
have
the
opportunity
right
now,
for
we
can
do
it
every
week.
It's
always
there.
F
It's
all-
and
it's
been
said
every
time,
I
I
personally,
don't
think
it
has
to
do
with
people
not
knowing
that
it's
the
this
one
process,
category
particular
per
container,
has
been
there
as
let's
get
this
done.
We've
said
that
for
a
while
you
it's,
where
is
anyone
available
and
right
now,
instead
of
working
on
it?
We're
talking
about
these
other
things
like
we
could
literally
just
say:
let's
stop
talking
and
go
work
on
that.
C
C
You
know,
okay,
let's
look
at
this.
This
is
again
for
those
there'll
be
people.
There
have
been
people
who
popped
in
on
the
latest
call
and
then
haven't
shown
back
up
again.
I
don't
know
because
the
topic
was
not
interesting
or
they
don't
know
how
to
contribute
and
I
know.
We've
written
you
know
material
about
how
to
contribute,
but
I
think
you
know
from
you
know,
having
one
or
two
best
practices:
three
best
practices,
as
you
start
to
kind
of
work
through
those
and
people
start
going.
C
Oh
okay
I
get
this
and
you
might
find
that
people
are
a
little
bit
more
independent
in
terms
of
being
able
to
contribute.
You
know
asynchronously,
but
I
think
maybe
for
the
benefit
of
the
group.
We
might
say:
hey.
We
really
want
to
get
this
particular
best
practice
and
again
it
I
just
used
the
one.
It
was
an
example,
but
we
would
pick
whatever
one
and
we
say
we
think
we're
so
far
with
this,
and
we
just
need
to
help
push
it
across
the
Finish
Line.
We're.
C
C
Making
it
up
but
to
come,
contribute
help
put
the
stock.
You
know
put
finish
this
document
and
then
we
present
it
to
the
group.
Any
questions.
No
great
can
we
get
the
looks
good
to
me
and
then
we
move
on
to
the
next
one
and
we
might
find
that
that
we
get
a
little
bit
more
focused
because
again,
I
think
people,
don't
it's
just
a
it's
just
an
opinion,
so
I
just
feel
like
people
come
and
they
don't
really
know.
C
So
what
what
will
be
the
topic
today
and
I
know
that
they
know
about
this
best
practice,
but
you
know
we're
also
willing
to
entertain.
Oh,
is
there
something
else
of
more
interest
that
you'd
like
to
talk
about,
and
then
we
might
get
sidetracked
right?
We
get
a
new
thing
to
start
looking
at
and
we
may
not
may
or
may
not
finish
that
one
either
that
that's
my
only
you
know
that
was
my
only
thinking
in
terms
of
and
it
may
not
succeed,
but
I
feel
like.
We
should
try
something.
C
You
know
try
some
different
approaches
here,
because
I
think
I'd,
like
I'd,
like
to
see
you
going
back
to
your
comment.
How
important
this
is
to
companies
I.
Think
a
lot
of
companies
I
would
I
would
expect
are
are
certainly
interested
in
the
outcome.
I,
don't
know
if
they're
interested
in
the
putting
the
time
and
effort
in,
but
if
they
start
to
see
outcome
that
might
also
you
know
all
of
a
sudden.
You
go.
Oh
wait
a
minute.
C
There
are
things
happening
now,
things
are
actually
being
produced
that
you
know
will
shape
how
people
see,
cnfs
and
and
sort
of
what
a
good
CNF
is
and
that
might
bring
them
back
to
the
table
as
well
when
they
start
seeing
that
there's
an
output.
If
there's
not
a
lot
of
output,
they're
not
going
to
be
too
concerned.
B
The
other
thing
that
I
was
thinking
about
it's
easy
to
say
a
lot
of
things
right
and
if
someone
has
been
doing
a
lot
of
things
and
make
us
sit,
and
this
working
group
has
been
Taylor
so
I
have
to
recognize
that
Taylor
has
been
do
a
lot
of
a
lot
of
work
and
yeah
collecting
information
promoting
the
the
different
events
like
spraying
in
the
world
like
Dustin
Taylor,
has
been
doing
a
lot
of
things
and
I
guess
this
is
not
a
critique
of
what
Taylor
has
been
done.
B
F
I
recognize
it.
This
is
being
crazy.
I'm
really
not
worried
about
that
I,
but
I
appreciate
your
your
sentiment
on
that
I
I'm,
not
I'm,
not
taking
any
of
this
as
a
critique.
F
My
issue
is
that
I
don't
feel
like
people
are
contributing
and
that's
not
that's
why
it's
not
getting
done
and
I
could
go
in
and
Victor
can
go
in
and
and
we
can
just
complete
a
practice
on
our
own
I
can
take
the
time
to
go
complete
that
the
point
would
be
to
try
to
get
more
than
one
contributor
to
to
write
up
a
best
practice
and
that's
what
I'm
hoping
for
yeah.
F
The
reason
why
I
haven't
just
said
we're
going
to
work
on
the
one
concern
is
because
I'm
I
feel
like
I'm,
forcing
my
opinion
on
that,
and
this
is
why
I've
said
if
there's
something
that's
more
relevant
for
anyone
else
than
I'm
happy
to
spend
my
time
working
on
that.
So,
if
Matrix
said
hey,
we
actually
care
about
this
other
best
practice,
and
this
is
where
the
engineers
would
be
passionate.
Then
I'd
be
happy
to
just
let's
focus
the
time
and
put
that
forward.
F
As
the
agenda
item,
but
me
going
Oliver,
can
you
go
ask
folks
from
your
team
to
join
the
call
and
put
their
time
into
something
that
may
not
be
of
interest
that
doesn't
feel
okay?
This
is
this
is
a
open
area?
That's
supposed
to
be.
You
contribute
because
it
matters
to
you
now.
I
do
want
to
say.
Oliver
you've
put
comments
in
there,
so
I
know
you've
been
adding
to
that
best
practice
and
trying
to
make
adjustments.
F
I
really
feel
like
it's
just
time
we
haven't
put
the
time
into
it,
and
I
have
been
thinking
like
before.
Y'all
join
the
call
like
especially
today,
thinking
I
just
need
to
go
in
and
try
to
resolve
all
the
comments
in
the
practice
myself
and
try
to
get
it
to
a
point
where
it's
you
know
where
I
think
it's
ready
and
and
then
put
it
Forward
I
mean
there's
comments.
A
lot
of
them
are
me
putting
stuff
in
and
asking
for
feedback.
F
The
latest
ones
were
from
you
Oliver,
but
I
could
do
that.
I
could
just
go
in
and
finish
this
out
and
then
present
it
yeah.
C
And
I
I
hear
I,
hear
you
Taylor
and
I
think
we're
not
that
far
off
from
I
I.
Don't
hopefully
we're
not
that
far
off
from
one
another
in
terms
of
what
I'm
trying
to
say,
which
is,
let
me
try,
let
me
try
backing
up
and
just
catching
a
few
points.
So
one
absolutely
I
I
recognize
that
the
the
the
co-lead
shouldn't
dictate
what
best
practices
we
work
on.
C
That
would
feel
very
strange,
so
I
do
think
there
may
or
may
not
be
an
opportunity,
and
it
may
or
may
not
be
that
easy
to
do,
but
we
might
be
able
to
say,
for
example,
over
the
next
quarter.
You
know
here's
here's
five
best
practices
that
we
think
you
know
are
are
are
maybe
good
for
discussions.
Anyone
have
that
you
know
anything
else
they
would
like
to.
C
In
other
words,
you
just
try
to
do
a
set
of
little
scoping
and
they
say:
okay,
let's
try
to
look
at
these
and,
let's
start
working
on
and
then
it
just
kind
of
keeps
it
provides
a
little
bit
of
focus
for
a
short
period
of
time
and
then
you
know
there's
another
opportunity
to
say:
okay,
let's
look
again,
it's
almost
like
backlog.
You
know,
grooming
and
say:
okay,
here's
the
here's,
the
next
five
are
these
still
the
relevant
ones
or
is
there?
Something
else
is
something
else
popped
up?
C
C
C
You
know
specific
on
this
and
I
and
I.
You
know
like
how
do
you
guys
see
this
as
a
challenge?
Or
you
know
what
are
some
of
the
exceptions
or
I'm
just
saying
to
you?
I
have
some
personal
challenges
in
writing.
The
best
practice
going
in
the
document,
knowing
exactly
how
I
can
contribute,
maybe
there's
other
people
in
the
same
place,
I
think
you
and
Victor
and
I'm
sure
others
have
you
know-
have
probably
feel
confident
in
going
in
the
document,
but
we
do
need
more
scale.
C
That's
the
only
way
I
can
describe
it,
I
mean
otherwise.
I
can
just
go
put
it
in
the
document
and
then
we
can
all
look
at
it.
10
people
I
just
think
it
would
be
more
effective
if
we're
a
small
working
group
to
kind
of
try
pushing
it
over
the
you
know
pushing
it
to
a
ready
state
for
review.
D
F
Been
offering
doing
individual
or
small
working
sessions
for
for
months
now,
I'm
willing
to
do
it.
Okay,.
C
C
F
F
We
I
want
to
go
back
to
one
thing.
I
said,
though
we
if
we
don't
have
a
topic.
Last
week,
we
had
a
bunch
of
questions
that
if
people
have
questions
on
this,
then
I
think
it's
okay
to
dig
into
those,
but
most
of
the
time,
if
we
don't
have
a
lot
of
topics,
we
could
spend
the
time
as
just
now
as
a
working
session.
It's
not
a
large
group
today,
so
we
could
be
focused
on
that,
like
I
I.
Don't
think
that
this
is
a
big
for
me.
F
F
C
F
C
F
C
F
Know,
I
guess
the
least
privileged
principles.
C
F
Yeah
I'm
trying
to
look
because
this
top
part
was
kind
of
reference
to
help
us
get
going
I,
don't
know
why
this
one
was
linked
at
all.
So
let
me
see
if
there's
anything
related
to
this
top
part
should
not
be
in
in
the
final
proposal.
This
was
quick
access,
anything
that's
actually
relevant,
which
would
be
the
issue.
So
that's
fine
and
then
all
of
these
right
here
to
keep
they
should
go
down
into
the
reference
section
down
here.
Okay,
anything
there.
This
was
like
quick
access.
F
While
we
were
just
trying
to
read
and
understand
what
we
were
working
on
on
the
best
practice,
okay
strictly
in
the
in
the
Google
Doc,
so
you
don't
have
to
scroll
to
the
bottom
every
time
all
right.
This
is
the
issue,
though
I
think
yeah.
A
C
F
C
C
F
That's
possible:
that's
possible
you'll.
C
See
that
through
here
that
you
know
there
were
there's
still
some
places
where
we're
referring
to
least
privilege
principle
at
least
privilege,
which
I
think
suggest
to
me.
It
was
just
from
another.
F
All
right,
so
it's
it,
doesn't
it's
not
there.
So,
at
least
in
the
discussion
itself,.
F
E
F
Right
so
this
would
be
about.
You
know
whether
you
have
one
process
or
you
have
multiple
process
types.
If
you're
writing
the
process,
a
process
manager
so
something
that's
handling,
multiple
processes
and
different
types.
F
So
there's
I
mean
the
very
first
thing
that
comes
to
mind
is
just
like
in
a
day
or
whatever,
but
you
have
different
process.
Supervisors
is
what
we're
talking
about
supervisor
D,
but
that's
not
what
I
was
wanting.
C
F
F
The
thing
it
takes
away
and
someone
can
talk
about
it,
but
supervisor
D
would
be
a
one
that
I
would
point
to
that's,
not
homegrown.
So
then
somebody
so
this
would
have
to
do
with
another
best
practice.
That's
talking
about
where
you
can
end
up
with
runaway
containers
that
never
die
and
the
kubernetes
doesn't
restart
them
because
they
look
like
they're
okay,
so
you
have
zombie
processes
and
stuff.
F
So
a
good
supervisor
is
going
to
handle
all
those
things
and
child
processes
and
there's
a
lot
of
scenarios
that
start
happening
and
when
someone
is
trying
to
manage,
manage
all
the
processes
and
keep
them
alive
in
a
container
the
number
one
they
are
probably
going
to
do
it
bad
and
then
the
system
is
not
going
to
know
when
to
restart
or
or
whatever
the
the
container
and
and
then
you're
also
likely
to
get
away
from
allowing
kubernetes
to
orchestrate
containers
and
instead
of
and
you
let
things
fail,
and
it's
supposed
to
know,
there's
a
problem.
F
Let's
report
that,
let's
have
you
know,
visibility
and
let's
start
up
other
containers,
so
always
staying
alive,
and
then
you
get
a
thicker
container.
Instead
of
having
it
a
minimal
container
where
the
orchestration
is
outside,
so
there's
a
lot
of
things
in
this,
it's
related
to
you
know,
having
a
container
only
do
one
thing:
minimize,
a
single
concern
and
and
the
processes
that
are
involved
in
that
single
concern
being
minimal.
F
Let
me
move
on
from
that
and
then
let's
maybe
come
back.
If,
if
that
did
that
make
sense
and
and
Victor,
you
may
already
understand
what
I'm
talking
about
as
far
as.
B
Yes,
yes,
the
the
other
thing
that
I
was
thinking
is
like
in
the
second,
the
second
sentence,
which
is
saying
like
the
microservice
shooting
we
focus
just
in
the
container
I
mean
yeah.
The
first
sentence
is
fine,
but
the
second
one
is
it's
just
referring
to
the
micro
service
and
I
guess:
a
micro
service
could
be
something
more
architecture
genetic,
so
it
shouldn't
be
like
a
the
container
should
not
spawn
or
process
types.
I.
D
Mean
we'll.
C
F
That
makes
sense
and
connect,
and
you
were
saying
that
Victor
I
just
put
about
getting
it
the
container.
Yes,
that's
one
other
process
types
as
a
way
to
contribute.
F
Yeah
I
guess
it's
trying
to
refer
the
scene
of
microservices
I
got
it
so
the
microservices
running
in
the
container.
That's
why
it's
trying
to
get
people
to
think
about
microservices
rather
than
the
container.
But
how
would
we
write
this
to
make
it
coherent
because
I
I
get
what
you're
saying
that
it
wouldn't
coherent
there.
C
C
E
B
Well,
first
of
all,
right
we
have
to
clarify
like
that,
because
Microsoft
you
can
use
Virtual
machines
to
use
in
a
micro
series,
architecture
right
and
that's
totally
fine,
so
microservices
is
just
an
architectural
thing.
Yeah.
F
F
Process
but
I
feel
like
I
need
to
do
that.
The
processes
in
the
container
should
not
spawn
other
process
types,
so
you
may
have
multiple
processes
or
threads,
so
you
could
have
I'm
going
to
use
the
HTTP
web
application
Apache.
You
can
run
it
with
a
single
thread
single
process.
You
can
run
it
multi-threaded
and
you
can
run
it
multi-process,
but
it's
all
the
same.
You
could
say
the
same
type
or
the
same
category.
It's
still
the
HTTP
server
when
it
spins
off
multiple
processes.
F
B
C
If
you
I'll,
let
you
just
finish
putting
that
in
there?
Would
it
be
more?
Is
it
would
it
be
accurate
or
inaccurate
to
say
so
we're
looking
at
the
sentence?
Second
sentence
there,
it
says
the
process
or
processes
in
the
container
should
not
spawn
other
process
types
as
a
way
to
contribute
to
the
workload
but
should
interact
with
other
okay,
it's
a
bit
redundant.
Sorry
I
was
thinking
with
other
processes.
You,
okay,
yeah,
never
mind.
I
was
thinking
of.
Maybe
types
should
be
there
again,
but
I.
Don't
think
so.
C
I
think
it's
more
accurate,
just
like
as
it
is
so
yeah
I'm
good
with
it,
in
other
words,
I,
was
trying
to
basically
make
it
to
your
point.
It's
like.
Well,
you
need
to
interact
with
something
else
for
different
process
types.
Don't
don't
try
to
spawn
those
or
don't
try
to
have
multiple
you're,
just
you're,
interacting
with
others
different
types
right
right
through
the
Microsoft
microservice
API.
So
that's
fine.
F
F
Let's
see
where
is
it
Ian
and
the
ticket
for
this
book
asks
if
it's
okay
to
spawn
the
IP
Command?
Yes,
yes,
yes,
this
is
just
saying
that,
yes,
you
can
spawn
other
things,
but
we
don't
need
to
say
that
here.
F
No
I,
just
I
can
do
this.
Having
only
one
concern
means.
F
E
F
F
Right-
and
this
is
more
of
a
related-
so
there's
a
few
things
about
one
process
type
per
container
and
why
this
is
a
difficult
one
to
talk
about,
why
we
have
it
as
best
practice,
and
one
of
the
main
parts
has
to
do
with
it's
well.
This
is
a
microservice,
primarily
a
microservice
type
of
best
practice,
so
that
architecture,
patterns
and
stuff
that
you're
referring
to
Victor
and.
F
Print
one
concern
per
container:
this
is
a
principle,
so
this
isn't
just
a
micro
service.
You
can
actually
have
when
you
look.
This
is
why
there's
all
this
stuff
single
responsibility,
principle
and-
and
you
can
see-
here's
a
Erickson-
actually
refers
to
this,
except
only
necessary.
B
F
It's
talking
about
separation
of
concerns,
so
this
would
be
related
to
what
are
we
trying
to
do
with
one
process
or
type
or
or
one
category
type,
or
how
we're
trying
to
Define
that
there's
there's
overlap
between
different
practices
and
principles
here,
where
you
could
say
there
you're
not
going
to
fully
embrace
one
when
you're
trying
to
talk
about
it,
but
you
kind
of
have
to
talk
about
both
a
little
bit
so
right
here.
F
This
Ericsson
document,
our
white
paper
they're
talking
about
separation
of
concerns,
and
this
ends
up
being
part
of
like
functions
and
stuff,
and
why
they're
doing
that
and
there's
some
other
links
that
point
to
other?
F
How
do
you
br?
How
do
you
break
down
the
different
functions
into
smaller
components
and
I
think
you're,
saying
stuff
with
a
lot
of
different
places,
but
this
is
the
back
to
the
concern
stuff
like
the
single
responsibility
principle
and
stuff
like
that,
I,
don't
know
that
we
need
to
talk
about
the
summary
it
could
be
somewhere
else.
C
D
C
F
B
F
B
Is
is
just
talking
about
the
same,
like
I
mean,
maybe
you
can
use
in
the
description
or
another
section,
just
expand
idea.
I
mean
at
least
this.
The
summaries.
C
F
With
this
is
about
the
privileged
containers,
but
we
actually
point
out
some
specific
areas
in
the
CIS
Benchmark,
where
we're
talking
about
it,
we
can
do
that
sort
of
thing
with
something
like
this
I
do
think
that
it's,
this
sort
of
thing
will
come
up
like.
Why
are
you
saying
this
is
important?
You
know,
and
then
we,
you
know
we
have
the
references.
F
This
is
an
external
party
that
are
talking
about
why
this
is
a
best
practice,
so
this
is
maybe
more
relevant
to
this
particular
practice.
So
this
is
Docker
talking
about
containers
and
there-
and
this
is
not
specifically
same
process
type,
but
they
are
saying
different
concerns,
and
this
is
a
specific
and
what
the
patchy
right
and
and
then
saying,
don't
put
other
things
in
there.
Yeah
multiple
processes
are
fine,
so
that
points
out
something
that
other
folks
like
Ian
had
pointed
out.
Can
we
run
what?
If
what
about
applications
that
do
multi-process
types?
F
Yes,
but
you
should
avoid
different
responsibilities,
so
you
don't
want
to
run
your
database,
but
you
know
as
a
guideline.
You
don't
want
to
run
your
database
and
your
proxy
and
a
bunch
of
different
things.
All
in
one
container.
You
want
to
split
those
out
and
that's
what
this
is
talking
about,
but
maybe
do
you
all
think
this
should
go
into
where?
Where
should
this
go
and
it
sounded
like
y'all
both
think
it's
redundant
here,
it
doesn't
need
to
be.
In
summary,
are
you
thinking
reference
or
somewhere
else.
F
Well,
motivation,
yes,
but
motivation
really
is
talking
about
this
doesn't
say
what
the
benefits.
F
C
I
I,
my
suggestion
is,
leave
it
for
now
and
then
I
mean
I.
I
said:
leave
it
because
I
think
it
work
it
very.
It's
a
nice
motivator
for
that
first
paragraph,
right,
I
mean
it
basically
to
your
point.
It
makes
an
external
reference.
You
know
this
is
just
not
coming
up
anywhere
and
it
kind
of
explicitly
points
to
one
example.
That
is,
you
know,
has
strong
relation.
You
know
correlation
to
what
we've
just
said
and
I.
We
can
always
have
it
in
the
reference
section
again
at
the
bottom.
C
C
Having
one
concern
means:
there's
only
one
process:
category
process
type
within
one
container:
there
can
be
any
number
yeah,
but
it's
kind
of
reiterating
it
again
Within
example
and
then
that's
good
and
then
I
think
for
me,
I'm
I'm,
comfortable
with
this
summary
I,
think
you've
gotten
across
what
it's
about
now.
I'm
naturally
inclined
to
say
so.
C
Why
do
I
want
to
do
this,
and
then
this
is
where
you
know:
I
took
from
the
article
that
we
had
already
referenced
before
to
some
of
these
benefits
and
I
put
that
in
there
more
or
less
just
putting
within
a
leading
line,
saying
the
best
practice
benefits
a
CNF
consumer
operator
in
the
following
ways,
and
then
you
probably
needs
an
extra
space
in
there.
I
don't
know
if
that's
a
page
break
but
then
I
just
you
know
copied
them
in
and
I'm,
not
sure.
D
F
Can
we
what
about
this
one
right
here
in
the
summary,
this
is
kind
of
a
duplicate
of
the
Apache,
so
this
is
thing
in
Gen
X
instead
and
which
is
and
just
another
web
server.
So
I
don't
see
a
reason
to
have
this
since
it's
a
duplicate
and
then
this
is
maybe
an
explanation
of
the
process
type
having
only
which
could
maybe
be
merged
with
the
top
part.
But
first
let
me
say
this:
can
we
delete
this
part,
which
is
a
duplicate
of
the
Apache
right
above
yeah?
F
C
And
seeing
it
this
way,
what
I
would
actually
think
is
that
because,
if
you
recall,
we've
had
different
names,
we've
called
this
a
single
process,
single
process,
category
type
concern,
and
maybe
that's
where
we
should
need
to
start.
Maybe
it's
as
a
CNF
Microsoft
should
only
have
shall
have
only
one.
C
F
A
F
First
say
having
only
one
process
type
so
now
we
go
having
only
process
type.
F
I
want
to
go
back
to
maybe
the
warning
single.
So
that's
something
about
the
is
related
to
the
single
concern
principle.
There's
something
there
but
I'm.
Not
quite
it's
not
fitting.
For
me.
B
Sorry
I
have
to
go
to
another
meeting,
so
I
have
to
draw,
can
I
just
check
it
later,
like
absolutely.
C
One
way
what
if
you
did
it
like
it
almost
feels
like
that
almost
could
be.
C
C
C
A
E
C
C
C
F
All
right,
so
that
looks
pretty
good
I.
Think
we're
done
with
summary.
I
don't
want
to
just
keep
pushing
on
this
other
than
I
want
to
go
back
to
what
you
said.
You
were
trying
to
say
about
the
best
practice.
The
motivation
section
so
I
think
you
were
talking
about
this.
So
it
looks
like
you
wrote
this.
C
Is
from
the
article
that
I
believe
it
was
Watson
who
wrote
an
article
okay.
F
So
you've
kind
of
taken
some
pieces
out
of
there.
C
Yeah
I
mean
it
seems
so
well
outlined
to
you
know.
Why
do
you
want
to
do
this?
It
was
you
know,
then
it's
a
question
whether
we
agree
with
that.
All
of
this
is
you
know
the
case.
I
really
did
just
copied
and
pasted
over
so
that
we'd
have
a
because
it
felt
like
when
I
was
looking
at
the
different
references.
C
This
one
came
to
mind.
Of
course
we
refer,
you
know,
we've
talked
about
it
in
the
past.
C
Go,
can
you
just
add
an
extra
space
right
after
that
first
colon,
because
it
the
isolation,
comes
right
after
the
first
one
is
isolation.
You
see
it.
It
should
have
a
space
in
between
it
or
something
yeah.
E
D
C
And
I
think
you
know,
maybe
that
we
do
this
is
the
next
step
is
just
going
to
walk
through
Okay,
so
we've
got,
we've
got
a
summary.
This
is
why
this
or
this
is
a
summary.
What
it
is
this
is
the
motivations
is
there
is:
are
these
the
right
ones?
Is
there
something
else?
I
I,
admittedly
had
a
challenge
when
I
read
this
and
I
go
okay,
so
the
CNF
can.
This
is
a
best
practices
benefiting
the
CNF
consumer
and
operator.
C
That
makes
sense,
probably
can
benefit
even
the
vendors
themselves,
but
you
know
who's
most
important
is
the
end
user.
So
leave
it
like
that.
It
makes
sense
to
me
yeah,
we
might,
there
might
be
some
fine
tuning,
but
I
think
it
starts
with
this.
C
A
F
A
F
So
we're
done
with
motivation,
we're
done
with
I'm.
Sorry
we're
done.
With
summary.
We
have
a
start
on
motivation.
Let
me
glance
through
it.
F
No,
what
do
you
mean
it's
no,
for
this
section,
yeah
I
mean
it's
just
it
kind
of
covers
it.
Anything
else
needs
to
be.
We
get
feedback
from
other
people
or
in
the
pr
we
get
feedback
or
someone
comes
and
says
hey.
Why
don't
we
add
this
and
we
do
a
new
new
pull
request,
because
we
can
always
update
they're
not
and.
C
F
So
that
section's
good
this
one,
we
need
to
do
something.
Paragraphs.
F
A
A
F
All
right,
so
that
one
needs
to
be
just
reiterated
and
expanded
on
maybe
a
little
bit
I
think
the
best
specific
containers.
This
part
can
be
deleted.
F
A
C
F
Oh,
what
like
this
no.
A
F
That's
how
I
was
using
italics
yeah
all
right.
This
is
pointing
at
the
same
place,
but
all.
E
F
E
E
F
A
F
We're
not
really
doing
enhancement
proposal,
we're
more
doing
like
a
write-up
of
a
best
practice
like
12
factors
and
other
places
like
that
documentation,
yeah,
but
since
this
relates
to
the
ability
to
do
testing
and
people,
saying,
I
would
like
to
try
to
use
that.
That's
why
we're
tying
these
are
together,
so
that
we
can
support
each
other.
It
can
work
independently
and
someone
doesn't
have
to
use
the
test
suite
at
all.
F
They
could
just
if
we,
if
we
actually
do
what
you
were
talking
about
earlier
in
the
call
just
having
something
a
completed
and
and
something
available
where
people
are.
The
idea
is
to
put
something
out
there,
that's
useful.
So
if
we
have
a
publicized
list
of
best
practices
and
then
the
content
behind
it,
that
can
become
a
resource
for
developers
to
use,
even
if
they
never
touched
a
test
Suite,
because
this
works
independently.
You
can
go
through
all
this
and
we
can
go
yeah.
F
We
want
to
do
this
yeah
and-
and
you
don't
you
wouldn't
even
a
lot
of
this-
would
be,
in
my
mind,
applicable
outside
of
kubernetes
and
not
in
any
container
environment
and
probably
in
just
a
virtualized
environment
VM
for
a
lot
of
these
things,
so
I'm
hoping
it'll
be
beneficial
in
those
sort
of
ways
all
right.
So
this
is
not
good
goals
improve
the
security,
so
we
want
to
do
I'm
going
to
just
write
something
here:
I,
don't
just
to
kind
of
kick
start
it
and
then
delete
the
rest.
E
F
Cnfs,
so
something
about
that
so
like
if,
if
you're
not
doing
this,
then
you're
fighting
kubernetes.
So
that's
part
of
this
you're
being
inefficient.
You
don't
have
to
use
kubernetes,
you
could
go
Slimmer
and
Slimmer
and
then
try
to
go
I'm
going
with
Docker,
not
swarm
or
any
other
environment.
I'm
just
gonna
go
as
minimal
or
you
go
down
even
below
that
because
Docker
is,
and
all
of
these
are
just
using
like
container
day
I
can
use
container
day
and
and
do
my
own
orchestration
yeah.
F
Right
this
reduce.
F
Risk
of
run.
A
C
A
F
C
C
F
So
this
one's
easier
to
see
so
this
best
practice
we're
not
TR
in
the
security
one
we're
not
trying
to
handle
fine-grained
access
or
deny
all
access
to
the
host.
It
was
a
one,
limited
area
to
try
to
reduce
security
issues,
that's
it
but
not
trying
to
handle
all
of
the
different
security
items
on
that.
So
yeah,
that's!
You
could
almost
say
this
is
like
a
summary
of
the
motivation
so
that
the
motivation
here
is
kind
of
okay,
the
higher
it
gets
into
higher
level
as
well,
but.
F
Higher
level
or
detailed,
so
some
of
the
motivations
that
we've
done
are
talk
about
business
motivations.
F
But
anyways
the
goals
are
kind
of
a
summary,
but
the
main
thing
I
think,
is
to
separate
what
is
in
scope
versus
out
of
scope.
A
E
F
F
F
C
A
F
So
they're
not
going
to
find
it
here
right.
We
may
write
it
up
somewhere
else,
but
not
here.
Does
this
make
sense?
It
does
all
right
all
right,
I'm,
just
I'm
not
going
to
delete
this,
but
I'm
going
to
mark
it.
I've
done
this
in
other
ones.
I
stopped
doing
it
here
because
it
it
gets
old,
but
I'll
just
do
it
like
it
doesn't
really
matter
what
color
it
is,
oh
other
than
it's
so
hideous
that
we
can't.
E
D
F
F
F
F
Sometimes
we
said
this
is
not
relevant
to
system,
or
this
is
only
for
system
pod
types
system,
pod
types
of
be
those
that
are
run
by
the
Main
kubernetes,
namespace
and
group
it.
It
runs
them
like
services
like
the
cube
proxy
and
sometimes
people
will
write
something.
It
may
be
an
operator
or
container
that's
running
in
that
type
of
space
and
it
needs
additional
Privileges
and
other
things.
F
So
that's
why
we
need
to
say
this
I'm
sure,
as
things
are
expanding
on
and
we're
thinking
about,
also
the
workload
in
reference
to
Telecom
type
workloads
and
we
may
think
user
plane.
A
E
F
C
You,
if
we
do
this
on
the
next
Monday
meeting
or
because
I
I,
don't
know
how
this
works
when
you're.
If,
if
we
are,
let's
say
we
are
10,
people
I
mean,
maybe
that
you
know
maybe
it
still
works.
I
found
this
I
found
this
useful,
especially
you
know
when
we're
a
couple
of
us,
obviously
different
ideas.
Different
frame
of
reference
help
us
pull
together.
F
Yeah
I
think
we
can,
if
we
don't
get
to
working
on
this
before
Monday
I,
think
we
should
be
able
to
knock
out
the
last
Parts
this
next
Monday.
If
not,
nothing
else
comes
up
as
a
higher
priority
and
and
then
we
can
put
in
a
pull
request.
That's
great
at
that
point.
We
tag
as
many
people
as
we
can
try
to
get
some
reviews
make
any
other
updates
and
then
get
it
put
in
place,
and
then
we
can
move
on
to
the
next.
One
sounds
great.