Azure || Defining Container Limits
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [YESNO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [YES]
What is the current behavior?
- Container limits for CPU and Memory resources are not set for Storage Service Containers on Azure.
What is the new/expected behavior?
- Defined Memory limits and set to 2Gi
- Defined CPU requests and limits and set it to 500m and 1 respectively.
- Increased number of tomcat threads.
- Added JVM parameters to change Min and MAX heap configuration.
Have you added/updated Unit Tests and Integration Tests?
- N/A
Any other useful information
To be merged after - osdu/platform/deployment-and-operations/infra-azure-provisioning!221 (merged)
Edited by Krishna Nikhil Vedurumudi