v1.0.12 Release

Initial AWS catalog publication of the BigHammer umbrella Helm chart (bighammer) for Amazon EKS.

This baseline aligns with chart version 1.0.12 in bh-helm-charts/incubator/bighammer and includes the full microservice suite (UI, Catalog, Audit, AI Agent, Keycloak, Migration API/Worker, Celery Beat, Transformation Utils) with AWS Secrets Manager + External Secrets Operator (ESO), IRSA, and AWS Load Balancer Controller (ALB Ingress).

---

Published Chart & Download Instructions

Customers entitled to BigHammer on AWS can obtain the published chart using any of the following methods.

Prerequisites

• Kubernetes: EKS 1.28+
• Helm: v3.10+ (v3.17+ recommended)
• Ingress: AWS Load Balancer Controller (ALB Ingress Class alb)
• Secrets Management: External Secrets Operator (ESO) v0.18.x with IRSA → AWS Secrets Manager
• Database: Amazon RDS PostgreSQL with pgvector (application + Keycloak DBs)
• Message broker: RabbitMQ as a separate Helm release — RabbitMQ Broker

---

Option 1: Download from Your Mirrored ECR (Recommended)

In production, pull the chart from your mirrored Amazon ECR (see Release Manifest & Distribution):

aws ecr get-login-password --region <your-aws-region> | \
  helm registry login --username AWS --password-stdin \
  <your-aws-account-id>.dkr.ecr.<your-aws-region>.amazonaws.com

helm pull oci://<your-aws-account-id>.dkr.ecr.<your-aws-region>.amazonaws.com/bh-helm-release/bighammer \
  --version 1.0.12

tar -xzf bighammer-1.0.12.tgz
cd bighammer

---

Option 2: Pull Directly from BigHammer ECR Catalog

If your CI/CD runner can assume the BigHammer reader role (bh-artifact-reader-<customer-id>):

aws ecr get-login-password --region <bh-catalog-aws-region> | \
  helm registry login --username AWS --password-stdin \
  <bh-aws-account-id>.dkr.ecr.<bh-catalog-aws-region>.amazonaws.com

helm pull oci://<bh-aws-account-id>.dkr.ecr.<bh-catalog-aws-region>.amazonaws.com/aws/bh-helm-release/bighammer \
  --version 1.0.12

tar -xzf bighammer-1.0.12.tgz
cd bighammer

---

Option 3: Source Checkout via Git

git clone --depth 1 https://github.com/bh-ai/bh-helm-charts.git
cd bh-helm-charts/incubator/bighammer
# Pin to the commit / tag that published chart 1.0.12
helm dependency build .

---

Summary of This Release

Chart

Field	Value
Chart name	bighammer
Chart version	1.0.12
App version	1.0.12
Catalog OCI (BH source)	oci://…/aws/bh-helm-release/bighammer:1.0.12
Customer OCI (after mirror)	oci://…/bh-helm-release/bighammer:1.0.12

Features (AWS baseline)

• AWS Secrets Manager via ESO + IRSA (SecretStore aws-secret-store)
• Configurable global.remoteSecrets for per-environment Secrets Manager names
• Sample overlays: values-release.yaml (customer placeholders) and internal values-dev.yaml
• ALB Ingress (ingressClassName: alb) with values-driven annotations (scheme, certificate ARN, group name)
• Dual-role application DB users (bh_dev_user / bh_app_user)
• Separate Keycloak server database (keycloak_db_<env> / keycloak_db_user)
• Migration microservices: bhmigrateapi + bhmigrateworker (schema migrate_db)
• Values-driven ingress hostnames and backend ports (EKS ALB vs optional Traefik/K3s overlays)

Subcharts included

Subchart	Purpose
bhui	BigHammer UI + platform Ingress
bhadminui	Admin UI
bhcatalogapi / bhcatalogworker	Catalog API + Celery worker
bhauditapi / bhauditworker	Audit API + worker
bhaiagent / bhaiagentworker	AI Agent API + worker
bhmigrateapi / bhmigrateworker	Migration API + worker
bhkeycloak / bhkeycloakapi	Keycloak + Keycloak API
bhcelerybeat	Celery Beat
bhtransformationutils	Transformation / Spark utils

Image tags (sample from values-release.yaml — pin from your release manifest)

Service	Example image	Example tag
bh-ui	bh-ui	1.0.0-23
bh-catalog-api	bh-catalog-api	1.0.0-6
bh-audit-api	bh-audit-api	1.0.0-1
bh-ai-agent	bh-ai-agent	1.0.0-3
bh-migrate-api	bh-migrate-api	1.0.0-1
bh-keycloak	bh-keycloak	1.0.0-4
bh-keycloak-api	bh-keycloak-api	1.0.0-1
bh-admin-ui	bh-admin-ui	1.0.0-1
bh-transformation-utils	bh-transformation-utils	1.0.0-3-PR.117

Always prefer tags from your customer release manifest, not floating tags.

---

Before you install

Step	Doc
Mirror chart + images to your ECR	Release Manifest & Distribution
Create Secrets Manager secrets	Secrets Manager Secrets
Deploy RabbitMQ (bhrabbitmq)	RabbitMQ Broker
Prepare values and helm upgrade	Platform Deployment

Secrets Manager (initial)

Create all Secrets Manager names referenced by global.remoteSecrets before the first Helm install. ESO fails the entire Kubernetes secret if any remote key is missing.

See the full checklist: Secrets Manager Secrets.

---

Deploy

cp values-release.yaml values-<env>.yaml
# Edit placeholders: account IDs, hostnames, ACM ARN, remoteSecrets names, image tags

helm upgrade --install bighammer ./bighammer \
  --namespace bh-control-plane \
  --create-namespace \
  -f values-<env>.yaml

---

Upgrade notes (future versions)

1. Mirror the new chart version and image tags to your ECR.
2. Update values-<env>.yaml and your release manifest pins.
3. Review new Secrets Manager keys (if any) in that version’s release notes.
4. Run helm upgrade from your ECR OCI URI.

---

Template for future releases

## [x.y.z] — YYYY-MM-DD

### Added
- ...

### Changed
- ...

### Fixed
- ...

### Breaking changes
- ...

### Secrets Manager
- New / renamed secrets: ...

### Promoted to customers
- Customer <name>: chart x.y.z + images <tags>

Add a new page under helm-releases/ (for example v1.0.13.md) when the next chart version is published.

---

Related docs

Doc	Link
EKS platform deploy	Platform Deployment
POC / K3s on EC2	POC Setup
Secrets Manager checklist	Secrets Manager Secrets
Azure equivalent releases	Azure Helm Releases
GCP release notes	GCP Helm Chart Release Notes
RabbitMQ chart (AWS)	RabbitMQ Broker