Hi @Alfredo Neto,
I think your annotations might work if you move them from the IrisCluster to the Pod:
spec:
topology:
data:
podTemplate:
metadata:
annotations:
prometheus.io/scrape: "true"
prometheus.io/path: "/api/monitor/metrics"
prometheus.io/port: "52773"
Please let me know if that works for you.
-Steve
I wrote these several years ago - please do not code like this!
Quine 1:
s s=" s s= w $E(s,1,5),$C(34),s,$C(34),$E(s,6,*)" w $E(s,1,5),$C(34),s,$C(34),$E(s,6,*)
Quine 2:
s p="w $c(115,32,112,61,34)_p_$c(34,32,120,32,112)" x p
Certifications & Credly badges:
Steve has no Certifications & Credly badges yet.
Global Masters badges:
Steve has no Global Masters badges yet.
Followers:
Steve has no followers yet.
Following:
Steve has not followed anybody yet.
I'm not sure about this particular error, but some tips for using CPF merge that might apply:
1) "iris start" returns before IRIS is fully up (run "iris list" fast enough and you may see that the status hasn't yet reached "running"). To mitigate this you can block on the IRIS readiness script, something like:
2) You can avoid the timing issues above by having the merge carried out as part of "iris start" using environment variable ISC_CPF_MERGE_FILE, something like:
Note in all of the above examples, best practice is to provide the full path to the merge file.