Is version tag in sync with the actual EKS versioning
- Dominant language
- Shell
- Stars
- 1.5k
- Forks
- 198
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 28
Description
Hello
We configured a Kyvernos rule that checks the version on this repo and proposes a K8s version to our terraform code. However, the version 1.36.0 is not yet available on the EKS clusters and thus the proposed version update fails. Is there a standard delay between this repo and availability on the EKS clusters ?
Thank you
Lars
Contributor guide
Research direction
No file, test, or entry point is identified. Start by comparing the repository's 1.36.0 version with the availability of that Kubernetes version on EKS clusters, then review the release information needed to determine whether a standard delay exists. Done means documenting the synchronization behavior or confirming the version discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100