jklein
6295f4b9c1
Tika has no Ingress, so the notes lead with the cluster-internal URL, the Service-port-80 to container-port-9998 mismatch a consumer has to get right, and /parsers as the direct answer to "why did this file come back empty". Two warnings come from measuring the running container rather than from reading the values file: - The image tag has to keep its "-full" suffix. That variant is where Tesseract 5.5.0 and the extra parsers live; the plain image carries no tesseract binary at all, so dropping the suffix does not fail loudly, it just stops OCR and returns empty text for scans. - The JVM never sees the container limit. It starts without -Xmx and derives its heap from the limit at MaxRAMPercentage=25, so the number worth sizing against is a quarter of it. The heap figure is computed from the effective limit through the chart's own null-safe effectiveResources helper, so an erased resources: block still prints the defaults the container actually receives instead of dropping the paragraph. Refs #43.
10 lines
228 B
YAML
10 lines
228 B
YAML
apiVersion: v2
|
|
name: apache-tika
|
|
description: A Helm chart to deploy Apache Tika on Kubernetes
|
|
icon: https://www.apache.org/logos/res/tika/default.png
|
|
|
|
type: application
|
|
|
|
version: 9.1.0+up3.3.1.0.full
|
|
appVersion: "3.3.1.0-full"
|