From 6a1caa355aca001f4127160a4d131c521b08c93e Mon Sep 17 00:00:00 2001 From: Michael Date: Fri, 15 Jul 2022 17:10:48 +0800 Subject: [PATCH] [en] fix typos in /projected-volumes.md --- content/en/docs/concepts/storage/projected-volumes.md | 4 +++- .../custom-resources/custom-resource-definitions.md | 7 +++---- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/content/en/docs/concepts/storage/projected-volumes.md b/content/en/docs/concepts/storage/projected-volumes.md index df67132cf5..a404a26e5e 100644 --- a/content/en/docs/concepts/storage/projected-volumes.md +++ b/content/en/docs/concepts/storage/projected-volumes.md @@ -73,7 +73,7 @@ volume mount will not receive updates for those volume sources. ## SecurityContext interactions -The [proposal](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2451-service-account-token-volumes#proposal) for file permission handling in projected service account volume enhancement introduced the projected files having the the correct owner permissions set. +The [proposal](https://git.k8s.io/enhancements/keps/sig-storage/2451-service-account-token-volumes#proposal) for file permission handling in projected service account volume enhancement introduced the projected files having the correct owner permissions set. ### Linux @@ -99,6 +99,7 @@ into their own volume mount outside of `C:\`. By default, the projected files will have the following ownership as shown for an example projected volume file: + ```powershell PS C:\> Get-Acl C:\var\run\secrets\kubernetes.io\serviceaccount\..2021_08_31_22_22_18.318230061\ca.crt | Format-List @@ -111,6 +112,7 @@ Access : NT AUTHORITY\SYSTEM Allow FullControl Audit : Sddl : O:BAG:SYD:AI(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;0x1200a9;;;BU) ``` + This implies all administrator users like `ContainerAdministrator` will have read, write and execute access while, non-administrator users will have read and execute access. diff --git a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md index 7766bcedf3..812c723a51 100644 --- a/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md +++ b/content/en/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md @@ -362,9 +362,9 @@ and create it: kubectl create --validate=false -f my-crontab.yaml -o yaml ``` -your output is similar to: +Your output is similar to: -```console +```yaml apiVersion: stable.example.com/v1 kind: CronTab metadata: @@ -836,7 +836,7 @@ Validation Rules Examples: | `has(self.expired) && self.created + self.ttl < self.expired` | Validate that 'expired' date is after a 'create' date plus a 'ttl' duration | | `self.health.startsWith('ok')` | Validate a 'health' string field has the prefix 'ok' | | `self.widgets.exists(w, w.key == 'x' && w.foo < 10)` | Validate that the 'foo' property of a listMap item with a key 'x' is less than 10 | -| `type(self) == string ? self == '100%' : self == 1000` | Validate an int-or-string field for both the the int and string cases | +| `type(self) == string ? self == '100%' : self == 1000` | Validate an int-or-string field for both the int and string cases | | `self.metadata.name.startsWith(self.prefix)` | Validate that an object's name has the prefix of another field value | | `self.set1.all(e, !(e in self.set2))` | Validate that two listSets are disjoint | | `size(self.names) == size(self.details) && self.names.all(n, n in self.details)` | Validate the 'details' map is keyed by the items in the 'names' listSet | @@ -844,7 +844,6 @@ Validation Rules Examples: Xref: [Supported evaluation on CEL](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#evaluation) - - If the Rule is scoped to the root of a resource, it may make field selection into any fields declared in the OpenAPIv3 schema of the CRD as well as `apiVersion`, `kind`, `metadata.name` and `metadata.generateName`. This includes selection of fields in both the `spec` and `status` in the