anchor.diff:  type set to 'MustRunAs'.
   ====
   
  +
  +[[node-config-pod-and-node-config]]
  +=== Pod and Node Configuration
  +
  +.Pod and Node Configuration Parameters
  +[cols="3a,6a",options="header"]
  +|===
  +
  +| Parameter Name | Description
  +
  +|`*NodeConfig*`
  +|The fully specified configuration starting an {product-title} node.
  +
  +|`*NodeIP*`
  +|Node may have multiple IPs, so this specifies the IP to use for pod traffic
  +routing. If not specified, network parse/lookup on the *nodeName* is performed
  +and the first non-loopback address is used.
  +
  +|`*NodeName*`
  +|The value used to identify this particular node in the cluster. If possible,
  +this should be your fully qualified hostname. If you are describing a set of
  +static nodes to the master, this value must match one of the values in the list.
  +
  +|`*PodEvictionTimeout*`
  +|Controls grace period for deleting pods on failed nodes. It takes valid time
  +duration string. If empty, you get the default pod eviction timeout.
  +
  +|`*ProxyClientInfo*`
  +|Specifies the client cert/key to use when proxying to pods.
  +
  +|===
  +
  +
  +[[node-config-docker-config]]
  +=== Docker Configuration
  +
  +.Docker Configuration Parameters
  +[cols="3a,6a",options="header"]
  +|===
  +
  +| Parameter Name | Description
  +
  +|`*AllowDisabledDocker*`
  +|If true, the kubelet will ignore errors from Docker. This means that a node can
  +start on a machine that does not have docker started.
  +
  +|`*DockerConfig*`
  +|Holds Docker related configuration options
  +
  +|`*ExecHandlerName*`
  +|The handler to use for executing commands in Docker containers.
  +
  +|===
  +
   [[master-node-configuration-parallel-image-pulls-with-docker]]
   === Parallel Image Pulls with Docker 1.9+
   
  
positive.code: files can be created with the `--write-config` option and then used with the
  `--config` option.
  
  [[creating-new-configuration-files]]
  
  == Creating New Configuration Files
  For masters, the `openshift start` command accepts options that indicate that it
  should simply write the configuration files that it would have used, then
  terminate. For nodes, a configuration file can be written using the `oadm
  create-node-config` command. Creating new configuration files is useful to get a
  starting point for defining your configuration.
  
  The following commands write the relevant launch configuration file(s),
  certificate files, and any other necessary files to the specified
  `--write-config` or `--node-dir` directory.
  
  To create configuration files for an all-in-one server (a master and a node on
  the same host) in the specified directory:
  
  [options="nowrap"]
  ----
  $ openshift start --write-config=/openshift.local.config
  ----
  
  To create a xref:master-configuration-files[master configuration file] and
  other required files in the specified directory:
  
  [options="nowrap"]
  ----
  $ openshift start master --write-config=/openshift.local.config/master
  ----
  
  To create a xref:node-configuration-files[node configuration file] and other
  related files in the specified directory:
  
  [options="nowrap"]
  ----
  $ oadm create-node-config --node-dir=/openshift.local.config/node-<node_hostname> --node=<node_hostname> --hostnames=<hostname>,<ip_address>
  ----
  
  For the `--hostnames` option in the above command, use a comma-delimited list of
  every host name or IP address you want server certificates to be valid for. The
  above command also assumes that certificate files are located in an
  *_openshift.local.config/master/_* directory. If they are not, you can include
  options to specify their location. Run the command with the `-h` option to see
  details.
  
  [[launching-servers-using-configuration-files]]
  
  == Launching Servers Using Configuration Files
  Once you have modified the master and/or node configuration files to your
  specifications, you can use them when launching servers by specifying them as an
  argument. Keep in mind that if you specify a configuration file, none of the
  other command line options you pass are respected.
  
  To launch an all-in-one server using a master configuration and a node
  configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start --master-config=/openshift.local.config/master/master-config.yaml --node-config=/openshift.local.config/node-<node_hostname>/node-config.yaml
  ----
  
  To launch a master server using a master configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start master --config=/openshift.local.config/master/master-config.yaml
  ----
  
  To launch a node server using a node configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start node --config=/openshift.local.config/node-<node_hostname>/node-config.yaml
  ----
  
  [[master-configuration-files]]
  
  == Master Configuration Files
  The following *_master-config.yaml_* file is a sample master configuration
  file that was generated with the default values as of writing. You can
  xref:creating-new-configuration-files[create a new master configuration file]
  to see the valid options for your installed version of {product-title}.
  
  .Sample Master Configuration File
  ====
  [source,yaml]
  ----
  admissionConfig:
    pluginConfig: null
  apiLevels:
  - v1
  apiServerArguments:
    event-ttl: <1>
    - "15m"
  apiVersion: v1
  assetConfig:
    extensionDevelopment: false
    extensionScripts: null
    extensionStylesheets: null
    extensions: null
    loggingPublicURL: ""
    logoutURL: ""
    masterPublicURL: https://10.0.2.15:8443
    metricsPublicURL: ""
    publicURL: https://10.0.2.15:8443/console/
    servingInfo:
      bindAddress: 0.0.0.0:8443
      bindNetwork: tcp4
      certFile: master.server.crt
      clientCA: ""
      keyFile: master.server.key
      maxRequestsInFlight: 0
      namedCertificates: null
      requestTimeoutSeconds: 0
  controllerLeaseTTL: 0
  controllers: '*'
  corsAllowedOrigins:
  - 10.0.2.15:8443
  - 127.0.0.1
  - localhost
  disabledFeatures: null
  dnsConfig: allowRecursiveQueries: false
    bindAddress: 0.0.0.0:8053
    bindNetwork: tcp4
  etcdClientInfo:
    ca: ca.crt
    certFile: master.etcd-client.crt
    keyFile: master.etcd-client.key
    urls:
    - https://10.0.2.15:4001
  etcdConfig:
    address: 10.0.2.15:4001
    peerAddress: 10.0.2.15:7001
    peerServingInfo:
      bindAddress: 0.0.0.0:7001
      bindNetwork: tcp4
      certFile: etcd.server.crt
      clientCA: ca.crt
      keyFile: etcd.server.key
      namedCertificates: null
    servingInfo:
      bindAddress: 0.0.0.0:4001
      bindNetwork: tcp4
      certFile: etcd.server.crt
      clientCA: ca.crt
      keyFile: etcd.server.key
      namedCertificates: null
    storageDirectory: /root/openshift.local.etcd
  etcdStorageConfig:
    kubernetesStoragePrefix: kubernetes.io
    kubernetesStorageVersion: v1
    openShiftStoragePrefix: openshift.io
    openShiftStorageVersion: v1
  imageConfig:
    format: openshift/origin-${component}:${version}
    latest: false
  imagePolicyConfig:
    disableScheduledImport: false
    maxImagesBulkImportedPerRepository: 5
    maxScheduledImageImportsPerMinute: 60
    scheduledImageImportMinimumIntervalSeconds: 900
  kind: MasterConfig
  kubeletClientInfo:
    ca: ca.crt
    certFile: master.kubelet-client.crt
    keyFile: master.kubelet-client.key
    port: 10250
  kubernetesMasterConfig:
    admissionConfig:
      pluginConfig: null
    apiServerArguments: null
    controllerArguments: null
    disabledAPIGroupVersions: {}
    masterCount: 1
    masterIP: 10.0.2.15
    podEvictionTimeout: 5m
    proxyClientInfo:
      certFile: master.proxy-client.crt
      keyFile: master.proxy-client.key
    schedulerConfigFile: ""
    servicesNodePortRange: 30000-32767
    servicesSubnet: 172.30.0.0/16
  masterClients:
    externalKubernetesKubeConfig: ""
    openshiftLoopbackKubeConfig: openshift-master.kubeconfig
  masterPublicURL: https://10.0.2.15:8443
  networkConfig:
    clusterNetworkCIDR: 10.128.0.0/14
    hostSubnetLength: 9
    networkPluginName: redhat/openshift-ovs-subnet
    serviceNetworkCIDR: 172.30.0.0/16
  oauthConfig:
    alwaysShowProviderSelection: false
    assetPublicURL: https://10.0.2.15:8443/console/
    grantConfig:
      method: auto
    identityProviders:
    - challenge: true
      login: true
      mappingMethod: claim
      name: anypassword
      provider:
        apiVersion: v1
        kind: AllowAllPasswordIdentityProvider
    masterCA: ca.crt
    masterPublicURL: https://10.0.2.15:8443
    masterURL: https://10.0.2.15:8443
    sessionConfig:
      sessionMaxAgeSeconds: 300
      sessionName: ssn
      sessionSecretsFile: ""
    templates: null
    tokenConfig:
      accessTokenMaxAgeSeconds: 86400
      authorizeTokenMaxAgeSeconds: 300
  pauseControllers: false
  policyConfig:
    bootstrapPolicyFile: policy.json
    openshiftInfrastructureNamespace: openshift-infra
    openshiftSharedResourcesNamespace: openshift
  projectConfig:
    defaultNodeSelector: ""
    projectRequestMessage: ""
    projectRequestTemplate: ""
    securityAllocator:
      mcsAllocatorRange: s0:/2
      mcsLabelsPerProject: 5
      uidAllocatorRange: 1000000000-1999999999/10000
  routingConfig:
    subdomain: router.default.svc.cluster.local
  serviceAccountConfig:
    limitSecretReferences: false
    managedNames:
    - default
    - builder
    - deployer
    masterCA: ca.crt
    privateKeyFile: serviceaccounts.private.key
    publicKeyFiles:
    - serviceaccounts.public.key
  servingInfo:
    bindAddress: 0.0.0.0:8443
    bindNetwork: tcp4
    certFile: master.server.crt
    clientCA: ca.crt
    keyFile: master.server.key
    maxRequestsInFlight: 500
    namedCertificates: null
    requestTimeoutSeconds: 3600
  ----
  <1> Prevents memory overload by defining a lower limit (for example, 15m) for
  stored events. This prevents excessive memory growth that can be the result of
  etcd storing too many events. By default, this is set to two hours.
  ====
  
  [[node-configuration-files]]
  
  
negative.code: Encrypted data is only as secure as the decrypting key. Care should be taken
  to limit filesystem permissions and access to the key file.
  ====
  
  [[creating-new-configuration-files]]
  
  == Creating New Configuration Files
  For masters, the `openshift start` command accepts options that indicate that it
  should simply write the configuration files that it would have used, then
  terminate. For nodes, a configuration file can be written using the `oadm
  create-node-config` command. Creating new configuration files is useful to get a
  starting point for defining your configuration.
  
  The following commands write the relevant launch configuration file(s),
  certificate files, and any other necessary files to the specified
  `--write-config` or `--node-dir` directory.
  
  To create configuration files for an all-in-one server (a master and a node on
  the same host) in the specified directory:
  
  [options="nowrap"]
  ----
  $ openshift start --write-config=/openshift.local.config
  ----
  
  To create a xref:master-configuration-files[master configuration file] and
  other required files in the specified directory:
  
  [options="nowrap"]
  ----
  $ openshift start master --write-config=/openshift.local.config/master
  ----
  
  To create a xref:node-configuration-files[node configuration file] and other
  related files in the specified directory:
  
  [options="nowrap"]
  ----
  $ oadm create-node-config --node-dir=/openshift.local.config/node-<node_hostname> --node=<node_hostname> --hostnames=<hostname>,<ip_address>
  ----
  
  For the `--hostnames` option in the above command, use a comma-delimited list of
  every host name or IP address you want server certificates to be valid for. The
  above command also assumes that certificate files are located in an
  *_openshift.local.config/master/_* directory. If they are not, you can include
  options to specify their location. Run the command with the `-h` option to see
  details.
  
  [[launching-servers-using-configuration-files]]
  
  == Launching Servers Using Configuration Files
  Once you have modified the master and/or node configuration files to your
  specifications, you can use them when launching servers by specifying them as an
  argument. Keep in mind that if you specify a configuration file, none of the
  other command line options you pass are respected.
  
  To launch an all-in-one server using a master configuration and a node
  configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start --master-config=/openshift.local.config/master/master-config.yaml --node-config=/openshift.local.config/node-<node_hostname>/node-config.yaml
  ----
  
  To launch a master server using a master configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start master --config=/openshift.local.config/master/master-config.yaml
  ----
  
  To launch a node server using a node configuration file:
  
  [options="nowrap"]
  ----
  $ openshift start node --config=/openshift.local.config/node-<node_hostname>/node-config.yaml
  ----
  