Kubernetes

<p>[Argo CD](https://github.com/argoproj/argo-cd) is a Kubernetes-native GitOps continuous delivery tool for managing application deployments from Git. This project builds a Headlamp plugin that integrates Argo CD concepts directly into Kubernetes workflows by extending the **Projects view**. The plugin surfaces high-level GitOps signals (applications, sync status, health, revisions) so SREs, operators, and developers can understand deployment state.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p>&nbsp;- Extend **Projects view** to include Argo CD context per project.</p><p>&nbsp;- Show associated Argo CD Applications with:</p><p>&nbsp;- Sync Status (Synced / OutOfSync)</p><p>&nbsp;- Health Status (Healthy / Degraded)</p><p>&nbsp;- Current Revision (Git commit / branch)</p><p>&nbsp;- Surface minimal GitOps context:</p><p>&nbsp;- Source repository + revision</p><p>&nbsp;- Target namespace / cluster</p><p>&nbsp;- Deployment status summary</p><p>&nbsp;- Lightweight UX enhancements:</p><p>&nbsp;- GitOps status indicators (icons / badges)</p><p>&nbsp;- Inline listing of related Applications</p><p>&nbsp;- Links to Application detail pages and Kubernetes resources</p><p>&nbsp;- Follow **Headlamp UX patterns**:</p><p>&nbsp;- Tables, icons, detail layouts</p><p>&nbsp;- Cross-resource navigation (Project → Application → Workloads)</p><p>&nbsp;- README with prerequisites and limitations; blog post demoing usage.</p>

Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon 15 years of experience of running production workloads at Google, combined with best-of-breed ideas and practices from the community.

The process that signs with Sigstore all container images released on community infra was designed for a different serving architecture. When the community moved to registry.k8s.io (https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/) and increased 10x the number of registries, the replication of signatures broke due to rate limits imposed on the new registries. As part of the project, you will be instrumental in implementing the new signing process currently being designed by the Kubernetes Release Engineering team. This project will involve heavy rewrites and refactoring of parts of the Image Promoter (https://github.com/kubernetes-sigs/promo-tools), the tool that releases community images. Expected Outcome: Implementation of the new signing process, ideally we'll fix all inconsistent signatures across community registries.

Kubernetes Pods are the unit of execution. Pods's API surface is limited, but yet presenting many challenges for people authoring complex behaviors like proper graceful termination, probes, or advances initialization behaviors. Documentation and testing of those scenarios is limited. The misunderstanding of pod lifecycle and edge casesoften lead to reliability issues in Pods. Lately there were limited efforts to document and test those behaviors. Creating a skaffolding to document and test those behaviors will help temendously the Kubernetes project as well as end users. Expected Outcome: Skaffolding in https://github.com/kubernetes/website/ to add new pod lifecycle behavios descriptions. Tests for those edge cases. And cross linking between tests and documentation.

Description: Cluster API (CAPI) is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify lifecycle management of Kubernetes clusters. CAPA is the infrastructure provider that extends Cluster API to manage Kubernetes clusters on AWS. As a mentee, you will start with learning CAPI/CAPA concepts and then, will work on the main project which is to automate AMI build, test, and publish workflows using Prow, Github, and other Kubernetes automation tools.