-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[OSDOCS-5240] Installer support to automatically create the MachineSets when installing in existing VPC on AWS w/Local Zones #57427
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
[OSDOCS-5240] Installer support to automatically create the MachineSets when installing in existing VPC on AWS w/Local Zones #57427
Conversation
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/15883 |
|
@mtulio I'm also happy to integrate whatever is new for SPLAT-363 into https://docs.openshift.com/container-platform/4.12/installing/installing_aws/installing-aws-localzone.html. That assumes that the user story for the new content is simpatico with the old content, which I gather is the case? At the moment, this PR is about getting what I grabbed from openshift/installer#6371 into something that roughly resembles our mod docs format and then thinking through what is essential to the story and what is not. It's flexible. 👍 |
Yes, currently phase-1 (this PR) will automate the sections I mentioned above, adding manifests manually.
That's perfect! Thanks! |
1baddd9 to
f8ee526
Compare
0f5493c to
c86374c
Compare
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.
Probably redundant. Keeping for now. Not currently incorporated into installation guide.
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.
Probably redundant. Keeping for now. Not currently incorporated into installation guide.
527f0ac to
b3ced87
Compare
|
@mtulio https://57427--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-localzone.html incorporates some of the edge pool content from openshift/installer#6371 and replaces the CloudFormation templates with the latest from the installer repo. What do you think so far? Feel free to make comments or suggestions against the source files directly. The 4.12 guide uses JSON files to handle a number of parameters for configuration and deployment. Is there any reason not to keep to that pattern here, at least as far as CloudFormation templates go? Assuming that's fine, it seems like what remains to be exported is just |
mtulio
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.
Great! Initial review of the structure. Thanks
| * `zone_type=local-zone` | ||
| * `zone_group=<LOCAL_ZONE_GROUP>` |
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.
Those labels should be updated to:
machine.openshift.io/zone-group=<$ZONE_GROUP_NAME>machine.openshift.io/zone-type=local-zone
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.
Could you please make sure those labels are set correctly on the entire Local Zone book? It's defined on the Enhancement Proposal and installer implementation for phase-1, but it seems to passed from the phase-0 docs review.
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.
Beyond what this PR touches, I'm not seeing these labels anywhere.
| @@ -0,0 +1,9 @@ | |||
| :content-type: CONCEPT | |||
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.
same comment for file modules/installation-aws-local-zones-ref-deployment.adoc
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.
Marking this for removal.
Particularly I prefer the inline method which could save some steps. I think it is an improvement based on the last version. Open for thoughts. |
My preference is to use content that's already been through our review process when possible, though I'm not against your method if there's time. Could we agree to make that a low priority switch within this PR? |
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.
Not sure where to put this yet, or even if it should be included.
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.
I think it could be important to note if the user add the gp3 as volume type to be used on edge pool, the machineset manifest will be forced to use it, if gp3 is not supported on the location (discovered by the subnet ID for Local Zones) the machine will fail to create.
is it possible to add a comment after the 'title' of the example? (below)
.Example edge pool with a custom EBS type
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.
@mtulio Which example are you referring to? Just want to be sure that I'm tagging the right thing.
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.
@mtulio Which example are you referring to? Just want to be sure that I'm tagging the right thing.
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.
I can insert text before or after the sample and its title, sure.
For sure, I am reviewing the other references for AWS CLI in our docs, it also uses Example:
|
Co-authored-by: Yunfei Jiang <[email protected]>
|
@yunjiang29 What do you think of my comment here: https://github.com/openshift/openshift-docs/pull/57427/files/73048b401fc2219248d960e153ea71f5b131495b#r1187570706 Generate install-config.yaml -> read about what you'll edit in the install-config.yaml -> edit install-config.yaml isn't an unusual pattern in the docs, and I don't think there's duplication in the current state of the PR, but I'm happy to change things. This is not my usual territory. :) |
|
/lgtm |
|
Thank you! |
lpettyjo
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.
Otherwise, LGTM. Nice work!
|
New changes are detected. LGTM label has been removed. |
|
/cherry-pick enterprise-4.13 |
|
@maxwelldb: new pull request created: #59950 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. |
…s on the structure (openshift#4) * OSDOCS-5240 openshift#57427: review rendered page with important fixes on the structure * Apply suggestions from code review Co-authored-by: Max Bridges <[email protected]> * Apply suggestions from code review Co-authored-by: Max Bridges <[email protected]> --------- Co-authored-by: Max Bridges <[email protected]>
Version(s): 4.13
Issue: OSDOCS-5240, SPLAT-636
Link to docs preview: https://57427--docspreview.netlify.app/openshift-enterprise/latest/installing/installing_aws/installing-aws-localzone.html
QE review: