OpenShift :: Tag :: Workspace Docs

Checking OpenShift Certificates

Sat, 01 Aug 2026 00:00:00 +0000

This guide covers methods for checking the expiration dates of critical OpenShift certificates, including the API server and Ingress controller. While OpenShift typically auto-rotates most internal certificates, manually verifying them can be useful for troubleshooting and custom monitoring. Key Certificate Locations Critical certificates are stored as Kubernetes Secrets across different namespaces:

BigFix Host Agent Client Deployment on OpenShift via GitOps

Mon, 01 Jan 0001 00:00:00 +0000

Overview This guide details the architecture, design decisions, and configuration required to deploy the HCL BigFix Host Agent Client onto a Red Hat OpenShift Container Platform (OCP) cluster using Argo CD. This implementation rigorously adheres to and matches the standardized Helm component structures, sync-waves, and folder layouts defined in the helm-component-pattern artifact collection.

BigFix Inventory (BFI) Discovery & NFD Deployment via GitOps

Mon, 01 Jan 0001 00:00:00 +0000

Overview This guide details the architecture, design decisions, and configuration required to deploy the HCL BigFix Inventory (BFI) discovery and sub-capacity licensing integration on Red Hat OpenShift Container Platform (OCP). This implementation rigorously adheres to and matches the standardized Helm component structures, sync-waves, and folder layouts defined in the helm-component-pattern artifact collection.

Using the integrated OpenShift container image registry

Mon, 01 Jan 0001 00:00:00 +0000

OpenShift ships with a cluster-internal container registry (the Image Registry Operator, namespace openshift-image-registry). You can push images there instead of an external registry (for example Quay.io), as long as workloads that need the image can pull from the namespace where the image lives. This is the same pattern NVIDIA documents for hosting built images (for example vGPU Manager) on the cluster’s own registry. What you get In-cluster pull hostname (from any pod on the cluster): image-registry.openshift-image-registry.svc:5000 Full image reference: image-registry.openshift-image-registry.svc:5000//: Example: image-registry.openshift-image-registry.svc:5000/nvidia-gpu-operator/vgpu-manager:9.0.0.0 Private by default: images are not public on the internet; access is via Kubernetes RBAC and image pull credentials where needed.