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

redpanda.yaml redux proposal #4535

Closed
twmb opened this issue May 4, 2022 · 0 comments
Closed

redpanda.yaml redux proposal #4535

twmb opened this issue May 4, 2022 · 0 comments

Comments

@twmb
Copy link
Contributor

twmb commented May 4, 2022

redpanda.yaml is a bit confusing and has many use cases. We should propose a better long term format. This issue will be fleshed out more as a more comprehensive redux is proposed. For starters:

  • rpk configuration is separate and distinct from redpanda configuration, and these should be different files. It is surprising that rpk defaults to /etc/redpanda/redpanda.yaml if no other configuration is found.
  • If we separate rpk configuration into a separate file, we can collapse the entire rpk section up by one level. The same holds true for the redpanda configuration.
  • The way to define listeners is a bit confusing. The original format follows the Kafka format closely, but we can simplify the definitions to make things more understandable to everybody long term.
  • Anything "trustfile" should be removed, because trustfile is a Java concept, and the files are actually PEM.

This placeholder issue will be expanded as we plan this more. This issue will affect rpk and redpanda, and we will want to do it in a backwards compatible way, which will be difficult.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants