Toxiproxy Helm Chart

Toxiproxy
Analyzed version: 1.3.6

By Delivery Hero

A TCP proxy to simulate network and system conditions for chaos and resiliency testing. By default the chart will install toxiproxy with blank configuration. You can add [toxics](https://github.com/Shopify/toxiproxy#toxics) to the running configuration using the [API](https://github.com/Shopify/toxiproxy#http-api). For large configurations it is easier to store your toxics in a JSON file, in a `ConfigMap` and pass this to the chart to be used by toxiproxy: ```console kubectl create configmap my-toxiproxy-config --from-file path/to/your/toxiproxy.json ``` And then install the chart passing the name of the `ConfigMap` as a value: ```console helm install toxiproxy deliveryhero/toxiproxy --set toxiproxyConfig=my-toxiproxy-config ```

Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.

Latest version: 15.5.3
View GitHub

How to Install the Toxiproxy Helm Chart

Add Chart Repository to Helm

helm repo add deliveryhero https://charts.deliveryhero.io/

Install Chart

helm install my-toxiproxy deliveryhero/toxiproxy --version 1.3.6

Does the Toxiproxy Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 5 of the best practices recommended by the industry.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Prevent ConfigMap security vulnerability (CVE-2021-25742)

1 occurrences:

  • metadata.name: release-name-toxiproxy-config (kind: ConfigMap)

💡 Missing property object `allow-snippet-annotations` - set it to "false" to override default behaviour

Learn how to fix the issue here

❌ Ensure each container has a configured memory request

1 occurrences:

  • metadata.name: release-name-toxiproxy (kind: Deployment)

💡 Missing property object `requests.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU request

1 occurrences:

  • metadata.name: release-name-toxiproxy (kind: Deployment)

💡 Missing property object `requests.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured memory limit

1 occurrences:

  • metadata.name: release-name-toxiproxy (kind: Deployment)

💡 Missing property object `limits.memory` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

❌ Ensure each container has a configured CPU limit

1 occurrences:

  • metadata.name: release-name-toxiproxy (kind: Deployment)

💡 Missing property object `limits.cpu` - value should be within the accepted boundaries recommended by the organization

Learn how to fix the issue here

This is some text inside of a div block.
This is some text inside of a div block.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started