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
| livenessProbe.successThreshold | int |`1`| Minimum consecutive successes for the probe to be considered successful after having failed. Minimum value is 1. |
248
248
| livenessProbe.terminationGracePeriodSeconds | int |`30`| Optional duration in seconds the pod needs to terminate gracefully upon probe failure. Minimum value is 1. |
249
249
| livenessProbe.timeoutSeconds | int |`10`| Number of seconds after which the probe times out. Minimum value is 1. |
| logging.file.threshold | string |`"ALL"`| The log level of the file appender. |
272
272
| logging.level | string |`"INFO"`| The log level of the root category, which is used as the default log level for all categories. |
273
273
| logging.mdc | object |`{}`| Configuration for MDC (Mapped Diagnostic Context). Values specified here will be added to the log context of all incoming requests and can be used in log patterns. |
274
-
| logging.requestIdHeaderName | string |`"Polaris-Request-Id"`| The header name to use for the request ID. |
274
+
| logging.requestId | object |`{"generator":{"type":"default"},"headerName":"Polaris-Request-Id"}`| Configuration for request IDs. |
275
+
| logging.requestId.generator.type | string |`"default"`| The type of the request ID generator to use. |
276
+
| logging.requestId.headerName | string |`"Polaris-Request-Id"`| The name of the request header that contains the request ID. If no such header is found, a new ID will be generated using the configured generator. |
275
277
| managementService | object |`{"annotations":{},"clusterIP":"None","externalTrafficPolicy":null,"internalTrafficPolicy":null,"ports":[{"name":"polaris-mgmt","nodePort":null,"port":8182,"protocol":null,"targetPort":null}],"sessionAffinity":null,"trafficDistribution":null,"type":"ClusterIP"}`| Management service settings. These settings are used to configure liveness and readiness probes, and to configure the dedicated headless service that will expose health checks and metrics, e.g. for metrics scraping and service monitoring. |
276
278
| managementService.annotations | object |`{}`| Annotations to add to the service. |
277
279
| managementService.clusterIP | string |`"None"`| By default, the management service is headless, i.e. it does not have a cluster IP. This is generally the right option for exposing health checks and metrics, e.g. for metrics scraping and service monitoring. |
0 commit comments