-
Notifications
You must be signed in to change notification settings - Fork 112
Description
What happened?
Receiving a YAML validation error when deploying console chart v3.0.x with protobuf configuration:
{"level":"fatal","msg":"failed to load yaml config","error":"failed to validate YAML config (strict validation): decoding failed due to the following error(s):\n\n'serde.protobuf' has invalid keys: enabled, git, importPaths, mappings"}
The console fails to start, reporting that 'serde.protobuf' has invalid keys even though the configuration follows the documented structure changes in v3.0.
What did you expect to happen?
Expected the console pod to start successfully with the protobuf configuration placed in config.serde.protobuf as per the breaking changes documented in the v3.0 changelog.
https://docs.redpanda.com/current/upgrade/migrate/console-v3/
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
Apply the following values file to the console chart v3.0.x:
config:
kafka:
brokers:
- kafka-broker-1:9092
- kafka-broker-2:9092
sasl:
enabled: true
mechanism: PLAIN
tls:
enabled: true
serde:
protobuf:
enabled: true
git:
enabled: true
refreshInterval: 5m
repository:
url: https://github.com/example/protobufs.git
importPaths:
- protos/
mappings:
- topicName: example-topic
valueProtoType: example.MessageAnything else we need to know?
No response
Which are the affected charts?
No response
Chart Version(s)
v3.0.0
Cloud provider
All cloud providers
JIRA Link: K8S-593