mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-02-07 20:40:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
2b47ab2c7a4bec8c2926e6b23dc118ed98523708
velero/site/content/docs/main/plugin-release-instructions.md
Nolan Brubaker 2b47ab2c7a Add initial instructions for releasing plugins (#2952) 
* Add initial instructions for releasing plugins

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Document that goreleaser isn't needed

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Add link from core release instructions to plugins

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Add notes about updating compatibility matrix

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Add velero install note

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Address review feedback

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>

* Remove anchor link to table, since it didn't work

Signed-off-by: Nolan Brubaker <brubakern@vmware.com>
2020-10-13 16:18:05 -07:00

1023 B
Raw Blame History

title, layout, toc
title layout toc
Releasing Velero plugins docs true

Velero plugins maintained by the core maintainers do not have any shipped binaries, only container images, so there is no need to invoke a GoReleaser script. Container images are built via a CI job on git push.

Plugins the Velero core team is responsible include all those listed in the Velero-supported providers list except the vSphere plugin.

  1. Update the README.md file to update the compatibility matrix and velero install instructions with the expected version number and open a PR.
  2. Determining the version number is based on semantic versioning and whether the plugin uses any newly introduced, changed, or removed methods or variables from Velero.
  3. Once the updated README.md PR is merged, checkout the upstream main branch. git checkout upstream/main.
  4. Tag the git version - git tag v<version>.
  5. Push the git tag - git push --tags <upstream remote name>
  6. Wait for the container images to build