<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7" -->

---
title: Volcano v1.16 Released: NamespaceQueue, fairshare, and a...
description: Volcano v1.16.0 adds NamespaceQueue and a fairshare scheduling plugin. NamespaceQueue lets tenants manage hierarchical queues and quotas inside their own...
canonical: https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Volcano v1.16 Released: NamespaceQueue, fairshare, and a broader HyperNode ecosystem | daily.dev
og:description: Volcano v1.16.0 adds NamespaceQueue and a fairshare scheduling plugin. NamespaceQueue lets tenants manage hierarchical queues and quotas inside their own...
og:url: https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7
og:image: https://api.daily.dev/og/posts/imt7vg8U7.png
og:image:alt: Volcano v1.16 Released: NamespaceQueue, fairshare, and a broader HyperNode ecosystem
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Volcano v1.16 Released: NamespaceQueue, fairshare, and a broader HyperNode ecosystem

**[CNCF](https://daily.dev/sources/cncf)** · 11 min read · 0 upvotes · 0 comments

## Summary

Volcano v1.16.0 adds NamespaceQueue and a fairshare scheduling plugin. NamespaceQueue lets tenants manage hierarchical queues and quotas inside their own namespace, within resource pools authorized by admins. Fairshare, inspired by Slurm, tracks cumulative resource-seconds per namespace with an exponential decay defaulting to a four-hour half-life, improving fairness across teams sharing a queue. The release also makes the HyperNode controller independently deployable so other schedulers can reuse its topology discovery, adds PodGroup topology anti-affinity to spread replicas across supernodes, and introduces an Unschedulable Job Cache that skips redundant scheduling checks, with a default five-minute watchdog retry. It also adds Kubernetes 1.36 support and requires Go 1.26 for source builds.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.cncf.io/blog/2026/10/28/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem>

## Questions this post answers

### What does the NamespaceQueue feature in Volcano v1.16.0 do?

NamespaceQueue is a namespaced resource in Volcano v1.16.0 that lets tenants manage hierarchical queues, quotas, and resource sharing within their own namespace. Administrators authorize a namespace to attach its queue hierarchy to a cluster Queue via spec.allowedNamespaces, after which tenants manage sub-hierarchies without needing cluster-wide queue access. It requires hierarchical capacity scheduling and is disabled by default.

_Teams designing multi-tenant Kubernetes queue structures can track scheduler features like this via daily.dev._

### How does the fairshare plugin in Volcano decide scheduling order between namespaces sharing a queue?

The fairshare plugin tracks cumulative resource-seconds consumed by each namespace within a shared queue, inspired by Slurm fair-share scheduling. Consumption decays exponentially with a configurable half-life defaulting to four hours, so namespaces with lower historical usage get earlier consideration while old usage loses influence over time. It complements DRF's current-resource fairness and does not preempt running jobs.

_Engineers tuning fair scheduling across teams can follow updates like Volcano's fairshare plugin on daily.dev._

### What is the Unschedulable Job Cache in Volcano v1.16.0 and what is its default retry interval?

The Unschedulable Job Cache records why a Job could not be scheduled and skips repeated checks until a relevant change makes retrying worthwhile, reducing redundant work in clusters with large pending backlogs. A watchdog retries cached Jobs after a configurable maximum skip duration that defaults to five minutes, and the cache clears on scheduler restart. It is disabled by default and enabled via a scheduler feature gate.

_Operators chasing scheduler backlog performance can keep up with changes like this on daily.dev._

## Similar posts on daily.dev

- [Beyond Batch: Volcano Evolves into the AI-Native Unified Scheduling Platform](https://daily.dev/posts/beyond-batch-volcano-evolves-into-the-ai-native-unified-scheduling-platform-fa9jezis1) · CNCF · 0 upvotes · 0 comments
- [Inspect Volcano workloads faster with Headlamp](https://daily.dev/posts/inspect-volcano-workloads-faster-with-headlamp-yutkvfhwm) · Kubernetes · 3 upvotes · 0 comments
- [New Features We Find Exciting in the Kubernetes 1.36 Release](https://daily.dev/posts/new-features-we-find-exciting-in-the-kubernetes-1-36-release-1b2qr04hy) · MetalBear · 10 upvotes · 2 comments
- [Configure admission fair sharing in Red Hat build of Kueue 1.4](https://daily.dev/posts/configure-admission-fair-sharing-in-red-hat-build-of-kueue-1-4-5cbb0b8uc) · Red Hat Developer · 0 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#multi-tenancy](https://daily.dev/tags/multi-tenancy)

[View this post on daily.dev](https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Volcano v1.16 Released: NamespaceQueue, fairshare, and a broader HyperNode ecosystem","url":"https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7"},"datePublished":"2026-10-28T20:45:46.740Z","dateModified":"2026-10-28T21:36:42.889Z","description":"Volcano v1.16.0 adds NamespaceQueue and a fairshare scheduling plugin. NamespaceQueue lets tenants manage hierarchical queues and quotas inside their own...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/829f765afb531d43e78bc344cebe7ce5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/829f765afb531d43e78bc344cebe7ce5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CNCF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CNCF","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/55536a03390741eebd96d2f9b74d2d8d","url":"https://daily.dev/sources/cncf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,multi-tenancy","timeRequired":"PT11M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CNCF","item":"https://daily.dev/sources/cncf"},{"@type":"ListItem","position":3,"name":"Volcano v1.16 Released: NamespaceQueue, fairshare, and a broader HyperNode ecosystem"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/volcano-v1-16-released-namespacequeue-fairshare-and-a-broader-hypernode-ecosystem-imt7vg8u7#faq","mainEntity":[{"@type":"Question","name":"What does the NamespaceQueue feature in Volcano v1.16.0 do?","acceptedAnswer":{"@type":"Answer","text":"NamespaceQueue is a namespaced resource in Volcano v1.16.0 that lets tenants manage hierarchical queues, quotas, and resource sharing within their own namespace. Administrators authorize a namespace to attach its queue hierarchy to a cluster Queue via spec.allowedNamespaces, after which tenants manage sub-hierarchies without needing cluster-wide queue access. It requires hierarchical capacity scheduling and is disabled by default. Teams designing multi-tenant Kubernetes queue structures can track scheduler features like this via daily.dev."}},{"@type":"Question","name":"How does the fairshare plugin in Volcano decide scheduling order between namespaces sharing a queue?","acceptedAnswer":{"@type":"Answer","text":"The fairshare plugin tracks cumulative resource-seconds consumed by each namespace within a shared queue, inspired by Slurm fair-share scheduling. Consumption decays exponentially with a configurable half-life defaulting to four hours, so namespaces with lower historical usage get earlier consideration while old usage loses influence over time. It complements DRF's current-resource fairness and does not preempt running jobs. Engineers tuning fair scheduling across teams can follow updates like Volcano's fairshare plugin on daily.dev."}},{"@type":"Question","name":"What is the Unschedulable Job Cache in Volcano v1.16.0 and what is its default retry interval?","acceptedAnswer":{"@type":"Answer","text":"The Unschedulable Job Cache records why a Job could not be scheduled and skips repeated checks until a relevant change makes retrying worthwhile, reducing redundant work in clusters with large pending backlogs. A watchdog retries cached Jobs after a configurable maximum skip duration that defaults to five minutes, and the cache clears on scheduler restart. It is disabled by default and enabled via a scheduler feature gate. Operators chasing scheduler backlog performance can keep up with changes like this on daily.dev."}}]}
```

