Inquiry about the Release Date for v1.2

kubernetes-sigs / hierarchical-namespaces

Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.

Apache License 2.0

607 stars 105 forks source link

Inquiry about the Release Date for v1.2 #353

Open shokada opened 7 months ago

shokada commented 7 months ago

Hi maintainers,

I am a member of an SRE team that uses the hierarchical-namespaces controller in conjunction with ArgoCD for managing our Kubernetes cluster. We have been looking forward to the new feature mentioned for the v1.2 release that introduces support for unpropagated labels.

This feature is particularly important for us as it would enable better integration between HNC and ArgoCD, by preventing ArgoCD from inadvertently taking ownership of propagated resources, which is a challenge we are currently facing.

According to the project's documentation, the estimated time of arrival for v1.2 was late 2023. However, it appears that the release has not yet been made available.

Could you kindly provide an update on the expected release date for v1.2? Any information regarding the timeline would be highly beneficial for our planning purposes.

We appreciate the effort put into developing this project and look forward to your response.

mzain commented 7 months ago

Slightly off topic, but we ran into same issue. We switched to annotations as the tracking method in ArgoCD. We didn't even need to configure unpropagate annotations feature because on ArgoCD, it handles it gracefully and doesn't track the resources copied by HNC.

Let me know if you want more info. You can also find me on slack.

shokada commented 7 months ago

@mzain Thank you for your comment! I see, so by setting application.resourceTrackingMethod: annotation in ArgoCD, resources that are copied won't be tracked. We might consider using this method to prevent tracking of propagated resources until v1.2 is released, if necessary.

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

david-garcia-garcia commented 3 months ago

/remove-lifecycle stale

everflux commented 3 months ago

Is this project still under active development?

testinfected commented 2 months ago

Same question, is a 1.2 still in the plans?

ESmithaaS commented 2 weeks ago

Will there be a new release in the year 2024??