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
Copy file name to clipboardExpand all lines: DEV_GUIDE.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -437,9 +437,10 @@ To enable the docker workflow, you need to configure three repository [variables
437
437
and one repository [secret](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions).
438
438
439
439
*`REGISTRY_SERVER` variable - the server of the container registry service e.g. `quay.io` or `docker.io`
440
+
*`REGISTRY_ORGANISATION` variable - the organization of the container registry service e.g. `kroxylicious` or `yourusername`
441
+
*`PROXY_IMAGE_NAME` variable - the image name e.g. `kroxylicious`
442
+
*`OPERATOR_IMAGE_NAME` variable - the image name e.g. `operator`
440
443
*`REGISTRY_USERNAME` variable - your username on the service (or username of your robot account)
441
-
*`REGISTRY_DESTINATION` variable - the push destination (without tag portion) e.g. `quay.io/<my org>/kroxylicious`
442
-
443
444
*`REGISTRY_TOKEN` secret - the access token that corresponds to `REGISTRY_USERNAME`
444
445
445
446
The workflow will push the container image to `${REGISTRY_DESTINATION}` so ensure that the `${REGISTRY_USERNAME}` user has sufficient write privileges.
0 commit comments