-
Notifications
You must be signed in to change notification settings - Fork 87
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
[WIP]: Add listener based on the machine label and listener label #2155
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. |
@@ -127,6 +127,8 @@ type AdditionalListenerSpec struct { | |||
// Will default to TCP protocol if not specified. | |||
// +optional | |||
Protocol *VPCLoadBalancerListenerProtocol `json:"protocol,omitempty"` | |||
|
|||
Selector metav1.LabelSelector `json:"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.
- This needs to be optional and also omitempty
- Is there a scope for multiple selector? @Karthik-K-N
- what will happen if someone changes this field? are we allowing this field to be changed? if not - can we block it?
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.
what will happen if someone changes this field?
I think to start with we can make this field immutable? so we can block the changes to the field.
Is there a scope for multiple selector?
You mean like configure the listener to multiple machine like Port 22 for machine-1 and machine-2
There are two options
- Add 2 listener with same port but with different selector
- Allow label to have multiple machine separated by comma(,) and add support for this in controller
like
infrastructure.cluster.x-k8s.io/machine-name: machine1, machine2
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.
my bad, this make sense.. may be its worth adding more examples so that it becomes clear for the consumers.
I find this reference useful - https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
@Shilpa-Gokul its worth writing a design doc with more examples, lets do that before this PR. I like the way it is written here - #2139 for one of the work. |
Yes, We have already planned to do so, With some diagrams and examples, That would become easier for review and to see if there is any better approach as well, This is also one of the reasons for keeping this as WIP and also adding UT with only happy paths. |
What this PR does / why we need it:
This PR is not ready to review yet.
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 #1678
Special notes for your reviewer:
/area provider/ibmcloud
Release note: