Closed thesurlydev closed 4 years ago
I don't believe it's due to your Kubernetes version. It's actually a new IAM permission required by v1.1.7. See the v1.1.7 release notes.
Frankly, I find this kind of change to be hostile to users. The expectation should be that a PATCH version change from 1.1.6 to 1.1.7 wouldn't have any breaking changes.
I did see the IAM permission change and had added that but didn't turn out to be the issue.
I eventually got it to work and wasn't a version incompatibility (afaik). What it ended up being in my case was a missing annotation in the service.yaml:
alb.ingress.kubernetes.io/target-type: ip
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/close
@digitalsanctum: Closing this issue.
Apologies if I've missed any documentation around this but can someone comment on which versions of Kubernetes/EKS are compatible with which versions of aws-alb-ingress-controller?
Specifically, I'm wondering if for example the version of ingress-controller should match K8s version? I'm asking because I'm running into the following issue:
I'm current running (not quite) the following versions and curious to know with confidence that aws-alb-ingress-controller is backwards compatible with older versions of Kubernetes.
Thanks!