build release version container images and update deployment manifests

[rootfs]

Is your feature request related to a problem? Please describe. Current the kepler container image is built on main branch and the tag is latest. The tag is used in kepler deployment manifests

Describe the solution you'd like In the release branch (e.g. branch name is release-x.x), the CI should build the image and use the release tag, update the manifests once the image is pushed.

Describe alternatives you've considered This can be done manually but CI is better suited for this purpose.

Additional context Add any other context or screenshots about the feature request here.

[rootfs]

@sustainable-computing-io/kepler-deployment

[husky-parul]

@rootfs Should we update the manifest each time or just point latest to the latest release in image repository?

[rootfs]

we can use bot to update the manifest once a release image is built

[jichenjc]

I think this can also be integrated with github actions @SamYuan1990 @rootfs e.g every time a new release come out we cut the branch and let github actions tag and build image then upload

this might be FYI as we did it every k8s release https://github.com/kubernetes/cloud-provider-openstack/blob/master/release-procedure.md

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.