-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inquiry about the Release Date for v1.2 #353
Comments
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. |
@mzain Thank you for your comment! |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Is this project still under active development? |
Same question, is a 1.2 still in the plans? |
Will there be a new release in the year 2024?? |
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.
The text was updated successfully, but these errors were encountered: