github.com/docker/compose-on-kubernetes@v0.5.0/docs/install-on-kind.md (about)

     1  # Install on Kind (Kubernetes in Docker)
     2  
     3  ## Pre-requisites
     4  - [Kind](https://kind.sigs.k8s.io/ 0.5 or later
     5  - To install etcd using these instructions, you must have [Helm](https://helm.sh) in your client environment.
     6  - [Download the Compose on Kubernetes installer](https://github.com/docker/compose-on-kubernetes/releases).
     7  - [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) availabe in path.
     8  
     9  ## Create compose namespace
    10  
    11  Create a Kind cluster with `kind create cluster`
    12  
    13  ## Populate Kubernetes Config
    14  
    15  Configure kubectl so it points to your freshly created Kind cluster
    16  `export KUBECONFIG="$(kind get kubeconfig-path)"`
    17  
    18  ## Deploy etcd
    19  
    20  Compose on Kubernetes requires an etcd instance (in addition to the kube-system etcd instance). Please follow [How to deploy etcd](./deploy-etcd.md).
    21  
    22  ## Deploy Compose on Kubernetes
    23  
    24  Run `./installer-[darwin|linux|windows.exe] -namespace=compose -etcd-servers=http://compose-etcd-client:2379`.
    25  
    26  ## Deploy a stack in the cluster
    27  
    28  By now you should be able to [Check that Compose on Kubernetes is installed](../README.md#check-that-compose-on-kubernetes-is-installed):
    29  
    30  ```bash
    31  $ kubectl api-versions | grep compose
    32  compose.docker.com/v1beta1
    33  compose.docker.com/v1beta2
    34  ```
    35  
    36  If the APIs are visible it should be possible to [Deploy a stack](../README.md#deploy-a-stack).
    37  
    38  If everything has worked the `web-published` service should be visible from `kubectl` e.g:
    39  
    40  ```
    41  $ kubectl get services
    42  NAME            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE
    43  db              ClusterIP      None             <none>        55555/TCP         3m31s
    44  kubernetes      ClusterIP      10.152.183.1     <none>        443/TCP           33m
    45  web             ClusterIP      None             <none>        55555/TCP         3m31s
    46  web-published   LoadBalancer   10.152.183.180   <pending>     33000:30218/TCP   3m31s
    47  words           ClusterIP      None             <none>        55555/TCP         3m31s
    48  ```
    49  
    50  In this case it's possible to open <http://10.152.183.180:33000/> in the browser, but your Cluster IP will most likely be different.