-
Notifications
You must be signed in to change notification settings - Fork 179
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
Ability to link EKS-D release to Platform Version on AWS EKS service #2329
Comments
@jrm16020 - Since your goal is to get documentation for EKS-D releases (based on your inputs in "why is this needed"), have you considered looking at the EKS-D changelog? E.g.: https://distro.eks.amazonaws.com/releases/1-27/9/CHANGELOG-v1-27-eks-9/ This should give you the information on what has changed between versions. |
@vipin-mohan the changelog is great but there's no clear link between the EKS-D release and the EKS platform version made available online in the service. v1-27-eks-9 != eks.5 for the 1.27 release branch. |
Hi, I've also stumbled upon this issue by looking for something similar to the OP. I was sure EKS was based on EKS-d, i mean why have 2 versions of the same? but the release dates don't make sense.
v1-27-eks-5 (June 09, 2023) |
There is no one-to-one mapping between EKS platform versions and EKS-D patch releases. Moreover, EKS platform versions (and similarly EKS-D patch releases) don't introduce breaking changes. I'm not clear about why you want to align an EKS-D patch version with an EKS platform version. Can you share more details? |
Sure, i need to understand the changes made in both of them so that i know if it's something that can cause issues for other products being used, even if the changes aren't breaking changes they might still interfere with the things we are running or plan to run. |
What would you like to be added:
Why is this needed:
This helps keep up with documentation to show exactly what has changed between versions and would help include these details in any tool encouraging users to adopt the most recent release/version of Kubernetes for their team!
The text was updated successfully, but these errors were encountered: