Move istio-ingressgateway to Yorkie Namespace
#836
Merged
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #836 +/- ##
=======================================
Coverage 50.95% 50.95%
=======================================
Files 70 70
Lines 10226 10226
=======================================
Hits 5211 5211
Misses 4487 4487
Partials 528 528 ☔ View full report in Codecov by Sentry. |
hackerwins
approved these changes
Apr 6, 2024
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.
What this PR does / why we need it:
Relocate the
istio-ingressgatewayto the yorkie namespace under the nameyorkie-gateway.The purpose of this move is to clearly segregate yorkie-related Kubernetes resources from other services for better organization and management.
Additionally, for production Istio deployments, it is crucial to separate the istio-ingressgateway and istiod components to enable independent operation.
In Istio, this gateway topology is called Dedicated application gateway.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation:
Checklist: