[
https://issues.apache.org/jira/browse/TIKA-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132890#comment-18132890
]
ASF GitHub Bot commented on TIKA-5004:
--------------------------------------
tballison commented on PR #47:
URL: https://github.com/apache/tika-helm/pull/47#issuecomment-6442461136
My :robot: recommends:
```
- Restrict values to strings in the schema. Right now it uses
additionalProperties: true. Kubernetes label
values must be strings, and --set podLabels.team=true (or =123) gives an
unquoted bool or int. That passes the
schema and lint, then the API server rejects it at install time. Using
"additionalProperties": {"type":
"string"} catches it at template time.
- Selector-key collisions. If someone sets
podLabels."app.kubernetes.io/name", the label is emitted twice. The
later value wins, so the pod labels no longer match the Deployment
selector and the install fails with an
opaque "selector does not match template labels" error. Common charts
handle this with merge (selector labels
take precedence) or by documenting it. This one is minor and can wait
for a follow-up.
```
wdyt?
> Support pod labels
> ------------------
>
> Key: TIKA-5004
> URL: https://issues.apache.org/jira/browse/TIKA-5004
> Project: Tika
> Issue Type: Improvement
> Components: helm
> Reporter: Nils Griebner
> Priority: Trivial
>
> Hey,
> would be great if the helm chart could support pod labels, because we use
> alerting rules that depend on that. I'll provide a pull request for this.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
