Merge pull request #5 from paritytech/substrate-telemetry-readme

fixig the readme
paritytech · Aug 20, 2021 · 61de17f · 61de17f
2 parents b4ba684 + 5a4b51c
commit 61de17f
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/charts/substrate-telemetry/Chart.yaml b/charts/substrate-telemetry/Chart.yaml
@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
+version: 2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

diff --git a/charts/substrate-telemetry/README.md b/charts/substrate-telemetry/README.md
@@ -22,4 +22,3 @@ By default, the type of Kubernetes service used for Telemetry-Core, Telemetry-Sh
 - All the services must be exposed over `HTTPS`.
 - The `Core` service could also be exposed using the `Frontend` Nginx service. The Nginx configuration should be tweaked for this purpose.
 - Consider setting `.Values.envVars.frontend.SUBSTRATE_TELEMETRY_URL` variable otherwise the web clients wouldn't be able to find the `Core` service address.
-
Original file line number	Diff line number	Diff line change
Expand Up		@@ -22,4 +22,3 @@ By default, the type of Kubernetes service used for Telemetry-Core, Telemetry-Sh
		- All the services must be exposed over `HTTPS`.
		- The `Core` service could also be exposed using the `Frontend` Nginx service. The Nginx configuration should be tweaked for this purpose.
		- Consider setting `.Values.envVars.frontend.SUBSTRATE_TELEMETRY_URL` variable otherwise the web clients wouldn't be able to find the `Core` service address.