►
From YouTube: SIG Node Sidecar WG 2023-07-18
Description
Meeting notes and agenda: https://docs.google.com/document/d/1E1guvFJ5KBQIGcjCrQqFywU9_cBQHRtHvjuqcVbCXvU/edit#heading=h.m8xoiv5t6qma
GMT20230718-160229_Recording_1632x1020.mp4
A
A
Oh,
it's
nice
side,
car
signal
working
group.
This
is
2023
July
18th,
welcome
everybody.
Let's
go
through
the
Uber
issues
that
we
have
and
see
what's
left
with
sidecars,
so
we
enabled
Readiness
probes
and
such
this
and
the
life
cycle
hooks
as
well.
Yes,
it
was
too
supposed
to
be
working
now.
A
So
we
have
this
request:
it's
it
doesn't
independent
from
everything
else.
I'd
really
like
to
have
it,
because
it
will
simplify
lots
of
scenarios
but
yeah.
Let's,
let's
see
if
you
can
make
it
what
else?
A
A
A
I
think
today,
topology
manager
allocates
enough
CPUs
to
handle
everything,
so
they
probably
will
just
work
I,
just
not
sure
how
how.
A
And
then,
last
year,
blog
post,
yeah,
focused
I,
think
releasing
your
PIN
cover
body
release,
yeah
I
think
we're
in
a
good
shape.
A
Also,
a
big
question
for
beta
will
be
determination,
order
I
think
there
will
be
discussions
that
we
need
to
have.
So,
if
you
have
anybody
here
to
test
it
out,
lose
do
so.
C
No,
no
I,
don't
so
we're
a
topology
managers
and
we
will
not
make
any
patch
for
your
first
stage.
It.
A
A
Great
yeah:
let's
try
to
merge
this
one
total
request,
count
and
limitation
issue
and.
C
Then
and
I
found
that
the
the
resource
we
cut
from
tube
control
to
control
this
quiet
node
is
not
correct.
Is
it
fixed
by
your
PR
code.
B
If
you
click
yeah
click
mop,
you
order
that
I
told
resource
requests,
I
thought
I
had
it
in
the
out
there.
B
B
B
A
C
A
A
There
may
be
issues
if
it
wouldn't
locate
enough,
but
I
think
the
worst
case
scenario
is
that
CPU
sidecar
will
not
work
on
the
same
suicide.
That's
my
understanding
of
a
call.