geonetwork / geonetwork-helm-charts Goto Github PK

#3

By default:

• the datahub pod looks for the config at /etc/datahub/{{ .Values.configuration.override_directories.config_directory_override }}, so /etc/datahub/config ( https://github.com/geonetwork/geonetwork-helm-charts/blame/main/datahub/templates/datahub-deployment.yaml#L58)
• but the georchestra datadir is mounted at /etc/datahub, which means that the conf will be at /etc/datahub/datahub/conf

So they do not match.

I understand that datahub can be deployed independently of geOrchestra and that this only means changing a few values for the chart, but wouldn't it be great if it deployed out-of-the-box when used in a geOrchestra context ?

like in helm-georchestra
https://github.com/georchestra/helm-georchestra/blob/main/.github/workflows/helm-lint-and-test.yml

I'm using the helm chart and I modified only the ingress part to be publish it on my server

ingress:
  enabled: true
  annotations: 
    cert-manager.io/cluster-issuer: letsencrypt-http01-prod 
    nginx.ingress.kubernetes.io/proxy-buffer-size: "128k"
  hosts:
    - host: geonetwork.myhost.com
      paths:
        - "/datahub"
  tls: 
    - secretName: geonetwork-myhost-com-key-pair
      hosts:
        - geonetwork.myhost.com
  className: "external-nginx"

The application starts and it's available using https://geonetwork.myhost.com/datahub but in the homepage I receive an error

An error was received
Http failure response for https://geonetwork.myhost.com/geonetwork/srv/api/me: 404 Not Found

Is there some additional configuration in this chart that can be used to manage the relative path?

I believe commit #9cc4ccc broke the initialization.
The logs are telling me

bootstrap-datahub-configuration rm: unrecognized option '--depth'
A describe on the deployment indeed shows that the rm and git clone lines are merged, which explains the error

A missing ; ?

geonetwork/geonetwork-ui#507

here : https://github.com/geonetwork/geonetwork-helm-charts/blob/main/datahub/templates/tests/test-connection.yaml#L14

when deployed it wget : datahub:80 it should refere to datahub-datahub-svc

Currently, it's only possible to customize the configuration of datahub through a git repository.

Ideally, it would be great to offer the ability to provide a PVC for storing the configuration locally instead of a git repository.

(This feature wasn't provided in the first place because at Camptocamp it was more flexible to store the configuration files outside of a server in a Kubernetes cluster, and it's easier to manage configurations through a version control system)