Skip to content

Conversation

@sairameshv
Copy link
Member

@sairameshv sairameshv commented Jan 16, 2026

Reference doc for the future releases of DAS operator via Konflux
Generated by Claude

/cc @kannon92 @cpmeadors

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 16, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 16, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sairameshv

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 16, 2026
@sairameshv sairameshv force-pushed the konflux_release_readme branch from a567571 to a11a759 Compare January 19, 2026 13:59
@sairameshv
Copy link
Member Author

This doc also requires further changes that are to be done to the instaslice-fbc repository and hence keeping the PR still in draft state.

@sairameshv sairameshv force-pushed the konflux_release_readme branch from a11a759 to c5447dc Compare January 19, 2026 16:34
@openshift-ci openshift-ci bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 19, 2026
@sairameshv sairameshv marked this pull request as ready for review January 19, 2026 17:36
@sairameshv sairameshv changed the title WIP: Add a reference konflux release doc OCPNODE-4041: Add a reference konflux release doc Jan 19, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 19, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@sairameshv: This pull request references OCPNODE-4041 which is a valid jira issue.

Details

In response to this:

Generated by Claude

/cc @kannon92 @cpmeadors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 19, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 19, 2026

@sairameshv: This pull request references OCPNODE-4041 which is a valid jira issue.

Details

In response to this:

Reference doc for the future releases of DAS operator via Konflux
Generated by Claude

/cc @kannon92 @cpmeadors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.


The InstaSlice operator uses File-Based Catalog (FBC) releases for different OCP versions. Each new OCP version requires changes in **two separate repositories**:

### Part A: konflux-release-data Repository
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like you should either mention that the new applications you want to release have already been created or add steps here on how to do that. For example you need to create the new dynamicacceleratorslicer-fbc-4-20 application and get everything building.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put Part B first and include the steps to create the new application at the end of that, then Part A comes. This is a more logical flow.

- Access to the konflux-release-data repository
- Access to the instaslice-fbc repository

### Environment Setup
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like it will get stale really quick.

We should just link to this repo and provide good onboarding docs there.

@cpmeadors
Copy link
Contributor

I would expect some reference links back to the Konflux docs. They are useful to understand the process, but don't have the best examples. We also have done this work before so they are example PRs in the repos for much of this work. I think more links to the official docs and specific examples would make this doc more maintainable and more useful.

Signed-off-by: Sai Ramesh Vanka <svanka@redhat.com>
@sairameshv sairameshv force-pushed the konflux_release_readme branch from c5447dc to 0ead51a Compare January 22, 2026 14:11
@sairameshv
Copy link
Member Author

I would expect some reference links back to the Konflux docs. They are useful to understand the process, but don't have the best examples. We also have done this work before so they are example PRs in the repos for much of this work. I think more links to the official docs and specific examples would make this doc more maintainable and more useful.

@cpmeadors , Could you help quoting some of the example PRs that you worked for the earlier release on the instaslice-fbc repo and any if required? I would be adding them along with the konflux docs

@sairameshv
Copy link
Member Author

/override ci/prow/e2e-bundle-4.20-runc

@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

@sairameshv: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/e2e-bundle-4.20-runc

Only the following failed contexts/checkruns were expected:

  • ci/prow/ci-index-das-operator-bundle
  • ci/prow/e2e-bundle-4-19-runc
  • ci/prow/e2e-bundle-4-20-runc
  • ci/prow/e2e-bundle-runc
  • ci/prow/images
  • ci/prow/lint
  • ci/prow/unit
  • pull-ci-openshift-instaslice-operator-next-ci-index-das-operator-bundle
  • pull-ci-openshift-instaslice-operator-next-e2e-bundle-4-19-runc
  • pull-ci-openshift-instaslice-operator-next-e2e-bundle-4-20-runc
  • pull-ci-openshift-instaslice-operator-next-e2e-bundle-runc
  • pull-ci-openshift-instaslice-operator-next-images
  • pull-ci-openshift-instaslice-operator-next-unit
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override ci/prow/e2e-bundle-4.20-runc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Signed-off-by: Sai Ramesh Vanka <svanka@redhat.com>
@sairameshv
Copy link
Member Author

/override ci/prow/e2e-bundle-4-19-runc
/override ci/prow/e2e-bundle-4-20-runc
/override ci/prow/e2e-bundle-runc

@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2026

@sairameshv: Overrode contexts on behalf of sairameshv: ci/prow/e2e-bundle-4-19-runc, ci/prow/e2e-bundle-4-20-runc, ci/prow/e2e-bundle-runc

Details

In response to this:

/override ci/prow/e2e-bundle-4-19-runc
/override ci/prow/e2e-bundle-4-20-runc
/override ci/prow/e2e-bundle-runc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2026

@sairameshv: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants