-
Reuben Pereira authored
- ETag caching will help reduce the load from polling the API. - Query parameters are not supported with ETag caching since the middleware only looks at the request path. Modify the frontend to work with path params We've changed the pod logs API to use path params instead of query params in order to support ETag caching. Simpify api replacing patterns - Use a single object as a parameter - Remove some code - Update specs Separate out html and json logs endpoints - Create separate APIs for the logs HTML page and the JSON endpoint that returns k8s logs. - Also correct the route for the JSON endpoint by adding the resource names to the route.
5c7a4307