Migrate to GWAPI for store-front routing

[hariscats]

Purpose

• Migrate from Istio-specific Gateway and VirtualService resources to the standardized Gateway API resources (Gateway and HTTPRoute). This aligns with the new stable Gateway API version and ensures consistency across environments.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Test the code

1. Deploy the updated Gateway and HTTPRoute configurations to the Kubernetes cluster.
2. Ensure the store-front service is running in the 'pets' namespace.
3. Verify that the Gateway is correctly listening on port 80 and handling HTTP requests.
4. Test HTTP requests to confirm they are routed to the store-front service as expected.

What to Check

Verify that the following are valid

• The Gateway is created successfully and is listening on port 80.
• HTTP requests to the Gateway are correctly routed to the store-front service.
• The HTTPRoute is correctly attached to the Gateway and matches all hostnames and paths.
• No errors or unexpected behavior occurs during routing.

Other Information

• Verify that the cluster has the appropriate permissions to manage Gateway and HTTPRoute resources.

[pauldotyu]

@hariscats sorry for the delay here and appreciate the contribution! I took a look at your manifest and wanted to confirm... You tested this against open-source Istio not the AKS managed Istio, right?

[hariscats]

That's correct, @pauldotyu, given the limitation below from the docs.

Gateway API for Istio ingress gateway or managing mesh traffic (GAMMA) are currently not yet supported with Istio addon. It's planned to allow customizations such as ingress static IP address configuration as part of the Gateway API implementation for the add-on in future.