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

Keda apache-kafka scaler for MSK cluster can't connect using IAM / K8s AssumeRole #6409

Open
nkfirdigi opened this issue Dec 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@nkfirdigi
Copy link

nkfirdigi commented Dec 8, 2024

Report

Keda apache-kafka scaler for MSK cluster can't connect using IAM / K8s AssumeRole
Using keda-2.14.2
Using apache-kafka scaler connected to MSK cluster.
Secret definition:

apiVersion: v1
kind: Secret
metadata:
  name: keda-kafka-secrets-msk
data:
  sasl: {{ "aws_msk_iam" | b64enc }} # or scram_sha512
  tls: {{ "enable" | b64enc }}
  awsRoleArn: {{ "arn:aws:iam::<....>:role/KubernetesServiceAccount_keda" | b64enc }}
  awsRegion: {{ "eu-west-1" | b64enc }}

Expected Behavior

Expecting the AWS client to use k8s assume role IAM to access MSK cluster with no need to specify access key and secret.

Actual Behavior

ScaleObject error: requires to define access key and secret

KEDAScalerFailed
error parsing kafka metadata: awsAccessKeyID not found

Steps to Reproduce the Problem

  1. define apache-kafka
  2. define sasl of type "aws_msk_iam"
  3. define tls: "enabled"

Logs from KEDA operator

KEDA Version

2.14.1

Kubernetes Version

1.29

Platform

Amazon Web Services

Scaler Details

apache-kafka

Anything else?

No response

@nkfirdigi nkfirdigi added the bug Something isn't working label Dec 8, 2024
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
Status: To Triage
Development

No branches or pull requests

1 participant