You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "stijnbrouwers (via GitHub)" <gi...@apache.org> on 2023/03/03 13:06:29 UTC
[GitHub] [tika-helm] stijnbrouwers opened a new pull request, #9: feat(hpa): Allow setting apiVersion through values file
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 change still uses the same default value for the apiVersion as before (since not everyone will have migrated to v1.25 yet) but it's now possible to change the value through the values-file
--
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-unsubscribe@tika.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tika-helm] stijnbrouwers commented on pull request #9: feat(hpa): Allow setting apiVersion through values file
Posted by "stijnbrouwers (via GitHub)" <gi...@apache.org>.
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 maybe even difficult or impossible since there might be multiple chart updates during a single version.
An automatic build based on the upstream would indeed be ideally, I'll try to keep it in mind for a nice future project since I don't have the time for it atm either :-)
Thanks for merging btw!
--
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-unsubscribe@tika.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tika-helm] stijnbrouwers commented on pull request #9: feat(hpa): Allow setting apiVersion through values file
Posted by "stijnbrouwers (via GitHub)" <gi...@apache.org>.
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 unsubscribe, e-mail: dev-unsubscribe@tika.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tika-helm] lewismc commented on pull request #9: feat(hpa): Allow setting apiVersion through values file
Posted by "lewismc (via GitHub)" <gi...@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 or simply make it `latest-full`? Any thoughts...? Ideally I would like to automate the Helm Chart releases based on new upstream Docker releases but I don't really have time to implement that right now.
--
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-unsubscribe@tika.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tika-helm] lewismc merged pull request #9: feat(hpa): Allow setting apiVersion through values file
Posted by "lewismc (via GitHub)" <gi...@apache.org>.
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-unsubscribe@tika.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org