mirror of https://github.com/k3s-io/k3s
119 lines
4.6 KiB
Markdown
119 lines
4.6 KiB
Markdown
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
||
|
||
<!-- BEGIN STRIP_FOR_RELEASE -->
|
||
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING"
|
||
width="25" height="25">
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING"
|
||
width="25" height="25">
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING"
|
||
width="25" height="25">
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING"
|
||
width="25" height="25">
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING"
|
||
width="25" height="25">
|
||
|
||
<h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2>
|
||
|
||
If you are using a released version of Kubernetes, you should
|
||
refer to the docs that go with that version.
|
||
|
||
<!-- TAG RELEASE_LINK, added by the munger automatically -->
|
||
<strong>
|
||
The latest release of this document can be found
|
||
[here](http://releases.k8s.io/release-1.1/docs/user-guide/quick-start.md).
|
||
|
||
Documentation for other releases can be found at
|
||
[releases.k8s.io](http://releases.k8s.io).
|
||
</strong>
|
||
--
|
||
|
||
<!-- END STRIP_FOR_RELEASE -->
|
||
|
||
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
||
|
||
# Kubernetes User Guide: Managing Applications: Quick start
|
||
|
||
**Table of Contents**
|
||
<!-- BEGIN MUNGE: GENERATED_TOC -->
|
||
|
||
- [Kubernetes User Guide: Managing Applications: Quick start](#kubernetes-user-guide-managing-applications-quick-start)
|
||
- [Launching a simple application](#launching-a-simple-application)
|
||
- [Exposing your application to the Internet](#exposing-your-application-to-the-internet)
|
||
- [Killing the application](#killing-the-application)
|
||
- [What's next?](#whats-next)
|
||
|
||
<!-- END MUNGE: GENERATED_TOC -->
|
||
|
||
This guide will help you get oriented to Kubernetes and running your first containers on the cluster. If you are already familiar with the docker-cli, you can also checkout the docker-cli to kubectl migration guide [here](docker-cli-to-kubectl.md).
|
||
|
||
|
||
## Launching a simple application
|
||
|
||
Once your application is packaged into a container and pushed to an image registry, you’re ready to deploy it to Kubernetes.
|
||
|
||
For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](kubectl/kubectl_run.md) command below will create two nginx replicas, listening on port 80.
|
||
|
||
```console
|
||
$ kubectl run my-nginx --image=nginx --replicas=2 --port=80
|
||
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
|
||
my-nginx my-nginx nginx run=my-nginx 2
|
||
```
|
||
|
||
You can see that they are running by:
|
||
|
||
```console
|
||
$ kubectl get po
|
||
NAME READY STATUS RESTARTS AGE
|
||
my-nginx-l8n3i 1/1 Running 0 29m
|
||
my-nginx-q7jo3 1/1 Running 0 29m
|
||
```
|
||
|
||
Kubernetes will ensure that your application keeps running, by automatically restarting containers that fail, spreading containers across nodes, and recreating containers on new nodes when nodes fail.
|
||
|
||
## Exposing your application to the Internet
|
||
|
||
Through integration with some cloud providers (for example Google Compute Engine and AWS EC2), Kubernetes enables you to request that it provision a public IP address for your application. To do this run:
|
||
|
||
```console
|
||
$ kubectl expose rc my-nginx --port=80 --type=LoadBalancer
|
||
service "my-nginx" exposed
|
||
```
|
||
|
||
To find the public IP address assigned to your application, execute:
|
||
|
||
```console
|
||
$ kubectl get svc my-nginx
|
||
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
|
||
my-nginx 10.179.240.1 25.1.2.3 80/TCP run=nginx 8d
|
||
```
|
||
|
||
You may need to wait for a minute or two for the external ip address to be provisioned.
|
||
|
||
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](services-firewalls.md).
|
||
|
||
If you're running on AWS, Kubernetes creates an ELB for you. ELBs use host
|
||
names, not IPs, so you will have to do `kubectl describe svc my-nginx` and look
|
||
for the `LoadBalancer Ingress` host name. Traffic from external IPs is allowed
|
||
automatically.
|
||
|
||
## Killing the application
|
||
|
||
To kill the application and delete its containers and public IP address, do:
|
||
|
||
```console
|
||
$ kubectl delete rc my-nginx
|
||
replicationcontrollers/my-nginx
|
||
$ kubectl delete svc my-nginx
|
||
services/my-nginx
|
||
```
|
||
|
||
## What's next?
|
||
|
||
[Learn about how to configure common container parameters, such as commands and environment variables.](configuring-containers.md)
|
||
|
||
|
||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||
[]()
|
||
<!-- END MUNGE: GENERATED_ANALYTICS -->
|