Change:
Kubernetes version (use ): Environment: Cloud provider or hardware configuration: Vagrant OS (e.g. from /etc/os-release): CoreOS Kernel (e.g. ):Install tools: Vagrant & Others: What happened: What you expected to happen: Success How to reproduce it (as minimally and precisely as possible): Followed instructions at Tried to run Received: Anything else do we need to know: From googling, it seems several of the fields in the config are for when using OpenShift origin. But creating the replication controller is a prerequisite to launching OpenShift Origin. Chicken & egg problem.

Discussion:
}, "../examples/openshift-origin": { "openshift-origin-namespace": &api.Namespace{}, <del> "openshift-controller":       &api.ReplicationController{}, </del> <ins> "openshift-controller":       &extensions.Deployment{}, </ins> "openshift-service":          &api.Service{}, <del> "etcd-controller":            &api.ReplicationController{}, </del> <ins> "etcd-controller":            &extensions.Deployment{}, </ins> "etcd-service":               &api.Service{}, <del> "etcd-discovery-controller":  &api.ReplicationController{}, </del> <ins> "etcd-discovery-controller":  &extensions.Deployment{}, </ins> "etcd-discovery-service":     &api.Service{}, "secret":                     nil, },

<del> kind: ReplicationController apiVersion: v1 </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: name: etcd <del> creationTimestamp: </del> spec: strategy: type: Recreate <del> resources: {} triggers: - type: ConfigChange </del> replicas: 3 selector: <del> name: etcd </del> <ins> matchLabels: name: etcd </ins> template: metadata: <del> creationTimestamp: </del> labels: name: etcd spec:

<del> kind: ReplicationController apiVersion: v1 </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: name: etcd-discovery <del> creationTimestamp: </del> spec: strategy: type: Recreate <del> resources: {} triggers: - type: ConfigChange </del> replicas: 1 selector: <del> name: etcd-discovery </del> <ins> matchLabels: name: etcd-discovery </ins> template: metadata: <del> creationTimestamp: </del> labels: name: etcd-discovery spec:

resources: {} terminationMessagePath: "/dev/termination-log" imagePullPolicy: IfNotPresent <del> capabilities: {} </del> securityContext: capabilities: {} privileged: false

apiVersion: v1 metadata: name: etcd-discovery <del> creationTimestamp: </del> labels: name: etcd-discovery spec:

apiVersion: v1 metadata: name: etcd <del> creationTimestamp: </del> labels: name: etcd spec:

<del> apiVersion: v1 kind: ReplicationController </del> <ins> apiVersion: extensions/v1beta1 kind: Deployment </ins> metadata: labels: name: openshift name: openshift spec: replicas: 1 <del> selector: name: openshift </del> <ins> selector: matchLabels: name: openshift </ins> template: metadata: labels:

# TODO update to dns role once we have one. ${KUBECTL} --kubeconfig="${CERT_DIR}/admin.kubeconfig" create clusterrolebinding system:kube-dns --clusterrole=cluster-admin --serviceaccount=kube-system:default <del> # use kubectl to create kubedns rc and service </del> <ins> # use kubectl to create kubedns deployment and service </ins> ${KUBECTL} --kubeconfig="${CERT_DIR}/admin.kubeconfig" --namespace=kube-system create -f kubedns-deployment.yaml ${KUBECTL} --kubeconfig="${CERT_DIR}/admin.kubeconfig" --namespace=kube-system create -f kubedns-svc.yaml <del> echo "Kube-dns rc and service successfully deployed." </del> <ins> echo "Kube-dns deployment and service successfully deployed." </ins> rm  kubedns-deployment.yaml kubedns-svc.yaml fi }