openobserve-helm-chart
openobserve-helm-chart copied to clipboard
Helm charts for OpenObserve
Why? ---- Annotations can be used to control how different operators affect services which can be mightily handy. How? ---- - Added values for `zplane.service.annotations`, `headless.service.annotations` and `service.annotations` - Added...
when I install by HA mode . It told me "parse error at (openobserve/charts/nats/templates/tests/request-replay.yaml:8):unclosed action"。 which I run "helm upgraed --install o2 openobserve/openobserve -f values.yaml --namespace openobserve"
As already noted in some issue reports, sometimes there are breaking changes which require special attention to how a smooth upgrade is being approached. Some scenarios include: 1. upgrading to...
Hello, It seems that multiple secrets remains in the configmap.yaml. Here are some variables that seems to be secret to me, please correct me if I'm wrong. What do you...
The `values.yaml` file assumes the built-in `letsencrypt` issuer is enabled, and breaks if you attempt to use OpenObserve with a `ClusterIssuer` instead. https://github.com/openobserve/openobserve-helm-chart/blob/main/charts/openobserve-standalone/values.yaml#L262 Deploying openobserve-standalone with the following values file...
Make the service names constant across different modes of deployment , so we don't have to change the names to send logs , while migrating across modes
Setting `securityContext.readOnlyRootFilesystem: true` causes most of the containers to fail because they are unable to create a cache directory: ``` thread 'main' panicked at src/config/src/config.rs:1066:57: create cache dir success: Os...
I'd like to be able to add a data volume to /data for the compactor component in the openobserve helm chart. That could be an ephemeral volume (which enables me...
When deploying the OpenObserve Collector agent DaemonSet using this Helm chart, we are encountering two issues in a specific managed Kubernetes environment: a permission denied error when attempting to read...
tl;dr the `values.yaml` of openobserve-collector is over-complicated. A simpler solution can be achieved using the upstream OpenTelemetry collector's chart. I am reviewing the code of the openobserve-collector and would like...