TriggerAuthentication defines how a trigger can authenticate
4 top-level fields, 1 required · unchanged since Keda v2.0.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
TriggerAuthenticationSpec defines the various ways to authenticate
HashiCorpVault is used to authenticate using Hashicorp Vault
VaultAuthentication contains the list of Hashicorp Vault authentication methods
Credential defines the Hashicorp Vault credentials depending on the authentication method
AuthPodIdentity allows users to select the platform native identity mechanism
PodIdentityProvider contains the list of providers
Source: keda.sh_triggerauthentications.yaml
Changes to TriggerAuthentication (keda.sh/v1alpha1) in each Keda version, compared to the version before it.
TriggerAuthentication was first seen on this version of Keda
Released · View TriggerAuthentication in v2.0.0
No examples of TriggerAuthentication yet. Contribute one on GitHub.
kubespec.dev