You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Community Note
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
The text was updated successfully, but these errors were encountered: