☸️ [FEATURE] [1.0] Kubernetes Deployment Tooling

Is your feature request related to a problem?

Customers deploying Flock in Kubernetes need official tooling. Without maintained Helm charts, manifests, and scaling guidance, every team writes their own YAML, leading to inconsistent security settings and no supported upgrade path.

Describe the solution you want to see

• Publish a Helm chart (or Kustomize bundle) that installs the orchestrator, dashboard, persistence backends, and optional event bus with production defaults.
• Document and expose configuration for auto-scaling agents based on blackboard queue depth or custom metrics via Horizontal Pod Autoscaler.
• Provide readiness/liveness probes, resource recommendations, and zero-downtime upgrade strategies.
• Include CI validation so chart releases stay in sync with core version bumps and configuration options.

Describe alternatives you have considered

Internal teams maintain bespoke manifests, but they drift quickly and lack QA. Third-party charts don’t understand Flock’s components or visibility requirements, creating support risks.

Additional context

Coordinate with persistence (#271) and Kafka (#278) efforts so operators can toggle those integrations from the chart. Include guidance for secret management and network policies to satisfy enterprise security teams.

No files, tests, or entry points are named. Start by reviewing the repository's existing deployment and configuration structure, then coordinate with persistence (#271) and Kafka (#278). Done means a maintained Helm chart or Kustomize bundle, scaling and health-check guidance, security configuration, upgrade guidance, and CI validation tied to core releases.