[dev-v2.9] rancher-logging 104.0.0 support resources on daemonsets

[ricoapon]

Issue

I did not report one (just created this PR) and couldn't find an existing issue.
EDIT: created rancher/rancher#46499 for this.

Problem

Rancher-logging instals DaemonSets, which did not have any way to limit resources. This gave problems on our Kubernetes cluster where the pods could use 50% of the node memory.

Solution

Make it possible to configure the resources on DaemonSets. Default should stay the same (no limits configured).

Engineering Testing

Manual Testing

I installed the Helm chart manually on our own cluster to check that the rke2 code works.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.

[github-actions]

Validation steps

• Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.

  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  

• Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
• Approve the PR to run the CI check.