Empty ingress resource created when all services in ingress.yaml are disabled

[spwoodcock]

Background

• The ingress.yaml template creates an ingress resource even when all services it manages (raster, vector, multidim, mockOidcServer, docServer) are disabled.
• This results in an ingress with paths: null, which is invalid.

In ArgoCD I get an error that the resource is out of sync:

Failed sync attempt to : one or more synchronization tasks completed unsuccessfully, reason: Ingress.networking.k8s.io "eoapi-ingress" is invalid: spec.rules[0].http.paths: Required value (retried 5 times).

Goals

• Am trying to deploy only the STAC element of eoAPI, so stac-fastapi will be served under the root path (no subdomains).

• For Argo I thought I could simply:

  ignoreDifferences:
    - group: networking.k8s.io
      kind: Ingress
      name: fair-eoapi-ingress
      jsonPointers:
        - /spec/rules/0/http/paths

• But that doesn't work. It would be nicer if the chart could be configured to not cause sync issues.

If this is confirmed and a desirable thing to fix, let me know if you would prefer I make a PR for it 🙏

[pantierra]

Hi @spwoodcock. Thanks for bringing this up. I do think one should be able to only set up the STAC API. The challenge i see currently, the chart has two separate ingress templates:

• ingress.yaml: for services that need path stripping (raster, vector, multidim, mockOidcServer, docServer)
• ingress-no-prefix.yaml for services that handle their own routing (stac, browser)

STAC can be correctly configured in ingress-no-prefix.yaml, but ingress.yaml would be still being created even when all of its services were disabled, resulting in the empty paths: array.

I think I would like to think a bit about a more elegant solution, or if we just fix the current approach. Do you have any suggestions?