XRD detailed
While looking at Composite Resource Definition (XRD) in the previous chapter, we touched on limited configuration options required to learn the basics of XR. It’s now time to look at more detailed configuration options to build clean and robust XR APIs. A significant part of the details we will look at are about openAPIV3Schema, which is used to define the input and output of the XR API. The following are the topics we will cover in this section:
- Naming the versions
- The openAPIV3Schema structure
- The additional parameter of an attribute
- Printer columns
Let’s start with the Naming the versions section.
Naming the versions
The version name of our XRD cannot have any random string. It has a specific validation inherited from the CRDs and standard Kubernetes APIs. The string can contain only lowercase alphanumeric characters and -. Also, it must always start with an alphabetic character and end with an alphanumeric character,...
