Skip to content
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.

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

x509: certificate signed by unknown authority #3

Open
mrethers opened this issue Sep 21, 2022 · 0 comments
Open

x509: certificate signed by unknown authority #3

mrethers opened this issue Sep 21, 2022 · 0 comments

Comments

@mrethers
Copy link

mrethers commented Sep 21, 2022

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)

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. 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant