bug(kagent): Decommissioned Groq model llama3-8b-8192 mapped in setup.yaml

[GunaPalanivel]

Problem

kagent-feast-mcp/manifests/kagent/setup.yaml line 21 specifies:

model: <model of your choice>

This placeholder gives no guidance to new contributors. During local PoC testing, the previous value llama3-8b-8192 returned a 400 model_decommissioned error from the Groq API. A working default should be provided so the PoC is functional out of the box.

Reproduction

# After applying setup.yaml with a decommissioned or empty model value:
kubectl logs -f deployment/kubeflow-docs-agent -n docs-agent
# → Groq API returns: 400 {"error": {"message": "model_decommissioned"}}

Proposed Fix

Replace the placeholder with a known working model:

# Before (line 21)
model: <model of your choice>

# After
model: llama-3.1-8b-instant

Add a YAML comment listing other valid options for contributors who want to swap models.

File

• kagent-feast-mcp/manifests/kagent/setup.yaml:21

Context

Discovered during local Kagent PoC validation — #59 (comment)

[Rakshanda3]

Hi! I'd like to work on this issue and submit a PR.

[Rakshanda3]

Thank you! I’m happy to make any requested changes.

[nameershah]

Hi! I'm a GSoC 2026 applicant. I've worked with
Groq's API extensively (built TaleemAI on Groq + Llama 3)
and I'd like to fix this. Can I be assigned this issue?