@@ -29,7 +29,7 @@ entities to represent the state of your cluster. Specifically, they can describe
29
29
* The policies around how those applications behave, such as restart policies, upgrades, and fault-tolerance
30
30
31
31
A Kubernetes object is a "record of intent"--once you create the object, the Kubernetes system
32
- will constantly work to ensure that object exists. By creating an object, you're effectively
32
+ will constantly work to ensure that the object exists. By creating an object, you're effectively
33
33
telling the Kubernetes system what you want your cluster's workload to look like; this is your
34
34
cluster's * desired state* .
35
35
@@ -72,7 +72,7 @@ When you create an object in Kubernetes, you must provide the object spec that d
72
72
desired state, as well as some basic information about the object (such as a name). When you use
73
73
the Kubernetes API to create the object (either directly or via ` kubectl ` ), that API request must
74
74
include that information as JSON in the request body.
75
- Most often, you provide the information to ` kubectl ` in file known as a _ manifest_ .
75
+ Most often, you provide the information to ` kubectl ` in a file known as a _ manifest_ .
76
76
By convention, manifests are YAML (you could also use JSON format).
77
77
Tools such as ` kubectl ` convert the information from a manifest into JSON or another supported
78
78
serialization format when making the API request over HTTP.
@@ -121,7 +121,7 @@ its desired state.
121
121
Within the ` .spec ` of a StatefulSet is a [ template] ( /docs/concepts/workloads/pods/#pod-templates )
122
122
for Pod objects. That template describes Pods that the StatefulSet controller will create in order to
123
123
satisfy the StatefulSet specification.
124
- Different kinds of object can also have different ` .status ` ; again, the API reference pages
124
+ Different kinds of objects can also have different ` .status ` ; again, the API reference pages
125
125
detail the structure of that ` .status ` field, and its content for each different type of object.
126
126
127
127
{{< note >}}
0 commit comments