Beta resources: Setting storage version to v1beta1, not serving v1alpha2

[robscott]

What type of PR is this?
/kind cleanup
/kind deprecation

What this PR does / why we need it:
This affects resources that graduated to v1beta1 in the v0.5.0 release.
Although that specific change is relatively small, it required a lot of
related work:

• Restructuring examples to remove v1alpha2 examples where they were no
  longer useful and their installation would fail
• Updating conformance tests to use v1beta1 where possible
• Some related fixes to v1alpha2 blog post to account for removal of
  v1alpha2 example

This is closely related to #1347

Does this PR introduce a user-facing change?:

GatewayClass, Gateway, and HTTPRoute are now only supported with the v1beta1 version of the API. The v1alpha2 API versions of these resources will be fully removed in a future release.

[robscott]

This is a big change. Adding a hold for consensus.

/hold

[youngnick]

Wow, this was a surprisingly big one. Most of the changes are pretty straightforward renames, but this probably needs someone to do another visual check through the docs and make sure they make sense (I am going a bit crosseyed).

/lgtm

[youngnick]

Ooh, this is a good catch.

[markmc]

"Temporary workaround for release" sounds like something that should just be removed? If it's needed permanently, maybe we need to update the comment?

[robscott]

I think you're right, this probably shouldn't exist at all. There was a time where we wanted the manifests installed from the main branch to be at least somewhat useful and refer to the latest released image instead of the latest image build from the main branch. All of our installation instructions clearly refer to a versioned release so this is likely entirely unnecessary, will revert this change altogether.

[robscott]

Actually as I was digging into this more, it looks more complicated than initially expected and I don't want to expand this PR any further. I've created #1366 to track this and added it to the v0.6.0 milestone.

[markmc]

This needs updating in admission_webhook.yaml doesn't it?

webhooks:
  - name: validate.gateway.networking.k8s.io
    matchPolicy: Equivalent
    rules:
      - operations: [ "CREATE" , "UPDATE" ]
        apiGroups: [ "gateway.networking.k8s.io" ]
        apiVersions: [ "v1alpha2" ]
        resources: [ "gateways", "gatewayclasses", "httproutes" ]

[robscott]

Good catch @markmc! Should be fixed by #1365

[markmc]

/lgtm

[shaneutt]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: robscott, shaneutt

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [robscott,shaneutt]

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

[robscott]

Fixes #1372

/hold cancel

[robscott]

Missed updating one conformance test to use v1beta1, PTAL.

[youngnick]

/lgtm