-
Notifications
You must be signed in to change notification settings - Fork 1.9k
BZ1850510 - remove NFS from image reg docs #25826
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
Conversation
|
The preview will be available shortly at: |
ba494bd to
704a2e1
Compare
|
@huffmanca PTAL, thank you! |
|
@qinpingli PTAL for QE, especially in the PV/PVC examples that were updated, thanks! |
|
All in all, Image registry support both RWX and RWO pvc, no matter the PVC is using what kind of storage backend. For RWX pvc, Image registry is hardcoded to use RWX+100Gi PVC which can be auto-created if user configure config.imageregistry to spec.pvc.claim(leave the name blank); For RWO pvc which is usually used on barematal and vsphere cluster, user has to a create it first and make sure it can be auto-attached to a PV; b. Input the created pvc's name to spec.pvc.claim in config.imageregistry, and change spec.rolloutStrategy=Recreate; |
I had already added a procedure for configuring RWO block registry storage for vSphere as part of #24043. However, that PR did not add the procedure to the bare metal docs. I've now updated the bare metal docs to also include the same RWO procedure ("Configuring block registry storage"). Please verify that this is correct, @wzheng1? |
704a2e1 to
e194ffc
Compare
81c7981 to
8b69ee9
Compare
|
@bmcelvee - wanted you to know this PR is currently under review as part of BZ 1850510. |
|
@bobfuru As for "object storage" , maybe we can leave it there, since we found Openshift Container Storage can be used as an object storage. But Openshift QE is not responsible for this part of testing, we cannot ack this for sure. |
I agree that it's better to leave object storage out of this note, so I will. We do already mention OCS as an example in the prereqs anyway. But as a side note, OCS is storage-agnostic, "supporting file, block, and object storage, either in-house or in hybrid clouds" [1]. |
8b69ee9 to
22baa39
Compare
|
@wzheng1 Thanks for your feedback. I believe this is ready for a final ack from QE, please? |
|
Acked by QE. |
|
@openshift/team-documentation PTAL |
codyhoag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few nits; otherwise LGTM!
modules/installation-registry-storage-block-recreate-rollout-bare-metal.adoc
Outdated
Show resolved
Hide resolved
modules/installation-registry-storage-block-recreate-rollout-bare-metal.adoc
Outdated
Show resolved
Hide resolved
22baa39 to
826fd0d
Compare
|
@huffmanca Do these changes look good to you? |
|
Apologies for the delay. These changes look good to me! |
|
/cherrypick enterprise-4.6 |
|
@bobfuru: #25826 failed to apply on top of branch "enterprise-4.6": DetailsIn 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. |
|
Opened #26512 to CP to 4.6, which caused merge conflict due to IBM Z edits. Cc: @vikram-redhat and @ktania |
|
/cherrypick enterprise-4.5 |
|
/cherrypick enterprise-4.4 |
|
@bobfuru: new pull request created: #26694 DetailsIn 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. |
|
@bobfuru: #25826 failed to apply on top of branch "enterprise-4.4": DetailsIn 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. |
This work updates content that was added in #24276 and is a continuation of BZ 1850510. Based on consultation with @huffmanca, this PR:
Preview links: