|
29 | 29 | - Bill Mulligan ( @xmulligan, [email protected]) |
30 | 30 | - Upstream Issue: https://github.com/cilium/cilium.io/issues/633 |
31 | 31 |
|
| 32 | +### Harbor |
| 33 | + |
| 34 | +#### Harbor CLI - System Settings and Configuration |
| 35 | + |
| 36 | +- Description: Harbor is a widely adopted container registry, and its initial CLI has been developed by LFX mentees. The goal is to extend this CLI by implementing additional functionalities and workflows that are currently only available in the Web UI. The CLI should be useful for Harbor administrators and users, especially to manage workflows within CI/CD pipelines. We seek a Golang-experienced mentee to enhance the CLI independently. |
| 37 | + |
| 38 | +- Expected Outcome: |
| 39 | + - Extend the Harbor CLI to include essential commands not yet implemented. |
| 40 | + - Add new features to improve Harbor management via the CLI for Harbor Administration, enabling robust workflows in CI/CD environments. |
| 41 | + - Review and test all implemented commands to ensure they work as expected. |
| 42 | +- Recommended Skills: Golang, spf13/cobra, Harbor |
| 43 | +- Mentor(s): |
| 44 | + - Vadim Bauer ( @vad1mo, [email protected]) |
| 45 | + - Prasanth Baskar ( @bupd, [email protected]) |
| 46 | +- Upstream Issue: https://github.com/goharbor/harbor-cli/issues/450 |
| 47 | + |
| 48 | + |
| 49 | + |
| 50 | +#### Extend Harbor's Pluggable Scanner API for Runtime Behavior Profiles |
| 51 | + |
| 52 | +- Description: Harbor is a widely adopted container registry. As one of the most widely adopted container registries, it is a critical component in modern software supply chains. This project aims to enhance its security capabilities by extending Harbor's Pluggable Scanner specification to support Runtime Behavior Profiles (also known as a Behavior of Bill, or "BoB"). While Software Bill of Materials (SBOMs) describe what an artifact *contains*, a BoB describes how it *behaves* at runtime. By integrating `kubescape-node-agent` as a scanner, Harbor will be able to retrieve, store, and display these runtime profiles for OCI artifacts. This allows software producers to ship secure-by-default configurations and provides consumers with a way to verify runtime behavior, detect anomalies, and report unexpected activity. This feature will create greater trust in artifacts and help users meet emerging compliance requirements, such as the EU's CyberResilience Act, by enabling active breach identification through anomaly detection. |
| 53 | + |
| 54 | +- Expected Outcome: |
| 55 | + * Propose and document the minimally necessary modifications to the Harbor Pluggable Scanner Spec to support the retrieval of runtime profiles. |
| 56 | + * Implement a scanner adapter that integrates `kubescape-node-agent` with Harbor. |
| 57 | + * The adapter must be able to retrieve and process SPDX-compliant Runtime Profiles (SBOBs). |
| 58 | + * Extend Harbor's UI to allow users to view runtime profiles and see potential mismatches between expected and observed behavior. |
| 59 | + * Lay the foundation for interoperability of runtime and supply chain security tooling across the CNCF ecosystem. |
| 60 | + |
| 61 | +- Recommended Skills: |
| 62 | + * Golang |
| 63 | + * REST API Design |
| 64 | + * Kubernetes |
| 65 | + * Containers and OCI Image/Distribution Specifications |
| 66 | + * Familiarity with software supply chain security concepts (SBOM, SPDX) |
| 67 | + |
| 68 | +- Mentor(s): |
| 69 | + * Vadim Bauer ( @vad1mo, [email protected]) |
| 70 | + * Prasanth Baskar ( @bupd, [email protected]) |
| 71 | + |
| 72 | +* **Upstream Issue:** |
| 73 | + - Upstream Issue: https://github.com/goharbor/pluggable-scanner-spec/issues/22 |
| 74 | + |
| 75 | + |
| 76 | +#### Harbor Satellite: Q&A and Docs |
| 77 | + |
| 78 | +- Description: As edge computing grows, managing container registries at edge becomes a challenge. As the Harbor satellite project matures and evolves, we need to improve the code quality, the release process and user documentation. |
| 79 | + |
| 80 | +- Expected Outcome: |
| 81 | + - Extend build and release artifacts using Dagger. |
| 82 | + - Perform code reviews and establish a Q&A process |
| 83 | + - Create, Update and Improve documentation for Harbor Satellite. |
| 84 | + - Implement new features. |
| 85 | + |
| 86 | +- Recommended Skills |
| 87 | + - Golang |
| 88 | + - GitHub workflow |
| 89 | + - Dagger |
| 90 | + - Testing |
| 91 | + - Q&A |
| 92 | + - Good writing and communication |
| 93 | + |
| 94 | + |
| 95 | +- Mentor(s): |
| 96 | + - Vadim Bauer ( @vad1mo, [email protected]) |
| 97 | + - Prasanth Baskar ( @bupd, [email protected]) |
| 98 | + |
| 99 | +- Upstream Issue: https://github.com/goharbor/harbor/issues/21959 |
| 100 | + |
| 101 | + |
| 102 | +#### Harbor Satellite: Implementing a Eventing System for Satellite |
| 103 | + |
| 104 | +- Description: |
| 105 | + Harbor Satellite is a lightweight, OCI-compliant registry (currently based on Zot) designed to run on edge devices, such as Raspberry Pi or ARM-based hardware. It acts as a local container registry for edge devices and workloads. The satellite autonomously fetches configuration and state, registers with Ground Control, reports its status, and optionally sends system-level events to connected edge systems. |
| 106 | + |
| 107 | +- Expected Outcome: |
| 108 | + - Implement an eventing mechanism to notify edge systems about critical state transitions (e.g., "state update ready", "sync complete"). |
| 109 | + - Improve build and release pipelines. |
| 110 | + - Make the satellite functional on ARM-based edge devices (like Raspberry Pi). |
| 111 | + - Add reliable state and health reporting back to Ground Control. |
| 112 | + - Add e2e tests to validate artifact fetching, status reporting, and eventing. |
| 113 | + |
| 114 | +- Recommended Skills |
| 115 | + - Golang |
| 116 | + - Containers |
| 117 | + - Edge Computing |
| 118 | + - OCI Image/Distribution Spec |
| 119 | + - Webhooks |
| 120 | + - Event-Driven Architecture |
| 121 | + |
| 122 | +- Mentor(s): |
| 123 | + - Vadim Bauer ( @vad1mo, [email protected]) |
| 124 | + - Orlin Vasilev ( @OrlinVasilev, [email protected]) |
| 125 | + - Prasanth Baskar ( @bupd, [email protected]) |
| 126 | + |
| 127 | +- Upstream Issue: https://github.com/goharbor/harbor/issues/21986 |
| 128 | +- LFX |
| 129 | + |
| 130 | + |
32 | 131 | ### Jaeger |
33 | 132 |
|
34 | 133 | #### Next-Generation Jaeger Demo with OpenTelemetry and OpenSearch (2025 Term 3) |
|
0 commit comments