[Bug]: Prometheus mcp server pod not comming 1/1 Running state

[shreyansh2953]

Pre-submission Checklist

• I have searched existing issues to ensure this bug hasn't been reported before
• I have checked the documentation and this appears to be a bug, not a configuration issue
• I can reproduce this issue consistently

Priority Level

High - Significant impact, blocks important functionality

Bug Description

Hi @pab1it0

i am trying to install your mcp server with my prometheus url, the configuration looks good !!

but it is giving this issue, can you please help me on this !!

Steps to Reproduce

Expected Behavior

my mcp server should run without any issue

Actual Behavior

my mcp server not running due to this issue

Affected Component

Prometheus Integration (queries, metrics, API calls)

Operating System

Linux

Python Version

using your docker image

Prometheus MCP Server Version

1.0.0

Prometheus Version

No response

Transport Mode

HTTP

Configuration

Error Logs

PromQL Query (if applicable)

Workaround

No response

Additional Context

No response

Contribution

• I would be willing to submit a pull request to fix this issue

[github-actions]

👋 Welcome to the Prometheus MCP Server project, @shreyansh2953!

Thank you for taking the time to report this issue. This project provides AI assistants with access to Prometheus metrics through the Model Context Protocol (MCP).

To help us resolve your issue quickly:

• Please ensure you've filled out all relevant sections of the issue template
• Include your environment details (OS, Python version, Prometheus version)
• Provide steps to reproduce if applicable
• Check if this might be related to Prometheus configuration rather than the MCP server

A maintainer will review and triage your issue soon. If you're interested in contributing a fix, please feel free to submit a pull request!

Useful resources:

• Configuration Guide
• Installation Guide
• Contributing Guidelines

[frwa-enpace]

I have the same problem, to resolve it, I removed livenessProbe and readinessProbe from the chart's values.yaml.

But you should create a health endpoint.