DataDog/helm-charts

Remove allowedFlexVolumes from SCC or add possibility on values.yaml to configure it

Open

#1,789 opened on Apr 1, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (1,048 forks)auto 404
chart/datadoggood first issuestale

Repository metrics

Stars
 (418 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi Folks,

When using the chart on openshift, and using GitOPS (like ArgoCD), it will constantly show it is out of sync because you set allowedFlexVolumes here:

https://github.com/DataDog/helm-charts/blob/b9b9b80c562531b0e89b194c85b092c39749e592/charts/datadog/templates/agent-scc.yaml#L40 .

And since you are adding an empty value, Openshift will delete it from the SCC causing it to be out of sync with your code.

Potential Solutions 1- Add a parameter on values.yaml so people can actually add values to it 2- Just remove the allowedFlexVolumes line from the SCC, since Openshift will not use it

Source: https://access.redhat.com/solutions/7040709

Image

See if that makes sense, the fixes shouldn't affect anybody, just get in sync with the end state in the cluster.

Best Regards, Filipe

Contributor guide

Research direction
Modify the SCC template in the Helm chart to either remove the allowedFlexVolumes line or add a values.yaml parameter to configure it.
Tech stack
None
Domain
devopsinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HelmOpenShift
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70