Closed manno closed 3 years ago
This would make nats-1 with startup ordinal 0 (which happens after an upgrade) use the nats-0 service. That service selects the nats-1 pod.
It is consistent with the template rendering job instances address in https://github.com/cloudfoundry-incubator/quarks-operator/blob/master/pkg/bosh/manifest/instance_group.go#L150
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/176906742
The labels on this github issue will be updated when the story is started.
This would make nats-1 with startup ordinal 0 (which happens after an upgrade) use the nats-0 service. That service selects the nats-1 pod.
It is consistent with the template rendering job instances address in https://github.com/cloudfoundry-incubator/quarks-operator/blob/master/pkg/bosh/manifest/instance_group.go#L150