Merge branch 'master' into master
This commit is contained in:
@@ -27,3 +27,7 @@ defaults:
|
|||||||
showedit: true
|
showedit: true
|
||||||
|
|
||||||
permalink: pretty
|
permalink: pretty
|
||||||
|
|
||||||
|
gems:
|
||||||
|
- jekyll-redirect-from
|
||||||
|
|
||||||
|
|||||||
@@ -178,7 +178,7 @@ As an example, install a sample microservices application, a socks shop, to put
|
|||||||
To learn more about the sample microservices app, see the [GitHub README](https://github.com/microservices-demo/microservices-demo).
|
To learn more about the sample microservices app, see the [GitHub README](https://github.com/microservices-demo/microservices-demo).
|
||||||
|
|
||||||
# git clone https://github.com/microservices-demo/microservices-demo
|
# git clone https://github.com/microservices-demo/microservices-demo
|
||||||
# kubectl apply -f microservices-demo/deploy/kubernetes/manifests
|
# kubectl apply -f microservices-demo/deploy/kubernetes/manifests/sock-shop-ns.yml -f microservices-demo/deploy/kubernetes/manifests
|
||||||
|
|
||||||
You can then find out the port that the [NodePort feature of services](/docs/user-guide/services/) allocated for the front-end service by running:
|
You can then find out the port that the [NodePort feature of services](/docs/user-guide/services/) allocated for the front-end service by running:
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,7 @@
|
|||||||
---
|
---
|
||||||
|
redirect_from:
|
||||||
|
- /docs/tutorials/getting-started/create-cluster/
|
||||||
|
- /docs/tutorials/getting-started/create-cluster.html
|
||||||
---
|
---
|
||||||
|
|
||||||
<!DOCTYPE html>
|
<!DOCTYPE html>
|
||||||
|
|||||||
@@ -77,7 +77,7 @@ Operation | Syntax | Description
|
|||||||
`stop` | `kubectl stop` | Deprecated: Instead, see `kubectl delete`.
|
`stop` | `kubectl stop` | Deprecated: Instead, see `kubectl delete`.
|
||||||
`version` | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
|
`version` | `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
|
||||||
|
|
||||||
Remember: For more about command operations, see the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation.
|
Remember: For more about command operations, see the [kubectl](/docs/user-guide/kubectl) reference documentation.
|
||||||
|
|
||||||
## Resource types
|
## Resource types
|
||||||
|
|
||||||
@@ -115,7 +115,7 @@ Resource type | Abbreviated alias
|
|||||||
|
|
||||||
## Output options
|
## Output options
|
||||||
|
|
||||||
Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation.
|
Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/docs/user-guide/kubectl) reference documentation.
|
||||||
|
|
||||||
### Formatting output
|
### Formatting output
|
||||||
|
|
||||||
@@ -146,7 +146,7 @@ In this example, the following command outputs the details for a single pod as a
|
|||||||
|
|
||||||
`$ kubectl get pod web-pod-13je7 -o=yaml`
|
`$ kubectl get pod web-pod-13je7 -o=yaml`
|
||||||
|
|
||||||
Remember: See the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation for details about which output format is supported by each command.
|
Remember: See the [kubectl](/docs/user-guide/kubectl) reference documentation for details about which output format is supported by each command.
|
||||||
|
|
||||||
#### Custom columns
|
#### Custom columns
|
||||||
|
|
||||||
@@ -281,4 +281,4 @@ $ kubectl logs -f <pod-name>
|
|||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
|
|
||||||
Start using the [kubectl](/docs/user-guide/kubectl/kubectl) commands.
|
Start using the [kubectl](/docs/user-guide/kubectl) commands.
|
||||||
|
|||||||
Reference in New Issue
Block a user