Odigos v1.37.0 introduces breaking changes to container privilege settings

The release of Odigos v1.37.0, as noted in the project's GitHub release notes, includes several breaking changes that alter default container privilege behavior. Specifically, the odiglet and data-collection containers now run as non-privileged by default. Operators who wish to restore the previous privileged behavior must explicitly set the flags `odiglet.odiglet.privileged=true` and `odiglet.dataCollection.privileged=true`. Additionally, the `odiglet.unPrivileged` flag has been replaced by per-container flags to clarify their scope. Another notable change is that the `k8s-csi-driver` mount method now requires `odiglet.odiglet.privileged=true`. These adjustments aim to enhance security while providing more granular control over container privilege settings.

Operators should carefully review their configurations before upgrading, especially if their workloads rely on privileged containers or use the `k8s-csi-driver` mount method. The shift to non-privileged defaults may disrupt existing setups that assume elevated privileges, potentially causing failures in instrumentation or data collection workflows. Testing the upgrade in a staging environment and validating the impact on workloads is strongly recommended to avoid unexpected downtime.