Summary

The feast-operator's Owns() calls create cluster-wide informers for ConfigMaps, Deployments, Services, and other resource types. On clusters with a large number of these objects, the informer cache can grow beyond the operator's 256Mi memory limit, causing OOMKill and restarts.

Changes

ByObject label selectors for all owned resource types

Restrict informer caches to only objects with app.kubernetes.io/managed-by: feast-operator. Covers all 10 owned types: ConfigMap, Deployment, Service, ServiceAccount, PVC, RoleBinding, Role, CronJob, HPA, PDB. Extracted into newCacheOptions() for clarity.

DefaultTransform: cache.TransformStripManagedFields()

Strip managedFields from all cached objects, reducing per-object memory footprint by ~30-50%.

GOMEMLIMIT=230MiB

Set Go runtime soft memory limit (90% of 256Mi container limit). Triggers GC pressure before hard OOMKill as defense-in-depth.

Additional changes

• Add app.kubernetes.io/managed-by: feast-operator label to getLabels() so all FeatureStore-managed resources carry it
• Introduce getSelectorLabels() for immutable selectors (Deployment spec.selector, Service spec.selector, TopologySpreadConstraints, PodAffinity) to avoid breaking existing resources on upgrade
• Standardize notebook controller's managed-by label to app.kubernetes.io/managed-by
• Use shared constants (services.ManagedByLabelKey/Value) throughout

Test Results

Verified on cluster with a large number of ConfigMaps pre-loaded:

Test plan

• Deploy fixed operator on RHOAI 3.3.0 cluster
• Verify memory usage stays well below 256Mi limit under load
• Verify no OOMKill or CrashLoopBackOff
• Run existing unit tests (make test) — all pass
• Verify getSelectorLabels() prevents immutable selector breakage on upgrade

Summary by CodeRabbit

• Chores
  • Operator cache now only watches/caches resources marked with the managed-by label, reducing resource usage.
  • Added GOMEMLIMIT=230MiB to the controller-manager container.
  • Standardized managed-by label constants and separated immutable selector labels from mutable metadata to improve stability.
• Tests
  • Updated tests to use the shared label constants.