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
Co-authored-by: Per Goncalves da Silva <pegoncal@redhat.com>
Co-authored-by: Predrag Knezevic <pknezevi@redhat.com
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Copy file name to clipboardExpand all lines: api/v1/clusterextension_types.go
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -482,8 +482,11 @@ type ClusterExtensionStatus struct {
482
482
// When Progressing is True and the Reason is Succeeded, the ClusterExtension is making progress towards a new state.
483
483
// When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts.
484
484
// When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery.
485
+
// <opcon:experimental:description>
486
+
// When Progressing is True and Reason is RollingOut, the ClusterExtension has one or more ClusterExtensionRevisions in active roll out.
487
+
// </opcon:experimental:description>
485
488
//
486
-
// When the ClusterExtension is sourced from a catalog, if may also communicate a deprecation condition.
489
+
// When the ClusterExtension is sourced from a catalog, it may also communicate a deprecation condition.
487
490
// These are indications from a package owner to guide users away from a particular package, channel, or bundle.
488
491
// BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog.
489
492
// ChannelDeprecated is set if the requested channel is marked deprecated in the catalog.
// ClusterExtensionRevisionSpec defines the desired state of ClusterExtensionRevision.
@@ -190,17 +183,16 @@ type ClusterExtensionRevisionStatus struct {
190
183
// ClusterExtensionRevision.
191
184
//
192
185
// The Progressing condition represents whether the revision is actively rolling out:
193
-
// - When status is True and reason is Progressing, the revision rollout is actively making progress and is in transition.
194
-
// - When Progressing is not present, the revision is not currently in transition.
186
+
// - When status is True and reason is RollingOut, the ClusterExtensionRevision rollout is actively making progress and is in transition.
187
+
// - When status is True and reason is Retrying, the ClusterExtensionRevision has encountered an error that could be resolved on subsequent reconciliation attempts.
188
+
// - When status is True and reason is Succeeded, the ClusterExtensionRevision has reached the desired state.
189
+
// - When status is False and reason is Blocked, the ClusterExtensionRevision has encountered an error that requires manual intervention for recovery.
190
+
// - When status is False and reason is Archived, the ClusterExtensionRevision is archived and not being actively reconciled.
195
191
//
196
192
// The Available condition represents whether the revision has been successfully rolled out and is available:
197
-
// - When status is True and reason is Available, the revision has been successfully rolled out and all objects pass their readiness probes.
198
-
// - When status is False and reason is Incomplete, the revision rollout has not yet completed but no specific failures have been detected.
193
+
// - When status is True and reason is ProbesSucceeded, the revision has been successfully rolled out and all objects pass their readiness probes.
199
194
// - When status is False and reason is ProbeFailure, one or more objects are failing their readiness probes during rollout.
200
-
// - When status is False and reason is ReconcileFailure, the revision has encountered a general reconciliation failure.
201
-
// - When status is False and reason is RevisionValidationFailure, the revision failed preflight validation checks.
202
-
// - When status is False and reason is PhaseValidationError, a phase within the revision failed preflight validation checks.
203
-
// - When status is False and reason is ObjectCollisions, objects in the revision collide with existing cluster objects that cannot be adopted.
195
+
// - When status is Unknown and reason is Reconciling, the revision has encountered an error that prevented it from observing the probes.
204
196
// - When status is Unknown and reason is Archived, the revision has been archived and its objects have been torn down.
205
197
// - When status is Unknown and reason is Migrated, the revision was migrated from an existing release and object status probe results have not yet been observed.
206
198
//
@@ -217,6 +209,7 @@ type ClusterExtensionRevisionStatus struct {
Copy file name to clipboardExpand all lines: docs/api-reference/olmv1-api-reference.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -359,7 +359,7 @@ _Appears in:_
359
359
360
360
| Field | Description | Default | Validation |
361
361
| --- | --- | --- | --- |
362
-
| `conditions` _[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#condition-v1-meta) array_ | The set of condition types which apply to all spec.source variations are Installed and Progressing.<br />The Installed condition represents whether or not the bundle has been installed for this ClusterExtension.<br />When Installed is True and the Reason is Succeeded, the bundle has been successfully installed.<br />When Installed is False and the Reason is Failed, the bundle has failed to install.<br />The Progressing condition represents whether or not the ClusterExtension is advancing towards a new state.<br />When Progressing is True and the Reason is Succeeded, the ClusterExtension is making progress towards a new state.<br />When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts.<br />When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery.<br />When the ClusterExtension is sourced from a catalog, if may also communicate a deprecation condition.<br />These are indications from a package owner to guide users away from a particular package, channel, or bundle.<br />BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog.<br />ChannelDeprecated is set if the requested channel is marked deprecated in the catalog.<br />PackageDeprecated is set if the requested package is marked deprecated in the catalog.<br />Deprecated is a rollup condition that is present when any of the deprecated conditions are present. | | |
362
+
| `conditions` _[Condition](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#condition-v1-meta) array_ | The set of condition types which apply to all spec.source variations are Installed and Progressing.<br />The Installed condition represents whether or not the bundle has been installed for this ClusterExtension.<br />When Installed is True and the Reason is Succeeded, the bundle has been successfully installed.<br />When Installed is False and the Reason is Failed, the bundle has failed to install.<br />The Progressing condition represents whether or not the ClusterExtension is advancing towards a new state.<br />When Progressing is True and the Reason is Succeeded, the ClusterExtension is making progress towards a new state.<br />When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts.<br />When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery.<br /><opcon:experimental:description><br />When Progressing is True and Reason is RollingOut, the ClusterExtension has one or more ClusterExtensionRevisions in active roll out.<br /></opcon:experimental:description><br />When the ClusterExtension is sourced from a catalog, it may also communicate a deprecation condition.<br />These are indications from a package owner to guide users away from a particular package, channel, or bundle.<br />BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog.<br />ChannelDeprecated is set if the requested channel is marked deprecated in the catalog.<br />PackageDeprecated is set if the requested package is marked deprecated in the catalog.<br />Deprecated is a rollup condition that is present when any of the deprecated conditions are present. | | |
363
363
|`install`_[ClusterExtensionInstallStatus](#clusterextensioninstallstatus)_| install is a representation of the current installation status for this ClusterExtension. |||
Copy file name to clipboardExpand all lines: helm/olmv1/base/operator-controller/crd/experimental/olm.operatorframework.io_clusterextensionrevisions.yaml
The Progressing condition represents whether the revision is actively rolling out:
193
-
- When status is True and reason is Progressing, the revision rollout is actively making progress and is in transition.
194
-
- When Progressing is not present, the revision is not currently in transition.
196
+
- When status is True and reason is RollingOut, the ClusterExtensionRevision rollout is actively making progress and is in transition.
197
+
- When status is True and reason is Retrying, the ClusterExtensionRevision has encountered an error that could be resolved on subsequent reconciliation attempts.
198
+
- When status is True and reason is Succeeded, the ClusterExtensionRevision has reached the desired state.
199
+
- When status is False and reason is Blocked, the ClusterExtensionRevision has encountered an error that requires manual intervention for recovery.
200
+
- When status is False and reason is Archived, the ClusterExtensionRevision is archived and not being actively reconciled.
195
201
196
202
The Available condition represents whether the revision has been successfully rolled out and is available:
197
-
- When status is True and reason is Available, the revision has been successfully rolled out and all objects pass their readiness probes.
198
-
- When status is False and reason is Incomplete, the revision rollout has not yet completed but no specific failures have been detected.
203
+
- When status is True and reason is ProbesSucceeded, the revision has been successfully rolled out and all objects pass their readiness probes.
199
204
- When status is False and reason is ProbeFailure, one or more objects are failing their readiness probes during rollout.
200
-
- When status is False and reason is ReconcileFailure, the revision has encountered a general reconciliation failure.
201
-
- When status is False and reason is RevisionValidationFailure, the revision failed preflight validation checks.
202
-
- When status is False and reason is PhaseValidationError, a phase within the revision failed preflight validation checks.
203
-
- When status is False and reason is ObjectCollisions, objects in the revision collide with existing cluster objects that cannot be adopted.
205
+
- When status is Unknown and reason is Reconciling, the revision has encountered an error that prevented it from observing the probes.
204
206
- When status is Unknown and reason is Archived, the revision has been archived and its objects have been torn down.
205
207
- When status is Unknown and reason is Migrated, the revision was migrated from an existing release and object status probe results have not yet been observed.
Copy file name to clipboardExpand all lines: helm/olmv1/base/operator-controller/crd/experimental/olm.operatorframework.io_clusterextensions.yaml
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -518,7 +518,9 @@ spec:
518
518
When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts.
519
519
When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery.
520
520
521
-
When the ClusterExtension is sourced from a catalog, if may also communicate a deprecation condition.
521
+
When Progressing is True and Reason is RollingOut, the ClusterExtension has one or more ClusterExtensionRevisions in active roll out.
522
+
523
+
When the ClusterExtension is sourced from a catalog, it may also communicate a deprecation condition.
522
524
These are indications from a package owner to guide users away from a particular package, channel, or bundle.
523
525
BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog.
524
526
ChannelDeprecated is set if the requested channel is marked deprecated in the catalog.
Copy file name to clipboardExpand all lines: helm/olmv1/base/operator-controller/crd/standard/olm.operatorframework.io_clusterextensions.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -479,7 +479,7 @@ spec:
479
479
When Progressing is True and the Reason is Retrying, the ClusterExtension has encountered an error that could be resolved on subsequent reconciliation attempts.
480
480
When Progressing is False and the Reason is Blocked, the ClusterExtension has encountered an error that requires manual intervention for recovery.
481
481
482
-
When the ClusterExtension is sourced from a catalog, if may also communicate a deprecation condition.
482
+
When the ClusterExtension is sourced from a catalog, it may also communicate a deprecation condition.
483
483
These are indications from a package owner to guide users away from a particular package, channel, or bundle.
484
484
BundleDeprecated is set if the requested bundle version is marked deprecated in the catalog.
485
485
ChannelDeprecated is set if the requested channel is marked deprecated in the catalog.
0 commit comments