mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-27 00:30:18 +00:00
63 lines
2.6 KiB
Markdown
63 lines
2.6 KiB
Markdown
|
## Running your first containers in Kubernetes
|
||
|
|
|
||
|
|
Ok, you've run one of the [getting started guides](https://kubernetes.io/docs/getting-started-guides/) and you have
|
||
|
|
successfully turned up a Kubernetes cluster. Now what? This guide will help you get oriented
|
||
|
|
to Kubernetes and running your first containers on the cluster.
|
||
|
|
|
||
|
|
### Running a container (simple version)
|
||
|
|
|
||
|
|
From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides.
|
||
|
|
|
||
|
|
The [`kubectl run`](https://kubernetes.io/docs/user-guide/kubectl/kubectl_run.md) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](https://kubernetes.io/docs/user-guide/pods.md) listening on port 80. It will also create a [deployment](https://kubernetes.io/docs/user-guide/deployments.md) named `my-nginx` to ensure that there are always two pods running.
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl run my-nginx --image=nginx --replicas=2 --port=80
|
||
|
|
```
|
||
|
|
|
||
|
|
Once the pods are created, you can list them to see what is up and running:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl get pods
|
||
|
|
```
|
||
|
|
|
||
|
|
You can also see the deployment that was created:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl get deployment
|
||
|
|
```
|
||
|
|
|
||
|
|
### Exposing your pods to the internet.
|
||
|
|
|
||
|
|
On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](https://kubernetes.io/docs/user-guide/services.md#publishing-services---service-types) for the pods,
|
||
|
|
to do this run:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl expose deployment my-nginx --port=80 --type=LoadBalancer
|
||
|
|
```
|
||
|
|
|
||
|
|
This should print the service that has been created, and map an external IP address to the service. Where to find this external IP address will depend on the environment you run in. For instance, for Google Compute Engine the external IP address is listed as part of the newly created service and can be retrieved by running
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl get services
|
||
|
|
```
|
||
|
|
|
||
|
|
In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a firewall to allow traffic on port 80.
|
||
|
|
|
||
|
|
### Cleanup
|
||
|
|
|
||
|
|
To delete the two replicated containers, delete the deployment:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
kubectl delete deployment my-nginx
|
||
|
|
```
|
||
|
|
|
||
|
|
### Next: Configuration files
|
||
|
|
|
||
|
|
Most people will eventually want to use declarative configuration files for creating/modifying their applications. A [simplified introduction](https://kubernetes.io/docs/user-guide/deploying-applications.md)
|
||
|
|
is given in a different document.
|
||
|
|
|
||
|
|
|
||
|
|
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||
|
|
[]()
|
||
|
|
<!-- END MUNGE: GENERATED_ANALYTICS -->
|