Bug fix: Fix the Git Service when running on Ollama

[esnible]

Summary

We supply a configuration for the Git Service when running on Kagenti under Ollama, but it doesn't work.

For example, the chat query What do you think about https://github.com/kagenti/agent-examples/issues/218 ? yields

Thought: The user query involves retrieving issues from a specific GitHub repository and issue number. Action: list_issues Action Input: {"owner":"kagenti","repo":"agent-examples","state":"all"}

The default port for an MCP tool in Kagenti is 8000, but this Agent example assumes the MCP server will be deployed on 9090.

(Optional) Testing Instructions

1. Deploy the Git Tool
2. http://kagenti-ui.localtest.me:8080/agents/import

• Deploy from Existing Image,
• ghcr.io/kagenti/agent-examples/git_issue_agent
• tag v0.1.0-alpha.8
• Env vars https://raw.githubusercontent.com/kagenti/agent-examples/refs/heads/main/a2a/git_issue_agent/.env.ollama
  • Override the values with the changes in this PR
• Deploy
• Wait for agent to become Ready

[rubambiza]

Review Summary

The MCP port fix (9090 -> 8000) is correct and matches Kagenti's default tool port. The /v1 URL suffix and model ID change look intentional for OpenAI-compatible mode via litellm. One issue: the file header comment is now stale.

Areas reviewed: Config/env
Commits: 1 commit, signed-off
CI status: All passing (10/10)

[rubambiza]

must-fix: The header comment on line 5 still says ollama pull ibm/granite4:latest but the model ID is now gpt-oss:latest. Please update the comment to match the new model, or explain what gpt-oss is and what prerequisite pull command is needed.

[rubambiza]

suggestion: Adding /v1 switches from the native Ollama API to the OpenAI-compatible endpoint. This is correct for litellm with the gpt-oss model prefix, but a brief inline comment explaining why /v1 is needed would help future readers.

[esnible]

Thanks, please re-review.