Closed nightkr closed 2 months ago
I need to check if other operators than secret and listener are using h2 (probably not)
A lot of them will be pulling in h2, but they shouldn't have needed the patch to begin with.
Searched for [patch.crates-io]
in our github org, could not find any other h2 patches.
Closing this
Could you please add a comment here with a snippet that could go into the release notes? It should mention that this means 1.25 doesn't work anymore.
Sticking to our usual release notes:
This release supports the following Kubernetes versions:
These Kubernetes versions are no longer supported:
Okay, come release note time I'd include a sentence like this with an asterisk next to the versions we remove (OpenShift and Kubernetes):
"A change was merged (link to https://github.com/stackabletech/issues/issues/636) that breaks compatiblity with Kubernetes 1.25 and older. This includes OpenShift x.yz"
Ok, maybe something like
These Kubernetes versions are no longer supported:
Description
Currently, secret-operator and listener-operator use a forked version of the h2 crate due to https://github.com/hyperium/tonic/issues/243.
Kubernetes v1.26 has fixed the invalid data from Kubernetes' side, such that we no longer need to relax this check once drop support for older versions.
Value
The forked crate becomes a special case that makes it harder to stay up to date with upstream.
Dependencies
Tasks
(Information Security) Risk Assessment
This should help us stay up to date with upstream h2.
Accessibility Assessment
N/A
Quality
The test suite should pass, with an emphasis on our current minimum supported versions.
## Release Notes N/A, internal change - [ ] https://github.com/stackabletech/secret-operator/pull/495 - [ ] https://github.com/stackabletech/listener-operator/pull/219