Releases: zalando-incubator/kube-ingress-aws-controller
Releases · zalando-incubator/kube-ingress-aws-controller
v0.3.9
v0.3.8
- For migrations it is necessary to update CF Stacks. We update all CF stacks we created every hour which can be customized by setting --update-stack-interval or UPDATE_STACK_INTERVAL environment variable. A known problem was that TargetGroups from ALBs get no interfaces in new Subnets, so we had to update the CF stack to migrate this.
v0.3.7
v0.3.6
- Fixed #68 to safely delete CF stacks. In case of the automatic certificate lookup and a newer/better x509 certificate was issued, we would have created a downtime for all ingresses which depended on the same ALB linked to the old certificate.
- Docker image name was changed to reflect the project name
docker run -it registry.opensource.zalan.do/teapot/kube-ingress-aws-controller:v0.3.6
v0.3.5
v0.3.4
v0.3.1
v0.3.0
This release contains a major refactoring from v0.2.x.
- It uses CloudFormation stacks to create, update, delete ALBs, instead of API calls, because we got too often rate limited.
- Old ALBs are not cleaned up, but will be recreated using CF. You have to manually clean up old ALBs, which were created from ingress controllers with version
< v0.3.0
docker run -it registry.opensource.zalan.do/teapot/kube-aws-ingress-controller:v0.3.0