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

Provide CloudEvents around the management of (Cluster)TriggerAuthentication resources #3524

Open
6 tasks
tomkerkhove opened this issue Aug 9, 2022 · 0 comments
Labels
cloudevents All events related to CloudEvents to extend KEDA extensibility All issues related to extensibility of KEDA feature All issues for new features that have been committed to operations

Comments

@tomkerkhove
Copy link
Member

tomkerkhove commented Aug 9, 2022

Proposal

Event Types

  • keda.authentication.triggerauthentication.created.v1
  • keda.authentication.triggerauthentication.updated.v1
  • keda.authentication.triggerauthentication.removed.v1
  • keda.authentication.clustertriggerauthentication.created.v1
  • keda.authentication.clustertriggerauthentication.updated.v1
  • keda.authentication.clustertriggerauthentication.removed.v1

Events scoped to the cluster should not have the “namespace” segment in the subject.

Payload:

{
    "specversion" : "1.0",
    "type" : "keda.authentication.triggerauthentication.created.v1",
    "subject" : "/{kubernetes-cluster-name}/{namespace, only if it’s namespaces}/{cluster-trigger-authentication or trigger-authentication}/{resource-name}/",
    "time" : "2018-04-05T17:31:00Z",
    "datacontenttype" : "application/json",
    "data" : {
      "podIdentity": {
         "provider": "azure"
      },
      "secretTargetRef": [
        {
          "parameter": "<parameter-name>",
          "name": "<secret-name>",
          "key": "<secret-key-name>"
        }
      ],
      "environmentVariables": [
        {
          "parameter": "<parameter-name>",
          "name": "<environment-variable-name>",
          "containerName": "<container-name>"
        }
      ],
      "hashiCorpVault": {
         // Omitted, follow current configuration spec
      },
      "azureKeyVault": {
         "vault": {
           "vaultUri": "<URL>",
           "resourceUrl": "<URL>",
           "cloud": {
             "type": "AzurePublicCloud"
           }
         },
         "activeDirectory": {
           "client": {
             "id": "<id>",
             "secretKeyRef": {
               "name": "<secret-name>"
               "key": "<secret-key-name>"
             }
           }
           "endpoint": "<ad-endpoint-url>",
         }
      }
   }
}

Use-Case

Allow end-users to react to changes to their (Cluster)TriggerAuthentication resource.

Anything else?

Relates to #479

@tomkerkhove tomkerkhove added needs-discussion feature-request All issues for new features that have not been committed to labels Aug 9, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Aug 9, 2022
@tomkerkhove tomkerkhove added extensibility All issues related to extensibility of KEDA feature All issues for new features that have been committed to operations cloudevents All events related to CloudEvents to extend KEDA and removed needs-discussion feature-request All issues for new features that have not been committed to labels Aug 9, 2022
@tomkerkhove tomkerkhove moved this from Proposed to To Do in Roadmap - KEDA Core Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloudevents All events related to CloudEvents to extend KEDA extensibility All issues related to extensibility of KEDA feature All issues for new features that have been committed to operations
Projects
Status: To Do
Development

No branches or pull requests

1 participant