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: api/core/v1alpha1/clustercatalog_types.go
+10-12Lines changed: 10 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ type ClusterCatalogSpec struct {
87
87
// priority is an optional field that allows the user to define a priority for a ClusterCatalog.
88
88
// A ClusterCatalog's priority is used by clients as a tie-breaker between ClusterCatalogs that meet the client's requirements.
89
89
// For example, in the case where multiple ClusterCatalogs provide the same bundle.
90
-
// A higher number means higher priority. Negative number as also accepted.
90
+
// A higher number means higher priority. Negative numbers are also accepted.
91
91
// When omitted, the default priority is 0.
92
92
// +kubebuilder:default:=0
93
93
// +optional
@@ -106,15 +106,15 @@ type ClusterCatalogStatus struct {
106
106
// - Message: a human-readable message that further elaborates on the state of the condition.
107
107
//
108
108
// The current set of condition types are:
109
-
// - "Unpacked", epresents whether, or not, the catalog contents have been successfully unpacked.
110
-
// - "Deleted", represents whether, or not, the catalog contents have been successfully deleted.
109
+
// - "Serving", which represents whether or not the contents of the catalog are being served via the HTTP(S) web server.
110
+
// - "Progressing", which represents whether or not the ClusterCatalog is progressing towards a new state.
111
111
//
112
112
// The current set of reasons are:
113
-
// - "UnpackPending", this reason is set on the "Unpack" condition when unpacking the catalog has not started.
114
-
// - "Unpacking", this reason is set on the "Unpack" condition when the catalog is being unpacked.
115
-
// - "UnpackSuccessful", this reason is set on the "Unpack" condition when unpacking the catalog is successful and the catalog metadata is available to the cluster.
116
-
// - "FailedToStore", this reason is set on the "Unpack" condition when an error has been encountered while storing the contents of the catalog.
117
-
// - "FailedToDelete", this reason is set on the "Delete" condition when an error has been encountered while deleting the contents of the catalog.
113
+
// - "Succeeded", this reason is set on the "Progressing" condition when progressing to a new state is successful.
114
+
// - "Blocked", this reason is set on the "Progressing" condition when the ClusterCatalog controller has encountered an error that requires manual intervention for recovery.
115
+
// - "Retrying", this reason is set on the "Progressing" condition when the ClusterCatalog controller has encountered an error that might be resolvable on subsequent reconciliation attempts.
116
+
// - "Available", this reason is set on the "Serving" condition when the contents of the ClusterCatalog are being served via an endpoint on the HTTP(S) web server.
117
+
// - "Unavailable", this reason is set on the "Serving" condition when there is not an endpoint on the HTTP(S) web server that is serving the contents of the ClusterCatalog.
Copy file name to clipboardExpand all lines: config/base/crd/bases/olm.operatorframework.io_clustercatalogs.yaml
+10-12Lines changed: 10 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ spec:
57
57
priority is an optional field that allows the user to define a priority for a ClusterCatalog.
58
58
A ClusterCatalog's priority is used by clients as a tie-breaker between ClusterCatalogs that meet the client's requirements.
59
59
For example, in the case where multiple ClusterCatalogs provide the same bundle.
60
-
A higher number means higher priority. Negative number as also accepted.
60
+
A higher number means higher priority. Negative numbers are also accepted.
61
61
When omitted, the default priority is 0.
62
62
format: int32
63
63
type: integer
@@ -142,15 +142,15 @@ spec:
142
142
- Message: a human-readable message that further elaborates on the state of the condition.
143
143
144
144
The current set of condition types are:
145
-
- "Unpacked", epresents whether, or not, the catalog contents have been successfully unpacked.
146
-
- "Deleted", represents whether, or not, the catalog contents have been successfully deleted.
145
+
- "Serving", which represents whether or not the contents of the catalog are being served via the HTTP(S) web server.
146
+
- "Progressing", which represents whether or not the ClusterCatalog is progressing towards a new state.
147
147
148
148
The current set of reasons are:
149
-
- "UnpackPending", this reason is set on the "Unpack" condition when unpacking the catalog has not started.
150
-
- "Unpacking", this reason is set on the "Unpack" condition when the catalog is being unpacked.
151
-
- "UnpackSuccessful", this reason is set on the "Unpack" condition when unpacking the catalog is successful and the catalog metadata is available to the cluster.
152
-
- "FailedToStore", this reason is set on the "Unpack" condition when an error has been encountered while storing the contents of the catalog.
153
-
- "FailedToDelete", this reason is set on the "Delete" condition when an error has been encountered while deleting the contents of the catalog.
149
+
- "Succeeded", this reason is set on the "Progressing" condition when progressing to a new state is successful.
150
+
- "Blocked", this reason is set on the "Progressing" condition when the ClusterCatalog controller has encountered an error that requires manual intervention for recovery.
151
+
- "Retrying", this reason is set on the "Progressing" condition when the ClusterCatalog controller has encountered an error that might be resolvable on subsequent reconciliation attempts.
152
+
- "Available", this reason is set on the "Serving" condition when the contents of the ClusterCatalog are being served via an endpoint on the HTTP(S) web server.
153
+
- "Unavailable", this reason is set on the "Serving" condition when there is not an endpoint on the HTTP(S) web server that is serving the contents of the ClusterCatalog.
154
154
items:
155
155
description: Condition contains details for one aspect of the current
0 commit comments