promenade/doc/source/configuration/genesis.rst

Genesis

Specific configuration for the genesis process. This document is a strict superset of the combination of kubernetes-node and host-system, so only differences are discussed here.

Sample Document

Here is a complete sample document:

schema: promenade/Genesis/v1
metadata:
  schema: metadata/Document/v1
  name: genesis
  layeringDefinition:
    abstract: false
    layer: site
data:
  hostname: n0
  ip: 192.168.77.10
  armada:
    target_manifest: cluster-bootstrap
  labels:
    static:
      - calico-etcd=enabled
      - node-role.kubernetes.io/master=
    dynamic:
      - kubernetes-apiserver=enabled
      - kubernetes-controller-manager=enabled
      - kubernetes-etcd=enabled
      - kubernetes-scheduler=enabled
      - promenade-genesis=enabled
      - ucp-control-plane=enabled
  images:
    armada: quay.io/airshipit/armada:latest
    helm:
      tiller: gcr.io/kubernetes-helm/tiller:v2.10.0
    kubernetes:
      apiserver: gcr.io/google_containers/hyperkube-amd64:v1.10.2
      controller-manager: gcr.io/google_containers/hyperkube-amd64:v1.10.2
      etcd: quay.io/coreos/etcd:v3.0.17
      scheduler: gcr.io/google_containers/hyperkube-amd64:v1.10.2
  files:
    - path: /var/lib/anchor/calico-etcd-bootstrap
      content: ""
      mode: 0644

Armada

This section contains particular configuration options for bootstrapping with Armada. It currently only supports a single option: target_manifest, which specifies which armada/Manifest/v1 to be used during Genesis.

Bootstrapping Images

Bootstrapping images are specified in the top level key images:

armada: <Armada image for bootstrapping>
helm:
  tiller: <Tiller image for bootstrapping>
kubernetes:
  apiserver: <API server image for bootstrapping>
  controller-manager: <Controller Manager image for bootstrapping>
  etcd: <etcd image for bootstrapping>
  scheduler: <Scheduler image for bootstrapping>