...
Environment Variable | Description | Value needs to be specified |
|---|---|---|
KUBERNETES_CLUSTER_ID | Give your cluster a unique name in order to identify clusters within Yotascale. | Yes |
PROMETHEUS_API_ENDPOINT | Point the agent to the Prometheus API by providing the URL. | Yes |
YOTASCALE_API_KEY | This Environment variable authenticates (and identifies) this agent against a Service Role that your administrators have subscribed to by default. This will be pre-populated in the deployment descriptor and does not need to be updated by the user. | No |
YOTASCALE_KUBERNETES_API_ENDPOINT | This is the URL of the Yotascale API that allows the agent to authenticate iteself with Yotascale, and send frequent heartbeats for monitoring. This URL will be pre-populated in the deployment descriptor. | No |
Step 3 (Optional): Create Self-Signed Certificate Secret for calling Prometheus API
If your Prometheus is using a self-signed certificate, you would need to create a Secret with your PEM file and mount the Secret as a Volume and file on the Pod. The agent would use this certificate when making calls to Prometheus.
Create a Secret named ‘prometheus-certificate’ using the following command. The certificate could be named anything.
| Code Block | ||
|---|---|---|
| ||
kubectl create secret generic prometheus-certificate \
--from-file=/path/to/certificate.pem --output=yaml --namespace yotascale
|
When the Pod is up and running, the certificate is mounted at the following location
| Code Block | ||
|---|---|---|
| ||
/opt/yotascale/prometheus-certificate/certificate.pem |
Step 4 : Deploy Yotascale Agent on Kubernetes
Once you have updated the deployment descriptor, apply the updated file onto your cluster
| Code Block | ||
|---|---|---|
| ||
kubectl apply -f yotascale-kubernetes-agent-deployment.yaml |
Step
...
5: Verifying the Installation
Once you have applied the deployment descriptor to your cluster, you will see it appear in the List of Clusters widget in the Manage Cloud Services Page.
...