-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
wip: redpanda serverless demo #7927
base: develop
Are you sure you want to change the base?
Conversation
cat >application_team/volumes/config/kafka.config <<EOF | ||
request.timeout.ms=30000 | ||
sasl.mechanism=SCRAM-SHA-256 | ||
security.protocol=SASL_SSL | ||
sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \ | ||
username="$username" \ | ||
password="$password"; | ||
|
||
producer.sasl.mechanism=SCRAM-SHA-256 | ||
producer.security.protocol=SASL_SSL | ||
producer.sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \ | ||
username="$username" \ | ||
password="$password"; | ||
|
||
consumer.sasl.mechanism=SCRAM-SHA-256 | ||
consumer.security.protocol=SASL_SSL | ||
consumer.sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \ | ||
username="$username" \ | ||
password="$password"; | ||
EOF |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the most useful difference between this and the docker version, for now.
If you sign up for a Redpanda account you can start a free serverless cluster. You'll also need to create a user, (I think) add an ACL that grants everything, and then in the API settings section you'll see that they support SASL_SSL and SCRAM-SHA-256/512 as the protocol and mechanism. These settings need to be passed into the kafka CLI tools and AIUI this is how you do that.
So the problem I currently have is I can't get the Redpanda Serverless cluster working. I've gone all the way back and tried to manually change the steps from our previous managed kafka guide. Unfortunately trying to start the consumer throws up the following error:
As the error states, this appears to be a problem with TLS/authentication. I've either got it misconfigured, or the node/relay is interfering with expectations the kafka console tools have about how that works. Any ideas? |
Thought I should break out the actual suggested causes in the error message incase it's something other than the one I suggested: (1) Authentication failed due to invalid credentials with brokers older than 1.0.0, |
No description provided.