SPLAT-1159: installer: support of extending workers to AWS Wavelength

[mtulio]

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength
• Goal 4 (SPLAT-1220): Carrier IP Address assignment when creating EC2 instances with Machine API

[openshift-ci-robot]

@mtulio: This pull request references OCPSTRAT-736 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 feature to target the "4.15.0" version, but no target version was set.

In response to this:

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength Zones - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength Zones
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength Zones
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength Zones

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.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jerpeter1 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@mtulio: This pull request references OCPSTRAT-736 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 feature to target the "4.15.0" version, but no target version was set.

In response to this:

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength Zones - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength Zones
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength Zones
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength Zones
• Goal 4 (SPLAT-1220): Carrier IP Address assignment when creating EC2 instances with Machine API

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.

[mtulio]

Would you mind taking a look at this proposal?
/assign @rvanderp3 @JoelSpeed @patrickdillon

[openshift-ci]

@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.

[openshift-bot]

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 /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle stale

[openshift-ci-robot]

@mtulio: This pull request references OCPSTRAT-736 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 feature to target either version "4.16." or "openshift-4.16.", but it targets "openshift-4.15" instead.

In response to this:

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength Zones
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength Zones
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength Zones
• Goal 4 (SPLAT-1220): Carrier IP Address assignment when creating EC2 instances with Machine API

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.

[openshift-ci-robot]

@mtulio: This pull request references OCPSTRAT-736 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 feature to target either version "4.16." or "openshift-4.16.", but it targets "openshift-4.15" instead.

In response to this:

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength
• Goal 4 (SPLAT-1220): Carrier IP Address assignment when creating EC2 instances with Machine API

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.

[openshift-bot]

Stale enhancement proposals rot after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Rotten proposals close after an additional 7d of inactivity.
Exclude this proposal from closing by commenting /lifecycle frozen.

If this proposal is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

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.

[dhellmann]

(automated message) This pull request is closed with lifecycle/rotten. The associated Jira ticket, OCPSTRAT-736, has status "In Progress". Should the PR be reopened, updated, and merged? If not, removing the lifecycle/rotten label will tell this bot to ignore it in the future.

[dhellmann]

(automated message) This pull request is closed with lifecycle/rotten. The associated Jira ticket, OCPSTRAT-736, has status "In Progress". Should the PR be reopened, updated, and merged? If not, removing the lifecycle/rotten label will tell this bot to ignore it in the future.

[dhellmann]

(automated message) This pull request is closed with lifecycle/rotten. The associated Jira ticket, OCPSTRAT-736, has status "Release Pending". Should the PR be reopened, updated, and merged? If not, removing the lifecycle/rotten label will tell this bot to ignore it in the future.

[openshift-ci-robot]

@mtulio: This pull request references SPLAT-1159 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.19.0" version, but no target version was set.

In response to this:

This enhancement introduces the support of installing a cluster on AWS extending worker nodes to Wavelength - as edge zones.

This is part of the feature OCPSTRAT-736, covering the following epics/goals:

• Goal 1 (SPLAT-1125): Fully automate the network requirements to deploy edge nodes on AWS Wavelength
• Goal 2 (SPLAT-1218): Support Installing a cluster in existing VPC (BYO VPC) extending nodes to AWS Wavelength
• Goal 3 (SPLAT-1219): Document the steps to extend existing OpenShift clusters running on AWS to the edge nodes in AWS Wavelength
• Goal 4 (SPLAT-1220): Carrier IP Address assignment when creating EC2 instances with Machine API

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.

[mtulio]

For some reason this EP has been lost when wrapping up the feature last year.

The feature has been added to 4.15+. I am reopening this PR to formalize the flow.

/assign @rvanderp3 @JoelSpeed @patrickdillon

/reopen

[openshift-ci]

@mtulio: Failed to re-open PR: state cannot be changed. The installer-aws-wavelength-zones branch was force-pushed or recreated.

In response to this:

For some reason this EP has been lost when wrapping up the feature last year.

The feature has been added to 4.15+. I am reopening this PR to formalize the flow.

/assign @rvanderp3 @JoelSpeed @patrickdillon

/reopen

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.