Open gafda opened 4 years ago
Hi @gafda
Thanks for the feedback !
Indeed, the current reservation usage is based on limits
whereas it should be based on requests
. Where you able to notice this via applications created outside of Portainer or via the advanced deployment method?
FYI, all applications created through the Portainer UI via the application creation view enforce a limit and request set to the same value (specified in the UI).
Regarding your arm64 request, please see: https://github.com/portainer/kubernetes-beta/issues/7#issuecomment-632481138
I learned kubernetes via CLI e stick to it for the most part even nowadays. For an overview and quicker checkup I usually use the k9s ( https://github.com/derailed/k9s ). So answering your questions, I manually created all of the k8s objects by hand, and then checked on the Portainer and noticed the values reported matched the limits instead of the reserved. :)
Regarding my arm64 request, it's not a priority or an actual necessity. I'm just trying to create my very own personal k8s cluster exclusively with 64bit SO & Apps :)
Bug description In the cluster section "Resource reservation" bar values are based on the ResourceLimits instead of the ResourceReservation values.
Expected behavior I excepted to either show ResourceLimits and ResourceReservation of at least show ResourceReservation correctly.
Steps to reproduce the issue:
Technical details:
Additional context Being a sideuser of Portainer for Docker (marvelous work btw) I just had to try it on my local cluster of Raspberry Pi's. Are you considering creating a docker image of Portainer-k8s for arm64?