Update Webservice & NGinx pod config to follow latest recommendations
What does this MR do?
MR updates Webservice pod config to follow latest recommendations after recent Reference Architecture reviews for Webservice memory and NGinx placement:
- Webservice pod config has been updated to have a limit of 7G memory
- Default Webservice Pod counts have been adjusted slightly for 5k and 50k deployments
- Switched NGinx to be a daemonset on Webservice nodes for better scalability
- Updated docs with latest Pod config settings
- Added setting to set
maxUnavailable
config for each pod type - Fixed issue with
kube-prometheus-stack
deployments to include latest CRDs
Author's checklist
When ready for review, the Author applies the workflowready for review label and mention @gl-quality/get-maintainers
:
- Merge request:
-
Corresponding Issue raised and reviewed by the GET maintainers team. -
Merge Request Title and Description are up-to-date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline -
MR has no new security alerts in the widget from the Secret Detection
andIaC Scan (SAST)
jobs.
-
- Code:
-
Check the area changed works as expected. Consider testing it in different environment sizes (1k,3k,10k,etc.). -
Documentation created/updated in the same MR. -
If this MR adds an optional configuration - check that all permutations continue to work. -
For Terraform changes: set up a previous version environment, then run a terraform plan
with your new changes and ensure nothing will be destroyed. If anything will be destroyed and this can't be avoided please add a comment to the current MR.
-
-
Create any follow-up issue(s) to support the new feature across other supported cloud providers or advanced configurations. Create 1 issue for each provider/configuration. Contact the Quality Enablement team if unsure.
Edited by Grant Young