kubernetes-retired/hierarchical-namespaces

Project still alive?

Opened this issue · 10 comments

sanderv32 commented

Hi,

Multiple issues are reported and also multiple PR's are still waiting to be merged. Is this project still alive?
The customer i'm working for is using HNS and if CVE's are not going to be fixed we need to find another solution instead of HNS.

JuJup commented

Hello
I was hoping for an affirmation, but due to the fact, that this questions remains unanswered for 3 weeks and the classification in the sig-auth annual report 2024 it does not look too good:

Archiving in 2025:

  • hierarchical-namespace-controller

However, it'd love to see it turning out the other way and the project to be continued, as I really like the idea and would love to use it in my projects.

williamohara commented

I am using it for my project and if it is going to be discontinued, I will need to fork and maintain. It's pretty crucial to my project. I don't mind inactivity - but if it is going to go away, I just assume fork it and continue it if there is more than a few interested parties

sanderv32 commented

Checkout this thread in the HNC slack channel about this topic https://kubernetes.slack.com/archives/C8E6YA9S7/p1741730793926819 @JuJup @kxs-jnadeau @sanderv32

I can't read that topic somehow

  • 👍2
pjonsson commented

I don't know anything about the sig-auth annual report, but I got some pull requests merged in the beginning of the month in this repository.

  • ❤️1
pjonsson commented

Thank you for the headsup @enj.

I don't know how the machinery works but I assume it will be hard to make a release from an archived repository so I requested a delay of the archiving until after the next release.

dhorner71 commented

i'm hopeful that this project can still stay around. may i ask what folks are using in leu of HNC as alternate solutions? this project has been recommended to us and i'm currently trying to implement in our environments.

FearlessHyena commented

From the discussion linked above this project might be forked to a different org and hopefully be maintained there
This is a great feature and it would have been really nice if it this functionality was part of core k8s