-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have release artifacts available for BMO #2089
Comments
This issue is currently awaiting triage. 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. |
@kashifest @adilGhaffarDev as discussed offline. |
#1722 more or less a duplicate. Which one to close discussed there. |
On principle I would close the new and just add your issue description as a comment to the old one. |
/close |
@tuminoid: Closing this issue. In response to this:
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. |
We currently don't have any release artifacts for BMO. Following CAPM3 and IPAM, we should have some manifests available, where we can set the tags etc. Committing them to repo like this suggestion is not right. Checking k8s, CAPI, CAPM3 etc the template is unchanged, but release artifacts are corrected.
We should decide what are the release artifacts for BMO, and add them to the releasing automation.
The text was updated successfully, but these errors were encountered: