anchor.diff:  |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.
  +a|If present, then etcd starts based on the defined parameters. For example:
  +----
  +etcdConfig:
  +  address: master.ose32.example.com:4001
  +  peerAddress: master.ose32.example.com:7001
  +  peerServingInfo:
  +    bindAddress: 0.0.0.0:7001
  +    certFile: etcd.server.crt
  +    clientCA: ca.crt
  +    keyFile: etcd.server.key
  +  servingInfo:
  +    bindAddress: 0.0.0.0:4001
  +    certFile: etcd.server.crt
  +    clientCA: ca.crt
  +    keyFile: etcd.server.key
  +  storageDirectory: /var/lib/origin/openshift.local.etcd
  +----
   
   |`*oauthConfig*`
  -|If present, then start the /oauth endpoint in this process.
  +a|If present, then the /oauth endpoint starts based on the defined parameters. For example:
  +----
  +oauthConfig:
  +  assetPublicURL: https://master.ose32.example.com:8443/console/
  +  grantConfig:
  +    method: auto
  +  identityProviders:
  +  - challenge: true
  +    login: true
  +    mappingMethod: claim
  +    name: htpasswd_all
  +    provider:
  +      apiVersion: v1
  +      kind: HTPasswdPasswordIdentityProvider
  +      file: /etc/origin/openshift-passwd
  +  masterCA: ca.crt
  +  masterPublicURL: https://master.ose32.example.com:8443
  +  masterURL: https://master.ose32.example.com:8443
  +  sessionConfig:
  +    sessionMaxAgeSeconds: 3600
  +    sessionName: ssn
  +    sessionSecretsFile: /etc/origin/master/session-secrets.yaml
  +  tokenConfig:
  +    accessTokenMaxAgeSeconds: 86400
  +    authorizeTokenMaxAgeSeconds: 500
  +----
   
   |`*assetConfig*`
  -|If present, then start the asset server in this process.
  +a|If present, then the asset server starts based on the defined parameters. For example:
  +----
  +assetConfig:
  +  logoutURL: ""
  +  masterPublicURL: https://master.ose32.example.com:8443
  +  publicURL: https://master.ose32.example.com:8443/console/
  +  servingInfo:
  +    bindAddress: 0.0.0.0:8443
  +    bindNetwork: tcp4
  +    certFile: master.server.crt
  +    clientCA: ""
  +    keyFile: master.server.key
  +    maxRequestsInFlight: 0
  +    requestTimeoutSeconds: 0
  +----
   
   |`*dnsConfig*`
  -|If present, then start the DNS server in this process.
  +a|If present, then start the DNS server based on the defined parameters. For example:
  +----
  +dnsConfig:
  +  bindAddress: 0.0.0.0:8053
  +  bindNetwork: tcp4
  +----
   
   a|`*serviceAccountConfig*`
   a|Holds options related to service accounts:
  
positive.code: |Option |Description
  
  |`*servingInfo*`
  |Describes how to start serving.
  
  |`*corsAllowedOrigins*`
  |Specifies the host name to use to access the API server from a web application.
  
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"]
  