Showcase Your Kubernetes Skills with a GitHub README Badge

Use this markdown in your README:

![Kubernetes](https://img.shields.io/badge/Kubernetes-326CE5?style=for-the-badge&logo=kubernetes&logoColor=white)

The #326CE5 color is the official Kubernetes blue used in the project's logo and branding. The kubernetes logo identifier renders the distinctive Kubernetes helm wheel icon from Simple Icons. This badge is immediately recognizable to DevOps engineers and cloud architects who are your most likely collaborators or hiring managers.

Kubernetes experience spans a wide range of depths — from running kubectl apply against a pre-configured cluster to architecting multi-cluster, multi-region deployments with custom operators. Be specific about your depth.

In your bio or dedicated skills section, mention what you have actually deployed on Kubernetes: stateless services, stateful workloads (databases, message queues), custom CRDs, operators, or service mesh integrations. If you manage Kubernetes in a cloud provider (EKS, GKE, AKS), name the specific managed service. 'Kubernetes on GKE for a team of 20 engineers' tells a more specific story than 'experienced with Kubernetes'.

Kubernetes appears in two primary DevOps contexts:

• Cloud infrastructure stack: Kubernetes + Terraform + AWS/GCP/Azure + Helm + ArgoCD
• Container development stack: Kubernetes + Docker + CI/CD tools + Prometheus + Grafana

Group these badges in a 'DevOps & Infrastructure' section separate from your programming language badges. The visual grouping makes it easy for engineering managers and platform engineers to identify your infrastructure skill depth at a glance.

If you specialize in Kubernetes-related tools (Helm chart development, Operator SDK, service mesh configuration), mention these specifically in your profile bio rather than only in the badge row.

Kubernetes configuration work is often in YAML and Helm templates, which GitHub's language detection may count as 'Smarty' (Helm) or simply 'YAML'. Consider using the hide parameter in your top languages card to exclude these from the percentage breakdown if they obscure your primary coding languages.

Pin repositories that demonstrate real Kubernetes work: infrastructure-as-code repositories with Helm charts, operator implementations, or GitOps configurations. A GitOps repository showing Kubernetes manifests with proper resource management, namespacing, and RBAC configuration demonstrates DevOps expertise more convincingly than a badge alone.