-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metrics with type http brings the whole deployment config as query #185
Comments
Hi @lyudmilalala, thanks for raising this. If you are hitting one of your own endpoints that needs access to this resource information you can use a I think you are right though, some endpoints will not need this resource information at all (the example that you have been running is one of them, it just needs the random number, and it shouldn't be exposing deployment information to random.org). Let me look at adding in a new configuration option that skips including any resource information in hooks. |
Thanks for quick reply @jthomperoo . According to the definition of RESTful APIs, Also, want to quickly ask, if the metrics shell exit with status not equals to 0 because of error, will the evaluate script still be called, or the evaluation step will just be skipped? Hope this project becomes better. |
Kubernetes Details (
kubectl version
):K8s in Docker on Windows 10
K8s version v1.27.2
Bug & Reproduce
I try the get metrics by http request example.
It works properly if everything are unchanged. However, if I add more features into the
deployment.yaml
, make it as belowCPA will give out the error
I think it is because the deployment configuration is appended as a query parameter of the request. This conjecture can be proved by another line of error log mentioned below.
Currently, for workaround, I write a python shell script, and send requests there.
Expected behavior
The
deployment.yaml
used in production will probably be longer than the one I list above, so I think we should avoid to take it in query, or at least give users a choice not to send it by query.Additional context - The other error log
If everything are unchanged, the following error will be printed after running CPA for around 10 minutes. I think it is caused by frequestly request to https://www.random.org/integers/, and won't regard it as a client-side issue.
The text was updated successfully, but these errors were encountered: