helm-charts icon indicating copy to clipboard operation
helm-charts copied to clipboard

Helm Charts ⛵ @ Delivery Hero ⭐

Results 23 helm-charts issues
Sort by recently updated
recently updated
newest added

- `` Update `postgresql` dependency version to stop the error: ``` Error: could not find : chart postgresql not found in https://charts.bitnami.com/bitnami ``` - `kubecost-reports-exporter`: docker image pushed to stop...

Wiremock documentation seems outdated: https://artifacthub.io/packages/helm/deliveryhero/wiremock For example: `helm install my-wiremock deliveryhero/wiremock \ --set consumer=my-consumer --set "consumer.stubs.my-service1-stubs=/mnt/my-service1-stubs" \ --set "consumer.stubs.my-service2-stubs=/mnt/my-service2-stubs"` There is no consumer, its consumer.name as per Default Values: `consumer:...

## Description * If a user installs this chart and sets the [`api_token` value](https://github.com/deliveryhero/helm-charts/blob/master/stable/cloudhealth-collector/values.yaml#L1), the cloudhealth-colllector pod will fail to start due to the deployment config using the wrong secret...

## Description Since the variable is already defined at `database.driver` it causes duplication error in the configmap ## Checklist - [x] Title of the PR starts with chart name (e.g....

## Description Secret having api_token as a key, but in deployment.yaml we are looking api_key. Wrong call of token, due to this is pod not coming up. ## Checklist -...

## Description This adds an easy way to deploy additional manifests alongside the locust chart like for example external secrets that can then be mounted into the locust pods via...

no-pr-activity

## Description - add [asqe](https://github.com/deliveryhero/asqe) helm chart ## Checklist - [ ] Title of the PR starts with chart name (e.g. `[stable/mychartname]`) - [ ] I have read the [contribution...

no-pr-activity

Hello, The ChartMuseum instance you're running on charts.deliveryhero.io has been responding with HTTP 504 for pretty much all endpoints since earlier today. I'm not sure if this is the correct...

## Description **latest api version is v2 so I updated the hpa file.** In my case sync failed because of this error: `The Kubernetes API could not find version "v2beta1"...

Can someone update the node-problem-detector application version as there are some problems in 0.8.15 according to the following [issue ](https://github.com/kubernetes/node-problem-detector/issues/854) ? The last version of the application is v0.8.17. Thanks!