Answers: <p><a href="https://kubernetes.io/docs/getting-started-guides/centos/centos_manual_config/" rel="nofollow noreferrer">https://kubernetes.io/docs/getting-started-guides/centos/centos_manual_config/</a></p>
  
  <blockquote>
  <pre><code># Address range to use for services
  KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
  </code></pre>
  </blockquote>
  
Answers: CC BY-SA 3.0
Answers: 2017-11-12T14:25:16.453Z
Answers: 2017-11-12T14:25:16.453Z
Answers: 030
Body: <h1>Question</h1>
  
  <p>Where is the Kubernetes documentation regarding KUBE_SERVICE_ADDRESSES parameter of API server and Pod network configuration?</p>
  
  <h2>Background</h2>
  
  <p>KUBE_SERVICE_ADDRESSES parameter value needs to go hand-in-hand with CIDR configuration of the Pod network, because <code>KUBE_SERVICE_ADDRESSES</code> is
  "Address range to use for services" and I suppose <code>services</code> communicate in the Pod network.</p>
  
  <p>Trying to find out a Kubernetes document which explains it but looks no specific documentation. Please suggest if this is true and where is the documentation related.</p>
  
  <p><strong>/etc/kubernetes/apiserver</strong></p>
  
  <pre><code># The address on the local server to listen to.
  #KUBE_API_ADDRESS="--insecure-bind-address=127.0.0.1"
  KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
  
  # The port on the local server to listen on.
  # KUBE_API_PORT="--port=8080"
  
  # Port minions listen on
  # KUBELET_PORT="--kubelet-port=10250"
  
  # Comma separated list of nodes in the etcd cluster
  KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:2379"
  
  # Address range to use for services
  KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
  
  # default admission control policies
  KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota"
  </code></pre>
  
  <h2>Related sites</h2>
  
  <p><a href="https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#pod-network" rel="noreferrer">Using kubeadm to Create a Cluster (3/4) Installing a pod network</a> says specific CIDR needs to be specified to <code>kubeadm init</code> as a option <code>--pod-network-cidr</code>. </p>
  
  <p><a href="https://devops.profitbricks.com/tutorials/deploy-a-multi-node-kubernetes-cluster-on-centos-7/" rel="noreferrer">Deploy a Multi-node Kubernetes Cluster on CentOS 7</a>:</p>
  
  <blockquote>
    <p>Create a flannel-config.json file that will define the Flannel settings. The subnet specified in the Flannel settings should match that of the API server KUBE_SERVICE_ADDRESSES value. This is the subnet that the containers will use.</p>
  </blockquote>
  
Tags: <kubernetes><configuration>
Title: Kubernetes API Server KUBE_SERVICE_ADDRESSES parameter and Pod Network configuration
UserDisplayName: mon
ThreadText: # Kubernetes API Server KUBE_SERVICE_ADDRESSES parameter and Pod Network configuration
  
  (Asked by: username_0 on 2017-11-08)
  
  # Question
  
  Where is the Kubernetes documentation regarding KUBE\_SERVICE\_ADDRESSES parameter of API server and Pod network configuration?
  
  ## Background
  
  KUBE\_SERVICE\_ADDRESSES parameter value needs to go hand-in-hand with CIDR configuration of the Pod network, because `KUBE_SERVICE_ADDRESSES` is
  "Address range to use for services" and I suppose `services` communicate in the Pod network.
  
  Trying to find out a Kubernetes document which explains it but looks no specific documentation. Please suggest if this is true and where is the documentation related.
  
  **/etc/kubernetes/apiserver**
  
  ```
  # The address on the local server to listen to.
  #KUBE_API_ADDRESS="--insecure-bind-address=127.0.0.1"
  KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
  
  # The port on the local server to listen on.
  # KUBE_API_PORT="--port=8080"
  
  # Port minions listen on
  # KUBELET_PORT="--kubelet-port=10250"
  
  # Comma separated list of nodes in the etcd cluster
  KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:2379"
  
  # Address range to use for services
  KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
  
  # default admission control policies
  KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota"
  
  ```
  
  ## Related sites
  
  [Using kubeadm to Create a Cluster (3/4) Installing a pod network](https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#pod-network) says specific CIDR needs to be specified to `kubeadm init` as a option `--pod-network-cidr`.
  
  [Deploy a Multi-node Kubernetes Cluster on CentOS 7](https://devops.profitbricks.com/tutorials/deploy-a-multi-node-kubernetes-cluster-on-centos-7/):
  
  > Create a flannel-config.json file that will define the Flannel settings. The subnet specified in the Flannel settings should match that of the API server KUBE\_SERVICE\_ADDRESSES value. This is the subnet that the containers will use.
  
  **Tags:** kubernetes, configuration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-11-12. Score: 3
  
  <https://kubernetes.io/docs/getting-started-guides/centos/centos_manual_config/>
  
  > ```
  > # Address range to use for services
  > KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
  >
  > ```
  
  
  ---
  
  