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/camunda-platform-8.8/README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -608,7 +608,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
608
608
| `identity.sidecars` | can be used to attach extra containers to the identity deployment | `[]` |
609
609
| `identity.initContainers` | can be used to set up extra init containers for the application Pod | `[]` |
610
610
| `identity.fullURL` | can be used when Ingress is configured (for both multi and single domain setup). | `""` |
611
-
| `identity.contextPath` | can be used to make Management Identity web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `/identity` |
611
+
| `identity.contextPath` | can be used to make Management Identity web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `""` |
612
612
| `identity.podAnnotations` | can be used to define extra Management Identity pod annotations | `{}` |
613
613
| `identity.podLabels` | can be used to define extra Management Identity pod labels | `{}` |
614
614
| `identity.logging` | configuration for the Management Identity logging. This template will be directly included in the Management Identity configuration YAML file | |
@@ -815,7 +815,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
815
815
| `console.tls.existingSecret` | The name of the existing secret that contains the TLS certificates. Each key of the secret corresponds to a certificate filename, and each value of a key corresponds to the content of the certificate file. | `""` |
| `console.keycloak.realm` | Specifies the Keycloak realm used for authentication. | `camunda-platform` |
818
-
| `console.contextPath` | can be used to make Console web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `/` |
818
+
| `console.contextPath` | can be used to make Console web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `""` |
819
819
| `console.initContainers` | can be used to set up extra init containers for the application Pod | `[]` |
820
820
| `console.podAnnotations` | can be used to define extra Console pod annotations | `{}` |
821
821
| `console.podLabels` | can be used to define extra Console pod labels | `{}` |
@@ -892,7 +892,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
892
892
| `webModeler.image.registry` | can be used to set the Docker registry for the WebModeler images (overwrites global.image.registry) | `""` |
893
893
| `webModeler.image.tag` | can be used to set the Docker image tag for the WebModeler images (overwrites global.image.tag) | `8.8.0-alpha8` |
894
894
| `webModeler.image.pullSecrets` | can be used to configure image pull secrets, see https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod | `[]` |
895
-
| `webModeler.contextPath` | can be used to make WebModeler available on a custom sub-path. This is mainly used to run the Camunda web applications under a single domain. | `/modeler` |
895
+
| `webModeler.contextPath` | can be used to make WebModeler available on a custom sub-path. This is mainly used to run the Camunda web applications under a single domain. | `""` |
896
896
897
897
### WebModeler - RestAPI Parameters
898
898
@@ -1220,7 +1220,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
1220
1220
| `connectors.sidecars` | can be used to attach extra containers to the connectors deployment | `[]` |
1221
1221
| `connectors.initContainers` | can be used to set up extra init containers for the application Pod | `[]` |
1222
1222
| `connectors.replicas` | number of Connectors replicas | `1` |
1223
-
| `connectors.contextPath` | can be used to make Connectors web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `/connectors` |
1223
+
| `connectors.contextPath` | can be used to make Connectors web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `""` |
1224
1224
| `connectors.podAnnotations` | can be used to define extra Connectors pod annotations | `{}` |
1225
1225
| `connectors.podLabels` | can be used to define extra Connectors pod labels | `{}` |
1226
1226
| `connectors.logging` | configuration for the Connectors logging. This template will be directly included in the connector configuration YAML file | |
@@ -1432,7 +1432,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
1432
1432
| `orchestration.ingress.grpc.tls` | configuration for tls on the ingress resource https://kubernetes.io/docs/concepts/services-networking/ingress/#tls | |
1433
1433
| `orchestration.ingress.grpc.tls.enabled` | if true, then tls is configured on the ingress resource. If enabled the Ingress.host need to be defined. | `false` |
1434
1434
| `orchestration.ingress.grpc.tls.secretName` | defines the secret name which contains the TLS private key and certificate | `camunda-platform-orchestration-grpc` |
1435
-
| `orchestration.contextPath` | can be used to make Orchestration Cluster web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `/orchestration` |
1435
+
| `orchestration.contextPath` | can be used to make Orchestration Cluster web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `""` |
1436
1436
| `orchestration.cpuThreadCount` | defines how many threads can be used for the processing on each broker pod | `3` |
1437
1437
| `orchestration.ioThreadCount` | defines how many threads can be used for the exporting on each broker pod | `3` |
1438
1438
| `orchestration.resources` | configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits | |
@@ -1553,7 +1553,7 @@ Please see the corresponding [release guide](../../docs/release.md) to find out
| `optimize.sidecars` | can be used to attach extra containers to the optimize deployment | `[]` |
1556
-
| `optimize.contextPath` | can be used to make Optimize web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `/optimize` |
1556
+
| `optimize.contextPath` | can be used to make Optimize web application works on a custom sub-path. This is mainly used to run Camunda web applications under a single domain. | `""` |
1557
1557
| `optimize.configMap` | configuration which will be applied to the mounted config map. | |
1558
1558
| `optimize.configMap.defaultMode` | can be used to set permissions on created files by default. Must be an octal value between 0000 and 0777 or a decimal value between 0 and 511. | `754` |
1559
1559
| `optimize.podAnnotations` | can be used to define extra Optimize pod annotations | `{}` |
Copy file name to clipboardExpand all lines: charts/camunda-platform-8.8/test/integration/scenarios/chart-full-setup/values-integration-test-ingress-basic.yaml
Copy file name to clipboardExpand all lines: charts/camunda-platform-8.8/test/integration/scenarios/chart-full-setup/values-integration-test-ingress-keycloak.yaml
Copy file name to clipboardExpand all lines: charts/camunda-platform-8.8/test/integration/scenarios/chart-full-setup/values-integration-test-ingress-oidc.yaml
0 commit comments