You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/AWS/AWS-EKS/README.md
+42-42Lines changed: 42 additions & 42 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,10 +74,10 @@ This process can also be done using the AWS Command Line Interface (CLI) or the
74
74
you can add to customize the cluster further. Cluster creation takes around 20 minutes.
75
75
76
76
## Installing the Amazon EBS CSI Driver
77
-
You need to install the Elastic Block Store (EBS) Container Storage Interface (CSI) Driver so the EKS cluster can manage Amazon EBS volumes. This is necessary if you want to run any application that has a database, such as Prometheus.
78
-
1. First, attach an OpenID Connect (OIDC) identity provider so that applications within the EKS cluster can access AWS resources. Execute the command `eksctl utils associate-iam-oidc-provider --region=<cluster_region> --cluster=<cluster_name> --approve`.
79
-
2. Next, grant the prospective EBS CSI driver IAM permissions to call the AWS APIs with this command:
80
-
'''
77
+
You need to install the Elastic Block Store (EBS) Container Storage Interface (CSI) Driver so the EKS cluster can manage Amazon EBS volumes. This is necessary if you want to run any application that has a database, such as Prometheus.
78
+
1. First, attach an OpenID Connect (OIDC) identity provider so that applications within the EKS cluster can access AWS resources. Execute the command `eksctl utils associate-iam-oidc-provider --region=<cluster_region> --cluster=<cluster_name> --approve`.
79
+
2. Next, grant the prospective EBS CSI driver IAM permissions to call the AWS APIs with this command:
80
+
81
81
eksctl create iamserviceaccount \
82
82
--name ebs-csi-controller-sa \
83
83
--namespace kube-system \
@@ -87,78 +87,78 @@ This process can also be done using the AWS Command Line Interface (CLI) or the
87
87
--role-only \
88
88
--role-name AmazonEKS_EBS_CSI_DriverRole \
89
89
--region <cluster_region>
90
-
'''
91
-
3. Finally, add the EBS CSI driver with this command:
3. Execute these commands to get the URL. Login in with the username admin and the password EKS!sAWsome
133
-
```
131
+
132
+
3. Execute these commands to get the URL. Login in with the username admin and the password EKS!sAWsome
133
+
134
134
export ELB=$(kubectl get svc -n grafana grafana -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
135
135
echo "http://$ELB"
136
136
```
137
-
4. To create the dashboard for monitoring Prometheus metrics, go to the sidebar, click on the four square icon, and click '+Import.' For the ID, type in 3119. For tracking, select Prometheus. Hit Create.
138
-
5. For the Opencost dashbaord, go to the sidebar, click on the four square icon, and click '+Import.' Upload the opencostGrafana.json file, select Prometheus under tracking, and then create.
139
-
6. You need to edit the Grafana ini file to make Grafana publicly accessible. In order to do so, go to your terminal and run:
137
+
4. To create the dashboard for monitoring Prometheus metrics, go to the sidebar, click on the four square icon, and click '+Import.' For the ID, type in 3119. For tracking, select Prometheus. Hit Create.
138
+
5. For the Opencost dashbaord, go to the sidebar, click on the four square icon, and click '+Import.' Upload the opencostGrafana.json file, select Prometheus under tracking, and then create.
139
+
6. You need to edit the Grafana ini file to make Grafana publicly accessible. In order to do so, go to your terminal and run:
140
140
`kubectl edit -n grafana configmap/grafana`
141
-
7. Press the 'i' key to start editing and add this into the Grafana ini section:
142
-
```
141
+
7. Press the 'i' key to start editing and add this into the Grafana ini section:
142
+
143
143
documentation:
144
144
[security]
145
145
allow_embedding: true
146
146
[auth.anonymous]
147
147
enabled: true
148
148
[dataproxy]
149
149
timeout: 600
150
-
```
151
-
8. Type ':wq' to save the file and quit the editor.
## Adding EKS cluster to Chronos dashboard using the Grafana URL
155
-
1. Click the add modal on the dashboard. Select Cloudbased Services. Select EKS. Input your Grafana URL (ex: xxxx.region.xxx.amazonaws.com) at the root path.
156
-
2. You should now be able to view two Grafana embedded dashboards -- the Prometheus Metrics & Opencost! Anytime you want to view the status of other microservices, whether cloudbased or locally hosted, go back to the Dashboard on the sidebar menu and click a new modal.
155
+
1. Click the add modal on the dashboard. Select Cloudbased Services. Select EKS. Input your Grafana URL (ex: xxxx.region.xxx.amazonaws.com) at the root path.
156
+
2. You should now be able to view two Grafana embedded dashboards -- the Prometheus Metrics & Opencost! Anytime you want to view the status of other microservices, whether cloudbased or locally hosted, go back to the Dashboard on the sidebar menu and click a new modal.
Credit for Knote application goes to the user learnK8s on [Github](https://github.com/learnk8s). Here is the source project [folder](https://github.com/learnk8s/knote-js/tree/master/04-05/kube).
163
+
Credit for Knote application goes to the user learnK8s on [Github](https://github.com/learnk8s). Here is the source project [folder](https://github.com/learnk8s/knote-js/tree/master/04-05/kube).
0 commit comments