-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Hierarchical Namespace Controller As A Sig-Auth Subproject #1687
Comments
/sig auth |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hi @rjbez17 Enhancements Lead here. Any plans for this in 1.20? I see that in the description you note it's a subproject proposal - will you be needing this issue going forward? Thanks! |
@kikisdeliveryservice we still need this issue open but as it's a sub project that releases separately from k/k we don't need to track this for the release. |
Appreciate the explanation, we'll remove this from the tracking sheet. 👍 Thanks |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
HNC has been accepted as a subproject and the repo was created. Closing. /close |
@rjbez17: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hierarchical Namespace Controller As A Sig-Auth Subproject
The text was updated successfully, but these errors were encountered: