| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Eliminating Kubernetes Image Signature Replication |
| |
| |
The Kubernetes image promoter no longer replicates container image signatures across regions. The rewrite drops that replication entirely, cuts latency, and simplifies the codebase, while keeping signature verification working seamlessly for end users.
Next, the project is moving to OCI 1.1 referrers for signature discovery, which opens the door to further improvements in how signatures are handled. |
|
| |
|
| |
|
| |
| Breaking free of a single datacenter: Practical geo-distributed AI operations with the k0smos platforms |
| |
| |
| This post discusses the challenges of leveraging distributed resources for AI workloads and the role of Kubernetes in addressing these challenges. The k0smos stack is highlighted as a solution for operating geo-distributed AI infrastructure, divided into three technical layers: k0s, k0smotron, and k0rdent. Field studies conducted using this stack demonstrate the feasibility of running AI workloads across dynamic, energy-aware orchestration models. |
|
| |
|
| |
|
| |
| Benchmarking KubeVirt performance with virtbench |
| |
| |
| Portworx released "virtbench," an open-source CLI that lets platform teams run reproducible KubeVirt benchmarks and assess VM readiness, rather than rely on pod health as a proxy. |
|
| |
|
| |
|
| |
| From Dashboard to Headlamp: Understanding the Transition |
| |
| |
The Kubernetes Dashboard project has been archived, with Headlamp now carrying the legacy forward by offering a visual interface with enhanced capabilities like multi-cluster visibility and application-centric views.
Headlamp keeps familiar workflows, while expanding to support multi-cluster environments and application context with Projects. The UI can be extended with plugins, and Headlamp can be run in-cluster or as a desktop application based on user needs. |
|
| |
|
| |
|
| |
| Kubernetes' Default CoreDNS Configuration is insecure |
| |
| |
| CoreDNS pods insecure option is the default in Kubernetes as it allows for the creation of arbitrary DNS A records. Combined with wildcard SSL certs, it poses a security risk, highlighted by Cilium's handling of network policies in the face of DNS manipulation. Time to shift to a more secure DNS configuration! |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |