self-node-remediation
self-node-remediation copied to clipboard
medik8s
Automate community bundle via GitHub Actions
Why we need this PR:
Currently, the GitHub Action workflow is only able to create a RH/OKD bundle, while SNR is also supported in K8S community.
Moreover, the need of inputs like previous version does not allow to keep using the automatic CI for the release.
Changes made
Create a manual workflow to provide the necessary inputs to the shared GitHub Action to:
- build and push versioned images to quay registry
- create the OKD release branch, ready for the PR
- create the K8S release branch, ready for the PR
Which issue(s) this PR fixes
It contributes to solving ECOPROJECT-1579
Test plan
Tested locally via nektos/act.
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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: clobrano
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [clobrano]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/hold
I realized only now that we could just put the same workflow under the .github special repository and make it available for all operatores at once. I need to try
Unfortunately it is not possible. Each repository has to at least call the reusable workflow from its own action
/unhold
/hold it seems that conditional workflow isn't working too well, need to investigate
/hold Waiting for https://github.com/medik8s/node-healthcheck-operator/pull/300
This change does not affect the code and so the E2E tests are not necessary
@clobrano: Overrode contexts on behalf of clobrano: ci/prow/4.12-openshift-e2e
In response to this:
/override "ci/prow/4.12-openshift-e2e"
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.
@clobrano: Overrode contexts on behalf of clobrano: ci/prow/4.13-openshift-e2e
In response to this:
/override "ci/prow/4.13-openshift-e2e"
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.
@clobrano: Overrode contexts on behalf of clobrano: ci/prow/4.14-openshift-e2e
In response to this:
/override "ci/prow/4.14-openshift-e2e"
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.
@clobrano: Overrode contexts on behalf of clobrano: ci/prow/4.15-openshift-e2e
In response to this:
/override "ci/prow/4.15-openshift-e2e"
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.
@clobrano: Overrode contexts on behalf of clobrano: ci/prow/4.16-openshift-e2e
In response to this:
/override "ci/prow/4.16-openshift-e2e"
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.