-
Notifications
You must be signed in to change notification settings - Fork 163
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: forbidden node labels and annotations
- Loading branch information
Maksim Fedotov
committed
Oct 28, 2021
1 parent
f2746fb
commit 49189f6
Showing
4 changed files
with
37 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# Denying specific user-defined labels or annotations on Nodes | ||
|
||
When using `capsule` together with [capsule-proxy](https://github.com/clastix/capsule-proxy), Bill can allow Tenant Owners to [modify Nodes](../../proxy/overview.md). | ||
|
||
By default, it will allow tenant owners to add and modify any label or annotation on their nodes. | ||
|
||
But there are some scenarios, when tenant owners should not have an ability to add or modify specific labels or annotations (there are some types of labels or annotations, which must be protected from modifications - for example, which are set by `cloud-providers` or `autoscalers`). | ||
|
||
Bill, the cluster admin, can deny Tenant Owners to add or modify specific labels and annotations on Nodes: | ||
|
||
```yaml | ||
kubectl apply -f - << EOF | ||
apiVersion: capsule.clastix.io/v1alpha1 | ||
kind: CapsuleConfiguration | ||
metadata: | ||
name: default | ||
annotations: | ||
capsule.clastix.io/forbidden-node-labels: foo.acme.net,bar.acme.net | ||
capsule.clastix.io/forbidden-node-labels-regexp: .*.acme.net | ||
capsule.clastix.io/forbidden-node-annotations: foo.acme.net,bar.acme.net | ||
capsule.clastix.io/forbidden-node-annotations-regexp: .*.acme.net | ||
spec: | ||
userGroups: | ||
- capsule.clastix.io | ||
- system:serviceaccounts:default | ||
EOF | ||
``` | ||
# What’s next | ||
|
||
This ends our tour in Capsule use cases. As we improve Capsule, more use cases about multi-tenancy, policy admission control, and cluster governance will be covered in the future. | ||
|
||
Stay tuned! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters