Kubernetes-Native Overview

Overview

Kubernetes-Native deployment of Jama Connect delivers the application as a Helm chart into your existing Kubernetes cluster, allowing you to configure, operate, and upgrade it using the same platform tools and processes that you already know and trust.

A Kubernetes application is installed into an existing Kubernetes cluster using standard Kubernetes resources and tooling.

This means that Jama Connect:

Is delivered as a Helm chart
Defines all the services, containers, and configuration
Deploys standard Kubernetes objects, including:
- Deployments
- Services
- Ingress
- StatefulSet
- Jobs
- ServiceAccounts
- ConfigMaps
- Secrets
- PersistentVolumeClaims

Your platform team owns the cluster and core add-ons (networking, ingress controller, storage, secrets, monitoring, and RBAC). Jama Software assumes that the platform already exists.

WHAT IS HELM?

Helm is the Kubernetes package manager that enables you to ship your application as a

chart. You log in to the Helm repository and configure the values.yaml file for your environment and install or upgrade with simple Helm commands. All key configuration settings (networking, scaling, storage, external services, security, resource limits) live in the values.yaml file.

BENEFITS

You can use your existing Kubernetes platform

Jama Connect runs on your own on-premises clusters.
You are no longer constrained by vendor-managed Kubernetes or locked-in infrastructure.

Standard tools, no proprietary installer

Install, upgrade, and operate with Helm and kubectl.

Security, compliance, and transparency

All resources are standard Kubernetes objects for easy review.

Operational consistency

Customer operations and IT teams can use familiar workflows such as scaling, monitoring health, troubleshooting, and upgrading.
Helm-based rolling upgrades avoid downtime by letting Kubernetes handle pod restarts, traffic routing, and readiness checks.

Installation and deployment workflows

This information depicts the workflows for installing and deploying Jama Connect in a Kubernetes environment.

INSTALLATION WORKFLOW

Whether your environment is internet-enabled or airgap, the installation process consists of three stages:

Planning your installation
Preparing your environment
Installing and upgrading

DEPLOYMENT PROCESS WORKFLOW

These are the steps involved in deploying Kubernetes:

Verify that a Kubernetes cluster and core platform services exist.
Configure values.yaml (including Jama Connect license and other configuration settings).
Log into the Helm repository.
Install the application and components into a dedicated namespace.
Allow Kubernetes to create services, pods, and storage.

Jama Connect is accessible via the ingress controller and uses standard Kubernetes tooling.

NOTE: For airgap environments, the same flow is used with an offline Helm bundle and locally imported container images.

Architectural components

These diagrams show the high-level logical architecture of Jama Connect in a Kubernetes deployment.

This diagram identifies the application components, deployment components, and customer-provided infrastructure within the Kubernetes cluster, including the external database server and components that can be optionally enabled or provided.

This color-coding legend summarizes the roles of customer-provided components, deployment jobs, and core application components that run and manage Jama Connect.

In This Section

Related to