-
Notifications
You must be signed in to change notification settings - Fork 331
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
feat(gateway): cp annotations from gateway to svc #4327
feat(gateway): cp annotations from gateway to svc #4327
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4327 +/- ##
==========================================
- Coverage 55.75% 55.70% -0.05%
==========================================
Files 935 935
Lines 56434 56437 +3
==========================================
- Hits 31462 31439 -23
- Misses 22498 22527 +29
+ Partials 2474 2471 -3
Continue to review full report at Codecov.
|
Test failure looks unrelated? |
@johnharris85 What do you think about just adding a single |
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.
LGTM maybe @lahabana take a look too 🤷
6837a95
to
a2323eb
Compare
/golden_files |
Arg obviously my tool is broken with forks :( |
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.
Once the conflict is resolved
Signed-off-by: John Harris <john@johnharris.io>
Signed-off-by: Mike Beaumont <mjboamail@gmail.com>
a2323eb
to
faa8b0c
Compare
Summary
Many cloud providers use annotations on service objects to control behavior with their auto-provisioned load balancers. This PR adds a feature that will copy all annotations specified on the
MeshGatewayInstance
object to the generated service.In #4075 there was some discussion about how to implement this, and a suggestion that maybe we go down the route of creating a CRD that would allow full customization of the generated service. This makes sense in future, however the 90% use case is solved by just enabling a user to specify annotations. This PR's implementation covers that use case for users who are currently experiencing issues while not adding / altering any CRDs / APIs, and is easy to deprecate when we decide on a 'better' solution.
Will add docs if folks are fine with this implementation.
Issues resolved
Partially fix #4075
Documentation
Testing
- [ ] Manual testing on UniversalBackwards compatibility
- [ ] UpdateUPGRADE.md
with any steps users will need to take when upgrading.- [ ] Addbackport-to-stable
label if the code follows our backporting policy