Debug toolbox in a sidecar container
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
This page shows how you can add a sidecar container with debug tools installed.
|
||||
|
||||
The debug sidecar container will have access to the same resources as your app container, so you don't have to inflate your app container with debug tools.
|
||||
|
||||
The following example adds a default debug container (a debian image) to your deployment, and you can verify that this container will have access to the defined volume.
|
||||
|
||||
```yaml
|
||||
debugSidecarEnabled: true
|
||||
|
||||
volumes:
|
||||
- name: data
|
||||
path: /data
|
||||
size: 1Gi
|
||||
storageClass: local-path
|
||||
```
|
||||
|
||||
Check the Kubernetes manifest:
|
||||
|
||||
```bash
|
||||
helm template my-release onechart/onechart -f values.yaml
|
||||
```
|
||||
@@ -140,3 +140,4 @@ nav:
|
||||
- Cron job: examples/cron-job.md
|
||||
- Feature branch deploys: examples/feature-branch-deploys.md
|
||||
- Prometheus monitoring rules: examples/prometheus-monitoring-rules.md
|
||||
- Debug toolbox in a sidecar: examples/debugSidecar.md
|
||||
|
||||
Reference in New Issue
Block a user