mhausenblas / right-size-guide Goto Github PK

We wanted to test the usage of APIs hosted in Kubernetes. I came to know that the feature is not available and the tool can be used to test locally hosted APIs. So I am trying to run a Docker image in my developer machine and test the API using localhost. But it is not working as expected. The steps performed is given below

1. Created Docker image with Python Django image to expose Rest API
2. Started the container in the developer machine

docker run -p 8090:8080 djangoimage:1.0
Watching for file changes with StartReloader

3. Started duplicate session and verified the API

curl -i http://127.0.0.1:8090/
Hello World. You are at the index page

4. Executed below rsg command

rsg --target test/test --api-path / --api-port 8090
Launching test/test for idle state resource usage assessment
Found idle state resource usage. Memory 0 kb CPU: 0 ms

5. The docker is also throwing below error message in the first session
   ConnectionResetError: [Error 104] Connection reset by peer

Can you please look into the issue ? Can we use the tool to test Rest API created using Docker containers ?

Thanks
Raju Sreenivasan

Team,
We are trying to use rsg cli to test resource allocation of API hosted in Kubernetes. The ingress URL is https://k8s-api.mycompany.com

command used
rsg --target test/test --api-path /k8s-api.mycompany.com --api-port 443

The output is
Get http://127.0.0.1:443/k8s-api.mycompany.com dial tcp 127.0.0.1:443 connect: connection refused

Can you please let us know if the tool can be used to analyze the K8S API ingress URL ?

Thanks
Raju Sreenivasan

Hi, I'd like to try your tool to estimate an appropriate pod limit and request but i don't get how to use it.
especially I do not understand what to input for the target.
what do you mean of $BINARY and $HTTP_URL_PATH here?

rsg --target $BINARY
[--api-path $HTTP_URL_PATH --api-port $HTTP_PORT --peak-delay $TIME_MS --sampletime-idle $TIME_SEC --sampletime-peak $TIME_SEC --export-findings $FILE --output json|openmetrics]

Example usage:
rsg --target test/test --api-path /ping --api-port 8080 2>/dev/null