Open webbrandon opened 6 years ago
Not sure if it matters but this stopped when i added either the label to the service or matchLabel
to deployment.
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 register_mode
as single andregister_source
to pods and got this error again.
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, register_source: "endpoints"
should be register_source: "endpoint"
(without "s"). When you use endpoint as a source you should add the annotation to endpoint (kubectl annotate endpoints my-nginx consul.register/enabled=true
).
Second off, in such configuration also pod_label_selector: "stage"
and the annotation consul.regiser/enabled: "true"
in deployment template is useless.
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: