How devops-ia/helm-opencti works
Main Components
• OpenCTI Server: This is the central component as reflected by the chart’s “server” templates (deployment, service, ingress, configmaps, etc.).
• Worker: The “worker” folder indicates that asynchronous/background tasks or processing are handled via separate deployments.
• Connectors: There is a dedicated “connector” folder in templates plus multiple example connector configurations. These connectors likely represent integrations with third-party threat intelligence sources (e.g., AlienVault, MISP, Shodan, etc.).
• Kubernetes Resources: Represent the overall Kubernetes objects (Deployments, Services, ConfigMaps, Secrets, Network Policies, etc.) that are being deployed.
• CI/CD Pipelines: The .github/workflows directory indicates that automated testing, linting, version checking, and release processes are implemented, which support the deployment lifecycle.
Relationships and Interactions
• The OpenCTI Server interacts with the Worker and Connector components to render the platform’s cyber threat intelligence capabilities.
• The Connectors serve as external integration points, pulling in threat intelligence data or interacting with third-party security tools.
• The Server and Worker communicate through internal APIs or data queues, indicating a decoupled microservice design within the Kubernetes cluster.
• CI/CD pipelines (from the .github folder) automate chart testing, linting, and updating processes, ensuring consistency across releases.
Architectural Patterns & Design Principles
• Kubernetes and Helm: The structure uses Helm’s templating system to define Kubernetes resources. This represents an Infrastructure-as-Code (IaC) pattern that enables repeatable, declarative deployment.
• Microservices Decomposition: Though all parts are deployed as separate Kubernetes deployments, they are isolated in function (server, worker, connectors) which resembles a microservices architecture.
• Separation of Concerns: Deploying server, worker, and connectors separately is a good example of separating logic into distinct roles that communicate with each other through defined interfaces.
• Extensibility: The connector examples suggest that the chart is designed for pluggable integrations, which is key to the system’s flexibility and ease of extension.