This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
Consul integration cldcvr #66
Open
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
…o push svcmesh-consul metrics from prometheus, added consul service monitor changes to benchmark code
…ted helm values in all files 3. Updated else if in wrk2.yaml
…mary dashboard 3. Consul setup added to the benchmark suite script
…afana Dashbaords to include Consul results 3. Updaetd the run_benchmark.sh for the consul integration 4. Updated the metric-merger code to push consul job metrics 5. Updated the README.md with the same.
|
@surajssd Please review this PR. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
[Title: Consul service mesh Integration to the benchmarking too;]
[ 1. Added all changes required to consul integration 2. Updated the Grafana Dashboards to include Consul results 3. Updated the run_benchmark.sh for the consul integration 4. Updated the metric-merger code to push consul job metrics 5. Updated the emojivoto helm template to add the namespace creation logic wrt the service mesh in use 6. Updated the README.md with the same.]
How to use
[ 1. If you are using the run_benchmark.sh then follow the same process
2. Else use the script/setup-servicemeshes.sh to install the service mesh onto your k8s cluster(tested on GKE). Then deploy the applications with service mesh as per the README.md. Run the benchmark tool as it is and then metric-merger and observe the output ]
Testing done
[1. Tested the entire flow on GKE and it is working as expected. Demoed it to Thilo Fromm. ]