Karpenter git directories not aligned with git tags

[gaborho]

Version

v0.27.3

Expected Behavior

Hi, I noticed that when a new Karpenter version is released, the reference on the website to the older version's CloudFormation script is gone (same applies for Grafana dashboards). For example, at the time when v0.27.2 was the latest version, I could download CloudFormation template from the URL that is formatted like this:
https://karpenter.sh/v0.27.2/getting-started/getting-started-with-karpenter/

Then, v0.27.3 was released, and the link above returns since then "Not found" error message.
I would expect that old releases are still available.
Reason behind is, that I'd like to have a stable CI/CD pipeline, where I can pin a version, and every time I build our release package, I am able to fetch the pinned version at any time.

Actual Behavior

Currently on Karpenter's GitHub under v0.27.3 tag I see only this:
https://github.com/aws/karpenter/blob/v0.27.3/website/content/en/v0.27.2/getting-started/getting-started-with-karpenter/cloudformation.yaml

Notice that although the tag is v0.27.3, the directory is v0.27.2.

Can you please align the git tags with the included directories in the content dir? Thank you.

Steps to Reproduce the Problem

N/A

Resource Specs and Logs

N/A

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, 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

[njtran]

We're hoping to fix this by reducing the amount of website versions that we track. For reference, we prune website folders so that we're not retaining many old versions of docs.

If you need to, you can still access the information you need by checking out the repo at the version after and navigating the filesystem. For example, to get v0.27.0 artifacts you can go to https://github.com/aws/karpenter/tree/v0.27.1/website/content/en/v0.27.0. I realize this isn't the best experience, and it's odd that you can't checkout the repo at v0.27.0 to get the v0.27.0 docs. This is also something we need to improve.

Going to track this effort here #3659 and close this issue. Feel free to re-open if you have an issue with this.

[njtran]

Actually! I'm sorry! I closed this too prematurely. You're right, this should be open because of the exact solution I gave you. Going to re-open.

[gaborho]

We're hoping to fix this by reducing the amount of website versions that we track. For reference, we prune website folders so that we're not retaining many old versions of docs.

If you need to, you can still access the information you need by checking out the repo at the version after and navigating the filesystem. For example, to get v0.27.0 artifacts you can go to https://github.com/aws/karpenter/tree/v0.27.1/website/content/en/v0.27.0. I realize this isn't the best experience, and it's odd that you can't checkout the repo at v0.27.0 to get the v0.27.0 docs. This is also something we need to improve.

Going to track this effort here #3659 and close this issue. Feel free to re-open if you have an issue with this.

Thank you for the solution proposal, but how would I be able to checkout for example right now v0.27.3 if I want to use a specific version? I can't checkout always main in my pipeline, and hope that v0.27.3 will be there always. If I want to pin my pipeline to a certain version, I think the best would be to checkout that given version's tag, and expect that it will always contain the resources for that given version. I hope you can improve this. Thanks for the efforts.