Replies: 1 comment
-
Intended yes, but it has been used for only a few different use cases so far. The more it is great to see you setting it up in your environment. I see this as a chance to make it more flexible and configurable as you suggest. We can definitively identify the missing pieces you have and address them to improve the helm charts. Feel also free to propose code suggestions in PRs for anything you will need on the way. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to deploy eoapi on eoxhub via this helm chart, but in our environment, we need a lot of specific settings, such as:
--root-path
for stac-api and titiler (this can probably be achieved by including it inraster.command
and settingingress.className
to an empty string or so (we don't the helm bundled ingress here)Is this eoapi helm chart intended to be applicable for a very broad set of use cases?
If so, i would suggest adding values for most fields, which is the strategy that many popular charts take, such as this grafana one (just to name one example):
https://artifacthub.io/packages/helm/grafana/grafana
https://github.com/grafana/helm-charts/blob/main/charts/grafana/templates/service.yaml
Beta Was this translation helpful? Give feedback.
All reactions