Perses Helm Charts#
You can deploy the Perses application in your Kubernetes cluster using the official Helm charts.
Quick Start#
For installation instructions, see the Installation Guide.
Configuration#
The Perses Helm chart allows you to configure the Perses application through your values.yaml file. The config section in your values file maps directly to the Perses configuration structure.
How Configuration Works#
Any configuration option from the Perses Configuration Documentation can be set under the config key in your Helm values:
# values.yaml
config:
security:
enable_auth: true
readonly: false
authentication:
providers:
oidc:
- slug_id: "github"
name: "Github"
issuer: "https://github.com"
client_id: "your-client-id"
database:
file:
folder: "/var/lib/perses"
# use an environment variable from a kubernetes secret to inject client_secret
envVars:
- name: PERSES_SECURITY_AUTHENTICATION_PROVIDERS_OIDC_0_CLIENT_SECRET
value: "your-client-secret"
This configuration structure mirrors exactly what you would put in a Perses configuration file, making it easy to adapt existing Perses configurations to Helm deployments.
For the complete list of available configuration options, refer to the Perses Configuration Documentation.
Features#
Perses Resource Management#
The Helm chart supports two powerful approaches for managing Perses resources:
- managing resources with ConfigMaps: Use Kubernetes ConfigMaps with a sidecar container to automatically provision dashboards, datasources, and other Perses resources
- packaging resources as OCI artifacts: Package and version your Perses resources as OCI artifacts