chore: Deprecate aws-load-balancer-controller in favor of moving to upstream repository

[bryantbiggs]

Issue

• Resolves aws-load-balancer-controller v2.7.0 : no endpoints available for service aws-load-balancer-webhook-service #1058

• Resolves Allow configuration of webhook selectors #1063

• Resolves Error while installing aws-load-balancer-controller CRDs from github url #964

• Resolves Alb is failling to create in EKS cluster #926

• Resolves [aws-load-balancer-controller] Webhooks allow update failurePolicy #917

• Resolves aws-load-balancer-controller chart is reporting changes each time helm diff is called #902

• Resolves aws-load-balancer-controller contains kind: List in manifest #890

• Resolves AWS load balancer not getting provisioned on installing controller in AWS EKS #876

• Resolves [aws-load-balancer-controller] Any way to retrieve an NLB's listener ARN after reconciliation? #860

• Resolves Usage stats for the aws-load-balancer-controller chart #533

• Resolves Helm chart variable to specify webhook annotations #1106

• Resolves Update deployment.yaml to use the fullname helper #1086

• Resolves Enable Prometheus metrics without service monitor in aws-load-balancer-controller #960

• Relates Update remaining DockerHub-hosted repositories to use ECR #356

Description of changes

• Deprecate aws-load-balancer-controller in favor of moving to upstream repository

Checklist

• Added/modified documentation as required (such as the README.md for modified charts)
• Incremented the chart version in Chart.yaml for the modified chart(s)
• Manually tested. Describe what testing was done in the testing section below
• Make sure the title of the PR is a good description that can go into the release notes

Testing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[oliviassss]

@bryantbiggs, hi, can you elaborate more on the decision process? Why deprecating?

[M00nF1sh]

Hi,
we shouldn't deprecate the aws-load-balancer-controller chart at this moment.
This has been our primary source to host the chart and there are customers relies on this.

The helm charts in the https://github.com/kubernetes-sigs/aws-load-balancer-controller repo is simply a source, where we sync to this eks-charts repo periodically for publish it.

Eventually we'd like to move to public ECR to host helm charts, but it's not ready yet, and we need carefully do the transition.

[bryantbiggs]

@bryantbiggs, hi, can you elaborate more on the decision process? Why deprecating?

yes! the source of truth lies in the AWS LBC repo and this is merely a legacy artifact for publishing purposes. However, that also means it lacks a true owner and questions go unanswered here (see linked issues and PRs. with Public ECR, the better approach is to keep everything in the main repo (the AWS LBC repo) and simply publish to Public ECR from there. this keeps the artifacts in one location, the ownership is clearly defined, and customers/users know where to go for issues/questions/PRs

we aren't making any changes here until the upstream projects have started publishing directly from their repository(s) to Public ECR.