Prevent SNR from installing/ remediating control plane nodes
13 views
Skip to first unread message
JamesG
unread,
Oct 15, 2025, 3:42:56 PM (5 days ago) Oct 15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to medik8s
Is it possible via configuration to disable SNR control plane remediation and/ or prevent daemonsets from being installed? I would like to prevent control plane remediation for right now. Ive been reading through the documentation and only see how to add additional tolerations not remove existing defaults.
Thanks! James
Carlo Lobrano
unread,
Oct 16, 2025, 3:28:52 AM (4 days ago) Oct 16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to medik8s
Hi James,
I think you could set the "remediation.medik8s.io/exclude-from-remediation" label on the nodes you want, and then manually delete the daemonsets on the same nodes. They won't be re-deployed, as per daemonset nodeAffinity configuration
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to medik8s
Close but no luck It looked like it was going to work. Applying the label did remove the daemonset from the master nodes but the remaining worker daemonsets started crashlooping after they were rolled.
Error for reference ```
ERROR setup problem running manager {"error": "Node master-00 has no matching Pod"} main.main /app/self-node-remediation/main.go:167 runtime.main /usr/lib/golang/src/runtime/proc.go:272
```
self-node-remediation v0.10.2
ocp 4.17.26/ 4.18.22
Carlo Lobrano
unread,
Oct 17, 2025, 10:46:11 AM (3 days ago) Oct 17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to medik8s
> {"error": "Node master-00 has no matching Pod"}
Did that actually cause any problem? That error message shouldn't prevent the other nodes to work