You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/design/building-your-csv.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ It’s common for your Operator to use multiple CRDs to link together concepts,
44
44
45
45
**Name**: The full name of your CRD
46
46
47
-
The next two sections require more explanation.
47
+
The next two sections require more explanation.
48
48
49
49
**Resources**:
50
50
Your CRDs will own one or more types of Kubernetes objects. These are listed in the resources section to inform your end-users of the objects they might need to troubleshoot or how to connect to the application, such as the Service or Ingress rule that exposes a database.
@@ -178,7 +178,7 @@ An APIService is uniquely identified by the group-version it provides and can be
178
178
179
179
**Kind**: A kind that the APIService is expected to provide.
180
180
181
-
**DeploymentName**:
181
+
**DeploymentName**:
182
182
Name of the deployment defined by your CSV that corresponds to your APIService (required for owned APIServices). During the CSV pending phase, the OLM Operator will search your CSV's InstallStrategy for a deployment spec with a matching name, and if not found, will not transition the CSV to the install ready phase.
183
183
184
184
**Resources**:
@@ -190,8 +190,8 @@ It’s recommended to only list out the objects that are important to a human, n
190
190
Essentially the same as for owned CRDs.
191
191
192
192
### APIService Resource Creation
193
-
The Lifecycle Manage is responsible for creating or replacing the Service and APIService resources for each unique owned APIService.
194
-
* Service pod selectors are copied from the CSV deployment matching the APIServiceDescription's DeploymentName.
193
+
The Lifecycle Manage is responsible for creating or replacing the Service and APIService resources for each unique owned APIService.
194
+
* Service pod selectors are copied from the CSV deployment matching the APIServiceDescription's DeploymentName.
195
195
* A new CA key/cert pair is generated for for each installation and the base64 encoded CA bundle is embedded in the respective APIService resource.
196
196
197
197
### APIService Serving Certs
@@ -232,6 +232,8 @@ The metadata section contains general metadata around the name, version and othe
232
232
233
233
**Description**: A markdown blob that describes the Operator. Important information to include: features, limitations and common use-cases for the Operator. If your Operator manages different types of installs, eg. standalone vs clustered, it is useful to give an overview of how each differs from each other, or which ones are supported for production use.
234
234
235
+
**MinKubeVersion**: A minimum version of Kubernetes that server is supposed to have so operator(s) can be deployed.
236
+
235
237
**Labels** (optional): Any key/value pairs used to organize and categorize this CSV object.
236
238
237
239
**Selectors** (optional): A label selector to identify related resources. Set this to select on current labels applied to this CSV object (if applicable).
0 commit comments