Red Hat OpenShift Pipelines vs Tracee

Red Hat OpenShift Pipelines automates application delivery on Red Hat OpenShift using a cloud-native CI/CD system built on Tekton. Pipelines are defined with Kubernetes resources and standard Tekton custom resource definitions, supporting portable pipeline definitions. Runs execute with their dependencies in isolated containers and can scale on demand, a fit for decentralized teams working with microservice-based architectures. The OpenShift Developer console can create Tekton resources, show run logs and manage pipelines in namespaces. Documented image-building tools include Source-to-Image, Buildah, Buildpacks and Kaniko. Red Hat lists integrations with Tekton Pipelines, Tekton Triggers, Tekton Chains, Tekton Results and OpenShift GitOps. Pipelines as Code supports versioned, auditable workflows aligned with GitOps practices. Red Hat describes hardened security and a Trusted Supply Chain framework intended to help ensure integrity and conform with SLSA levels. The product is available with a Red Hat OpenShift subscription and included in OpenShift Container Platform. The documented CI/CD system runs on OpenShift Container Platform. Pricing is on request; the Developer Sandbox offers a 30-day trial.

Tracee is a free, open-source runtime security and observability tool for Linux. Using eBPF, it watches system calls, network activity, and file operations in real time, then emits events for behavior patterns that may indicate threats. Events can include process lineage, file paths, and network connections. Listed uses include security monitoring, compliance monitoring, troubleshooting, and forensic investigation. Tracee is designed to operate without code changes and lists low overhead, container awareness, and adjustable policies. Deployment options are an executable binary, a Docker Hub image, or a Helm chart in Aqua Security’s registry; the quickstart covers Kubernetes installation with that chart. Prometheus scraping is enabled by default, with metrics at :3366/metrics. It supports x86 and arm64 processors and documents long-term kernel versions 5.4, 5.10, 5.15, 6.2, and 6.5, while some distribution kernels may work. Instrumentation needs elevated capabilities, with privileged or root execution described as easiest. Tracee does not run directly on macOS.