What's supported by Harness Platform
This topic lists the supported Harness Platform features and integrations you can use for deploying and verifying your apps.
For a comprehensive list that includes all Harness modules, go to Supported platforms and technologies.
- Access control
- Accounts Organizations Projects
- Delegates
- Notifications
- Secret management
- User management
- Self-Managed Enterprise Edition
The following table lists Harness support for SSO protocols and tools.
Go to Add and Manage Access Control.
| SSO Type | SSO Providers | Authentication Supported | Authorization (Group Linking) Supported | SCIM Provisioning |
|---|---|---|---|---|
| SAML 2.0 | Okta | Yes | Yes | Yes |
| Azure Active Directory | Yes | Yes | Yes | |
| Others | Yes | Yes | No | |
| OneLogin | Yes | Yes | Yes | |
| OAuth 2.0 | Github | Yes | No | N/A |
| GitLab | Yes | No | N/A | |
| Bitbucket | Yes | No | N/A | |
| Yes | No | N/A | ||
| Azure | Yes | No | N/A | |
| Yes | No | N/A | ||
| LDAP (Delegate connectivity needed) | Active Directory | Coming soon | Coming soon | N/A |
| Open LDAP | Coming soon | Coming soon | N/A | |
| Oracle LDAP | Coming soon | Coming soon | N/A |
Harness enables you to manage access control at the following scopes.
- Account
- Organization
- Project
Harness packages and distributes delegates on different types of images. Delegate images are identified by the delegate name. Image types are distinguished by tag.
| Image type | Image tag | Image description |
|---|---|---|
| DELEGATE | yy.mm.xxxxx | The release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform. |
| DELEGATE-MINIMAL | yy.mm.xxxxx.minimal | The minimal tag is appended to the release year, month, and version in dot-separated format. Supported on both NextGen and FirstGen Harness Platform. |
| DELEGATE-LEGACY | latest | Delegate that auto upgrades with no flexibility to turn off auto upgrade (DEPRECATED) |
Install delegate minimal image without SDKs
Notification methods supported for various pipeline events are:
- Slack
- PagerDuty
- Microsoft Teams
The following table lists Harness support for cloud platform secrets management services.
Go to Harness Secrets Management Overview.
| Provider Name | Key Encryption Support | Encrypted Data Stored with Harness | Support for Referencing Existing Secrets |
|---|---|---|---|
| AWS KMS | Yes | Yes | No |
| AWS Secret Manager | Yes | No | Yes |
| Hashicorp Vault | Yes | No | Yes |
| Azure Key Vault | Yes | No | Yes |
| Google KMS | Yes | Yes | No |
A Harness user is any individual registered with Harness with a unique email address. A User can be a part of multiple accounts. Go to the following topics to learn more about how to add and manage users.
The following table lists the major supported features for Harness Self-Managed Enterprise Edition offerings. For supported features, go to Supported features and integrations.
| Solution | Supported Platform | Connected | HA | Monitoring | Disaster Recovery |
|---|---|---|---|---|---|
| Kubernetes Cluster | Kubernetes - GKE - AKS - EKS | Yes | Coming soon | Prometheus, Grafana | Coming soon |
Supported Kubernetes versions for Harness Self-Managed Enterprise Edition
- Self-Managed Enterprise Edition supports Kubernetes v.1.25, as well as versions 1.24, 1.23, 1.22, 1.21 and 1.20.
- Effective October 7, 2022, with the release of version 76918, Self-Managed Enterprise Edition no longer supports Kubernetes open-source versions 1.18 and earlier.
- Self-Managed Enterprise Edition supports the other versions of Kubernetes you use on a best-effort basis.
- Harness commits to support new minor versions of Kubernetes within three months of the first stable release. For example, if the stable release of 1.25.0 occurs on August 31, Harness extends compatibility by November 30.
Terms of support for Harness Self-Managed Enterprise Edition
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.