-
Notifications
You must be signed in to change notification settings - Fork 50
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
Observed a panic "index out of range" on first event. #17
Comments
Not sure if it matters but this stopped when i added either the label to the service or But still not seeing services being added. |
@webbrandon thanks for created the issue. I'll take a look at it as soon as I found some spare time. |
I am trying to get down how to configure it to listen for new service pools and can't seem to get things working. I just updated my configs to run I also tried running several instances side by side with different configs and that "seemed" to have stopped all event watching across each instance. |
Indeed, with your configuration, I can reproduce your issue. @webbrandon let's take a look at the first post. There are a few mistakes in configuration. First off, Second off, in such configuration also When you fix your configuration everything should be fine. |
Problem
It seems on the first event emitted when Kubernetes is adding or removing (could be pods, service, deployment configs, not sure yet) when used as a in-cluster Replicaset is crashing
kube-consul-register
.Stack Trace:
Environment
Kubernetes v1.7.4
Consul 1.0.3
kube-consul-register v0.1.6
My Configurations
kube-consul-register
configurations.configmap:
replicaset:
Sample application configurations.
deployment:
service:
The text was updated successfully, but these errors were encountered: