Repository navigation
Description
What happened:
The install YAML manifests for v1.4.1 (and potentially earlier versions) contain explicit null values for .status.conditions and .status.storedVersions in the CustomResourceDefinition objects.
Example from gateway.networking.k8s.io_gateways.yaml:
gateway-api/config/crd/standard/gateway.networking.k8s.io_gateways.yaml
Lines 2248 to 2253 in 477d172
| status: | |
| acceptedNames: | |
| kind: "" | |
| plural: "" | |
| conditions: null | |
| storedVersions: null |
According to the Kubernetes API Reference (CRD v1), these fields cannot be null:
.status.conditions: Must be an array (or omitted)..status.storedVersions: Must be an string array (or omitted).
This causes CI/CD pipelines using strict validation tools like kubeconform to fail.
What you expected to happen:
Static manifest files intended for installation should ideally not contain a .status block at all.
If the block is present, the fields within it must adhere to the OpenAPI schema (i.e., be empty arrays rather than null).
How to reproduce it (as minimally and precisely as possible):
You can validate the release artifact against the official Kubernetes JSON schema using kubeconform:
$ curl -sL https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.1/standard-install.yaml | kubeconform -schema-location "https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/{{.NormalizedKubernetesVersion}}/{{.ResourceKind}}.json"
stdin - CustomResourceDefinition gatewayclasses.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/conditions': got null, want array - at '/status/storedVersions': got null, want array
stdin - CustomResourceDefinition backendtlspolicies.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/conditions': got null, want array - at '/status/storedVersions': got null, want array
stdin - CustomResourceDefinition referencegrants.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/conditions': got null, want array - at '/status/storedVersions': got null, want array
stdin - CustomResourceDefinition grpcroutes.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/storedVersions': got null, want array - at '/status/conditions': got null, want array
stdin - CustomResourceDefinition gateways.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/conditions': got null, want array - at '/status/storedVersions': got null, want array
stdin - CustomResourceDefinition httproutes.gateway.networking.k8s.io is invalid: problem validating schema. Check JSON formatting: jsonschema validation failed with 'https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/master/customresourcedefinition.json#' - at '/status': validation failed - at '/status/conditions': got null, want array - at '/status/storedVersions': got null, want arrayAnything else we need to know?:
Thanks π
Activity
jkleinlercher commentedon Feb 25, 2026
These null values breaks all kubeconform tests in GitOps pipelines, and I guess the fix would be rather easy?
youngnick commentedon Feb 25, 2026
These YAML files are all generated, so the fix will be to make the generator omit these fields correctly.
jkleinlercher commentedon Feb 25, 2026
I ask myself if the status fields in the CRDs are needed anyways. Havenβt seen them in other crds
MatteoFari commentedon Mar 24, 2026
/assign
test(conformance,chart): Gateway API v1.6 conformance parity β kubecoβ¦