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.

Sign up for GitHub

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

Jump to bottom

Configure Loadbalancer back-end pool only for controlplane machines #1990

Open
Karthik-K-N opened this issue Oct 4, 2024 · 3 comments · May be fixed by #2004
Open

Configure Loadbalancer back-end pool only for controlplane machines #1990

Karthik-K-N opened this issue Oct 4, 2024 · 3 comments · May be fixed by #2004
Assignees
@carmal891
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@Karthik-K-N
Copy link
Contributor

/kind bug
/area provider/ibmcloud

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

Creating a IBMPowerVS cluster from cluster-template-powervs-create-infra.yaml template creates a Loadbalancer and configures all the machines of the cluster to its backend pool.

What did you expect to happen:

Only control plane machines should be configured to backendpool as 6443 is APIServer port and only control-plane machines will serve in that port.

Changes needs to be done:

  1. Just skip configuring LB backend pool for data plane nodes here.
  2. Utility function
Screenshot 2024-10-04 at 4 08 58 PM available in capi repo for identifying machine as control-plane machine

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api version:
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Oct 4, 2024
@Karthik-K-N Karthik-K-N changed the title Configure Loadbalancer only to controlplane machines Configure Loadbalancer back-end pool only for controlplane machines Oct 4, 2024
@Karthik-K-N
Copy link
Contributor Author

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@Karthik-K-N:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Oct 4, 2024
@carmal891
Copy link

/assign

@carmal891 carmal891 linked a pull request Oct 12, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carmal891 carmal891

Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
3 participants
@k8s-ci-robot @Karthik-K-N @carmal891