dhi.io/gitlab-operator
GitLab Operator
GitLab Operator is a Kubernetes operator that deploys and manages the full lifecycle of GitLab instances on Kubernetes and OpenShift using the GitLab Helm chart.
pushed 18 hours ago
linux/amd64, linux/arm64
48.68 MB
for linux/amd64
283
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About GitLab Operator
GitLab Operator is a Kubernetes operator that deploys and manages GitLab instances on Kubernetes and OpenShift. It
watches GitLab custom resources (apps.gitlab.com/v1beta1) and reconciles them by deploying the GitLab Helm chart
that is bundled in the image, so a single resource describes a complete GitLab installation.
Each GitLab Operator release line deploys a matching GitLab release: operator 3.3.x deploys GitLab 19.3.x, operator 3.4.x deploys GitLab 19.4.x and operator 3.5.x deploys GitLab 19.5.x. Use the operator line that matches the GitLab version you run.
For more information, visit the GitLab Operator documentation.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
GitLab is a trademark of GitLab Inc. in the United States and other countries and regions. All rights in the mark are reserved to GitLab Inc. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.