Add Big Peer EKS deployment example - #35
Open
Jigar Patel (jiggy-ditto) wants to merge 3 commits into
Open
Conversation
Part 1 provisions VPC + EKS (managed or existing VPC) from config.yaml, including add-on ordering, EBS CSI via Pod Identity, admin access entries and private-subnet VPC endpoints. Part 2 installs cert-manager, Envoy Gateway, Strimzi, the Ditto Operator and Big Peer via Make, with a smoke test and teardown. The example is partition-safe (aws_partition/aws_caller_identity) but carries no environment-specific references.
Jigar Patel (jiggy-ditto)
changed the title
Jigar Patel (jiggy-ditto)
force-pushed
the
codex/big-peer-deployment-example
branch
2 times, most recently
from
September 2, 2026 19:11
6d37f79 to
b1c0224
Compare
- Validate admin_principal_arns is non-empty at plan time; the upstream EKS module defaults enable_cluster_creator_admin_permissions to false, so omitting it locks every identity out of the cluster API. - Comment out the big-peer-prod example deployment: two regions trip the single-region precondition, and its placeholder subnet IDs fail the existing-VPC data lookup. Uncomment with real IDs to use it. Addresses review feedback on PR #35.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A complete, runnable example for deploying a self-managed Big Peer on Amazon EKS, validated end-to-end for both new and existing vpc.
Part 1 (Terraform) provisions the VPC (managed or bring-your-own), EKS cluster, node groups, core add-ons, EBS CSI via Pod Identity, private-subnet VPC endpoints, and admin access entries — all driven by a single annotated
config.yaml.Part 2 (Make) installs cert-manager, Envoy Gateway, Strimzi, the Ditto Operator, and Big Peer, then verifies the deployment with an insert/read smoke test through the gateway. Includes an optional portal UI behind the internal gateway, idempotent targets, and full teardown.
Validation