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
Traceback (most recent call last):
Loading Kubernetes versions from https://endoflife.date/api/kubernetes.json...
File "/home/runner/work/kr8s/kr8s/./ci/update-kubernetes.py", line 200, in <module>
Loading Azure AKS versions from https://endoflife.date/api/azure-kubernetes-service.json...
main()
File "/home/runner/work/kr8s/kr8s/./ci/update-kubernetes.py", line 181, in main
versions = get_versions()
^^^^^^^^^^^^^^
File "/home/runner/work/kr8s/kr8s/./ci/update-kubernetes.py", line 125, in get_versions
versions = extend_versions(oss_versions, get_azure_aks_versions(), "Azure AKS")
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/runner/work/kr8s/kr8s/./ci/update-kubernetes.py", line 46, in get_azure_aks_versions
data = [
^
File "/home/runner/work/kr8s/kr8s/./ci/update-kubernetes.py", line 50, in <listcomp>
x["eol"] ifnot x["lts"] else x["support"], DATE_FORMAT~^^^^^^^^^^^KeyError: 'support'
Looks like endoflife.date has inconsistent data for the Azure Kubernetes Service which is causing the auto update script to break.
For Kubernetes 1.27 they appear to use the eol field for the LTS EOL date, and the lts and support fields for the original EOL date.
For the last few days the Kubernetes update script has been failing.
https://github.com/kr8s-org/kr8s/actions/runs/11676720158
Looks like
endoflife.date
has inconsistent data for the Azure Kubernetes Service which is causing the auto update script to break.For Kubernetes
1.27
they appear to use theeol
field for the LTS EOL date, and thelts
andsupport
fields for the original EOL date.but for
1.30
they seem to use thelts
date for the original EOL date and theeol
field for the LTS EOL date.The text was updated successfully, but these errors were encountered: