Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
docs: additional release note updates based on v1.0.0-rc.1
  • Loading branch information
tam7t committed Oct 6, 2021
1 parent d616ad5 commit a08861e
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/e2e.yaml
Expand Up @@ -17,7 +17,7 @@ on:
imageVersion:
description: 'image version for Secret Store CSI driver and CRDs'
required: true
default: 'v0.3.0'
default: 'v1.CHANGE_ME'
jobs:
e2e-test:
runs-on: ubuntu-20.04
Expand Down
7 changes: 6 additions & 1 deletion docs/RELEASE.md
Expand Up @@ -27,7 +27,7 @@ NOTE: On OSX you must have the gnu version of `sed` in your path: `brew install
1. Make sure that the `docs` include all necessary information included in the release (example [tag compare](https://github.com/kubernetes-sigs/secrets-store-csi-driver/compare/v0.3.0...main)).
1. Create a new release branch `release-X.X` using the UI (to avoid `git push`'ing directly to the repo).
1. Wait for the [new branch](https://github.com/kubernetes-sigs/secrets-store-csi-driver/branches) to receive [branch protection](https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches).
1. Update the version to the semantic version of the new release similar to [this](https://github.com/kubernetes-sigs/secrets-store-csi-driver/pull/251)
1. Update the version to the semantic version of the new release (`Makefile` and `docker/Makefile`) similar to [this](https://github.com/kubernetes-sigs/secrets-store-csi-driver/pull/767)
1. Commit the changes and push to remote repository to create a pull request to the `release-X.X` branch

```bash
Expand All @@ -38,6 +38,11 @@ NOTE: On OSX you must have the gnu version of `sed` in your path: `brew install

1. Once the PR is merged to `release-X.X`, the [prow job](https://testgrid.k8s.io/sig-auth-secrets-store-csi-driver#secrets-store-csi-driver-push-image) is triggered to build and push the new version to staging repo (`gcr.io/k8s-staging-csi-secrets-store/driver`)
1. After images are available in staging registry, head over to github [actions](https://github.com/kubernetes-sigs/secrets-store-csi-driver/actions) and select `e2e_mock_provider_tests` workflow. Click `Run workflow` and provide required inputs. This will run e2e tests against the staging images. Make sure this job is successful before proceeding to the next step.

```bash
gh workflow run e2e_mock_provider_tests -f imageVersion=<NEW_VERSION>
```

1. Once the e2e tests on staging images completes, follow the [instructions](https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io#image-promoter) to promote the image to production repo
- Within the Prow job "Artifacts" tab there is a file `artifacts/build.log` which will include the Cloud Build URL:

Expand Down

0 comments on commit a08861e

Please sign in to comment.