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
clustermesh-apiserver: ExternalTrafficPolicy and internalTrafficPolicy can now be changed. #24166
Conversation
6c950b9
to
59541a1
Compare
How can I get a CI through? |
CI can only be triggered by Cilium committers (see https://docs.cilium.io/en/v1.13/community/governance/commit_access/). Just ping one of the assigned reviewers to run the tests for you. |
/test |
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.
Thanks for the PR! I have left s ome feedback on Kubernetes compatibility.
Also, on a different note, the PR/commit description mentions ci:
- we use the term ci
typically for continuous integration. I think a better commit title here would be clustermesh-apiserver: ExternalTrafficPolicy and internalTrafficPolicy can now be changed
install/kubernetes/cilium/templates/clustermesh-apiserver/service.yaml
Outdated
Show resolved
Hide resolved
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.
ci: ExternalTrafficPolicy and internalTrafficPolicy can now be changed.
It would be nice to add a pointer to the commit that enabled this change, in the commit description.
Please note that the smoke tests for the Helm charts are failing:
please run 'make -C install/kubernetes' and submit your changes
754612d
to
b323347
Compare
I am getting an error in CI, but my commit message clearly does not exceed 75 characters.
|
I think it does, currently it's set to
which actually is 90 chars long |
b323347
to
0626882
Compare
Thx! |
How about now? |
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.
Thanks!
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.
Thanks
/test |
Thanks too! 🙏 |
0626882
to
9eae352
Compare
* ExternalTrafficPolicy * internalTrafficPolicy Signed-off-by: kahirokunn <okinakahiro@gmail.com>
9eae352
to
eed44f1
Compare
I think the CI test is failing in some areas that have nothing to do with my fix. |
Unfortunately, the push to the branch invalidated the results so I cannot check them anymore. But yes, there are a few flaky tests. Let me re-run CI to check if the test failures are legitimate or not. Please do not push to the branch anymore (unless to fix bugs). Rebasing is usually not needed. |
/test |
okay |
CI passed - the conformance ingress tests have been refactored and so will not be triggered in this branch. Old old test passed here: https://github.com/cilium/cilium/actions/runs/4350648456/jobs/7601557102 Marking ready to merge. Thanks @kahirokunn for your contribution! |
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.
If externalTrafficPolicy is set to Local, the IP address of the connection source can be retained.
This is very important for observer days, so you may want to enable it in many cases.
https://kubernetes.io/docs/tutorials/services/source-ip/#source-ip-for-services-with-type-nodeport