openshift-tools-installer is a GitHub Action that downloads, installs and caches OpenShift and Kubernetes related CLI tools from the OpenShift Mirror or from GitHub Releases, allowing you to easily use these tools in your Action workflows.

• Leverages the Actions cache so subsequent downloads are lightning fast
• Supports all 3 major operating systems
• Effective on a GitHub runner, or a self-hosted runner
• Semver support allows total version flexibility

Below is the list of supported tools that can be installed from the OpenShift Mirror or from GitHub.

*️ For Mirror: OPM versions less than 4.6.17 are only available for Linux.
For GitHub: OPM versions less than 1.15.1 are only available for Linux.
Note that OPM versions on the OpenShift Mirror are versioned by the OCP version, not the OPM executable version.
Note that the chart verifier binaries are only available starting with version 1.4.1

The other inputs are just the names of the supported tools, exactly as listed above. The value for each input is a semantic version or range for that tool. If the version given is a range, this action will install the maximum version that satisfies the range.

Version numbers must be quoted, so the yaml parser interprets them as strings.

The version can also be "*", or "latest", which are the same. This installs the latest release that is available on the selected source.

For a list of available versions of a given tool, follow the links in the Supported Tools table for the selected source, and look at the versions available.

If an invalid version is specified, the action will not proceed with any installations.

If the requested version is valid but not available on the mirror, the action fails, but any tools that were found will still be installed and cached.

Here is an workflow step demonstrating some example version inputs.

Also see the OpenShift Mirror example workflow, and the GitHub example workflow.

Refer to the semver documentation. The action uses the semver package, so all syntax is supported.

steps:
  - name: Install CLI tools from OpenShift Mirror
    uses: redhat-actions/openshift-tools-installer@v1
    with:

      # "mirror" is the default source, so this is optional.
      source: "mirror"

      # Installs the latest kam release.
      kam: "latest"

      # Installs the latest release of oc with the major version 3.
      # This is equivalent to "3.x" or "^3".
      oc: "3"

      # Installs the latest release of odo with the major version 2, and the minor version 0.
      # This would install odo 2.0.3, but not odo 2.1.0.
      odo: "2.0"

      # This exact version will install version 0.11.0 of Tekton, no other version.
      tkn: "0.11.0"

  - name: Install CLI tools from GitHub
    uses: redhat-actions/openshift-tools-installer@v1
    with:
      # Search through these projects' GitHub releases, instead of the OpenShift Mirror.
      # https://docs.github.com/en/actions/reference/authentication-in-a-workflow
      source: "github"

      # Using GitHub token from the github context
      github_pat: ${{ github.token }}

      kam: "latest"
      s2i: "1.2"
      tkn: "0.17"

The action has one output called installed, which is a JSON object that maps tool names (as above) to an object describing the version that was installed.

For example, after installing oc with the version range "4.3", the output object contains:

{
    // ... other items omitted
    oc: {
        fromCache: true,
        installedPath: "/home/runner/work/_temp/openshift-bin/oc",
        url: "https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.3.40/openshift-client-linux-4.3.40.tar.gz",
        version: "4.3.40"
    }
}

If a CLI was not installed due to an error, it will be absent from this object. Check the action output and workflow summary for the error.

The executables are cached after being download and extracted. The cache key is determined by the source, the tool name, and the actual version that was downloaded - not the range that was input.

This means that if a new version is released that satisfies the version range, the cached old version will be bypassed in favour of the new version which is then cached. The upgrade is done for you, so long as the version range allows it.

See the actions/cache repository for cache limits.

The cache can be disabled for the current action run by setting the skip_cache input to true.

The Actions cache is not supported on GitHub Enterprise Server, as per this issue.

The cache is disabled in this action if you are using GitHub Enterprise Server.

• If your installation is failing because the requested tool or version is not found:

  • Check if the requested tool is available on the provided OS.
  • Follow the links in the output to make sure the download exists, and check that your inputs match.

  If it does exist and the action doesn't find it, or if you believe it should exist but does not, then open a bug.

• If you hit the API rate limit, refer GitHub API rate limit docs.