You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Within container orchestration platforms you have to ensure that all interactions of the client and server are bound to the same Pod the initial request was sent to. This can be achieved by using a `sessionAffinity` which is set to ClientIP
121
+
122
+
Example service definition:
123
+
```yaml
124
+
kind: Service
125
+
apiVersion: v1
126
+
metadata:
127
+
labels:
128
+
app: prometheus-rsocket-proxy-server
129
+
# ...
130
+
spec:
131
+
ports:
132
+
- name: https
133
+
protocol: TCP
134
+
port: 8443
135
+
targetPort: https
136
+
- name: rsocket
137
+
protocol: TCP
138
+
port: 7001
139
+
targetPort: rsocket
140
+
selector:
141
+
app: prometheus-rsocket-proxy-server
142
+
type: ClusterIP
143
+
sessionAffinity: ClientIP
144
+
```
145
+
146
+
120
147
## Expected performance
121
148
122
149
A 3-pod deployment easily handles 1,000 connected application instances each serving 1,000 distinct time series with <1vCPU and <3Gi RAM total on GKE.
Copy file name to clipboardExpand all lines: starter-spring/src/main/java/io/micrometer/prometheus/rsocket/autoconfigure/PrometheusRSocketClientAutoConfiguration.java
Copy file name to clipboardExpand all lines: starter-spring/src/main/java/io/micrometer/prometheus/rsocket/autoconfigure/PrometheusRSocketClientProperties.java
0 commit comments