Skip to content

[GH#10755]: Clarify operator-managed Typha metrics service #2862

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
clcc2019 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[GH#10755]: Clarify operator-managed Typha metrics service #2862

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
23 changes: 7 additions & 16 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,13 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `spec.typhaMetricsPort`, the operator automatically creates the `calico-typha-metrics` service in the
`calico-system` namespace. You do not need to create another service.

Verify the operator-managed service:

```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 service calico-typha-metrics -n calico-system
```

</TabItem>
Expand Down Expand Up @@ -491,7 +483,7 @@ 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]
Expand Down Expand Up @@ -656,7 +648,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
23 changes: 7 additions & 16 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,13 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `spec.typhaMetricsPort`, the operator automatically creates the `calico-typha-metrics` service in the
`calico-system` namespace. You do not need to create another service.

Verify the operator-managed service:

```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 service calico-typha-metrics -n calico-system
```

</TabItem>
Expand Down Expand Up @@ -491,7 +483,7 @@ 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]
Expand Down Expand Up @@ -656,7 +648,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
23 changes: 7 additions & 16 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,13 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `spec.typhaMetricsPort`, the operator automatically creates the `calico-typha-metrics` service in the
`calico-system` namespace. You do not need to create another service.

Verify the operator-managed service:

```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 service calico-typha-metrics -n calico-system
```

</TabItem>
Expand Down Expand Up @@ -491,7 +483,7 @@ 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]
Expand Down Expand Up @@ -656,7 +648,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
23 changes: 7 additions & 16 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,13 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `spec.typhaMetricsPort`, the operator automatically creates the `calico-typha-metrics` service in the
`calico-system` namespace. You do not need to create another service.

Verify the operator-managed service:

```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 service calico-typha-metrics -n calico-system
```

</TabItem>
Expand Down Expand Up @@ -491,7 +483,7 @@ 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]
Expand Down Expand Up @@ -656,7 +648,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
23 changes: 7 additions & 16 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,13 @@ Typha uses **port 9091** TCP by default to publish its metrics. However, if $[pr
<Tabs>
<TabItem label="Operator" value="Operator-8">

When you set `spec.typhaMetricsPort`, the operator automatically creates the `calico-typha-metrics` service in the
`calico-system` namespace. You do not need to create another service.

Verify the operator-managed service:

```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 service calico-typha-metrics -n calico-system
```

</TabItem>
Expand Down Expand Up @@ -491,7 +483,7 @@ 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]
Expand Down Expand Up @@ -656,7 +648,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