►
From YouTube: Gateway API GAMMA Meeting for 20230404
Description
Gateway API GAMMA Meeting for 20230404
A
B
So
if
that's
how
you
want
to
discuss,
please
feel
free
to
add
your
topic
to
the
instruction
all
right.
Just
to
briefly
recap.
What
we
went
over
last
week:
Rob
shared
a
doc
on
the
goals
for
giveaway
API,
ga
prioritization,
which
basically
means
trying
to
get
Gateway,
API,
stable
and
to
I
believe
a
1.0.
Officially,
it's
applied
by
GA
and
basically
prioritizing
that
work
and
the
associated
light
work
and
supporting
things
to
make
that
happen.
B
B
B
F
One
thing
I
will
say
now
that
we
have
a
list
of
tests
that
we
want
and
a
couple
examples
of
tests,
it's
very
easy
to
go
short
out
the
list
and
have
people
contribute
if
you're
interested,
especially
I,
think
it's
a
fairly
good
low
hanging
fruit
for
a
newer
contributor,
I
was
trying
to
ramp
up.
We
should
probably
create
an
issue
that
has
like
a
check
box
for
each
of
the
cases,
and
people
can
maybe
claim
them
or
something.
G
Yeah
I
I,
don't
know
why
this
hadn't
thought
hadn't
come
to
me
yet,
but
are
we
planning
on
separating
mesh
conformance
tests
into
like
conformance
slash,
mesh
or
some
kind
of
sub
directory?
So
it's
you
can
have
mesh
specific,
reviewers
or
or
something
like
that.
I,
don't
know
if
that's
over
optimization
just
thinking
before
we
add
too
many.
We.
F
F
B
B
B
C
B
A
A
E
A
E
C
A
F
F
F
A
Yeah,
so
it
I
don't
need
to
take
up
too
much
time
and
it's
totally
cool,
if
you
think
of
something
that
you'd
kind
of
like
me
to
highlight.
Please
PM
me
on
slack.
Otherwise,
a
big
part
of
it's
probably
just
going
to
be
introducing
gamma,
because
that's
the
kind
of
audience
for
that
kind
of
thing,
but
thanks
yeah.
B
Cool
yeah
that
makes
sense
to
me
definitely
like
high
level
overview
of
just
like
yeah,
covering
the
scope,
drawing
up
interest
and
hopefully
try
having
more
engagement
with
us.
It'll,
be
good
to
start
hearing
from
like
users
that
are
interested
to
implement
to
this
and
what
they
want
to
be
able
to
do
with
it.
C
So
everybody
should
be
able
to
comment
on
that
doc.
Now
I
apologize
when
I
added
it
originally,
nobody
could
see
it,
except
probably
like
when
Mike
and
I
were
talking
about
or
as
Mike
and
I
have
been
talking
about,
the
interaction
between
the
Gateway
API
and
as
for
north
south
and
the
Gateway
API
for
gamma.
C
This
is
that
document.
Most
of
that
is
text
that
I
wrote
quickly,
without
necessarily
thinking
terribly
carefully,
to
make
sure
that
everything
was
getting
covered.
It
would
be
truly
lovely
if
y'all
have
the
opportunity
to
go
through
and
toss
in
things
that
you
think
would
be
important
to
users
of
gamma
or
things
that
you
want
to
make
sure
don't
get
missed,
as
we
think
about
how
to
fix
some
of
the
problems
we've
been
coming
up
with
and
yeah.
That's
about
it.
Unless
there
are
any
any
questions
there.
B
C
Actually
one
other
note
there:
can
you
flip
back
to
that
user
stories,
Dock
and
scroll
to
the
top,
so
you'll
note
the
names
there
Jane,
Julian
and
Jasmine,
where
there's
a
fair
amount
of
overlap
between
those
roles
and
the
Gateway
API
roles,
I've
deliberately
written
them.
That
way,
because
I
want
to
be
thinking
about
specific
user
personas.
B
C
And
I
feel
like
a
fair
amount
of
this
mostly
reflects
my
personal
bias.
I
tend
to
have
spent
my
time
in
the
cloud
native
World
thinking
about
things
from
the
application
developer's
point
of
view,
but
yeah
I
think
it's
going
to
be
very
interesting
too,
to
see
what
people
think
the
cluster
providers
of
the
world
need
to
worry
about.
H
E
H
If
you
only
cares
about
business
problems,
then
she
shouldn't
care
about
how
it
gets
implemented,
and
so
it's
having
her
say,
I
want
to
install
a
service
mesh
is
like
yeah,
yeah
and
so
and
so
and
the
reason
I
say
that
is
it's
to
some
extent.
It's
analogous
to
to
a
person
wanting
to
do
electrical
work
on
their
house.
Right,
like
you
might
say,
I
want
the
Powerpoints
here
and
here,
but
you're
not
going
to
be
it's.
Not
it's
not
really
correct.
C
She
may
not
care
whether
an
Ingress
controller
or
service
mesh
is
doing
it.
Likewise,
she
probably
cares
a
great
deal
about
being
able
to
do
Progressive
delivery
again
without
necessarily
carrying
whether
it's
the
service
measure,
the
at
the
English
controller.
That
does
it
so
in
a
lot
of
ways.
This
to
me
is
why
I
think
it
would
be
good
to
write
down
some
of
these
stories,
because
it
should
should
be
a
way
that
we
can
go
through
and
start
nailing
down.
C
Some
things
like
yeah
all
right
so
does
Jane
really
need
to
go
and
muck
around
with
stuff
in
the
service
mesh.
If
she
wants
to
do
a
canary
deployment
of
something,
that's
four
levels
deep
in
the
call
graph,
maybe
she
doesn't
maybe
there's
another
way.
We
can
approach
that
problem
entirely,
that
we
can
still
explain
to
Jane
and
give
her
a
tool,
that's
useful,
without
requiring
her
to
suddenly
become
an
expert
in
all
things,
Gamma
or
all
things.
Gateway,
API.
C
No
I
think
yeah
and
I
think
that
I
think
that
your
point
about
I
think
your
point
about
whether
or
not
it's
fair
in
some
of
these
areas,
I
think
is
very
well
made.
I
think
that
it's
something
that
we
absolutely
need
to
keep
an
eye
on
as
to
whether
you
know
as
we
look
through
these,
we
probably
will
end
up
looking
over
some
of
these
and
going
you
know
what
this
is
out
of
scope.
We
don't
really
think
it's
fair
for
the
user
to
make
this
kind
of
demand
to
us,
but
we'll
see.
H
H
Like
the
names
it
doesn't
make
it
easy
to
talk
about
them.
I
think
that
she's
gonna
she's
gonna
care
the
most
about
like
things
like
resource
utilization
and
not
overloading
shares,
proxies
and,
and
things
like
that,
where
yeah
yeah
and
so
like
it's
one
of
those
things
where
you
maybe
Julian
might
do
the
actual
installation
of
the
service
mesh.
Maybe
but
to
be
honest,
I
would
say.
Probably
if.
C
B
Cool
it
feels
like
this
is
at
least
a
good
start
to
be
able
to
focus
on
the
roles
and
kind
of
like
jobs
to
be
done,
rather
than
trying
to
lead
with
API
design
first.
So
let's
I
think
this
is
a
great
place
to
like
capture
that
and
start
from
that
perspective,
to
make
sure
we're
like
addressing
the
needs
of
each
of
these
various
personas.
B
D
Due
to
the
the
way
we
do,
our
our
scheduling
so
housekeeping
thing,
I
figured
this
would
be
fairly
unanimous,
but
why
don't
you
just
make
everybody
get
votes
and
check
to
see
how
we're
all
doing
okay,
good
so
we'll
consider
gamma
canceled
for
for
that
week.
Just
so
folks
can
focus
on
their
coupon
predates
like
contrib
Summit
and
such.
B
G
Yeah,
if
I
can
figure
out
how
to
mute,
I
had
I've
got
a
few
things
on
the
agenda
back
to
back
here.
First
off
the
feature
freeze
on
Thursday:
this
is,
we
are
trying
to
get
070
out
the
door
as
soon
as
possible.
We
added
a
rough
estimated
timeline
for
070
as
part
of
the
Milestone,
but
the
high
level
thing
is,
if
you
have
a
feature
that
is
just
on
the
cusp
of
getting
in
now
is
the
time
you
know
in
the
next
two
days,
basically
to
get
it
in
yeah.
G
That's
all.
Realistically,
this
is
just
the
starting
point.
We
go
through
review
process
and
the
couple
release
candidates
and
we
probably
won't
have
a
final
release
out
till
the
end
of
the
month,
but
that
means
we're
not
accepting
major
changes
between
now
and
then
yeah.
That's
that's
all
in
the
feature.
Freeze
next
up,
I
just
want
to
throw
a
reminder
out
there.
Both
of
these
are
very
related
to
that
feature.
Freeze
things
that
I
am
personally
trying
to
get
in.
G
First
off
is
the
gap
that
I
presented
in
a
meeting
or
two
ago.
I
can't
remember,
but
about
the
interaction
between
multi-cluster
services
and
Gateway
API
I
think
we
have
some
approvals
now.
I
am
really
hoping
to
get
this
in
in
the
next
couple
of
days
before
that
feature,
freeze,
so
yeah
I,
think
I've
I
think
we're
close
here.
I've
got
a
couple
little
things
to
clean
up,
but
please
do
take
a
look
at
it
as
soon
as
you
can,
because
it
will
I've
got
a
hold
on
it
right
now.
G
G
G
G
B
B
E
B
C
B
B
G
No,
no,
it's
there's
never
been
anything
formal,
I
I
would
love
to
you
know,
especially
people
that
are
able
to
make
it
to
contribute
Summit.
That's
that's,
basically,
just
a
a
constantly
informal
Gathering
of
maintainers,
so
if
anyone
can
make
that
that's
the
best
bet,
but
beyond
that,
sometimes
Sig
Network
as
a
whole
has
done
kind
of
informal
lunches
where
we
coordinate
on
slack
and
say
or
mailing
lists
and
say,
let's
meet
here
at
this
time
and
do
lunch
together
open
to
more
ideas.
G
C
Was
less
than
ideal,
so
I'm
actually
not
going
to
be
there
on
Friday
afternoon
for
this
one
so
yeah,
which
may
prompt
some
people
to
decide
that
Friday
evening
is
the
right
time
to
meet
up
I,
don't
know
but
I,
don't
know
I,
it's
good
to
have
some
better
sense
of
what
my
kubecon
schedule
is
like
in
the
next
few
days.
So
maybe
I'll
be
able
to
suggest
something.
On
slack
too
the
trying
to
grab
people
for
lunch,
or
something
like
that
sounds
like
a
pretty
good
way
to
do
that.
G
E
E
B
H
I
think
we've
got
actually
got.
Two
we've
actually
got
two
cfps
in
I
submitted
one
that
is
a
there's
going
to
be.
There's
planned
to
be
a
update
of
like
here's.
The
things
that
other
people
who
are
working
in
kubernetes
might
find
interesting,
so
conformance
testing
policy
attachment
that
sort
of
thing
and
then
I
think
Shane.
You
submitted
one
as
well
right.
A
H
Yeah
I
mean
we'll
wait
and
see
what
the
what
the
contrib
summit
votes.
Let's
do,
but
I
mean
I
think
if
anyone
else
wants
to
submit
like
an
unconference.
You
know,
let's
talk
about
Gateway
API
session,
that's
probably
also
worth
doing
just
so
that
we've
got
some
options
there
to
talk
about
it.
Yeah
I
mean
I
submitted
the
cfp.
My
cfp,
because
I
thought
I
feel
like
the
last
time.
Rob
and
I
did
an
update
at
a
contributor
at
a
contribute.
Summit.
G
G
The
things
that
I'm
most
interested
in
talking
about
are
things
like
yeah
conformance,
like
Nick
mentioned,
and
also
reference
Grant
there's
been
some
efforts
to
Upstream
that
so
that's
really
the
kind
of
thing
that
benefits
from
in-person
discussions
with,
say:
goth
and
Sig
storage,
even
that
are
all
kind
of
involved
in
this
process,
and
it
is
surprisingly
hard
to
get
all
of
those
people
online
at
the
same
time.
But
if
we
all
happen
to
be
in
the
same
place,
that
could
be
helpful.
So
yeah.