►
From YouTube: SIG-Kube-Proxy Bi-Weekly Meeting (APAC) for 20220608
Description
SIG-Kube-Proxy Bi-Weekly Meeting (APAC) for 20220608
A
Hi
everyone:
this
is
the
kpng
apec
meeting
working
group
meeting
under
sig
network.
This
is
8th
june
2022
and
this
meeting
falls
under
the
cncf
code
of
conduct.
So
please
be
nice
to
each
other,
okay,
so
on
the
agenda,
so
we
have
this
pr
to
discuss
from
yosh.
So
do
you
want
to
get
started?
Yash.
A
B
For
that,
like
I've,
created
a
document
and
also
a
script
that
will
generate
a
grpc,
but
in
the
pr
j
has
also
mentioned
like
we
need
to
verify
and
also
add
the
ci
jobs
which
I'm
not
aware
like
how
to
approach
congress
and-
and
also
michael
has
michael
has
like
mentioned,
the
link.
Sorry,
the
command,
which
can
basically
use
to
generate
the
proto
which
I
ran,
and
it
is
giving
me
this
error.
So
I'm
not
sure
like
whether
I'm
it
is
a
correct
way
or
maybe
you
can
help
us
in
this.
A
Okay,
so
I'm
at
least
not
well-versed
with
this
grpc
stuff,
but
what
I've
seen
is
there
is
this
mod
config,
which
also
has
some
grpc
stuff.
I
think
so.
This
will
run
it
for
all
dot
protofiles
and
there
is
a
make
target
for
it.
A
So
there
is
a
make
target
to
run
this,
but
we
are
not
running
it
in
ci,
so
I
maybe
a
good
start
would
be
to
understand
what
is
the
difference
between
this
and
what
you're
trying
to
add
in
the
pr
and
then
see
if
we
can
get
that
in
ci
as
well,
and
if
see
that
this
is
just
my
two
cents,
that's
that's
all
I
have
to
offer,
but
if
anyone
else
has
any
thoughts,
please
go
ahead.
C
C
B
B
C
C
C
B
A
So
I
think
this
is
basically
used
to
run
or
execute
commands,
and
things
like
that,
so
I
think
we
can.
We
should
be
able
to
run
this
command
as
well
and
then
just
check
if
that
works.
A
A
A
B
B
A
B
B
B
A
A
Dot,
proto
or
I
mean
with
the
file
command
or
try
to
use
the
mod
stuff.
The
mod
con.
B
A
C
A
One
more
question
I
have
is
like:
do
we
need?
Do
we
need
these
scripts?
If
we
have
the
make
target,
I
I'll
just
miss.
B
A
C
B
A
So
so,
from
what
I
understand
the
basic
stuff
is
that
once
you
once
you
run
this
protoc
command,
you
will
generate
a
bunch
of
files
and.
A
You
will
have
to
write
a
verify
file,
I
guess
or
verify
grpc
file.
So
there
is
no
verified
grpc
file.
A
C
A
Yeah,
so,
okay,
so
my
hunch
at
this
is
there
is
only
one
services:
dot,
pb
the
one
service
dot
product
file.
C
A
Okay,
so
if
you
go
to
api
local
v
net
one,
this
is
the
pb.go
file
which
exists,
and
we
make
changes
to
this
file
right
right.
A
A
Exactly
so,
if
you,
if
you
run,
if
you
run
this
or
if
you,
if
you
run
protoc
against
this
and
the
files
that
you
generate
through
this
right,
if
they
are
different,
then
there
has
to
be
an
issue.
The
job
should
fail.
A
C
Yeah
I
mean
you
could
have
your
output
directory
to
a
time
somewhere
in
your
ci
and
then
defeat
whatever
was
checked
in
right,
like
in
your
ci.
Your
runner
would
have
checked
out
your
repo,
so
with
that
with
what
you
generate
while
running
opposed
to
as
what
got
checked
out
yeah.
If
this
is,
if
we
have
only
services,
dot,
propose
pro
to
a
single
file,
then
a
single
div
should
work.
Just
a
diff
here.
A
Yep,
ideally,
this
should
be
done
for
all
dot,
proto
files,
and
it
should
be
done
in
a
way
like
you
know,
you
create
a
different
directory,
for
you,
know
all
the
generated
files
and
then
compare
them
with
wherever
those
pb.go
files
exist,
but
as
a
first
pass
yeah.
Maybe
we
can
go
with
like
just
the
visitors.proto
and
compare
the
generated
files
with
these
files,
as
amisha
mentioned
so.
C
B
A
You
don't
want
it
to
overwrite,
so
you
probably
want
to
create
a
new
directory
and
then
point
it
out
point
the
output
to
some
other
directory
or
you
can.
You
know,
change
the
output
file
names
to
something.
So
you
can
go
all
crazy
with
that
and,
like
you
know,
see
how
how
to
make
it
work.
But
basically
the
generated
files
should
be
checked
against
the
current
files,
and
the
idea
is
that
the
job
should
fail
and
if
the
job
fails,
we
should
create
an
issue,
and
you
know
make
sure
that
this
is
updated.
A
A
very
cool
thing,
maybe
that
once
the
job
fails
like
we
create
a
pr
that
a
new
pr
that
that
gets
raised
with
these
new
generated
files.
But
I
don't
know.
A
C
A
A
I.
I
think
it
can
be
like
a
simple
github
action
similar
to
the
ones
that
we
already
have,
and
so
things
like
you
know,
install
dependencies
can
have
all
of
your
code
from
that
check.
A
Yeah
one
good
thing
is:
if
you
once
you
fork
this
reaper
right
and
if
in
in
your
fork,
you
can
enable
kit
of
actions
and
try
it
out
in
your
fork
and
once
the
job
passes
in
your
fork,
you
can
raise
the
pr
or
basically
makes
like
you,
can
try
things
out
here
in
this
fork
of
yours.
A
You
should
see
a
settings
tab
and
be
able
to
in
basically
enable
github
actions
on
this
repo,
and
then
you
know,
try.
B
B
B
And
I
have
created
one
more
pr
for
unit
test
and
tables.
So
let's
just
have
a
look
around.
A
Oh
awesome
I'll,
probably
not
vivek,
to
take
a
look
at
this.
A
I'm
sure
this
is
all
yours.
If
you
want
to
review
it,
cop
assign
it
to
yourself,
like
whatever.
C
A
Apart
from
this,
this
there's
this
hack
md
running
on
on
what
are
the
next
steps
for
the
cap,
and
you
know
what
all
things
we
have
planned
so
so
just
just
wanted
to
highlight
that
as
well.
A
A
Yes,
so
so
the
idea
is
we,
we
already
have
this
cap
right.
I
don't
have
the
link
handy
now,
but
but
the
idea
is
to
like
revamp
the
cap
and
you
know
make
it
make
it
compliant
with
the
new
format,
and
you
know,
add
a
bunch
of
things
on
how
it
can
replace
q
proxy
and
things
like
that
and
then
once
the
cap
gets
merged,
then
we'll
actually
have
to
work
on
replacing
q
proxy
with
cupping.
What
is
the
policy
around
it?
A
How
to
go
about
it
which
release
this
will
get
it?
And
then
you
know
all
of
those
things
and
once
cupping
becomes
the
new
cube
proxy.
I
think
that's
that's
when
we'll
still
continue
with
this,
but
it
won't
be
a
working
group
as
such.
That's
my
understanding
about
it,
but
yeah.
If,
if
you
want
to
know
like
the
exact
details
and
things
like
that,
you
probably
should
follow
up
on
slack
like
maybe
ask
a
question
and
jay
or
mikhail
can
help
you
with
that.
A
Cool
so
yeah,
so
this
is
pretty
much
what
I
had.
I've
been
trying
to
work
on
the
cap,
but
I
I
didn't
get
to
spend
much
time
this
week,
but
I'm
planning
to
spend
some
more
time
on
it
like
later
this
week,
yeah.
So
if
y'all
have
any
other
things
to
discuss,
please
bring
them.
A
Awesome
so
I
think
the
very
first
step
I'm
looking
at
is
like
using
this
hack,
md
itself,
and
you
know
making
sure
we
yeah
we
get
started
with
all
of
these
like
new
format
and
things
like
that
and
then
work
our
way
through.
A
Do
we
have
anything
else
or
if,
if
we
don't,
then
then
we're
good.