-
Notifications
You must be signed in to change notification settings - Fork 35
/
Copy path_get_started_kubernetes.md.erb
332 lines (190 loc) · 19 KB
/
_get_started_kubernetes.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
<%
=begin
apps: none
platforms: kubernetes
id: get_started_kubernetes
=end %>
> NOTE: This guide focuses on Minikube, but we also have similar guides for [Google Kubernetes Engine (GKE)](/google/get-started-gke), [Azure Kubernetes Service (AKS)](/azure/get-started-aks) and [Amazon Elastic Container Service for Kubernetes (EKS)](/aws/get-started-eks). We also have a guide on [performing more complex post-deployment tasks](https://docs.bitnami.com/tutorials/secure-wordpress-kubernetes-managed-database-ssl-upgrades), including setting up TLS with Let's Encrypt certificates and performing rolling updates.
<%# intro_k8s %>
### Introduction
In recent years, containers have become the definitive way to develop applications because they provide packages that contain everything you need to run your applications: code, runtime, databases, system libraries, etc.
[Kubernetes](https://kubernetes.io/) is an open source solution for managing application containers. With Kubernetes, you can decide when your containers should run, increase, or decrease the size of application containers or check the resource consumption of your application deployments. The Kubernetes project is based on Google's experience working with containers, and it is gaining momentum as the easiest and the most recommended way to manage containers in production.
Applications can be installed in Kubernetes using [Helm charts](https://helm.sh/). Helm charts are packages that contain all the information that Kubernetes needs to know for managing a specific application within the cluster.
This guide will walk you, step by step, through the process of deploying applications within a Kubernetes cluster using [Bitnami Helm charts](https://github.com/bitnami/charts).
### Introducing Kubernetes
Kubernetes is an open source project designed specifically for container orchestration. Kubernetes offers a number of [key features](https://kubernetes.io/docs/whatisk8s/), including multiple storage APIs, container health checks, manual or automatic scaling, rolling upgrades and service discovery. Applications can be installed to a Kubernetes cluster via [Helm charts](https://helm.sh/), which provides streamlined package management functions.
If you're new to this container-centric infrastructure, the easiest way to get started with Kubernetes is with [Bitnami Helm charts](https://bitnami.com/kubernetes). Bitnami offers a number of stable, production-ready Helm charts to deploy popular software applications in a Kubernetes cluster.
<%= anchors 'kubernetes-native-app-architecture' %>
#### Kubernetes Native App architecture
The architecture of a typical Cloud-Native application consists of 3-tiers: a persistence or database tier, backend tier and frontend tier for your application.
In Kubernetes, you define and create multiple resources for each of these tiers, as you can see in the following diagram:
<%= documentation_img '/images/img/platforms/kubernetes/k8-architecture.png', 'Kubernetes architecture' %>
#### Working with Kubernetes
Kubernetes is platform-agnostic and integrates with a number of different cloud providers, allowing you to pick the platform that best suits your needs. Check [Kubernetes official documentation](https://kubernetes.io/docs/getting-started-guides/) to find out the right solution for you.
There are two different interfaces from which you can manage the resources on your cluster:
* Kubernetes command line interface: [kubectl](https://kubernetes.io/docs/user-guide/kubectl-overview/)
* Kubernetes web-based user interface: [Dashboard](https://kubernetes.io/docs/user-guide/ui/)
### Introducing Helm
The official [Helm](https://helm.sh/) webpage defines Helm as a "package manager for Kubernetes" but, it is more than this. Helm is a tool for managing applications that run in the Kubernetes cluster manager. Helm provides a set of operations that are useful for managing applications, such as: inspect, install, upgrade and delete.
#### Helm Charts: applications ready-to-deploy
Helm charts are packages of pre-configured Kubernetes resources. A Helm chart describes how to manage a specific application on Kubernetes. It consists of metadata that describes the application, plus the infrastructure needed to operate it in terms of the standard Kubernetes primitives. Each chart references one or more (typically Docker-compatible) container images that contain the application code to be run.
Helm charts contains at least these two elements:
* A description of the package (*chart.yml*).
* One or more templates, which contains Kubernetes manifest files.
Despite the fact you can run application containers using the Kubernetes command line (*kubectl*), the easiest way to run workloads in Kubernetes is using the ready-made Helm charts. Helm charts simply indicate to Kubernetes how to perform the application deployment and how to manage the container clusters.
[Bitnami](https://bitnami.com/kubernetes) provides a set of stable and tested charts that give you the opportunity to deploy popular software application with ease and confidence.
<%#/ intro_k8s %>
### Overview
[Minikube](https://kubernetes.io/docs/getting-started-guides/minikube/) is the official way to run Kubernetes locally. It is a tool that runs a single-node Kubernetes cluster inside a Virtual Machine (VM) on your computer. It is an easy way to try out Kubernetes and is also useful for testing and development scenarios.
> TIP: For more information on how to run a Kubernetes cluster on other platforms, please refer to [our other guides](/kubernetes/).
In this tutorial, you will learn how to install the needed requirements to run Bitnami applications on Kubernetes using Minikube.
Here are the steps you'll follow in this tutorial:
* [Configure the platform](#k8_tutorial_step1)
* [Create a Kubernetes cluster](#k8_tutorial_step2)
* [Install the *kubectl* command-line tool](#k8_tutorial_step3)
* [Install Helm](#k8_tutorial_step4)
* [Install an application using a Helm chart](#k8_tutorial_step5)
* [Access the Kubernetes Dashboard](#k8_tutorial_step6)
* [Uninstall an application using Helm](#k8_tutorial_step7)
The next sections will walk you through these steps in detail.
### Assumptions and prerequisites
This guide focuses on deploying Bitnami applications in a Kubernetes cluster running on Minikube. The example applications are [Redis, MongoDB, Odoo and WordPress](#k8_tutorial_step5).
This guide assumes that you have [VirtualBox](https://www.virtualbox.org/wiki/Downloads) installed on your computer or a similar [virtualization software](https://github.com/kubernetes/minikube#requirements).
<%= anchors 'option-1-install-minikube' %>
<%= anchors 'option-1-create-a-cluster-using-minikube' %>
### Step 1: Configure the platform
The first step for working with Kubernetes clusters is to have Minikube installed if you have selected to work locally.
Install Minikube in your local system, either by using a virtualization software such as VirtualBox or a local terminal.
* Browse to the [Minikube latest releases page](https://github.com/kubernetes/minikube/releases).
* Select the distribution you wish to download depending on your Operating System.
> NOTE: This tutorial assumes that you are using Mac OSX or Linux OS. The Minikube installer for Windows is under development. To get an experimental release of Minikube for Windows, check the [Minikube releases page](https://github.com/kubernetes/minikube/releases).
* Open a new console window on the local system or open your VirtualBox.
* To obtain the latest Minikube release, execute the following command depending on your OS. Replace the OS_DISTRIBUTION placeholder with the software distribution for your platform, which are "darwin" for OS X, "linux" for Linux and "windows" for Windows.
$ curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-OS_DISTRIBUTION-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
<%= anchors 'option-2-create-a-cluster-on-gke' %>
### Step 2: Create a Kubernetes cluster
By starting Minikube, a single-node cluster is created. Run the following command in your terminal to complete the creation of the cluster:
$ minikube start
To run your commands against Kubernetes clusters, the *kubectl* CLI is needed. Check step 3 to complete the installation of *kubectl*.
<%# kubectl_helm %>
<%= anchors 'step-3-install-kubectl-command-line' %>
### Step 3: Install the *kubectl* command-line tool
<%= partial 'platforms/kubernetes/install_kubectl.md.erb' %>
<%= anchors 'step-4-install-helm-and-tiller', 'step-4-install-and-configure-helm-and-tiller' %>
### Step 4: Install and configure Helm
<%= partial 'platforms/kubernetes/install_configure_helm.md.erb' %>
Add the Bitnami repository to Helm with the following command:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
<%#/ kubectl_helm %>
### Step 5: Install an application using a Helm Chart
A Helm chart describes a specific version of an application, also known as a "release". The "release" includes files with Kubernetes-needed resources and files that describe the installation, configuration, usage and license of a chart.
The steps below show how to run the following Bitnami applications using Helm charts:
* [Redis](https://kubeapps.com/charts/bitnami/redis)
* [MongoDB](https://kubeapps.com/charts/bitnami/mongodb)
* [Odoo](https://kubeapps.com/charts/bitnami/odoo)
* [WordPress](https://kubeapps.com/charts/bitnami/wordpress)
These are just some concrete examples of application releases. [Find more Bitnami charts](https://kubeapps.com/charts/search?q=bitnami).
By executing the *helm install* command the application will be deployed on the Kubernetes cluster. You can install more than one chart across the cluster or clusters.
> IMPORTANT: If you don't specify a release name, one will be automatically assigned.
You can find an example of the installation of Redis using Helm charts below:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install redis bitnami/redis
> NOTE: Check the configurable parameters of the Redis chart and their default values at the [GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/redis#configuration).
Once you have the chart installed a "Notes" section will be shown at the bottom of the installation information. It contains important instructions about how to obtain your application's IP address or credentials. Please check it carefully:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-51.png', 'Application deployment on Kubernetes' %>
> TIP: Unlike cloud platforms, Minikube doesn't support a load balancer so, if you're deploying the application on Minikube, use the command below instead:
>
> $ helm repo add bitnami https://charts.bitnami.com/bitnami
> $ helm install redis bitnami/redis --set serviceType=NodePort
>
> You should see output similar to that shown below as the chart is installed on Minikube.
>
> <%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-52.png', 'Application deployment on Minikube' %>
----
> IMPORTANT: When deploying on Minikube, you may see errors such as *CrashLoopBackOff* and your application may fail to start. This is typically an indication that the cluster does not have sufficient memory available to it. To resolve this error, make more resources available to the cluster (we recommend a minimum of 3 GB RAM) and try again.
Find how to install MongoDB, Odoo or WordPress in the examples below:
* To install on Minikube, run the following command:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install mongodb bitnami/mongodb --set serviceType=NodePort
> NOTE: Check the configurable parameters of the MongoDB chart and their default values at the [GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/mongodb#configuration).
* To install on Minikube, run the following command:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install odoo bitnami/odoo --set serviceType=NodePort
> NOTE: Check the configurable parameters of the Odoo chart and their default values at the [GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/odoo#configuration).
* To install on Minikube, run the following command:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install wordpress bitnami/wordpress --set mariadb.image=bitnami/mariadb:10.1.21-r0 --set serviceType=NodePort
> NOTE: Check the configurable parameters of the WordPress chart and their default values at the [GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/wordpress#configuration).
Now, you can manage your deployments from the Kubernetes Dashboard. Follow the instructions below to access the Web user interface.
<%# dashboard_links %>
<%= anchors 'step-6-access-kubernetes-dashboard' %>
### Step 6: Access the Kubernetes Dashboard
The [Kubernetes Dashboard](https://github.com/kubernetes/dashboard) is a Web user interface from which you can manage your clusters in a more simple and digestible way. It provides information on the cluster state, deployments and container resources. You can also check both the credentials and the log error file of each pod within the deployment.
To open the Kubernetes Dashboard, you just need to run the following command:
$ kubectl proxy
With this command, you will create a proxy server on port 8001 for accessing the Kubernetes Dashboard. It will be available at: *localhost:8001/ui*. The home screen shows the "Workloads" section. Here you get an overview of the following cluster elements:
* CPU usage
* Memory usage
* Deployments
* Replica Sets
* Pods
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-61.png', 'Access Kubernetes dashboard' %>
From this home screen, you can perform some basic actions such as:
* Monitoring the status of your deployments and pods.
* Checking pod and container(s) logs to identify possible errors during the creation of the containers.
* Finding application credentials.
#### Monitor the status of Deployments and Pods
##### Monitor Deployments
* To check detailed information about the status of your deployments, navigate to the "Workloads -> Deployments" section located on the left menu. It shows a screen with a graphical representation of the CPU and memory usage, as well as a list of all deployments you have in your cluster.
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-62.png', 'Access Kubernetes dashboard' %>
* Click each deployment to obtain detailed information of the selected deployment:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-63.png', 'Access Kubernetes dashboard' %>
##### Monitoring pods
Pods are the smallest units in Kubernetes deployments. They can contain one or multiple containers (that need to share resources in order to work together). [Learn more about pods](https://kubernetes.io/docs/user-guide/pods/).
When you click on a pod in the "Workloads -> Pods", you access the pod list. By selecting a pod, you will see the "Details" section that contains information related to the pod,and a "Containers" section that includes the information related to this pod's container(s).
Follow these instructions to access pod and container information:
* To check the status of your deployments in detail, navigate to the "Workloads -> Pods" section located on the left menu. It shows the pod list:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-64.png', 'Access Kubernetes dashboard' %>
* Click the pod you'd like to access further details for.
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-65.png', 'Access Kubernetes dashboard' %>
#### Check logs
The Kubernetes Dashboard allows you to check the logs of both the pod and any containers belonging to the pod to detect possible errors that might have occurred. To access the logs viewer, follow the steps below:
* Navigate to the "Workloads -> Pods" section located on the left menu, select the pod you'd like to check from the pod list.
* In the detail page of the selected pod, you will find a "View logs" link both in the "Details" and "Containers" section. Click the one you want to see:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-66.png', 'Access Kubernetes dashboard' %>
The logs viewer opens:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-67.png', 'Access Kubernetes dashboard' %>
#### Find application credentials
The application credentials are shown in the "Notes" section after installing the application chart:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-69.png', 'Access Kubernetes dashboard' %>
You can get the application username and password at any time by running the following command, replacing POD-NAME with the name of the pod:
$ kubectl describe pod POD-NAME
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-610.png', 'Access Kubernetes dashboard' %>
As you can see in the image above, the application password is configured as a secret password. To get it, browse to the Kubernetes Dashboard and follow these instructions:
* Navigate to the "Config -> Secrets" section located on the left menu.
* Click the application for which you wish to obtain the credentials.
* In the "Data" section, click the eye icon to see the password:
<%= documentation_img '/images/img/platforms/kubernetes/k8-tutorial-68.png', 'Access Kubernetes dashboard' %>
### Step 7: Uninstall an application using Helm
To uninstall an application, you need to run the *helm delete* command. Every Kubernetes resource that is tied to that release will be removed.
> TIP: To get the release name, you can run the *helm list* command.
$ helm delete MY_RELEASE
> NOTE: Remember that MY_RELEASE is a placeholder, replace it with the name you have used during the chart installation process.
### Useful links
To learn more about the topics discussed in this guide, use the links below:
* [Production-ready Kubernetes applications by Bitnami](https://bitnami.com/kubernetes)
* [Intro to deploying your favourite apps on Kubernetes](https://www.youtube.com/watch?v=bd8mXpFLUig)
* [Kubeapps](http://kubeapps.com/)
* [Kubernetes](https://kubernetes.io/)
* [Helm](https://helm.sh/)
* [Google Kubernetes Engine](https://cloud.google.com/container-engine/)
* [Minikube](https://github.com/kubernetes/minikube)
* [Bitnami](https://bitnami.com/)
> TIP: If you already have a Kubernetes cluster created with some running application deployments, you can take a step further and try to scale and upgrade them. For detailed instructions, refer to our tutorial on [deploying, scaling and upgrading an application on Kubernetes with Helm](https://docs.bitnami.com/tutorials/deploy-application-kubernetes-helm).
Do you want to learn more about how to deploy Bitnami applications on Kubernetes? Watch the following video for getting started with Kubernetes architecture and Helm charts:
<div>
<%= youtube_iframe("bd8mXpFLUig") %>
</div>
Watch the following video to learn how to install Kubernetes locally:
<%= youtube_iframe("JgqHS-30FXY?v=Mmo63uPlbwc&list=PLGgVZHi3XQNn8uIb3wy3u-Eq0xL-BU2Nk") %>
<%#/ dashboard_links %>