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
installer-aws: create edge compute pool for AWS Local Zones #1232
installer-aws: create edge compute pool for AWS Local Zones #1232
Conversation
Skipping CI for Draft Pull Request. |
4d438fa
to
e46530d
Compare
e46530d
to
64ad757
Compare
6a6a3e9
to
84458cd
Compare
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
/assign @patrickdillon @JoelSpeed @rvanderp3 @dhellmann |
8ca1a11
to
aa87fbb
Compare
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
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.
This is looking very good, thank you @mtulio! I left a few minor comments but in my opinion this is ready for review. @sdodson and @dhellmann might have opinions and of course our friends from installer @patrickdillon and @makentenza. Tks!
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
16ff2e6
to
fdbdba4
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.
Review comments addressed to the document in my last commit. New topics have been added and/or updated:
- Motivation
- Proposal / Phase 1: subnet allocation, instance and volume type, MachineSets
- Infrastructure costs
- Risks
- Test plan (Need help!)
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
enhancements/installer/aws-custom-edge-machineset-local-zones.md
Outdated
Show resolved
Hide resolved
Inactive enhancement proposals go stale after 28d of inactivity. See https://github.com/openshift/enhancements#life-cycle for details. Mark the proposal as fresh by commenting If this proposal is safe to close now please do so with /lifecycle stale |
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Presubmits were also created for two phases, awaiting the final credentials for a CI Account: |
I'm happy to proceed, suggest to squash the commits before we merge though (you've tagged my GH in one, should remove that) |
The enhancement proposes to introduce a new compute pool type edge to create MachineSets on a day zero operations in IPI, deploying compute resources with `NoSchedule` taints in AWS Local Zones locations. The R&D is divided into three phases: - Phase 0 / SPLAT-635: Research options to create compute nodes on AWS Local Zones and document it as a day-0 - Phase 1 / SPLAT-636: Create edge compute pool to generate MachineSets for node with NoSchedule taints when installing a cluster in an existing VPC with AWS Local Zone subnets. - Phase 2 / SPLAT-657: Installer automates the network resources creation on Local Zone based on the edge compute pool. This EP covers Phases 1 and 2, as part of RFE-2782.
c8b832e
to
15a2593
Compare
For sure, squashed! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson 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 |
/lgtm |
@mtulio: 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/test-infra repository. I understand the commands that are listed here. |
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
Inserting the instructions to install a cluster expanding nodes in Local Zones (new VPC), into existing documentation of installing in existing VPC. The Day-2 section is also added for reference of existing Local Zone automation. The Day 2 is not part of the official documentation delivered on 4.14, but it is mapped as an open question in the enhancement proposal [1232](openshift/enhancements#1232). The steps described on the KCS was validated with QE and SDN teams.
The enhancement proposes to introduce a new compute pool type
edge
to create MachineSets on a day zero operations on IPI to deploy compute resources withNoSchedule
taints in AWS Local Zones locations.The R&D is divided into three phases:
edge
compute pool to generate MachineSets for node withNoSchedule
taints when installing a cluster in existing VPC with AWS Local Zone subnets.edge
compute pool.This EP covers Phases 1 and 2.
This EP is part of the RFE-2782.