<p>I am using Kubernetes 1.0.3 where a master and 5 minion nodes deployed.
I have an Elasricsearch application that is deployed on 3 nodes using a replication controller and service is defined.
Now i have added a new minion node to the cluster and wanted to run the container elasticsearch on the new node.
I am scaling my replication controller to 4 so that based on the node label the elasticsearch container is deployed on new node.Below is my issue and please let me k ow if there is any solution ?</p>

<p>The cluster IP defined in the RC is wrong as it is not the same in service.yaml file.Now when I scale the RC new node is installed with the ES container pointing to the wrong Cluster IP due to which the new node is not joining the ES cluster.Is there any way that I can modify the cluster IP of deployed RC so that when I scale the RC the image is deployed on new node with the correct cluster IP ?</p>

<p>Since I am using old version I don't see kubectl edit command and I tried changing using kubectl patch command but the IP didn't change.</p>

<p>The problem is that I need to do this on a production cluster so I can't delete the existing pods but only option is to change the cluster IP of deployed RC and then scale so that it will take the new IP and image is started accordingly.</p>

<p>Please let me know if any way I can do this ?</p>

Kamesh
<p>Kubernetes creates that (virtual) ClusterIP for every service.<br>
Whatever you defined in your service definition (which you should have posted along with your question) is being ignored by Kubernetes, if I recall correctly.</p>

<p>I don't quite understand the issue with scaling, but basically, you want to point at the service name (resolved by Kubernetes's internal DNS) rather than the ClusterIP.<br>
E.g., <a href="http://myelasticsearchservice" rel="nofollow noreferrer">http://myelasticsearchservice</a> instead of <a href="http://1.2.3.4" rel="nofollow noreferrer">http://1.2.3.4</a></p>
