-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Issue with Protobuf Files Configuration when using Kubernetes ConfigMap #4412
Comments
Hello there kehao95! 👋 Thank you and congratulations 🎉 for opening your very first issue in this project! 💖 In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀 |
similar issue spring-projects/spring-boot#23232 Not sure, but maybe Files.walk with option FOLLOW_LINKS can resolve this issue. kafka-ui/kafka-ui-api/src/main/java/com/provectus/kafka/ui/serdes/builtin/ProtobufFileSerde.java Lines 399 to 415 in 53a6553
|
@kehao95 hey, as this repo is no longer maintained (see #4255) I'd be happy to help you out here: kafbat/kafka-ui#262 |
@Haarolean Thank you for your contribution and fix I'll try it out! I hope there will be a deprecation notice on this project though. |
Issue submitter TODO list
master
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
Hello,
I've encountered an issue with the Kafka-UI configuration when utilizing Protobuf files for serialization/deserialization in a Kubernetes environment.
The Protobuf files are mounted using a Kubernetes ConfigMap. However, Kubernetes creates hidden files and links (e.g., ..data, ..timestamp.file) in the mounted directory. These hidden files and links are inadvertently being processed by Kafka-UI, leading to errors related to multiple enums sharing the same constant due to the presence of duplicate Protobuf files.
Expected behavior
Kafka-UI should ignore hidden files and links created by Kubernetes when mounting ConfigMaps, or provide a mechanism to exclude specific files or patterns from being processed.
Your installation details
The configuration is specified as follows:
And I was mounting protobuf files using configmap (by ksutomization patch)
Steps to reproduce
Configure a Kafka cluster in Kafka-UI with Protobuf serialization/deserialization, specifying a directory mounted via Kubernetes ConfigMap for Protobuf files.
Observe the logs/errors in Kafka-UI related to duplicate enums or other Protobuf schema-related errors.
Screenshots
Logs
Additional context
Currently I'm using an init containers to copy the content over instead of mounting the configmap directly, which works for me.
The text was updated successfully, but these errors were encountered: