openshift-docs
openshift-docs copied to clipboard
openshift
OSDOCS-9695: Create the initial page for AWS AMIs in ROSA
Version(s):
enterprise-4.15+
Issue: OSDOCS-9695
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information: Created a landing space for the ROSA AMIs
@EricPonvelle: This pull request references OSDOCS-9695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
enterprise-4.15+Issue: OSDOCS-9695
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information: Created a landing space for the ROSA AMIs
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 openshift-eng/jira-lifecycle-plugin repository.
🤖 Wed May 15 14:33:34 - Prow CI generated the docs preview:
https://72483--ocpdocs-pr.netlify.app/openshift-rosa/latest/rosa_architecture/rosa-aws-amis.html
I also don't see a distinction between ROSA classic and ROSA HCP. I could be wrong but I understand the AMIs are different between the two.
@EricPonvelle As my comment in the JIRA ticket,
For classic cluster, it uses the override image, the id can get from rosacli, here is an example to get them for 4.15 version, rosa list versions -o json|jq -r '[.[]|select(.raw_id | contains("4.15"))]'|jq -r '.[0].image_overrides.aws[]| "\(.region.id) \(.ami)"'
For hosted-cp cluster, it uses the same OCP image, It can get from openshift-install coreos print-stream-json and also embedded in OCP installer code https://github.com/openshift/installer/blob/master/data/data/coreos/rhcos.json , for different versions, we can get the AMIs IDs in the rhos.json in different branch, like "release-4.14".
the versions for hosted-cp in document should only include versions >=4.14, as hosteed-cp commercially supports since 4.14.
Could you update the document accordingly?
@EricPonvelle: all tests passed!
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@EricPonvelle what are the two separate AMI columns in the HCP section for? Is it that we have two separate AMIs for use? Different architectures?
@michaelryanmcneill when @iamkirkbater and I were running the commands, we found one set of commands produced two AMIs per region. I compared that to the AMIs he found, and they did not match. Then, using this idea, I tested the various openshift-install z-stream versions, and found that even within the same Y-stream, we had different AMIs per region.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
The branch/enterprise-4.18 label has been added to this PR.
This is because your PR targets the main branch and is labeled for enterprise-4.17. And any PR going into main must also target the latest version branch (enterprise-4.18).
If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.
