-
Notifications
You must be signed in to change notification settings - Fork 47
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.
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
📖 Docs for version range support #544
📖 Docs for version range support #544
Conversation
Add docs explaining version range. Signed-off-by: Michael Ryan Peter <mipeter@redhat.com>
docs/drafts/version-ranges.md
Outdated
Specifying a channel | ||
: Installs or updates the latest version of the Operator in the channel. | ||
Updates are applied automatically when they are published to the specified channel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would expect this doc to be purely about spec.version
, so I'd suggest striking this.
In a higher-level doc, I'd expect something that talks about the various spec
fields and their interactions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed.
docs/drafts/version-ranges.md
Outdated
The following list describes how OLM resolves an Operator's target version, and the resulting actions: | ||
|
||
Not specifying a version in the CR | ||
: Installs or updates the latest version of the Operator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
latest
Technically, it's the latest version that satisfies resolution. I think it's important to call that out pretty clearly somewhere, and possibly explain with an example.
For example:
In the catalog:
- packageA v1.0.0 exists and depends on packageB v1.2.0
- packageB v1.2.0 exists
- packageB v1.2.1 exists
On the cluster:
- Operator for
packageA
saysspec.version: 1.0.0
- Operator for
packageB
saysspec.version: 1.2.x
The version that will ultimately be chosen for packageB
is 1.2.0 even though 1.2.1 is available, because that's what packageA
requires.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the moment, I linked to Deppy's README to explain resolution. WDYT of creating a follow up issue to port the OCP docs about dependency resolution upstream?
fd0bc69
to
57270d7
Compare
| `<` | less than | | ||
| `>=` | greater than or equal to | | ||
| `<=` | less than or equal to | | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created #550 to add docs on working with pre-releases
- Remove references to the Mastermind SemVer docs - Define operators and comparisons - Address review feedback Signed-off-by: Michael Ryan Peter <mipeter@redhat.com>
eb455f6
to
a112f0f
Compare
|
||
You define a version range in an Operator's custom resource (CR) file. | ||
|
||
## Specifying a version range in the CR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the other sections on the spec.version
field. They didn't make sense with the expanded content, and I think it will take a bit more work to incorporate the content into one doc on the spec.version
field. I created a follow up issue here: #551
@@ -0,0 +1,93 @@ | |||
# Operator version ranges |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I created a follow up issue to add example CRs to the doc: #552
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doc looks great to me! I noticed one small thing:
docs/drafts/version-ranges.md
Outdated
|
||
| Operator | Definition | | ||
|----------|-----------------------------------| | ||
| `=` | equal (not aliased to an operator | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing a closing parenthesis
| `=` | equal (not aliased to an operator | | |
| `=` | equal (not aliased to an operator) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in 164bb28
docs/drafts/version-ranges.md
Outdated
|
||
#### Range comparisons | ||
|
||
OLM 1.0 does not support hypen range comparisons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OLM 1.0 does not support hypen range comparisons. | |
OLM 1.0 does not support hyphen range comparisons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to mention hyphen ranges at all? If we're not mentioning Masterminds, should we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in 164bb28
- Close parenthesis on line 11 - Remove mention of hyphen range comparisons Signed-off-by: Michael Ryan Peter <mipeter@redhat.com>
e2a521b
to
164bb28
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #544 +/- ##
==========================================
+ Coverage 78.59% 83.72% +5.13%
==========================================
Files 18 20 +2
Lines 766 811 +45
==========================================
+ Hits 602 679 +77
+ Misses 131 91 -40
- Partials 33 41 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Description
Add docs about version range support. Create a
drafts
docs folder. This folder is for docs that are drafts to iterate on and not published as part of the customer-facing docs.Closes #407.
Reviewer Checklist