-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Jonathan Berkhahn <[email protected]> Signed-off-by: Jonathan Berkhahn <[email protected]>
- Loading branch information
Showing
28 changed files
with
95 additions
and
161 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
## v1.24.0 | ||
|
||
### Changes | ||
|
||
- Bumping java-operator-plugins to v0.6.0. ([#6007](https://github.com/operator-framework/operator-sdk/pull/6007)) | ||
|
||
### Bug Fixes | ||
|
||
- Support test selectors in scorecard-kuttl. This only works if you supply a test name in the config for the entrypoint in the scorecard test config.yaml | ||
In the `stages.tests`section add an `entrypoint`, in this entrypoint you add the name of the test you want to associate with the selector. | ||
If you have a kuttl test directory called `smoke` your entrypoint should have `- smoke` as an entry. That way scorecard can pass that into the image and kuttl will run the single test. ([#6015](https://github.com/operator-framework/operator-sdk/pull/6015)) | ||
- `operator-sdk run bundle(-upgrade)`: fixed bug that made it so bundles weren't properly upgraded if the channel used in the bundle wasn't in the same channel as the bundle installed via `operator-sdk run bundle`. Using `operator-sdk run bundle` will now use a default channel instead of the one in the bundle. ([#6042](https://github.com/operator-framework/operator-sdk/pull/6042)) | ||
- `operator-sdk run bundle(-upgrade)`: fixed bug causing `operator-sdk run bundle-upgrade` and `operator-sdk run bundle ... --index-image=...` to stall indefinitely. ([#6040](https://github.com/operator-framework/operator-sdk/pull/6040)) | ||
- For Ansible & Helm-based operators, the generated `Makefile` does not handle converting `aarch64` to `arm64`. This prevents it from downloading the appropriate binaries. | ||
This change simply adds a call to `sed` to convert `aarch64` to `arm64`. ([#5480](https://github.com/operator-framework/operator-sdk/pull/5480)) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.