K8s versions in pipeline

[EHJ-52n]

Improve pipeline to build different versions for different K8s versions and add according information to the image tags on docker hub.

[danishdynamic]

Hi @EHJ-52n, I've submitted a GSoC 2026 proposal for 52°North and I'm keen to start contributing to the pygeoapi_k8s-manager ecosystem.

I’ve looked into the pipeline requirements and would like to implement the K8s version matrix and automated tagging. Do you have a preferred list of Kubernetes versions to support, or should I start with the most recent stable releases (e.g., 1.28–1.30) ?

[EHJ-52n]

[…] most recent stable releases (e.g., 1.28–1.30)

Please ensure that you use up-to-date information before deciding what the most recent stable releases are!

Maybe, https://endoflife.date/kubernetes is a better source than the AI, search engine or book, you are using:

And than, just follow https://52north.org/software/contribute/#code and provide a PR from your fork, that is working and allows to configure the K8s version during two times:

1. build time
2. run time

[danishdynamic]

Hi @EHJ-52n , I will implement the matrix build for K8s ["1.33","1.34", "1.35"] (per endoflife.date) using ARG for build time and ENV for run time. I will be following the existing tagging convention (${IMAGE}:${VERSION}-k8s-1.35).

I am starting on the PR now!

[danishdynamic]

Hi @EHJ-52n , I have just submitted the PR (#29 ) for this task.

I have implemented the matrix strategy for K8s versions 1.33, 1.34, and 1.35. The builds are passing in my fork, and the docker tags are being generated according to the ${IMAGE}:${VERSION}-k8s-${K8S_VERSION}.

Looking forward to your feedback!