Fix docs for contour to use with AWS platform
AWS platform is also supoprted now, so removed the occurances where it
mentioned that only packet was supported.
@@ -18,13 +18,9 @@ The Contour Ingress component has different requirements on different platforms.
is that an Ingress Controller needs traffic to be routed to their ingress pods, and the network
configurations needed to achieve that differ on each platform.
-Currently the supported platform is Packet.
-
## Prerequisites
-* A Lokomotive cluster accessible via `kubectl` deployed on Packet.
-
-* [MetalLB component](metallb.md) installed and configured.
+* A Lokomotive cluster accessible via `kubectl`.
## Configuration
@@ -72,7 +68,7 @@ Example:
| `enable_monitoring` | Create Prometheus Operator configs to scrape Contour and Envoy metrics. Also deploys Grafana Dashboard. | false | bool | false |
| `ingress_hosts` | [ExternalDNS component](external-dns.md) creates DNS entries from the values provided. | "" | list(string) | false |
| `node_affinity` | Node affinity for deploying the operator pod and envoy daemonset. | - | list(object({key = string, operator = string, values = list(string)})) | false |
-| `service_type` | The type of Kubernetes service used to expose Envoy. | "LoadBalancer" | string | false |
+| `service_type` | The type of Kubernetes service used to expose Envoy. Set as "NodePort" on the **AWS** platform. | "LoadBalancer" | string | false |
| `toleration` | Tolerations that the operator and envoy pods will tolerate. | - | list(object({key = string, effect = string, operator = string, value = string, toleration_seconds = string })) | false |
