DevOps good first issues

AI Summary: This issue proposes integrating Meshery's Nighthawk performance testing capabilities with AI assistants. The goal is to enable AI agents to initiate, monitor, and retrieve results from performance tests using natural language commands. This involves implementing several new tools within the MCP framework to manage the entire performance testing workflow.

AI Summary: This issue proposes the implementation of several new tools within Meshery's MCP (Meshery Control Plane) to enable AI assistants to query and retrieve information about infrastructure components and models. These tools will allow AI agents to search, browse, and get detailed definitions of available infrastructure building blocks, such as Kubernetes Deployments or Istio components.

AI Summary: This issue proposes the implementation of several tools within Meshery's AI assistant to manage Kubernetes cluster connections. These tools will enable AI agents to list, connect, disconnect, and query the health and resources of Kubernetes clusters through natural language commands, enhancing Meshery's integration capabilities.

AI Summary: This issue proposes the implementation of a comprehensive CI/CD pipeline for the `meshery-mcp-server` repository. It includes setting up automated builds, tests, linting, and multi-platform binary/Docker image releases using GoReleaser. Additionally, it calls for dependency management with Dependabot and security scanning with CodeQL and Gosec.

AI Summary: This issue requests comprehensive documentation for the meshery-mcp-server, including a user guide, configuration reference, and AI client integration examples. The goal is to enable new users to set up and integrate the server quickly. The implementation plan involves overhauling the README and creating new markdown files for installation, configuration, tool references, specific integrations, and development guidelines.

AI Summary: This issue proposes the implementation of new MCP tools to enable AI assistants to manage Meshery environments and workspaces. The tools will allow users to list, create, and switch between these entities using natural language prompts, with specific requirements for input/output formats and error handling.

AI Summary: This issue proposes the implementation of several "MCP Tools" within Meshery to enable AI assistants to manage infrastructure designs and patterns. These tools will allow AI agents to perform operations like listing, creating, deploying, undeploying, and deleting designs through natural language commands. The implementation will involve creating specific Go functions with JSON schema validation, structured output, and error handling.

AI Summary: This issue proposes exposing live infrastructure topology data from Meshery as MCP resources. This will allow AI assistants to access real-time cluster information for analysis and troubleshooting without direct tool calls. The implementation involves defining specific MCP resource URIs and ensuring they return JSON-serialized topology data with subscription support.

AI Summary: This issue proposes the implementation of guided workflow templates (MCP prompts) for AI assistants interacting with Meshery. These templates will provide structured guidance for common Meshery operations like deploying applications, debugging clusters, and reviewing designs, improving consistency and reducing verbosity in AI interactions.

AI Summary: This issue proposes the implementation of an MCP (Model Context Protocol) server within Meshery to enable AI assistants to connect and interact with Meshery's capabilities. The implementation will involve adding an MCP Go SDK dependency, creating a new server entry point, and supporting both stdio and SSE/HTTP transports, along with graceful shutdown, structured logging, and server capability advertisement.

AI Summary: This issue proposes the implementation of a robust configuration system for the MCP server. It aims to enable API key authentication, support multiple named Meshery instances with context switching, and allow configuration via YAML files and environment variables. The goal is to provide a flexible and user-friendly way to manage connections to different Meshery deployments.

AI Summary: This issue proposes the creation of a Go client package to enable communication between the MCP server and a running Meshery instance. The client will wrap Meshery's REST and GraphQL APIs, supporting configuration via environment variables and a config file, and will include features like automatic authorization header injection, error mapping, and a health check method. Unit tests using httptest are also required.

AI Summary: This issue requests the creation of a complete Go project scaffold for the `meshery-mcp-server` repository. It outlines the desired directory structure, essential configuration files like `go.mod`, `.golangci.yml`, `Makefile`, `Dockerfile`, and GitHub Actions for CI. The goal is to provide contributors with a ready-to-use starting point for developing the MCP server.

AI Summary: This issue proposes the implementation of a comprehensive testing infrastructure for the repository, including unit, integration, and end-to-end tests. The goal is to achieve reliable test execution in CI and locally, with specific guidelines for each test tier, including mocking strategies, required dependencies, and desired code coverage.

AI Summary: Update the Olympgit lab documentation to reflect that the default branch is already olympgit, removing the unnecessary step of switching branches after cloning. The updated documentation should clearly explain how to clone the repository and begin working without any branch switching.

AI Summary: This bug report indicates that ArgoCD webhooks are no longer functioning because the ArgoCD instance's address has changed. The issue requires updating the webhook configurations for specific Kubernetes repositories to point to the new ArgoCD address.

AI Summary: The `apache/Dockerfile` fails to build a Docker image for Mautic because the `libc-client-dev` package cannot be located. This is likely due to recent changes in Debian's package structure, preventing the `apt-get install` command from finding the required dependency.

AI Summary: Update the `nix-flatpak` documentation to include instructions and examples for manual installation without using flakes, addressing the issue raised in discussion #104.

AI Summary: Refactor the Cluster Bare Autoscaler project by moving initialization logic from the `pkg/metrics` and `pkg/tracing` packages into a new `internal/bootstrap` directory. This improves code organization, simplifies testing, and clarifies the purpose of each package. The changes involve updating imports in `main.go`, deleting the now-empty `pkg` directories, and adjusting the `.codecov.yml` file to exclude the new `internal/bootstrap` directory from coverage.

AI Summary: Migrate the Confluent project from the deprecated Eventlet library to the standard Python asyncio library. This involves refactoring existing code to utilize asyncio's asynchronous programming model, potentially requiring significant changes depending on the extent of Eventlet's integration within Confluent.

AI Summary: The user needs guidance on deploying the DeepFlow agent in a non-Kubernetes environment. The task involves researching and documenting the process of installing and configuring the DeepFlow agent on a host machine outside of a Kubernetes cluster.

AI Summary: Modify the Python standalone build process to prevent static linking of the `_ctypes_test` module, ensuring its symbols are not exported in the final binaries (`bin/python` or `libpython`). The module should still be built dynamically to allow test execution. Consider adding a test to enforce a naming convention (e.g., `Py` or `_Py` prefix) for exported dynamic symbols.

AI Summary: The BeSman environment installation process needs to be improved so that environment variables from the configuration file are automatically exported after installation, eliminating the need for a manual `bes reload` command.

AI Summary: Enhance the Trema bot to validate the existence of GitHub usernames provided during membership requests. The bot should detect invalid usernames and prompt the user for correction before proceeding with the organization invitation.

AI Summary: Update the CEDILLE project README file to replace two broken links related to Kubernetes kubeconfig configuration with either working links or create new documentation explaining the process of merging kubeconfig files.

AI Summary: Update the Infomaniak Terraform provider documentation on the Terraform Registry to include the new fields introduced in pull request #28. This involves updating the documentation files located in the `docs/` directory and then deploying the updated documentation.