OSDOCS Document how to perform boot image updates on marketplace clusters GCP#108868
OSDOCS Document how to perform boot image updates on marketplace clusters GCP#108868mburke5678 wants to merge 15 commits intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
size/L
|
🤖 Tue Apr 14 12:01:31 - Prow CI generated the docs preview: |
|
/retest |
|
@djoshy PTAL |
| |=== | ||
| | Current image prefix | Variant | ||
| | `projects/rhcos-cloud/global/images/` | Default | ||
| | `projects/redhat-marketplace-public/global/images/` | Custom {op-system} image |
There was a problem hiding this comment.
| | `projects/redhat-marketplace-public/global/images/` | Custom {op-system} image | |
| | `projects/redhat-marketplace-public/global/images/` | GCP Marketplace {op-system} image |
It's better to lead with marketplace for this case, custom can be just non standard and doesn't necessarily have to be from the marketplace.
There was a problem hiding this comment.
I believe I picked this term up from the install docs: You can override the default behavior by using a custom RHCOS image that is available from the Azure Marketplace.
I like your version better, just to make it clear.
| {opp}:: `redhat-coreos-opp-413-x86-64-202305021736` | ||
| {oke}:: `redhat-coreos-oke-413-x86-64-202305021736` | ||
|
|
||
| {gcp-short} does not publish Marketplace images for {product-title} later than these {product-title} 4.13 images. If the current boot image in your cluster matches one of the listed images, no further action is necessary. |
There was a problem hiding this comment.
| {gcp-short} does not publish Marketplace images for {product-title} later than these {product-title} 4.13 images. If the current boot image in your cluster matches one of the listed images, no further action is necessary. | |
| Red Hat has not published Marketplace images for {product-title} later than these {product-title} 4.13 images. If the current boot image in your cluster matches one of the listed images, no further action is necessary. |
Similar to https://github.com/openshift/openshift-docs/pull/109021/changes#r3001249060; I'm not sure how to best explain this bit. Perhaps we should just ask them to compare their new bootimage vs their current bootimage so the docs dont have to be updated in the future for an update?
There was a problem hiding this comment.
GCP marketplace images are not accessible via openshift-install like AWS marketplace images are, so maybe the best approach is
- Azure -> ask them to compare against openshift-install values
- GCP -> we manually update the docs everytime the GCP marketplace gets a bump, so we just do the text change I proposed above(Red Hat is responsible, not GCP strictly speaking)
There was a problem hiding this comment.
we manually update the docs everytime the GCP marketplace gets a bump
How do we track if there is an image bump?
There was a problem hiding this comment.
No easy way, unfortunately. For now, we'd need to list the lack of newer images as a known issue so we don't forget about it. I can try to keep an eye on it and check occasionally, but ideally we're able to get the publishers to do a newer release/automate it to a degree.
|
@ptalgulk01 @sergiordlr PTAL |
mburke5678
force-pushed
the
mco-manual-boot-image-gcp
branch
from
4ee6ebd to
b74576b
Compare
mburke5678
force-pushed
the
mco-manual-boot-image-gcp
branch
from
b74576b to
ce7eb8f
Compare
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
4 participants
Incorporate https://gist.github.com/djoshy/5f2c6fe469d9ce5a9e4645e78ec57694#osd-clusters-only-for-sres
https://redhat.atlassian.net/browse/OSDOCS-18794
Link to docs preview:
OCP: Manually updating the boot image on an Google Cloud cluster -- New module. Final location TBD.
QE review: