Skip to content

Commit

Permalink
Updates GC link broken (#752)
Browse files Browse the repository at this point in the history
Co-authored-by: Steven Smith <stevsmit@stevsmit.remote.csb>
  • Loading branch information
stevsmit and Steven Smith authored Aug 14, 2023
1 parent a4048a6 commit 84bf929
Showing 1 changed file with 4 additions and 7 deletions.
11 changes: 4 additions & 7 deletions modules/rn_3_90.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ With this release, individual blob sizes are summed at the repository and namesp
+
[NOTE]
====
Because subtraction occurs from the total when the manifest is garbage collected, there is a delay in the size calculation until it is able to be garbage collected. For more information about {productname} garbage collection, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/manage_red_hat_quay/index#red_hat_quay_garbage_collection[{productname} garbage collection].
Because subtraction occurs from the total when the manifest is garbage collected, there is a delay in the size calculation until it is able to be garbage collected. For more information about {productname} garbage collection, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/manage_red_hat_quay/index#garbage-collection[{productname} garbage collection].
====
+
Additionally, manifest list totals are now counted toward the repository total, the total quota consumed when upgrading from a previous version of {productname} might be reportedly differently in {productname} 3.9. In some cases, the new total might go over a repository's previously-set limit. {productname} administrators might have to adjust the allotted quota of a repository to account for these changes.
Expand Down Expand Up @@ -116,7 +116,7 @@ With this release, if your database is managed by the {productname} Operator, up
Users with a managed database will be required to upgrade their PostgreSQL database from 10 -> 13.
====
+
If you do not want the {productname} Operator to upgrade your PostgreSQL deployment from 10 -> 13, you must set the PostgreSQL parameter to `managed: false` in your `quayregistry.yaml` file. For more information about setting your database to unmanaged, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/configure_red_hat_quay/index#operator-unmanaged-postgres[Using an existing Postgres database].
If you do not want the {productname} Operator to upgrade your PostgreSQL deployment from 10 -> 13, you must set the PostgreSQL parameter to `managed: false` in your `quayregistry.yaml` file. For more information about setting your database to unmanaged, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#operator-unmanaged-postgres[Using an existing Postgres database].
+
[IMPORTANT]
====
Expand All @@ -125,7 +125,7 @@ If you do not want the {productname} Operator to upgrade your PostgreSQL deploym
+
If you want your PostgreSQL database to match the same version as your {rhel} system, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/using-databases#migrating-to-a-rhel-8-version-of-postgresql_using-postgresql[Migrating to a RHEL 8 version of PostgreSQL] for {rhel-short} 8 or link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_using_database_servers/using-postgresql_configuring-and-using-database-servers#migrating-to-a-rhel-9-version-of-postgresql_using-postgresql[Migrating to a RHEL 9 version of PostgreSQL] for {rhel-short} 9.

For more information about the {productname} 3.8 -> 3.9 procedure, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/upgrade_red_hat_quay/index#operator-upgrade[Upgrading the {productname} Operator overview]
For more information about the {productname} 3.8 -> 3.9 procedure, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/upgrade_red_hat_quay/index#operator-upgrade[Upgrading the {productname} Operator overview].


[id="known-issues-and-limitations-39"]
Expand Down Expand Up @@ -167,9 +167,6 @@ This is a non-issue for proxy organizations employing a soft quota check and can

* When removing a site from your geo-replicated {productname} deployment, you might receive the following error when running `python -m util.removelocation`: `/app/lib/python3.9/site-packages/tzlocal/unix.py:141: SyntaxWarning: "is not" with a literal. Did you mean "!="? while start is not 0: /app/lib/python3.9/site-packages/netaddr/strategy/{}init{}.py:189: SyntaxWarning: "is not" with a literal. Did you mean "!="? if word_sep is not ''`. You can confirm the deletion of your site by entering `y`. The error is a known issue and will be removed in a future version of {productname}.




[id="limitations-39"]
=== {productname} 3.9 limitations

Expand Down Expand Up @@ -220,7 +217,7 @@ Some features available in previous releases have been deprecated or removed. De
|-
|-

|link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/manage_red_hat_quay/index#proc_manage-log-storage-splunk[Splunk log forwarding]
|link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.9/html-single/manage_red_hat_quay/index#proc_manage-log-storage-splunk[[Splunk log forwarding]
|General Availability
|-
|-
Expand Down

0 comments on commit 84bf929

Please sign in to comment.