K8s version deprecation guidance

[stockholmux]

What I'd like:
In bottlerocket-os/bottlerocket#2228, bottlerocket deprecates support for k8s 1.19. It isn't clear what triggers deprecation for a k8s version.

There should be a documented policy of what triggers a deprecation for a version of k8s as well as any timelines for support in bottlerocket.

Any alternatives you've considered:
Go without documenting the deprecation tiggers or timeline?

[stmcginnis]

Maybe a better fit for the project-website repo?

[stockholmux]

@stmcginnis being the OP, I think that's fine for the ender user (so on project-website), but does it also make sense to have it for developers (so in markdown content on the repo)?

[stmcginnis]

My thought was EOL dates would be more of a concern for end users and less of a developer concern. So to me the website would make the most sense. But I could see having it in both places.

What may be best to avoid duplication, if we have a landing page on the site (e.g. /variant-lifecycle.html), we could just mention a link to that somewhere in a develop-focused markdown file so folks know where to go to find out that information if needed.

[stockholmux]

@stmcginnis that sounds reasonable. Do you want me to transfer the issue?

[stmcginnis]

I thought I had rights to transfer to that repo, but it's not showing up in my list of repos to select from. If you could transfer it, that would be great @stockholmux. Thanks!