Harness Cloud VM Images Doc

docs/continuous-integration/use-ci/set-up-build-infrastructure/use-harness-cloud-build-infrastructure.md

@@ -42,12 +42,7 @@ Free plans require credit card validation to use Harness Cloud. If you don't wan
 
 Harness Cloud offers Linux, macOS, and Windows platforms. To enable Windows and macOS for Harness Cloud, contact [Harness Support](mailto:[email protected]).
 
-Review the following image specifications for information about image components and preinstalled software.
-
-* [Linux amd64 image specifications](https://github.com/wings-software/harness-docs/blob/main/harness-cloud/Linux-amd/Ubuntu2204-Readme.md)
-* [Linux arm64 image specifications](https://github.com/wings-software/harness-docs/blob/main/harness-cloud/Linux-arm/Ubuntu2204-Readme.md)
-* [macOS arm64 (M1) image specifications](https://github.com/wings-software/harness-docs/blob/main/harness-cloud/macos-14-Readme.md)
-* [Windows Server 2022 (Windows amd64) image specifications](https://github.com/wings-software/harness-docs/blob/main/harness-cloud/Windows2022-Readme.md)
+For detailed information about image components and preinstalled software, check out [this page](/docs/platform/references/harness-cloud-vm-images).
 
 **You can customize the Harness Cloud build environment.** In your pipelines, you can [select specific versions of pre-installed tools](#specify-versions), ensure that a step [uses a specific version every time](#lock-versions-or-install-additional-tools), or [install additional tools and versions](#lock-versions-or-install-additional-tools) that aren't preinstalled on the Harness Cloud images. You can run these steps on the host machine or as separate Docker images.
 
@@ -216,104 +211,6 @@ For more information about allowlisting, please review the [full allowlist for I
 * Know that you can add steps to your pipeline to [specify versions of tools](#specify-versions) and [lock versions, set up environments, or install additional tools](#lock-versions-or-install-additional-tools).
 * Run `apt-get update` before [installing additional software](#lock-versions-or-install-additional-tools) that might not be in the image's packages list.
 
-### Specify versions
-
-If a [Harness Cloud image](#platforms-and-image-specifications) has multiple versions of a tool pre-installed, you can specify the version that you want to use in a step's **Command**. For example, with the Harness Cloud macOS build infrastructure, you could use the following command in a [Run step](../run-step-settings.md) to select an Xcode version:
-
-```
-sudo xcode-select -switch /Applications/Xcode_15.1.0.app
-```
-
-:::warning
-
-Harness Cloud machine images can change. If your pipeline relies on a specific version of a software, tool, or environment, make sure you [lock versions](#lock-versions-or-install-additional-tools) to prevent your pipeline from failing when the image changes.
-
-:::
-
-### Lock versions or install additional tools
-
-If your build requires a specific version of a tool or you need to use a version/tool that isn't pre-installed on the [Harness Cloud image](#platforms-and-image-specifications), you must add a step (such as a [Run step](../run-step-settings.md) or [Plugin step](../use-drone-plugins/explore-ci-plugins.md)) to install the version/tool directly on the build machine or run a Docker image that has the required version/tool.
-
-When installing additional tools, run `apt-get update` before installing new software that might not be in the packages list.
-
-<details>
-<summary>Example: Use an Action step to setup Java</summary>
-
-In the following YAML example, an [Action step](../use-drone-plugins/ci-github-action-step.md) runs the `actions/setup-java` GitHub Action to install a Java version, and then the **Run** step confirms the Java version.
-
-```yaml
-            steps:
-              - step:
-                  identifier: install_java
-                  name: intall java version 17
-                  type: Action
-                  spec:
-                    uses: actions/setup-java@v3
-                    with:
-                      distribution: 'temurin'
-                      java-version: '16'
-              - step:
-                  identifier: java_ver_check
-                  name: java version check
-                  type: Run
-                  spec:
-                    shell: Bash
-                    command: |
-                      JAVA_VER=$(java -version 2>&1 | head -1 | cut -d'"' -f2 | sed '/^1\./s///' | cut -d'.' -f1)
-                      if [[ $JAVA_VER == 16 ]]; then
-                        echo successfully installed $JAVA_VER
-                      else
-                        exit 1
-                      fi
-```
-
-:::tip
-
-You can also use the [Bitrise step](../use-drone-plugins/ci-bitrise-plugin.md) to run Bitrise Workflow Steps in your CI pipelines.
-
-:::
-
-</details>
-
-<details>
-<summary>Example: Use a Docker image</summary>
-
-The following YAML example demonstrates how a **Run** step can use a Docker image to leverage tools that are available on the image without having to install them on the build machine.
-
-```yaml
-    - stage:
-        name: Print welcome message
-        identifier: welcome_message
-        type: CI
-        spec:
-          cloneCodebase: true
-          platform: ## Platform properties describe the target machine required by this stage.
-            os: Linux
-            arch: Amd64
-          runtime:
-            type: Cloud ## This build runs on Harness-provided infrastructure.
-            spec: {}
-          execution:
-            steps:
-              - step:
-                  type: Run
-                  name: Welcome
-                  identifier: Welcome
-                  spec:
-                    connectorRef: my_docker_hub  ## Specify a Docker connector to pull an image from Docker.
-                    image: alpine ## If no image is specified, the step runs on the host machine.
-                    shell: Sh
-                    command: Echo "Welcome to Harness CI"
-```
-
-:::info
-
-Steps running in containers can't communicate with [Background steps](../manage-dependencies/background-step-settings.md) running on Harness Cloud build infrastructure because they don't have a common host.
-
-:::
-
-</details>
-
 ## Secure connect (private networking)
 
 You can use Harness Cloud build infrastructure in firewalled environments. For more information, go to [Secure connector for Harness Cloud](/docs/continuous-integration/secure-ci/secure-connect).