helm-chart issues

Add loadBalancerSourceRanges

1

Added loadBalancerSourceRanges into service to provide network level security

Application stops sending data to Pyroscope Server

1

During helm upgrades of application, pyroscope stops sending data After restart of the application , the data starts to flow in pyroscope server the version is latest Any ideas on...

widdix123

Allow configuring labels on Pods

2

Update deployment templates to allow configuring labels on Pods

bakhtin

add priorityClassName to helm chart

6

bmike78

Add the ability to pass environment variables in Kubernetes format

3

tkukushkin

fix containerPort retrieving bug

2

Due to the pyroscope config api-bind-addr starts with ":", the pipeline to extract the port number in the containerPort will always return default 4040. This PR fix this issue

williamfeng323

Liveness and readiness probes prevent the pod from starting

Currently, liveness and readiness probes are configured with `initialDelaySeconds` set to 30s which is fairly high value. However, in case of the container crash, Pyroscope server may need even longer...

kolesnikovae

Support envfrom secret

1

pass env variables use secret https://pyroscope.slack.com/archives/C01FJRYENPQ/p1668486401890059 similar open issue: https://github.com/pyroscope-io/helm-chart/pull/41

futurelm