Warning: This is not a production release, please don't use it in production !

1. The purpose of this release is to gather early feedbacks about the APIs and usage.
2. If you have find issues or feedbacks, please create an issue with [V2] in title.
3. It's backwards compatible with aws-alb-ingress-controller:v1.1.3+.

Documentation (detailed documentation about new features coming soon)

Image: docker.io/amazon/aws-alb-ingress-controller:v2.0.0-rc0

Install Instructions:

1. change your-cluster-name to be real clusterName in https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/v2.0.0/config/samples/install_v2_0_0_rc0.yaml
2. apply the yaml

Features:

1. all existing annotations(in v1) except below are supported(coming soon):
   • alb.ingress.kubernetes.io/waf-acl-id
   • alb.ingress.kubernetes.io/wafv2-acl-arn
   • alb.ingress.kubernetes.io/shield-advanced-protection
2. ingress groups feature described in #914
   • alb.ingress.kubernetes.io/group.name
   • alb.ingress.kubernetes.io/group.order
3. A new controller for Kubernetes Service which will provision NLBs in IP targeting mode.
   • create a normal NodePort Service. (we'll support you use a LoadBalancer type soon)
   • add annotation to your service service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip
   • all other NLB related annotations in current kubernetes NLB support
4. A new alpha CRD called TargetGroupBinding to allow you register/deregister targets from TargetGroups.
   • crd schema(subject to change) can be viewed in https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/v2_ga/apis/elbv2/v1alpha1/targetgroupbinding_types.go
   • sample use cases:
     • manage your ALB/TargetGroups via cloudFormation/terraform/aws-cdk, which only use this controller to register/deregister targets for it.