chore: Update examples to use terraform-aws-eks module where possible

.github/scripts/plan-examples.py

@@ -10,13 +10,8 @@ def get_examples():
  """
  exclude = {
  'examples/appmesh-mtls', # excluded until Rout53 is setup
- 'examples/eks-cluster-with-external-dns', # excluded until Rout53 is setup
- 'examples/fully-private-eks-cluster/vpc', # skipping until issue #711 is addressed
- 'examples/fully-private-eks-cluster/eks',
- 'examples/fully-private-eks-cluster/add-ons',
- 'examples/ai-ml/ray', # excluded until #887 is fixed,
- 'examples/crossplane' #example removed
- 'examples/upgrade/blue-green-route53/core-infra'
+ 'examples/blue-green-upgrade/core-infra',
+ 'examples/blue-green-upgrade/modules/eks_cluster'
  }
 
  projects = {

.github/workflows/e2e-parallel-destroy.yml

@@ -24,11 +24,8 @@ jobs:
  matrix:
  include:
  - example_path: examples/agones-game-controller
- - example_path: examples/complete-kubernetes-addons
- - example_path: examples/eks-cluster-with-new-vpc
  - example_path: examples/fargate-serverless
- - example_path: examples/gitops/argocd
- - example_path: examples/grafana-loki
+ - example_path: examples/argocd
  - example_path: examples/ipv4-prefix-delegation
  - example_path: examples/ipv6-eks-cluster
  - example_path: examples/karpenter
@@ -63,4 +60,5 @@ jobs:
  terraform init -upgrade=true
  terraform destroy -target=module.eks_blueprints_kubernetes_addons -no-color -input=false -auto-approve
  terraform destroy -target=module.eks_blueprints -no-color -input=false -auto-approve
+ terraform destroy -target=module.eks -no-color -input=false -auto-approve
  terraform destroy -no-color -input=false -auto-approve

.github/workflows/e2e-parallel-full.yml

@@ -53,11 +53,8 @@ jobs:
  matrix:
  include:
  - example_path: examples/agones-game-controller
- - example_path: examples/complete-kubernetes-addons
- - example_path: examples/eks-cluster-with-new-vpc
  - example_path: examples/fargate-serverless
- - example_path: examples/gitops/argocd
- - example_path: examples/grafana-loki
+ - example_path: examples/argocd
  - example_path: examples/ipv4-prefix-delegation
  - example_path: examples/ipv6-eks-cluster
  - example_path: examples/karpenter
@@ -105,6 +102,7 @@ jobs:
  export AWS_CSM_HOST=127.0.0.1
  terraform apply -target=module.vpc -no-color -input=false -auto-approve
  terraform apply -target=module.eks_blueprints -no-color -input=false -auto-approve
+ terraform apply -target=module.eks -no-color -input=false -auto-approve
  terraform apply -target=module.eks_blueprints_kubernetes_addons -no-color -input=false -auto-approve
  terraform apply -no-color -input=false -auto-approve
 
@@ -118,6 +116,7 @@ jobs:
  export AWS_CSM_HOST=127.0.0.1
  terraform destroy -target=module.eks_blueprints_kubernetes_addons -no-color -input=false -auto-approve
  terraform destroy -target=module.eks_blueprints -no-color -input=false -auto-approve
+ terraform destroy -target=module.eks -no-color -input=false -auto-approve
  terraform destroy -no-color -input=false -auto-approve
 
  - name: Fail if TF apply failed

docs/add-ons/apache-airflow.md

@@ -1,7 +1,7 @@
 # Apache Airflow add-on
 
 This document describes the details of the best practices for building and deploying Self-managed **Highly Scalable Apache Airflow cluster on Kubernetes(Amazon EKS) Cluster**.
-Alternatively, Amazon also provides a fully managed Apache Airflow service(MWAA). Please see this [example](https://awslabs.github.io/data-on-eks/docs/job-schedulers-eks/aws-managed-airflow) if you are looking to build Amazon MWAA.
+Alternatively, Amazon also provides a fully managed Apache Airflow service(MWAA).
 
 Apache Airflow is used for the scheduling and orchestration of data pipelines or workflows.
 Orchestration of data pipelines refers to the sequencing, coordination, scheduling, and managing complex data pipelines from diverse sources.
@@ -60,18 +60,15 @@ This deployment example uses internet facing Load Balancer to easily access the
 You can modify the `values.yaml` to set the Load Balancer to `internal` and upload certificate to use HTTPS.
 Ensure access to the WebUI using internal domain and network.
 
-
-Checkout the [examples](https://awslabs.github.io/data-on-eks/docs/job-schedulers-eks/self-managed-airflow) of deploying and using Apache Airflow on Amazon EKS.
-
 ## Usage
 
-The [Apache Airflow](https://awslabs.github.io/data-on-eks/docs/job-schedulers-eks/self-managed-airflow) can be deployed by enabling the add-on via the following.
+The Apache Airflow can be deployed by enabling the add-on via the following.
 
 ```hcl
  enable_airflow = true
 ```
 
-For production workloads, you can use this [example](https://awslabs.github.io/data-on-eks/docs/job-schedulers-eks/self-managed-airflow) with custom Helm Config.
+For production workloads, you can use the following custom Helm Config.
 
 ```hcl
  enable_airflow = true
@@ -116,5 +113,4 @@ airflow-scheduler 2/2 2 2 77m
 airflow-statsd 1/1 1 1 77m
 airflow-triggerer 1/1 1 1 77m
 airflow-webserver 2/2 2 2 77m
-
 ```

docs/add-ons/argo-workflows.md

@@ -4,8 +4,6 @@
 
 For complete project documentation, please visit the [Argo Workflows documentation site](https://argoproj.github.io/argo-workflows/).
 
-[DoEKS has an example demonstrates how to use Argo Workflows to assign jobs to Amazon EKS] (https://awslabs.github.io/data-on-eks/docs/job-schedulers-eks/argo-workflows-eks)
-
 ## Usage
 
 Argo Workflows can be deployed by enabling the add-on via the following.

docs/add-ons/kafka.md

@@ -5,7 +5,7 @@ This addon deploys Strimizi Kafka Operator and it makes it really easy to spin u
 For complete project documentation, please visit the [Strimzi Kafka](https://strimzi.io/).
 
 ## Usage
-Strimzi Kafka Operator can be deployed by enabling the add-on via the following. Check out the full [example](https://github.com/awslabs/data-on-eks/tree/main/streaming/kafka) to deploy the EKS Cluster with Kafka.
+Strimzi Kafka Operator can be deployed by enabling the add-on via the following.
 
 ```hcl
 enable_strimzi_kafka_operator = true