[DatadogAgent] Unable to override topologySpreadConstraints

[starlightromero]

Describe what happened:

A user is unable to override topologySpreadConstraints on the DatadogAgent custom resource.

kubectl explain DatadogAgent.spec.override
GROUP:      datadoghq.com
KIND:       DatadogAgent
VERSION:    v2alpha1

FIELD: override <map[string]Object>


DESCRIPTION:
    <empty>
FIELDS:
  affinity	<Object>
    <no description>

  annotations	<map[string]string>
    <no description>

  containers	<map[string]Object>
    <no description>

  createRbac	<boolean>
    <no description>

  customConfigurations	<map[string]Object>
    <no description>

  disabled	<boolean>
    <no description>

  env	<[]Object>
    <no description>

  extraChecksd	<Object>
    <no description>

  extraConfd	<Object>
    <no description>

  hostNetwork	<boolean>
    <no description>

  hostPID	<boolean>
    <no description>

  image	<Object>
    <no description>

  labels	<map[string]string>
    <no description>

  name	<string>
    <no description>

  nodeSelector	<map[string]string>
    <no description>

  priorityClassName	<string>
    <no description>

  replicas	<integer>
    <no description>

  securityContext	<Object>
    <no description>

  serviceAccountName	<string>
    <no description>

  tolerations	<[]Object>
    <no description>

  volumes	<[]Object>
    <no description>

Describe what you expected:

topologySpreadConstraints could be modified

Steps to reproduce the issue:

Set topologySpreadContraints on the manifest and apply.

---
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  ...
spec:
  override:
    nodeAgent:
      topologySpreadConstraints:
      - maxSkew: 1
        topologyKey: topology.kubernetes.io/zone
        whenUnsatisfiable: ScheduleAnyway        

Additional environment details (Operating System, Cloud provider, etc):

[levan-m]

Hello, thanks for raising this question! Could you please submit a feature request in the Datadog Operator repo and close this one.

[alee2233]

Actually, the node agent is a daemonset, so topology spread constraints shouldn't apply right?

EDIT: TSCs would still be relevant for the other components like Cluster Agent

[starlightromero]

DataDog/datadog-operator#1530