- 2 minutes to read

Run Nodinite on OpenShift (Experimental Sandbox)

Use this page to run Nodinite Core Services on OpenShift in a container sandbox model.

OpenShift uses Kubernetes foundations with additional enterprise governance and route management. The current Nodinite runtime scope is intentionally limited to Core Services.

Current Scope and Boundaries

  • Core Services are included in the OpenShift sandbox path.
  • Monitoring agents and logging agents are not bundled.
  • OAuth 2.0 and OpenID Connect are required.
  • SQL Server is an external dependency provided by the customer.
  • Identity provider is an external dependency provided by the customer.

Important

The OpenShift runtime currently targets Core Services only. This path is intended for sandbox and controlled pre-production validation.

OpenShift Runtime Architecture

flowchart LR PORTAL["fa:fa-globe Nodinite Portal"] --> ZIP["fa:fa-file-zipper Configuration ZIP"] ZIP --> README["fa:fa-file-lines readme.md"] README --> HELM["fa:fa-file-code Helm instructions"] HELM --> OCP["fa:fa-cloud OpenShift Route + Workloads"] OCP --> SQL["fa:fa-database External SQL Server"] OCP --> IDP["fa:fa-id-card External OAuth 2.0/OpenID Connect IDP"] OCP --> REG["fa:fa-box-archive Container Registry"] style OCP fill:#90EE90,stroke:#2e7d32 style SQL fill:#FFD700,stroke:#8a6d00 style IDP fill:#FFD700,stroke:#8a6d00 style REG fill:#87CEEB,stroke:#1e5f86

Diagram: OpenShift deployment flow where users start in Nodinite Portal, use readme instructions for Helm deployment, pull images from the container registry, and connect Core Services to external SQL Server and identity provider.

OpenShift Nodinite Core Services (7.0)
Example of Nodinite Core Services running in an OpenShift topology with external dependencies.

Installation Package and Delivery Flow

Start in Nodinite Portal and download the customer-specific configuration ZIP.

The ZIP contains runtime-specific values and a readme.md that explains:

  • How to retrieve the Helm chart for Kubernetes-compatible deployments.
  • How to apply OpenShift-specific route and environment values.
  • Which OAuth 2.0/OpenID Connect settings must be configured.

Authentication and Access Requirements

  • Configure OAuth 2.0/OpenID Connect discovery and client settings.
  • Define required scopes and claims used by Core Services.
  • Configure callback and redirect URIs to match OpenShift hostnames/routes.
  • Store sensitive client values in secure secret storage.

If OAuth validation fails, review Troubleshooting OAuth2 Validation Failures.

Troubleshooting Checklist

  • Confirm all required values in the configuration ZIP environment files.
  • Confirm OpenShift routes resolve and terminate TLS correctly.
  • Confirm image pull permissions to the container registry.
  • Confirm Core Services connectivity to SQL Server.
  • Confirm OAuth 2.0/OpenID Connect token validation and audience values.

OpenShift and Other Runtimes

Runtime Deployment style Artifact flow
OpenShift Kubernetes-based with Route model Portal ZIP + readme + Helm instructions
Kubernetes Generic cluster with Ingress model Portal ZIP + readme + Helm instructions
Azure Container Apps Managed Kubernetes service Portal ZIP + readme + Bicep + az command

Next Step