Open JakeSCahill opened 1 year ago
@JakeSCahill are you creating users from a list or is there a secret named 'redpanda-superusers'?
There’s a Secret with the super user credentials
Tested this again. Can someone confirm if this config should be valid?
helm repo update
helm install redpanda redpanda/redpanda \
--version 5.9.0 \
--namespace jake \
--create-namespace \
--set external.domain=customredpandadomain.local \
--set statefulset.initContainers.setDataDirOwnership.enabled=true --set "auth.sasl.users[0].name=superuser" --set auth.sasl.enabled=true --set "auth.sasl.users[0].password=secretpassword" --set "auth.sasl.users[0].mechanism=SCRAM-SHA-512" --set listeners.kafka.authenticationMethod=mtls_identity --set listeners.kafka.tls.requireClientAuth=true
When I try to use the Kafka API, rpk seems not to have the correct certs:
kubectl exec redpanda-0 -n jake -- rpk topic create test -X user=superuser -X pass=secretpassword
Defaulted container "redpanda" out of: redpanda, config-watcher, tuning (init), set-datadir-ownership (init), redpanda-configurator (init)
unable to initialize kafka client: unable to read cert at "/etc/tls/certs/redpanda-client/tls.crt": open /etc/tls/certs/redpanda-client/tls.crt: no such file or directory
command terminated with exit code 1
And the Redpanda logs complain too:
INFO 2024-08-09 14:03:37,998 [shard 0:main] tx - [{kafka/_internal_connectors_offsets/11}] - rm_stm.cc:106 - Setting bootstrap committed offset to: 2
INFO 2024-08-09 14:03:37,998 [shard 0:main] raft - [group_id:13, {kafka/_internal_connectors_offsets/11}] vote_stm.cc:433 - became the leader term: 3
INFO 2024-08-09 14:03:38,000 [shard 0:main] raft - [group_id:44, {kafka/__consumer_offsets/11}] vote_stm.cc:433 - became the leader term: 4
INFO 2024-08-09 14:03:38,088 [shard 0:main] tx - [{kafka/_internal_connectors_offsets/9}] - rm_stm.cc:106 - Setting bootstrap committed offset to: 3
INFO 2024-08-09 14:03:38,088 [shard 0:main] tx - [{kafka/_internal_connectors_offsets/17}] - rm_stm.cc:106 - Setting bootstrap committed offset to: 2
WARN 2024-08-09 14:03:38,477 [shard 0:admi] request_auth - request_auth.cc:123 - Client auth failure: user '' not found
WARN 2024-08-09 14:03:38,480 [shard 0:admi] request_auth - request_auth.cc:123 - Client auth failure: user '' not found
WARN 2024-08-09 14:03:38,485 [shard 0:admi] request_auth - request_auth.cc:123 - Client auth failure: user '' not found
INFO 2024-08-09 14:03:38,491 [shard 0:main] cluster - health_monitor_backend.cc:424 - received node 1 health report, marking node as up
WARN 2024-08-09 14:03:38,492 [shard 0:main] cluster - metadata_dissemination_service.cc:436 - Error sending metadata update rpc::errc::exponential_backoff to 2
INFO 2024-08-09 14:03:38,492 [shard 0:main] cluster - partition_balancer_planner.cc:334 - node 2 is unresponsive, time since last status reply: 3042 ms
INFO 2024-08-09 14:03:38,492 [shard 0:main] cluster - partition_balancer_planner.cc:365 - node 2: no disk report
INFO 2024-08-09 14:03:38,724 [shard 0:main] cluster - members_manager.cc:411 - applying maintenance_mode_cmd, offset: 740, node id: 2, enabled: false
INFO 2024-08-09 14:03:38,724 [shard 0:main] cluster - members_table.cc:210 - marking node 2 not in maintenance state
redpanda configmap:
Name: redpanda
Namespace: jake
Labels: app.kubernetes.io/component=redpanda
app.kubernetes.io/instance=redpanda
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=redpanda
helm.sh/chart=redpanda-5.9.0
Annotations: meta.helm.sh/release-name: redpanda
meta.helm.sh/release-namespace: jake
Data
====
bootstrap.yaml:
----
audit_enabled: false
compacted_log_segment_size: 67108864
default_topic_replications: 3
enable_rack_awareness: false
enable_sasl: true
group_topic_partitions: 16
kafka_batch_max_bytes: 1048576
kafka_connection_rate_limit: 1000
kafka_enable_authorization: true
log_segment_size: 134217728
log_segment_size_max: 268435456
log_segment_size_min: 16777216
max_compacted_log_segment_size: 536870912
storage_min_free_bytes: 1073741824
superusers:
- superuser
topic_partitions_per_shard: 1000
redpanda.yaml:
----
config_file: /etc/redpanda/redpanda.yaml
pandaproxy:
pandaproxy_api:
- address: 0.0.0.0
authentication_method: http_basic
name: internal
port: 8082
- address: 0.0.0.0
authentication_method: http_basic
name: default
port: 8083
pandaproxy_api_tls:
- cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
name: internal
require_client_auth: false
truststore_file: /etc/tls/certs/default/ca.crt
- cert_file: /etc/tls/certs/external/tls.crt
enabled: true
key_file: /etc/tls/certs/external/tls.key
name: default
require_client_auth: false
truststore_file: /etc/tls/certs/external/ca.crt
pandaproxy_client:
broker_tls:
cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
require_client_auth: true
truststore_file: /etc/tls/certs/default/ca.crt
brokers:
- address: redpanda-0.redpanda.jake.svc.cluster.local.
port: 9093
- address: redpanda-1.redpanda.jake.svc.cluster.local.
port: 9093
- address: redpanda-2.redpanda.jake.svc.cluster.local.
port: 9093
redpanda:
admin:
- address: 0.0.0.0
name: internal
port: 9644
- address: 0.0.0.0
name: default
port: 9645
admin_api_tls:
- cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
name: internal
require_client_auth: false
truststore_file: /etc/tls/certs/default/ca.crt
- cert_file: /etc/tls/certs/external/tls.crt
enabled: true
key_file: /etc/tls/certs/external/tls.key
name: default
require_client_auth: false
truststore_file: /etc/tls/certs/external/ca.crt
audit_enabled: false
compacted_log_segment_size: 67108864
crash_loop_limit: 5
default_topic_replications: 3
empty_seed_starts_cluster: false
enable_sasl: true
group_topic_partitions: 16
kafka_api:
- address: 0.0.0.0
authentication_method: mtls_identity
name: internal
port: 9093
- address: 0.0.0.0
authentication_method: sasl
name: default
port: 9094
kafka_api_tls:
- cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
name: internal
require_client_auth: true
truststore_file: /etc/tls/certs/default/ca.crt
- cert_file: /etc/tls/certs/external/tls.crt
enabled: true
key_file: /etc/tls/certs/external/tls.key
name: default
require_client_auth: false
truststore_file: /etc/tls/certs/external/ca.crt
kafka_batch_max_bytes: 1048576
kafka_connection_rate_limit: 1000
kafka_enable_authorization: true
log_segment_size: 134217728
log_segment_size_max: 268435456
log_segment_size_min: 16777216
max_compacted_log_segment_size: 536870912
rpc_server:
address: 0.0.0.0
port: 33145
rpc_server_tls:
cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
require_client_auth: false
truststore_file: /etc/tls/certs/default/ca.crt
seed_servers:
- host:
address: redpanda-0.redpanda.jake.svc.cluster.local.
port: 33145
- host:
address: redpanda-1.redpanda.jake.svc.cluster.local.
port: 33145
- host:
address: redpanda-2.redpanda.jake.svc.cluster.local.
port: 33145
storage_min_free_bytes: 1073741824
superusers:
- superuser
topic_partitions_per_shard: 1000
rpk:
additional_start_flags:
- --default-log-level=info
- --memory=2048M
- --reserve-memory=205M
- --smp=1
admin_api:
addresses:
- redpanda-0.redpanda.jake.svc.cluster.local.:9644
- redpanda-1.redpanda.jake.svc.cluster.local.:9644
- redpanda-2.redpanda.jake.svc.cluster.local.:9644
tls:
truststore_file: /etc/tls/certs/default/ca.crt
enable_memory_locking: false
kafka_api:
brokers:
- redpanda-0.redpanda.jake.svc.cluster.local.:9093
- redpanda-1.redpanda.jake.svc.cluster.local.:9093
- redpanda-2.redpanda.jake.svc.cluster.local.:9093
tls:
cert_file: /etc/tls/certs/redpanda-client/tls.crt
key_file: /etc/tls/certs/redpanda-client/tls.key
truststore_file: /etc/tls/certs/default/ca.crt
overprovisioned: false
tune_aio_events: true
schema_registry:
schema_registry_api:
- address: 0.0.0.0
authentication_method: http_basic
name: internal
port: 8081
- address: 0.0.0.0
authentication_method: http_basic
name: default
port: 8084
schema_registry_api_tls:
- cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
name: internal
require_client_auth: false
truststore_file: /etc/tls/certs/default/ca.crt
- cert_file: /etc/tls/certs/external/tls.crt
enabled: true
key_file: /etc/tls/certs/external/tls.key
name: default
require_client_auth: false
truststore_file: /etc/tls/certs/external/ca.crt
schema_registry_client:
broker_tls:
cert_file: /etc/tls/certs/default/tls.crt
enabled: true
key_file: /etc/tls/certs/default/tls.key
require_client_auth: true
truststore_file: /etc/tls/certs/default/ca.crt
brokers:
- address: redpanda-0.redpanda.jake.svc.cluster.local.
port: 9093
- address: redpanda-1.redpanda.jake.svc.cluster.local.
port: 9093
- address: redpanda-2.redpanda.jake.svc.cluster.local.
port: 9093
BinaryData
====
What happened?
When you enable mTLS authentication in the chart, the Redpanda logs are flooded with errors, which suggest that users are not correctly created from the default self-signed certificates:
What did you expect to happen?
These errors should not appear.
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
Anything else we need to know?
No response
Which are the affected charts?
No response
Chart Version(s)
Cloud provider
JIRA Link: K8S-74