Helm charts, deployment guides, and helper tooling for deploying the EQTY Lab Governance Platform on Kubernetes. Supports Auth0, Microsoft Entra ID, and Keycloak as identity providers, with cloud-agnostic storage and key vault integration (AWS, Azure, GCP).
- Review the prerequisites below.
- Pick your identity provider and follow the matching guide in
docs/: - Use
govctlto generate Helm values and secrets, then install thegovernance-platformumbrella chart.
- Kubernetes 1.29+
- Helm 4.0+
kubectlconfigured for your target cluster- Pull access to the EQTY Lab container registry (GitHub Container Registry)
- A configured identity provider (Auth0, Microsoft Entra ID, or Keycloak)
- A cloud account (AWS, Azure, or GCP) with object storage and a key/secret vault provisioned for the platform
charts/— Helm charts for the Governance Platform services (auth, governance, integrity, studio) plus per-IdP bootstrap charts.docs/— Step-by-step deployment guides for each identity provider, with per-cloud variants (AWS, Azure, GCP).govctl/— CLI tool for generating Helm values, bootstrap configs, and secrets files interactively.scripts/— Helper scripts for NGINX ingress setup, cert-manager installation, IdP bootstrap, and post-install database seeding.releases/— Per-version release manifests pinning chart versions, image digests, and source refs for each platform release.containers/— Custom container image builds (e.g. patched PostgreSQL) used by the platform.schemas/— JSON schemas for release manifests and other structured artifacts in this repo.docs-site/— Source for the hosted customer documentation site.
Each platform release has a manifest under releases/ that pins the exact chart versions, image digests, and source refs that make up that release. Match the release version to the chart and image versions you deploy — do not mix versions across releases.
For questions, deployment assistance, or issues, contact your EQTY Lab representative or open an issue in this repository.