logs: Reduce logs spamming and introduce levels

[oshoval]

What this PR does / why we need it:

• Add standard log levels.
• Remove repetitive reconciliation logs, those spammed badly and were not helpful.
  For example from a cluster that ran for a while:

❌ log.Print("reconciling NetworkAddonsConfig") - 2,585 occurrences
❌ log.Print("starting render phase") - 2,585 occurrences
❌ log.Print("starting rendering objects to delete phase") - ~2,585 occurrences
❌ log.Print("update was successful") - 98,230 occurrences
❌ log.Print("Successfully updated status conditions") - 5,193 occurrences

Special notes for your reviewer:

Release note:

None

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[oshoval]

Some logs that might worth to investigate on follow-ups.
Easier to spot them now, once it is cleaner.
there might be more, just took those 3 as example.

1. seems that need to change 2nd container port name (KSD)

{"level":"info","ts":"2025-11-19T14:34:41Z","msg":"spec.template.spec.containers[1].ports[0]: duplicate port name \"healthport\" with spec.template.spec.containers[0].ports[1], services and probes that select ports by name will use spec.template.spec.containers[0].ports[1]"}

Note that i dont see it on KCLI, just on k8s.

2. Understand what are those 14 objs (actually it doesnt remove nothing at the end, maybe those are secrets and such that are later ignored)

{"level":"info","ts":"2025-11-19T14:37:42Z","logger":"render","msg":"object removal render phase done","objectsToRemove":14}

those are the oldKNMStateObjects,oldIPAMControllerPasstObjects
causing this print to be periodic, we can fix it on a follow-up either by dropping them in case 3 versions passed, or by ignoring the count if its only them.
Even easier, i am raising it to V(1).

{"level":"info","ts":"2025-11-19T14:37:42Z","msg":"unknown field \"spec.template.spec.securityContext.readOnlyRootFilesystem\""}

should be moved to the container (but need to be tested that it still works afterwards)
we should make it fatal instead warning (maybe on the first one as well)

{"level":"info","ts":"2025-11-20T10:57:51Z","msg":"spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[1].preference.matchExpressions[0].key: node-role.kubernetes.io/master is use \"node-role.kubernetes.io/control-plane\" instead"}

we do have both, maybe we can remove the deprecated one, in case its not needed anymore for BWC

2,3 repeat each reconcile before this PR

cc @RamLavi fyi please

[oshoval]

/test pull-e2e-cluster-network-addons-operator-macvtap-cni-functests

[RamLavi]

Hey, I think it's a great idea to introduce leveled logs.
Could you have it configurable on the operator via some flag? This way, the could control how much logging they see.

[oshoval]

Hey, I think it's a great idea to introduce leveled logs. Could you have it configurable on the operator via some flag? This way, the could control how much logging they see.

done

[oshoval]

/hold need to fix something

[oshoval]

/hold cancel

[oshoval]

/retest

[oshoval]

updated findings to #2491 (comment)

the 3rd issue is a real bug, the first is nice to fix as well, but self healing

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[oshoval]

changes: Reduce verbosity of repetitive logs

[oshoval]

unrelated to this PR
on Kcli i see this, fyi @RamLavi
maybe i am doing something wrong, but linux-bridge is installed on OpenShift

{"level":"info","ts":"2025-11-20T10:57:50Z","msg":"would violate PodSecurity \"restricted:latest\": privileged (container \"cni-plugins\" must not set securityContext.privileged=true), seLinuxOptions (pod set forbidden securityContext.seLinuxOptions: type \"spc_t\"), allowPrivilegeEscalation != false (container \"cni-plugins\" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container \"cni-plugins\" must set securityContext.capabilities.drop=[\"ALL\"]), restricted volume types (volume \"cnibin\" uses restricted volume type \"hostPath\"), runAsNonRoot != true (pod or container \"cni-plugins\" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container \"cni-plugins\" must set securityContext.seccompProfile.type to \"RuntimeDefault\" or \"Localhost\")"}

[oshoval]

point 3 of the above issues is fixed by #2497

[RamLavi]

/lgtm

[oshoval]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oshoval

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [oshoval]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment