- FIPS compliant GitLab Runner
GitLab Runner can be installed and used on GNU/Linux, macOS, FreeBSD, and Windows. You can install it:
- In a container.
- By downloading a binary manually.
- By using a repository for rpm/deb packages.
GitLab Runner officially supported binaries are available for the following architectures:
- x86, AMD64, ARM64, ARM, s390x, ppc64le
Official packages are available for the following Linux distributions:
- CentOS, Debian, Ubuntu, RHEL, Fedora, Mint, Oracle, Amazon
GitLab Runner officially supports the following operating systems:
- Linux, Windows, macOS, FreeBSD
You can find information on the different installation methods below. You can also view installation instructions in GitLab by going to your project’s Settings > CI / CD, expanding the Runners section, and clicking Show runner installation instructions.
After you install GitLab Runner, you must register individual runners with your GitLab instance. This instance can be self-managed, or you can use GitLab.com.
GitLab Runner runs the CI/CD jobs that are defined in GitLab.
As of GitLab Runner 14.7, we provide a FIPS 140-12 compliant GitLab Runner binary. This binary, built with the Red Hat Go compiler, bypasses the standard library cryptographic routines and instead calls into a FIPS 140-2 validated cryptographic library.
FIPS compliant GitLab Runner binaries are provided for the following architectures:
Docker images and RPM packages for the same architectures are also provided.
When you use the FIPS version of GitLab Runner in RHEL, you should enable FIPS mode.
Refer to this issue to follow progress on adding other architectures and distributions.
- Install as a Docker service
- Install on Kubernetes
- Install using the agent for Kubernetes
- Install as GitLab Runner Operator