Skip to main content

What's supported in Harness CDE?

Harness Gitspaces (CDEs) support several Git providers, IDEs, and deployment models to help you set up your development environment.

Deployment Models​

Harness Hosted​

In Harness Hosted, all Gitspaces are hosted and managed completely by Harness Control Plane.

Self Hosted​

We support the following cloud infrastructure providers for self-hosted Gitspaces:

Read more about the Harness CDE Deployment Models.

Regions Available​

Harness Hosted Regions​

We currently support the following regions for Harness Hosted Gitspaces:

  1. US West
  2. EU West

If you need other regions, please contact us at cde-interest@harness.io, and we can discuss more to meet your requirements.

Self Hosted Regions​

For Self Hosted Gitspaces, configure regions of your choice based on your infrastructure. For more details, go to Regions in Self Hosted Gitspaces.

Machine Types​

Harness Hosted Machines​

We currently support the following machine types for Harness Hosted Gitspaces:

  1. Standard: 2-core CPU, 8GB RAM, and 30GB disk size
  2. Large: 4-core CPU, 32GB RAM, and 30GB disk size

If you need larger machines, contact us at cde-interest@harness.io to discuss custom configurations to meet your requirements.

Self Hosted Machines​

Go to Machines in Self Hosted Gitspaces to configure machine types of your choice based on your infrastructure.

Git Providers​

Harness Gitspaces support two types of Git providers:

Cloud Git Providers​

  1. Harness Code
  2. GitHub Cloud
  3. GitLab Cloud
  4. Bitbucket Cloud
  5. Any public Git repository

On-Prem Git Providers​

  1. GitHub Enterprise Server
  2. GitLab Self-Managed
  3. Bitbucket Data Center

IDEs​

You can choose your preferred IDE for development. We currently support the following:

Microsoft IDEs​

  1. VS Code Desktop (>=v1.81.0)
  2. VS Code Browser

JetBrains IDEs​

  1. IntelliJ IDEA
  2. PyCharm
  3. PhpStorm
  4. GoLand
  5. CLion
  6. Rider
  7. RubyMine
  8. WebStorm

Artifact Repository Connectors​

To pull your private Docker images, you need to connect Harness to your artifact repository by adding a repository connector. Currently, we support the following connectors:

  1. JFrog Artifactory
  2. Docker Registry (any Docker V2-compliant registry)
  3. Amazon ECR