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/v1/clusterextension_types.go
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -485,10 +485,13 @@ type ClusterExtensionStatus struct {
485
485
//
486
486
// When the ClusterExtension is sourced from a catalog, it may surface deprecation conditions based on catalog metadata.
487
487
// These are indications from a package owner to guide users away from a particular package, channel, or bundle.
488
-
// PackageDeprecated becomes True when the catalog marks the requested package deprecated; otherwise it stays False.
489
-
// ChannelDeprecated becomes True when any requested channel is marked deprecated; otherwise it stays False.
490
-
// BundleDeprecated reports the catalog status of the installed bundle: it remains Unknown until a bundle installs, then becomes True or False depending on whether the catalog marks that bundle deprecated.
491
-
// Deprecated is a rollup that mirrors True whenever any of the specific deprecation conditions are True.
488
+
// PackageDeprecated reports the requested package as deprecated when the catalog says so. When no catalog talks
489
+
// about the package, the condition stays Unknown instead of claiming False.
490
+
// ChannelDeprecated follows the same rules for each requested channel.
491
+
// BundleDeprecated describes the installed bundle once one exists. Until a bundle installs, or when no catalog
492
+
// data is available, it remains Unknown.
493
+
// Deprecated is still the rollup: it goes True when any individual deprecation condition is True, and Unknown
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, it may surface deprecation conditions based on catalog metadata.<br />These are indications from a package owner to guide users away from a particular package, channel, or bundle.<br />PackageDeprecated becomes True when the catalog marks the requested package deprecated; otherwise it stays False.<br />ChannelDeprecated becomes True when any requested channel is marked deprecated; otherwise it stays False.<br />BundleDeprecated reports the catalog status of the installed bundle: it remains Unknown until a bundle installs, then becomes True or False depending on whether the catalog marks that bundle deprecated.<br />Deprecated is a rollup that mirrors True whenever any of the specific deprecation conditions are True. | | |
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, it may surface deprecation conditions based on catalog metadata.<br />These are indications from a package owner to guide users away from a particular package, channel, or bundle.<br />PackageDeprecated reports the requested package as deprecated when the catalog says so. When no catalog talks<br />about the package, the condition stays Unknown instead of claiming False.<br />ChannelDeprecated follows the same rules for each requested channel.<br />BundleDeprecated describes the installed bundle once one exists. Until a bundle installs, or when no catalog<br />data is available, it remains Unknown.<br />Deprecated is still the rollup: it goes True when any individual deprecation condition is True, and Unknown<br />when we have no catalog information to report. | | |
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_clusterextensions.yaml
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -520,10 +520,13 @@ spec:
520
520
521
521
When the ClusterExtension is sourced from a catalog, it may surface deprecation conditions based on catalog metadata.
522
522
These are indications from a package owner to guide users away from a particular package, channel, or bundle.
523
-
PackageDeprecated becomes True when the catalog marks the requested package deprecated; otherwise it stays False.
524
-
ChannelDeprecated becomes True when any requested channel is marked deprecated; otherwise it stays False.
525
-
BundleDeprecated reports the catalog status of the installed bundle: it remains Unknown until a bundle installs, then becomes True or False depending on whether the catalog marks that bundle deprecated.
526
-
Deprecated is a rollup that mirrors True whenever any of the specific deprecation conditions are True.
523
+
PackageDeprecated reports the requested package as deprecated when the catalog says so. When no catalog talks
524
+
about the package, the condition stays Unknown instead of claiming False.
525
+
ChannelDeprecated follows the same rules for each requested channel.
526
+
BundleDeprecated describes the installed bundle once one exists. Until a bundle installs, or when no catalog
527
+
data is available, it remains Unknown.
528
+
Deprecated is still the rollup: it goes True when any individual deprecation condition is True, and Unknown
529
+
when we have no catalog information to report.
527
530
items:
528
531
description: Condition contains details for one aspect of the current
Copy file name to clipboardExpand all lines: helm/olmv1/base/operator-controller/crd/standard/olm.operatorframework.io_clusterextensions.yaml
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -481,10 +481,13 @@ spec:
481
481
482
482
When the ClusterExtension is sourced from a catalog, it may surface deprecation conditions based on catalog metadata.
483
483
These are indications from a package owner to guide users away from a particular package, channel, or bundle.
484
-
PackageDeprecated becomes True when the catalog marks the requested package deprecated; otherwise it stays False.
485
-
ChannelDeprecated becomes True when any requested channel is marked deprecated; otherwise it stays False.
486
-
BundleDeprecated reports the catalog status of the installed bundle: it remains Unknown until a bundle installs, then becomes True or False depending on whether the catalog marks that bundle deprecated.
487
-
Deprecated is a rollup that mirrors True whenever any of the specific deprecation conditions are True.
484
+
PackageDeprecated reports the requested package as deprecated when the catalog says so. When no catalog talks
485
+
about the package, the condition stays Unknown instead of claiming False.
486
+
ChannelDeprecated follows the same rules for each requested channel.
487
+
BundleDeprecated describes the installed bundle once one exists. Until a bundle installs, or when no catalog
488
+
data is available, it remains Unknown.
489
+
Deprecated is still the rollup: it goes True when any individual deprecation condition is True, and Unknown
490
+
when we have no catalog information to report.
488
491
items:
489
492
description: Condition contains details for one aspect of the current
name: "deprecated channel specified, deprecated bundle, all deprecation statuses set to true, all deprecation statuses set to true except PackageDeprecated",
0 commit comments