|
1 | 1 | # Groups and Versions and Kinds, oh my!
|
2 | 2 |
|
3 |
| -Actually, before we get started with our API, we should talk terminology |
| 3 | +Before we get started with our API, we should talk about terminology |
4 | 4 | a bit.
|
5 | 5 |
|
6 | 6 | When we talk about APIs in Kubernetes, we often use 4 terms: *groups*,
|
@@ -38,7 +38,7 @@ lowercase form of the Kind.
|
38 | 38 |
|
39 | 39 | ## So, how does that correspond to Go?
|
40 | 40 |
|
41 |
| -When we refer to a kind in a particular group-version, we'll call it |
| 41 | +When we refer to a kind in a particular group version, we'll call it |
42 | 42 | a *GroupVersionKind*, or GVK for short. Same with resources and GVR. As
|
43 | 43 | we'll see shortly, each GVK corresponds to a given root Go type in
|
44 | 44 | a package.
|
|
51 | 51 | In the next section, [Adding a new API](../cronjob-tutorial/new-api.html), we will check how the tool helps us to
|
52 | 52 | create our own APIs with the command `kubebuilder create api`.
|
53 | 53 |
|
54 |
| -The goal of this command is to create Custom Resource (CR) and Custom Resource Definition (CRD) for our Kind(s). To check it further see; [Extend the Kubernetes API with CustomResourceDefinitions][kubernetes-extend-api]. |
| 54 | +The goal of this command is to create a Custom Resource (CR) and Custom Resource Definition (CRD) for our Kind(s). To check it further see; [Extend the Kubernetes API with CustomResourceDefinitions][kubernetes-extend-api]. |
55 | 55 |
|
56 | 56 | ## But, why create APIs at all?
|
57 | 57 |
|
@@ -87,7 +87,7 @@ API server that says
|
87 | 87 | }
|
88 | 88 | ```
|
89 | 89 |
|
90 |
| -or properly look up the group-version when we go to submit a `&CronJob{}` |
| 90 | +or properly look up the group version when we go to submit a `&CronJob{}` |
91 | 91 | in an update.
|
92 | 92 |
|
93 | 93 | [kubernetes-extend-api]: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/
|
|
0 commit comments