stijnbrouwers opened a new pull request, #9:
URL: https://github.com/apache/tika-helm/pull/9
With K8s v1.25 being available, the HPA apiVersion has changed.
```
apiVersion: autoscaling/v2beta1
```
is deprecated in favour of
```
apiVersion: autoscaling/v2
```
The
stijnbrouwers commented on PR #9:
URL: https://github.com/apache/tika-helm/pull/9#issuecomment-1453508809
FYI, @lewismc
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
lewismc merged PR #4:
URL: https://github.com/apache/tika-helm/pull/4
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org
[
https://issues.apache.org/jira/browse/TIKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696235#comment-17696235
]
ASF GitHub Bot commented on TIKA-3452:
--
lewismc merged PR #4:
URL:
[
https://issues.apache.org/jira/browse/TIKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-3452.
Resolution: Fixed
> java.nio.file.FileSystemException Read-only file system
>
[
https://issues.apache.org/jira/browse/TIKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated TIKA-3452:
---
Fix Version/s: 2.7.0
(was: 2.0.0-BETA)
>
lewismc commented on PR #4:
URL: https://github.com/apache/tika-helm/pull/4#issuecomment-1453865110
@frascu very shortly I will try to perform the release over the weekend. Do
you want me to set the Tika version to `latest-full` or should we be aligning
the Helm Chart against the docker
[
https://issues.apache.org/jira/browse/TIKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696236#comment-17696236
]
ASF GitHub Bot commented on TIKA-3452:
--
lewismc commented on PR #4:
URL:
lewismc merged PR #9:
URL: https://github.com/apache/tika-helm/pull/9
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org
lewismc commented on PR #9:
URL: https://github.com/apache/tika-helm/pull/9#issuecomment-1453867952
Excellent @stijnbrouwers thanks.
Same question as I asked @frascu , when I make the new Helm Chart release,
should we align the Helm Chart version with the upstream Dockerhub tika version
https://www.youtube.com/watch?v=O8sjtnXgu98
frascu commented on PR #4:
URL: https://github.com/apache/tika-helm/pull/4#issuecomment-1454242652
I would prefer to align the helm chart to the docker tags, but feel free to
decide the best strategy, I need at least a new version of helm chart having
the last changes.
--
This is an
Nice!
On Fri, Mar 3, 2023, 3:26 PM Tim Allison wrote:
> https://www.youtube.com/watch?v=O8sjtnXgu98
>
[
https://issues.apache.org/jira/browse/TIKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696358#comment-17696358
]
ASF GitHub Bot commented on TIKA-3452:
--
frascu commented on PR #4:
URL:
stijnbrouwers commented on PR #9:
URL: https://github.com/apache/tika-helm/pull/9#issuecomment-1453931179
@lewismc, personnaly, I like the appVersion in the chart.yaml file to be
equal to the tika version that's being used by default. Keeping the chart
version in sync is not necessary and
15 matches
Mail list logo
