-
Notifications
You must be signed in to change notification settings - Fork 95
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add test and example showing how to update alloy clustering to work w…
…ithin istio service mesh Signed-off-by: Pete Wall <[email protected]>
- Loading branch information
Showing
14 changed files
with
7,839 additions
and
5 deletions.
There are no files selected for viewing
41 changes: 41 additions & 0 deletions
41
charts/k8s-monitoring/docs/examples/istio-service-mesh/README.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
<!-- | ||
(NOTE: Do not edit README.md directly. It is a generated file!) | ||
( To make changes, please modify values.yaml or description.txt and run `make examples`) | ||
--> | ||
# Istio Service Mesh example | ||
|
||
This example shows how to ensure that Alloy clustering when Istio Service Mesh is enabled and has deployed the Istio | ||
sidecar to the Alloy pods. This change is necessary because the Alloy cluster's headless Service port name | ||
[will not work](https://istio.io/latest/docs/ops/common-problems/network-issues/#503-error-while-accessing-headless-services) | ||
if it keeps its default port name of `http`. | ||
|
||
## Values | ||
|
||
```yaml | ||
--- | ||
cluster: | ||
name: istio-service-mesh-example | ||
|
||
destinations: | ||
- name: localPrometheus | ||
type: prometheus | ||
url: http://prometheus-server.prometheus.svc:9090/api/v1/write | ||
|
||
annotationAutodiscovery: | ||
enabled: true | ||
annotations: | ||
scrape: prometheus.io/scrape | ||
metricsPath: prometheus.io/path | ||
metricsPortNumber: prometheus.io/port | ||
|
||
clusterMetrics: | ||
enabled: true | ||
|
||
alloy-metrics: | ||
enabled: true | ||
alloy: | ||
clustering: | ||
portName: tcp | ||
controller: | ||
replicas: 2 | ||
``` |
Oops, something went wrong.
4aac1c8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@petewall [CRITICAL_RISK] Hi, we noticed you made a commit in GitHub that may contain sensitive information (details below). Please double check if you intended to include or share this sensitive information in the issue.
Note that it may have already been addressed automatically by an administrator.
What types of sensitive information were detected?
Password with Exclusions
What was the context?
When did this happen?
Mon, 13 Jan 2025 at 16:50:37 UTC
Where did this happen?
Repository: k8s-monitoring-helm
File Path: charts/k8s-monitoring/tests/integration/istio-service-mesh/.rendered/output.yaml