deps: bump k8s-openapi from 0.27.1 to 0.28.0

[dependabot]

Bumps k8s-openapi from 0.27.1 to 0.28.0.

Release notes

Sourced from k8s-openapi's releases.

v0.28.0

k8s-openapi

• BREAKING CHANGE: Added support for Kubernetes 1.36 under the v1_36 feature.

• BREAKING CHANGE: Dropped support for Kubernetes 1.31.

• FEATURE: schemars v0.8 support has been restored under the schemars08 feature flag. This can be enabled independently of the existing schemars feature that enables schemars v1 support.

• FEATURE: StatefulSetSpec::volume_claim_templates field now uses a map merge strategy using its .metadata.name as the key.

Corresponding Kubernetes API server versions:

• v1.32.13
• v1.33.13
• v1.34.9
• v1.35.6
• v1.36.2

k8s-openapi-codegen-common

• FEATURE: schemars v0.8 support has been restored via a new parameter to fn run().

k8s-openapi-derive

• FEATURE: schemars v0.8 support has been restored via a new #[custom_resource_definition(generate_schema08)] attr.

Changelog

Sourced from k8s-openapi's changelog.

v0.28.0 (2026-06-14)

k8s-openapi

• BREAKING CHANGE: Added support for Kubernetes 1.36 under the v1_36 feature.

• BREAKING CHANGE: Dropped support for Kubernetes 1.31.

• FEATURE: schemars v0.8 support has been restored under the schemars08 feature flag. This can be enabled independently of the existing schemars feature that enables schemars v1 support.

• FEATURE: StatefulSetSpec::volume_claim_templates field now uses a map merge strategy using its .metadata.name as the key.

Corresponding Kubernetes API server versions:

• v1.32.13
• v1.33.13
• v1.34.9
• v1.35.6
• v1.36.2

k8s-openapi-codegen-common

• FEATURE: schemars v0.8 support has been restored via a new parameter to fn run().

k8s-openapi-derive

• FEATURE: schemars v0.8 support has been restored via a new #[custom_resource_definition(generate_schema08)] attr.

---

Commits

• b2c839b v0.28.0
• ebea539 Update to v1.33.13, v1.34.9, v1.35.6, v1.36.2
• b7acde4 Restore schemars 0.8 support.
• 366b480 Update kind to v0.32.0
• f1b5881 Update to v1.33.12, v1.34.8, v1.35.5, v1.36.1
• 8a891b9 Add v1.36 and drop v1.31
• bcd3499 Fix StatefulSet::volumeClaimTemplates to deep merge by name.
• 654a839 Update to v1.33.11, v1.34.7, v1.35.4
• eda35ab Update to v1.33.10, v1.34.6, v1.35.3
• See full diff in compare view

[raffaelschneider]

Blocked on upstream gateway-api-rs — holding for now.

This bump can't merge in isolation. The dependency cluster is coupled:

• kube 4.0 hard-requires k8s-openapi 0.28.
• But gateway-api (our pinned git dep) — including its latest release v0.21.0 and current main — still pins kube 3.1 + k8s-openapi 0.27.

Result: the tree ends up with two copies of each crate, and the k8s-openapi 0.27 copy pulled transitively by gateway-api panics at build time:

error: failed to run custom build command for `k8s-openapi v0.27.1`
  None of the v1_* features are enabled on the k8s-openapi crate.

(Reproduced locally with kube = "4.0" + k8s-openapi = "0.28".)

The upstream migration is not done yet — it lives in two unmerged dependabot PRs on gateway-api-rs:

• chore(deps): bump kube from 3.1.0 to 4.0.0 kube-rs/gateway-api-rs#238 (kube 4)
• chore(deps): bump k8s-openapi from 0.27.1 to 0.28.0 kube-rs/gateway-api-rs#237 (k8s-openapi 0.28)

There is no gateway-api revision with both changes. Once upstream lands those together and cuts a release, we can bump kube, k8s-openapi, and gateway-api in one coordinated change (and update the k8s-openapi feature flag in crates/gateway/Cargo.toml). Holding this PR open until then.