k8snetworkplumbingwg / plugins Goto Github PK

currently release workflow (image push release) acts on manual trigger or tag push.
however it only properly works with manual trigger as image tag value is taken from user input.

publishing a release requires a tag so once the tag is pushed it will trigger release workflow and fail because of issue described above.

release process should be well defined and workflow should be adjusted.

A few options that we can take:

1. in containernetworking/cni , add a workflow in their release process to publish container image
2. have a daily that syncs this repo master branch with containernetworking/cni which pushes changes to master with tags, adjust workflow to properly work with either "workflow_dispatch" or tag trigger
3. remove requirement for tag from workflow, then have a daily job that will trigger workflow if a new release in containernetworking/cni.
   if we want to also do a release, then we need to tag something (release branch in this case ?)