Skip to content

[GH#10755]: Stop telling operator users to create a Typha metrics service #2899

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
caseydavenport wants to merge 2 commits into
base: main
Choose a base branch
from
+65 −95
Open

[GH#10755]: Stop telling operator users to create a Typha metrics service #2899

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0500cc8
Stop telling operator users to create a Typha metrics service
caseydavenport Aug 3, 2026
9b87583
Verify the Typha metrics service by name
caseydavenport Aug 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 12 additions & 19 deletions calico/operations/monitor/monitor-component-metrics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,21 +248,18 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `typhaMetricsPort`, the operator automatically creates a service that exposes these metrics. You do not need to create one yourself.

You can use the following command to verify it.

```bash
kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
name: typha-metrics-svc
namespace: calico-system
spec:
clusterIP: None
selector:
k8s-app: calico-typha
ports:
- port: 9093
targetPort: 9093
EOF
kubectl get svc -n calico-system
Comment thread
caseydavenport marked this conversation as resolved.
Outdated
```

You should see a result similar to:

```bash
calico-typha-metrics ClusterIP 10.43.164.10 <none> 9093/TCP 39d
```

</TabItem>
Expand Down Expand Up @@ -491,12 +488,9 @@ data:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_service_name]
regex: typha-metrics-svc
regex: calico-typha-metrics
replacement: $1
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_name]
regex: calico-typha
action: drop
- job_name: 'kube_controllers_metrics'
scrape_interval: 5s
scheme: http
Expand Down Expand Up @@ -656,7 +650,6 @@ First remove the services by executing the following command:

```bash
kubectl delete service felix-metrics-svc -n calico-system
kubectl delete service typha-metrics-svc -n calico-system
```

If running $[prodnameWindows], also clean up the Windows nodes service:
Expand Down
31 changes: 12 additions & 19 deletions ...co_versioned_docs/version-3.29/operations/monitor/monitor-component-metrics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,21 +248,18 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `typhaMetricsPort`, the operator automatically creates a service that exposes these metrics. You do not need to create one yourself.

You can use the following command to verify it.

```bash
kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
name: typha-metrics-svc
namespace: calico-system
spec:
clusterIP: None
selector:
k8s-app: calico-typha
ports:
- port: 9093
targetPort: 9093
EOF
kubectl get svc -n calico-system
Comment thread
caseydavenport marked this conversation as resolved.
Outdated
```

You should see a result similar to:

```bash
calico-typha-metrics ClusterIP 10.43.164.10 <none> 9093/TCP 39d
```

</TabItem>
Expand Down Expand Up @@ -491,12 +488,9 @@ data:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_service_name]
regex: typha-metrics-svc
regex: calico-typha-metrics
replacement: $1
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_name]
regex: calico-typha
action: drop
- job_name: 'kube_controllers_metrics'
scrape_interval: 5s
scheme: http
Expand Down Expand Up @@ -656,7 +650,6 @@ First remove the services by executing the following command:

```bash
kubectl delete service felix-metrics-svc -n calico-system
kubectl delete service typha-metrics-svc -n calico-system
```

If running $[prodnameWindows], also clean up the Windows nodes service:
Expand Down
31 changes: 12 additions & 19 deletions ...co_versioned_docs/version-3.30/operations/monitor/monitor-component-metrics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,21 +248,18 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `typhaMetricsPort`, the operator automatically creates a service that exposes these metrics. You do not need to create one yourself.

You can use the following command to verify it.

```bash
kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
name: typha-metrics-svc
namespace: calico-system
spec:
clusterIP: None
selector:
k8s-app: calico-typha
ports:
- port: 9093
targetPort: 9093
EOF
kubectl get svc -n calico-system
Comment thread
caseydavenport marked this conversation as resolved.
Outdated
```

You should see a result similar to:

```bash
calico-typha-metrics ClusterIP 10.43.164.10 <none> 9093/TCP 39d
```

</TabItem>
Expand Down Expand Up @@ -491,12 +488,9 @@ data:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_service_name]
regex: typha-metrics-svc
regex: calico-typha-metrics
replacement: $1
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_name]
regex: calico-typha
action: drop
- job_name: 'kube_controllers_metrics'
scrape_interval: 5s
scheme: http
Expand Down Expand Up @@ -656,7 +650,6 @@ First remove the services by executing the following command:

```bash
kubectl delete service felix-metrics-svc -n calico-system
kubectl delete service typha-metrics-svc -n calico-system
```

If running $[prodnameWindows], also clean up the Windows nodes service:
Expand Down
31 changes: 12 additions & 19 deletions ...co_versioned_docs/version-3.31/operations/monitor/monitor-component-metrics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,21 +248,18 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `typhaMetricsPort`, the operator automatically creates a service that exposes these metrics. You do not need to create one yourself.

You can use the following command to verify it.

```bash
kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
name: typha-metrics-svc
namespace: calico-system
spec:
clusterIP: None
selector:
k8s-app: calico-typha
ports:
- port: 9093
targetPort: 9093
EOF
kubectl get svc -n calico-system
Comment thread
caseydavenport marked this conversation as resolved.
Outdated
```

You should see a result similar to:

```bash
calico-typha-metrics ClusterIP 10.43.164.10 <none> 9093/TCP 39d
```

</TabItem>
Expand Down Expand Up @@ -491,12 +488,9 @@ data:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_service_name]
regex: typha-metrics-svc
regex: calico-typha-metrics
replacement: $1
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_name]
regex: calico-typha
action: drop
- job_name: 'kube_controllers_metrics'
scrape_interval: 5s
scheme: http
Expand Down Expand Up @@ -656,7 +650,6 @@ First remove the services by executing the following command:

```bash
kubectl delete service felix-metrics-svc -n calico-system
kubectl delete service typha-metrics-svc -n calico-system
```

If running $[prodnameWindows], also clean up the Windows nodes service:
Expand Down
31 changes: 12 additions & 19 deletions ...co_versioned_docs/version-3.32/operations/monitor/monitor-component-metrics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,21 +248,18 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `typhaMetricsPort`, the operator automatically creates a service that exposes these metrics. You do not need to create one yourself.

You can use the following command to verify it.

```bash
kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
name: typha-metrics-svc
namespace: calico-system
spec:
clusterIP: None
selector:
k8s-app: calico-typha
ports:
- port: 9093
targetPort: 9093
EOF
kubectl get svc -n calico-system
Comment thread
caseydavenport marked this conversation as resolved.
Outdated
```

You should see a result similar to:

```bash
calico-typha-metrics ClusterIP 10.43.164.10 <none> 9093/TCP 39d
```

</TabItem>
Expand Down Expand Up @@ -491,12 +488,9 @@ data:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_service_name]
regex: typha-metrics-svc
regex: calico-typha-metrics
replacement: $1
action: keep
- source_labels: [__meta_kubernetes_pod_container_port_name]
regex: calico-typha
action: drop
- job_name: 'kube_controllers_metrics'
scrape_interval: 5s
scheme: http
Expand Down Expand Up @@ -656,7 +650,6 @@ First remove the services by executing the following command:

```bash
kubectl delete service felix-metrics-svc -n calico-system
kubectl delete service typha-metrics-svc -n calico-system
```

If running $[prodnameWindows], also clean up the Windows nodes service:
Expand Down