📝 docs: Improve documentation for installation of Unguard on AWS EKS …

…clusters

chart/README.md

@@ -115,9 +115,41 @@ helm install unguard -f aws.yaml oci://ghcr.io/dynatrace-oss/unguard/chart/ungua
 
 The above command applies the values from `aws.yaml` which creates and configures an ingress for EKS deployment.
 
-
 > **Tip**: You can use the default [values.yaml](values.yaml)
 
+
+## Installation on an AWS EKS cluster
+
+> **Warning** \
+> Unguard is **insecure** by design and a careless installation will leave you exposed to severe security vulnerabilities. \
+> When installing Unguard with the `aws.enabled=true` value set, an ingress gets created. Please make sure to review its configuration.
+
+This Chart is prepared to install Unguard on an AWS EKS cluster. \
+To switch from an installation on a local cluster to an AWS EKS cluster, you can run the following Unguard helm install command.
+
+```sh
+helm install unguard oci://ghcr.io/dynatrace-oss/unguard/chart/unguard --set localDev.enabled=false,aws.enabled=true
+```
+
+This creates an ingress and adds the following default annotations:
+
+```yaml
+kubernetes.io/ingress.class: alb
+alb.ingress.kubernetes.io/target-type: ip
+alb.ingress.kubernetes.io/scheme: internal
+alb.ingress.kubernetes.io/load-balancer-name: "unguard-lb"
+```
+
+These annotations can be adjusted by modifying and extending the `aws.yaml` values file and then passing it to the Unguard helm install command like shown bellow.
+
+```sh
+helm install unguard -f aws.yaml oci://ghcr.io/dynatrace-oss/unguard/chart/unguard
+```
+
+> **Note**:\
+Passing the `aws.yaml` values file removes and overrides ALL default annotations. 
+
+
 ## Tracing and Jaeger
 
 To enable tracing, provide the YAML file [tracing.yaml](tracing.yaml) during installation. **Unguard is configured for Jaeger tracing.** \