Skip to content
OSDU SPI Infrastructure

Introduction

OSDU SPI Infrastructure is an Infrastructure as Code project for deploying the OSDU Azure SPI (Service Provider Interface) implementation on AKS Automatic.

How is this different from CIMPL?

Section titled “How is this different from CIMPL?”

The OSDU Community Implementation (CIMPL) runs all middleware in-cluster — CosmosDB emulator, RabbitMQ, MinIO, Elasticsearch, PostgreSQL, Redis, and Keycloak all run as Kubernetes workloads.

The Azure SPI takes a hybrid approach: Azure PaaS services handle data persistence and messaging (CosmosDB, Service Bus, Azure Storage, Key Vault), while compute-oriented middleware (Elasticsearch, Redis, PostgreSQL, Airflow) runs in-cluster for faster provisioning and lower dev/test cost.

Three-Layer Deployment Model

Section titled “Three-Layer Deployment Model”

The project uses independent Terraform states for each deployment layer:

Layer 1:  infra/              Azure resources (AKS + PaaS)         ~15 min
Layer 1a: infra-access/       Privileged RBAC bootstrap            ~1 min
Layer 2:  software/foundation/ Cluster operators (cert-manager,     ~3 min
                               ECK, CNPG, ExternalDNS, Gateway API)
Layer 3:  software/spi-stack/   SPI middleware + OSDU services       ~5 min
Layer 3a: software/cimpl-stack/ CIMPL middleware + OSDU services    ~8 min

Each layer has its own lifecycle — infrastructure changes don’t re-evaluate application releases, and the stack can be redeployed independently in ~5 minutes.

Key Capabilities

Section titled “Key Capabilities”
  • One-command deployment via Azure Developer CLI (azd up)
  • AKS Automatic with managed Istio, Cilium, Deployment Safeguards, and Karpenter
  • Workload Identity for credential-free access to Azure PaaS resources
  • Local Helm chart (osdu-spi-service) with baked-in safeguards compliance
  • Feature flags for granular service control
  • Multi-stack support for blue/green deployments on a shared cluster
Section titled “Related Projects”