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

No matches for kind "ClusterTriggerAuthentication" if this CRD is referenced in extraObjects #513

Open
abdul-jabbar01 opened this issue Aug 28, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@abdul-jabbar01
Copy link

If I am referring ClusterTriggerAuthentication with extraObjects, it gives following error

Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ClusterTriggerAuthentication" in version "keda.sh/v1alpha1"

It works with following workaround:

  • Install KEDA without extraObjects
  • Then update extraObjects and then helm upgrade

But this is not the ideal workaround. It makes automation difficult (installing via pipelines)

Expected Behavior

It should first install CRDs and then run 99-extra-manifests.yaml for extraObjects

Actual Behavior

It is installing extraObjects first before installing CRDs

Steps to Reproduce the Problem

  1. Download KEDA chart 2.11.0 from here
  2. Update keda/values.yaml to include following
extraObjects:
  - apiVersion: v1
    kind: Secret
    metadata:
      name: keda-datadog-secrets
      namespace: keda
    type: Opaque
    data:
      apiKey: "xxxxxx"
      appKey: "xxxxxx"
      datadogSite: "xxxxxx"
  - apiVersion: keda.sh/v1alpha1
    kind: ClusterTriggerAuthentication
    metadata:
      name: keda-cluster-trigger-auth-datadog
    spec:
      secretTargetRef:
        - parameter: apiKey
          name: keda-datadog-secrets
          key: apiKey
        - parameter: appKey
          name: keda-datadog-secrets
          key: appKey
        - parameter: datadogSite
          name: keda-datadog-secrets
          key: datadogSite
  1. Then install keda with helm upgrade --install keda kedacore/keda -f values.yaml --namespace keda
  2. Then it should give above mentioned error.

Specifications

  • KEDA Version: 2.11.0
  • Kubernetes Version: 1.26.7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants