Expose updateStrategy to make it configurable for cloudwatch agent and fluentbit

[varunch77]

Expose updateStrategy to make it configurable for cloudwatch agent and fluentbit (daemonset only)

Cloudwatch agent - output after helm upgrade:

---
# Source: amazon-cloudwatch-observability/templates/linux/cloudwatch-agent-custom-resource.yaml
apiVersion: cloudwatch.aws.amazon.com/v1alpha1
kind: AmazonCloudWatchAgent
metadata:
  name: cloudwatch-agent
  namespace: amazon-cloudwatch
spec:
  updateStrategy:
      type: OnDelete

---
# Source: amazon-cloudwatch-observability/templates/linux/cloudwatch-agent-custom-resource.yaml
apiVersion: cloudwatch.aws.amazon.com/v1alpha1
kind: AmazonCloudWatchAgent
metadata:
  name: cloudwatch-agent
  namespace: amazon-cloudwatch
spec:
  updateStrategy:
      type: RollingUpdate
      rollingUpdate:
        maxUnavailable: 1
        maxSurge: 0

FluentBit changes - output after helm upgrade --dry-run:

---
# Source: amazon-cloudwatch-observability/templates/linux/fluent-bit-daemonset.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: fluent-bit
  namespace: amazon-cloudwatch
  labels:
    k8s-app: fluent-bit
    version: v1
    kubernetes.io/cluster-service: "true"
spec:
    ...
    spec:
      ...
      priorityClassName: system-node-critical
      priorityClassName: system-node-critical
      updateStrategy:
        type: RollingUpdate
        rollingUpdate:
          maxUnavailable: 1
          maxSurge: 0
      ...

---
# Source: amazon-cloudwatch-observability/templates/linux/fluent-bit-daemonset.yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
 name: fluent-bit
 namespace: amazon-cloudwatch
 labels:
   k8s-app: fluent-bit
   version: v1
   kubernetes.io/cluster-service: "true"
spec:
   ...
   spec:
     ...
     priorityClassName: system-node-critical
     updateStrategy:
       type: OnDelete

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. ✅