chore(*) inject ingress.kubernetes.io/service-upstream #1608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Nikolay Nikolaev <[email protected]>
|
@Mergifyio update |
|
Command
|
|
|
jakubdyszkiewicz
approved these changes
Mar 1, 2021
added 3 commits
March 2, 2021 11:00
Signed-off-by: Nikolay Nikolaev <[email protected]>
nickolaev
force-pushed
the
chore/service_controller
branch
from
31af9be to
aeb0181
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Automatically inject
ingress.kubernetes.io/service-upstreamto all K8s Services, for the purposes of exposing Service Mesh service through the GW.Previously users had to do this on their own.
Documentation