HNC v0.4 is intended to stabilize HNC's UX. From now on, we will not make backwards-incompatible changes to the v1alpha1 API; we will either maintain compatibility or introduce a new API version after a suitable deprecation period.

To install this release, run the following commands:

HNC_VERSION=v0.4.0-rc2
kubectl apply -f https://github.com/kubernetes-sigs/multi-tenancy/releases/download/hnc-${HNC_VERSION}/hnc-manager.yaml

For more instructions, see the user guide.

Changelog

A complete list of changes since HNC v0.3 is available here.

Since HNC v0.4.0 rc1

Fixed:

• Allow HNC to work without Stackdriver (#770)

Since HNC v0.3

Key new/changed features in this release include:

• The user interface for creating subnamespaces has changed - rather than creating a HierarchicalNamespace object, you now create a SubnamespaceAnchor object. Otherwise, the UX is identical (issue #704 plus doc updates)
• HNC no longer requires cert-manager to run (#653)
• The CritCycle condition is now applied to all namespaces involved in a cycle, not just one randomly-selected one (#666)
• Tree labels are updated even in the presence of critical conditions (#660)
• Namespace conditions are now available as a metric (#736)

Known issues

• The object validators are not all set up correctly and do not respond to changes in HNCConfiguration. That is, if you overwrite or delete an object managed by HNC, it may appear to succeed, but HNC will immediately overwrite it (#761)