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
description: GrpcPodConfig exposes different overrides for the pod spec of the CatalogSource Pod. Only used when SourceType = SourceTypeGrpc and Image is set.
72
+
type: object
73
+
properties:
74
+
nodeSelector:
75
+
description: NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node's labels for the pod to be scheduled on that node.
76
+
type: object
77
+
additionalProperties:
78
+
type: string
79
+
priorityClassName:
80
+
description: If specified, indicates the pod's priority. If not specified, the pod priority will be default or zero if there is no default.
81
+
type: string
82
+
tolerations:
83
+
description: Tolerations are the catalog source's pod's tolerations.
84
+
type: array
85
+
items:
86
+
description: The pod this Toleration is attached to tolerates any taint that matches the triple <key,value,effect> using the matching operator <operator>.
87
+
type: object
88
+
properties:
89
+
effect:
90
+
description: Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
91
+
type: string
92
+
key:
93
+
description: Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
94
+
type: string
95
+
operator:
96
+
description: Operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.
97
+
type: string
98
+
tolerationSeconds:
99
+
description: TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
100
+
type: integer
101
+
format: int64
102
+
value:
103
+
description: Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
description: OLMConfig is a resource responsible for configuring OLM.
23
+
type: object
24
+
required:
25
+
- metadata
26
+
properties:
27
+
apiVersion:
28
+
description: 'APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
29
+
type: string
30
+
kind:
31
+
description: 'Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
32
+
type: string
33
+
metadata:
34
+
type: object
35
+
spec:
36
+
description: OLMConfigSpec is the spec for an OLMConfig resource.
37
+
type: object
38
+
properties:
39
+
features:
40
+
description: Features contains the list of configurable OLM features.
41
+
type: object
42
+
properties:
43
+
disableCopiedCSVs:
44
+
description: DisableCopiedCSVs is used to disable OLM's "Copied CSV" feature for operators installed at the cluster scope, where a cluster scoped operator is one that has been installed in an OperatorGroup that targets all namespaces. When reenabled, OLM will recreate the "Copied CSVs" for each cluster scoped operator.
45
+
type: boolean
46
+
status:
47
+
description: OLMConfigStatus is the status for an OLMConfig resource.
48
+
type: object
49
+
properties:
50
+
conditions:
51
+
type: array
52
+
items:
53
+
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 }"
54
+
type: object
55
+
required:
56
+
- lastTransitionTime
57
+
- message
58
+
- reason
59
+
- status
60
+
- type
61
+
properties:
62
+
lastTransitionTime:
63
+
description: lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.
64
+
type: string
65
+
format: date-time
66
+
message:
67
+
description: message is a human readable message indicating details about the transition. This may be an empty string.
68
+
type: string
69
+
maxLength: 32768
70
+
observedGeneration:
71
+
description: observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.
72
+
type: integer
73
+
format: int64
74
+
minimum: 0
75
+
reason:
76
+
description: reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.
77
+
type: string
78
+
maxLength: 1024
79
+
minLength: 1
80
+
pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
81
+
status:
82
+
description: status of the condition, one of True, False, Unknown.
83
+
type: string
84
+
enum:
85
+
- "True"
86
+
- "False"
87
+
- Unknown
88
+
type:
89
+
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: Name of the environment variable. Must be a C_IDENTIFIER.
77
77
type: string
78
78
value:
79
-
description: 'Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".'
79
+
description: 'Variable references $(VAR_NAME) are expanded using the previously defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. "$$(VAR_NAME)" will produce the string literal "$(VAR_NAME)". Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".'
80
80
type: string
81
81
valueFrom:
82
82
description: Source for the environment variable's value. Cannot be used if value is not empty.
@@ -555,7 +555,23 @@ spec:
555
555
items:
556
556
type: string
557
557
dataSource:
558
-
description: 'This field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) * An existing custom resource that implements data population (Alpha) In order to use custom resource types that implement data population, the AnyVolumeDataSource feature gate must be enabled. If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source.'
558
+
description: 'This field can be used to specify either: * An existing VolumeSnapshot object (snapshot.storage.k8s.io/VolumeSnapshot) * An existing PVC (PersistentVolumeClaim) If the provisioner or an external controller can support the specified data source, it will create a new volume based on the contents of the specified data source. If the AnyVolumeDataSource feature gate is enabled, this field will always have the same contents as the DataSourceRef field.'
559
+
type: object
560
+
required:
561
+
- kind
562
+
- name
563
+
properties:
564
+
apiGroup:
565
+
description: APIGroup is the group for the resource being referenced. If APIGroup is not specified, the specified Kind must be in the core API group. For any other third-party types, APIGroup is required.
566
+
type: string
567
+
kind:
568
+
description: Kind is the type of resource being referenced
569
+
type: string
570
+
name:
571
+
description: Name is the name of resource being referenced
572
+
type: string
573
+
dataSourceRef:
574
+
description: 'Specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any local object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the DataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, both fields (DataSource and DataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. There are two important differences between DataSource and DataSourceRef: * While DataSource only allows two specific types of objects, DataSourceRef allows any non-core object, as well as PersistentVolumeClaim objects. * While DataSource ignores disallowed values (dropping them), DataSourceRef preserves all values, and generates an error if a disallowed value is specified. (Alpha) Using this field requires the AnyVolumeDataSource feature gate to be enabled.'
0 commit comments