feat: Update karpenter example to use the EKS module, latest version of Karpenter, and run on Fargate

[bryantbiggs]

What does this PR do?

• Update the karpenter example to:
  • Use the terraform-aws-eks module for cluster creation
  • Use the latest Karpenter settings and recommendations (i.e. - AWSNodeTemplate, consolidation, native spot termination handling, etc.)
  • Run Karpenter on EKS Fargate
• Update the karpenter addon to allow passing in a computed SQS ARN value without error and use the latest Karpenter release version
• Remove Datadog operator addon from example - requires an API key

Motivation

• Updates the example blueprint to the current practices used when running Karpenter on EKS

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs require a new example and/or doc page. In general:

• Use an existing example when possible to demonstrate a new addons usage
• A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[csantanapr]

TIL!

[csantanapr]

/lgtm

[FernandoMiguel]

this is a bad example default, from a security point of view, considering many will opy the examples as their deployment reference.

[bryantbiggs]

all examples, minus the fully private example, have the public endpoint enabled. This was done intentionally to make it easier to get started with interacting with the clusters from the examples as well as for testing from the GitHub workflows. The only change here is that it is now explicitly clear that the public endpoint is being enabled

Was there some value that was meant to be added by posting this comment?