-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
Couldn't find any clusters on your configuration file #184
Comments
Hi, Can you edit your issue with formatted yaml ? Thanks |
Hi, i changed it - it's my first issue sorry.. |
I've a better view now. There is a bug on helm that i corrected now : here is a minimal working examples : secrets: |
kafkahq:
connections:
cluster-name:
properties:
bootstrap.servers: "strimzi-kafka-control-kafka-bootstrap.cluster-name:9092"
connect:
url: "" no need to duplicated |
i still get the error |
can you connect on the pods and see if there is a file on |
yes, the file exists and has the configurations inside |
can you go on |
what am i looking for here?
|
Sorry' I'm mean http like |
oh no worries when i try to access it directly it doesn't even load anything, so i checked if the pod is ok
is there any network configuration i left out or something needed? |
really strange ... the kubectl logs don't give you any information ? |
super weird to me too.. everything seems fine other than that |
I don't think so ... The things I really need to debug your case is the files on /app/*.yml. Without the 2, I can't help you ... sorry |
if there's anything else tell me, thanks for helping out event from pod logs: curl output: (same as before) content of application-secrets.yml: (only yml file under /app)
Liveness probe failed: dial tcp x.x.x.x:8080: connect: connection refused
|
will other logs help? java log trace f.e?
|
Things is see : kafkahq:
cluster-name:
properties:
bootstrap.servers: "strimzi-kafka-control-kafka-bootstrap.cluster-name.svc.cluster.local:9092"
connect:
url: "http://x.x.x.x:9094" The curl {
"activeEnvironments": [
"dev"
],
"packages": [
"org.kafkahq"
],
"propertySources": [
{
"........................."
}
]
} I forgot this one is disabled by default, you need to add this to your configuration files :
Hope it can help |
Hi, thanks for the extra help
when i try the curl it still displays the same internal server error. |
I wrote the configuration file again and it worked. i think the problem was the double use of configuration and secrets that both required similar values. thanks for the help, @tchiotludo ! |
* fixed bug * urls in topic page are dynamic * urls in connect are dynamic * urls in node page are dynamic * url in schema page are dynamic * dropdown redirecting to error page when dropdown value is empty fixed in connect create * searchbar responsive again * search bar responsive in big screens
Hi, I'm trying to configure kafkahq for the first time
I am using helm to deploy it on kubernetes, but when i try to access it, i get the following error:
the kafka itself is working correctly and i only changed "cluster-name" from my original one,
when I deploy it, I get no errors. But when I try to login through 127.0.0.1:8080 i get the error message
my configuration file looks like this:
I'm not really sure why it has problem locating my cluster, and would love to get some insights:
Thanks in advance for any help :)
The text was updated successfully, but these errors were encountered: