Go Developer for Open Source Project
Budget: $250 – $750 USD
Hi, I'm looking for someone to work with on my open source project. The project is a Go application that is a Claude MCP-Server that primarily interacts with GitOps technologies to help facilitate better uptime, troubleshooting, and deployment creation mechanisms. The application currently works and is able to be deployed locally via a container or outside via the cli for debugging purposes. I have a postman collection I can share with all of the available calls and there is a well scripted README.md file in the repo as well.
The work for the project revolves around these main concentration areas/improvements to be made:
Core Observability Extensions
- Extend the k8s client to collect data on all resource types, not just the common ones
- Implement cross-resource relationship mapping (e.g., connecting Services to Deployments to ConfigMaps)
- Build a timeline view of cluster events with correlation between related resources
- Possibly create a resource state cache for faster repeated queries (Optional)
Repository Analysis System
- Develop Git repository scanner that integrates with GitLab API
- Create parsers for Kubernetes manifests (Helm charts only)
- Generate mappings between repository files and deployed cluster resources
- Build detection for deployment patterns and GitOps workflows
Recommendation Engine
- Enhance the troubleshoot correlator with common issue pattern detection
- Generate precise, actionable recommendations based on observed issues
- Provide exact file paths and line numbers for recommended changes
- Include example Git commands users can copy/paste to implement fixes
Claude Integration Improvements
- Refine system prompts to focus on actionable insights
- Implement specialized prompts for different resource types and scenarios
- Add support for generating exact kubectl commands for verification
- Improve response formatting for better readability (tables, sections, code blocks)
User Experience
- Create an API endpoint for repository structure reporting
- Implement better error summarization by severity and impact
Technical Implementation Details
- Implement connection pooling for more efficient API usage
- Add caching layer to reduce repeated API calls to Kubernetes
- Create background worker jobs for repository scanning
Final Core Deliverables
- Enhanced cluster state reporting with cross-resource relationships
- Basic repository analysis with file-to-resource mapping
- Improved recommendation quality with specific fix instructions
If you need anymore insight into these requests or the work, please let me know. I'm an SRE and Full-Stack developer, so I can assist as well if need be. Thanks!
Project Repository: https://github.com/Blankcut/kubernetes-mcp-server
The work for the project revolves around these main concentration areas/improvements to be made:
Core Observability Extensions
- Extend the k8s client to collect data on all resource types, not just the common ones
- Implement cross-resource relationship mapping (e.g., connecting Services to Deployments to ConfigMaps)
- Build a timeline view of cluster events with correlation between related resources
- Possibly create a resource state cache for faster repeated queries (Optional)
Repository Analysis System
- Develop Git repository scanner that integrates with GitLab API
- Create parsers for Kubernetes manifests (Helm charts only)
- Generate mappings between repository files and deployed cluster resources
- Build detection for deployment patterns and GitOps workflows
Recommendation Engine
- Enhance the troubleshoot correlator with common issue pattern detection
- Generate precise, actionable recommendations based on observed issues
- Provide exact file paths and line numbers for recommended changes
- Include example Git commands users can copy/paste to implement fixes
Claude Integration Improvements
- Refine system prompts to focus on actionable insights
- Implement specialized prompts for different resource types and scenarios
- Add support for generating exact kubectl commands for verification
- Improve response formatting for better readability (tables, sections, code blocks)
User Experience
- Create an API endpoint for repository structure reporting
- Implement better error summarization by severity and impact
Technical Implementation Details
- Implement connection pooling for more efficient API usage
- Add caching layer to reduce repeated API calls to Kubernetes
- Create background worker jobs for repository scanning
Final Core Deliverables
- Enhanced cluster state reporting with cross-resource relationships
- Basic repository analysis with file-to-resource mapping
- Improved recommendation quality with specific fix instructions
If you need anymore insight into these requests or the work, please let me know. I'm an SRE and Full-Stack developer, so I can assist as well if need be. Thanks!
Project Repository: https://github.com/Blankcut/kubernetes-mcp-server