You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Next-Generation Jaeger Demo with OpenTelemetry and OpenSearch (2025 Term 3)
35
+
36
+
Description: This project will create a Kubernetes deployment for the full stack: the OpenTelemetry Demo application, the Jaeger backend components (Collector, Query), and OpenSearch as a storage backend. The environment will be automatically redeployed weekly to ensure it is always fresh and to solve the problem of data retention. The entire stack will be hosted on a managed Kubernetes cluster (Oracle Kubernetes Engine) within an Oracle Cloud environment generously donated to the project.
37
+
Expected Outcome:
38
+
-A working, publicly accessible Jaeger demo featuring the OpenTelemetry Demo application, deployed on Oracle Cloud.
39
+
-Fully automated, weekly deployments using the existing Helm-based automation and GitHub Actions.
40
+
-The entire environment defined as "Configuration as Code".
41
+
-A secure deployment following best practices for public-facing services.
42
+
-The UIs for Jaeger, the OTel Demo, the load generator, and OpenSearch Dashboards exposed -publicly via the existing demo.jaegertracing.io URL.
43
+
-Public-facing documentation on the Jaeger website explaining the demo architecture and linking to the automation code.
#### Develop MCP Server for Agentic AI interaction with OpenCost
53
+
54
+
- Description: We would like OpenCost to more effectively integrate with AI agents. To do this, we need to implement a Model Context Protocol (MCP) server to surface the information from the OpenCost API. This is a great opportunity to learn about MCP servers, and help us build an interface for AI agents to obtain reliable cost/usage information so that they can accomplish their business goals.
55
+
- Expected Outcome: We would like an MCP server integrated into OpenCost. This MCP server should support queries on allocations, assets, and cloud costs. The MCP server should support the full range of allocations, assets, and cloud cost query parameters. A demo video should be recorded showing an interaction with the MCP server, and used to obtain costing information in a conversational setting. In addition, integration tests must be created in the OpenCost Integration Tests repo that test all interactions with the MCP server
56
+
- Recommended Skills: Golang, MCP, Comfort with OpenCost, Cost/Usage reporting, AI agent interfacing and usage, documentation writing
- Description: OpenCost's data model is now 6 years old, and we have learned a great deal long the way. Based on these learnings, we would like to revamp how OpenCost represents its cost and usage data across the stack. We want to set OpenCost up for the next set of features and scale by building a solid foundation for the way we represent data.
65
+
- Expected Outcome: We would make the UID of Kubernetes objects into a first class citizen. These UID based objects would then be grouped in a similar hierarchy to the way Kubernetes itself is organized. A successful conclusion of this project would see an additional emitter implemented in OpenCost, that emits data objects stored in compressed protobuf which reflect a hierarchy of Kubernetes objects. The mentors will help establish this hierarchy. This hierarchy should then be tested via integration tests against the existing objects, and key metrics compared to be equal across those.
- Description: Currently a Workload Description Space (WDS) has Binding objects that refer to inventory objects in exactly one Inventory and Transport Space (ITS). This mentorship project would generalize that, allowing references to inventory objects in multiple ITSes. Bear in mind scalability concerns.
97
+
- Expected Outcome: generalized API and implementation as described.
98
+
- Recommended Skills: Familiarity with Kubernetes and KubeStellar.
#### Implementing End-to-End Playwright Testing for KubeStellar UI
105
+
106
+
- Description:
107
+
This project focuses on building a robust end-to-end testing framework for the KubeStellar UI using Playwright. The goal is to ensure seamless user experiences by automating critical workflows, enhancing test coverage, and catching UI issues early across various browsers and environments. This includes setting up Playwright from scratch, writing reusable and scalable test suites using the Page Object Model (POM), and integrating these tests into the CI/CD pipeline. Special focus will be given to WebSocket-based testing, authentication, and resource-heavy scenarios in a multi-cluster Kubernetes context.
108
+
- Expected Outcome:
109
+
- End-to-end testing setup with Playwright integrated into the KubeStellar frontend
110
+
- Comprehensive test suites for login, cluster/resource management, and binding policy workflows
111
+
- Page Object Model-based modular test architecture
112
+
- Mocking framework for WebSocket and REST API-based interactions
113
+
- Visual regression testing integrated into GitHub Actions CI
114
+
- Test coverage for key workflows
115
+
- Cross-browser testing across Chromium, Firefox, Safari, and WebKit
116
+
- Flaky test rate under 5% with parallel test execution and retry strategies
117
+
- Documentation for writing, running, and debugging tests locally and in CI
118
+
- Recommended Skills:
119
+
- TypeScript / JavaScript
120
+
- Playwright or similar frameworks (Cypress, Puppeteer)
0 commit comments