-
Notifications
You must be signed in to change notification settings - Fork 573
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
rpk config set redpanda.advertised_kafka_api when using NAT #5498
Comments
Can you try adding
Please confirm that this solved your problem so we can close the issue. Also, in the upcoming v22.2 we will improve the error message to:
And we have a follow-up issue to let the users set a single value in a slice: #5264 |
The above will be possible in v22.2.1 |
Thanks! Wrapping the yaml inside '[]' helps. Should the Ansible script be updated to also use this syntax? Strangely, for
|
The advertised_rpc_api is actually a single element and not a list of hosts to advertise: redpanda/src/go/rpk/pkg/config/schema.go Line 61 in 5b0b0eb
trying to set a single element with an array will continue to fail, I'm not sure we should modify that |
Version & Environment
Redpanda version: (use
rpk version
):What went wrong?
While setting up a multi data centre cluster under AWS, ran into an issue of joining one region to the other. If the
advertised_kafka_api
is left empty the cluster doesn't join because https://github.com/redpanda-data/deployment-automation/tree/main/aws uses the default VPC which means both regions have the 172.31.0.0/16 CIDR space and cannot communicate. Hence need to communicate with one region over public IP:Setting the public IP causes an error like:
What should have happened instead?
The IP possibly should be allowed, if the configuration file is edited by hand to add this IP, cluster is able to start up and communicate.
How to reproduce the issue?
Set the
advertised_kafka_api
to an IP that doesn't exist on the server locally.The text was updated successfully, but these errors were encountered: