How fiware/helm-charts works
Main Components Identification
The system should be represented as a Kubernetes-based deployment architecture with the following key components:
a. Core Components:
• FIWARE Context Broker (central/mandatory component)
• Individual Generic Enablers (represented by separate Helm charts)
• Supporting Infrastructure Services
b. Chart Categories to represent:
• Core Services (e.g., Orion, Scorpio Broker)
• IoT Agents (iotagent-json, iotagent-ul)
• Security Components (Keyrock, endpoint-auth-service)
• API Management (api-umbrella)
• Business Framework Components (business-api-ecosystem)
Specific Implementation Details
Technical aspects:
• Kubernetes resource definitions (Deployments, Services, etc.)
• Helm chart relationships and dependencies
• Configuration options (values.yaml references)
• Integration points with external systems
• Security boundaries and access controls
Additional Elements
• Version compatibility matrix
• Resource requirements
• Scaling indicators (HPA configurations)
• External dependencies
• Configuration parameters
Notes for Implementation
• Maintain clear separation between infrastructure and application layers
• Central role of the Context Broker
• Optional/required component relationships
• Scaling capabilities
• Document security boundaries
• Integration points with external systems
Remember to include annotations for important configuration points and maintain a balance between detail and clarity, focusing on the architectural relationships rather than implementation specifics.