DevFW-CICD/ingress-nginx-helm
12
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix helm install on cloud provider admonition block (#11412)

Browse source 
* Fix helm install on cloud provider admonition block

* Add missing admonition type.
* Format link to AWS LB controller.
* Add nested YAML code block for annotations example
* Add a couple of line breaks for breathing and structure

* Fix admonition block title

* Another try

* Should be nice now

---------

Co-authored-by: Jérémie Tarot <silopolis@gmail.com>
This commit is contained in:
k8s-infra-cherrypick-robot 2024-06-02 12:25:34 -07:00 committed by GitHub
parent 503843119c
commit f2959041e3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
docs/deploy/index.md
View file

@ -65,14 +65,11 @@ It will install the controller in the `ingress-nginx` namespace, creating that n
helm show values ingress-nginx --repo https://kubernetes.github.io/ingress-nginx
```
!!! helm install on AWS/GCP/Azure/Other providers
There have been too many attempts at using helm to install the controller on the cloud infra like AWS/GCP/Azure/Other.
The ingress-nginx-controller helm-chart is a generic install out of the box.
The default set of helm values are not configured for installing on any infra provider.
The annotations that are applicable to the cloud provider must be customized by the users.
Link to AWS LB Constroller https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/
Examples of some annotations needed for the service resource of --type LoadBalancer on AWS are below
!!! attention "Helm install on AWS/GCP/Azure/Other providers"
The *ingress-nginx-controller helm-chart is a generic install out of the box*. The default set of helm values is **not** configured for installation on any infra provider. The annotations that are applicable to the cloud provider must be customized by the users.<br/>
See [AWS LB Constroller](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/).<br/>
Examples of some annotations needed for the service resource of `--type LoadBalancer` on AWS are below:
```yaml
annotations:
service.beta.kubernetes.io/aws-load-balancer-scheme: "internet-facing"
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
@ -85,11 +82,7 @@ helm show values ingress-nginx --repo https://kubernetes.github.io/ingress-nginx
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name: "somebucket"
service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix: "ingress-nginx"
service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval: "5"
```
**If you don't have Helm** or if you prefer to use a YAML manifest, you can run the following command instead: