Updates for exercise 4-6.
This commit is contained in:
@ -12,13 +12,10 @@ Another alternative approach for deploying and managing the lifecycle of more co
|
||||
|
||||
The goal of an **Operator** is to put operational knowledge into software. Previously this knowledge only resided in the minds of administrators, various combinations of shell scripts or automation software like Ansible. It was outside of your Kubernetes cluster and hard to integrate. **Operators** change that.
|
||||
|
||||
**Operators** are the missing piece of the puzzle in Kubernetes to implement and automate common Day-1 (installation, configuration, etc.) and Day-2 (re-configuration, update, backup, failover, restore, etc.) activities in a piece of software running inside your Kubernetes cluster, by integrating natively with Kubernetes concepts and APIs.
|
||||
**Operators** are the missing piece of the puzzle in Kubernetes to implement and automate common Day-1 (installation, configuration, etc.) and Day-2 (re-configuration, update, backup, failover, restore, etc.) activities in a piece of software running inside your Kubernetes cluster, by integrating natively with Kubernetes concepts and APIs.
|
||||
|
||||
With Operators you can stop treating an application as a collection␃of primitives like **Pods**, **Deployments**, **Services** or **ConfigMaps**, but instead as a singular, simplified custom object that only exposes the specific configuration values that make sense for the specific application.
|
||||
|
||||
|
||||
|
||||
|
||||
## 5.1 - Deploying an operator
|
||||
|
||||
Deploying an application via an **Operator** is generally a two step process. The first step is to deploy the **Operator** itself.
|
||||
@ -52,12 +49,11 @@ Paste the above snippet of YAML into the editor and replace the instance of `use
|
||||
Click **Create**. In a minute or so you should see the Grafana operator installed and running in your project.
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-------------------------------------------------------------------:|
|
||||
| *Deploying grafana operator via static yaml* |
|
||||
</Zoom>
|
||||
|
||||
|
||||
## 5.2 - Deploying an operator driven application
|
||||
|
||||
With our Grafana operator now running it will be listening for the creation of a `grafana` custom resource. When one is detected the operator will deploy the Grafana application according to the specifcation we supplied.
|
||||
@ -100,12 +96,11 @@ spec:
|
||||
```
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-------------------------------------------------------------------:|
|
||||
| *Deploying grafana application via the grafana operator* |
|
||||
</Zoom>
|
||||
|
||||
|
||||
## 5.3 Logging into the application
|
||||
|
||||
While we are in the **Administrator** perspective of the web console let's take a look at a couple of sections to confirm our newly deployed Grafana application is running as expected.
|
||||
@ -115,12 +110,11 @@ For our first step click on the **Workloads** category on the left hand side men
|
||||
We should see that a `grafana-deployment-<id>` pod with a **Status** of `Running`.
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-------------------------------------------------------------------:|
|
||||
| *Confirming the grafana pod is running* |
|
||||
</Zoom>
|
||||
|
||||
|
||||
Now that we know the Grafana application **Pod** is running let's open the application and confirm we can log in.
|
||||
|
||||
Click the **Networking** category on the left hand side menu and then click **Routes**.
|
||||
@ -135,10 +129,8 @@ Once the new tab opens we should be able to login to Grafana using the credentia
|
||||
| *Confirming the grafana route is working* |
|
||||
</Zoom>
|
||||
|
||||
|
||||
## 5.4 - Bonus objective: Grafana dashboards
|
||||
|
||||
If you have time, take a while to learn about the https://grafana.com/grafana/dashboards and how Grafana can be used to visualise just about anything.
|
||||
|
||||
|
||||
Well done, you've finished exercise 5! 🎉
|
||||
Well done, you've finished exercise 5! 🎉
|
||||
|
||||
Reference in New Issue
Block a user