Patrick O'Brien

I'm also seeing this issue, although I am getting no warnings in the debug logs. Here are all I get: ``` [2017-11-22 16:22:19] _collector_stub_0xa36d50__carbon.relays.ip-10-0-219-84.aggregators.metricsReceived 601624 1511367739 [2017-11-22 16:22:19] _collector_stub_0xa36d50__carbon.relays.ip-10-0-219-84.aggregators.metricsSent 0...

@grobian do you need anything from me to help test this?

Here's what we are using to manage the supernode process in systemd... /etc/systemd/system/dragonfly-supernode.service: ``` [Unit] Description = Dragonfly Supernode Documentation = https://github.com/dragonflyoss/Dragonfly After = network-online.target Wants = network-online.target [Service] Type...

We're currently rolling out our own dragonfly deployment. Our set up is slightly different as we are using an internal private registry rather than quay.io or docker.io, so YMMV with...

We do something similar to this with YAML anchors: ``` --- 'e': &CNAME_DEFAULTS ttl: 3600 type: CNAME value: email.example.net. 'email':

We are also seeing this issue when upgrading from 1.6.0 to 1.7.5

Does this PR need any help from outside contributors?

@harrypunk did you ever figure out a workaround for this?

I figured out a workaround. Here's our terraform snippet: ``` # fetch the sre role so we can authorize it against the cluster data "alicloud_ram_roles" "sre" { name_regex = "^sre$"...

We're also seeing this, but one of our clusters ended up staying in a broken state with the coredns service setting the UDP TargetPort to `dns-tcp`. Here's how we found...