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
. Start the `Quay` container in configuration mode and select the Enable Repository Mirroring check box. If you want to require HTTPS communications and verify certificates during mirroring, select the HTTPS and cert verification check box.
5
+
By default, `FEATURE_REPO_MIRROR` is set to `false`. To enable mirroring, you must set `FEATURE_REPO_MIRROR: true` in your `config.yaml` file.
6
+
7
+
.Procedure
8
+
9
+
. Set `FEATURE_REPO_MIRROR: true` in your `config.yaml` file. For example:
4
10
+
5
-
image:repo_mirror_config.png[Enable mirroring and require HTTPS and verified certificates]
11
+
[source,yaml]
12
+
----
13
+
# ...
14
+
FEATURE_REPO_MIRROR: true
15
+
# ...
16
+
----
6
17
7
-
. Validate and download the `configuration` file, and then restart Quay in registry mode using the updated config file.
Copy file name to clipboardExpand all lines: modules/mirroring-creating-repo.adoc
+28-27Lines changed: 28 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,7 @@
2
2
[id="mirroring-creating-repo"]
3
3
= Creating a mirrored repository
4
4
5
-
When mirroring a repository from an external container registry, you must create a new private repository. Typically, the same name is used as the target repository, for example, `quay-rhel8`.
6
-
7
-
image:repo_quay_rhel8.png[Create new {productname} repo]
5
+
When mirroring a repository from an external container registry, you must create a new private repository. Typically, the same name is used as the target repository, for example, `quay-rhel9`.
8
6
9
7
[id="mirroring-repository-mirroring-settings"]
10
8
== Repository mirroring settings
@@ -18,37 +16,42 @@ Use the following procedure to adjust the settings of your mirrored repository.
18
16
19
17
.Procedure
20
18
21
-
. In the Settings tab, set the Repository State to `Mirror`:
22
-
+
23
-
image:repo_mirror_create.png[Create a new {productname} repo mirror]
19
+
. Navigate to the *Repositories* page of your registry and click the name of a repository, for example, *test-mirror*.
24
20
25
-
. In the Mirror tab, enter the details for connecting to the external registry, along with the tags, scheduling and access information:
. Click the *Mirroring* tab and enter the details for connecting to the external registry, along with the tags, scheduling and access information:
28
26
29
27
. Enter the details as required in the following fields:
30
28
+
31
-
* **Registry Location:** The external repository you want to mirror, for example, `registry.redhat.io/quay/quay-rhel8`
32
-
* **Tags:** This field is required. You may enter a comma-separated list of individual tags or tag patterns. (See _Tag Patterns_ section for details.)
29
+
* **Registry Location:** The external repository you want to mirror, for example, `registry.redhat.io/quay/quay-rhel8`.
30
+
31
+
* **Tags:** Enter a comma-separated list of individual tags or tag patterns. (See _Tag Patterns_ section for details.)
33
32
34
33
* **Start Date:** The date on which mirroring begins. The current date and time is used by default.
34
+
35
35
* **Sync Interval:** Defaults to syncing every 24 hours. You can change that based on hours or days.
36
+
37
+
* **Skopeo timeout internal:** Defaults to `300` seconds (5 minutes). The maximum timeout length is `43200` seconds (12 hours).
38
+
36
39
* **Robot User:** Create a new robot account or choose an existing robot account to do the mirroring.
40
+
37
41
* **Username:** The username for accessing the external registry holding the repository you are mirroring.
42
+
38
43
* **Password:** The password associated with the Username. Note that the password
39
44
cannot include characters that require an escape character (\).
40
45
41
-
[id="mirroring-advanced-settings"]
42
-
== Advanced settings
43
-
44
-
In the *Advanced Settings* section, you can configure SSL/TLS and proxy with the following options:
45
-
46
+
. In the *Advanced Settings* section, you can optionally configure SSL/TLS and proxy with the following options:
47
+
+
46
48
* **Verify TLS:** Select this option if you want to require HTTPS and to verify certificates when communicating with the target remote registry.
47
49
* **Accept Unsigned Images:** Selecting this option allows unsigned images to be mirrored.
48
50
* **HTTP Proxy:** Select this option if you want to require HTTPS and to verify certificates when communicating with the target remote registry.
49
51
* **HTTPS PROXY:** Identify the HTTPS proxy server needed to access the remote site, if a proxy server is needed.
50
52
* **No Proxy:** List of locations that do not require proxy.
51
53
54
+
. After filling out all information, click *Enable Mirror*.
52
55
53
56
[id="mirroring-synchronize-now"]
54
57
== Synchronize now
@@ -57,14 +60,12 @@ Use the following procedure to initiate the mirroring operation.
57
60
58
61
.Procedure
59
62
60
-
* To perform an immediate mirroring operation, press the Sync Now button on the repository's Mirroring tab. The logs are available on the Usage Logs tab:
61
-
+
62
-
image:repo-mirror-usage-logs.png[Usage logs]
63
-
+
64
-
When the mirroring is complete, the images will appear in the Tags tab:
Copy file name to clipboardExpand all lines: modules/mirroring-working-with.adoc
+9-15Lines changed: 9 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,18 @@
1
-
[[mirroring-working-with]]
1
+
:_mod-docs-content-type: PROCEDURE
2
+
[id="mirroring-working-with"]
2
3
= Working with mirrored repositories
3
4
4
-
Once you have created a mirrored repository, there are several
5
-
ways you can work with that repository.
6
-
Select your mirrored repository from the Repositories page
7
-
and do any of the following:
5
+
After you have created a mirrored repository, there are several ways that you can work with that repository.
6
+
7
+
Select your mirrored repository from the *Repositories* page to do any of the following:
8
8
9
9
* **Enable/disable the repository**: Select the Mirroring button in the left column,
10
10
then toggle the Enabled check box to enable or disable the repository temporarily.
11
11
12
12
* **Check mirror logs**: To make sure the mirrored repository is working properly,
13
13
you can check the mirror logs. To do that, select the Usage Logs
14
14
button in the left column. Here's an example:
15
-
+
16
-
image:repo_mirror_logs.png[View logs for your {productname} repo mirror]
15
+
17
16
18
17
* **Sync mirror now**: To immediately sync the images in your repository,
19
18
select the Sync Now button.
@@ -28,22 +27,17 @@ new ones from being synced, select the CANCEL button.
28
27
for accessing external repositories. By assigning credentials to a robot, that robot can be used
29
28
across multiple mirrored repositories that need to access the same external registry.
30
29
+
31
-
You can assign an existing robot to a repository by going to Account Settings, then selecting
32
-
the Robot Accounts icon in the left column. For the robot account, choose the
33
-
link under the REPOSITORIES column. From the pop-up window, you can:
30
+
You can assign an existing robot to a repository by navigating to *Organizations*->*Robot accounts*. On this page, you can view the following information:
34
31
35
32
** Check which repositories are assigned to that robot.
36
33
37
-
** Assign read, write or Admin privileges to that robot from the PERMISSION field shown in this figure:
38
-
image:repo_mirror_robot_assign.png[Assign a robot to mirrored repo]
34
+
** Assign `Read`, `Write` or `Admin` privileges to that robot from the PERMISSION field.
39
35
40
36
* **Change robot credentials**: Robots can hold credentials such as
41
-
Kubernetes secrets, Docker login information, and Mesos bundles.
37
+
Kubernetes secrets, Docker login information, and Podman login information.
42
38
To change robot credentials, select
43
39
the Options gear on the robot's account line on the Robot Accounts window and choose View Credentials.
44
40
Add the appropriate credentials for the external repository the robot needs to access.
45
-
+
46
-
image:repo_mirror_robot_perm.png[Assign permission to a robot]
47
41
48
42
* **Check and change general setting**: Select the Settings button (gear icon) from the left
Copy file name to clipboardExpand all lines: modules/rn_3_15_0.adoc
+38-1Lines changed: 38 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,42 @@
1
+
:_content-type: CONCEPT
2
+
[id="release-notes-315"]
3
+
= {productname} release notes
4
+
5
+
The following sections detail _y_ and _z_ stream release information.
6
+
7
+
[id="rn-3-15-1"]
8
+
== RHBA-2025:7674 - {productname} 3.15.1 release
9
+
10
+
Issued 2025-08-14
11
+
12
+
{productname} release 3.15.1 is now available with Clair {clairproductminv}. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2025:13256[RHBA-2025:13256] advisory.
13
+
14
+
[id="bug-fixes-315-1-new-features"]
15
+
=== {productname} 3.15.1 new features
16
+
17
+
The following features have been added with {productname} 3.15.1.
18
+
19
+
[id="v2-ui-mirroring-tab"]
20
+
==== v2 UI mirroring tab
21
+
22
+
Previously, mirroring via the {productname} UI was only available when using the legacy UI. With this update, a *Mirroring* tab has been added to the {productname} v2 UI. This tab is available under the *Repositories* page of your registry.
23
+
24
+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html/manage_red_hat_quay/repo-mirroring-in-red-hat-quay[Repository mirroring].
25
+
26
+
[id="bug-fixes-315-1"]
27
+
=== {productname} 3.15.1 bug fixes
28
+
29
+
* link:https://issues.redhat.com/browse/PROJQUAY-9135[PROJQUAY-9135]. Before this update, Alembic migrations failed to install certificates during run, causing issues with {productname} behind HTTPS proxy due to lack of certificates. Consequently, users experienced migration failure when {productname} was behind an HTTPS proxy. With this release, Alembic migrations no longer require manual certificate installation for {productname} behind HTTPS proxy. As a result, Alembic migrations can now install certs, allowing smooth operation behind HTTPS proxies.
30
+
31
+
* link:https://issues.redhat.com/browse/PROJQUAY-9156[PROJQUAY-9156]. Previously, some `read-only` permissions were missing for `read-only` superusers. This issue has been resolved.
32
+
33
+
* link:https://issues.redhat.com/browse/PROJQUAY-9106[PROJQUAY-9106]. Previously, a bad proxy cache reference occurred due to an oversight. Consequently, users experienced stale cache data. With this release, the proxy cache reference issue is resolved, ensuring smoother performance for end users.
34
+
35
+
* link:https://issues.redhat.com/browse/PROJQUAY-9059[PROJQUAY-9059]. With this release, model card rendering is now enabled on the v2 UI by default. You no longer need to set the `FEATURE_UI_MODELCARD` field to `true`.
0 commit comments