1.4 KiB
In addition to the imperative style commands described elsewhere, Kubernetes supports declarative YAML or JSON configuration files. Often times config files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, producing a more robust, reliable and archival system.
Running a container from a pod configuration file
$ cd kubernetes
$ kubectl create -f ./pod.yaml
Where pod.yaml contains something like:
{% include code.html language="yaml" file="pod.yaml" ghlink="/docs/user-guide/pod.yaml" %}
You can see your cluster's pods:
$ kubectl get pods
and delete the pod you just created:
$ kubectl delete pods nginx
Running a replicated set of containers from a configuration file
To run replicated containers, you need a Replication Controller. A replication controller is responsible for ensuring that a specific number of pods exist in the cluster.
$ cd kubernetes
$ kubectl create -f ./replication.yaml
Where replication.yaml contains:
{% include code.html language="yaml" file="replication.yaml" ghlink="/docs/user-guide/replication.yaml" %}
To delete the replication controller (and the pods it created):
$ kubectl delete rc nginx