doc/openstack: add a note about image registry in AZ #4833
Conversation
|
/label platform/openstack |
There was a problem hiding this comment.
@maxwelldb, FYI, a small note stating that cinder can be a better choice for the image-registry in certain situations (mostly for edge deployments).
@EricArrakis this could actually be one of this few cases where it is beneficial for the installer that it is deploying at the edge. That being said, I still think we do not (yet) want to bake that logic in the installer.
Add a note that if we deploy a cluster in an OpenStack AZ, it's suggested to use Cinder backend if the service is available in this AZ, since Cinder is topology aware. Swift isn't deployed in AZs usually, so traffic would have to go through the link between sites, which isn't optimal in real world. Signed-off-by: Emilien Macchi <emilien@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/bugzilla refresh |
|
@mandre: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@mandre 4.8+ or all supported versions? Additionally, is there BZ for this? |
That would be 4.8+ since it assumes support for cinder AZs.
Sorry, there's not. We should have created one. |
|
@mandre TY. And to be clear, since I see "it is recommended" in this PR, is the content in this note still fully supported according to QE? |
No, to my understanding we're not going to support a deployment in an AZ using swift for the image registry when swift isn't available in the same AZ. |
Add a note that if we deploy a cluster in an OpenStack AZ, it's
suggested to use Cinder backend if the service is available in this AZ,
since Cinder is topology aware.
Swift isn't deployed in AZs usually, so traffic would have to go
through the link between sites, which isn't optimal in real world.