This pr addressing the walmart issue. Their systems hitting performance issues after agent update. As part of agent cgroup init, we use system daemon-load to update cgroup settings for agent service. Since it's global command, it's resetting the CPU affinity that that walmart Kubernetes uses. We observed this in ubunut22 specific containerD version.
Current fix targeting to walmart scenario
Changes are:
Their systems(uv22) come with cgroupV2 and we don't support v2 yet, so we can stop creating unit files as part of cgroup init that will avoid daemon-reload. Move the setup slices after cgroupv2 check
Remove the unit file creation for logcollector and that was the reason setup slice setup was added before cgroupsv2 check and can run independently without agent cgroupv2 support
Removed daemon-load in firewall service setup
Issue #
PR information
[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made
Description
This pr addressing the walmart issue. Their systems hitting performance issues after agent update. As part of agent cgroup init, we use system daemon-load to update cgroup settings for agent service. Since it's global command, it's resetting the CPU affinity that that walmart Kubernetes uses. We observed this in ubunut22 specific containerD version.
Current fix targeting to walmart scenario
Changes are:
Issue #
PR information
Quality of Code and Contribution Guidelines