Regression of max resync for EKS #2845
Labels
area/provider/eks
Issues or PRs related to Amazon EKS provider
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
/kind regression
/area provider/eks
/priority critical-urgent
Describe the solution you'd like
When EKS was graduated the check for the max resync period wasn't added. We need to include this as it will potentially cause
token expired
issues with anything that relies on the kubeconfig (i.e. crs, scaling).This will need to be back ported to 0.7.x as well.
Environment:
The text was updated successfully, but these errors were encountered: