Unable to install Experimental API CRDs

[mhkarimi1383]

What happened:

Unable to install Experimental CRDs

The CustomResourceDefinition "httproutes.gateway.networking.k8s.io" is invalid: metadata.annotations: Too long: may not be more than 262144 bytes

What you expected to happen:

Successful Installation

How to reproduce it (as minimally and precisely as possible):

 kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml 

Anything else we need to know?:

[rikatz]

@shaneutt @kflynn now this is reported, we may need to add it to release docs

@mhkarimi1383 for now, please try as kubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml

Thank you. We are aware of this issue and will use your report to add this known problem to release notes, and will work on future releases to also reduce the size of CRDs

[mhkarimi1383]

@rikatz

Thanks, Worked by the workaround

[kflynn]

We 100% need to release-note and document it. Also, for folks using the 1.34 kubectl, you can create $HOME/.kube/kuberc to make server-side apply the default:

apiVersion: kubectl.config.k8s.io/v1beta1
kind: Preference
defaults:
  # Default to server-side apply
  - command: apply
    options:
      - name: server-side
        default: "true"

That way kubectl apply will always be server-side, unless you explicitly use kubectl apply --server-side=false. This has working beautifully for me.

[rikatz]

I am looking at the release now, Shane added it to the top of it already:

Warning: Regarding the Experimental CRDs - please note that the experimental CRDs for this release are too large for a standard kubectl apply. You may receive an error like metadata.annotations: Too long: may not be more than 262144 bytes. To work around this please use kubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml. We're looking into ways to reduce the size for future releases to avoid this.

[shaneutt]

Thank you for reporting this, and thank you @rikatz and @kflynn for some help with workarounds.

I have updated the release notes with a warning about this.

We are considering some options to reduce the size (in particular, @rikatz is looking into reducing the documentation that gets emitted into the CRDs) for future releases. This can be the tracking issue.

/triage accepted
/lifecycle frozen

[rikatz]

/assign
I will assign this to myself so I can link it to the godoc reducing effort.

[danehans]

Can the workaround in #4156 (comment) be added to the install guide for both channels until this issue is fixed?