Kubernetes Helm architecture milestone
Historical platform-lineage note: the earlier self-managed architecture gained an official Helm deployment path. ZebraByte Cloud preserves the product capabilities without exposing this as a customer installation method.
Platform lineage note. ZebraByte is delivered as Cloud SaaS and is not distributed as a self-hosted or open-source product. This entry is preserved because it documents an important architectural milestone in the product lineage.
The earlier self-managed platform architecture gained a standardized Kubernetes deployment path through a Helm chart. That release packaged the application stack, object storage, ingress, SAML, SMTP and access-review connector configuration into one deployable model.
The architecture used an OCI registry for application images and standardized the way integration credentials and web-search dependencies were supplied to the deployment.
For teams reviewing a migration into ZebraByte Cloud, this historical milestone remains useful because it describes the operational surface that used to sit with the customer or platform operator: cluster lifecycle, ingress, secrets, persistent data services, upgrades and connector configuration.
Those responsibilities now belong on the ZebraByte side of the SaaS operating boundary. See the current ZebraByte Cloud documentation and the preserved architecture and migration reference for the distinction.
