Improve kubernetes.io docs with additional Gateway API pointers and information

[mlavacca]

What would you like to be added:

The official kubernetes.io docs contain a Gateway API section that can be improved in some ways to better advertise our project over Ingress API.

The following is a non-exhaustive list of parts that can be changed/added to gain more visibility on the main documentation:

• The Gateway API description can be expanded to make clear this is an alternative to the Ingress API and provides all the Ingress API features + many more.
• in the Gateway API page, make clear that users need a Gateway API implementation, similar to what Ingress requires, and provide our link to the Gateway API implementations.
• improve the migrating from ingress section, by directly adding links to ingress2gateway, advertising it as a useful tool to perform the migration. Be sure to list the tool's limitations, like the fact that not all the implementations are supported yet.
• improve the Gateway API page with a section on gwctl, explaining as it can be useful to inspect and manage user's Gateway API configuration.

[Nishant-k-sagar]

Hey @mlavacca I would like to work on this issue, I can update the information as per given details by simply adding required lines of code.

[mlavacca]

Hi @Nishant-k-sagar, we really appreciate your interest on this issue, but this is unfortunately not very suitable for a new contributor, as it needs a thorough knowledge of Gateway API and K8S docs. I invite you to look for something else marked as a good starting point for new contributors: good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. . For example, Rob has recently created a new CI-related issue that can be a great point to start gaining confidence with the project, if you want to take a look: #3282

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted