►
From YouTube: Kubernetes SIG Apps 20190114
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
Welcome
to
the
January
14th
2019,
kubernetes,
sig
apps,
and
with
that
into
chat,
I'm
gonna
go
ahead
and
drop
in
a
link
to
the
agenda
where
you
can
follow
along.
We
have
a
handful
of
things
I'll
be
chairing
today.
My
name
is
Matt
Farina.
The
other
chair
should
be
here
as
he
can
and
Adnan
are
both
here
today
to
co-chair
the
we
don't
have
any
announcements
today,
normally
we'll
go
through
announcements,
demos
and
then
get
into
discussion
topics
this
week
we
don't
have
any
announcements
we
do
have.
A
B
Mike,
you
can
do
it.
Okay,
I
think
I
managed
to
do
it
so
hi
everyone,
my
name
is
Anna
and
today
I
want
to
talk
about
Commerce
and
just
present
it
to
the
sig,
and
my
plan
is
to
go.
Put
your
other
side
do
a
demo
and
then
open
it
to
questions
and
if
and
if
I
have
time,
I'll
talk
about
the
security
of
Hamas
and
so
commerce
is
a
secret
and
killing
the
encryption
solution.
B
That
will
be
there,
it's
a
lot
of
where
I
walk
and
we
build
it,
because
none
of
the
existing
solution
was
good
enough
for
us.
It
has
Native
communities
integration
and
we
also
build
something
that
will
make
it
seamless
for
the
pod,
you're,
probably
wondering
what
is
Hamas
so
I
guess
there's
no.
He
was
speaking
in
the
audience.
Hamas
is
the
world
in
hippo,
which
means
something
that
is
secret
or
hidden
a
pretty
relevant.
What
is
Hamas
handling
could
anything
hidden.
B
Let's
go
quickly
over
the
auto
of
Commerce
and
analytics
I
do
demo
so
commence
composed
from
two
components.
We
have
done:
crypto
API
and
the
crypto
LTI.
The
user
is
talking
with
them
crypto.
They
send
it
and
the
sensitive
data
that
she
want
to
encrypt
and
get
back
some
single.
It
is
encrypted,
and
this
encrypted
data
called,
if
you
can
put
on
github
or
whatever
Symantec
happened,
a
DC
have
to
take
had
to
get
to
the
pod
here,
runs
and
in
each
container
the
inner
content.
B
Now
the
shaped
the
the
encrypted
data
and
create
a
config
file
and
this
config
file
can
be
used
by
the
application,
normally
like
any
other
configuration
files.
If
someone
wants
to
ask
something
before
I
go
to
the
demo,
just
to
make
it
clear
would
and
so
for
the
purpose
of
the
demo
I
build
a
small
application
in
PHP,
which
is
not
working
right
now,
hey
just
second
I
would
have
done
it
too.
B
Well,
okay,
yeah,
so
I
have
a
mini,
feel
burning
on
my
Mac
and
now,
when
I
open
this,
we
can
see
the
example
up
in
PHP
yeah.
We
can
say
that
it's
spoken
because
the
file
with
the
secret
is
missing
it.
So
what
I'm
going
to
do
now
is
I'm
going
to
show
what
we
need
in
order
to
add
secret
provided
to
this
application
yeah.
So,
let's
look
for
minute
what
we
have
on
the
tractor:
I
have
the
five
pots
and
come
on
to
the
Kyoto
Commerce
in
Kyoto,
and
one
part
for
the
example.
Now.
B
What
interesting
about
the
most
is
that
income
or
swim
kept
secret
for
a
specific
application?
I
identify
an
application
by
its
service
account.
So
if
you
look
on
the
deployment
in
commerce
example,
this
is
the
deployment
responsible
to
this
pod.
We
can
see
that
it
has
a
service
account
mounted
now,
when
I
want
to
encrypt
something
for
this
application,
so
the
example
of
could
could
do
it.
I
need
to
take
the
service
account
and
I
need
to
now.
B
I
can
use
common
sense,
a
right
I'm,
going
to
run
it
on
the
cluster
using
a
cube,
City
11,
because
then
crypto
is
running
without
Angus.
In
this
the
plan
I
can't
provide
you
the
data,
for
example,
super
seeker
and
then
I
need
to
tell
it
which
service
account
need
to
be
able
to
decrypt
the
data.
So
in
this
case
it's
this
service
account
and
it's
running
in
the
different
namespace.
B
B
Now
this
will
start
running,
it's
got
the
pot,
so
it
takes
few
seconds
and
you
see
I
refused
to
walk
because
the
you
Allah
is
not
HTTP,
but
we
can
tell
the
CLI
I
know
what
I
am
doing.
Let
me
do
a
job
hey,
so
this
will
allow
me
to
use
insecure
URL,
and
now
this
will
interact
with
almost
5000
API,
and
now
we
got
an
encrypted
secret.
I
can
do
it,
take
this
encrypted
seeker
and
now
to
put
to
pass
it
to
my
application,
which
is
here:
I
can
put
it
in
a
container.
B
So,
for
example,
I
can
put
here
like
I,
don't
know
thanks
seeker
or
something
like
that.
This
is
the
configure.
A
and
here
I
have
the
deployment,
and
it
is
responsible
for
that
occasional
just
job
and
we
have
a
day
in
each
container.
Now,
once
I
am
I
uncomment
the
in
each
container
a
twist
out
owning
a
it
will
start,
look
for
the
pod.
They
kept
the
secret
and
mountain.
So
let's
see
how
it
work.
I
now
can
do
a
cure
city
Iraq
time
in
a
safe
door
and
just
cause
I,
didn't
say.
B
A
Okay,
well
I'll
fire
it
off
with
questions
here.
So
kubernetes
recently
introduced
the
ability
to
URL
there
to
back
secrets
with
a
key
management
service,
and
so
everything
is
stored
encrypted
using
your
key
management
service,
whether
it's
AWS
TMS
or
something
like
as
your
vault
there's
different
key
management
services
out
there
have
you
looked
at
the
difference
between
using
this
for
your
encrypted
details
versus
not
because
I
notice
you've
got
an
encrypted
string
here
in
a
config
map
rather
than
a
secret,
so
there
may
be
some
experience
thing
I'm
curious.
A
B
B
A
No,
no,
no,
the
kms
is
actually
using
a
key
management
service
to
encrypt
your
data
and
to
decrypt
your
data,
and
so
it's
not
at
CD
encryption
at
rest,
because
I
understand,
if
you
were
to
compromised
at
CD
and
get
access
to
it,
you
could
then
still
get
the
raw
data
out,
because
that's
a
non
at
rest
way
to
access
it.
I
was
actually
talking
about
using
a
key
management
service
in
order
to
encrypt
the
data,
as
it
sits
inside
of
that
CD
yeah.
B
A
B
B
More
than
that
and
come
on
so
the
health
problem
of
how
you
can
let
all
the
developers
ki
ticket
and
manage
their
applications
with
full
responsibility
and
what
Commons
give
us
that
other
solutions,
don't
is
an
easy
way
to
encode
these
tickets
and
consume
them.
If
we're
going
to
talk
about
a
country
ago,
a
community
secret,
it
has
a
one
big
change,
which
is
how
you
can
consume
this
ticket.
Unless
and
unless
you
want
to
consume
the
secret
using
a
variable,
which
is
this
option
and.
C
A
A
Failed
and
they
stoie
for
that.
No
that's!
Quite
all
right,
I
just
dropped
a
Lincoln
I
was
gonna
actually
be
curious,
then,
with
the
sealed
seekers,
because
this
sounds
similar
to
bitNami,
sealed
secrets
as
well,
but
different
I
I
understand
the
space,
no
you're,
absolutely
right.
If
you
want
to
check
things
in,
you
have
to
have
a
way.
Some
folks
have
used
things
like
shops
or
from
Mozilla
and
black
box
from
Stack
Exchange
in
this
space.
This
just
looks
to
be
a
little
bit
more
kubernetes
centric
way
of
doing
it.
Yeah.
B
B
B
B
So
what
I
was
saying
it's
more
I
will
go
again
to
this
side.
So
usually,
when
you're
working
with
with
tickets,
you
have
one
config
file,
you
do
base64
encoding
of
this
file
and
then
you
put
it
in
a
secret
manifest,
like
you,
have
one
key
with
this
base64
presentation
of
the
config
file.
This
is
a
common
approach
to
how
to
work
with
ticket
and
sensitive
data.
This
means
that
any
chance
you
need
to
do
in
this
file,
you
need
to
decrypt
the
entire
key
and
then
modify
the
things.
B
Thomas
walks
every
different
day
if
I
have
multiple
things.
I
can
just
have
multiple
kids
like
this
and
then
first
it's
one
where
in
kitchen
there
is
no
way
as
a
user
to
the
kit,
this
data
fo
both
cc-cat
and
hence
ticket,
and
require
you
to
be
able
to
decrypt
the
data
each
time
you
change
the
seeker.
So
here
you
don't
need
never
to
decrypt
it
and
you
can.
This
is
the
main
difference
from
other
solutions.
Does
that
answer
your
question?
Oh,
it.
A
B
I'm
going
to
present
this
deck,
it's
not
compacted
yet
I'm
going
to
present
it
next
week,
California
and
I
will
put
it
online.
There
is
a
blog
post
in
progress,
so
yes,
I
will
put.
The
I
will
put
this
likes.
The
slide
I
showed
here,
which
is
just
there
part
about
commas,
and
there
is
a
lot
more
start
here
about
the
secure
design
and
all
that
and
I
didn't
had
time
to
mention
that,
but
the
most
also
walk
with
am
expecting
quantity.
B
A
B
B
D
D
B
Because
of
how
come
was
well
and
and
because
I
think
we
did
pretty
good
encryption
mechanism,
I
actually
didn't
mind
if
the
config
map
will
be
on
the
order
nodes,
because
as
long
as
you
don't
have
the
appropriate
service
account
or
the
token
of
the
service
account.
You
can't
the
kit,
this
data
and
so
it's
kind
of
answer,
a
question
from
a
different
angel.
It's
not
a
perfect
a
mechanism,
I
know,
but
it's
dancing
in
the
way
and
that's
the
answer.
It.
F
B
D
We're
saying
is
you're
okay
with
the
contact
mapping
in
distributed
across
all
news
and
you're
using
the
service
token,
as
a
credential,
in
order
to
block
access
to
the
encrypted
value
of
the
secret.
So
they're
saying
that,
basically,
if
the
contact
map
is
shared,
it's
not
considered
to
be
a
seeker
in
and
of
itself,
and
users
have
to
be
careful
about
the
distribution
of
their
service
circles
to
ensure
that
there
is
no
agent
on
the
host
that
can
actually
get
a
service
to
look
into
decrepit
secret
if
they
were
able
to
get
access.
Yes,.
B
B
A
A
G
Hi
everyone,
my
name,
is
Clara
Lawrence
and
I'm.
The
enhancements
lead
for
the
114
release
and
I
wanted
to
hop
on
here
to
introduce
myself.
We
also
have
Aaron
on
who's
the
lead
for
the
114
release,
and
so
yeah
I
just
wanted
to
introduce
myself.
So
you
all
know
who
we
are
and
wanted
to
check
in
with
cig
apps
on
existing
enhancement
issues
or
any
new
enhancement
issues
that
y'all
were
hoping
to
get
tracked
for
the
114
release.
D
Is
cron
jobs
yeah,
but
we
don't
have
the
cap
open
for
that
yet
and
I
don't
know
if
we're
going.
We
haven't
decided
exactly
on
this
stability
of
what
we're
going
to
do
with
the
controller,
but
it
probably
won't
be
ap
I
think
that
would
be
the
one
thing
to
definitively
look
at
going
forward.
I
think
the
other
big
things
that
are
kind
of
going
around
are
the
side
for
our
proposal,
but
I
don't
think
that's
going
to
get
for
114.
A
E
A
G
A
A
So
this
may
or
may
not
be
something,
but
it
doesn't
sound
like
we're.
Gonna
have
much
for
114.
A
number
of
our
things
are
a
little
bit
longer
planning,
but
since
feature
freeze
is
at
the
end
of
the
month,
we'll
make
sure
we
have
any
caps
in
and
I
know.
Aaron
really
wants
caps
in
with
lots
of
details
on
them.
We
will
try
to
give
him
what
he
wants
for
anything.
We
do
in
114.
G
H
A
C
Implementable
would
be
my
suggestion
because
I
feel,
like
you,
have
a
whole
additional
four
weeks
of
coding
afterwards.
This
is
more
about
like
what
I
did
during
the
113
release
cycle
was
bring
it
all
of
the
enhancements,
slash
caps
to
sate
architecture
once
before
enhancement
phrase
and
once
before,
countries
to
get
a
sanity
check
on
whether
we
as
a
community
felt
like
yeah.
These
look
like
they've,
had
enough
planning
and
forethought
and
are
on
track
to
land
appropriately.
Some
of
these
things
are
difficult
to
know.
C
Four
weeks
into
the
release,
life
cycle
and
sakes
want
to
say
well
we're
just
gonna,
try
our
best
and
see
how
far
we
get
before
countries
I
think
that's
totally
fair.
We
just
do
want
to
see
some
due
diligence
done
in
the
cap,
so
we
understand
where
you're
planning
to
head
and
that
we
then
have
something
to
evaluate
against
when
we
come
up
to
code
freeze.
Does
that
make
sense.
H
It
does
to
me
it
does
yeah
and
one
other
question
follow-up
question,
and
you
said
that
the
cap
should
have
like
the
criteria
for
alpha
beta
and
that
sort
of
thing
like
how
solid
should
that
be
like,
because
probably
a
lot
of
that
criteria
will
be
discovered.
You
know
after
it's
released
and
as
you
get
feedback,
so
did
you
just
like
just
a
general
direction,
good
enough.
C
That's
a
really
great
question:
I
think
that's
something
I
hope
we
can
just
sort
of
iterate
on
as
a
as
a
member
of
the
release
team.
What
what
we
are
looking
for
is
a
checklist
as
much
as
possible,
so
that,
like
we
can
verify
that
the
check
boxes
have
been
checked
off,
not
necessarily
that
we,
the
release
team,
are
responsible
for
chasing
down
each
of
those
requirements.
C
D
It's
good
if
it's
going
through.
So
yes,
for
instance,
when
we
like
to
see
days
later,
have
a
graduation
criteria
in
the
cap.
We
need
to
say
apps.
Let
people
in
the
community
comment
on
their
graduation
right.
Iria.
The
cap
is
a
living
document,
so
we
don't
expect
that
the
graduation
criteria
will
necessarily
remain
the
same
throughout
the
lifecycle
of
the
feature
or
enhancement.
C
Yeah
that
sounds
fair
to
me.
I
think-
and
this
is
part
of
the
thing
that's
still
trying
to
be
worked
out
right,
like
I
would,
like
some
sake,
I'm
looking
to
say
to
architecture
or
some
entity
beyond
just
the
owning
sake,
for
capacity
of
oversight
to
sanity,
check
things,
a
situation
that
I
feel
like
we're
trying
to
adjust
for
here
is
in
113
life
cycle
or
the
113
release
cycle.
C
When
the
windows
sake
tried
to
bring
a
feature
to
GA,
and
there
were
concerns
raised
about
whether
or
not
the
feature
was
even
at
beta
yet-
and
there
were
also
concerns
that
say,
big
windows
felt,
like
gold
posts,
are
being
moved
on
them.
So
I
agree
with
Ken
that
this
is
caps
are,
are
a
living
document.
It's
not
like
these
things
are
set
in
stone.
There
definitely
should
be
some
room
for
iteration,
but
it's
about
getting
consensus
on
what
those
graduation
criteria
are
in
a
format.
C
H
C
Trying
to
capture
this
in
the
notes
so
I
appreciate
that
and
we're
all
collectively
discovering
the
formality
of
this
out
loud
as
we're
going
through
to
all
of
the
stakes
and
talking
about
this,
so
I
appreciate
your
patience
and
is
being
kind
of
it,
an
iterative
and
potentially
about
the
process,
as
we
figured
this
out.
But
that's
just
sort
of
where
we're
coming
from
and
and
part
of
Claire
and
myself
coming
to
the
six
is
to
just
give
you
all
a
heads
up,
Aaron.
H
C
C
A
C
A
Right
now,
no
I
was
just
gonna,
say,
I
think
the
same
thing
you
were.
We
don't
currently
have
anything
slated
for
114,
but
we
will
circle
back
to
see
if
there's
anything
we
weren't
aware
of
that
we'd
want
to
get
in
and
we'll
get
it
into
an
implementable
state
if
there
is
but
as
of
right
now
there
isn't
anything
sounds
good.
Other.
C
C
A
So
moving
on
somebody
dropped
in
an
issue.
It's
in
kubernetes
kubernetes
its
issue.
Seventy
two
thousand
five
hundred
and
ninety
three
there's
a
link
in
the
meeting
minutes.
I
haven't
actually
looked
through
this
in
detail.
It
is
about
replica,
set
controller
continuously,
creating
pods,
failing
due
to
assist
control
forbidden.
I
So
yeah
I
think
it
was
added
in
the
last
for
the
last
wedding,
but
then
due
to
lack
of
time,
I
think
it
got
rolled
over
to
this.
This
that's
correct,
so
so
yeah.
So
to
give
a
rough
idea
of
what
it
is
about
is
like
the
parts
that
have
cysts
in
the
power
security
policy
in
there
for
security
context,
cysts
ATL
set,
and
if
none
of
the
cluster.
If
now
the
nodes
in
the
cluster
have
any
white
listed
space
ATL
the
replica
set
keeps
creating
those
spots
and
kept
cubelet
gets
denying
those
spots.
I
So
so,
basically,
there
are
a
lot
of
queue
for
objects
that
that
keep
creating
and
and
then
it
isn't
covered
of
it.
So
so
yeah
like
I
mentioned
Jordan
to
that
I
would
like
to
work
on
it.
He
mentioned
that
I
can
put
it
in
signal
and
six
idling
as
well.
So
the
the
the
fix
that
I
have
come
up
with
is
like
changing
the
changing
the
admission
of
cubelet
process,
ETL
from
from
being.
H
J
F
J
Something
like
that,
I
think
in
general,
any
admission
that
Cuba
does
should
be
also
evaluated
by
the
scheduler
before
placing
the
boat
on
that
note,
because
that
was
one
of
the
reason
why
we
will
have
one
scheduler
and
they
will
know
about
notes
and
we
work
scheduled
by
dementia
and
scheduled
literature.
So
that's.
D
That
to
me
that
sounds
reasonable,
but
it
basically
is:
it's
gonna
push
another
conformance
criteria
on
the
default
scheduler
and
the
other
scheduler
implementation,
which,
as
far
as
I
know,
there
are
maybe
two
of
outside
of
the
default
scheduler
anyway
and
they're
special
case
schedulers.
What
and
I'm
about
if
we
give
sig
scheduling
and
and
probably
sig
note
as
well
agree
on
that
I
don't
begin
to
work
with
API
issue
and
I,
don't
think
it's
limited
to
replica
set.
D
What
I
wouldn't
want
to
do
is
try
to
implement
that
sensitivity
and
every
work,
blue
controller
and
also
propagate
that
concern
to
anyone
wants
to
implement
a
custom
controller
on
top
of
the
CRV
that
generates
positive,
well
right,
I'm,
going
to
let
every
single
person
who
writes
a
control
loop
that
orchestrates
a
workload
to
have
to
reason
about
just
control
settings
on
that
node
when
it
tends
to
do
placement.
So
it's
not
something
that
we
would
fix
and
replica
set
a
demon
said
staple
set
and
any
other
controller
that
uses
a
CRV
to
turn
up.
D
A
cluster
of
pods
like
Thomas,
said
I,
agree
that
you
can
fix
it
and
scheduler
and
it
would
happen
if
you
got
the
coordinate
cooler,
so
you
have
to
have
people
per
node
and
schedule
and
agree
that
promisee
suggestion
as
a
password.
It
sounds
reasonable
to
me.
There
might
be
some
security
considerations
about
that,
though
you
may,
it
might
not
be
okay
to
have
the
little
broadcast
globally
that
well,
but
it
would
only
be
the
interaction
between
the
node
in
the
scheduler,
but
for
the
node
is
safe
and
you
can
override
these.
J
A
All
right,
yeah,
thank
you.
The
next
topic
we
have
on
here
is
planning
for
deprecated
API
s
being
turned
off.
If
you
go
back
to
our
notes
from
November
5th
Jordan
Leggett
came
in
and
talked
about
having
a
path
towards
turning
off
accepting
the
app's
workload,
things
that
are
stable
for
their
beta
groups,
so
we've
got
things
like
apps
v,
1
beta
1,
apps,
V,
1,
beta
2,
and
no
longer
accepting
those.
He
had
a
proposed
timeline
in
there
and
that
was
back
in
November.
D
A
Api's
did
that
that
started
because
there
were,
there
was
no
cap
around
this.
As
far
as
we
could
tell,
and
we
didn't
realize
that
he
had
stopped
the
emission
I
remember
seeing
the
pull
request
which
I
didn't
review,
because
I
see
that
he
was
talking
about
pre,
announcing
and
113
and
114
and
proposing
did
not
serve
in
115.
But
if
we
can
no
longer
accept
things
that
means
it
was
brought
ahead
from
115
from
his
original
discussion
here.
D
D
J
D
Know
it's
none
I
know
it's
non-trivial
Chow
is
the
one
who's
been
taking
a
look
at
it.
I
should
sync
up
with
them
in
series
and
on
that
and
I,
don't
think
the
auto
upgrade
the
generic
auto
upgrade
is
functional
as
it
stands
right
now
anyway,
but
T
we
did
have
discussion
on
many
of
the
special
cases
and
having
handled
the
busy
fault
in
what
will
break.
D
F
A
We
need
to
start
communicating
this
more
broadly
to
and
know
when
it's
coming,
because
there
are,
if
you
start
going
in,
like
scouring
just
applications,
people
have
on
github
and
files
on
github.
You
actually
still
find
things
using
deployments
from
the
old
enhancements
space
even
before
the
apps
existed,
and
so
we
probably
need
to
make
it
very
clear
that
this
is
coming.
So
people
are
aware
ahead
of
time
that
this
is
going
to
break
them.
Even
though
beta
this
is
long
past.
A
A
D
They're
gone
they're
like
in
the
registry,
so
you
want
me
to
want
it
from
the
API
standpoint.
I
think
it
still
exists,
but
the
registry
is
still
using.
The
storage
format
for
the
registry
version
is
still
going
straight
to
be
one
I,
think
they're,
often
the
API
server
by
people
you
can
maybe
enable
them
not
by
default.
So.
A
D
A
D
A
So
that's
all
I'm
thinking
of
okay.
No,
that's
great!
Then.
The
last
thing
we
had
on
here.
Let
me
scroll
back
a
was
the
so
we
got
an
email
to
the
mailing
list
about
so
we've
been
having
this
iteration
going
between
one
week
as
workloads
and
another
week
is
developer
discussions
and
we
we
sort
of
had
that
distinction
and
the
reality
is,
is
the
developer
discussions
kind
of
died
off
it
turns
out?
A
We
were
not
having
the
the
structure
of
developer
conversations
that
folks
wanted
to
have,
and
so
we've
been
talking
about
lots
of
other
things
that
become
kind
of
a
mishmash,
including
on
workloads
weeks
having
demos
that
are
more
developer
focused,
and
so
there
was,
it
was
brought
to
the
mailing
list.
Let
me
see
if
I
can
find
it
about
that
distinction
and
how
we
can
handle
that,
let
me
go,
find
drop
the
Lincoln.
A
I'll
drop
it
into
chat
and
then
add
it
to
the
notes.
There's
a
conversation
in
chat
and
I
talked
about
that
the
end
of
the
year.
We
reached
a
compromise
to
separate
workloads
and
developer
tooling
discussions
to
bi-weekly,
and
this
is
about
if
we
need
to
put
a
demo
into
a
workload
meeting,
because
if
unused
time
or
press
time
and
another
meeting
to
just
how
does
that
go
with
the
the
workloads
discussions,
so
that
those
who.
D
So
I
think
maybe
one
thing
we
can
do
is
just
back
to.
If
we
like,
we
can
do
bi-weekly
a
workloads
upfront
and
if
we
haven't,
if
we
don't
have
any
issues,
you
give
that
time
back
and
do
it
treated
free
demos,
so
that
people
who
are
in
off
times
for
this
meeting
can
use
their
time
as
best
as
possible.
J
D
You
know
people
who
are
in
off
times
rooms
are
contributing
primarily
to
the
workloads
API
as
part
of
a
function
of
their
job,
but
aren't
super
interested
in
attending.
The
demos
need
to
be
able
to
attend
the
meeting
in
order
to
collaborate
and
I
I.
Don't
I've
heard
anyone
strongly
objected,
saying:
okay,
we'll
block
off
some
time
every
two
weeks
early
in
the
meeting,
so
they
can
come
discuss
what
he's
discussing
and
move
on
from
there.
A
Okay,
thank
you
for
bringing
up
that
concern,
we're
happy
to
try
and
make
things
smoother,
and
with
that
that
that's
all
we
had
for
the
plane
discussion
this
week.
We've
got
about
ten
minutes
left,
which
means
we
can
move
into
a
time
of
open
discussion.
If
somebody
had
something
they
wanted
to
talk
about
this
week,.
D
A
D
No
I
had
one
last
thing
pertain
to
last
week's
discussion
about
Ranjan,
so
we're
trying
to
still
get
it
cut
out.
I
engaged
Janet
has
some
thoughts
about
things
that
have
been
tried
on
the
job
and
she
wants
to
make
sure
that
all
the
rejected
in
the
design,
then
we
have
bonding
who's.
Does
the
gas
number
whose
internal
the
Google,
who
was
taking
a
little
bit
as
well,
will
probably
get
a
design
out
I
hope
to
get
one
out
this
week
and
then
engage
all
the
interested
parties
worsen,
contributing
and
moving
that
forward?.
A
Do
we
have
anything
else?
Any
we
got
eight
minutes,
you
can
have
it
back
or
any
open
discussion
topics
everyone's
own
twice
three
times.
Thank
you.
Everyone
for
a
nice
conversation
here
in
say,
gaps
this
week
and
again
we
will
talk
to
you
again
in
two
weeks
next
week
due
to
the
u.s.
holiday,
where
many
of
us
will
not
be
able
to
attend.
We
are
kids
today,
so
we'll
be
back
again
in
two
weeks,
thanks
everyone
and
see
online
or
then
bye.