We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Keel: 0.16.1 WEBHOOK_URL configured to reach an internal service: http://myservice.namespace.svc.cluster.local:5000
http://myservice.namespace.svc.cluster.local:5000
The logs reports failed to send the notification message with:
Could not dial broker: dial tcp: lookup myservice.namespace.svc.cluster.local device or resource busy
However, if I set the same webhook service as a sidecar along with keel, and WEBHOOK_URL=http://127.0.0.1:5000, it works like a charm.
WEBHOOK_URL=http://127.0.0.1:5000
Could it be possible the issue below is related? segmentio/kafka-go#285 golang/go#35067
The text was updated successfully, but these errors were encountered:
This is alpine issue. I found workaround. Add these to keel deployment:
command: ['/bin/sh', '-c', 'apk add bind-tools && /bin/keel'] env: - name: GODEBUG value: netdns=go dnsConfig: options: - name: ndots value: '2'
bind-tools: stackoverflow
Sorry, something went wrong.
Closing for inactivity. Do not use the product anymore to follow up on it.
No branches or pull requests
Keel: 0.16.1
WEBHOOK_URL configured to reach an internal service:
http://myservice.namespace.svc.cluster.local:5000
The logs reports failed to send the notification message with:
However, if I set the same webhook service as a sidecar along with keel, and
WEBHOOK_URL=http://127.0.0.1:5000
, it works like a charm.Could it be possible the issue below is related?
segmentio/kafka-go#285
golang/go#35067
The text was updated successfully, but these errors were encountered: