# Scale a service with sidekicks

**URL:** <https://forums.suse.com/t/scale-a-service-with-sidekicks/2105>\
**Category:** Rancher 1.x\
**Created:** [March 20, 2016, 4:54pm UTC](https://forums.suse.com/t/scale-a-service-with-sidekicks/2105 "2016-03-20T16:54:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nlhkh](https://avatars.discourse-cdn.com/v4/letter/n/5fc32e/32.png) [@nlhkh](https://forums.suse.com/u/nlhkh)\
**Post date:** [March 20, 2016, 4:54pm UTC](https://forums.suse.com/t/scale-a-service-with-sidekicks/2105/1 "2016-03-20T16:54:59Z")

</div>

Suppose I have service A with sidekick B.

A is suppose to consume the http service from sidekick B by looking up B by dns name “B”.

Now, when I scale up this service to 2, using “B” to lookup sidekick B will result in 2 different IP addresses.

Is there a way to have service A to only resolve the IP to its sidekicks?

---

<div class="post-metadata">

**Author:** ![alena](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alena/32/50_2.png) [@alena](https://forums.suse.com/u/alena)\
**Post date:** [March 22, 2016, 9:10pm UTC](https://forums.suse.com/t/scale-a-service-with-sidekicks/2105/2 "2016-03-22T21:10:36Z")

</div>

@nlhkh you would have to use rancher-metadata to get information about your sidekick deployed on the same host. I’ve put more description in the comment to this post: [Sidekick how detect primary service (container)?](http://forums.suse.com/t/sidekick-how-detect-primary-service-container/1992)

hope it helps