GCP Workload Identity

The KEDA Documentation

Deploying KEDA
FAQ
Migration Guide
Troubleshooting

KEDA Concepts

Scaling Deployments, StatefulSets & Custom Resources
Scaling Jobs
Authentication
External Scalers
Troubleshooting

Operate

Cluster
Events
KEDA Metrics Server
Integrate with Prometheus

Scalers

ActiveMQ Artemis
Apache Kafka
AWS CloudWatch
AWS Kinesis Stream
AWS SQS Queue
Azure Blob Storage
Azure Event Hubs
Azure Log Analytics
Azure Monitor
Azure Pipelines
Azure Service Bus
Azure Storage Queue
Cassandra
CPU
Cron
Elasticsearch
External
External Push
Google Cloud Platform Pub/Sub
Graphite
Huawei Cloudeye
IBM MQ
InfluxDB
Kubernetes Workload
Liiklus Topic
Memory
Metrics API
MongoDB
MSSQL
MySQL
NATS Streaming
OpenStack Metric
OpenStack Swift
PostgreSQL
Prometheus
RabbitMQ Queue
Redis Lists
Redis Lists (supports Redis Cluster)
Redis Lists (supports Redis Sentinel)
Redis Streams
Redis Streams (supports Redis Cluster)
Redis Streams (supports Redis Sentinel)
Selenium Grid Scaler
Solace PubSub+ Event Broker

Authentication Providers

Azure Pod Identity
EKS Pod Identity Webhook for AWS
Environment variable
GCP Workload Identity
Hashicorp Vault secret
Kiam Pod Identity for AWS
Secret

GCP Workload Identity ^{Click here for latest}

Suggest a change

GCP Workload Identity allows workloads in your GKE clusters to impersonate Identity and Access Management (IAM) service accounts to access Google Cloud services.

You can tell KEDA to use GCP Workload Identity via podIdentity.provider.

podIdentity:
  provider: gcp # Optional. Default: none