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
The values-ha file doesn't set a CPU limit for linkerd-proxy, while the documentation states the following:
Should I interpret this as "The recommended production setting is to run linkerd-proxy in single thread, without cpu limits"?
Cause - If I do not set any kubernetes limits, and add that annotation, the container gets a cpu limit set.
Or should I read this as "Don't set kubernetes limits, but use annotations - which will then add limits for you"?
Ideally I'd like the proxy to not have any limit set, but still run multi-threaded..
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The values-ha file doesn't set a CPU limit for linkerd-proxy, while the documentation states the following:

Should I interpret this as "The recommended production setting is to run linkerd-proxy in single thread, without cpu limits"?
Cause - If I do not set any kubernetes limits, and add that annotation, the container gets a cpu limit set.
Or should I read this as "Don't set kubernetes limits, but use annotations - which will then add limits for you"?
Ideally I'd like the proxy to not have any limit set, but still run multi-threaded..
Beta Was this translation helpful? Give feedback.
All reactions