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
In the K8S cluster managed by the rancher, nginx-proxy is used on the worker node for highly available components to access the apiserver。However, the number of processes enabled by nginx-proxy on the worker node is the number of machine cores by default, and the number of my machine cores is 128. This way, too many processes are enabled. However, nginx-proxy is automatically managed by the rancher. How to change the default configuration of nginx proxy's worker processes?
Useful
Info
Versions
Rancher v2.5.12 UI: v2.5.12
The text was updated successfully, but these errors were encountered:
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.
In the K8S cluster managed by the rancher, nginx-proxy is used on the worker node for highly available components to access the apiserver。However, the number of processes enabled by nginx-proxy on the worker node is the number of machine cores by default, and the number of my machine cores is 128. This way, too many processes are enabled. However, nginx-proxy is automatically managed by the rancher. How to change the default configuration of nginx proxy's worker processes?
v2.5.12
UI:v2.5.12
The text was updated successfully, but these errors were encountered: