ROX-325150: Use Kubearchive for getting snapshots for the release #304
+20
−14
Conversation
This file contains hidden or 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
tommartensen
requested changes
Jan 20, 2026
scripts/generate-releases.sh
Outdated
| snapshot_copy_name="$(echo "${snapshot%-*}-${release_name_suffix}" | cut -c -63)" # Replace random suffix with release name and crop to 63 characters to avoid running over the Kubernetes limit. | ||
| echo "---" | ||
| kubectl -n rh-acs-tenant get snapshot.appstudio.redhat.com "${snapshot}" -o yaml | \ | ||
| kubectl ka -n rh-acs-tenant get snapshot.appstudio.redhat.com "${snapshot}" -o yaml | \ |
Contributor
There was a problem hiding this comment.
I tried to generate releases on the 0d6c22807f4629bf5aa5a065c7607bace38b7458 (current HEAD of the PR branch) and got an empty yaml:
./scripts/generate-releases.sh stage
---
apiVersion: null
kind: null
metadata:
labels: null
name: acs-operator-index-ocp-v4-12-20260120-stage-0d6c228
namespace: null
spec: nullI believe this is because this command will also return a list (with exactly one entry).
I am on this version:
$ kubectl ka version
kubectl-archive version v1.16.0
Build date: 2025-12-15T10:55:03Z
Git commit: 2032dac903c738150efa554158d642afecb6d22c
Member
Author
There was a problem hiding this comment.
Thanks for spotting this. There was a bug indeed and kubearchive has a different format when fetching snapshots as YAML. It's fixed and I added testing release to the PR description
Co-authored-by: Tom Martensen <tmartens@redhat.com>
kurlov
commented
Jan 21, 2026
kurlov
commented
Jan 21, 2026
tommartensen
requested changes
Jan 21, 2026
Contributor
tommartensen
left a comment
tommartensen
left a comment
There was a problem hiding this comment.
a nit and a discussion
Co-authored-by: Tom Martensen <tmartens@redhat.com>
…-release' of https://github.com/stackrox/operator-index into akurlov/ROX-325150-use-kubearchive-to-get-snapshots-for-release
|
/retest operator-index-ocp-v4-20-on-push |
tommartensen
approved these changes
Jan 21, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately snapshots might be getting deleted really fast on Konflux (in 1 hour or even faster). But the release process requires those snapshots. So it is more robust to rely on kubearchive to fetch snapshots instead.
Tested:
And the output: