Deploy MassAccess on-premise on Kubernetes with Helm

Manual installation from portal materials: cluster and Helm values preparation, activation, data stores, deployment, upgrades, backups and operations.

Short glossary
  • Helm release: an installed and independently managed resource set from one chart.
  • Secret object: a Kubernetes resource referenced for sensitive values; the delivery charts do not own the values themselves.
  • PersistentVolumeClaim (PVC): a storage request used by a bundled data component.
  • NetworkPolicy: rules governing permitted network connections for application Pods.
  • Container Storage Interface (CSI) and Container Network Interface (CNI) capabilities are provided by the customer cluster.
InformationThis page applies only to the Kubernetes/Helm delivery. Docker Compose remains a separate supported self-contained package; do not combine Compose and Helm commands in one installation.

Release and responsibility boundary

The portal offers one Kubernetes option: materials for a manual Helm installation. The archive contains the massaccess application chart and massaccess-data for selected bundled stores. Your team configures the four store modes and cluster settings locally. No data release is installed when all stores are external.

Helm installationOwnsDoes not own
massaccess 0.13.5Nine application Deployments, internal Services, probes, optional routes, and NetworkPolicyData StatefulSets and PVCs, Secrets, licensor, controllers, and CRDs
massaccess-data 0.3.0 (when any store is bundled)Selected single-node bundled data StatefulSets, Services, and retained PVC templatesApplication Deployments, external stores, Secrets, and cluster-scoped resources

Download materials and prepare local values

A company administrator opens On-premise in the dashboard, creates a license, selects Kubernetes and clicks Download Kubernetes deployment materials. Extract massaccess-kubernetes-manual-<version>.tar.gz into a protected directory and enter massaccess-kubernetes-manual/. Follow INSTALL.ru.md from that release. Kubernetes requires no portal configuration; your DevOps team creates and maintains the values.

Guide sections

  • Kubernetes requirements

    Supported versions, required cluster capabilities, exact-target checks, and confirmed scheduling request floors.

    Kubernetes requirements

  • Data placement and storage

    Independent bundled or external placement for PostgreSQL, Kafka, ClickHouse, and Redis, including bundled-store limits.

    Data placement and storage

  • Delivery package and configuration

    Archive contents, local Helm values, activation, Secret references and manifest validation before installation.

    Delivery package and configuration

  • Kubernetes installation and verification

    Safe data and application release installation, repeat execution, application-level checks, and external access.

    Kubernetes installation and verification

  • Kubernetes upgrade and rollback

    Upgrade planning, failed-upgrade recovery, and rollback for independent application and data releases.

    Kubernetes upgrade and rollback

  • Kubernetes backup and restore

    Responsibility boundaries, component-consistent backups, and evidence-based restore verification.

    Kubernetes backup and restore

  • Kubernetes monitoring

    Metrics, logs, Events, alerts, and the customer infrastructure responsibility boundary.

    Kubernetes monitoring

  • Kubernetes troubleshooting

    Bounded diagnostic collection and exact failing-path checks without exposing secrets.

    Kubernetes troubleshooting

  • Kubernetes uninstall

    Separate application and data-controller removal while preserving volumes, backups, and Secret objects.

    Kubernetes uninstall