-
Notifications
You must be signed in to change notification settings - Fork 216
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
faasd does not provide memory limits of functions in Canonicalize format #228
Comments
Could you submit a PR for initial review and testing? Alex |
I will work on this. |
Sorry, I think this issue is my bad 😓 I should have written a test case for the SI conversion aswell. Anyways @nitishkumar71 this is the problematic line that you looking for: There was a conversation about this on the PR aswell, you might find something useful there: Since the memory limit itself is working, only the format breaks. |
So we put in: 1Mi For this import What do these calls generate?
|
So just checked below lines in playground
and the output we received is
|
Is that ordering correct in the output? |
Yes. Including playground link. |
All the openfaas implementation should return the memory info in the Canonicalize format.
Expected Behaviour
faasd should return memory limits in Canonicalize i.e. 5000000 should be returned as 5M. We follow the same into faas-netes.
Current Behaviour
faasd Provides function memory limit in bytes.
Are you a GitHub Sponsor (Yes/No?)
Check at: https://github.com/sponsors/openfaas
List all Possible Solutions
We can follow the implementation for k8s
https://github.com/openfaas/faas-netes/blob/master/pkg/k8s/function_status.go#L38
https://github.com/openfaas/faas-netes/blob/master/vendor/k8s.io/api/core/v1/resource.go#L34
List the one solution that you would recommend
Steps to Reproduce (for bugs)
The text was updated successfully, but these errors were encountered: