You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/contour/README.md
+2-18Lines changed: 2 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,26 +29,8 @@ These commands deploy contour on the Kubernetes cluster in the default configura
29
29
30
30
> **Tip**: List all releases using `helm list` or `helm ls --all-namespaces`
31
31
32
-
## Installing CRDs
33
-
34
-
Contour and Gateway API CRDs are shipped in the separate `contour-crds` chart and should be installed once per cluster before installing or upgrading the main `contour` chart.
35
-
36
-
```console
37
-
helm install contour-crds contour/contour-crds
38
-
```
39
-
40
-
The `contour` chart no longer manages CRDs directly, allowing multiple Contour deployments without reapplying cluster-scoped resources.
41
-
42
32
## Configuration and installation details
43
33
44
-
## Developing and testing locally
45
-
46
-
- Lint both charts from the repo root: `helm lint charts/contour-crds charts/contour`.
47
-
- Install CRDs once into a dev cluster (namespace is arbitrary for CRDs): `helm install contour-crds ./charts/contour-crds --namespace contour-system --create-namespace`.
48
-
- Install or upgrade the main chart for a test release: `helm upgrade --install contour ./charts/contour --namespace projectcontour --create-namespace`.
49
-
- Render templates without touching a cluster: `helm template contour ./charts/contour -f my-values.yaml`.
50
-
- When cleaning up, `helm uninstall contour` (leave `contour-crds` in place if other Contour installs exist).
51
-
52
34
### Resource requests and limits
53
35
54
36
The chart allows setting resource requests and limits for all containers inside the chart deployment. These are defined in the `resources` value (see the parameters table). Setting requests is essential for production workloads and these should be adapted to your specific use case.
@@ -236,6 +218,7 @@ To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.
236
218
| `contour.extraArgs` | Extra arguments passed to Contour container | `[]` |
237
219
| `contour.resourcesPreset` | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if contour.resources is set (contour.resources is recommended for production). | `nano` |
238
220
| `contour.resources` | Set container requests and limits for different resources like CPU or memory (essential for production workloads) | `{}` |
221
+
| `contour.manageCRDs` | Manage the creation, upgrade and deletion of Contour CRDs. | `false` |
239
222
| `contour.envoyServiceNamespace` | Namespace of the envoy service to inspect for Ingress status details. | `""` |
240
223
| `contour.envoyServiceName` | DEPRECATED: use envoy.service.name | `""` |
241
224
| `contour.leaderElectionResourceName` | Name of the contour (Lease) leader election will lease. | `""` |
@@ -548,6 +531,7 @@ To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.
0 commit comments