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
I'm passing the secret ca.crt reference in my triggerauth CR but I'm getting that x509 problem in the metric server logs. This is a AWS ROSA cluster with the default domain (self-signed cert)
kind: TriggerAuthentication
metadata:
name: thanos
namespace: sample-ns
spec:
secretTargetRef:
- key: token
name: keda-token
parameter: bearerToken
- key: ca.crt
name: keda-token
parameter: ca
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: echo-service-spring-boot
spec:
cooldownPeriod: 100
maxReplicaCount: 100
minReplicaCount: 2
pollingInterval: 30
scaleTargetRef:
apiVersion: apps.openshift.io/v1
kind: DeploymentConfig
name: echo-service-spring-boot
triggers:
- authenticationRef:
name: thanos
metadata:
metricName: http_requests_total
query: >-
sum(rate(http_server_requests_seconds_count{application="echo-service-spring-boot"}[1m]))
serverAddress: 'https://thanos-querier.openshift-monitoring.svc.cluster.local:9091'
threshold: '10'
type: prometheus`
I'm able to query from POSTMAN using the same bearer token, and the HTTPS route.
The text was updated successfully, but these errors were encountered:
Hi,
I'm passing the secret ca.crt reference in my triggerauth CR but I'm getting that x509 problem in the metric server logs. This is a AWS ROSA cluster with the default domain (self-signed cert)
The text was updated successfully, but these errors were encountered: