First alpha release for V2 branch

The V2 branch contains massive refactor to support IngressGroup feature,

Docker Image: amazon/aws-alb-ingress-controller:v1.2.0-alpha.1
Instructions for install and IngressGroup feature: #914

Caution

• Do not use this release in production yet.
• This release is not backwards compatible with current v1.1.2 release(old ALB/TargetGroup for Ingress won't be reused), we'll release a glue version(likely v1.1.3) to enable seamless upgrades.

v1.1.2

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.2

Changelog since v1.1.1

Action Required

1. New IAM permission needed: ec2:DescribeNetworkInterfaces (The full set of required IAM permission is available in iam-policy.json)

New Features

1. Auto select certificates based on ingress hostname(#864) (note: HTTPS listener must be explicitly requested via alb.ingress.kubernetes.io/listen-ports to enable this feature)

Other notable changes

1. Register out-of-vpc targets using 'all' AZ setting
2. E2E framework & test cases for mode instance and mode IP
3. Remove cache on AWS API calls
4. Fix error msg for internet LB subnet tagging requirement
5. Bug fix for hanging when delete managed securityGroup
6. Bug fix for detect WAF Regional service availablity
7. Doc update for cognito sample
8. Doc improvement
9. Doc improvement
10. Doc improvement

v1.1.1

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.1

Changelog since v1.1.0

Action Required

1. If you manually added multiple certificates to ALB listeners before, you needs to add the additional certificate via alb.ingress.kubernetes.io/certificate-arn annotation(otherwise, these additional certificates will be removed during reconcile)
2. Additional IAM Permission are needed:

• elasticloadbalancing:AddListenerCertificates
• elasticloadbalancing:RemoveListenerCertificates
• elasticloadbalancing:DescribeListenerCertificates

New Features

1. Support for multiple SSL certificates
2. Installation via kustomize

v1.1.0

Documentation
Image: docker.io/amazon/aws-alb-ingress-controller:v1.1.0

Changelog since v1.0.1

Action Required

N/A

New Features

1. Support authentication via Cognito and OIDC, See docs here
2. Support using existing targetGroup as backend, See docs here
3. Support using named port to denote healthcheck port

Other notable changes

1. Bug fix for disable access_log
2. Bump aws-sdk-go version to v1.16.11 to support kube-aws-iam-controller
3. Enhancement for host only condition
4. Apply k8s standard package layout
5. Doc enhancements for workthough
6. Doc enhancements for helm
7. Doc enhancements
8. Doc enhancements
9. Doc enhancements

v1.0.1

v1.0.1

Documentation

image: docker.io/amazon/aws-alb-ingress-controller:v1.0.1

Changelog since v1.0.0

Action Required

N/A

Other notable changes

• Bug fix for incompatible securityGroup tagging with k8s core
• Bug fix for controller crash with missing action annotation
• Doc enhancements for IAM policy
• Doc enhancements for external-DNS config
• Doc enhancements for work through

v1.0.0

v1.0.0

Documentation

Docker Image: 894847497797.dkr.ecr.us-west-2.amazonaws.com/aws-alb-ingress-controller:v1.0.0

Changelog since 1.0-beta.7

Action Required

• change annotation security-group-inbound-cidr to inbound-cidr(#733, @M00nF1sh)
• annotation ignore-host-header is removed. Please remove it from your ingress.(Host condition will only be applied if you have specified host in your ingress spec)
• IAM policy have been changed. Please refer iam-policy.json
• --ingress-class flag behavior has changed: (note: --ingress-class=alb is set in helm chart/example yaml by default)
  • new behavior:
    • If --ingress-class=xxx flag is set, only ingress with kubernetes.io/ingress.class: xxx annotation will be targeted.
    • If --ingress-class=xxx flag is not set, both ingress without kubernetes.io/ingress.class or with kubernetes.io/ingress.class: alb will be targeted.
  • old behavior:
    • If --ingress-class=xxx flag is set, and xxx is not alb, only ingress with kubernetes.io/ingress.class: xxx annotation will be targeted.
    • if --ingress-class flag is not set, or set as --ingress-class=alb, both ingress without kubernetes.io/ingress.class or with kubernetes.io/ingress.class: alb will be targeted.

Other notable changes

• Refactored whole codebase to improve maintainability and testability.(#650, #651, #653, #654, #664, #674, #694, @bigkraig, @M00nF1sh)
• Adding support for specify default tags at controller level(#711, @jmcarp)
• Adding feature gate for WAF support(#728, @M00nF1sh)
• Allow service of type LoadBalancer for instance target mode(#732, @hatmatter)
• Align tagging support for securityGroups with other resources(#730, @M00nF1sh)
• Fixed bug when handling empty path in ingress spec(#736, @M00nF1sh)
• Resolve VPC ID and AWS Region from ec2metadata during start up(#723, @M00nF1sh)
• Rewriten docs using mkdocs(#737, @M00nF1sh)
• Migrate CI/CD from travis to PROW(#705, @M00nF1sh)

1.0-beta.7

New Feature:

1. ingress paths without backend is now default to 404(previously, it's default to the first backend available).
   An implicit of this is that path:/ need to be changed to path:/* to match all paths

Bug Fixes:

1. http->https redirection now works
2. Multiple ENI issue
3. Multiple issues for IP target mode
4. Annotation merging
5. other issues

Refactor:

1. caching/tracing for API calls are now implemented at AWS session level
2. securityGroup handling is fully refactored

1.0-beta.6

Merge pull request #555 from kubernetes-sigs/master

merge master

1.0-beta.5

Fix a type mismatch that was detected in #507

1.0-beta.4

Merge pull request #462 from kubernetes-sigs/1.0-beta.4

1.0-beta.4