Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation updated for IBM Power and IBM Z #1141

Merged
merged 1 commit into from
Oct 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions modules/georepl-intro.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,6 @@
[id="georepl-intro"]
= Geo-replication

[NOTE]
====
Currently, the geo-replication feature is not supported on IBM Power.
====

Geo-replication allows multiple, geographically distributed {productname} deployments to work as a single registry from the perspective of a client or user. It significantly improves push and pull performance in a globally-distributed {productname} setup. Image data is asynchronously replicated in the background with transparent failover and redirect for clients.

Deployments of {productname} with geo-replication is supported on standalone and Operator deployments.
6 changes: 3 additions & 3 deletions modules/rn_3_13_0.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -316,7 +316,7 @@ Some features available in previous releases have been deprecated or removed. De
|Supported

|Geo-Replication (Operator)
|Not Supported
|Supported
|Not Supported

|IPv6
Expand All @@ -328,8 +328,8 @@ Some features available in previous releases have been deprecated or removed. De
|Supported

|Mirror registry
|Not Supported
|Not Supported
|Supported
|Supported

|PostgreSQL connection pooling via pgBouncer
|Supported
Expand Down