GoogleCloudPlatform/kubectl-ai

[Bug]: Bedrock-llm-provider bad response upon kubectl-ai trigger

Open

#519 opened on Sep 8, 2025

 (13 comments) (0 reactions) (0 assignees)Go (708 forks)auto 404
bughelp wanted

Repository metrics

Stars
 (7,532 stars)
PR merge metrics
 (PR metrics pending)

Description

Environment (please complete the following):

  • OS: MacOS
  • kubectl-ai version (run kubectl-ai version): 0.0.23
  • LLM provider: bedrock
  • LLM model: us.anthropic.claude-sonnet-4-20250514-v1:0

Describe the bug I've set the config.yaml at: ~/.config/kubectl-ai/config.yaml as said in the README. My configurations are as mentioned above (bedrock, us.anthropic.claude-sonnet-4-20250514-v1:0, kubeconfig path is set to default: ~/.kube/config). I've been trying to simply understand if i'm connected and set up properly using the following prompt: "how many namespaces are in the cluster?", or "what pods are currently live in my cluster?", and I keep getting the following answers:

>>> what namespaces are here?

  I'll check what namespaces are available in your cluster.                   

>>> 
>>> 
>>> exit

or even:

  Hey there, what can I help you with today?                                  

>>> what namespaces are here?

  I'll check what namespaces are available in your Kubernetes cluster.        

>>> exit

Meaning - nothing really happening. If it make sense or assist with anything, I have multiple profiles in my ~/.aws/config file, but even when login to a specific profile (instead of using the regular aws sso login, i've tried aws sso login --profile <profile_name> - got the same responses.

To Reproduce Steps to reproduce the behavior:

  1. Open a terminal, after aws sso login successfully
  2. run: kubectl-ai, then ask a simple question.
  3. Nothing happens after the polite answer

Expected behavior I was supposed to see any response, even an error code or something

Contributor guide