You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove memory metric from Istio HPA for ingress gateway for regular profile. For light profile set max replicas for ingress gateway to 1 and disable autoscale. Execute performance tests to rule out OOM.
Reasons
DoD:
[ ] Provide unit and integration tests.
Provide documentation.
Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
[ ] If you changed the resource limits, explain why it was needed.
If the default configuration of Istio Operator has been changed, you performed a manual upgrade test to verify that the change can be rolled out correctly.
[ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
No significant raise in memory usage was seen, and the memory level stayed very far from the set limit, meaning that there should be no risk of OOMKills happening.
On light installation, when the replicaNumber is limited to 1, the pod get's CPU bound before it could get up to the memory limit, as CPU rises significantly faster.
I limited maxreplicas from 5 to 1 instead of disabling autoscaling to make sure that configuration from Istio CR is still possible
Description
Remove memory metric from Istio HPA for ingress gateway for regular profile. For light profile set max replicas for ingress gateway to 1 and disable autoscale. Execute performance tests to rule out OOM.
Reasons
DoD:
[ ] Provide unit and integration tests.[ ] If you changed the resource limits, explain why it was needed.[ ] Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.Attachments
istio/internal/istiooperator/istio-operator.yaml
Line 72 in 6001548
istio/internal/istiooperator/istio-operator-light.yaml
Line 63 in 6001548
istio/internal/istiooperator/istio-operator-light.yaml
Line 199 in 6001548
PR
The text was updated successfully, but these errors were encountered: