OpenShift Integration
Full-stack Red Hat OpenShift monitoring — operator lifecycle health, project-level resource quotas, etcd performance, and cluster version operator tracking in one place.
How It Works
Deploy via OpenShift OperatorHub
Install the TigerOps Operator from OperatorHub in your OpenShift console. The operator provisions the monitoring stack with the correct SecurityContextConstraints and ClusterRole bindings automatically.
Configure Remote Write to TigerOps
Apply a RemoteWrite CR to forward cluster Prometheus metrics to TigerOps. The TigerOps operator patches the openshift-monitoring PrometheusK8s CR to add the remote write endpoint without disrupting existing alerts.
Set Project-Level Scoping
Use TigerOps project selectors to scope dashboards and alerts per OpenShift project (namespace). Project owners can view only their workload metrics while cluster admins see the aggregate view.
Enable Operator & Route Monitoring
Enable OLM operator health tracking and OpenShift Route latency monitoring. TigerOps correlates operator reconciliation failures with the workloads they manage for rapid incident scoping.
What You Get Out of the Box
Operator Lifecycle Manager Health
Track OLM CSV phase transitions, subscription states, install plan approvals, and operator reconciliation failures. Alert when operators enter a degraded or unknown state before workloads are impacted.
Project-Level Resource Quota Monitoring
Monitor ResourceQuota utilization per OpenShift project — CPU requests, memory limits, persistent volume claims, and object counts. Alert when projects approach quota boundaries before scheduling failures occur.
Cluster Version Operator Tracking
Track ClusterVersion conditions, update progress, and rollout failures from the Cluster Version Operator. Get notified when OpenShift updates stall, degraded operators block upgrades, or Cluster Operator health changes.
etcd Performance & Health
Monitor etcd leader elections, wal fsync duration, backend commit latency, and peer round-trip time. TigerOps baselines etcd performance and alerts on latency regressions that signal disk or network pressure.
OpenShift Route & Ingress Metrics
Track HAProxy Router request rates, response codes, backend connection counts, and TLS handshake failures per Route. Identify slow backends and certificate expiry across all exposed services.
AI-Powered Cluster Incident Correlation
When a cluster operator degrades, TigerOps AI correlates the event with etcd latency spikes, node resource pressure, and pending OLM updates — surfacing the root cause chain in a single incident view.
TigerOps RemoteWrite for OpenShift
Apply these resources to forward OpenShift Prometheus metrics to TigerOps without modifying existing monitoring infrastructure.
# Patch the OpenShift cluster Prometheus to forward metrics to TigerOps
# oc apply -f tigerops-openshift-remotewrite.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: cluster-monitoring-config
namespace: openshift-monitoring
data:
config.yaml: |
prometheusK8s:
remoteWrite:
- url: https://ingest.atatus.net/api/v1/write
bearerToken: "${TIGEROPS_API_KEY}"
writeRelabelConfigs:
# Forward all metrics — narrow with matchExpressions if needed
- sourceLabels: [__name__]
action: keep
regex: .*
queueConfig:
maxSamplesPerSend: 10000
batchSendDeadline: 10s
---
# TigerOps Operator CRD — enables OLM and Route monitoring
apiVersion: monitoring.tigerops.io/v1alpha1
kind: TigerOpsCluster
metadata:
name: openshift-cluster
namespace: tigerops
spec:
platform: openshift
olmMonitoring:
enabled: true
# Track CSV phase, subscription state, install plans
trackInstallPlans: true
clusterVersionMonitoring:
enabled: true
routeMonitoring:
enabled: true
namespaces: [] # empty = all projects
projectQuotaAlerts:
cpuUsagePct: 80
memoryUsagePct: 80
pvcUsagePct: 90Common Questions
Does TigerOps require modifications to the built-in openshift-monitoring stack?
TigerOps adds a remoteWrite entry to the existing PrometheusK8s CR in the openshift-monitoring namespace via the TigerOps Operator. No components are replaced or removed. The built-in Alertmanager and Thanos continue to function as normal.
How does TigerOps handle OpenShift multi-tenancy and project isolation?
TigerOps respects OpenShift RBAC. Project-scoped users see only metrics from their own namespace. Cluster admins have full visibility. Metric labels include the OpenShift project name so dashboards can be filtered and shared per team.
Can TigerOps monitor user-workload monitoring (UWM) metrics alongside cluster metrics?
Yes. TigerOps integrates with both the platform Prometheus (openshift-monitoring) and the user workload Prometheus (openshift-user-workload-monitoring). Both metric streams are merged into a single correlated view in TigerOps.
Does TigerOps support OpenShift on-premises and OpenShift Dedicated / ROSA?
Yes. The TigerOps Operator works with self-managed OCP, OpenShift Dedicated, and ROSA. For managed offerings, TigerOps uses the Prometheus remote write path since direct cluster access to control plane components may be restricted.
How does TigerOps handle OpenShift upgrade monitoring?
TigerOps tracks ClusterVersion conditions throughout the upgrade lifecycle. It monitors each Cluster Operator progression, flags degraded operators that block the upgrade, and maintains historical upgrade duration data so you can benchmark future rollouts.
Unified Observability for Every OpenShift Project and Operator
OLM health, cluster upgrade tracking, project quotas, and etcd performance — correlated by AI in a single pane of glass.