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

tls related issues #60

Open
gene-redpanda opened this issue Oct 26, 2023 · 0 comments
Open

tls related issues #60

gene-redpanda opened this issue Oct 26, 2023 · 0 comments

Comments

@gene-redpanda
Copy link
Contributor

Broker role still uses tls flag rather than enable_tls in redpanda_broker/vars/main.yaml in

---
custom_config_templates:
  - template: configs/defaults.j2
  - template: configs/tls.j2
    condition: "{{ tls | default(False) | bool }}"
  - template: configs/tiered_storage.j2
    condition: "{{ tiered_storage_bucket_name is defined | default(False) | bool }}"
console_config_templates:
  - template: console/defaults.j2

This causes substantial confusion. Fixing it will require a docs pass.

We should strongly consider breaking up enable_tls into enabling tls for each endpoint individually (while retaining the global flag). So for example enable_tls_kafka_api and enable_tls_schema_registry as it makes a large difference to end users who may want to only secure one or two endpoints rather than all of them. Cert passthrough should also be broken up while still retaining the global variables to set all of them at once.

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

No branches or pull requests

1 participant