Webserver Operator
Deploys and manages standardized web workloads (NGINX/HTTPD) with opinionated defaults, health checks, and Route/TLS patterns.
- CRDs for simple app definitions
- Route + TLS termination defaults
- ConfigMap-driven site content
OpenShift • Operators • GitOps
We build OpenShift Operators that package day-2 operations into repeatable, supportable APIs — backed by best practices for OLM, RBAC, and secure delivery.
A preview of current Operators built by Duncan Networks. Each Operator is designed to be GitOps-friendly, secure by default, and easy to support in production.
Deploys and manages standardized web workloads (NGINX/HTTPD) with opinionated defaults, health checks, and Route/TLS patterns.
Automates identity integration patterns and safe configuration rollout for SSO-related services.
Encodes repeatable cluster tasks into reconciled resources (day-2 automation), reducing manual toil and drift.
A predictable workflow that turns operational requirements into versioned APIs.
Define the CRD around real operational intent: desired state, constraints, and safe defaults. Emphasis on simplicity and supportability.
Ship with OLM in mind: proper RBAC, CSV metadata, upgrades, and clear ownership boundaries.
Build and publish through pipelines, then deploy via GitOps. Repeatable releases with minimal drift.
Operators should make platforms more boring — reliable, observable, and secure.
Observability, runbooks, and predictable behaviors. We build for the on-call engineer.
Least privilege, strong TLS, and a clean supply chain. Secure patterns are the baseline.
If it happens twice, it becomes code. Operators exist to eliminate click-ops and drift.
This landing page is ConfigMap-driven (HTML/CSS). Update Git, let Argo CD sync, and your site updates.
OpenShift • nginx