feat: Batch_engine config injection in feature_store.yaml through operator

[aniketpalu]

What this PR does / why we need it:

Adds support for batch_engine configuration in the Feast Operator, allowing users to configure compute engines (Spark, Ray, etc.) via ConfigMap reference in the FeatureStore CR.

Usage

1. Create a ConfigMap with batch engine config

apiVersion: v1
kind: ConfigMap
metadata:
  name: ray-batch-engine-config
data:
  config: |
    type: ray.engine
    max_workers: 4
    enable_optimization: true

2. Reference it in FeatureStore CR

apiVersion: feast.dev/v1
kind: FeatureStore
metadata:
  name: my-feature-store
spec:
  feastProject: my_project
  batchEngine:
    configMapRef:
      name: ray-batch-engine-config
    configMapKey: config  # optional, defaults to "config"

3. Generated feature_store.yaml output

project: my_project
batch_engine:
  type: ray.engine
  max_workers: 4
  enable_optimization: true

Important Considereations

• Only api/v1 modified (not v1alpha1)
• ConfigMap used instead of Secret (engine configs typically don't contain credentials)
• configMapKey defaults to "config" if not specified
• type field required in ConfigMap data

Which issue(s) this PR fixes:

Misc

---

[devin-ai-integration]

Devin Review found 1 potential issue.

View issue and 5 additional flags in Devin Review.

[devin-ai-integration]

🔴 Development image registry left in production kustomization.yaml

The kustomization.yaml file was changed to point to a personal development registry instead of the official Feast registry.

Click to expand

Issue

The image configuration in infra/feast-operator/config/manager/kustomization.yaml was changed from the official registry to a personal development registry:

Before (correct):

images:
- name: controller
  newName: quay.io/feastdev/feast-operator
  newTag: 0.59.0

After (incorrect):

images:
- name: controller
  newName: quay.io/aniket-redhat/feast-operator
  newTag: dev0.8

Impact

If this change is merged and deployed:

1. Production deployments would pull from a personal development registry (quay.io/aniket-redhat/feast-operator)
2. The image tag dev0.8 suggests an unstable development build
3. This could cause security concerns (untrusted image source) and reliability issues (development images may not be stable)
4. The image may not even be publicly accessible, causing deployment failures

Recommendation: Revert the image configuration to use the official Feast registry: newName: quay.io/feastdev/feast-operator and newTag: 0.59.0

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[ntkathole]

@aniketpalu this ^