Upgrading from Jama Connect KOTS to Kubernetes-Native

Carmen Santos
Carmen Santos
  • Updated

Published Date: October 20 2026
Validated: No 
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect® Self-hosted
    • Replicated - KOTS
    • Kubernetes - Native

  • Upgrade Target: Jama Connect 9.35.2

Summary

Customers upgrading from Jama Connect® KOTS to Kubernetes-Native should first upgrade their existing KOTS deployment to Jama Connect 9.35.2.

This article outlines the recommended upgrade sequence, including version prerequisites, licensing, data restoration options, reindexing requirements, and downtime considerations.

This guidance is intended for customer self-service and supplements the Jama Connect Kubernetes-Native Deployment Install Guide. It does not replace the detailed installation and configuration instructions.

For additional technical guidance or upgrade planning assistance, Jama Software recommends scheduling a complimentary Pre-Upgrade Consultation. Customers requiring hands-on implementation assistance can contact their Customer Success Manager to explore professional services through Customer Deployment Services and preferred partners.

Resolution

1. Upgrade the Existing KOTS Deployment

Before transitioning to Kubernetes-Native, upgrade your existing KOTS deployment to Jama Connect 9.35.2.

Consider the following version-specific requirements:

  • Customers running Jama Connect 9.22.x or 9.28.x can upgrade directly to 9.35.2 KOTS.
  • Jama Connect 9.35.1 introduced the transition from Elasticsearch to OpenSearch. Customers upgrading from earlier versions should account for this change.
  • A full reindex is not automatically required during the KOTS upgrade. Upgrading from 9.35.1 to 9.35.2 does not inherently require one.
  • A full reindex is required after upgrading to Kubernetes-Native when using the database-backup restoration approach.
  • For subsequent upgrades, a full reindex is required only when specified in the applicable release documentation.

Before proceeding: Verify that the upgraded KOTS environment is functioning as expected.

2. Prepare for the Kubernetes-Native Upgrade

Complete the following preparations before beginning the upgrade:

  1. Obtain licensing and registry credentials: Contact Jama Software Support to request a string-based license and Registry Credentials for the Kubernetes-Native deployment.
  2. Schedule a maintenance window: Allow sufficient time for installation, data restoration or connection, indexing, and validation.
  3. Enable maintenance mode: Place the existing Jama Connect environment in maintenance mode before beginning the production transition.
  4. Disable integrations: Prevent external integrations and automated processes from modifying data during the upgrade.
  5. Back up production data: Create and verify backups of the database and application assets.

For additional planning guidance, refer to Plan a Self-Hosted Jama Connect® Upgrade: Kubernetes-Native & KOTS.

3. Install and Configure Kubernetes-Native

Install Jama Connect Kubernetes-Native on the target Kubernetes cluster using Helm, following the Jama Connect Kubernetes-Native Deployment Install Guide.

The guide describes two approaches for using existing Jama Connect data:

Option A: Restore a Database Backup

Recommended for larger datasets.

  • Restore the existing database backup into the target database.
  • Configure the Kubernetes-Native deployment to use the restored data.
  • Complete a full reindex after the new environment becomes operational.

This approach is generally recommended for larger datasets because it can provide a more predictable data restoration process.

Option B: Use the Existing Production Database

  • Configure the Kubernetes-Native deployment to connect to the existing production database.
  • Follow the installation guide's requirements for database connectivity, application configuration, and cutover.

Important: Ensure that only one Jama Connect application environment is connected to the production database at any given time.

Follow the installation guide for the complete procedures and requirements applicable to your selected approach.

4. Validate the Kubernetes-Native Environment
Before returning the environment to production use, verify:

  • Application availability and functionality
  • User authentication and access
  • Data integrity and attachments
  • Search functionality and required indexing
  • External integrations and automated processes
  • General application performance

Resolve any identified issues before completing the production transition.

5. Plan for Upgrade Downtime

Kubernetes-Native supports Helm rolling upgrades, readiness checks, and traffic routing, which can improve the experience of subsequent upgrades.

However, Kubernetes-Native does not guarantee reduced downtime. Production upgrades should continue to be scheduled within an appropriate maintenance window.

Actual downtime depends on:

  • Database size and attachment volume
  • Database and OpenSearch performance
  • Storage performance
  • Kubernetes or Amazon EKS resource allocation
  • Required indexing and validation activities

Recommendation: Test the KOTS-to-Kubernetes-Native upgrade and a representative subsequent upgrade in a suitably sized non-production environment to estimate downtime and identify potential issues.

Always review the applicable Jama Connect release notes and installation documentation for version-specific requirements.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.