In links to ref pages, use {{page.version}}.
This commit is contained in:
committed by
Andrew Chen
parent
28f3cfdd4f
commit
f9ac865c5f
+1
-1
@@ -952,7 +952,7 @@ template:
|
||||
- [Managing Kubernetes Objects Using Imperative Commands](/docs/tutorials/object-management-kubectl/imperative-object-management-command/)
|
||||
- [Imperative Management of Kubernetes Objects Using Configuration Files](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/)
|
||||
- [Kubectl Command Reference](/docs/user-guide/kubectl/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/{{page.version}}/)
|
||||
{% endcapture %}
|
||||
|
||||
{% include templates/concept.md %}
|
||||
|
||||
@@ -83,7 +83,7 @@ The `kubectl` tool supports these additional ways to update a live object direct
|
||||
however they require a better understanding of the Kubernetes object schema.
|
||||
|
||||
- `edit`: Directly edit the raw configuration of a live object by opening its configuration in an editor.
|
||||
- `patch`: Directly modify specific fields of a live object by using a patch string.
|
||||
- `patch`: Directly modify specific fields of a live object by using a patch string.
|
||||
For more details on patch strings, see the patch section in
|
||||
[API Conventions](https://git.k8s.io/community/contributors/devel/api-conventions.md#patch-operations).
|
||||
|
||||
@@ -156,7 +156,7 @@ kubectl create --edit -f /tmp/srv.yaml
|
||||
- [Managing Kubernetes Objects Using Object Configuration (Imperative)](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/)
|
||||
- [Managing Kubernetes Objects Using Object Configuration (Declarative)](/docs/tutorials/object-management-kubectl/declarative-object-management-configuration/)
|
||||
- [Kubectl Command Reference](/docs/user-guide/kubectl/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/{{page.version}}/)
|
||||
{% endcapture %}
|
||||
|
||||
{% include templates/concept.md %}
|
||||
|
||||
+4
-4
@@ -27,7 +27,7 @@ for a discussion of the advantages and disadvantage of each kind of object manag
|
||||
## How to create objects
|
||||
|
||||
You can use `kubectl create -f` to create an object from a configuration file.
|
||||
Refer to the [kubernetes object schema reference](/docs/resources-reference/v1.6/)
|
||||
Refer to the [kubernetes object schema reference](/docs/resources-reference/{{page.version}}/)
|
||||
for details.
|
||||
|
||||
- `kubectl create -f <filename|url>`
|
||||
@@ -61,7 +61,7 @@ described in a configuration file.
|
||||
|
||||
- `kubectl get -f <filename|url> -o yaml`
|
||||
|
||||
The `-o yaml` flag specifies that the full object configuration is printed.
|
||||
The `-o yaml` flag specifies that the full object configuration is printed.
|
||||
Use `kubectl get -h` to see a list of options.
|
||||
|
||||
## Limitations
|
||||
@@ -71,7 +71,7 @@ configuration is fully defined and recorded in its configuration
|
||||
file. However when a live object is updated, and the updates are not merged
|
||||
into its configuration file, the updates will be lost the next time a `replace`
|
||||
is executed. This can happen if a controller, such as
|
||||
a HorizontalPodAutoscaler, makes updates directly to a live object. Here's
|
||||
a HorizontalPodAutoscaler, makes updates directly to a live object. Here's
|
||||
an example:
|
||||
|
||||
1. You create an object from a configuration file.
|
||||
@@ -134,7 +134,7 @@ template:
|
||||
- [Managing Kubernetes Objects Using Imperative Commands](/docs/tutorials/object-management-kubectl/imperative-object-management-command/)
|
||||
- [Managing Kubernetes Objects Using Object Configuration (Declarative)](/docs/tutorials/object-management-kubectl/declarative-object-management-configuration/)
|
||||
- [Kubectl Command Reference](/docs/user-guide/kubectl/{{page.version}}/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/{{page.version}}/)
|
||||
{% endcapture %}
|
||||
|
||||
{% include templates/concept.md %}
|
||||
|
||||
@@ -71,7 +71,7 @@ operation (create, replace, etc.), optional flags and at least one file
|
||||
name. The file specified must contain a full definition of the object
|
||||
in YAML or JSON format.
|
||||
|
||||
See the [resource reference](https://kubernetes.io/docs/resources-reference/v1.6/)
|
||||
See the [resource reference](https://kubernetes.io/docs/resources-reference/{{page.version}}/)
|
||||
for more details on object definitions.
|
||||
|
||||
**Warning:** The imperative `replace` command replaces the existing
|
||||
@@ -173,7 +173,7 @@ Disadvantages compared to imperative object configuration:
|
||||
- [Managing Kubernetes Objects Using Object Configuration (Imperative)](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/)
|
||||
- [Managing Kubernetes Objects Using Object Configuration (Declarative)](/docs/tutorials/object-management-kubectl/declarative-object-management-configuration/)
|
||||
- [Kubectl Command Reference](/docs/user-guide/kubectl/{{page.version}}/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/v1.6/)
|
||||
- [Kubernetes Object Schema Reference](/docs/resources-reference/{{page.version}}/)
|
||||
|
||||
{% comment %}
|
||||
{% endcomment %}
|
||||
|
||||
Reference in New Issue
Block a user