anchor.diff:  |Option |Description
   
   |`*servingInfo*`
  -|Describes how to start serving.
  +a|Describes how to start serving. For example:
  +----
  +servingInfo:
  +  bindAddress: 0.0.0.0:8443
  +  bindNetwork: tcp4
  +  certFile: master.server.crt
  +  clientCA: ca.crt
  +  keyFile: master.server.key
  +  maxRequestsInFlight: 500
  +  requestTimeoutSeconds: 3600
  +----
   
   |`*corsAllowedOrigins*`
   |Specifies the host name to use to access the API server from a web application.
  
positive.code: |Contains information about how to connect to kubelet's KubernetesMasterConfig. If present, then start the kubernetes master in this process.
  
  |`*etcdConfig*`
  |If present, then start etcd in this process.
  
  |`*oauthConfig*`
  |If present, then start the /oauth endpoint in this process.
  
  |`*assetConfig*`
  |If present, then start the asset server in this process.
  
  |`*dnsConfig*`
  |If present, then start the DNS server in this process.
  
  a|`*serviceAccountConfig*`
  a|Holds options related to service accounts:
  
negative.code: ----
  
  You have now manually modified the master and node configuration files,
  but this is just a simple use case.
  From here you can see all the
  link:../admin_solutions/master_node_config.html#master-config-options[master] and
  link:../admin_solutions/master_node_config.html#node-config-options[node configuration] options, and further customize your own cluster by making further modifications.
  
  == Configuration Options 
  
  === Master Configuration File Options
  
  The table below contains the options available for configuring your
  {product-title} *_master-config.yaml_* file. Use this table as a reference, and
  then follow the section on
  link:../admin_solutions/master_node_config.html#master-node-config-manual[making manual configuration changes]
  and substitute in whatever values you want to change.
  
  [[master-config-options]]
  [cols="1,4"]
  