Drop support for Kube 1.25 and 1.26

[scholzj]

Type of change

• Task

Description

As planned earlier, we should drop support for Kubernetes 1.25 and 1.26 in Strimzi 0.48. This has minimal impact on the code. Only on CIs and Docs. But it makes sure the amount of covered Kubernetes versions remains in check.

Checklist

• Update documentation
• Update CHANGELOG.md

[scholzj]

/azp run regression

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scholzj]

/azp run helm-acceptance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scholzj]

/azp run upgrade

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scholzj]

/packit test --labels upgrade,regression

[ppatierno]

LGTM. @scholzj I have a question for my own knowledge because I have never done that. I see a lot of changes in the doc but I guess it wasn't done manually. Where did you apply the main change so that a make command generated all the rest?

[scholzj]

@ppatierno The changes to documentation/shared/attributes.adoc are manual. Changes to documentation/modules/appendix_crds.adoc are generated. The updated parameter in api/pom.xml defines how the link to the Kubernetes API docs will be constructed. So that drives the changes in appendix_crds.adoc.

[ppatierno]

@scholzj thanks a lot! I will open a PR on the development docs trying to summarize the process as we have for the upgrades of Kafka.

[scholzj]

@ppatierno Well, feel free to document it. But keep in mind that while the steps around the docs are always the same, sometimes there might be other changes to the code etc. In general, the easiest way to start with it is to search for the version and update it that way (e.g. search for 1.27 next time etc.).

[ppatierno]

@scholzj yes yes totally understandable if the new Kube version brought some (breaking) changes. Anyway, it's good having broader lines to follow and mentioning that code changes could be necessary.