What's supported
Self-Managed Enterprise Edition allows organizations to leverage nearly all Harness modules and features available on Harness SaaS, ensuring a powerful and flexible on-premises experience.
This section provides a clear overview of the Supported features, integrations, and capabilities available in the system.
Supported Modules
- Cloud & AI Cost Management
- Chaos Engineering
- Continuous Delivery and GitOps
- Continuous Integration
- Code Repository
- Database DevOps
- Feature Management & Experimentation
- Infrastructure as Code Management
- Platform (core services and databases)
- Software Supply Chain Security
- Security Test Orchestration
For more details on the supported features of other Harness modules, visit Harness Supported platforms and technologies.
Supported Features
The table below outlines the key features supported in the Harness Self-Managed Enterprise Edition.
| Feature | Supported |
|---|---|
| Cloud Platform |
|
| External Databases |
|
| High availability (HA) | Yes |
| Disaster Recovery (DR) | Active-Passive |
| Backup and Restore | Velero |
| Networking |
|
| Monitoring | |
| Air-gapped | Yes |
| FIPS-enabled K8S | No |
Supported Kubernetes versions
Harness Self-Managed Enterprise Edition supports Kubernetes versions 1.30 through 1.35.
Starting with EKS 1.30 (AWS), support for the default annotation on the storage class has been removed. For Harness to work, update your overrides to include the storageClassName (gp2, gp3, etc.):
global:
storageClass: "gp3"
storageClassName: "gp3"
Supported functionality
- Self-signed certificates
- Air-gap mode
- Infrastructure monitoring
- Backup and restore
- External Database
- Disaster Recovery
Kubernetes Networking
- Istio supported version: 1.15.3 to 1.24.2
- NGINX supported version: v1.3.0
Terms of support
The support policy is 12 months of full support, followed by 6 months of limited support for critical security fixes only.
Harness Self-Managed Enterprise Edition does not introduce changes that break compatibility with supported versions of Kubernetes. For example, Self-Managed Enterprise Edition does not use features from Kubernetes version n that do not work in Kubernetes version n-2.
Installation and upgrade preflight checks provide warnings when you use unsupported Kubernetes versions.
In cases where you encounter a problem related to an incompatibility issue, you must upgrade your cluster. Harness does not issue a patch to accommodate the use of unsupported Kubernetes versions.