chore: Update documentation for removed references

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

@@ -29,16 +29,11 @@ jobs:
           - example_path: examples/eks-cluster-with-new-vpc
           - example_path: examples/fargate-serverless
           # - example_path: examples/fully-private-eks-cluster # skipping until issue #711 is addressed
-          - example_path: examples/game-tech/agones-game-controller
           - example_path: examples/gitops/argocd
           # - example_path: examples/ingress-controllers/nginx # ignoring due to https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1629
           - example_path: examples/ipv6-eks-cluster
           - example_path: examples/karpenter
           - example_path: examples/multi-tenancy-with-teams
-          - example_path: examples/node-groups/fargate-profiles
-          - example_path: examples/node-groups/managed-node-groups
-          - example_path: examples/node-groups/self-managed-node-groups
-          - example_path: examples/node-groups/windows-node-groups
           - example_path: examples/stateful
           - example_path: examples/vpc-cni-custom-networking
     steps:

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

@@ -33,16 +33,11 @@ jobs:
           - example_path: examples/eks-cluster-with-new-vpc
           - example_path: examples/fargate-serverless
           # - example_path: examples/fully-private-eks-cluster # skipping until issue #711
-          - example_path: examples/game-tech/agones-game-controller
           - example_path: examples/gitops/argocd
           # - example_path: examples/ingress-controllers/nginx # ignoring due to https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1629
           - example_path: examples/ipv6-eks-cluster
           - example_path: examples/karpenter
           - example_path: examples/multi-tenancy-with-teams
-          - example_path: examples/node-groups/fargate-profiles
-          - example_path: examples/node-groups/managed-node-groups
-          - example_path: examples/node-groups/self-managed-node-groups
-          - example_path: examples/node-groups/windows-node-groups
           - example_path: examples/stateful
           - example_path: examples/vpc-cni-custom-networking
     steps:

.github/workflows/plan-examples.py

@@ -10,12 +10,11 @@ def get_examples():
     """
     exclude = {
         'examples/eks-cluster-with-external-dns',  # excluded until Rout53 is setup
-        'examples/ci-cd/gitlab-ci-cd',  # excluded since GitLab auth, backend, etc. required
+        'examples/gitlab-ci-cd',  # excluded since GitLab auth, backend, etc. required
         '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/portworx',  # excluded due to policy not known at plan/apply time
     }
 
     projects = {

docs/add-ons/portworx.md

@@ -6,13 +6,9 @@
 
 - [Helm chart](https://github.com/portworx/helm)
 
-## Examples Blueprint
-
-To get started look at these sample [blueprints](../../examples/portworx).
-
 ## Requirements
 
-For the add-on to work, Portworx needs additional permission to AWS resources which can be provided in the following way. For an example blueprint, click [here](../../examples/portworx).
+For the add-on to work, Portworx needs additional permission to AWS resources which can be provided in the following way.
 
 Note: Portworx currently does not support obtaining these permissions with an IRSA. Its support will be added with future releases.
 

docs/advanced/bottlerocket.md

@@ -4,7 +4,7 @@
 
 Bottlerocket has two containers runtimes running. Control container **on** by default used for AWS Systems manager and remote API access. Admin container **off** by default for deep debugging and exploration.
 
-Bottlerocket [Launch templates userdata](https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/main/modules/aws-eks-managed-node-groups/templates/userdata-bottlerocket.tpl) uses the TOML format with Key-value pairs.
+Bottlerocket launch templates userdata uses the TOML format with Key-value pairs.
 Remote API access API via SSM agent. You can launch trouble shooting container via user data `[settings.host-containers.admin] enabled = true`.
 
 ### Features

docs/core-concepts.md

@@ -14,8 +14,6 @@ This document provides a high level overview of the Core Concepts that are embed
 
 A `cluster` is simply an EKS cluster. EKS Blueprints provides for customizing the compute options you leverage with your `clusters`. The framework currently supports `EC2`, `Fargate` and `BottleRocket` instances. It also supports managed and self-managed node groups. To specify the type of compute you want to use for your `cluster`, you use the `managed_node_groups`, `self_managed_nodegroups`, or `fargate_profiles` variables.
 
-See our [Node Groups](https://aws-ia.github.io/terraform-aws-eks-blueprints/latest/node-groups/) documentation and our [Node Group example directory](https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/examples/node-groups) for detailed information.
-
 ## Add-on
 
 `Add-ons` allow you to configure the operational tools that you would like to deploy into your EKS cluster. When you configure `add-ons` for a `cluster`, the `add-ons` will be provisioned at deploy time by leveraging the Terraform Helm provider. Add-ons can deploy both Kubernetes specific resources and AWS resources needed to support add-on functionality.