kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Archive kubernetes-sigs/hierarchical-namespaces 

Signed-off-by: Nabarun Pal <pal.nabarun95@gmail.com>
This commit is contained in:
Nabarun Pal 2025-04-17 11:52:31 +05:30
parent d507973947
commit 29b2cc54e7
2 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sig-auth/README.md
View File

@ -124,10 +124,6 @@ API storage support for storing data encrypted at rest in etcd.
- **Owners:**
- [kubernetes/kubernetes/staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig/OWNERS)
- [kubernetes/kubernetes/staging/src/k8s.io/apiserver/pkg/storage/value](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/value/OWNERS)
### hierarchical-namespace-controller
Controller to manage hierarchical namespaces
- **Owners:**
- [kubernetes-sigs/hierarchical-namespaces](https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/OWNERS)
### node-identity-and-isolation
Node identity management (co-owned with sig-lifecycle), and authorization restrictions for isolating workloads on separate nodes (co-owned with sig-node).
- **Owners:**

5
sigs.yaml
View File

@ -581,11 +581,6 @@ sigs:
owners:
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/apiserver/pkg/server/options/encryptionconfig/OWNERS
- https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/apiserver/pkg/storage/value/OWNERS
- name: hierarchical-namespace-controller
description: |
Controller to manage hierarchical namespaces
owners:
- https://raw.githubusercontent.com/kubernetes-sigs/hierarchical-namespaces/master/OWNERS
- name: node-identity-and-isolation
description: |
Node identity management (co-owned with sig-lifecycle), and authorization restrictions for isolating workloads on separate nodes (co-owned with sig-node).