-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ingress: Add loadBalancerIP and loadBalancerClass #22670
Conversation
This pull request has been automatically marked as stale because it |
Bump! Really want this. |
Commits 9a70feef22e598cf19f7d694a64a0420d5855215, e18b4ce8d5fb2941a24d117f3e58f0fce998a44d do not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
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.
Sorry for the delay, the changes look good to me :), only one minor comment as per below (which can be taken care separately).
@@ -24,6 +24,14 @@ spec: | |||
protocol: TCP | |||
nodePort: {{ .Values.ingressController.service.secureNodePort }} | |||
type: {{ .Values.ingressController.service.type }} | |||
{{- if semverCompare ">=1.24-0" .Capabilities.KubeVersion.Version -}} |
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.
these two fields are only applicable if ServiceType is LoadBalancer. Understand that the service type is added in dependently with this PR, so we can take care of this subsequently.
e87eeac
to
2d29102
Compare
/test |
This commit is to add loadBalancerIP and loadBalancerClass for shared Ingress service. Kindly note the below points: - loadbalancerIP feature is depending on cloud provider controller - loadBalancerClass is only supported for k8s 1.24 and later. Signed-off-by: Oliver Ni <oliver.ni@gmail.com>
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
Test failure seems like a flake connecting to the apisever for one single test in one run. I'm going to go and say that this is ok to merge. The run was https://jenkins.cilium.io/job/Cilium-PR-K8s-1.25-kernel-4.19/638/, and the failure message was
Given that this change has no effect by default, it's safe to say this is a flake. Labeling as ok-to-merge. |
FYI, that is known flake #15455, for which Cilium is known to be the culprit. |
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: <commit-id>
tag, thenplease add the commit author[s] as reviewer[s] to this issue.
This pull request adds configuration options for the
loadBalancerClass
andloadBalancerIP
fields in theService
object created for cilium's ingress controller wheningressController.loadbalancerMode
is set toshared
.Previously, there was no option to configure these options, which makes it difficult for me to use the chart in my situation. I have to manually delete and recreate the service, since the field cannot even be edited with
kubectl edit
.Sorry about the commit titles. If this change is approved, would appreciate a squash and merge with a better title.