Kubernetes Helm architecture milestone
The platform’s historical line note: the previous self-managed architecture has won an official Helm deployment path.ZebraByteCloud retains the product capabilities without exposing this as a client installation method.
Platform lineage note. ZebraByte is delivered as a SaaS Cloud and is not distributed as a self-hosted or open-source product.
The previous self-managed platform architecture achieved a standardized Kubernetes deployment path through a Helm graph. This version packaged the application set, object storage, input, SAML, SMTP and Access-Review connector configuration into a single deployment model.
The architecture used an OCI registry for application images and standardized how integration credentials and web search dependencies were provided for deployment.
For teams considering a migration to ZebraByteCloud, this historical step remains useful as it describes the operating space that settled with the client or platform operator: cluster life cycle, input, secrets, persistent data services, upgrades, and connector configuration.
These responsibilities now belong to the ZebraBytea side of the SaaS operational boundary. ZebraByte Cloud documentation The Preserved architecture and migration reference for this distinction.
