whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

It's better to be "behavior" (#7738)

Browse Source 
* Correct spelling mistake

The whole file only appeared once

* Correct spell 

Correct the word "resource" spell.

* Is "kube/.config" should be ".kube/config"

It seems that the file is ".kube/config"

* behaviour to behavior
This commit is contained in:
Sun Lintong
2018-03-16 00:53:24 +08:00
committed by k8s-ci-robot
parent ac2f75b05a
commit d942390c63
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin/admission-controllers.md
+1 -1
View File
@@ -329,7 +329,7 @@ When the admission controller sets a compute resource request, it does this by *
the pod spec rather than mutating the `container.resources` fields. the pod spec rather than mutating the `container.resources` fields.
The annotations added contain the information on what compute resources were auto-populated. The annotations added contain the information on what compute resources were auto-populated.
See the [InitialResouces proposal](https://git.k8s.io/community/contributors/design-proposals/autoscaling/initial-resources.md) for more details. See the [InitialResources proposal](https://git.k8s.io/community/contributors/design-proposals/autoscaling/initial-resources.md) for more details.
### LimitPodHardAntiAffinity ### LimitPodHardAntiAffinity
docs/admin/authentication.md
+1 -1
View File
@@ -373,7 +373,7 @@ users:
refresh-token: q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXq refresh-token: q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXq
name: oidc name: oidc
``` ```
Once your `id_token` expires, `kubectl` will attempt to refresh your `id_token` using your `refresh_token` and `client_secret` storing the new values for the `refresh_token` and `id_token` in your `kube/.config`. Once your `id_token` expires, `kubectl` will attempt to refresh your `id_token` using your `refresh_token` and `client_secret` storing the new values for the `refresh_token` and `id_token` in your `.kube/config`.
##### Option 2 - Use the `--token` Option ##### Option 2 - Use the `--token` Option
docs/admin/high-availability/building.md
+1 -1
View File
@@ -219,7 +219,7 @@ endpoints. You can switch to the new reconciler by adding the flag
{% include feature-state-alpha.md %} {% include feature-state-alpha.md %}
If you want to know more, you can check the following resources: If you want to know more, you can check the following resources:
- [issue kubernetes/kuberenetes#22609](https://github.com/kubernetes/kubernetes/issues/22609), - [issue kubernetes/kubernetes#22609](https://github.com/kubernetes/kubernetes/issues/22609),
which gives additional context which gives additional context
- [master/reconcilers/mastercount.go](https://github.com/kubernetes/kubernetes/blob/dd9981d038012c120525c9e6df98b3beb3ef19e1/pkg/master/reconcilers/mastercount.go#L63), - [master/reconcilers/mastercount.go](https://github.com/kubernetes/kubernetes/blob/dd9981d038012c120525c9e6df98b3beb3ef19e1/pkg/master/reconcilers/mastercount.go#L63),
the implementation of the master count reconciler the implementation of the master count reconciler
docs/admin/multiple-zones.md
+1 -1
View File
@@ -36,7 +36,7 @@ zone information.
Kubernetes will automatically spread the pods in a replication controller Kubernetes will automatically spread the pods in a replication controller
or service across nodes in a single-zone cluster (to reduce the impact of or service across nodes in a single-zone cluster (to reduce the impact of
failures.) With multiple-zone clusters, this spreading behaviour is failures.) With multiple-zone clusters, this spreading behavior is
extended across zones (to reduce the impact of zone failures.) (This is extended across zones (to reduce the impact of zone failures.) (This is
achieved via `SelectorSpreadPriority`). This is a best-effort achieved via `SelectorSpreadPriority`). This is a best-effort
placement, and so if the zones in your cluster are heterogeneous placement, and so if the zones in your cluster are heterogeneous