feat(contour-bookinfo): Add Contour Ingress Gateway configuration for Bookinfo application #45
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.
fixes : #30
This PR addresses the issue of using a production-ready ingress gateway instead of direct NodePort exposure for the bookinfo application, implementing Contour as the ingress controller .
Implementations :
Added
In the
kind/bookinfo/contour_ingress/README.mdi've mentioned installation of contour ingress and bookinfo setup , also providedkind/bookinfo/contour_ingress/slice.yamlfor inter cluster communication of ingress and istio bookinfo services via OpenVPN .Tested this configuration based on kind cluster using kubeslice minimal-demo
kubeslice-cli install --profile=minimal-demo