Fixed several typos in markdown files. (#5005)
This commit is contained in:
@@ -86,7 +86,7 @@ The known stages are:
|
||||
- `RequestReceived` - The stage for events generated as soon as the audit handler receives the request.
|
||||
- `ResponseStarted` - Once the response headers are sent, but before the response body is sent. This stage is only generated for long-running requests (e.g. watch).
|
||||
- `ResponseComplete` - Once the response body has been completed.
|
||||
- `Panic` - Events generated when a panic occured.
|
||||
- `Panic` - Events generated when a panic occurred.
|
||||
|
||||
### Audit Policy
|
||||
|
||||
|
||||
@@ -262,7 +262,7 @@ kubefed init fellowship \
|
||||
[service](/docs/concepts/services-networking/service/) on the host cluster. By default,
|
||||
this service is exposed as a
|
||||
[load balanced service](/docs/user-guide/services/#type-loadbalancer).
|
||||
Most on-premises and bare-metal enviroments, and some cloud
|
||||
Most on-premises and bare-metal environments, and some cloud
|
||||
environments lack support for load balanced services. `kubefed init`
|
||||
allows exposing the federation API server as a
|
||||
[`NodePort` service](/docs/user-guide/services/#type-nodeport) on
|
||||
|
||||
@@ -294,7 +294,7 @@ Conditions:
|
||||
---- ------ ------ -------
|
||||
AbleToScale True ReadyForNewScale the last scale time was sufficiently old as to warrant a new scale
|
||||
ScalingActive True ValidMetricFound the HPA was able to successfully calculate a replica count from pods metric http_requests
|
||||
ScalingLimited False DesiredWithinRange the desired replica count is within the acceptible range
|
||||
ScalingLimited False DesiredWithinRange the desired replica count is within the acceptable range
|
||||
Events:
|
||||
```
|
||||
|
||||
|
||||
@@ -92,7 +92,7 @@ kubectl can be installed as part of the Google Cloud SDK.
|
||||
|
||||
gcloud components install kubectl
|
||||
|
||||
3. Run `kubectl version` to verify that the verison you've installed is sufficiently up-to-date.
|
||||
3. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.
|
||||
|
||||
## Install with snap on Ubuntu
|
||||
|
||||
@@ -102,7 +102,7 @@ kubectl is available as a [snap](https://snapcraft.io/) application.
|
||||
|
||||
sudo snap install kubectl --classic
|
||||
|
||||
2. Run `kubectl version` to verify that the verison you've installed is sufficiently up-to-date.
|
||||
2. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.
|
||||
|
||||
## Install with Homebrew on macOS
|
||||
|
||||
@@ -110,7 +110,7 @@ kubectl is available as a [snap](https://snapcraft.io/) application.
|
||||
|
||||
brew install kubectl
|
||||
|
||||
2. Run `kubectl version` to verify that the verison you've installed is sufficiently up-to-date.
|
||||
2. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.
|
||||
|
||||
## Install with Chocolatey on Windows
|
||||
|
||||
@@ -118,7 +118,7 @@ kubectl is available as a [snap](https://snapcraft.io/) application.
|
||||
|
||||
choco install kubernetes-cli
|
||||
|
||||
2. Run `kubectl version` to verify that the verison you've installed is sufficiently up-to-date.
|
||||
2. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.
|
||||
3. Configure kubectl to use a remote Kubernetes cluster:
|
||||
|
||||
cd C:\users\yourusername (Or wherever your %HOME% directory is)
|
||||
|
||||
Reference in New Issue
Block a user