-
-
Notifications
You must be signed in to change notification settings - Fork 262
Open
Labels
status/feedback-requestedstatus/triage/completedAutomatic triage completedAutomatic triage completedstatus/triage/manualManual triage in progressManual triage in progresstype/bugSomething isn't workingSomething isn't working
Description
Issue submitter TODO list
- I've looked up my issue in FAQ
- I've searched for an already existing issues here
- I've tried running
main-labeled docker image and the issue still persists there - I'm running a supported version of the application which is listed here
Describe the bug (actual behavior)
Having studied all the available documentation, there is no information on how to properly deploy helm kafbat with dynamic configuration.
After trying many installation variations, it was not possible to save the configuration, each time I get the error 400 Bad Request Fields validation failure.
If I set the Kafka connections to static, everything works correctly.
The Kafka cluster is in the same namespace. and does not use any authorization system
Expected behavior
deploy kafbat in k8s, use the functionality of adding Kafka clusters via the UI
Your installation details
I've tried a lot of options с env dynamic configuration
1 ArgoCD Application
2 Helm
3 Deployment + configmap + service + volume
Steps to reproduce
Screenshots
Logs
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
status/feedback-requestedstatus/triage/completedAutomatic triage completedAutomatic triage completedstatus/triage/manualManual triage in progressManual triage in progresstype/bugSomething isn't workingSomething isn't working