-
Notifications
You must be signed in to change notification settings - Fork 333
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
HOSTEDCP-2231: Remove cloud connection, Set Transit Gateway as default #5293
base: main
Are you sure you want to change the base?
Conversation
@aman4433: This pull request references HOSTEDCP-2231 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:
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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aman4433 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @aman4433. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
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.
Overall PR looks good to me.
Before merging this PR, please keep a PR to update the CI jobs in openshift/release
as well. Since this is a breaking change for CI job configuration.
@@ -48,8 +48,19 @@ where | |||
|
|||
Running this command will create [infra](create-infra-separately.md) and manifests for the hosted cluster and deploys it. | |||
|
|||
## Utilizing Power Edge Router(PER) via Transit Gateway | |||
To use IBM Cloud's PER feature via transit gateway, need to pass `--use-power-edge-router` and `--transit-gateway-location $TRANSIT_GATEWAY_LOCATION` flags to create cluster command like below. | |||
## Using Transit Gateway (Default Networking Mode) |
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.
IMO this block is not required, let's update the previous block itself with --transit-gateway-location
flag and explaining it like other flags would be enough. By keeping it in separate block will confuse the user.
--pull-secret $PULL_SECRET \ | ||
--node-pool-replicas=2 \ | ||
--use-power-edge-router \ | ||
--transit-gateway-location $TRANSIT_GATEWAY_LOCATION | ||
|
||
Read [here](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-per) to know more about PER and data centers where its deployed currently. |
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.
As PER is not supported, we can remove this description for now.
Looks good to me. Just some minor nits ! |
Please update the docs/content/how-to/powervs/prerequisites-and-env-guide.md's Authorization section since we need an extra permission to do operation on TG. |
768ef52
to
50e2cdb
Compare
What this PR does / why we need it: This PR updates the PowerVS documentation and code to reflect Transit Gateway as the default networking mode. IBM Cloud has removed support for cloud connection, necessitating this change.
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story: Fixes #5062Checklist