[WIP]bump gateway_api_version to v1.2.0

[KubeKyrie]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Support Gateway API upgrade to v1.2.0
See https://gateway-api.sigs.k8s.io/guides/?h=crds#v12-upgrade-notes
Which issue(s) this PR fixes:

Fixes #11630

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Bump Gateway API to v1.2.0

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: KubeKyrie
Once this PR has been reviewed and has the lgtm label, please assign ant31 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @KubeKyrie. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tico88612]

/remove-kind flake
/kind feature

[tico88612]

I wrote this code at the beginning, only change this is useless, in order to support offline installation, I finally did not use to this variable (PR #11376), I hope that the version can be differentiated by folder.

[KubeKyrie]

Thanks for reminding.

1. I do not understand how the support of offline installation affects this variable.
2. And how should I do to upgrade gateway_api. Should v1.1.0 be retained after updating?

[tico88612]

You can refer #11376.
My imagination is that you could put the original Gateway API CRDs in the v1.1.0 folder, and you create a separate v1.2.0 folder for the new version, and then you could use the gateway_api_version.

[KubeKyrie]

IMO, difference gateway-api version by folder is not very good for scaling. We can't add a directory for every version because the list will be very long after later versions.

[tico88612]

Because Gateway API release cycle is not very frequent, reserve 3 patch version I think it's appropriate.
If you have a better idea, you can suggest in a comment.

[yankay]

/ok-to-test