Remove example Go code from condition descriptions

Also remove a blank line from the switchover description that caused
trailing spaces in API documentation.

Author: cbandy

build/crd/condition.yaml

@@ -0,0 +1,8 @@
+# PostgresCluster "v1beta1" is in "/spec/versions/0"
+
+- op: add
+  path: /spec/versions/0/schema/openAPIV3Schema/properties/status/properties/conditions/items/description
+  value: Condition contains details for one aspect of the current state of this API Resource.
+- op: add
+  path: /spec/versions/0/schema/openAPIV3Schema/properties/status/properties/conditions/items/properties/type/description
+  value: type of condition in CamelCase.

build/crd/kustomization.yaml

@@ -10,10 +10,16 @@ patchesJson6902:
     version: v1
     kind: CustomResourceDefinition
     name: postgresclusters.postgres-operator.crunchydata.com
-  path: validation.yaml
+  path: condition.yaml
 - target:
     group: apiextensions.k8s.io
     version: v1
     kind: CustomResourceDefinition
     name: postgresclusters.postgres-operator.crunchydata.com
   path: todos.yaml
+- target:
+    group: apiextensions.k8s.io
+    version: v1
+    kind: CustomResourceDefinition
+    name: postgresclusters.postgres-operator.crunchydata.com
+  path: validation.yaml

config/crd/bases/postgres-operator.crunchydata.com_postgresclusters.yaml

@@ -5151,14 +5151,14 @@ spec:
                         type: string
                       type:
                         default: switchover
-                        description: "Type allows you to specify the type of Patroni
+                        description: 'Type allows you to specify the type of Patroni
                           switchover that will be performed. `patronictl` supports
                           both `switchovers` and `failovers` where a `failover` is
-                          effectively a \"forced switchover\". The main difference
-                          is that `failover` can be used when there is not currently
+                          effectively a "forced switchover". The main difference is
+                          that `failover` can be used when there is not currently
                           a leader. A TargetInstance must be specified to failover.
-                          \n NOTE: The switchover type failover is reserved as the
-                          \"last resort\" case."
+                          NOTE: The switchover type failover is reserved as the "last
+                          resort" case.'
                         enum:
                         - switchover
                         - failover
@@ -7592,16 +7592,8 @@ spec:
                   current state. Known .status.conditions.type are: "PersistentVolumeResizing",
                   "ProxyAvailable"'
                 items:
-                  description: "Condition contains details for one aspect of the current
-                    state of this API Resource. --- This struct is intended for direct
-                    use as an array at the field path .status.conditions.  For example,
-                    type FooStatus struct{     // Represents the observations of a
-                    foo's current state.     // Known .status.conditions.type are:
-                    \"Available\", \"Progressing\", and \"Degraded\"     // +patchMergeKey=type
-                    \    // +patchStrategy=merge     // +listType=map     // +listMapKey=type
-                    \    Conditions []metav1.Condition `json:\"conditions,omitempty\"
-                    patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"`
-                    \n     // other fields }"
+                  description: Condition contains details for one aspect of the current
+                    state of this API Resource.
                   properties:
                     lastTransitionTime:
                       description: lastTransitionTime is the last time the condition
@@ -7643,11 +7635,7 @@ spec:
                       - Unknown
                       type: string
                     type:
-                      description: type of condition in CamelCase or in foo.example.com/CamelCase.
-                        --- Many .condition.type values are consistent across resources
-                        like Available, but because arbitrary conditions can be useful
-                        (see .node.status.conditions), the ability to deconflict is
-                        important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
+                      description: type of condition in CamelCase.
                       maxLength: 316
                       pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
                       type: string

docs/content/references/crd.md

@@ -83,7 +83,6 @@ type PatroniSwitchover struct {
 	// effectively a "forced switchover". The main difference is that `failover` can be
 	// used when there is not currently a leader. A TargetInstance must be specified to
 	// failover.
-	//
 	// NOTE: The switchover type failover is reserved as the "last resort" case.
 	// +kubebuilder:validation:Enum={switchover,failover}
 	// +kubebuilder:default:=switchover