General Next Steps And Enhancements to Prioritize

[ranchodeluxe]

This repository hasn't really been touched since November and needs some love. Here is my priority list for us to talk about and ticket further with @j08lue and @ividito:

0. Write IaC and documentation about using cloud provider storage solutions (RDS and GCD):

   • add optionally-enabled cloud provider storage to Terraform
   • documentation is already started here but needs to be totally redone
   • make sure service charts and configs take extraSecret and extraConfig to be mounted into the pods like JH does for extra* things
   • relevant to Use external PostgreSQL database #65 (reply in thread)

1. It's typical for most demo k8s installs to default to using an in-memory database but I think our default should just install Crunchy's Postgres Operator . Then folks have high-available k8s alternative already set up to go

2. move CI/CD tests to using k3's. Even though we currently can have parallel tests deploy parallel eoapi-k8s and run against a real cloud provider k3's would be more reliable and just use the CI runners

3. We need to automate releases using GH Actions for releases:

   • releases should also auto-generate a documentation site on GH pages

4. The support helm chart is crucial to set up Prometheus and certain auto-scaling and needs to be it's own separate chart release:

   • we need to make sure by default this seamlessly gives us the Grafana dashboard and ability to auto-scale by request

5. Write documentation about generating certs for TLS using Let'sEncrypt. There are manual steps for this like running let's encrypt CLI and generating secrets. The current helm addition PR also conflates the idea of staging and prod

[ranchodeluxe]

Finally got around to ticketing these:

1. Add Crunchy Postgres Operator as Default #77
2. https://github.com/developmentseed/eoapi-k8s/issues/80
3. Automate Releases #39
4. https://github.com/developmentseed/eoapi-k8s/issues/81

@ividito: let me know which ones you're interested in and we can start jamming on them

[ividito]

I can pick up 2 and 3 - possibly overlapping with 4, if we start expanding on the eoapi-support CI.