-
Notifications
You must be signed in to change notification settings - Fork 77
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
Extend supported service endpoints #1637
Conversation
|
Welcome @cjschaef! |
Hi @cjschaef. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cjschaef 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 |
✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
/cc @Prajyot-Parab |
Add additional services to endpoint override support for VPC related services.
1efdfa6
to
e51c0f2
Compare
Note: we're following OpenShift convention for service names being |
I don't mind but just make sure we keep the backward compatibility as well, so that existing consumers shouldn't be suffering from this refactor. e.g: we can deprecate |
@@ -47,7 +47,7 @@ it into a management cluster using `clusterctl`. | |||
> `${ServiceRegion1}:${ServiceID1}=${URL1},${ServiceID2}=${URL2};${ServiceRegion2}:${ServiceID1}=${URL1...}`. | |||
|
|||
|
|||
Supported ServiceIDs include - `vpc, powervs, rc` | |||
Supported ServiceIDs include - `CIS, COS, DNSServices, IAM, KeyProtect, ResourceManager, powervs, rc, vpc` |
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 of today, We dont user any of CIS, DNSServices, KeyProtect services. so should we add them now or add them when we start using these services later.
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.
make sense, lets remove the entries which aren't used in this controller at the moment.
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.
@Karthik-K-N is the ResourceManager duplicate of rc here?
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.
@Karthik-K-N also the iam
endpoint is being set via IBMCLOUD_AUTH_URL
param, so do we really need the IAM service ID?
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 so its duplicate, if we want to use ResourceManager instead of rc, may be we can add support for both for a release and based on requirement we can deprecate later.
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.
additional information... we have our (IBM Cloud VPC) set of required endpoint services for OCP defined here: https://github.com/openshift/installer/blob/release-4.15/data/data/install.openshift.io_installconfigs.yaml#L3450-L3492
we default to public endpoints for these required services, but provide the ability to override via install-config arguments (in order to support restricted network (airgap) install scenario)
that served as our basis for 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.
Thanks for the information, not all those service endpoints from openshift will be used by the CAPI controller, e.g: CIS will be used by the ingress operator(part of OCP Cluster Operartors) which is out of scope for this project.
We will add which are really required for the CAPI controllers to run e.g: COS, IAM, ResourceController VPC etc..
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 add them later, but they could all possibly be required (depending on the Network design) as the Infrastructure resources get created/referenced in VPC related enhancements.
Or we can wait on merging this until I have completed the necessary enhancements to CAPI for VPC Infrastructure, if that appears to be a better option.
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.
Let's have an incremental approach, you can merge the code with bare minimum required changes, later will add those additional endpoints as in when needed.
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 will wait until I have my first series of improvements to CAPI and VPCluster management then, since that is where I will start requiring the additional endpoints.
PR needs rebase. 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. |
we don't need this anymore, got it merged part of #1648. |
Add additional services to endpoint override support for VPC related services.
What this PR does / why we need it: Expands the supported IBM Cloud Services that can have endpoint overrides.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Special notes for your reviewer:
/area provider/ibmcloud
Release note: