You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar Issue https://github.com/newrelic/newrelic-infra-operator/issues/218
We are experiencing an issue where the New Relic Infrastructure Operator’s mutating webhook is unexpectedly removing the restartPolicy field from initContainers in pods created by CronJobs.
Although we have disabled sidecar injection, the webhook still modifies the pod spec, causing pods to fail to start properly when executed by CronJobs. This behavior is disruptive as it affects workloads running in AWS EKS Fargate.
Steps to Reproduce
- Deploy a CronJob that contains an initContainer with a restartPolicy set at the Pod level.
- When the CronJob executes, it creates a Job, which then creates a Pod.
- The New Relic webhook removes restartPolicy from initContainers when the Pod is created.
- The Pod fails to start properly, even though no sidecar is injected.
- The issue persists even after applying infra-operator.newrelic.com/disable-injection: "true" to the CronJob.
Similar Issue
https://github.com/newrelic/newrelic-infra-operator/issues/218
We are experiencing an issue where the New Relic Infrastructure Operator’s mutating webhook is unexpectedly removing the
restartPolicy
field from initContainers in pods created by CronJobs.Although we have disabled sidecar injection, the webhook still modifies the pod spec, causing pods to fail to start properly when executed by CronJobs. This behavior is disruptive as it affects workloads running in AWS EKS Fargate.
Steps to Reproduce
Example
Logs
"patch.webhook.admission.k8s.io/round_0_index_5": "{\"configuration\":\"newrelic-bundle-newrelic-infra-operator\",\"webhook\":\"newrelic-infra-operator.newrelic.com\",\"patch\":[{\"op\":\"remove\",\"path\":\"/spec/initContainers/0/restartPolicy\"}],\"patchType\":\"JSONPatch\"}"
The text was updated successfully, but these errors were encountered: