Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect EOL dates for GKE k8s #4973

Open
Rizarai opened this issue Apr 11, 2024 · 1 comment
Open

Incorrect EOL dates for GKE k8s #4973

Rizarai opened this issue Apr 11, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Rizarai
Copy link

Rizarai commented Apr 11, 2024

Link to product page on endoflife.date

Let us know the URL of the product page on endoflife.date you found the incorrect details.

Details of incorrect and correct details you have found

The EOL date on endoflife.date is not the same as in the product documentation for GKE k8s (Example with 1.26 version).

endoflife.date: 2024-05-31

Product documentation: 2024-06-30

What is the source website for the product and for its version information?

https://cloud.google.com/kubernetes-engine/docs/release-schedule

In turn using the endoflife API (https://endoflife.date/api/product/gke.json) returns incorrect data too:

{ "releaseDate": "2023-03-31", "eol": "2024-05-31", "latest": "1.26.15-gke.1090000", "latestReleaseDate": "2024-04-08", "lts": false, "support": "2024-03-31" }

I see that the official documentation was updated on 2024-04-05 and the latest update on the endoflife.date GKE page is on 2024-04-09. So either what is being scrapped is incorrect or whoever edits the page input the wrong information.

@Rizarai Rizarai added the bug Something isn't working label Apr 11, 2024
Copy link

welcome bot commented Apr 11, 2024

Thank you for opening your first issue here 👍. Be sure to follow the issue template if you chose one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant