Skip to content

Commit

Permalink
Add test and example showing how to update alloy clustering to work w…
Browse files Browse the repository at this point in the history
…ithin istio service mesh

Signed-off-by: Pete Wall <[email protected]>
  • Loading branch information
petewall committed Jan 13, 2025
1 parent ed27059 commit 4aac1c8
Show file tree
Hide file tree
Showing 14 changed files with 7,839 additions and 5 deletions.
41 changes: 41 additions & 0 deletions charts/k8s-monitoring/docs/examples/istio-service-mesh/README.md
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
```
Loading

1 comment on commit 4aac1c8

@nightfall-for-github
Copy link

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?

9raQ==" password: "bG**************" --- # Source: k8s-m
VzZXI=" password: "cH******************…" --- # Source: k8s-m

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

Please sign in to comment.