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
The "e2e run" target also creates all the repositories for the user, and
then they only have to make them public. Adding a note as an alternative
to manage those repositories in case the user wants to follow that path
instead.
Copy file name to clipboardExpand all lines: quay.adoc
+23-15Lines changed: 23 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,30 @@
1
1
== Configure your Quay account for dev deployment
2
2
3
-
There is a set of images that is built and pushed to quay repositories while deploying local versions of Toolchain (Sandbox) operators to OpenShift cluster. Please make sure that the repositories exist in your quay.io account.
3
+
There is a set of images that is built and pushed to quay repositories while deploying local versions of Toolchain
4
+
(Sandbox) operators to OpenShift cluster. Please make sure that the repositories exist in your Quay.io account.
4
5
5
6
=== Repositories
6
-
. Register for a quay.io account if you don't have one
7
-
. Make sure you have set the _QUAY_NAMESPACE_ variable: +
8
-
`export QUAY_NAMESPACE=<quay-username>`
9
-
. Log in to quay.io using +
10
-
`podman login quay.io`
11
-
* Make sure that these repositories exist on quay.io and the visibility is set to `public` for all of them:
0 commit comments