replaced custom CRD patches with property annotations

[AndrewChubatiuk]

use annotations to consistently trim same fields in all CRDs, for the rest use custom patches

[cubic-dev-ai]

1 issue found across 32 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="api/operator/v1beta1/vlogs_types.go">

<violation number="1" location="api/operator/v1beta1/vlogs_types.go:84">
P2: These markers do not add a property-level schema for VLogs because the enclosing `VLogsSpec` is already schemaless, leaving the VLogs CRD behavior unchanged. If this is intended to replace the VLogs CRD patch, the parent must become structural or the custom patch must remain; otherwise these annotations are ineffective metadata.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[vrutkovs]

I wonder if we can break up config/crd/patches/operator.victoriametrics.com_vlclusters.yaml into smaller patches: requestsLoadBalancer, volumeClaimTemplate etc so that we could unify reused parts across all objects?

[AndrewChubatiuk]

I wonder if we can break up config/crd/patches/operator.victoriametrics.com_vlclusters.yaml into smaller patches: requestsLoadBalancer, volumeClaimTemplate etc so that we could unify reused parts across all objects?

it's achieveable only with custom scripts as patches for CRs may have different property prefixes

[vrutkovs]

Ah, okay, sure - it seems feasible for some cases at least. I'll experiment with that and create a PR