-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add proposal for assigning additional listener to specific machines #2173
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Shilpa-Gokul 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 @Shilpa-Gokul. 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
docs/proposal/additional-listener.md
Outdated
|
||
[Github Issue](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/issues/1678) | ||
## Motivation | ||
Currently, when a listener pool is configured for a specific port (e.g., port 22), all machines are added to the pool. |
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 it should be like, When configuring Loadbalancer's additional listeners, all the machines are added to Listenr's pool.
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.
Addressed
docs/proposal/additional-listener.md
Outdated
[Github Issue](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/issues/1678) | ||
## Motivation | ||
Currently, when a listener pool is configured for a specific port (e.g., port 22), all machines are added to the pool. | ||
This creates a challenge when debugging OpenShift cluster deployments, as access to the bootstrap node is necessary for |
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.
Lets not mention anything like Openshift, It should be generic. But you can mention you want to ssh to particular machine.
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.
Done
docs/proposal/additional-listener.md
Outdated
The load balancer details are retrieved from the IBMPowerVSCluster.Spec.LoadBalancers. If no load balancers are | ||
specified in the Spec, the load balancer details are generated based on the IBMPowerVSCluster name. | ||
Loop through the load balancers, check the status of the IBMPowerVSCluster, and verify the load balancer's | ||
provisioning status. Proceed only if the status is Active and it contains backend pools. |
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 existing flow need not be mentioned. Lets only mention how we are changing the flow.
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.
Removed old flow
can be assigned to control plane machines. | ||
|
||
### Workflow | ||
![additional-listeners-workflow](../images/additional-listener-workflow.png) |
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.
In diagram to start with
IBMPowerVSCluster -> Loadbalancers
In parallel flow lets mention
IBMPowerVSMachine -> IBMPowerVSMachine.Lables == selector
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.
Done
1b395b0
to
a08663e
Compare
What this PR does / why we need it:
Adds a proposal to support assigning additional listeners to specific machines based on label selectors.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
/area provider/ibmcloud
Release note: