You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Note: cannot use env variables to set go-version (https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations)
38
55
go-version: '1.24'
39
56
platforms: linux/amd64,linux/arm64
@@ -46,14 +63,15 @@ jobs:
46
63
controller-image-provenance:
47
64
needs:
48
65
- controller-image
66
+
- set-registry-namespace
49
67
permissions:
50
68
actions: read # for detecting the Github Actions environment.
51
69
id-token: write # for creating OIDC tokens for signing.
52
70
packages: write # for uploading attestations. (https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/container/README.md#known-issues)
53
71
# Must be refernced by a tag. https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/container/README.md#referencing-the-slsa-generator
actions: read # for detecting the Github Actions environment.
67
86
id-token: write # for creating OIDC tokens for signing.
68
87
packages: write # for uploading attestations. (https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/container/README.md#known-issues)
69
88
# Must be refernced by a tag. https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/container/README.md#referencing-the-slsa-generator
Copy file name to clipboardExpand all lines: docs/releasing.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,21 @@ execution. You can follow its progress under the [Actions](https://github.com/ar
68
68
brew upgrade kubectl-argo-rollouts
69
69
kubectl argo rollouts version
70
70
```
71
+
72
+
### Releasing from your own fork of Argo Rollouts
73
+
74
+
It is also possible to release from your own personal/company fork. This is useful if your organization keeps [a second copy of Argo Rollouts](https://github.com/argoproj/argo-rollouts/blob/master/docs/proposals/parameterized-build-system.md) for hot-fixes or security updates.
75
+
76
+
1. Sign-up for a RedHat account so that you get acess to [Quay Registry](http://quay.io)
77
+
2. Login and create two repositories called `argo-rollouts` and `kubectl-argo-rollouts` (for the CLI)
78
+
3. Under "Account settings" create a "Robot account"for CI automation with any name you want. A token will be generated for you
79
+
80
+
Then enter your GitHub account in your own forked repo and under Settings ->"Secrets and Variables" -> actions:
81
+
82
+
* Add `QUAY_USERNAME` and `QUAY_ROBOT_TOKEN` as "Repository Secrets" with the values you created from the previous step
83
+
* Add `REGISTRY_NAMESPACE` with your own Quay username/organization as "Repository variables"
84
+
85
+
Now follow any of the instructions from the previous section and you will see released images in your own Quay repository.
86
+
87
+
!!! tip
88
+
The `trigger-release.sh` does some basic checks for the name of the tag. If you want to release with a tag that doesn't follow the expected naming convention you can skip this script and just push a tag on your own directly to GitHub.
0 commit comments