feat(applicationsets): register protohype-team app tenants#17
Merged
Conversation
CI Results
All validations passed. |
1 similar comment
CI Results
All validations passed. |
stxkxs
changed the title
CI Results
All validations passed. |
1 similar comment
CI Results
All validations passed. |
Adds apps-tenants.yaml — the ApplicationSet that fans protohype-team app tenants (now in their own repos) across clusters, mirroring the proven druid-tenants.yaml idiom (goTemplate matrix: clusters selector × a per-app list). Each list element carries its own source repo, so onboarding a new app is one element, not a new ApplicationSet. First entry: slack-knowledge-bot (https://github.com/nanohype/slack-knowledge-bot, chart at repo root). Scoped to the operator-reconciled tenant-protohype AppProject, namespace tenants-protohype, sync-wave 100 (after cluster addons). CreateNamespace=false — the eks-agent-platform Platform reconciler owns the namespace. Per-env values resolve via the $values multi-source ref against chart/values.yaml + chart/values-<environment>.yaml, environment read from the cluster secret label.
Adds digest-pipeline (formerly protohype/dispatch — weekly newsletter pipeline: pipeline CronJob + Fastify api + Next.js web) as a second element in the apps-tenants list. Same tenant-protohype AppProject / tenants-protohype namespace / sync-wave 100, chart at the repo root of github.com/nanohype/digest-pipeline.
Adds incident-response (formerly protohype/marshal — ceremonial incident commander: webhook + processor Deployments) as the third element in the apps-tenants list. Same tenant-protohype AppProject / tenants-protohype namespace / sync-wave 100, chart at the repo root of github.com/nanohype/incident-response.
Adds competitive-intelligence (formerly protohype/sigint — competitor-site semantic-diff radar) as the fourth and final element in the apps-tenants list. Same tenant-protohype AppProject / tenants-protohype namespace / sync-wave 100, chart at the repo root of github.com/nanohype/competitive-intelligence. Its durable pgvector + Aurora substrate is the new landing-zone competitive-intelligence-platform component.
stxkxs
force-pushed
the
feat/register-slack-knowledge-bot-tenant
branch
from
2ba9b85 to
7363e0a
Compare
CI Results
All validations passed. |
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
1 participant
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.
Registers the newly-promoted slack-knowledge-bot app (formerly
protohype/almanac) as a Platform tenant via a newapplicationsets/apps-tenants.yaml.What
apps-tenants.yamlApplicationSet — the home for protohype-team apps that have graduated into their own repos. Mirrors the provendruid-tenants.yamlidiom:goTemplatematrix of theclustersselector × a per-applist. Unlike druid (one repo, git-directory generator), each app lives in its own repo, so each list element carries its ownrepoURL— onboarding the next app (digest-pipeline / incident-response / competitive-intelligence) is one list element, not a new ApplicationSet.slack-knowledge-bot→https://github.com/nanohype/slack-knowledge-bot, chart at repo root.Wiring
tenant-protohypeAppProject, namespacetenants-protohype.sync-wave: 100— after all cluster addons (bootstrap/networking/karpenter/security/policies/observability/operations/argo at 0–52).CreateNamespace=false— the eks-agent-platform Platform reconciler owns the namespace (applyplatform.yamlfirst; the AppProject + namespace come from the operator).$valuesmulti-source ref →chart/values.yaml+chart/values-<environment>.yaml, environment from the cluster secret label.Notes for the reviewer
slack-knowledge-bot-<env>Applications. Before merge, confirm: (a) thetenant-protohypeAppProject exists (applyslack-knowledge-bot/platform.yamland wait forReady), and (b) the landing-zonealmanac-platformIRSA role ARN + tenantInfra outputs are filled into the chart's per-env values (they ship empty)..app(not.name) in the list to avoid colliding with theclustersgenerator's.name.