search

GSA / data.gov

Main repository for the data.gov service
https://data.gov
Other
597 stars 93 forks source link

optimize egress app usage #4498

Open FuhuXia opened 11 months ago

FuhuXia commented 11 months ago

We have the 7 egress apps as listed below, each scaled to 2, in each of the 3 egress spaces (development-egress, staging-egress, and prod-egress).

That makes a total of 42 instances.

In the listed 7 apps, first one egress-proxy-gsa-datagov-prod and 2nd one proxy-gsa-datagov-prod-inventory are not being used. The rest are for catalog apps, all sharing the same allow/deby acl, therefore they can be combined into one app.

I think we only need one egress space, with 9 catalog egress apps, each scaled to 3. That is total 9 instances, less memory usage and much simplier structure.

nickumia commented 11 months ago

We've been talking about this for a while. It should be pretty straightforward, but will take some setup with network-policies and testing to make sure all apps are wired up correctly. This can be partly open-source with making the changes to code. I know I didn't want to work on this because there were always more pressing things going on. After prioritization, let me know if I can help with this.