Component C12 – Manifestor
By Raj Marni. March 23, 2025. Revised. Version: 0.1.22
Overview
Component C12 – Manifestor plays a pivotal role in the deployment pipeline by converting user-provided image data and metadata into fully-formed Helm chart manifests. It acts as a bridge between the initial user input captured by the K8or Portal (C8) and the subsequent stages of storage and deployment (via C20 and C24). With templating, validation, and API integration capabilities, the Manifestor ensures that every deployment artifact is generated accurately, consistently, and ready for the next steps in the pipeline.
Key Functions
Helm Chart Generation
Templating Engine: Utilizes templating mechanisms to produce Helm charts that encapsulate deployment configurations for each image.
Dynamic Manifest Creation: Adapts charts based on metadata such as environment, version, and configuration parameters provided by the user.
Validation & Error Handling
Schema Validation: Ensures that the generated charts adhere to predefined schemas and Kubernetes standards.
Feedback Loop: Provides immediate error reporting or logging in case of failures, enabling rapid debugging and correction.
API Integration & Service Coordination
Upstream Communication: Receives input from the K8or Portal (C8), which sends the necessary image data and metadata.
Downstream Interaction: Passes the resulting Helm chart manifests to storage components such as the Chart Store (C20) and designates the chart artifact (C24) for subsequent deployment steps.
Inter-Service Messaging: Engages in structured communications with other services, ensuring that the chart generation process is seamlessly integrated into the broader deployment workflow.
Architecture & Interaction
Internal Structure
Templating Module:
Processes input data and applies it to Helm chart templates.
Supports dynamic configuration to accommodate various deployment scenarios.
Validation Module:
Runs automated checks to ensure generated manifests are valid and error-free.
Interfaces with logging systems to capture any issues during generation.
API Layer:
Exposes endpoints for receiving input from C8.
Facilitates secure and efficient communication with both upstream and downstream components.
External Interactions
Upstream (from C8 – OpsBoard):
Receives user-submitted image details and deployment metadata.
Acts upon this data to begin the manifest generation process.
Downstream:
Chart Store (C20): Once the manifest is generated, it is stored along with metadata for quick retrieval and reference.
Chart Artifact (C24): The finalized Helm chart is designated as a tangible deployment package, ready to be applied to the Cluster Plane.
Kustomize (C28): Further interacts to overlay environment-specific customizations on the base chart manifest.
Benefits & Impact
Automation & Consistency:
Automates the creation of deployment configurations, reducing manual errors and ensuring uniformity across deployments.
Scalability:
Supports dynamic generation of charts tailored to diverse environments and application needs, facilitating scalable deployments across ephemeral clusters.
Operational Efficiency:
Streamlines the transition from image upload (via C8) to deployable Helm chart, accelerating the overall deployment process and enhancing CI/CD workflows.
Last updated