Implement VPA/HPA(s) and Replicas

[ranchodeluxe]

Depends On

#41
#42

Background

In the far future it would be nice to set up folks immediately with the default k8s metrics server and HPA rules so they don't have to guess about this stuff. Given that these flows are IO bound that will only come from us load testing and understanding which metrics will trigger HPA auto scaling (request rate and memory likely)

AC

• k8s metric server
• HPA rules

[vincentsarago]

Given that the STAC service

you're talking about the database here (pgSTAC) ?

have two "raster" services -- one exposed via ALB and the internal one

I'm not sure to understand this

[ividito]

Given that the STAC service

you're talking about the database here (pgSTAC) ?

have two "raster" services -- one exposed via ALB and the internal one

I'm not sure to understand this

Greg's talking about the stac-fastapi service, which optionally refers to the titiler service here. IIUC external /raster requests will go through our ingress/ALB, but requests coming through that internal reference will not, which is where we might want to divide things up a bit more.

[vincentsarago]

The stac-fastapi service itself will not use the raster endpoint but just redirect to it: https://github.com/developmentseed/eoAPI/blob/main/runtime/eoapi/stac/eoapi/stac/extension.py#L92-L103
https://github.com/developmentseed/eoAPI/blob/main/runtime/eoapi/stac/eoapi/stac/extension.py#L79-L82

This is ONLY enable if the titiler endpoint environment is set in the stac-fastapi service https://github.com/developmentseed/eoAPI/blob/main/runtime/eoapi/stac/eoapi/stac/app.py#L58-L61

[ranchodeluxe]

Thanks for the context @vincentsarago ! I'll rework this ticket to mostly be about HPA when I get a chance