Configuration examples for OIDC/security and metrics #1384
Conversation
MikeEdgar
force-pushed
the
readme-examples
branch
from
b58d1ac to
2f58374
Compare
| metricsSources: | ||
| # type=openshift-monitoring requires no other attributes, but truststore may be used if necessary | ||
| - name: my-ocp-prometheus | ||
| type: openshift-monitoring |
There was a problem hiding this comment.
will this always be openshift-monitoring?
There was a problem hiding this comment.
For this example, yes. But, the type value is an enumeration. It could be one of openshift-monitoring, standalone, or embedded.
There was a problem hiding this comment.
would they require additional attributes? Just thinking of what would be needed in the docs.
There was a problem hiding this comment.
The openshift-monitoring and embedded do not take any additional attributes. However, standalone requires a url and optionally takes authentication and a trustStore. The examples/console/console-standalone-prometheus.yaml includes them as well.
Signed-off-by: Michael Edgar <[email protected]>
Signed-off-by: Michael Edgar <[email protected]>
Co-authored-by: PaulRMellor <[email protected]>
Signed-off-by: Michael Edgar <[email protected]>
MikeEdgar
force-pushed
the
readme-examples
branch
from
9813bd9 to
d7a5b43
Compare
| metricsSources: | ||
| # type=openshift-monitoring requires no other attributes, but truststore may be used if necessary | ||
| - name: my-ocp-prometheus | ||
| type: openshift-monitoring |
There was a problem hiding this comment.
would they require additional attributes? Just thinking of what would be needed in the docs.
| # Using claims is only supported when OIDC security is enabled. | ||
| - claim: groups | ||
| include: | ||
| - team-a |
There was a problem hiding this comment.
Yep. Makes sense for me.
Co-authored-by: PaulRMellor <[email protected]>
Signed-off-by: Michael Edgar <[email protected]>
Co-authored-by: PaulRMellor <[email protected]>
|
No description provided.