fix: Correct feature-server image name in Helm chart

[AdityaPatil22]

What this PR does / why we need it:

The Helm chart's feature-server subchart references quay.io/feastdev/feature-server-java, which does not exist in the container registry. The
correct image is quay.io/feastdev/feature-server (without the -java suffix). This causes ImagePullBackOff errors when deploying Feast via Helm.

This PR fixes the image repository name in infra/charts/feast/charts/feature-server/values.yaml.

Which issue(s) this PR fixes:

Fixes #6409

Checks

• I've made sure the tests are passing.
• My commits are signed off (git commit -s)
• My PR title follows [conventional commits] format

Testing Strategy

• Unit tests
• Integration tests
• Manual tests
• Testing is not required for this change

Verified by deploying the chart to a local Kubernetes cluster and confirming pods reach Running state instead of ImagePullBackOff.

[aniketpalu]

LGTM

[ntkathole]

@AdityaPatil22 I think the correct fix is either:

• Remove/deprecate the feast umbrella chart's feature-server subchart entirely (it's stale since Java was dropped from CI in May 2025)
• Rewrite the subchart's deployment.yaml to use feast serve like the standalone feast-feature-server chart does

You can see the Helm chart's deployment template at infra/charts/feast/charts/feature-server/templates/deployment.yaml, it has java -jar command, which won't work with python image.

[AdityaPatil22]

Hi @ntkathole,

Thanks for the detailed analysis!

I've updated the subchart's deployment.yaml to use feast serve instead of the legacy java -jar command, aligning it with the standalone feast-feature-server chart.

I also removed the stale Java-specific templates (configmap, secret, and ingress) simplified the values.yaml and README to reflect the current Python-based configuration.

Could you please take a look when you have a chance and let me know if everything looks good, or if there are any additional changes you'd recommend?