Add Helm Chart for OpenViking Deployment

[kartikey54]

Problem Statement

Right now, deploying OpenViking to a Kubernetes cluster means a bunch of manual configuration and setup. It's error-prone and honestly pretty tedious if you just want to get OpenViking running in a K8s environment.

A Helm chart would make deployment way simpler and bring things in line with how the K8s community typically handles package management. It'd make OpenViking much more accessible for folks running containerized workloads.

Proposed Solution

I'd like to create a Helm chart for OpenViking that covers:

1. Helm Chart Structure — standard chart layout with:

   • values.yaml for configuration
   • Templates for Deployment, Service, ConfigMap, and other K8s resources
   • Chart.yaml with metadata

2. Key Features:

   • Support for multiple environment configs (dev, staging, production)
   • Configurable resource limits and requests
   • Persistent storage support
   • Environment-specific values
   • Health checks and probes configuration

3. Distribution:

   • Host the chart in a Helm repository
   • Clear documentation for installation and configuration
   • Examples for common deployment scenarios

This would let users deploy OpenViking on Kubernetes with a single command while following best practices for containerized apps.

Alternatives Considered

• Manual Kubernetes manifests — requires users to understand YAML and manage deployments by hand
• Docker Compose — limited to single-host deployments, not really suitable for production K8s clusters
• Operator — more complex than what's needed for initial Helm support

Helm is the industry standard for K8s package management and seems like the most practical starting point.

Feature Area

Other

Use Case

With a Helm chart, deploying OpenViking to a K8s cluster would be as simple as:

helm repo add openviking https://charts.openviking.io
helm install openviking openviking/openviking

This would cut down deployment time and complexity significantly.

Additional Context

No response

Contribution

• I'm happy to help implement this