eoapi-k8s Cleanup Recommendations

[emmanuelmathot]

Deprecated Components

• Deprecated Database Configuration: (after Unified PostgreSQL Configuration #209)
  • The db section in values.yaml is explicitly marked as DEPRECATED with comments indicating it's only for backward compatibility
  • Default setting is db.enabled: false as the project now uses PostgreSQL Operator/Cluster approach
  • Related resources in helm-chart/eoapi/templates/db/ directory (deployment.yaml, service.yaml, etc.) could be removed or archived

Obsolete Files

• Backup Ingress Configuration:
  • helm-chart/eoapi/ingress.bkup appears to be a backup of an old ingress template and is likely obsolete
  • Contains comments indicating it was the "ORIGINAL INGRESS TEMPLATE FROM helm create"
  • Not referenced elsewhere and can be safely removed

Documentation Issues

• Outdated Documentation References:
  • docs/helm-install.md references specific old chart versions (0.2.14, 0.1.13, 0.1.2) while the current version in Chart.yaml is 0.6.0
  • Documentation should be updated to reflect current versions and practices

Resource Configuration Issues

• Resource Naming Inconsistency: (fixed in Simplify PgSTAC Bootstrap Process #208)

  • In the pgstacboostrap job, there's a ConfigMap named pgstac-setup-config-{{ $.Release.Name }} which mounts Python scripts to /opt/initdb/python-scripts/
  • The ConfigMap populates from "initdb-data/*.py" files
  • This naming inconsistency could potentially lead to issues if files aren't found where expected

• Multiple Ingress Configurations: (to be fixed in Consolidate Multiple Ingress Implementations into a Single Configuration #205)

  • The project contains both nginx and traefik ingress configurations
  • While this appears intentional to support different ingress controllers, it might be worth evaluating if both are still actively used or if one approach should be preferred

Additional Items