Prometheus-Operator

Mentors: Student: Yash Kumar Patel

The project aims to implement status subresource in Service Monitor, Pod Monitor, Probes, AlertmanagerConfig, PrometheusRule and ScrapeConfig Custom Resource. Currently, these CRs lack the status subresource, implementing it will increase the observability, as it enables users and controllers to observe the current state of the resource, for users having access to the status enhances the user experience by providing transparency and visibility into the state of resources.

Mentors: Student: Dhruv puri

The project aims to bring the Prometheus Agent's DaemonSet mode in Prometheus Operator to full production readiness. This involves addressing missing functionalities, improving configuration validation, enhancing reliability, and providing comprehensive documentation. The ultimate goal is to offer a scalable, efficient, and fully supported way to run Prometheus Agent across Kubernetes nodes. This is achieved by integrating remaining features like using CEL for CRD validation to provide immediate feedback along with adding runtime checks as a fallback for older Kubernetes versions. Furthermore, Investigating and potentially implementing EndpointSlice for scalability and extending integration tests to multi-node Kind clusters. Finally, adding detailed documentation and example manifests.

Mentors: Student: S Ashwin

The Prometheus Operator plays a pivotal role in deploying, configuring, and managing Prometheus instances within Kubernetes clusters. Despite its significance, fully leveraging its functionalities remains challenging due to outdated and ambiguous documentation. This proposal aims to address this issue by identifying the current shortcomings in the documentation and development processes. It will outline strategies to revamp the documentation, ensuring clarity and relevance. Additionally, emphasis will be placed on establishing sustainable practices to prevent future documentation difficulties. By implementing these improvements, the goal is to elevate the Prometheus Operator documentation to a level where users can easily engage with the project. This initiative seeks to highlight the importance of Prometheus Operator while fostering accessibility and usability for all users.

Mentors: Student: M Viswanath Sai

This proposal aims to enhance the ScrapeConfig CRD to achieve stability and usability. Currently in alpha, the CRD lacks the originally intended 1:1 relationship with Prometheus configurations. The project outlines a roadmap to address these issues, focusing on adding necessary fields, extending support for service discoveries, and implementing thorough testing. The plan includes a strategy for graduating the CRD to beta and eventually stable versions, following Kubernetes API versioning guidelines. Deliverables: Updated ScrapeConfig CRD with added fields to support service discoveries and other configuration options. Thorough test coverage for the added fields and overall functionality. Graduation of the ScrapeConfig CRD to beta stage, with documentation outlining the upgrade process. Enhanced documentation providing up-to-date information on the CRD and migration guides for users upgrading if necessary.

Mentors: Student: Ha Anh Vu

This project is about designing and implementing the deployment of Prometheus Agent as DaemonSet. Currently, Prometheus Agent can only be deployed as StatefulSet, which could be considered as “cluster-wide” strategy, meaning one or several high-availability Prometheus Agents are responsible for scraping metrics of the whole cluster. Though this works well for many use cases, some use cases may indeed require a “node-specific” strategy (DaemonSet), where each Prometheus Agent only scrapes the metrics of the node it’s on. This proposal will discuss the advantages and tradeoffs of this deployment mode, list the key implementation issues and propose a solution approach for each issue.