Skip to content
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

Closed

Conversation

cjschaef
Copy link
Contributor

@cjschaef cjschaef commented Feb 28, 2024

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

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

Extend supported IBM Cloud Service endpoint overrides

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Feb 28, 2024
Copy link

linux-foundation-easycla bot commented Feb 28, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: cjschaef / name: Christopher J Schaefer (e51c0f2)

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Feb 28, 2024
@k8s-ci-robot
Copy link
Contributor

Welcome @cjschaef!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-ibmcloud 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-ibmcloud has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 28, 2024
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cjschaef
Once this PR has been reviewed and has the lgtm label, please assign mkumatag 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:

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

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 28, 2024
Copy link

netlify bot commented Feb 28, 2024

Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!

Name Link
🔨 Latest commit e51c0f2
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/65e0a48d79b25c0008933091
😎 Deploy Preview https://deploy-preview-1637--kubernetes-sigs-cluster-api-ibmcloud.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 28, 2024
@cjschaef cjschaef marked this pull request as ready for review February 28, 2024 21:23
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 28, 2024
@mkumatag
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 29, 2024
@mkumatag
Copy link
Member

/cc @Prajyot-Parab

Add additional services to endpoint override support for VPC
related services.
@jeffnowicki
Copy link

jeffnowicki commented Mar 1, 2024

Note: we're following OpenShift convention for service names being PascalCase. While we don't want to impose any specific consumer conventions, in this particular case it would ease our (VPC) OpenShift use of CAPI if we could follow similar conventions (where it makes sense). Let us know your thoughts and if you are open to refactoring the current names to PascalCase also.

@mkumatag
Copy link
Member

mkumatag commented Mar 1, 2024

Note: we're following OpenShift convention for service names being PascalCase. While we don't want to impose any specific consumer conventions, in this particular case it would ease our (VPC) OpenShift use of CAPI if we could follow similar conventions (where it makes sense). Let us know your thoughts and if you are open to refactoring the current names to PascalCase also.

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 vpc in this release and introduce VPC and next release you can remove vpc from the code.

@@ -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`
Copy link
Contributor

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.

Copy link
Member

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.

Copy link
Contributor

@Prajyot-Parab Prajyot-Parab Mar 5, 2024

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?

Copy link
Contributor

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?

Copy link
Contributor

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.

Copy link

@jeffnowicki jeffnowicki Mar 5, 2024

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

Copy link
Member

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

Copy link
Contributor Author

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.

Copy link
Member

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.

Copy link
Contributor Author

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.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 13, 2024
@k8s-ci-robot
Copy link
Contributor

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.

@mkumatag
Copy link
Member

we don't need this anymore, got it merged part of #1648.

@mkumatag mkumatag closed this Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants