Issue#27 pycsw single microservice

[mwallschlaeger]

Closes #27

📑 Description

ref #27

added pycsw microservice inspired by pycsw helm chart (https://github.com/geopython/pycsw/tree/master/docker/helm) with adoption to the style of this helm chart.

Implementation:

• nginx container forwarding traffic to pycsw via .Values.pycsw.endpoint url
• mappings.py taken from GeoNode codbase (https://github.com/GeoNode/geonode/blob/master/geonode/catalogue/backends/pycsw_local_mappings.py)
• pycsw.cfg taken from pycsw helm chart

ℹ Additional Information

[mwallschlaeger]

waiting for GeoNode/geonode#11319 . meanwhile you can use the following geonode image including the bugfix promoted inside the PR.

  image:
    # -- used geonode image
    name: mwall2bitflow/geonode
    # -- tag of used geonode image
    tag: '4.1.x-pycsw-hotfix'

[mwallschlaeger]

GeoNode/geonode#11319 got merged, so no reason to hold this back anymore

[ridoo]

Should we better include that configuration as is in the values.yml and embed the config via {{- include "pycsw.config" . | nindent 4 }}?

[ridoo]

Would be nice to have a link reference here, e.g. https://docs.pycsw.org/en/2.6.1/configuration.html

[ridoo]

Really the default?

[ridoo]

We do not have to resolve #64 first, but at least should have a look at the way how the config is embedded in the configMap