Uploaded July 2026 | Updated September 2026, 2 weeks ago
Hard-coding credentials, or relying on basic Kubernetes secrets, can cause security vulnerabilities at scale. Senior Product Marketing Manager Amber Silver explains how Red Hat OpenShift can help you protect your sensitive database credentials, API keys, and access tokens.
In application development, keeping private information secure is a business necessity. Red Hat OpenShift helps protect your data by connecting your clusters to a single external source of truth. By automating the entire secrets lifecycle, you can manage rotation and expiration dates to reduce manual work and human error, and automatically synchronize or delete credentials across the cluster when they need to be updated or revoked, shrinking the blast radius of a potential breach.
Resources:
🔒 Watch the demo with HashiCorp Vault → interact.redhat.com/share/pFScA2wEIsF2KcrjyoKT
✨ Learn more about Red Hat OpenShift → redhat.com/en/technologies/cloud-computing/openshift
#RedHat #OpenShift #SecretsManagement #Kubernetes
Hard-coding credentials, or relying on basic Kubernetes secrets, can cause security vulnerabilities at scale. Senior Product Marketing Manager Amber Silver explains how Red Hat OpenShift can help you protect your sensitive database credentials, API keys, and access tokens.
In application development, keeping private information secure is a business necessity. Red Hat OpenShift helps protect your data by connecting your clusters to a single external source of truth. By automating the entire secrets lifecycle, you can manage rotation and expiration dates to reduce manual work and human error, and automatically synchronize or delete credentials across the cluster when they need to be updated or revoked, shrinking the blast radius of a potential breach.
Resources:
🔒 Watch the demo with HashiCorp Vault → interact.redhat.com/share/pFScA2wEIsF2KcrjyoKT
✨ Learn more about Red Hat OpenShift → redhat.com/en/technologies/cloud-computing/openshift
#RedHat #OpenShift #SecretsManagement #Kubernetes
![[vLLM Office Hours #55] - Mooncake + vLLM/llm-d Deep Dive - August 6, 2026](https://i.ytimg.com/vi/RFyeBEy1AP8/mqdefault.jpg "[vLLM Office Hours #55] - Mooncake + vLLM/llm-d Deep Dive - August 6, 2026
Welcome to vLLM office hours! These bi-weekly sessions are your chance to stay current with the vLLM ecosystem, ask questions, and hear directly from contributors and power users.
This weeks special topic: Mooncake + vLLM/llm-d Deep Dive.
vLLM project update from core maintainer Michael Goin, covering the v0.26 release plus recent model support, performance work, and quantization updates.
Hackathon spotlight: Timothy and David present TickyTalky, a winning project from the Austin Red Hat and NVIDIA vLLM hackathon, built on DeepSeek V4 Flash running on a DGX Spark.
Then the main event, with Ke Yang and Christian Angelo Velarde (Approaching.AI) and Greg Pereira (Red Hat AI). Mooncake began as the inference architecture behind Kimi and has grown into communication and storage infrastructure for large-scale LLM serving. We cover how it integrates with vLLM for PD disaggregation and cluster-wide KV cache reuse, and how llm-d wraps these pieces for distributed serving on Kubernetes.
Slides: https://docs.google.com/presentation/d/1JCwGvhFdTJt_jCFvQYTmMp2zgWBVJIoSnxciYDP0U0o
Want to join the discussion live on Google Meet? Get a calendar invite by filling out this form: https://red.ht/office-hours
Timestamps:
00:00 Intro
02:48 About vLLM
06:50 Recent Community blogs and model releases
14:10 vLLM v0.26 release update
19:43 Hackathon spotlight: TickyTalky
26:38 Mooncake architecture and ecosystem
41:08 Mooncake x vLLM integration and benchmarks
51:24 llm-d: distributed serving and tiered cache offloading")
