Support for Kubernetes version 1.31

[taf-b]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Is your feature request related to a problem? Please describe.

Kubernetes version 1.30 reaches end of life on June 28, 2025. Users running Consul on Kubernetes are currently unable to upgrade their Kubernetes version to 1.31 as per the compatibility matrix here: https://developer.hashicorp.com/consul/docs/k8s/compatibility#compatibility-matrix

This also impacts users running Consul on services such as EKS where standard support ends shortly after Kubernetes end of life. See: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar

Feature Description

Requesting support for Kubernetes version 1.31 before 1.30 reaches end of life.

Use Case(s)

Applicable to users running Consul on Kubernetes.

Contributions

[steevi]

Also based on tha compatibility matrix in the following link https://developer.hashicorp.com/consul/docs/upgrade/k8s/compatibility

1.20 is compatible with kubernetes up to 1.30 and 1.21 consul is compatible with kubernetes 1.31 and onwards.

Having no overlap in compatible kubernetes versions means when upgrading the cluster toto 1.31 and until we upgrade consul there will be an incompatibiilty which unsure that the consequences will be.