Skip to content

📖 [Docs] How-to: Version Range Automatic Updates #1218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 5, 2024
Merged

📖 [Docs] How-to: Version Range Automatic Updates #1218

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions docs/drafts/how-to-version-range-upgrades.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
## How-to: Version Range Automatic Updates

Set the version for the desired package in the Catalog source to a comparison string, like `">=3.0, <3.6"`, to restrict the automatic updates to the version range. Any new version of the extension released in the catalog within this range will be automatically applied.

Example:

```yaml
apiVersion: olm.operatorframework.io/v1alpha1
kind: ClusterExtension
metadata:
name: argocd
spec:
installNamespace: argocd
source:
sourceType: Catalog
catalog:
packageName: argocd-operator
version: ">=3.0, <3.6" # Install versions from v3.0.0 up to, but not including, v3.6.0
serviceAccount:
name: argocd-installer
```

For more information on SemVer version ranges see [version-rages](version-ranges.md)
Loading