enh: use aws-load-balancer-controller in front of ingress-nginx

[mglotov]

PR Description

• Enabled aws-load-balancer-controller by default
• Changed ingress-nginx service type from LoadBalancer to ClusterIP by default
• Disabled external-dns by default
• Generated SSL certificates for aws-load-balancer-controller due to this issue
• Updated FAQ.md with notes on how to terminate SSL on ingress-nginx side (use cert-manager)

New default scheme looks like:

Pros:

• we can use WAF without using Cloudfront
• we can use WebSockets

Cons:

• can be used only for http traffic

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication